-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
_TZE200_3towulqd with cluster check #740
base: SDK3
Are you sure you want to change the base?
Conversation
@MihaiINW Could you look at this? |
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. |
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. |
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. |
@maccyber , you mentioned that for your device you got the following attributes and their values: { The device I have has the following: { Any idea if the different appVersion can cause issues? Maybe @JohanBendz has some ideas about this? |
@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. |
No description provided.