_TZE200_3towulqd with cluster check

[maccyber]

No description provided.

[Boechie]

@MihaiINW Could you look at this?

[MihaiINW]

I tried testing this code with the device for which the #724 PR was made. Unfortunately it did not want to pair the device. The only way it did work is if I extended ZigBeeDevice instead of TuyaSpecificClusterDevice, while still using the TuyaSpecificCluster. This way it did report the values. But I am not sure why it didn't work with TuyaSpecificClusterDevice since it already extends the class ZigBeeDevice.
As for implementing the settings configuration, I have tried that as well based on the commented code in the onSettings method of this PR. It seems that it does save the changes made to the settings, but I do not notice any change in the actual use of the device.

[maccyber]

Thanks for testing. Does this work for you if you use ZigBeeDevice instead of TuyaSpecificClusterDevice @MihaiINW?

If so, I can remove the settings and we could use the same driver. TuyaSpecificClusterDevice is just used for saving settings.

Btw, about settings - you have to insert your pin after changing a setting to wake up the device, i have not found another way.

[MihaiINW]

When I first tested the device, I had to try many times to pair it until it worked. From then on when I tested I did not remove the device from the Homey, I was just running "homey app run" for debugging. When testing whether the settings take effect, I could see that only the intervalTime being set to 1 would make the luminance sensor report every 60 seconds independent of the motion sensor, but any other value I'd try didn't seem to work.

I then removed the device and tried adding it again, but it never paired. So I am not sure why it did pair that one time. It's very strange.
I noticed that whenever I add the piece of code: Cluster.addCluster(TuyaSpecificCluster); it causes this problem, even if I don't use it further in the code.
Any idea why this would cause issues?

[MihaiINW]

@maccyber , you mentioned that for your device you got the following attributes and their values:

{
"manufacturerName": "_TZE200_3towulqd",
"zclVersion": 3,
"appVersion": 72,
"modelId": "TS0601",
"hwVersion": 1,
"dateCode": "",
"clusterRevision": 2
}

The device I have has the following:

{
manufacturerName: '_TZE200_3towulqd',
zclVersion: 3,
appVersion: 130,
modelId: 'TS0601',
hwVersion: 1,
clusterRevision: 1
}

Any idea if the different appVersion can cause issues?
I find it a bit strange that in your input cluster list you don't have the Tuya manufacturer cluster mentioned, yet it is there since you said it does report values.

Maybe @JohanBendz has some ideas about this?

[HendrikGrunstra]

I've merged this pull request locally and installed to my Homey. Before the sensor didn't work properly, with this change of code the sensor works for me. Thanks.

I have this version (same as @Boechie)
image

[Boechie]

@HendrikGrunstra Thank you for the confirmation. FYI: We are now working on a improved version of that driver, that will support both types, regardless of its support for Zigbee Standard Clusters or Tuya Specific clusters. I hope we can supply that version to the community in the near future.

[dlnraja]

Hi! 👋

Thank you for this contribution! The fingerprint(s) from this PR have been integrated into dlnraja/com.tuya.zigbee (Universal Tuya Zigbee fork) as of v5.11.14.

Install the latest test version:
https://homey.app/a/com.dlnraja.tuya.zigbee/test/

Community forum:
https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352

This PR can be closed. Thanks for contributing! 🎉