I read several posts where people have made similar requests and got shot down with use sync. I think my proposal for this ability shows validation to add/allow this.
Example:
One room with three completely different lighting setups. Let’s call one ‘mirror,’ two ‘ceiling light’ and the third ‘table lights.’ Let’s complicate that and state that two of them are custom mapped because of wiring logic complications. I want the ability to use them all not sync’ed. I would like a button on table lights that calls out “load preset1” on the other two but not continue to receive all of my other future changes. In my case I want them to all turn specifically mapped areas to white that would be programmed into preset 1. I would also like a double press on that button to run preset 12, as example, because that is strobe lights. Perhaps long press sets all to max brightness or reboots all or change to a specific palette, or, or, or… If I have sync on all changes on master change all others.
Is it just not technically an option to send 10.10.10.45/win&A=255 and also send 10.10.10.46/win&A=255 or send API to run playlist or whatever API I want to send?
If I understand correctly: you want to “abuse” one WLED instance as a remote controller for the other two? Why not just add a proper remote?
I wrote code for that, its here:
What you call abuse I would call a simple solution not needing additional hardware. When sitting at my “table” and we want all lights to a specific condition, such as full bright white, or start strobing, or start fade to dark, or set all palette to red, or whatever I can setup as a remote JSON command this would allow one button to do that. Why would you call it abuse?
If this JSON command would be invalid, or unable to do in a preset, could we make a button ‘run a command’ instead of just call a preset. I am not faulting how it works now, I am just suggesting an improvement.
I have a wizmote and I was wondering if we can change what some of the 13 buttons do. As an example I would like to abuse the nitelite(moon) button for something else specifically. Perhaps run a JSON command set again. I would prefer the button option, but think both as solutions would give most functionality for all.
I cannot locate the how to redirect the wizmote command in the documentation. Any chance to explain here?
Still wondering if the API command in preset is illegal or impossible. I have many devices that all have ‘very different’ segment configurations and where the ability to change colors, effects, and more to match the master is good, I am looking to have presets on multiple devices all get triggered by presets on any device that has a button and preset with API commands to SEND the ‘change other devices’ signal. I have seen others request this here before, but I do not think anyone is seeing the power this then provides.
Thank you again for your attention and assistance. I am planning soon to share my many device situation in a video. I now have four ESP32 WLED running and I am about to make two more.
this part
" The function numbers assigned to each button can be changed in the buttons.ino file where I added some examples. WLED supports the standard WiZ-mote codes by default, however those are highly limited in use. You can add a remote.json file to WLED using a web-browser (wled-ip/edit) to assign any supported JSON-API command to any button function.
Triggering a preset using the command {"ps":5} to trigger preset 5 for example and adding the JSON-commands in the WLED web UI allows for easier adjustments than editing the remote.json file as that requires an active internet connection for the editor."
If I am reading this correctly you need additional hardware running for what you are suggesting. Is it possible to (within WLED) reassign the remote functions for the Wiz-mote? I have done the IR custom remote settings by changing ir.json, and I am hoping that it could be like that. When wiz-mote button1 is seen do this.
Sorry this went off topic. I am now running WLED version 15 now and I see that API commands are eligible from presets. I tested brightness and I am thrilled to report that does work, kinda. I moved on to asking another WLED device to change preset and that did not work.
Where I said that the brightness kinda worked needs some explanation. In both of the attempted examples above the request happened locally on the device, device1, that was submitting it. I was not expecting that to happen on that local device.
192.168.12.12/win&A=20
Resulted in both devices brightness being set to 20.
192.168.12.12/win&PL=45
Resulted in device1, sending device, changed to preset 45, but device2 did not change.
Feels like it should work and I would only expect it to execute on the local device if there was not an address that it was sending to like the following example.