This may also apply to other accessory switches, like Evolve's LTM-5, since Evolve and Linear/2Gig/Nortek seem to source from the same factory. The accessory switch is one that does not control any load directly. Rather, you can associate it with other Z-Wave load-controlling devices to create 3-way situations, etc.
In any case, the default for the indicator is for the LED to be on when you've clicked the top part of the paddle (i.e., clicked it "on"), and off when you've clicked the bottom part of the paddle (i.e., clicked it "off"). Note that this is reverse from what the manual says (as an aside, it constantly annoys me how much inaccurate information is provided in instruction manuals).
Now, here's the fun part. There's a parameter to switch this functionality, so the LED is on when you click the paddle off, and the LED is off when you click the paddle on -- i.e., so the LED acts as a nightlight. That's all well and good.
However, when you send (such as in an event action) a Z-Wave action to turn the LED on, the way the switch responds is that it turns the LED to the state you've programmed it be in when click the *paddle* on (the top part of the paddle). So, if you've set the switch to act in nightlight mode, this actually turns the LED off. A bit confusing -- when in nightlight mode, the LED is turned *OFF* when you send an action to turn it *ON*. The reverse is true as well.
Discovered this last night. Set up events to trigger this action and do some other things, and the net effect was that I created a neat strobe effect (which my wife find funny to no end).
FWIW, here's how I use it. We have two nightstand lights in the master bedroom (plugged into GE modules). You click the accessory switch just inside the door to turn them both on (or both off). Each nightstand also has a minimote to control the lights individually. What I'm doing is that when the minimote is used to turn one light off, if the other light is off, then I send an action to the accessory switch to turn on its indicator LED (by sending an action to turn it *off*, per above). Likewise, when the minimote is used to turn one light on, if the other light is on, then I send an action to the accessory switch to turn off its indicator LED (by sending an action to turn it *on*, per above).
The idea is that the accessory switch's indicator light tracks whether both lights are on or off. If both are on, then the LED is off, and if both are off, then the LED is on. When just one of the lights is on, the indicator can be in either state.
In any case, the default for the indicator is for the LED to be on when you've clicked the top part of the paddle (i.e., clicked it "on"), and off when you've clicked the bottom part of the paddle (i.e., clicked it "off"). Note that this is reverse from what the manual says (as an aside, it constantly annoys me how much inaccurate information is provided in instruction manuals).
Now, here's the fun part. There's a parameter to switch this functionality, so the LED is on when you click the paddle off, and the LED is off when you click the paddle on -- i.e., so the LED acts as a nightlight. That's all well and good.
However, when you send (such as in an event action) a Z-Wave action to turn the LED on, the way the switch responds is that it turns the LED to the state you've programmed it be in when click the *paddle* on (the top part of the paddle). So, if you've set the switch to act in nightlight mode, this actually turns the LED off. A bit confusing -- when in nightlight mode, the LED is turned *OFF* when you send an action to turn it *ON*. The reverse is true as well.
Discovered this last night. Set up events to trigger this action and do some other things, and the net effect was that I created a neat strobe effect (which my wife find funny to no end).
FWIW, here's how I use it. We have two nightstand lights in the master bedroom (plugged into GE modules). You click the accessory switch just inside the door to turn them both on (or both off). Each nightstand also has a minimote to control the lights individually. What I'm doing is that when the minimote is used to turn one light off, if the other light is off, then I send an action to the accessory switch to turn on its indicator LED (by sending an action to turn it *off*, per above). Likewise, when the minimote is used to turn one light on, if the other light is on, then I send an action to the accessory switch to turn off its indicator LED (by sending an action to turn it *on*, per above).
The idea is that the accessory switch's indicator light tracks whether both lights are on or off. If both are on, then the LED is off, and if both are off, then the LED is on. When just one of the lights is on, the indicator can be in either state.