If it’s truly a switch, then I’d say it will always switch the local load, and if it supports instant status (or Vera can ‘fake it’), you can reasonably quickly trigger an event off of the changed state of the switch (instead of having to wait for the next poll of the switch).
If the device is (also) a scene controller, it may be able to separate the button from the switch. One example that comes to mind is the Leviton VRCS2.
Thanks. That will always control the local load, and you may get something resembling instant status; so not the best trigger for a scene.
There are some prior topics on this. (In short: you may be able to successfully trigger scenes if the device is close to Vera and you operate it either locally or through Vera. If it’s too far from Vera, or you have it in a wired multi-way setup, or some secondary controller changing its state, the scene may not fire for quite some time.)
When lampOutlet OFF & fanSwitch OFF:
if fanSwitch is turnedON, turn lampOutlet ON and immediately turn fanSwitch OFF [outcome: only lamp is on]
when lampOutlet ON & fanSwitch OFF:
if fanSwitch is turnedON, leave lampOutlet alone, and turn fanSwitch ON, and stay ON. [outcome: both lamp and fan are on]
when lampOulet ON & fanSwitch ON:
if fanSwitch is turned OFF, turn lampOutlet OFF, and immediately turn fanSwitch back ON. [outcome: only fan is on]
when lampOutlet OFF & fanSwitch ON:
if fanswitch is turned OFF, turn OFF and leave OFF [outcome: both are off]
the 1 second delay of the fan being on doesn’t bother me TOO much. assuming the light kit is turned off on the fan (or one just doesn’t exist)… the user may here the buzz right before the motor starts, and even see a partial spin, but so what. far more convenient that turning the switch on and walking over to play with the switches.
edited rule 3 and 4 there was a bug in my psuedo code.