One lost message stops SEM selling from a Sessy

[traktore-org]

@RienduPre has two Sessy batteries. SEM cannot sell to the grid from either, and it never says why.

The battery refuses every power setting while it is in its own "nom" mode. It has to be put in "api" mode first. Rien proved this himself: flipping the mode by hand makes the same write work straight away.

SEM does try to flip it. The flip is silently dropped, and SEM remembers it as done — so it never tries again. One lost message withdraws selling to the grid for good.

Two faults: SEM does not check that the flip landed, and it treats "I sent it" as "it worked".

[traktore-org]

Merged to develop; it rides tonight's beta (the release note here will name it).

What changed, in your terms:

• SEM now believes the select, not the service call. A flip to api counts only once select.sessy_N_power_strategy actually reads api; nothing is sent when it already does.
• A flip that has not landed after 60 s is re-sent and named once in the log — asked select.sessy_N_power_strategy for power strategy 'api' … and it still reads nom — and after three such misses the existing "A battery control write is not taken" Repair names the select with the wanted and the read value. The setpoint is not written, and the device is not blamed, until the strategy is in place — so "battery-to-grid unsupported" can no longer come from a strategy that never moved.

Still open, and the log line above is what will answer it: why HA cannot deliver SEM's select_option to that id while a manual call works. The line prints the exact entity id SEM targets; if it is not the select the Sessy integration serves right now (a renamed entity, a stale registry entry), that is the cause — the diagnostics options block asked for in the discussion would settle it.

One limitation I'm noting rather than hiding: the Repair is raised for the primary battery's ledger only (a pre-existing shape of the read-back check); the second Sessy's misses reach the log but not a Repair. Follow-up filed as a note here.

Refs #978

[traktore-org]

🔔 Closing the loop — this was fixed and shipped in v2.1.0-beta.30, but the release reply never landed here (our miss, caught by an automated audit).

🐛 A dropped power-strategy flip silently withdrew battery-to-grid (#978,

Full details: v2.1.0-beta.30 release notes. Please update to the latest beta and let us know whether it resolves it for you — then we'll close.