snowjay wrote:Can't you just link the extra lights to the other switches locally?
I only want the switches to turn the lights off, not on.
These are the kitchen lights. We have under cabinet counter lights, and overhead lights. Under normal circumstances, the counter lights provide enough lights. The overhead ones are glary but are useful if you're working in there. So the switches switch the counter lights on normally. A double tap on switches on the overheads as well. I use a server action for that. I want the off to switch off all the lights with one touch, so I added the server action as well.
Even if the overheads were put into the normal on/off group, it'd still be sending lots of individual commands to lots of different switches. (Unless the switches are more intelligent than I'm giving them credit for and already use a scene/group command to do this.) If each switch just sent a group on/off command it seems it'd be a lot more efficient.
Or create one group/scene that controls all the switches and lights. Then create 8 trigger actions (two for each switch - on & off) that watch for the status change of each switch and then call that group/scene with either the on or off command.
The other thing I want to do is have the lights work in the absence of the server. I don't want the lights to stop working if we have server trouble. The idea of just triggering server actions is attractive, but then subject to a single point of failure which seems like a bad idea.
So I've programmed the switches for basic operation, supplemented with server actions. I'd like to stick with that idea. Currently, if the server goes down, the counter lights will still work, just the double tap on won't work, and the all off won't work with a single tap.
The alternative to that is can you link a device just to the on or the off of a switch? As far as I can see, devices only respond to on/off, not individually to on and off.