This is my first post and I want to say thank you to all of you who contribute to this incredible project.
It is by far the most user friendly and open RGB* LED controller firmware ever.
Recently I thought about giving away a complete set to someone. They are not tech savvy and would probably not even use the interface to WLED.
My idea was to gift them a strip of WS821* LED for outside. Electronics are covered, but implementing a seasonal switch to a different preset can’t be implemented with the current timer options and would require those interested to implement it offline and then upload the whole compiled firmware to the controller.
In most settings there is still enough resources left for custom mods (flash/ram/CPUs).
It would be great if there were a small subset of commands in a script language (uPython?) that can be interpreted by the controller and would also be part of the configuration or preset backup.
In my case it would not require many lines of code, just a short state machine that compares current date with a variable and switch the preset to preset X.
I understand that this is not a use-case for all and its implementation would be tricky because of the sparse resources (especially ESP8266 and similar MCU with little flash and no SPIRAM) and furthermore the hooks that would be necessary to enable a scripts to influence the state machines in general.
But it would be neater than toggling inputs by using a piggyback MCU with RTC (or even NTP via *LAN)
Thank you for taking the time to read my first post
There is already an option for Calendar-based preset activation which can cover a bunch of seasonal things (if you can get NTP into the ESP).
To your point about a “mid level API” via some other device(s), that exists now. Unfortunately it’s not in a prettied up form, the WLED API is extremely powerful (if somewhat sparsely documented). One of the aspects recently uncovered (to me at least) is the ability to use the API to rewrite (or add) presets and then fire them or even leave them in waiting for the next calendar event. In addition, you can even change the base configuration of your LED setup and force WLED to reload that on-the-fly via the API.
The relevant details were in an attempt to restructure a setup between 1D and 2D and use various effects: 2D - 1D Presets
There are a number of techniques shown there that can give you the tools to build the tools you are envisioning (I think).
And on a final note about simple interfaces, don’t discount the basic Json-IR interface.
It can be a very easy way to hand over basic control of a device.
The new Wiz-mote interface is even more powerful.
almost everyone here does its own stuff no need to do such a projekt
it is interesting ok but people like this woudt be better up with the twinkle sets all over the next Homedepo worldwide at a good cost and workes out of the box
Thank you very much for your prompt and very helpful response!
I will have a look at the options and consider the IR-JSON too, maybe I just need some infrastructure on my side and the possibility to connect to it from the WLED in another household.
More use-cases other the one above would be necessary to justify further exploration of the feasibility of an interpreter within WLED.
PS:
This is really cool! If I link our networks (VPN) then this would be easily accessible.
Even simpler:
Using AP-mode and connecting when the season comes and go for a cup of tea there.
