Repository navigation
fix: keep event entity available when a device disappears (#28), release 3.1.0 - #29
Merged
Merged
Conversation
Event entity follows gateway status only (MQTT discovery) or stays available (HACS), so reconnects no longer replay the last key to state triggers. Switch keeps presence-based availability. Release 3.1.0.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #28.
Event entity went unavailable on device loss; on reconnect HA restored the old timestamp with event_type/key, so state-triggered automations replayed the last key on every reconnect (sleeping BT remotes).
Verified in HA 2026.9.4 with a uinput repro: 1 press + 3 unplug/replug cycles fired the automation 4x before, 1x after.