Tuya Window Sensor ZG-102ZL does not update/work

Configuration Zigbee
1

Hey,
I bought Tuya windows sensors labeled as ZG-102ZL. I connected them with ZHA using a “sonoff zigbee stick”. It connects with no problem and as seen in the pictures the entities are also correct. The problem is, that those entities are not updated and the battery level always shows 0%. I tried to reconnect it several times and used a second sensor of the same model which results in the same problem.

Screenshot 2022-04-06 225234
Screenshot 2022-04-06 2252341014×643 73.1 KB

Device signature

{
  "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=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, 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)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0402",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0500"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    }
  },
  "manufacturer": "_TZE200_pay2byax",
  "model": "TS0601",
  "class": "zigpy.device.Device"
}
2

Hey Dominik, I experience the exact same problems. Did you come closer to a solution? I use the Conbee II stick with the according integration.
Changing the battery to one which surely works did not help.

3

Have not tried something else yet but it seems this device/ a similar one is not listed on the compatibility list of ZHA yet but is listed as compatible to deconz and zigbee2mqtt

4

I tried to add the device using deconz but I did not even manage to get a connection.

5

I opened a device support request in ZHA project: [Device Support Request] Tuya ZG-102ZL / _TZE200_pay2byax · Issue #1502 · zigpy/zha-device-handlers · GitHub

6

I´m using the Skyconnect dongle, with same results. The device is shown but no updates occur.
Any news on this?

7

Hello, I have exactly the same problem. the sensor is recognized in the zha with the skyconnect Stück but the status does not change and the battery is always at 0%. is there a simple solution now?

8

nothing? no solution? for TS0203

9

hello,
may I come back to this topic?
In my MQTT portal the device appears correctly with all values.
But in my HA this device appears as well, but illuminance and illuminance_interval are declared as inactive, although the illuminance_interval also appears under control elements.
Doing an analysis I believe that the device does not respond with a configuration so it is not setup correctly in HA!? Within the data all values appear, but I cannot use the illuminance values for automation.

Is there a way how I can activate those attributes, esp. the illuminance because this is the importance information from that device? Trying to create a configuration by hand and to send it via MQTT in HA (publishing a package) does not work although some details appear in developer tools → states.
(Im a working in a German environment.)
thx

10

That was caused by one of the Z2M 2.0 breaking changes:

image
image1368×443 85.3 KB

All you need to do is click on the disabled entity in HA, click the settings (cog) icon in the top right and enable it from the options. Don’t forget to press updated at the bottom when you’re done

image
image899×1105 45.7 KB

PS - remove your manual MQTT config. You don’t need it.

11

thx, but this is not the problem. The entity is listed in both, Zigbee2MQTT and HA. It is active in both. But in HA the illuminance attribute is inactive. Therefore I cannot use it for automation although the value is delivered.
According to my research this is caused by a missing configuration message from the device.It sends to battery, door and illuminance_interval, but not for interval.
I cannot find any means in HA to add a configuration for the attribute, nor to activate it. Also, trying to send a configuration message internally (by using publish package in the MQTT integration) does not work. Either the config data in the message is wrong or HA does not accept late configuration details. However, something is processed from this message although I do not understand what and why.

12

Maybe it was a configuration error somehow. I do not know why, but it works now.
thx