v2.2.0 coming soon

[AndrewTapp]

Hierarchy & Aggregated Sensors

• Introduction of a clear site hierarchy

  • SolarEdge topology will be modeled as Site → Inverter → String → Optimizer.

• Addition of hierarchical aggregated sensors (kept per-optimizer sensors)

  • Existing per-optimizer sensors remain (Current/Voltages/Power/Energy/Last Measurement).
  • Addiiton of aggregated sensors at:
    • String level
    • Inverter level
    • Site level

• Device metadata & naming improvements

  • Inverter devices will show the serial number in hardware info.
  • Count sensors will be named contextually:
    • String: Optimizer count
    • Inverter: String count
    • Site: Inverter count

“Last Polled” Simplification

• Removal of per-entity “Last polled” sensors

  • Removal of “Last polled” entities from optimizer levels.

• Addition of a single integration-wide “Last polled” sensor

  • One timestamp sensor per config entry/site, updated after the full update pipeline completes.

• Defined update order

  • Update flow will be enforced as:
    1. Optimizers
    2. String aggregations
    3. Inverter aggregations
    4. Site aggregations
    5. Integration “Last polled”

Adaptive Polling (Reducing Portal Delay)

• Adaptive polling addition

  • The coordinator will ticks more frequently, but avoids unnecessary heavy refreshes.
  • Uses a lightweight single-optimizer check to detect when the portal has new data, then triggers a full refresh only when needed.
  • When data is stale (e.g., overnight), checks become less frequent to reduce portal load.

• Lifetime energy requests reduced

  • Lifetime energy is retrieved via a cached accessor (refreshed at most hourly) to avoid repeated portal calls.

[AndrewTapp]

v2.2.0 released today
https://github.com/AndrewTapp/solaredgeoptimizers/releases/tag/2.2.0