Describe the bug
A clear and concise description of what the bug is.
Short Summary of the expected behavior:
When the Krake payload is bad format the Krake should do nothing.
Short Summary of the buggy behavior:
On the receipt of bad format the LCD contend did not change but the speaker repeated the previous alarm message.
To Reproduce
Steps to reproduce the behavior:
- Publish to the krake a valid alarm and confirm the LCD displays alarm and you hear the alarm from speaker once.
- Begin publishing to the Krake a payload with "bad format" For example the measurements of the VentMon
- The Krake should start repeating alarm on the speaker.
Test Equipment
Used the PMD_PROCESSING_MQTT to send valid alarm message.
Used VentMon with code ???? to publish measurments to the Krake_ALM
Additional context
Add any other context about the problem here.
Here is the Krake serial monitor during receipt of bad payload (published by a VentMon)
Command: {
bad format of command!
PubInv GPAD: enter command in form CDa (C is a char, D is a digit)
currentlyMuted : 1
interpret Done
Describe the bug
A clear and concise description of what the bug is.
Short Summary of the expected behavior:
When the Krake payload is bad format the Krake should do nothing.
Short Summary of the buggy behavior:
On the receipt of bad format the LCD contend did not change but the speaker repeated the previous alarm message.
To Reproduce
Steps to reproduce the behavior:
Test Equipment
Used the PMD_PROCESSING_MQTT to send valid alarm message.
Used VentMon with code ???? to publish measurments to the Krake_ALM
Additional context
Add any other context about the problem here.
Here is the Krake serial monitor during receipt of bad payload (published by a VentMon)