Like many Tuya devices sold by third parties, it probably has a unique fingerprint, and it may be using proprietary code.
Check the quick browse list in the community-created wiki for remotes and buttons and see if thereβs a Tuya button edge driver there. It might also be listed under MOES.
If you find the right model, but the fingerprint isnβt an exact match because the manufacturer name is different, ask in that author thread to have them include it.
The Ultraloq U-Bolt Pro Z-Wave Smart Deadbolt has not be assigned an Edge Driver as yet. I have tried to uninstall the re-onboard the device on a couple of different occasions and it does not discover any of the Z-Wave Drivers to which I have subscribed. I am requesting that the devices manufacture and fingerprints be added to one of the existing Z-Wave Lock drivers.
Hello everyone, I got a hold of some very compact and inexpensive sensors from EZVIZ (HIKVISION) that Iβve had no luck getting to work and would love to buy more because of their bang/buck ratio.
One is a basic door sensor and the other is a motion sensor.
Hello again. Just noticed the drivers are crisscrossed. The T1C is the motion sensor and the T1C is the contact sensor. At the moment the T1C is set as contact sensor and the T2C is set as motion sensor.
Hoping to get this product in the next week or so.
I may work with the standard temp humidity sensor but I believe there are settings for the device at control whatβs displayed on the lcd panel. These are present in the ewelink app if connected via an ewelink hub. But since I wonβt be using ewelink it would be great to get this supported in SmartThings
I only know the automatic, waiting maximum 12 hours since the publication of the new version and manually with the CLI from a PC.
I donβt know if there will be any way to force driver update
Iβm trying to get the following running, but it keeps reverting to stock DTH instead of edge drivers, I have your switch and light installed, as well samsungβs beta zigbee switch driver.
I see it should match up with your light driver, and samsungs switch driver but think the extra character in the model name is causing problems - any suggestions?
Do you think itβs the weird non-printing character causing the mismatch?
But I suspect the following symbol οΏ½ isnβt correct, and has been put there because itβs a non standard character the ide canβt understand it - but I canβt be certain.
Is there another way to get the model name than the old ide?
Edit: I have just checked the value through the api browser, itβs also as above with the weird character in.