Greetings from Australia and thanks @jonathanb and other contributors. I just found this thread and driver today.
Got the integration going up to the point where it interrogates the API to get child devices. I can see a deviceCount of 3 but it fails to create them and has a state: error
The log shows it executing API GET [uri:https://openapi.tuyaeu.com, path:/v1.0/devices/xxx/specifications
However I'm getting a code:2009 "not support this device". JSON response is:
{"code":2009,"msg":"not support this device","success":false,"t":1689843869060,"tid":"6ee6802e26dc11ee8ac9ce4d0cb672c1"}
{"code":2009,"msg":"not support this device","success":false,"t":1689843868998,"tid":"6ede8f6926dc11ee94e0a2e0adfc0b14"}
{"code":2009,"msg":"not support this device","success":false,"t":1689843868692,"tid":"6eb0614526dc11eea28d7e2a94be2486"}
This is an IR/RF blaster and two remote commands for roller shutters (open/close).
I'm way out of my depth with I look at the driver code and API support doco. If it can't determine the category through the specifications API then I suppose there is a fudge required to create the devices in HE?
All of my switches are the fan+light dimmer combo--the fan is working but the light isn't. I noticed earlier you mentioned adding more support for the combo switches, did you ever get around to adding/fixing this?
// EDIT: for clarity, your driver did enumerate the combo switch properly and split it out into a separate fan and dimmer control.
// EDIT #2: finished reading the thread; didn't see anything to address my particular issue. Did anyone else encounter this?
PS: if this is already answered, apologies--I''ve read through the entire thread but it's gotten LARGE so possible I missed something.
@limeypride I had a very similar problem with my fan which has a built in Tuya wifi controller. I could get the fan to work but not the light.
So far I’ve only got as far as getting the light to work on / off in hubitat and not change colour or dimmer settings. If this stop gap measure would help you take a look at my posts 430 and 433 in this thread and see if this works for you
I'll begin working through those steps once I'm done with work. I already have the IoT direct driver assigned to my loft fan but I'm having a helluva time pinning down its IP address--over 80 WiFi devices and 11 Tuya devices/switches. I figured I'd just use MAC vendor prefixes to narrow the list down only to find that Tuya have 14 or so assigned prefixes... sigh. Anyhoo, I'll figure it out.
I'm assuming you had to tweak OP's original driver code. If so, could you post your mods--it'll probably save me a ton of time later if our switches happen to be compatible.
The ON/OFF only functionality is enough since what I'm really trying to get to for now is the ability to have the Hubitat keep my lighting sane during daytime hours and when we go to bed--OFF would be great.
Has anyone had success removing scene/groups that have been deleted? I still have a couple that just won't go away, and new ones are not synching. Says [Deprecated] on the scene api thing, and won't let me renew...Seems they changed something.
I've configured local control for RGB lights with the library/driver you linked a few years back. The one thing is that my lights are running the 3.4 protocol so I don't think it's working correctly and it just falls back to the cloud control. I tried searching but didn't see if there was an update for 3.4 bulbs.
I had wondered for a while why my device count was always 20 when I have more than 20 devices. So it appears in the json the code is looking for has_more but the json contains hsa_more
lines 1841 and 1842
LOG.info "Received ${result.devices.size()} cloud devices (hsa_more: ${result.hsa_more})"
if (result.hsa_more) {
once I made that change I get the proper count.
New to the Tuya world today, picked up a Treatlife DS03 Fan Light switch to retire the insufferable Hampton Bay zigbee controller.
So far I’ve gotten the FAN only working via this driver. Has anyone figured out how to get the light side working as well? Tried switching the child driver to Generic Component Fan Light Control, but that didn’t seem to do anything.
Has anyone got one of the Diffusers working with this?
i'm all set up, 2 child devices created, but as they are not recognised they are created as generic switches - the on/off switches the LED on and off on the diffuser.
Hi Guys, i'm completely new to this thread and its a very long one. i'm just beginning to set things up from post 1, point number 3. It's a brilliant piece of kit and thank you!
Hi,
I used this for a while with tuya app and smartlife app. But now my smartlife do not work anymore. I click initialize but it tell me: Cloud API request failed: {"code":1106,"msg":"permission deny","success":false,"t":2423525252,"tid":"235243gfd25252wer"}
The tuya still working... anybody with the same issue or an idea on how to solve it? My tuya account is up to date with all autorization that I renew each time!
Thanks!
Ok, I found out that if I create a new device from the start, it discover child devices and seems to work fine... So I turn the question like this: Why my parent device stopped working? And is there a way to replace old child devices with new one where its used, like webcore? One by one is a little too long and they have the same name so hard to choose the right one and I m not sure if I remove one device and allow the other if it would keep the name or if I wont be able to know wich device it was within pistons...
little question, I would like to add healthcheck capability to child device and I just dont know where to start, can you tell me what you think about it? Is it a possibility ?
thanks!
My Tuya devices had been working fine, but they now periodically fail with the Tuya virtual device status showing as "error." After I hit "initialize," things start working again.
I'm trying to make a rule that says when the Tuya virtual device shows error, trigger initialize. However, while the Tuya virtual device shows up under possible triggers, I can't figure out how to choose it as an action. I select "run custom action" and then look under "select capability of action device" for Tuya virtual device, but it's not listed. I had thought every device is listed under "actuators," but it isn't there, nor can I find it in any other category. Any advice?
EDIT:
Well, it hasn't shown an error for a few days, so maybe the issue was something transient on the server side. I still haven't found a way to have a rule trigger initialization of the Tuya virtual device, but I can at least have it send me a notification if there is a persistent error state.
You are trying to run the Initialize on the main integration driver I assume?
Edit the code for the integration on the hub. Near the top of the code in the metadata section, add the Actuator capability right by the Refresh and Initialize ones so it looks like this:
so possible I missed something.
