I am trying to assign one button on one of my leviton 4-scene controllers to a vacation mode. I’ve done this by setting up a virtual sensor called Vacation that can be tripped or untripped by the button on the scene controller. Additionally, I set up a scene to untrip the Vacation sensor if I enter the correct pin on my schlage lock coming in the house. I can set Vacation mode by pushing the button, and unset it by entering the correct pin at the door just fine.
The problem I am having is getting the LED to turn off at the 4-scene controller, if I turn off the vacation mode from schlage keypad. Any thoughts? I know I can assign a real dummy device, like the internal switch on the controller, but I don’t want to go that route, because I am already using it as a dummy for another purpose.
I believe Leviton uses a semi-proprietary HAIL feature to update controller’s state (LED). Not sure how to control it from Vera… MCV has recently mentioned they made agreement with Leviton and promised to implement all their proprietary features in the future. Whether this will be supported or not, I don’t know.
Thanks for the info, denix… let’s cross our fingers, doubtfully…
Well, I resorted to using the local switch as a dummy device, but I’m struggling with it. I tried just associating button 1 (group 1) with the local switch, and nothing else. I can manually activate and deactivate button 1 to turn on and off the local switch respectively. However, if I activate the local switch manually by hitting button 1, and then turn off the local switch through vera, the led stays on. Similarly, if the led is off, and i turn on the local switch through vera, the led doesn’t come on. Is the local switch not “scene-capable”? Am I doing something wrong?
One thing to note, I have an “entertain” scene set up on another button, and it sets dim levels on all the dimmers through the house and turns on the binary light at the front porch. If I activate the scene at the keypad, then adjust one of the dimmed lights at it’s local dimmer, the led turns off. But if I activate the scene at the keypad, then turn off the binary front porch light, the led stays on… makes me think that leviton binary switches aren’t considered scene-capable by the scene controller…
Just to clarify, the only way to turn off the LED of a 4-scene controller is to physically press the button again to deactivate the scene which in turn shuts off the LED. Am I understanding this correctly?
Jeffy… additionally, if you adjust any scene-capable devices (i.e. vizia rf dimmers) included in a scene assigned to a button on the 4-scene, it will turn off the led.
As mentioned on several other threads, MCV has worked out a deal with Leviton to share information about their devices. The fruits of this should make it into Vera in the next couple of months. It was not clear what functionality would be added, but it is possible that controlling those LEDs is among the features.
@mikeholczer, just 4 posts above… 
I’ll be impressed if they add LED control support. My guess is support for ramp rate on dimmers will be the biggest addition - which is great… I can’t wait for that support…
@woodsby, LED on/off on a scene controller would be nice. But I’m not sure adjusting ramp rates on dimmers is so hot feature, when it can be done locally:
http://forum.micasaverde.com/index.php?topic=3149.msg13611#msg13611
Denix, I read that post the other day. I didn’t want to try reprogamming my newer vizia dimmers since those instructions seem awfully similar to resetting the switch. Can anyone confirm if this works on the new vizia rf dimmers?
As for setting ramp rates… I’m not looking to set them one time… I’m looking to do it on a per-scene basis. For example, I want the bedroom lamps to fade to black over 30 seconds when going to bed, but turn right off when leaving the house. This is a pretty common feature in most lighting control solutions, and as I mentioned, is available in ThinkEssentials.
Why do you care how long it takes to turn the lights off when you aren’t in the house? You could always do a Luup Scene to send commands to dim the lights slowly.
Haha, I guess I don’t care how long it takes the lights to turn off when I leave the house… a better example would be the one I mentioned in the other thread about this subject - where I’d like a couple of dimmers to flash on and off for an emergency scene without having them fade up and down…
Anyway, the point i was trying to make is the vizia dimmers already support ramp rate functionality, and it would be more likely, if MCV and Leviton started talking, that would be one of the first functions supported… just speculating though…
FYI, it appears that these dimmers support a ramp rate range of 0 seconds to about 3 minutes…
Back to the topic of the thread - I tried something today and found yet another problem. I tried setting up a scene based on a button on one of the 4-scene controllers - if scene 4 is activated, it trips a virtual luup sensor. I set up a second scene - if scene 4 is de-activated, untrip the sensor. When I push button 4, it trips the sensor just fine - and the button led comes on. When I hit button 4 a second time, the led goes off, but the sensor doesn’t untrip.
I get the feeling that the “A Scene is De-activated” isn’t supported by these scene controllers. Anyone have any experience with this?
I was not able to get “A Scene is De-activated” to work either. However, I have a simple scene that turns on one light. If I press the button again, it will turn the light off, but only because it is a scene capable switch and does not even require a separate scene in Vera to turn the light off. This is not the case with my appliance module that is not scene capable.
It appears that when you de-activate any scene, it’s actually seen as activating scene 0 (sl_SceneActivated variable). I wonder if there’s a way to get the sl_SceneDeactivated variable to work - I could have sworn I was messing around with that variable a few weeks ago…