A few months ago on Reddit in /r/homeassistant there was a thread about someone getting their system setup with their WiFi bulbs and using the Local Tuya plugin to control them.
Today, I put some time into and was able to decode the settings for Local Tuya to properly (or within a 2% range of brightness) . The settings are as follows in case anyone else has been stumped by them.
You will need to have your Device ID, and local key, but once you get in there, the settings are:
Brightness 3
Color Temp 3
Brightness Lower Value: 15
Brightness Upper Value 255
Color Mode 2
Color 5
Minimum Color Temp in K 2700
Maximum Color Temp in K 6500
Color Temp Reverse Unchecked
Scene 1
Music Mode Available Unchecked
I hope that if anyone else has run into this issue can benefit from these settings as they have so far been very elusive online from my searches for the proper settings.
EDIT I have been able to test this some more with other Feit bulbs on lower firmware. I managed to get this to work on the 1.0.12 firmware. On the suggestion on another post below, I ended up attempting a flash to the Tasmota or similar firmware and ended up bricking a bulb so I am out one so I tried a replacement one I had which was a spare. As for the firmware, you can not easily see this in the Tuya App. but if you pair the bulb with the Feit app, you can see the firmware version. Be aware, by doing this, your local key WILL CHANGE so you will need to grab that from Tuya when you add it back in. The bulb seems to auto update on the Tuya App, but not Feit at least from what I could tell.
The older firmware does not take these settings very well, for example, turning off the lamp, turned it to a very dim 2% or so and burnt brown/orange color. I left the bulb in the Tuya App over the weekend and on Monday morning, it was working as it should so I think it was a firmware update which took place to get this back up and running.
I have flashed Tasmota to outlets before, but never a bulb and my understanding from some of the links in the one you provided all suggest modifying the bulb hardware before flashing.
@Hellis81 For the Brightness Lower Value: 15 to get it to match it should now be 23. I had it too low, but this matches the Tuya App.
EDIT: So, I tried flashing and the firmware on the bulb is too new:
Timed out while waiting for the device to (re)connect
Attempting to diagnose the issue…
Your device’s firmware is too new.
Tuya patched the PSK vulnerability that we use to establish a connection.
You might still be able to flash this device over serial.
For more information and to follow progress on solving this issue see:
teardown is optional, looks like the same fcc id as the one with beken chip
use tuya-cloudcutter (tuya convert for beken) and you’ll get it done in like 2 minutes
Bricked a bulb doing this, others are on 1.0.12 firmware and can’t be unlocked yet - I have to wait I guess until they update in the background. I had 4 spares, so now down to 3. I think I soft bricked it by putting the firmware which I thought matched my bulb as shown in the video and it needs to be SPI flashed. The bulb refuses to light up and base gets hot fast. With that - if I feel adventurous will try, but not quite ready yet. I have a JTAG set up and can maybe do that, but that’s for another day.
My other bulbs, I think I will leave as is - and once I confirm they are on the 1.1.2 (which is the one I was able to unlock was on), I will detach them from the Tuya Cloud for local control. I never got that far, but I am guessing the supplied Device ID and local key, would just replace the one I have in the Local_Tuya addon?
I added an edit - I had an issue with the color myself, but setting the color option to 5 (value ff00000000fff) fixed the issue, so try that. The colors replicated accurately from what I could tell. My wife suffers from migraines so I had to keep them dimmed to 15% when testing this, but I was able to confirm most color tests I did (Red, blue, green, yellow, purple, pink, white, orange) So it worked as expected on my end with the 1.0.12 firmware. My OP has been edited to show more information on the firmware, so YMMV if you are on a different version.
Pardon my ignorance, but what is the “Device ID”? Is that the “Virtual ID” displayed in the Feit app? Also, what is the “local key”? Is that the “User Code,” also from the Feit app?
Sorry for the late reply, (I didn’t get the notification) the Device ID and Local Key are part of Tuya Cloud which only now applies to the Tuya Local plugin.
For this you would need to look online or here on how to set up a dev account with Tuya. (https://auth.tuya.com/) Download the Tuya App for your device. Once you do this, you need to reset your bulb by turning off and on rapidly a few times until it blinks to pairing mode. Then, in the Tuya App, pair your bulb(s) with that, then go through the site and grab those values.
The last I checked tonight, it is here. My dev trial expired with them, so I can’t do this anymore, but that is also why I copied my local keys.
If you don’t mind controlling your devices with Tuya’s app (works mostly with Feit Bulbs), since the latest updates to Home Assistant, none of this is needed and it will integrate fine with the Tuya app and you will have full control (just cloud based). I found that the Tuya cloud integration worked perfectly for some string lights I bought for Christmas and while I got the local key and the like, it didn’t play well with Local Tuya and there was no support yet for them. I was able to control them perfectly with Home Assistant using the Tuya App integration which for us was fine for the holidays only.
My bulbs are BPA800/RGBw/AG/2(P).
