-
Notifications
You must be signed in to change notification settings - Fork 96
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
No handler for message 5 #126
Comments
Using tag latest from DockerHub. |
Might be coincidence with arm/disarm as i receive also this message 4-5 mins after arm/disarm. |
dupe #89 |
Hi @yozik04 i still experience this with version 2.2.0 |
I've just set PAI using ESP32 Serial -> IP method, everything seems to work but I'm getting these error messages every few seconds. Mine look pretty much the same as OPs:
I have the ESP32 serial connection piggy-backing off the serial output on my Olarm Pro (https://olarm.com/products/olarm-pro-4g) and I wonder if that's causing this potentially. I don't want to lose the Olarm as it is useful and I'm already paying for the subscription through my security company. I'm currently using PAI through the HA Addon on version 3.4.0 with a MG5050 (only the one serial connection which is why I'm using the one on the Olarm). |
@drzoidberg33 it is fine, relax 😎 |
Thanks, it's working great btw, but I've only had it up for 30 minutes so far 👍 |
I have added IO_TIMEOUT setting. Please try to play with it. Default is 0.5 seconds. |
I receive this sometimes when doing some arming / disarming via Home Assistant.
I have not seen that many errors when running the docker on my Windows PC, but i see this now more frequent when running on the Docker NAS.
Is the async handler robust or is something wrong in my setup?
The text was updated successfully, but these errors were encountered: