Had the same issue with the “let vera mange lights” option and unchecked it the “Scenes” tab of the controller.
I added the scene controller button (scene 1 or 2) in the advanced tab to turn the light on (1) or light off (0).
Edit: Split off from this topic.
@AgileHumor - I’m confused. Are you saying that you tried the method laid out by @sgruby and it works? Are you further saying that the Leviton switch does not become unstable after you operate the loads directly from Vera’s GUI?
In my previous testing all was well, until I operated the loads from Vera’s GUI. At that point the LEDs failed to update and the switch became unstable.
Well, I don’t know if it was unstable. It just wasn’t predictable and needed the double tap 1/3 of the time to turn off the light…until I went to manual lighting mode.
I’m still confused. What do you mean by “manual lighting mode”? Are you using the method laid out by @sgruby?
No, I’m sorry I was giving you how I had it setup reliably and with low latency.
Default: VRCS2 is in default mode. Load turns on and off with no delay. This is ereased never to return once you include it with Vera. The only way to return to this is to reset it IME, YMMV.
After Inclusion: You must use scenes and MANUAL 'set light" scene controller mode to make it snappy. You must include it within 3ft of Vera or you won’t get the 2 appliance modules (individual load switches) even though you get the scene controller over longer distances.
I’m not using associations. There is no delay in using scenes in this setup.
Video:
http://sdrv.ms/1gMHUgb
I think I understand now. Sorry for being thick.
If I’m not mistaken, what you are saying is that you used this configuration method. To great success. This is the method that has given me the most success so far, as well. But I still see a longer delay than your video for updating the LEDs. My loads react as fast as yours, but the LEDs are not as quick. But that may be due to different routing distances between yours and mine.
You you used a different technique, perhaps you’d be kind enough to do a detailed instruction write up for us. Your video certainly shows the behavior as it should be and as I would like it to be.
I read your posts to mean that you included it the standard way, set it up with scenes the standard way, but your only change was to disable Vera having control of the LEDs (on the [tt]Scenes[/tt] tab of the controller).
Do the LEDs update when you control the loads from Vera?
I’ve gotten some screenshots attached.
Once included, you should start with 3 devices:
You also should have 4 scenes:
@OTI, I would only run the SCENES…Not the Device. If you need a device, you may need a virtual switch and triggers (device virtual switch 1 on fires scene button 1 on) if you want the LED’s in sync.
Thanks for the clarification.
Ah! To turn the LED for that button on or off.
I just tested @AgileHumor’s method and it is my fastest configuration yet. My LEDs are still slower to respond than what he shows in his video, but it is plenty fast enough and I have no complaints.
THANKS @AgileHumor!
How much faster would you say it is, compared to letting Vera auto-update the LEDs?
(Personally, I don’t mind the short delay, as I don’t normally toggle switches that quickly.)
@AgileHumor,
I put this on a separate thread (with a reference to where it came from in the initial post).
Have a look at AgileHumor’s video. My present response time is a few milliseconds slower that the video. But, it responds much more consistently.
My previous various configuration attempts of this controller were always at least 500 milliseconds slower than this to update the LED, and some days(suboptimal routes) it might pause for a second or two. Repeated cycling of the switch could also cause a several second blocking state. With this new configuration, I am able to cycle On/Off as often as I like and I have yet(after only two days) to see a blocking state of more than 500 milliseconds.
The only downside with this configuration, for me, is the total dependence on Vera. I strive to make as much as possible independent of Vera.
My Vera is only about 20 ft away, so it may be quicker as I have no hops.
What is your autoroute in the advanced tab of the scene controller?
Mine is:
0-9,26-13,37-15,32-15
This means it will try this route first:
0=Direct to Vera Node # (no relay through other nodes)
9=Signal Strength
If the first router direct route fails (0-9), it will then move to 26-13 and try to relay through node #26 which has a signal strength of 13.
PS - ‘Signal strength’ is the non-techie term for ‘metric’ or ‘route cost’.
@AgileHumor - I understand the routing. My VRCS2 is one hop away and when I allow Vera to recalculate the routing(heals) it doesn’t always choose the best one. For this reason, this switch has been assigned a manual route that is indeed the optimal route.
Using your configuration method for the VRCS2 my LEDs now update very quickly, though still a couple of milliseconds slower than your zero-hop setup and video. Even so, it is now not more than one second to do a complete cycle On/update/Off/update. I’m very pleased with this.
I stated in the previous post that this configuration was dependent on Vera. But I have found that the local loads are not dependent on Vera. The local loads continue to work, even with Vera turned off. This is great! The other devices in the scene, which now lack associations, do not work without Vera, naturally.
Of the two or three previous configuration methods I have tried in the past, this one is by far the best.
Really, so it works with the Vera off? Does the scene light still work too?
I’m assuming you have “Use Vera Routing turned off”?
PS - I assumed you knew the details of Z-Wave routing based on the username 
Just trying to help the next person whom didn’t know how the routing worked.
My local load switches and my scene light changes, with Vera off! I didn’t expect that, but I’m very glad for it.
I'm assuming you have "Use Vera Routing turned off"?No. "Use Vera routing" is checked. I generally have better results with this and I prefer to maintain defaults whenever possible. However, due to Vera automatically choosing a flaky route over the optimal one, I have a manual route set on the VRCS2 that overrides the autoroutes. Wrench -> Device Options -> Manual Z-Wave route or Wrench -> Advanced Settings -> manual route
I’ll need to test that when I get home. That’s pretty neat Vera can translate that to a local “program” and run independently.
Did you by any chance power-cycle the VRCS2 after Vera was off?
Did you by any chance power-cycle the VRCS2 after Vera was off?[/quote]
After your post I:
Powered off Vera.
Cycled the breaker for the VRCS2.
Pressed a button on the VRCS2.
Results: The local load turns on and the LED indicator comes on immediately. Three to four seconds later, the LED blinks Off and On three or four times and then remains on. Pushing the bitton again, the local load turns off immediately and the LED turns off within a second or so. The switch, LEDs, and local loads, continue to operate normally with the additional LED blinking.
Powering the Vera back on, everything operates as described in previous posts.
OK. And continue in that state by powering off Vera again, then try the buttons on the VRCS2. Do the LEDs update?
Best Home Automation shopping experience. Shop at Ezlo!
© 2026 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules