-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
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
ZHA - bellows.ezsp error AttributeError: No such command name: battery_percent_reported #101996
Comments
Hey there @dmulcahey, @Adminiuga, @puddly, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) zha documentation |
What Aqara devices do you have on your network? |
All of them :D |
There's some faulty quirk then. Are you using any custom quirks for the roller blind controllers? Otherwise, please check if the logs contain more information (above the exception). If not, enable debug logs through the integration page, wait a bit until the issue reproduces, then disable debug logs through the integrations page. That will prompt you to download them. |
Interesting. The only quirk file I have is for the roller blinds as they simply refused to operate correctly without it. I'll try and find the forum post I got it from. The .py is below but I can't find any "battery_percent_reported" in it...
|
Yeah, there are multiple issues with that quirk. Ah, mhmm. You have another device. What doesn't work without the custom quirk? |
Please also upload the device signature / device diagnostics without having the quirk applied. |
To be fair it was a few months ago at the start of the year I got these so I can't honestly say I've tried without. I've just compared mine with the one in zigpy and it contains mine plus an _3 so I should probably just remove altogether. QQ: do I just remove the .py from the quirks folder and restart the ZHA integration or does HA need a full restart to remove a quirk? |
Still having perf issues with hypervisor/VM so had to restart HA this morning anyway and can confirm the error is gone with no custom quirks file. For those with E1s it looks like the custom bits are now baked in to zigpy 👍. |
Its one more problem then you have only end device that need having one parent for working and you is only having the coordinator so you have one star network and not one redundant mesh network and then the coordinator is going off like all devices is loosing the network and is getting problems. Minimum is 3 routers for getting some mesh network functionality and redundancy. |
The problem
Logs below are reported very frequently. Not sure what is causing it but no automations call that command as far as I know.
What version of Home Assistant Core has the issue?
20232.10.2
What was the last working version of Home Assistant Core?
2023.9.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
ZHA
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: