Another Problematic Tuya Device On C8

🛎️ Get Help Devices
1

I have these downlights which worked with C5 using the Generic RGBW driver but no with the C8:

On Amazon: GIDERWEL-Recessed-Downlight-Ambiance-Dimmable

Here's the info for the device:

  • endpointId: 01
  • inClusters: 0003,0004,0005,0006,1000,0008,0300,EF00,0000
  • manufacturer: _TZ3210_dxzgodw8
  • model: TS0505B
  • outClusters: 0019,000A
  • softwareBuild:

I tried out the driver written by @kkossev and tried modifying it to add my manufacturer number. I re-paired one of the bulbs with it close to my hubitat, but no dice. Here's a sample set of logs, including the F2 issue. This was generated using another driver, the one for Tuya dimmers:

updated() ... model=TS0505B manufacturer=_TZ3210_dxzgodw8 destinationEP=UNKNOWN deviceProfile=UNKNOWN

fingerprint profileId:"0104", endpointId:"01", inClusters:"0003,0004,0005,0006,1000,0008,0300,EF00,0000", outClusters:"0019,000A", model:"TS0505B", manufacturer:"_TZ3210_dxzgodw8"

Model:TS0505B
Manufacturer:_TZ3210_dxzgodw8
getting info for unknown Zigbee device...
fingerprint profileId:"A1E0", endpointId:"F2", inClusters:"", outClusters:"0021", model:"null", manufacturer:"null"
fingerprint profileId:"A1E0", endpointId:"F2", inClusters:"", outClusters:"0021", model:"null", manufacturer:"null"

I can provide additional information if helpful. I'd love to get it working and would be happy to try hacking around on the Groovy driver code if useful.

2

@user5925 with the Tuya Dimmer Module driver, have you tried setting manually the "TS0505B Tuya Bulb" Device Profile?

image

You can also try the Tuya Advanced Zigbee RGBW Bulb driver.

This F2 issue is a strange one. I had it with some Tuya devices, but after removing the problematic device and pairing it again, the problem disappeared.

3

I’ve tried both solutions. The result is the same for both. Hubitat thinks it paired, but the bulb keeps flashing red, indicating that it hasn't. I tried the Tuya Advanced Zigbee RGBW Bulb driver and got different log messages when I added the details for my device to your driver code (and Hubitat detected the device correctly).

I'm not sure what log messages I should be looking at in particular or how they correspond to the code in the driver. What's odd is that the device never exits the "searching" phase, meaning it keeps blinking red. In all my past experiences with Zigbee devices, the device indicates (usually by no longer blinking) that it's moved out of that phase. Then, you set the correct driver and things work. In this case, it seems like something more fundamental is at issue.

And, what's even odder is this device worked with the C5 hub.

4

Seems like a Zigbee connectivity issue with the C-8 hub. In this case, the driver doesn't matter...

If the device is paired and stays connected to the HE hub, then clicking on the 'Get Info' button using the inbuilt 'Device' driver should always produce a fingerprint log. I suppose this is not happening on your C-8 ?

5

Here's what I see when I pair it new:

  • getting info for unknown Zigbee device...
  • fingerprint profileId:"0104", endpointId:"01", inClusters:"0003,0004,0005,0006,1000,0008,0300,EF00,0000", outClusters:"0019,000A", model:"TS0505B", manufacturer:"_TZ3210_dxzgodw8"
  • Manufacturer:_TZ3210_dxzgodw8
  • fingerprint profileId:"A1E0", endpointId:"F2", inClusters:"", outClusters:"0021", model:"TS0505B", manufacturer:"_TZ3210_dxzgodw8"

That last message repeats 12 times. Then this:

  • getting device info in 10 seconds...
  • fingerprint profileId:"A1E0", endpointId:"F2", inClusters:"", outClusters:"0021", model:"TS0505B", manufacturer:"_TZ3210_dxzgodw8"

Then if I click the getInfo button, it does this:

  • getting info for unknown Zigbee device...

--

I'm thinking this corresponds to your statement that it can't stay connected to the hub, probably because of these F2 log messages?

6

In this case the F2 endpoint is not the problem, the device just leaves the C-8 Zigbee network after some time.

I have another device (a cheap water leak sensor) that behaves just the opposite - it works without any problems on my C-8 hub, but will leave the two older C-7 hubs within a minute after pairing.

With my device, obviously the manufacturer has interpreted the Zigbee 3.0 specs as “work with 3.0 Zigbee coordinator only” : (