Add alive signal to monitor that the service is up and running #3
Conversation
This file contains 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.
Recently, I've noticed that the service had gone down due to some issue, whether it was a network issue, or it was a cat bumping into the USB Neural Compute Stick and causing it to crash.
This adds a some new configuration for both a LWT (last will and testament), as well as topic for the alive status of the app.
What this will allow is the automation of a system alert, broadcast to my media devices in Home Assistant, that lets me know when it has not been running for some length of time.
Also, it fixes a bug where the initial "OFF" state was not getting broadcast to all camera topics.