Hey @Thorn thanks so much for this deeper dive into finding a solution!
So I tried what you suggested (I went with the ‘reduce brightness by 1’ rest command). It worked (awesome!), but I think this solution may be problematic for my use case.
The triggers are
(1) Plex start playing
(2) Plex is paused or stopped (idle)
There’s a condition that checks if the WLED Media Cabinet (Responder) is on or off. If it’s off, no action is taken.
If the Responder is on, when Play is triggered, the Responder dims to 10%.
When Pause is triggered, the Responder should sync with whatever state the WLED Kitchen (Controller) is at (which is typically set to 20%, but not always)
Where I think I may run into an issue is, if the Controller is set to 20% brightness, over the course of a few hours of watching Plex on our Living Room TV, with each press of the Play/Pause button (which occurs a lot in our living room - kids coming in and out, etc.), the brightness of the Controller will slowly but surely start creeping down.
I bet we’ve got evenings where we pause Plex 20-30 times. This would cause the Controller to dim a lot, maybe even turn off completely at some point.
Does that make sense?
I was thinking maybe there was a rest_command that that would trigger a sync, but without actually changing any of the light settings. I looked through the list in the link you provided (HTTP Request API - WLED Project), but I didn’t see anything that I thought might do the trick. Unless, maybe “SN” (Send UDP Notifications") would do that?
What would be great is if there were some way to set something like a variable, or multiple variables, corresponding to the current state of the Controller, and then applying those variables to the responder.
Or even better, some way to just cause the Responder to resync with the Controller.
Thanks again for all of your input!