Report state of room-assistant node via MQTT after a broker reconnect #218
Labels
Comments
github-actions bot
pushed a commit
that referenced
this issue
Aug 16, 2020
# [2.9.0-beta.1](v2.8.2...v2.9.0-beta.1) (2020-08-16) ### Features * **bluetooth-classic:** add option for preserving sensor state ([7cd2afe](7cd2afe)), closes [#156](#156) * **bluetooth-classic:** add scan time limit option ([ae40009](ae40009)), closes [#179](#179) * **home-assistant:** refresh states after broker re-connect ([85064e6](85064e6)), closes [#218](#218)
|
🎉 This issue has been resolved in version 2.9.0-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
github-actions bot
pushed a commit
that referenced
this issue
Aug 23, 2020
# [2.9.0](v2.8.2...v2.9.0) (2020-08-23) ### Bug Fixes * **bluetooth-classic:** exclude old measurements from preservation ([10b0e21](10b0e21)) ### Features * **bluetooth-classic:** add option for preserving sensor state ([7cd2afe](7cd2afe)), closes [#156](#156) * **bluetooth-classic:** add scan time limit option ([ae40009](ae40009)), closes [#179](#179) * **home-assistant:** refresh states after broker re-connect ([85064e6](85064e6)), closes [#218](#218)
|
🎉 This issue has been resolved in version 2.9.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The state of room-assistant nodes is lost after a MQTT broker restart
Describe the solution you'd like
After a MQTT broker restart, have room assistant nodes detect the reconnect event and report their current state to the broker. That would ensure that all subscribers get to a known state after a broker restart.
Describe alternatives you've considered
Polling against the current REST APIs
Issue a Room Assistant service restart request via Ansible
Additional context
N/A
The text was updated successfully, but these errors were encountered: