-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MQTT communication should be robust, GPAD_API FIRMWARE_VERSION "0.12, #66
Comments
Perhaps the formatting of the MQTT failure reported on the serial could be cleaned up for more human friendly review. Should the LCD Display warn the user of MQTT connection failure? |
Note regarding this issue. To really test MQTT communication interruption we must have a Broker which we can control so as to make unavailable and available during our testing. Such a broker is MOSQUITO. It can be installed on PCs and Linux machines like RaspberryPi and I assume MACs. |
Describe the bug
A clear and concise description of what the bug is.
Short Summary of the expected behavior: MQTT communication should be robust. It should recover if interrupted for example.
Short Summary of the buggy behavior: It looks as if from 9 AM till nearly midnight 23:14:56 the MQTT connection was abonrmal
Serial Monitor Screen Shot
Send from PMD Processing the A2 command
To Reproduce
Steps to reproduce the behavior:
Use the Processing sketch
Load the Krake prototype with firmware FIRMWARE_VERSION "0.12 "
Let run and watch on serial monitor and hope
See error
Expected behavior
A clear and concise description of what you expected to happen.
If the MQTT connection is reported lost, reconnection should be reported too.
Screenshots
If applicable, add screenshots to help explain your problem.
Hardware description
Model: Homework2 Assembly from JLCPCB with LCD and DFPlayer
Serial Number: 20240421_USA1
Other:
The text was updated successfully, but these errors were encountered: