core
core copied to clipboard
ZHA: tuya zigbee siren TS0601 _TZE200_t1blo2bj doesn't work anymore
The problem
I have two tuya zigbee sirens (TS0601 _TZE200_t1blo2bj) but they don't play sounds anymore. I use this sirens as a doorbell in an automation trigged by a zigbee switch.
In my automation first I configure the siren with
- melody = 2 (attribute 1126 = 0x0466, see yaml code below)
- volume = 2 (attribute 1140 = 0x0474, see yaml code below)
- duration = 7 (attribute 615 = 0x0267, see yaml code below)
and then I enable the sirens switch entity. This works fine till about 2-3 weeks ago but now it doens't work anymore.
The debug log is in the attachements. I triggered the automation at 2023-03-20 13:50
After that I try the manual way at 2023-03-20 13:56 (with enabled debug-log, see below)







What version of Home Assistant Core has the issue?
2023.3.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
Diagnostics information
Error-Debug with triggered automation: home-assistant_zha_2023-03-20T12-50-25.022Z.log
Error-Debug-Log for the manual way home-assistant_zha_2023-03-20T12-57-52.708Z.log
Example YAML snippet
action:
- service: zha.set_zigbee_cluster_attribute
data:
endpoint_id: 1
cluster_id: 6
attribute: 1126
value: "2"
ieee: a4:c1:38:e3:07:14:cb:bd
cluster_type: in
- service: zha.set_zigbee_cluster_attribute
data:
endpoint_id: 1
cluster_id: 6
attribute: 1140
ieee: a4:c1:38:e3:07:14:cb:bd
value: "2"
cluster_type: in
- service: zha.set_zigbee_cluster_attribute
data:
endpoint_id: 1
cluster_id: 6
attribute: 615
value: "7"
ieee: a4:c1:38:e3:07:14:cb:bd
cluster_type: in
- service: switch.turn_on
data: {}
target:
entity_id: switch.eg_sirene_switch
Anything in the logs that might be useful for us?
No response
Additional information
No response
Hey there @dmulcahey, @adminiuga, @puddly, 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!
Code owner commands
Code owners of zha can trigger bot actions by commenting:
@home-assistant closeCloses the issue.@home-assistant rename Awesome new titleRenames the issue.@home-assistant reopenReopen the issue.@home-assistant unassign zhaRemoves the current integration label and assignees on the issue, add the integration domain after the command.
(message by CodeOwnersMention)
zha documentation zha source (message by IssueLinks)
Same story here. Trigger does not work anymore. HA Version: 2023.3.6
Interestingly enough, If I send "1" to the on_off (0x0000) via Manage Zigbee Device, it becomes Bool.true and then goes back to Bool.false and the alarm actually works. If I trigger via the switch, the value stays "1" and doesn't convert to Bool.true nor goes back to Bool.false after the duration.
Found the issue:
Triggered via switch (as exposed) - uses "1" as attr.value. Doesn't work
2023-03-29 11:52:03.462 DEBUG (MainThread) [zigpy.zcl] [0x8971:1:0xef00] tuya_mcu_command: cluster_data=TuyaClusterData(endpoint_id=1, cluster_name='on_off', cluster_attr='on_off', attr_value=1, expect_reply=True, manufacturer=-1)
Manually triggered - uses <Bool.true: 1> -> works
2023-03-29 11:53:22.376 DEBUG (MainThread) [zigpy.zcl] [0x8971:1:0xef00] tuya_mcu_command: cluster_data=TuyaClusterData(endpoint_id=1, cluster_name='on_off', cluster_attr='on_off', attr_value=<Bool.true: 1>, expect_reply=False, manufacturer=-1)
Workaround works for me. After configure the siren (see above), I enable the "on_off" 0x0000 attribute in my automation
service: zha.set_zigbee_cluster_attribute data: endpoint_id: 1 cluster_id: 6 attribute: 0 value: "1" ieee: a4:c1:38:e3:07:14:cb:bd cluster_type: in
Can anyone help me with some basic instructions what value to set which clusters to get this alarm to sound please? I am using 2023.3.4 and can't get a squeak out of my device (using ZHA).
The issue should be fixed in the next HA version.
Can anyone confirm that the issue is already fixed? Can the issue be closed?
Can anyone confirm that the issue is already fixed? Can the issue be closed?
No. I am on 2023.4.1 and anything related to the sirene, from switching it on or off or change the volume or type of sirene sound still only works manually as described above.
Fix will only land in 2023.4.2
Fix will only land in 2023.4.2
Yep. Working with 2023.4.2