-
Notifications
You must be signed in to change notification settings - Fork 20
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
Unknown command received: CommandId.undefined_0x81: 129 #258
Comments
Can you enable ZHA debugging and post a log containing a few of these warnings? deCONZ was recently open sourced and I can't find any mention of a command 0x81: https://github.com/dresden-elektronik/deconz/blob/d9ddb8a8731301ac61e44434f031f7cf5651e3ca/src/common/zm_protocol.h#L106 |
Enabling ZHA debugging gives a gazillion of log messages. Anything specific I should look for? Or how I can dail down the logging? Should debug logging for zigpy-deconz be sufficient? |
You can ZIP and attach the whole log here |
I think this part of the log contains the relevant info
|
I'm not exactly sure how this command could have been triggered, but I'm suspecting one of my custom HA integrations was doing blocking IO which somehow corrupted some communication ending up in this command. I've upgraded some of my custom integrations and the issue has not shown up since. |
Very strange. The UART buffer cannot be corrupted by event loop stuttering: it's something handled entirely by the OS. Python just schedules writes and receives read data, it's not doing anything low-level. Also, the deCONZ UART protocol has checksums so (single) bit flips should not be possible. |
Also that it always the same payload is strange to me. If it would be corrupted data I would expect the payload to be random But I actually still get the messages, they're not entirely gone but is seems to be less frequent. Only 6 times in the las 8 hours |
I also see a lot of these messages:
|
Not a problem. There is a device on your network that is sending data but it cannot be interviewed. It's likely an Aqara sensor. |
I'm getting these messages a couple of times per hour. Haven't figured out which device is sending it or what message 0x81 is.
Payload always seems to be the same
The text was updated successfully, but these errors were encountered: