Open kennethahoward opened 3 years ago
+1
I'm having the exact same problem with a generic Tuya downlight. I retrieved the keys via tinytuya. The Tuya app can control the light. It appears in Homebridge, but nothing happens when I turn it on/off/change settings. I tried both HEXHSB and HSB - no difference.
Log spew:
[TuyaDiscovery] Discovery started on port 6666.
[TuyaDiscovery] Discovery started on port 6667.
[24/12/2021, 22:19:03] Homebridge v1.3.8 (HAP v0.9.7) (Homebridge C8E2) is running on port 51779.
[24/12/2021, 22:19:04] [TuyaLan] Discovered Smart Bulb 2 (ebbc5c932afe52aebab7fx) identified as RGBTWLight (3.3)
[Tuya] Changing ping gap for Smart Bulb 2 to 9s
[Tuya DEBUG] reconnect called for Smart Bulb 2
[24/12/2021, 22:19:04] [TuyaLan] Connected to Smart Bulb 2
[Tuya] Sending first query to Smart Bulb 2 (3.3)
[Tuya] Heard back from Smart Bulb 2 with command 10
[24/12/2021, 22:19:04] [TuyaLan] Ready to handle Smart Bulb 2 (RGBTWLight:3.3) with signature {"20":true,"21":"white","22":1000,"23":1000,"24":"000003e803e8","25":"000e0d0000000000000000c80000","26":0}
[24/12/2021, 22:19:05] [homebridge-tuya] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://git.io/JtMGR for more info.
[24/12/2021, 22:19:05] [homebridge-tuya] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://git.io/JtMGR for more info.
Switching back to tuya-web for now :-(.
Config:
"type": "RGBTWLight",
"name": "Smart Bulb 1",
"id": "eb2a3268a518fe06d9tzno",
"key": "XXXXXXXXXXXXXX",
"manufacturer": "Tuya",
"model": "Default-Model",
"colorFunction": "HSB"
I'm having some issues getting a Cree Connected Max PAR38 White+Color Floodlight bulb working with Homebridge Tuya. I used TinyTuya to gather the device ID and key for the light. Cree has their own app but it appears to be just a rebranded version of the Tuya app and I'm able to control it identically with the Tuya app. I also registered it in Tuya Cloud as part of the process outlined in the TinyTuya docs to get the ID and key. I can see that there is communication with the light when homebridge starts up:
But when I try to control the light (power it on), I get this error:
I restarted Homebridge in debug mode to get more information and saw the same behavior from start. Oddly, though, after a number of minutes, I saw this in the log:
I could then see it appearing to respond in my Home app on the iPad I'm using as a Home Hub, however the light itself remained off.
I still see some of this in the log as well.
Are there any further troubleshooting steps I might take, or does this indicate a bug with this particular model of bulb (Cree)? I'm willing to provide any further logs or info if it would help.
I'm running Homebridge v1.3.4 with Node.js v14.16.1 with homebridge-tuya v2.0.1 within the onzu-homebridge1 docker container on a Synology NAS.