String cumulative energy sensors not detected

[Liontooth]

Integration Version

3.5.0

Home Assistant Version

2026.7.4

Connection Mode

Cloud (HTTP)

Device Model(s)

6000XP

Describe the Bug

The integration currently relies on a regex pattern (_PV_STRING_SENSOR) that finds keys prefixed with pv (e.g., pv1_yield), but the Luxpower web API for Luxpower SNA US 6000 also returns per-string cumulative energy data using the ePv prefix:

  "ePvDay": "3",
  "ePv1Day": "3",
  "ePv2Day": "2.2",
  "ePv3Day": "0",
  "ePvAll": "2684.3",
  "ePv1All": "2684.3",
  "ePv2All": "912.4",
  "ePv3All": "0",

Note ePvDay and ePvAll in my situation is identical to ePv1Day and ePv1All.

Steps to Reproduce

1. Install eg4_web_monitor
2. Check sensors
3. Notice string cumulative sensors are missing

Home Assistant Logs

Screenshots

No response

[btli]

@Liontooth This is now released in v3.5.1-beta.5.

To get the per-string values on your Cloud connection:

1. Install the beta — HACS lists it as a pre-release, so select the version explicitly (or call update.install with version: v3.5.1-beta.5 on the integration's update entity), then restart Home Assistant.
2. The sensors are disabled by default: go to Settings → Devices & Services → EG4 Web Monitor → your inverter → entities, find PV1/PV2/PV3 Yield and PV1/PV2/PV3 Yield Lifetime, and enable the ones you want. They populate on the next refresh cycle (daily values update about every 5 minutes, lifetime hourly).

Two expectations to set: the values come from EG4's chart endpoints — the same figures the portal's energy charts show — and the scaling was live-verified (per-string lifetimes sum exactly to the portal's total lifetime yield on our dev inverter). And the cloud only exposes strings 1–3, so on units with more strings PV4–6 still require a local (Modbus/dongle) connection.

If the numbers you see don't match your portal charts, please report back here and we'll reopen.