v3.4.0-beta.27

Requires pylxpweb 0.9.36 — the first stable release of the 0.9.36 line (installed automatically).

Fixed

• EPS Load Power was a duplicate of EPS Power (#336, closes #335, thanks @brendonlobo123): on the off-grid family the EPS Load sensors were aliases of the combined EPS output — the original off-grid enablement validated the alias at a moment when the smart load was idle, the one state where the two quantities match. EPS Load Power now reads the cloud's real epsLoadPower field: the always-connected-loads subset of the backup output, diverging from EPS Power exactly when your smart load runs (matching the EG4 portal).
• Grid Peak Shaving Power read unknown in LOCAL mode (#334, found by the 3.4.0 validation sweep): the beta.25 fix reached cloud and hybrid but the LOCAL-mode targeted register poll still skipped register 206. LOCAL now reads it like the other modes.

Breaking / Behavior Changes (off-grid family)

• EPS Load Power L1 / EPS Load Power L2 are retired: EG4 provides no per-leg load values — these were never real measurements, only copies of EPS Power L1/L2. Registry entries clean up automatically; point dashboards/automations at EPS Power L1/L2 (the identical values those sensors always showed).
• EPS Load Power (total) changes meaning: previously the fabricated combined sum, now the true EPS-loads subset. Entity and unique ID unchanged — statistics carry over — but expect a level shift in history if your smart load runs regularly. Pure-LOCAL installs read unknown for this sensor (the subset is cloud-only; no local register is known).

Validated on the docker hybrid rig (grid-tied regression: EPS family unchanged, clean startup). 1949 tests.