Preflashed ESPHome / Tasmota Smart Bulbs with an Added Bonus - Kauf BLF10
Someone has finally done it, a bulb with an oh sh!$ recovery method! The Kauf BLF10 Bulb is on Amazon and preflashed with ESPHome. Yes, you can also install other open source ESP8266 projects such Tasmota, WLED, etc by simply using your web browser. No exploits, no hacks, no soldering, no wires, take it out of the box and go.
Purchase and skip the reading (Amazon)
The bulb is a 10W LED (not to be confused with wattages stated as equivalent), I do not see a lumen rating at this time on the specifications but found the brightness by eye to be on par for a bulb of this size. There are 5 independent color channels to this bulb; Red, Green, Blue, Cool White, and Warm White. None of that 4 channel simulated warm white or cool white mess! Keep in mind this is an A21 sized bulb that could have size issues fitting in some enclosures. What's the added bonus?
Your eyes aren't deceiving you, those are indeed solder pads for 3V3, RX, TX, GND and GPIO Zero. What does that mean? Hardware Recovery if needed! Unlike other bulbs that might have been converted to open source with Tuya Convert or maybe even Athom preflashed bulbs, they do not have the ability to be recovered from a bad upgrade, software failure, etc, but these definitely do. For myself that means no worry at all switching over to WLED for the holiday season, switching to Tasmota, etc. I know I can always break out the USB TTL adapter and install my software without any issues. Great job Kauf!
Kaufman Home Automation has done a great job on documenting everything you need for this bulb from custom YAML code with ESPHome, installation, converting to Tasmota, the Tasmota Template, etc. all directly from the source. Thanks to @tonyfav on the digiblurDIY Discord for digging through the ESPHome code to see the blue channel needed a bit of tweaking since it was too strong in default use cases in Tasmota as well. I've included this in the template below. If you do find the blue channel is too bright use the following command in the Tasmota console to knock it down a bit.
Kaufha.com also has a US/NA Smart Plug PLF10 with power monitoring as well. Be sure to check out their website for any new products, procedures, etc. I purchased a couple of bulbs as soon as I heard about these as I definitely want to support the cause of some preflashed ESP based devices with Home Assistant! Hopefully we see their product line expand as they feel out the market and see what other products are requested.
 |
| Kauf Bulb (top) , 60w Incandescent (middle) , Kauf Bulb Diffuser top down |
Kauf BLF10 Bulb
Amazon US - https://amzn.to/2YZNDeO
Amazon UK - https://amzn.to/2TnG2R4
Amazon CA - https://amzn.to/2JWsNq5
Discord Chat - https://discord.digiblur.com
Patreon - https://patreon.digiblur.com
Facebook - https://facebook.digiblur.com
Instagram - https://instagram.digiblur.com
Please note, the product links above could be affiliate links, using them could earn digiblurDIY a small commission of most purchases and helps with future video projects. Thank you!
Hi, the layout seems the same as some zemismart bulb i got year ago. I ordered two RGBW bulbs and one of them came with this PCB as RGBCWWW. It was flashed with standard firmware, but thanks to the pads, it was easy task to liberate it.
ReplyDeleteTried to flash WLED to the bulb but it says it's too big. Do you know of a way to get around that?
ReplyDeleteHi! What command do I send to the console to keep it from turning on when power is re-applied (after power loss)? Thanks!
ReplyDeleteRead a little (works sometimes) SetOption0 0
DeleteAlso poweronstate command will change that too.
DeleteHow do you send this command to the bulb using curl? "setpoweronstate" doesn't seem to be listed in the any ESP@home or tasmota documentation I have found so far. I will keep looking, but maybe I'm looking in all the wrong places? Can you link me to the right documentation?
DeleteHow do you get the bulb apart to get to the PCB?
ReplyDeleteThe diffuser just pops off.
DeleteIs there a full list of all of the specific parameters supported, for use with Curl?
ReplyDeleteI've found the "generic set" listed by ESP@home but I suspect it isn't the full set. For example, the "SetOption0" to turn off power-fail turn on isn't part of that set.
Hrm. I actually tried the "SetOption0" but I must have done it wrong, or I am misunderstanding how to send it?
ReplyDeleteThese are examples of what I am using - note that I specifically DO NOT want to use Home Assistant or any other similar thing. I need to control these from my own shell scripts.
$ curl 'http://172.16.12.208/light/kauf_bulb/turn_on?brightness=99' -X 'POST'
$ curl 'http://172.16.12.208/light/kauf_bulb/turn_on?brightness=200' -X 'POST'
$ curl 'http://172.16.12.208/light/kauf_bulb/turn_on?brightness=255' -X 'POST'
$ curl 'http://172.16.12.208/light/kauf_bulb/turn_on?r=0' -X 'POST'
$ curl 'http://172.16.12.208/light/kauf_bulb/turn_on?b=0' -X 'POST'
MQTT might be easier but you can use the web API
DeleteI don't understand your reply. The end goal here is to be able to have a shell script control the bulbs, via something like curl. So far the most basic things work, but I am wondering where I can find a find the full set of parameters and input that is supported using http.
DeleteMQTT is a protocol that can be used by just about anything. Send your commands via that but otherwise check out the tasmota docs for the HTTP posts.
DeleteWhat command line tool would I use in a shell script to issue MQTT commands to control the bulb? My understanding of MQTT is that there had to be some permanently running server - I don't want that. I just want to directly control the bulbs from a shell script, ad-hoc.
DeleteThe only "tasmota" docs I can find seem to be generic, and not specifically list the parameters supported by this specific bulb.
One thing I thing I've noticed is that, after some period of time (it might be a set time, or possibly random) it "reboots" and turns on full white, even if it was set "off" or to something else before. I'm not sure if this is some flaw or if it is by design.
If its a flaw, I suppose I will have to return the bulb. If its by design, I am hoping there is some way to change it? If I leave it off, I want it to STAY off, unless and until specifically commanded to turn back on. Any tips on that?
Ok, it looks like this is what is happening? How to I disable this "feature" in the bulb? I do not need any sort of watchdog timeout - there will only be a "client connection" to the bulb when it is commanded to turn on, off, change color, etc. Absent any further connections or commands, I want it to stay in the same state it is in indefinitely.
Deletehttps://github.com/esphome/issues/issues/1420
... either that, or if I can't stop it from restarting, how can I tell it at least to revert to its previous state, eg if it was off, to STAY off.. This will leave it with an annoying "flicker" every interval if it is on, but definitely better than it randomly rebooting and turning on in the middle of the night.
Delete... using a command line tool such as curl, no server application, no Home Assistant, etc.
What software do you have on it?
DeleteI had done some research, found a "power on" state, did some more, and realized that was added in a newer firmware than I had (1.6 vs 1.4) so I downloaded that from the kauf site and installed it. There HTML page the bulb shows now shows a "power on" state (which shows as "always on full white") and there is even a drop-down with apparently other options, but pulling it down and selecting one doesn't change anything, nor is there a "save" button or anything to make it take effect. I also cannot figure out what the URL is I would use with curl to adjust this.
DeleteThis might be helpful https://tasmota.github.io/docs/Commands/#with-web-requests
DeleteI appreciate your help - but I've seen that, and it doesn't give me any clue how to change this particular setting.
DeleteI've even tried some of the basic commands there, copy/pasting the examples given and they don't seem to work at all.
For instance
curl -v http://172.16.12.208/cm?cmnd=Power%20off
just gives me
HTTP/1.1 500 Internal Server Error
I don't think you have Tasmota on it then if you can't open the Web GUI.
DeleteNo, it doesn't it has the "kauf" firmware on it.
DeleteHowever, I have been in contact with someone from that company, and they have led me in a direction that I think will solve my issue.
I noticed that on the kaufha.com they have a different template:
Delete{"NAME":"Kauf Bulb", "GPIO":[0,0,0,0,416,419,0,0,417,420,418,0,0,0], "FLAG":0, "BASE":18, "CMND":"SO105 1|RGBWWTable 255,255,153,191,191"}
Vs your
{"NAME":"Kauf Bulb", "GPIO":[0,0,0,0,416,419,0,0,417,420,418,0,0,0], "FLAG":0, "BASE":18, "CMND":"SO105 1|RGBWWTable 255,255,153,191,191"}
The RGBWWTable is different and their has that extra so105 command. Which one is better to use?
That is all your choice if you want that blend and if you want the channels limited that much. I use mine for 99% of the time on WW or CW combos so I left mine 255,255 limits on those two channels. All that command does is say, hey, make the channel have an artificial software limit, don't go as bright. So 153 out of 255 is the limit on the blue for example. 191 out 255. I didn't like that myself. It's your bulb and you choose the best what you want.
DeleteIt's great to have this available. Everyone changing chips has made things rough.
ReplyDelete