-
Notifications
You must be signed in to change notification settings - Fork 0
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
Serial Exception: read failed #8
Comments
Retry when the serial adapter unexpectedly does not return data. Currently there is no proper backoff mechanism in case the serial port would not return data multiple times.
@Phi2k I finally found some time to implement this. Let me know if it properly catches the issue. |
Thanks as well! This looks good. Both systems are now running since 4 days - so 8 days of testing in total without the error. |
Unfortunately not completely fixed. This one seems to be related and occurs more rarely (once per 2 weeks). Is it possible to catch this error as well? Thank you very much.
|
The error message is longer. The block
is repeated like 100 times. The whole error message is printed every second. |
Hi @Phi2k, I added a patch that should fix this issue. On an error, the software will retry 5 times before giving up entirely. |
About once per week I get the following exception causing the script to stop.
I suppose this is a system error (it did not happen on my first setup on a Raspberry Pi Zero. The current setup is Raspberry Pi 5, 2x Docker container and 2x serial hardware both containers reporting to two separate MQTT broker.
Is it possible to catch this error (e.g. like that: https://forums.raspberrypi.com/viewtopic.php?t=201976#p1256252) or at least cause the container to exit that it can restart properly? Current situation is that this error does not trigger a restart. My current workaround would be to schedule a restart every day.
Thank you very much
The text was updated successfully, but these errors were encountered: