Well you could, it’s an ESP12S board with 4MB or memory. But I’ve just realised you are using a LED strip with separate R, G and B PWM channels for control. So do not do it.
WLED is only compatible with WS2812B, WS2811, SK6812, and APA102 one wire addressable type strips.
Exception in rgb_received when handling msg on ‘tele/magichome/STATE’: ‘{“Time”:“2019-10-28T11:04:01”,“Uptime”:“0T00:29:51”,“Heap”:14,“SleepMode”:“Dynamic”,“Sleep”:50,“LoadAvg”:19,“POWER”:“OFF”,“Dimmer”:100,“Color”:“FF000000”,“HSBColor”:“0,100,100”,“Channel”:[100,0,0,0],“Scheme”:0,“Fade”:“OFF”,“Speed”:1,“LedTable”:“ON”,“Wifi”:{“AP”:1,“SSId”:“PimpRoad9”,“BSSId”:“D0:17:C2:D8:7C:70”,“Channel”:10,“RSSI”:86,“LinkCount”:1,“Downtime”:“0T00:00:04”}}’
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/mqtt/light/schema_basic.py”, line 362, in rgb_received
rgb = [int(val) for val in payload.split(",")]
File “/usr/src/homeassistant/homeassistant/components/mqtt/light/schema_basic.py”, line 362, in
rgb = [int(val) for val in payload.split(",")]
ValueError: invalid literal for int() with base 10: ‘FF000000’
Seems like it is sending color in HEX instead of RGBW. FIXED that error. My rules in console was wrong.
I have a couple of RGBW LED Strips.
I use an h801 led controller to control them. it’s based on ESP8266
Here is an example of the code I used to flash the device:
After several hour of reading (and ignoring my wife, she´s not very happy now) I finally found the setting for getting it to work!
SetOption59 1
Send tele/%topic%/STATE in addition to stat/%topic%/RESULT for commands: State, Power and any command causing a light to be turned on. »6.3.0.13 0 = disable (default) 1 = enable
You are a life saver! I could not figure out for the life of me how to fix my new bulbs since Christmas after using the latest Tuya-Convert! Thank you so much!
I had a similar issue when I started using the Tasmota. I used to upload everything by Arduino IDE and with a pre-written sample code for the configuration.yaml for HomeAssistant. I used the code from the top and continued from there. I found that the button did not update when I set another value, but only after 60 seconds. Turns out this is the default ‘update’ period where all the device parameters are published. I got everything working by writing: TelePeriod 10 in the console of the esp web app. To let itself update (just really a temporary fix) .
For the following, note that my device name is: DVES_2F675E = %Topic%
But it turns out that the subscription topics are not correct. Where tele is used, there should be used stat. Because at the time the ON Payload is written to "cmnd/DVES_2F675E/POWER" the response is written to the "stat/DVES_2F675E/RESULT" topic
I added descriptive text after the effect number, not that this addition is handled perfectly by the esp and is very handy for the HomeAssistant GUI
Thanks Koen, this worked EXACTLY how I wanted it to, and with very little change on my part thanks to your brilliant explanations! I’m running on TASMOTA 8.2.0.3. You saved me a lot of time with this template.