Skip to content

EPS: own sub-device, entities removed when the option is off - #2283

Merged
wills106 merged 2 commits into
wills106:mainfrom
Bl00d-B0b:feat/eps-subdevice
Aug 22, 2026
Merged

EPS: own sub-device, entities removed when the option is off#2283
wills106 merged 2 commits into
wills106:mainfrom
Bl00d-B0b:feat/eps-subdevice

Conversation

@Bl00d-B0b

Copy link
Copy Markdown
Contributor

Stacked on #2279 (sub-device infrastructure). Review the last commit only — the diff includes the parent until it merges.

The 36 EPS entities move from the main inverter device to <hub> EPS, linked to the inverter with via_device — the same pattern the battery pack devices already use. The redundant EPS prefix is dropped from the names, since the device now provides that context. Keys and entity ids are unchanged.

With the Emergency Power Option (EPS) switched off the entities are not created and the device is removed from the registry instead of lingering forever.

EPS Mute becomes a switch (write 0x43, readback 0xB7) instead of a read-only sensor, matching the cloud app.

Verified on an X3-Hybrid-G4 15 kW.

…ptions dialog

Energy Dashboard: the refresh only marked sensors inactive when a feature
switch was turned off - the entity stayed alive and its registry entry was
never removed, so the device accumulated sensors stuck at unavailable
(grid-to-battery, home-consumption and PV-variant sensors). They are now
removed and their registry entries purged.

Generic sub-device infrastructure, used by follow-up PRs that move the
EPS, Parallel, External Generator and Dry Contact families into their own
devices: entity descriptions gain device_group (assigns the entity to a
named sub-device linked to the inverter with via_device, the same pattern
as the battery pack devices) and active_when ({sensor_key: allowed values}
evaluated against polled hub.data; keys not polled on a model never block
availability). The hub tracks gated entities and adds or removes them as
conditions change, with a two-poll hysteresis so a stale readback right
after a write cannot make entities flicker. A sub-device whose option is
switched off is removed from the registry instead of lingering. Switch and
number writes publish the written value immediately, as selects and times
already did. Numbers gain max_key, letting a sensor value override
native_max_value. The number, select, switch, time and sensor platforms
honour all of it. No entities move in this PR.

The options dialog no longer shows feature switches the selected plugin
does not implement, and all feature options now default to off for new
entries, including the Energy Dashboard virtual device.
The 36 EPS entities were mixed into the main inverter device, which on a
hybrid means hundreds of entities in one list. They now use device_group
and appear under "<hub> EPS", linked to the inverter with via_device - the
same pattern the battery pack devices already use. The redundant EPS
prefix is dropped from the names, which the device now provides. Keys and
entity ids are unchanged.

With the Emergency Power Option (EPS) switched off the entities are not
created and the device is removed from the registry instead of lingering
forever.

EPS Mute becomes a switch (write 0x43, readback 0xB7) instead of a
read-only sensor, matching the cloud app.

Stacked on the sub-device infrastructure PR.
@wills106
wills106 merged commit 82e072f into wills106:main Aug 22, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants