WLED-wemos-shield VS feature-requests

If you want to try out the new stuff, you can grab the nightly builds here https://github.com/srg74/WLED-wemos-shield/tree/master/resources/Firmware

Here’s the srg74 one with relay at Tindie And the GitHub for it github Shield at at Tindie

If you're running that many strips you'll need to ensure you can supply enough power, and at various points along the length of the strip. You may also need a level shifter to ensure the strips are change reliably. You may also want to save energy and avoid the strips consuming power when "off", which they do. So you can get a shield for the WeMos D1 Mini which includes a level shifter and relay, like: https://github.com/srg74/WLED-wemos-shield and works with WLED.

If you are considering using lots of LEDs which may be powered off for large amounts of time, then you may want to look at using a controller board with a relay which cuts power completely to the strips when "off", like the WLED-Wemos-shield: https://github.com/srg74/WLED-wemos-shield

This is the best expliantion of what I'm seeing but the solution the issue was closed with doesnt work for me (the switch.turn_on = I2C_POWER line causes an error). https://github.com/esphome/feature-requests/issues/1511

I found this post on github: Cover, open_duration and close_duration, variables instead of just numbers · Issue #930 · esphome/feature-requests (github.com) The response to the post was:

Yes, use global with restore true. see example here https://github.com/esphome/feature-requests/issues/461

Found this: https://github.com/esphome/feature-requests/issues/1712 looks like documentation is incorrect...

It's not currently supported.

I've had a github issue for ESPhome open for a while on this. Although some possible solutions have been presented, I don't think anyone has been successful.