Skip to content

fix: do not let no-op Home Assistant events consume cooldown#12083

Open
LeonSGP43 wants to merge 1 commit into
NousResearch:mainfrom
LeonSGP43:fix/homeassistant-cooldown-noop-12062
Open

fix: do not let no-op Home Assistant events consume cooldown#12083
LeonSGP43 wants to merge 1 commit into
NousResearch:mainfrom
LeonSGP43:fix/homeassistant-cooldown-noop-12062

Conversation

@LeonSGP43

Copy link
Copy Markdown
Contributor

Summary

  • fix the Home Assistant adapter so no-op state_changed events do not consume the per-entity cooldown
  • update the cooldown timestamp only after _format_state_change(...) produces a real message
  • add a regression test that proves a 20 -> 20 event no longer suppresses the following 20 -> 21 change

Closes #12062.

Testing

  • python3 -m pytest -o addopts= tests/gateway/test_homeassistant.py

@alt-glitch alt-glitch added type/bug Something isn't working P2 Medium — degraded but workaround exists comp/gateway Gateway runner, session dispatch, delivery labels Apr 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp/gateway Gateway runner, session dispatch, delivery P2 Medium — degraded but workaround exists type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Home Assistant no-op state_changed events consume cooldown and suppress the next real change

2 participants