When the application starts, several messages are being published after the hub is polled to learn the current state of the hub. This causes issues since messages will be sent even if the event that triggers them isn't happening.
The messages that are currently being sent every time the application starts are:
The changes in this PR will cause pi-topd to stop sending these messages until the app is initialized. Also, a new message PUB_PITOPD_READY is published when this happens, to let other applications know about this.
Screenshots (feature, test output, profiling, dev tools etc)
[insert screenshots here]
Other notes (e.g. implementation quirks, edge cases, questions / issues)
Main changes
When the application starts, several messages are being published after the hub is polled to learn the current state of the hub. This causes issues since messages will be sent even if the event that triggers them isn't happening.
The messages that are currently being sent every time the application starts are:
The changes in this PR will cause
pi-topd
to stop sending these messages until the app is initialized. Also, a new messagePUB_PITOPD_READY
is published when this happens, to let other applications know about this.Screenshots (feature, test output, profiling, dev tools etc)
[insert screenshots here]
Other notes (e.g. implementation quirks, edge cases, questions / issues)
-
Manual testing tips
-
Tag anyone who definitely needs to review or help
-