publish battery_dangerous message if battery level is dangerous #15135
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
Signed-off-by: RomanBapst <bapstroman@gmail.com>
|
I agree and this was already fixed in #14960, although I haven't yet reviewed and tested it in detail (sorry @BazookaJoe1900). |
|
@dagar Can we merge this? I'm not sure about the state of the other PR. |
dagar
approved these changes
Jul 10, 2020
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.
I found it highly confusing that even though the battery_level can be "dangerous" the commander does not always use the battery_dangerous message to report the current state.
In fact it made me think that there is a problem in the state machine because when battery level was clearly dangerous, commander was still only reporting the critical message.