FlexMeasures / flexmeasures-ha-integration

85%

main: 85%

LAST BUILD ON BRANCH v0.4.0

branch: v0.4.0

CHANGE BRANCH

x

Reset

Sync Branches

• v0.4.0
• chore/move-integration-from-core-to-hacs
• chore/upgrade-fm-client
• feat/v0.4.0-modernization
• feature/TUNES/automatic-change-control-type
• feature/TUNES/create-service-send-frbc-instruction
• feature/TUNES/limit-send-measurements
• feature/TUNES/manual-frbc-schedule
• feature/TUNES/send-active-actuator
• feature/get-measurements-by-source
• feature/services/expose-flex-model-context
• feature/services/get_measurement
• fix/TUNES/send-frbc-instruction
• fix/credential-leak-in-log
• fix/reload-integration-on-options-change
• main
• release/v0.3.8
• v0.2.0
• v0.2.0.dev0
• v0.2.0.dev1
• v0.2.0.dev2
• v0.2.0.dev3
• v0.2.1
• v0.2.10
• v0.2.11
• v0.2.12
• v0.2.13
• v0.2.2
• v0.2.3
• v0.2.4
• v0.2.5
• v0.2.7
• v0.2.8
• v0.2.8.dev1
• v0.2.8.dev2
• v0.2.8.dev3
• v0.2.9
• v0.3.8
• v0.3.9

Build # 29407909445

Build Type

push

github

Committed by web-flow

Commit Message

v0.4.0: several FlexMeasures servers, plus modernization for Home Assistant 2026.7 (#30)

* fix: stop logging the FlexMeasures client (and thus the password) on websocket connect

WebSocketHandler logged the whole FlexMeasuresClient at WARNING level on
every incoming S2 websocket connection. The client is a dataclass, so its
repr contains the configured password and username in plain text — they
ended up in the Home Assistant log, and in any log bundle shared for
support. The line was a leftover debug statement.

Adds a regression test that opens a websocket connection and asserts the
credentials do not appear in the captured log.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: F.N. Claessen <felix@seita.nl>

* feat: support several FlexMeasures servers, and modernize for Home Assistant 2026.7

Runtime state moves from a global hass.data[DOMAIN] onto the config
entry (entry.runtime_data), so the integration can be added more than
once. Each entry gets its own client, S2 datastore, schedule state,
device and schedule sensor. Services are now registered once for the
integration and resolve the entry per call, through an optional entry_id
field; Resource Managers reach a specific entry at
/api/websocket_custom/<entry_id>. With a single entry configured,
nothing changes for the user.

This also fixes a reload bug: services were registered per entry, and
the registration list was mutated in place, so after every options change
(which reloads the entry) the handlers bound to the *previous* entry
state were re-registered.

Config entry migration v3 -> v4 keeps existing installs intact: it
re-scopes the schedule sensor's unique id to the entry (so the entity
and its history survive) and moves the shared S2 datastore to the
entry's own store.

Further changes:
- config flow: drop the hardcoded defaults, which pointed a fresh
  install at one pilot's FlexMeasures server (https://seita.energy) and
  at the asset and sensor ids on it. The S... (continued)

Coverage Stats

461 of 541 relevant lines covered (85.21%)

0.85 hits per line