No entities in zigbee tuya siren with ZHA

CharlieBailly · April 9, 2021, 3:30pm

First, thank you @familieeck for the details.
Then, for your problem, maybe you could remove your siren from ZHA, then re-pair it and show us the logs (there is a show logs button while pairing a device).
I also use a tasmotized sonoff zigbee bridge so the problem is not from here.

meremortal · April 10, 2021, 1:15am

William Tell Overture ( Gioacchino Rossini)

penpal1278 · April 10, 2021, 1:23am

I see, good to hear that the Sonoff Bridge is probably not the root cause of my issues. I’ve removed the siren from ZHA, reset, and re-paired it to my ZHA. Here is the log output:

[0x0000:zdo] ZDO request ZDOCmd.Mgmt_Permit_Joining_req: [60, <Bool.false: 0>]
Device 0xf817 (<siren ieee>) joined the network
[0xf817] Requesting 'Node Descriptor'
Tries remaining: 2
[0xf817] Extending timeout for 0x71 request
Device 0xf817 (<siren ieee>) joined the network
Skip initialization for existing device <siren ieee>
[0xf817:zdo] ZDO request ZDOCmd.Device_annce: [0xF817, <siren ieee>, 128]
[0xf817] Node Descriptor: NodeDescriptor(byte1=2, byte2=64, mac_capability_flags=128, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=0, *allocate_address=True, *complex_descriptor_available=False, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False, *is_valid=True, *logical_type=<LogicalType.EndDevice: 2>, *user_descriptor_available=False)
[0xf817] Discovering endpoints
Tries remaining: 3
[0xf817] Extending timeout for 0x73 request
[0xf817] Discovered endpoints: [1]
[0xf817:1] Discovering endpoint information
Tries remaining: 3
[0xf817] Extending timeout for 0x75 request
[0xf817:1] Discovered endpoint information: SizePrefixedSimpleDescriptor(endpoint=1, profile=260, device_type=81, device_version=1, input_clusters=[0, 4, 5, 61184], output_clusters=[25, 10])
Unknown cluster 61184
[0xf817] Extending timeout for 0x77 request
[0xf817:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=119 command_id=Command.Read_Attributes_rsp>
[0xf817:1] Manufacturer: _TZE200_d0yu2xgi
[0xf817:1] Model: TS0601
Checking quirks for _TZE200_d0yu2xgi TS0601 (<siren ieee>)
Considering <class 'zhaquirks.tuya.siren.TuyaSiren2'>
Found custom device replacement for <siren ieee>: <class 'zhaquirks.tuya.siren.TuyaSiren2'>
device - 0xF817:<siren ieee> entering async_device_initialized - is_new_join: True
device - 0xF817:<siren ieee> has joined the ZHA zigbee network
[0xF817](TS0601): started configuration
[0xF817:ZDO](TS0601): 'async_configure' stage succeeded
[0xF817:1:0x0006]: bound 'on_off' cluster: Status.SUCCESS
[0xF817:1:0x0006]: reporting 'on_off' attr on 'on_off' cluster: 0/900/1: Result: '[ConfigureReportingResponseRecord(status=0)]'
[0xF817:1:0x0006]: finished channel configuration
[0xF817:1:0x0402]: bound 'temperature' cluster: Status.SUCCESS
[0xF817:1:0x0402]: reporting 'measured_value' attr on 'temperature' cluster: 30/900/50: Result: '[ConfigureReportingResponseRecord(status=0)]'
[0xF817:1:0x0402]: finished channel configuration
[0xf817] Extending timeout for 0x79 request
[0xF817:1:0x0405]: bound 'humidity' cluster: Status.SUCCESS
[0xF817:1:0x0405]: reporting 'measured_value' attr on 'humidity' cluster: 30/900/50: Result: '[ConfigureReportingResponseRecord(status=0)]'
[0xF817:1:0x0405]: finished channel configuration
[0xf817] Extending timeout for 0x7b request
[0xf817:zdo] ZDO request ZDOCmd.Node_Desc_req: [0x0000]
[0xf817:zdo] Unsupported ZDO request:ZDOCmd.Node_Desc_req
[0xF817:1:0x0000]: bound 'basic' cluster: Status.SUCCESS
[0xF817:1:0x0000]: finished channel configuration
[0xF817:1:0x0019]: bound 'ota' cluster: Status.SUCCESS
[0xF817:1:0x0019]: finished channel configuration
[0xF817:1:0x0006]: 'async_configure' stage succeeded
[0xF817:1:0x0402]: 'async_configure' stage succeeded
[0xF817:1:0x0000]: 'async_configure' stage succeeded
[0xF817:1:0x0405]: 'async_configure' stage succeeded
[0xF817:1:0x0019]: 'async_configure' stage succeeded
[0xF817](TS0601): completed configuration
[0xF817](TS0601): stored in registry: ZhaDeviceEntry(name='_TZE200_d0yu2xgi TS0601', ieee='<siren ieee>', last_seen=1618017548.6267056)
[0xf817] Extending timeout for 0x7d request
[0xf817:1:0x0003] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=125 command_id=Command.Default_Response>
[0xF817:1:0x0003]: executed 'trigger_effect' command with args: '(2, 0)' kwargs: '{}' result: [64, <Status.UNSUPPORTED_CLUSTER: 195>]
[0xF817](TS0601): started initialization
[0xF817:ZDO](TS0601): 'async_initialize' stage succeeded
[0xF817:1:0x0006]: initializing channel: from_cache: False
[0xF817:1:0x0006]: finished channel configuration
[0xF817:1:0x0402]: initializing channel: from_cache: False
[0xF817:1:0x0402]: finished channel configuration
[0xF817:1:0x0000]: initializing channel: from_cache: False
[0xF817:1:0x0000]: finished channel configuration
[0xF817:1:0x0405]: initializing channel: from_cache: False
[0xF817:1:0x0405]: finished channel configuration
[0xF817:1:0x0019]: initializing channel: from_cache: False
[0xF817:1:0x0019]: finished channel configuration
[0xF817:1:0x0006]: 'async_initialize' stage succeeded
[0xF817:1:0x0402]: 'async_initialize' stage succeeded
[0xF817:1:0x0000]: 'async_initialize' stage succeeded
[0xF817:1:0x0405]: 'async_initialize' stage succeeded
[0xF817:1:0x0019]: 'async_initialize' stage succeeded
[0xF817](TS0601): power source: Battery or Unknown
[0xF817](TS0601): completed initialization
[0xF817:1:0x0006]: attempting to update onoff state - from cache: True
Ignoring message (b'0011000700') on cluster 10: unknown endpoint or cluster id: 'No cluster ID 0x000a on (<siren ieee>, 1)'
Ignoring message (b'0011000700') on cluster 10: unknown endpoint or cluster id: 'No cluster ID 0x000a on (<siren ieee>, 1)'
Ignoring message (b'0011000700') on cluster 10: unknown endpoint or cluster id: 'No cluster ID 0x000a on (<siren ieee>, 1)'
Ignoring message (b'0011000700') on cluster 10: unknown endpoint or cluster id: 'No cluster ID 0x000a on (<siren ieee>, 1)'
Ignoring message (b'0011000700') on cluster 10: unknown endpoint or cluster id: 'No cluster ID 0x000a on (<siren ieee>, 1)'
Ignoring message (b'0011000700') on cluster 10: unknown endpoint or cluster id: 'No cluster ID 0x000a on (<siren ieee>, 1)'
Ignoring message (b'0011000700') on cluster 10: unknown endpoint or cluster id: 'No cluster ID 0x000a on (<siren ieee>, 1)'
[0xf817:1:0xef00] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=True> manufacturer=None tsn=18 command_id=36>
Failed to parse message (b'191224001b') on cluster 61184, because Data is too short to contain 1 bytes
[0xf817:1:0xef00] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=19 command_id=17>
[0xf817:1:0xef00] Unknown cluster-specific command 17
[0xf817:1:0xef00] ZCL request 0x0011: b'\x00\x1cD'
[0xf817:1:0xef00] No handler for cluster command 17

erikkt · April 20, 2021, 3:51pm

I have the exact same problem as you do. Did you find a solution?

penpal1278 · April 21, 2021, 1:01am

@erikkt nope, not yet unfortunately

AngryIain · April 29, 2021, 7:30pm

@penpal1278 Is your device signature not different from the one @CharlieBailly has, device_type and clusters vary, so needs a different quirk?

penpal1278 · April 30, 2021, 12:49pm

@AngryIain Thanks for the pointer! I didn’t catch it since the manufacturer and model info matched… I’ll follow what @CharlieBailly did and see if I can write up a new quirk for this particular device.

AngryIain · April 30, 2021, 2:51pm

Just for full disclosure, I have no experience in this area and have the same problem as you, and this is just my latest observation…
I have no idea how to resolve it properly but I am willing to research next week if I can. Hopefully we’ll get some help on this thread…

CalcU · May 1, 2021, 10:26am

Hi, just a question, i have the same problem / siren.
the same model / manufacturer (d0yu2xgi)

I think quirks are not bein used… can you guide me about how to be sure my HA is using quirks? i installed (i think everything) but i can’t see tuyasiren2 anywhere, and in siren.py there is this tuyasiren2.

I think quirks aren’t enabled in my system (debian + docker) + ha

AngryIain · May 1, 2021, 9:46pm

@CalcU Are you using ZHA and do you not see this in Config → Device?

dryros · May 1, 2021, 10:03pm

I also have the same problem the device looks exactly like this but it does not work correctly:

CalcU · May 1, 2021, 10:13pm

Yes:


{
  "node_descriptor": "NodeDescriptor(byte1=2, byte2=64, mac_capability_flags=128, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=0, *allocate_address=True, *complex_descriptor_available=False, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False, *is_valid=True, *logical_type=<LogicalType.EndDevice: 2>, *user_descriptor_available=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0403",
      "in_clusters": [
        "0x0000",
        "0x0003",
        "0x0006",
        "0x0402",
        "0x0405",
        "0xef00"
      ],
      "out_clusters": [
        "0x0003",
        "0x0019"
      ]
    }
  },
  "manufacturer": "_TZE200_d0yu2xgi",
  "model": "TS0601",
  "class": "zhaquirks.tuya.siren.TuyaSiren2"

AngryIain · May 1, 2021, 10:46pm

I believe the manufacturer has updated this device so a new quirk is required. I don’t know how to do this and maintain backwards compatibility with previous versions of the device so we need to seek advice from the community here, IMHO.

Zannabis · May 7, 2021, 11:36am

Same issue here. But a newbee on Zigbee. Available if I can give help and support on that. Thanks

dryros · May 8, 2021, 8:25am

It seems that the issue is already forgotten, those who managed to solve it, it seems that they have closed the issue and are not giving more answers or support to solve the new problems, they have to buy new devices that are easier to integrate because no one give solutions

Enjoy-Combi · May 18, 2021, 9:25pm

Same issue, Neo zigbee alarm detected but doesn’t get the data and no control on the functions.

DM-AU · May 19, 2021, 12:17am

Also have the same problem here. Appreciate any help.

xion2000 · May 20, 2021, 1:36pm

I’m struggling too, siren shows up but unable to do anything with it

Soul · May 28, 2021, 4:33pm

What zigbee hub are you connecting the siren to?

I’m trying to pair a Neo/Tuya siren to my zzh stick with zigbee2mqtt and nothing happens.

DM-AU · June 1, 2021, 3:32am

I have a sonoff zb bridge running tasmota. This is what I see:

Currently its off, but these show/do nothing.