I have a bunch of Tuya devices, and have been converting over to Hubitat. The challenge is that some things just don't seem to lock in correctly with the existing drivers.
For instance, I have 5 temp/humidity sensors on my desk right now that work fine with Tuya, but when I set them up with "Tuya Temperature Humidity Luminance LCD Display with Clock", they get identified as:
While these should all follow general TUYA guidelines, I do not understand the file on how to ensure these types are properly recognized.
Now the point isn't that they don't configure. They do that to some degree. The problem is they do not report anything - just that they are online/offline -- and sometimes that the temperature etc is "unknown". Not too helpful bits of info, so I know there has to be something that Joe Average should be able to do to enhance the driver to deliver useful results.
Now, it is possible that I will be advised to get the latest version of the driver. I believe I have that, being v1.8.0 which addresses issues with the big 2.4.0.x upgrade to Hubitat that recently occurred.
So is there some place where a soul can read up on how to tweak our available drivers to achieve good results with the never ending list of definition variations on what is basically the same product?
What driver are you using for these? It sounds like you are using a custom driver. Developers typically create a topic in the forum (here) with information and a place for discussion about their driver, so I would suggest finding that for yours, seeing what you can find there, and ask questions if you can't find anything.
As a side note, if the best answer you can give as to what you're using "from HPM," that is an easy way to install things -- but it's not a place per se. It just links to existing works if the developer (or someone) has chosen to make their work available that way. The "View Apps and Drivers" page will show you information about what you're using, including a "Community Thread" link (which would take you to what I'm talking about above) if the developer has specified one there. If not, a search here for whatever information you can find may help.
First note is I found the right driver for Moes T&H so that isnt an issue now.
I got the impression that the thread for the Tuya drivers was no longer really being used. I can dig it out of course. I am NOT using custom drivers of my own, but those from the HPM, and that I have also accessed (the same driver code) from outside of that.
I will look around more, but the question on how to take a driver and tweak/modify it to meet needs not covered so far, would be ideal. The drivers aren't also so obvious on how they are structured.
Which TuYa driver? There are many such threads on TuYa drivers. You’d be best off posting in the thread for whichever driver you want to modify (tweak in your terms).
The author and users of that particular driver are better positioned to help you; they are most likely to see your request if you make it in a thread dedicated to the specific driver you wish to change.
In general, this requires knowledge of both the Zigbee protocol as well as what the device does (with Tuya, often manufacturer-specific clusters, not always the same, and different attributes in these clusters for various properties of the device) -- beyond knowledge of how Hubitat drivers work, which isn't really much help if you don't have a handle on either of those first. If you share more about your background on these subjects, someone may be able to suggest a good starting point.
If you don't, your best bet would probably be asking if the developer of a similar-looking driver would be willing to help you out if you provide them the information you do know, such as the model numbers you already have and possibly the clusters the device reports. There are a few Zigbee experts here who are often willing to help (though, of course, this should not be considered a guarantee). The Community topic for such a driver is the often a good place for such discussion, so that's again what I'd suggest finding.
'Tweaking' Tuya ecosystem Zigbee device drivers is not easy.
Remember that these devices are not designed and not intended to be used outside of Tuya own hubs. Also, none of these devices are actually manufactured by Tuya (there are a few exceptions). Tuya is not mainly a device manufacturer company; Tuya provides the sophisticated Tuya OS development platform and the Tuya Cloud services for hundreds of smaller companies that do the actual development and manufacturing of these smart devices. Next, thousands of sellers are selling these devices under different brand names.
So, a 'Tuya' device produced by different companies may have different Zigbee device Manufacturer IDs. They may differ in the plastic cabinets that the electronic is put into, may use different battery types, etc..
There are seventeen known manufacturers of (presumingly) the same device
TS0201 - _TZ3000_fllyghyj This is the eighteen manufacturer - probably a new one and this device fingerprint is not in the driver (yet).
When using the 'Tuya Temperature Humidity Illuminance LCD Display with a Clock' driver, you can try to manually configure this device to be recognized and messages to be processed as the rest of the 'TS0201' devices group. Select 'TS0201' from the drop-down menu in the Preferences section and then click 'Save'.
Very important: to make this device work in Hubitat, you need to pair it again to your HE hub (without deleting it). Just pair it again:
This seems to be one of these Tuya devices that must be initialized during the pairing process with a very specific Tuya 'Magic' sequence of Zigbee commands. This is a kind of 'foe or enemy' handshaking procedure that some (not all!) Tuya-OS devices require to work when used with non-Tuya Zigbee hubs.
Update: after reviewing the code, I found that the TS0201 _TZ3000_fllyghyj fingerprint was already in the latest driver version 1.8.0
Was this driver selected automatically when you paired the TS0201 _TZ3000_fllyghyj for a first time to your HE hub?
If not, then most probably the device fingerprint InClusters are not correctly defined in the driver.
Please change the driver manually to the HE inbuilt 'Device' driver, then try to obtain the fingerprint by clicking on the 'Get Info' button at the same time when the device is awake. You can wake it up by pressing the pairing button shortly, or by rapidly changing the humidity.
Thank you for such a wonderful, clear and helpful email.
I was able to get 4 of my 5 temperature sensors to work after much effort of pairing etc.
I did as recommended with repairing without removal. As well, I have found rebooting the HE C5 I am using seemed to help in some cases.
Of the two noted examples, the _TZ3000_fllyghyj turned out to pair and work correctly with the Generic Zigbee Temperature Humidity/Sensor driver, while _TZ3000_xr3htd96 finally worked with the Tuya Temperature Humidity Illumination LCD with Clock driver.
The only one left is a small LCD display one which is just not cooperating at all. It works fine on SmartLife, and was reference mid-2024 in the driver thread for something TZB05 or something like that.
Most things are resolving now, so we'll see how all the new items I am adding do. Sometimes its challenging to get item to come alive, stay alive, and report properly. I really do appreciate the wonderful drivers that you have written and contributed to. Great stuff!
With some more good fortune, I hope to have my place fully automated within the month.
It is a ZTH05 temperature/humidity LCD display and it connects to HE but does not work with the drivers available. It is definitely Zigbee. I can pair it with my Tuya/SmartLife gateways under a Zigbee gateway just fine.
