Open BR4DY opened 5 years ago
why would you need a new signature? i have simmilar bulb and it worked perfectly (untill i updated firmware which i know i shouldnt :( )
He asked people to post the signature of bulbs and a link as to where to buy them. Also updated the firmware on one of the bulbs and now that doesn't work too. Going to explore using the IFTTT integration and a homebridge-IFTTT plugin as a workaround.
It seems new Tuya firmware was supported in this lib https://github.com/codetheweb/tuyapi/issues/175, but it doesn’t seem the case for current plugin...
Is there any development going on here?
Please give the latest rc
release a shot by doing npm i -g homebridge-tuya-lan@rc
. It includes logic to understand this newer API.
A known issue is that the current state is not reported by some devices; they however work fine as soon as you interact with them. I have reached out to Tuya for a solution.
The Setup Instructions have changed in case you need to obtain a fresh id
and key
.
Ready to handle Lamp1 with signature {"1":true,"2":"white","3":71,"4":35,"5":"ffb0e101434fff","6":"bd76000168ffff","7":"ffff500100ff00","8":"ffff80040000ffff0000ff0000ff0000ff0000ff0000","9":"ffff5001ff0000","10":"ffff050200fff24d00ff4d00ff4d00ffff0000ff0000"}
Bought from: https://www.aliexpress.com/item/WiFi-Smart-LED-Candle-Bulbs-E14-5W-Equal-40W-RGB-Warm-Day-White-Colour-Changing-Mood/32966237286.html?spm=a2g0s.9042311.0.0.6d384c4dkVYwtv