-
Notifications
You must be signed in to change notification settings - Fork 41
Unhandled Commands Warnings in Home Assistant Core #75
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
Comments
Out of curiosity, what brands do you have on your network? I get maybe one warning per week, never more, so seeing them this frequently is unexpected but harmless. These messages are not used by zigpy or zigpy-znp so in the next release I will just silence these warnings. |
I was loosing 3 GU10 WS and one plug this week on IKEA GW that was working with the remotes but was off line in the GW and coming back nicely after re power them. |
Updated, as its been running all afternoon...
00:1e:5e:09:02:13:2a:28 = Computime/Salus SP600 Smart Socket - this one is the one thats generating a warning a minute, the others are much less frequent Broadly I have: |
@puddly Is ZNP doing energy scan then the network it up and running ?? But i like that and also moving from one bad channel then its possible (but that is not working with Xiaomi devices). Back to the spamming:
|
zigpy-znp definitely isn't but I'll have to set a sniffer up to check if Z-Stack itself is. I don't see any reason why it would need to. |
Thanks for the quick responses :) |
I've recently set up a new clean instance of Home Assistant with an Electrolama zzh! (TI CC2652R) plugged in to a RPi4 but am receiving a fairly solid stream of unhandled command warnings (~1 per minute):
Please advise if this is a problem with the configuration, or 'expected' behaviour?
The text was updated successfully, but these errors were encountered: