Lidl doorbell

Rifrouf · August 31, 2021, 3:00pm

I have activated ZHA logs and see what is happening when I press the doorbell button.
The procedure is:

Press the doorbell button on the device every 5 seconds for one minute (there is only one button on this device).

I expected the entity “binary_sensor.sonnette_ias_zone” change his state during the procedure but it is stuck to ‘off’.

I have searched entries in the log, and there is only 8 reference to the device IEEE, 00:0d:6f:00:16:1f:67:b7. These entries seems to belong to only one communication.

Here is the log (I cuttedit before and after to have only the moment where the IEEE is referenced). I cannot analyse what is happening but it looks like the device only says it is on the network and I cannot see any command/status send.

Is the anyone who can tell be if there is a clue in the log ? Or if I shall see anything with this procedure ?

2021-08-31 15:24:12 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame 69 (incomingMessageHandler) received: b'0004010005010100010000156cb73379ffff0909640000800000000002'
2021-08-31 15:24:12 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_UNICAST: 0>, EmberApsFrame(profileId=260, clusterId=1280, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=0, sequence=21), 108, -73, 0x7933, 255, 255, b'\td\x00\x00\x80\x00\x00\x00\x00']
2021-08-31 15:24:12 DEBUG (MainThread) [zigpy.zcl] [0x7933:1:0x0500] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=100 command_id=0>
2021-08-31 15:24:12 DEBUG (MainThread) [zigpy.zcl] [0x7933:1:0x0500] ZCL request 0x0000: [<ZoneStatus.32768: 32768>, <bitmap8.0: 0>, 0, 0]
2021-08-31 15:24:12 DEBUG (MainThread) [zigpy.zcl] [0x7933:1:0x0500] No handler for cluster command 0
2021-08-31 15:24:12 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x7933:1:0x0500]: Updated alarm state: ZoneStatus.0
2021-08-31 15:24:16 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame 35 (childJoinHandler) received: b'01013379b7671f16006f0d0004'
2021-08-31 15:24:16 DEBUG (MainThread) [bellows.zigbee.application] Received childJoinHandler frame with [1, <Bool.true: 1>, 0x7933, 00:0d:6f:00:16:1f:67:b7, <EmberNodeType.SLEEPY_END_DEVICE: 4>]
2021-08-31 15:24:16 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame 36 (trustCenterJoinHandler) received: b'3379b7671f16006f0d0000030000'
2021-08-31 15:24:16 DEBUG (MainThread) [bellows.zigbee.application] Received trustCenterJoinHandler frame with [0x7933, 00:0d:6f:00:16:1f:67:b7, <EmberDeviceUpdate.STANDARD_SECURITY_SECURED_REJOIN: 0>, <EmberJoinDecision.NO_ACTION: 3>, 0x0000]
2021-08-31 15:24:16 INFO (MainThread) [zigpy.application] Device 0x7933 (00:0d:6f:00:16:1f:67:b7) joined the network
2021-08-31 15:24:16 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame 69 (incomingMessageHandler) received: b'000401000501010001000016a4c53379ffff0909650000800000000002'
2021-08-31 15:24:16 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_UNICAST: 0>, EmberApsFrame(profileId=260, clusterId=1280, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=0, sequence=22), 164, -59, 0x7933, 255, 255, b'\te\x00\x00\x80\x00\x00\x00\x00']
2021-08-31 15:24:16 DEBUG (MainThread) [zigpy.zcl] [0x7933:1:0x0500] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=101 command_id=0>
2021-08-31 15:24:16 DEBUG (MainThread) [zigpy.zcl] [0x7933:1:0x0500] ZCL request 0x0000: [<ZoneStatus.32768: 32768>, <bitmap8.0: 0>, 0, 0]
2021-08-31 15:24:16 DEBUG (MainThread) [zigpy.zcl] [0x7933:1:0x0500] No handler for cluster command 0
2021-08-31 15:24:16 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x7933:1:0x0500]: Updated alarm state: ZoneStatus.0
2021-08-31 15:24:16 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame 98 (incomingSenderEui64Handler) received: b'b7671f16006f0d00'
2021-08-31 15:24:16 DEBUG (MainThread) [bellows.zigbee.application] Received incomingSenderEui64Handler frame with [00:0d:6f:00:16:1f:67:b7]
2021-08-31 15:24:16 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame 69 (incomingMessageHandler) received: b'040000000000000004000017a4c53379ffff0bd46f3930feff504b80000002'
2021-08-31 15:24:16 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_BROADCAST: 4>, EmberApsFrame(profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_SOURCE_EUI64: 1024>, groupId=0, sequence=23), 164, -59, 0x7933, 255, 255, b'\xd4o90\xfe\xffPK\x80\x00\x00']
2021-08-31 15:24:16 DEBUG (MainThread) [zigpy.zdo] [0x7933:zdo] ZDO request ZDOCmd.NWK_addr_req: [80:4b:50:ff:fe:30:39:6f, 0, 0]
2021-08-31 15:24:16 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame 98 (incomingSenderEui64Handler) received: b'b7671f16006f0d00'
2021-08-31 15:24:16 DEBUG (MainThread) [bellows.zigbee.application] Received incomingSenderEui64Handler frame with [00:0d:6f:00:16:1f:67:b7]
2021-08-31 15:24:16 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame 69 (incomingMessageHandler) received: b'040000130000000004000018a4c53379ffff0cd53379b7671f16006f0d008002'
2021-08-31 15:24:16 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_BROADCAST: 4>, EmberApsFrame(profileId=0, clusterId=19, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_SOURCE_EUI64: 1024>, groupId=0, sequence=24), 164, -59, 0x7933, 255, 255, b'\xd53y\xb7g\x1f\x16\x00o\r\x00\x80']
2021-08-31 15:24:16 INFO (MainThread) [bellows.zigbee.application] ZDO Device announce: 0x7933, 00:0d:6f:00:16:1f:67:b7
2021-08-31 15:24:16 INFO (MainThread) [zigpy.application] Device 0x7933 (00:0d:6f:00:16:1f:67:b7) joined the network
2021-08-31 15:24:16 DEBUG (MainThread) [zigpy.zdo] [0x7933:zdo] ZDO request ZDOCmd.Device_annce: [0x7933, 00:0d:6f:00:16:1f:67:b7, 128]
2021-08-31 15:24:16 DEBUG (MainThread) [bellows.ezsp.protocol] Send command sendUnicast: (<EmberOutgoingMessageType.OUTGOING_DIRECT: 0>, 0x7933, EmberApsFrame(profileId=0, clusterId=32768, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY|APS_OPTION_RETRY: 320>, groupId=0, sequence=212), 237, b'\xd4\x00o90\xfe\xffPK\x80\x00\x00\x00\x00')
2021-08-31 15:24:17 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame 52 (sendUnicast) received: b'0097'
2021-08-31 15:24:17 DEBUG (MainThread) [bellows.ezsp.protocol] Send command readCounters: ()
2021-08-31 15:24:17 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame 241 (readCounters) received: b'af017400880030000100000002000000440017000000000000000100010000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
2021-08-31 15:24:17 DEBUG (MainThread) [bellows.zigbee.application] EZSP Counters: COUNTER_MAC_RX_BROADCAST: 431,COUNTER_MAC_TX_BROADCAST: 116,COUNTER_MAC_RX_UNICAST: 136,COUNTER_MAC_TX_UNICAST_SUCCESS: 48,COUNTER_MAC_TX_UNICAST_RETRY: 1,COUNTER_MAC_TX_UNICAST_FAILED: 0,COUNTER_APS_DATA_RX_BROADCAST: 2,COUNTER_APS_DATA_TX_BROADCAST: 0,COUNTER_APS_DATA_RX_UNICAST: 68,COUNTER_APS_DATA_TX_UNICAST_SUCCESS: 23,COUNTER_APS_DATA_TX_UNICAST_RETRY: 0,COUNTER_APS_DATA_TX_UNICAST_FAILED: 0,COUNTER_ROUTE_DISCOVERY_INITIATED: 0,COUNTER_NEIGHBOR_ADDED: 1,COUNTER_NEIGHBOR_REMOVED: 1,COUNTER_NEIGHBOR_STALE: 0,COUNTER_JOIN_INDICATION: 1,COUNTER_CHILD_REMOVED: 0,COUNTER_ASH_OVERFLOW_ERROR: 0,COUNTER_ASH_FRAMING_ERROR: 0,COUNTER_ASH_OVERRUN_ERROR: 0,COUNTER_NWK_FRAME_COUNTER_FAILURE: 0,COUNTER_APS_FRAME_COUNTER_FAILURE: 0,COUNTER_UTILITY: 0,COUNTER_APS_LINK_KEY_NOT_AUTHORIZED: 0,COUNTER_NWK_DECRYPTION_FAILURE: 0,COUNTER_APS_DECRYPTION_FAILURE: 0,COUNTER_ALLOCATE_PACKET_BUFFER_FAILURE: 0,COUNTER_RELAYED_UNICAST: 0,COUNTER_PHY_TO_MAC_QUEUE_LIMIT_REACHED: 0,COUNTER_PACKET_VALIDATE_LIBRARY_DROPPED_COUNT: 0,COUNTER_TYPE_NWK_RETRY_OVERFLOW: 0,COUNTER_PHY_CCA_FAIL_COUNT: 0,COUNTER_BROADCAST_TABLE_FULL: 0,COUNTER_PTA_LO_PRI_REQUESTED: 0,COUNTER_PTA_HI_PRI_REQUESTED: 0,COUNTER_PTA_LO_PRI_DENIED: 0,COUNTER_PTA_HI_PRI_DENIED: 0,COUNTER_PTA_LO_PRI_TX_ABORTED: 0,COUNTER_PTA_HI_PRI_TX_ABORTED: 0,COUNTER_ADDRESS_CONFLICT_SENT: 0
2021-08-31 15:24:17 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame 63 (messageSentHandler) received: b'06fdff0000000000000004000017ff0000'
2021-08-31 15:24:17 DEBUG (MainThread) [bellows.zigbee.application] Received messageSentHandler frame with [<EmberOutgoingMessageType.OUTGOING_BROADCAST: 6>, 65533, EmberApsFrame(profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_SOURCE_EUI64: 1024>, groupId=0, sequence=23), 255, <EmberStatus.SUCCESS: 0>, b'']
2021-08-31 15:24:17 DEBUG (MainThread) [bellows.zigbee.application] Unexpected message send notification tag: 255
2021-08-31 15:24:17 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame 63 (messageSentHandler) received: b'06fdff0000130000000004000018ff0000'
2021-08-31 15:24:17 DEBUG (MainThread) [bellows.zigbee.application] Received messageSentHandler frame with [<EmberOutgoingMessageType.OUTGOING_BROADCAST: 6>, 65533, EmberApsFrame(profileId=0, clusterId=19, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_SOURCE_EUI64: 1024>, groupId=0, sequence=24), 255, <EmberStatus.SUCCESS: 0>, b'']
2021-08-31 15:24:17 DEBUG (MainThread) [bellows.zigbee.application] Unexpected message send notification tag: 255
2021-08-31 15:24:17 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame 63 (messageSentHandler) received: b'0033790000008000004001000097ed0000'
2021-08-31 15:24:17 DEBUG (MainThread) [bellows.zigbee.application] Received messageSentHandler frame with [<EmberOutgoingMessageType.OUTGOING_DIRECT: 0>, 31027, EmberApsFrame(profileId=0, clusterId=32768, sourceEndpoint=0, destinationEndpoint=0, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY|APS_OPTION_RETRY: 320>, groupId=0, sequence=151), 237, <EmberStatus.SUCCESS: 0>, b'']
2021-08-31 15:24:19 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame 69 (incomingMessageHandler) received: b'000401000501014001000019a4c53379ffff0909660000000000000002'
2021-08-31 15:24:19 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_UNICAST: 0>, EmberApsFrame(profileId=260, clusterId=1280, sourceEndpoint=1, destinationEndpoint=1, options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY|APS_OPTION_RETRY: 320>, groupId=0, sequence=25), 164, -59, 0x7933, 255, 255, b'\tf\x00\x00\x00\x00\x00\x00\x00']
2021-08-31 15:24:19 DEBUG (MainThread) [zigpy.zcl] [0x7933:1:0x0500] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=102 command_id=0>
2021-08-31 15:24:19 DEBUG (MainThread) [zigpy.zcl] [0x7933:1:0x0500] ZCL request 0x0000: [<ZoneStatus.0: 0>, <bitmap8.0: 0>, 0, 0]
2021-08-31 15:24:19 DEBUG (MainThread) [zigpy.zcl] [0x7933:1:0x0500] No handler for cluster command 0
2021-08-31 15:24:19 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x7933:1:0x0500]: Updated alarm state: ZoneStatus.0

adamba · October 28, 2021, 5:40pm

I can confirm that it works fine! I set it up with Zigbee2MQTT and I used the following automation. Of course you need to replace the xxxxx by the ID of your doorbell.

  - platform: state
    entity_id: sensor.0x842xxxxxxxxxxc0_action
    to: pressed

Joe34 · December 18, 2021, 9:47am

Is there a solution for zha? Thanks.

Mysteriosis · January 5, 2022, 12:15pm

It is normal that ias_zone stays on closed, this is the state of the device’s back cap.
Somehow, home assistant mixes the ias_zone and the missing action entity.
So, open the back of the device, ias_zone changes to open, then put it back to make it closed again.
Your doorbell will now work only once, until you open and close the back of the device again…

An entity is missing on this product.

Smartuser · February 14, 2022, 9:16pm

It is right what you say that’s what I discovered as well when I try to make it work …
But there is anything that could do to make it work? Besides Mqtt…?

Hedda · February 16, 2022, 1:40pm

ZHA Device Handlers “quirks” is needed when device don’t follow Zigbee Cluster Library specifications:

https://www.home-assistant.io/integrations/zha#zha-exception-and-deviation-handling

https://www.home-assistant.io/integrations/zha#reporting-issues

https://github.com/zigpy/zha-device-handlers/issues/1168

https://github.com/zigpy/zha-device-handlers/issues/759

https://github.com/zigpy/zha-device-handlers

https://github.com/zigpy/zha-device-handlers/issues

Zigbee2MQTT equivalent to zha-device-handlers (zha-quirks) is called zigbee-herdsman-converters:

https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html

https://github.com/Koenkk/zigbee-herdsman-converters

These parse/translate/convert non-standard messages to ZCL R6 or R7 (ZCL6/ZCL7) specifications:

https://zigbeealliance.org/wp-content/uploads/2019/12/07-5123-06-zigbee-cluster-library-specification.pdf

jakob.tewes · August 27, 2022, 10:42am

Also interested in a zha based solution. Did you get it to work?

jakob.tewes · August 27, 2022, 4:32pm

Works with a raw zha_event trigger:

  - alias: garage doorbell
    initial_state: 'on'
    trigger:
      - platform: event
        event_type: zha_event
        event_data:
          device_ieee: 84:2e:14:ff:fe:f8:1b:a8
          unique_id: 84:2e:14:ff:fe:f8:1b:a8:1:0x0500
          device_id: 9d21b0fcb47dd999f7f9a1df85b7662e
          endpoint_id: 1
          cluster_id: 1280
          command: single
          args: []

mararn1618 · September 24, 2022, 8:37am

Also integrated the doorbell with zha, but I always get 3 zha_events for one button press, with approx 3-4 secs delay between them. Did you experience the same? Any fix or workaround?

olwin · October 2, 2022, 3:00pm

Same here, only I get either 2 or 3 identical (except for time stamp and context ID) zha_events with 2 to 4 seconds delays, basically rendering the button useless :[

Hedda · October 3, 2022, 2:48pm

Again, for ZHA suggest start by submitting a new device support request with device signature and debug logs to ZHA Device Handlers → https://github.com/zigpy/zha-device-handlers/issues

ZHA will need a quirk/handler for zha-quirks if devices do not fully follow standard Zigbee specifcations, see → https://www.home-assistant.io/integrations/zha#zha-exception-and-deviation-handling

mrrobot1453 · February 6, 2023, 9:18pm

Had the same issue and I found the following page: https://smarthomepursuits.com/add-thirdreality-zigbee-button-to-home-assistant/.
I’ve made an automation to perform some actions. It has one downside. When pushing the button 2 events are fired, so it will trigger the automation twice. But if you’re fine with that, this is a possible solution.

olwin · August 10, 2023, 5:17am

Thanks for suggesting to write a quirk for this thing. But either the documentation is too stupid or I am. Probably the latter.

Still, it just occurred to me how to handle the multiple event firing. Epic facepalm moment, actually.

Here the recipe:

Write a (single mode) automation, triggered by

  - platform: event
    event_type: zha_event
    event_data:
      command: single
      device_id: <insertDeviceIdHere>

Add the list of actions you want performed, followed by a 10 seconds delay.
The delay will turn the multiple firings into harmless log messages.

Voila. Problem solved.

Granted, it’s not the nicest conceivable solution but it works like a charm.