FlexMeasures / flexmeasures-ha-integration

84%

LAST BUILD ON BRANCH main

branch: main

CHANGE BRANCH

x

Reset

Sync Branches

• main
• 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
• 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 # 29295848247

Build Type

push

github

Committed by web-flow

Commit Message

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

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.

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

Coverage Stats

342 of 407 relevant lines covered (84.03%)

0.84 hits per line