What Does "Command only switches that are [on|off]" Accomplish?

The basic explanation is obvious, but what are practical uses in the real world? Is it just a hub processing and/or network traffic saver, or does it change something else in the background?

I'm trying to figure out if I need it or not. It seems to me that -ignoring the aforementioned potential bandwidth issues- I'm better served by leaving that function unused, and in the one-in-a-million chance I have a device status out of sync, the rule running will still cycle the device as I intend. Perhaps it's a consideration that all my rules are clear cut 'turn off [device] that is already on,' so I wouldn't need this as an additional logic tool. (Or, on the off-chance that something is already as I desire, I don't care if a rule send the device an additional command.)


As far as I know, it will only help release network traffic.


It's intent is more for when you are turning off/on multiple lights in a situation like a Good Night Routine that would turn off 10-15 lights but only 3-4 might be on. If all of your rules are only changing 1 or 2 devices, then it isn't necessary.


FWIW, I leave that option off most of the time. Especially if you are only turning one or two things on or off. I've had lights that the hub thought were already off but wern't. In that case the rule wouldn't turn them off.

1 Like