Open Sisylam opened 2 days ago
Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
zha documentation zha source (message by IssueLinks)
The problem
I currently trying to create an IAS ACE alarm panel using an ESP32-C6 and general binding and communication with home-assistant works as expected and it shows up as an alarm panel inside of the dashboard. I went into 'Manage Zigbee device' to directly send a cluster command which somehow works as I do receive the proper arm command. However, in the HA dashboard I get an error 'Failed to perform the action...' and in the logs I see a stacktrace posted below.
Could someone please be so kind and take a look at it or advice me how to resolve the error?
What version of Home Assistant Core has the issue?
core-2025.1.0.dev202411280234
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
ZigBee Home Automation
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
Diagnostics information
As written above, I currently trying to create an IAS ACE alarm panel using an ESP32-C6 and general binding and communication with home-assistant works as expected and it shows up as an alarm panel inside of the dashboard. I noticed that when I select the functionality in the dashboard to switch the state to arming then it will only send me for whichever arming state always a panic event only
Maybe that is how it is supposed to work, but it was irritating, but not the issue at hand. Then I went into 'Manage Zigbee device' to directly send a cluster command via which somehow works as I do receive the proper arm command on the ESP side:
However, in the HA dashboard I get an error 'Failed to perform the action...' and in the logs I see the posted stacktrace.
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response