Hello everyone,
I bought a couple of Lidl Zigbee devices and connected them with ZHA via a Sonoff-Zigbee-Stick.
The pairing worked perfect, also controlling the smart plugs.
But the motion sensor and window sensor don’t update their entities. They always show “closed” or “no detection”, even though the red light on the sensors indicate that they are working.
Did someone has the same problem? I couldn’t find any help in the forum.
Thanks in advance!
Chris
Couldn’t help you, only can say that my motion sensor from SilverCrest/Lidl (TY0202
by _TZ1800_fcdjzz3s) is working in ZHA via a ConBee II stick.
Thanks for the answer. Does anyone else know something about that?
Do I really need to buy an addtitional ConBee-Stick in order to geht it running?
There are actually two versions of the motion detector.
The “older” one has a 90 degree motion detection, the “newer” version has a 120 degree motion detection.
The door/window sensor was just released.
I am using conbee2 and the newer version of the motion detector + door/window sensor are not working! Integration over ZHA failed, because the sensors don’t show up.
I think they have to be integrated first.
Hi NB,
thats’s very interesting! I’m using a zigbee-sonoff-dongle and indeed I have the new 120 degree motion sensors as well as the new door-window-sensor.
But the sensor do get registerd and configured by ZHA, they just don’t update ther entities.
Do you know when they will be integrated?
For others having the same problem: I figured out a solution. ZHA is not recognizing the new lidl sensors, but Zigbee2MQTT does!
Everything works fine now, although I’m not sure, if the battery values are correct, with the ZHA-integration they show quite different values (60% etc.), now they are all on 100%.
Many greetings!
This is exactly what I encounter. The sensors work for a minute, sometimes more, after connecting/reconfiguring but then eventually fall into oblivion. No matter how much I liked the Sonoff-Zigbee-Stick, I’ve reverted to using my older tuya hub for the motion sensors.
I can confirm this and unfortunately, the error still exist.
Actually with all motion detectors from lidl. I have several of them from different years 
I just bought Lidl Smart Motion Sensor from Lidl, paired it with Conbee II stick. I run latests version of HA with zha.
Pairing was piece of cake and motion detection has been working just fine for the past day.
> # Device info
> TY0202
> by _TZ1800_fcdjzz3s
> Connected via [Zigbee Coordinator](http://myassistant.local:8123/config/devices/device/656e0d6b71a81aa7c73ece001f973e47)
> Firmware: 0x00000043
> Zigbee info
> IEEE: b4:e3:f9:ff:fe:07:bc:0e
> Nwk: 0x99c9
> Device Type: EndDevice
> LQI: 159
> RSSI: -74
> Last Seen: 2023-01-29T14:51:51
> Power Source: Battery or Unknown
Everything works now fine, but one problem remains: I do not know how often the detection triggers.
Does someone know?
I had a Lidl Motion detector _TZ1800_fcdjzz3s running successfully using deconz integration. Recently I changed my home assistant configuration to ZHA. All elements were detected successfully except the _TZ1800_fcdjzz3s motion detector.
In deconz rest api:
{
“config”: {
“battery”: 100,
“duration”: 60,
“enrolled”: 1,
“on”: true,
“pending”: [],
“reachable”: true
},
“ep”: 1,
“etag”: “ef0b0ffc15dfd98944fd3bfe42270d69”,
“lastannounced”: “2022-12-02T12:42:43Z”,
“lastseen”: “2022-12-02T22:03Z”,
“manufacturername”: “_TZ1800_fcdjzz3s”,
“modelid”: “TY0202”,
“name”: “Presence 5”,
“state”: {
“lastupdated”: “2022-12-02T22:04:12.799”,
“lowbattery”: false,
“presence”: true,
“tampered”: false
},
“swversion”: “2019.12.12”,
“type”: “ZHAPresence”,
“uniqueid”: “ec:1b:bd:ff:fe:ab:8a:97-01-0500”
},
In ZHA the device is detected but the initialisation does not complete…
Untitled-3
107,90: Received a packet: ZigbeePacket(src=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x658C), src_ep=0, dst=AddrModeAddress(addr_mode=<AddrMode.Broadcast: 15>, address=<BroadcastAddress.RX_ON_WHEN_IDLE: 65533>), dst_ep=0, source_route=None, extended_timeout=False, tsn=None, profile_id=0, cluster_id=19, data=Serialized[b’\x81\x8ce\x97\x8a\xab\xfe\xff\xbd\x1b\xec\x80’], tx_options=<TransmitOptions.NONE: 0>, radius=0, non_member_radius=0, lqi=255, rssi=-48)
108,12: New device 0x658c (ec:1b:bd:ff:fe:ab:8a:97) joined the network
109,2: [0x658c] Scheduling initialization
110,74: Received frame on uninitialized device from ep 0 to ep 0, cluster 19: b’\x81\x8ce\x97\x8a\xab\xfe\xff\xbd\x1b\xec\x80’
111,2: [0x658c:zdo] ZDO request ZDOCmd.Device_annce: [0x658C, ec:1b:bd:ff:fe:ab:8a:97, 128]
111,48: [0x658c:zdo] ZDO request ZDOCmd.Device_annce: [0x658C, ec:1b:bd:ff:fe:ab:8a:97, 128]
113,2: [0x658c] Requesting ‘Node Descriptor’
115,2: [0x658c] Extending timeout for 0x40 request
116,90: Received a packet: ZigbeePacket(src=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x658C), src_ep=0, dst=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x0000), dst_ep=0, source_route=None, extended_timeout=False, tsn=None, profile_id=0, cluster_id=32770, data=Serialized[b’@\x00\x8ce\x02@\x80\x0b\x12RR\x00\x00,R\x00\x00’], tx_options=<TransmitOptions.NONE: 0>, radius=0, non_member_radius=0, lqi=255, rssi=-48)
117,74: Received frame on uninitialized device from ep 0 to ep 0, cluster 32770: b’@\x00\x8ce\x02@\x80\x0b\x12RR\x00\x00,R\x00\x00’
118,2: [0x658c] Got Node Descriptor: NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4619, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *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)
119,2: [0x658c] Discovering endpoints
121,2: [0x658c] Extending timeout for 0x42 request
139,2: [0x658c] Extending timeout for 0x44 request
147,2: [0x658c] Extending timeout for 0x46 request
164,2: [0x658c] Discovering endpoints
166,2: [0x658c] Extending timeout for 0x48 request
170,2: [0x658c] Extending timeout for 0x4a request
180,2: [0x658c] Extending timeout for 0x4c request
182,2: [0x658c] Discovering endpoints
184,2: [0x658c] Extending timeout for 0x4e request
217,2: [0x658c] Extending timeout for 0x56 request
231,2: [0x658c] Extending timeout for 0x58 request
I tried to connect the Lidl motion sensor in ZHA but it does not work.
Other Lidl devices work fine in ZHA.
Is there a way to get this working in ZHA?
Or can ZHA be upgraded to include this motion sensor?
After some time I started experiencing the same issue.
The door / windows sensor does not provide the status (Open, Close, Tempered) change, or shows itself as “disconnected”. It has been shown as “connected”. I have deleted one of those malfunctioning sensors and tried to pair it again - no success.
It starts the negotiation process, but then reports “Sensor xxx is leaving the network”.
Is there any possibility to “reset” the sensor to the initial / factory state?
[UPDATE]
following on this topic further, I have found one thing. in order to get this device back to the network following steps are needed: