-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Sporadic UnhandledPromiseRejection #21696
Comments
To debug this I need the herdsman debug logging of the crash. See this on how to enable the herdsman debug logging. Note that this is only logged to STDOUT and not to log files. |
Sorry for the late reply. 2024-03-08T11:53:23.768Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010 |
Do you have Note to self; add |
There are two instances of "permit_join" in configuration.yaml, all of which are now set to "false". Previously both had value "true". A small hint: I suspect that Silvercrest (Lidl) plugs are causing the crash. Because I believe that the error only occurs since I have used three of them. If the problem occurs again, I will remove it to verify my suspicion. |
After setting the permit_join option to false, the problem no longer occurred. So, the ticket can be closed.. |
Great, also pushed a fix! Changes will be available in the dev branch in a few hours from now. |
What happened?
The add-on sporadically crashes after receiving an UnhandledPromiseRejection. Unfortunately, the problem cannot be reproduced systematically, but it occurs again and again.
What did you expect to happen?
The add-on should work reliably.
A guide that helps me to provide further information to solve the problem.
How to reproduce it (minimal and precise)
Unfortunately, the problem cannot be reproduced systematically.
Zigbee2MQTT version
1.36.0
Adapter firmware version
0x26520700
Adapter
RaspBee2
Setup
Add-On on Home Assistant OS on Raspberry PI4
Debug log
UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "TIMEOUT".
The text was updated successfully, but these errors were encountered: