I recently transitioned from my Vera Lite (UI5) to a Vera Edge (UI7). I have noticed that, in general, devices are much slower to respond on the Vera Edge than they were on my Vera Lite. For example, I have scenes that are motion triggered. There is a longer delay on the Vera Edge from the time motion is detected to the time the device is turned on. The issue is easiest to see when I trigger a scene that has 4 devices. With my Vera Lite, the same scene would turn on all of the devices essentially at the same time (nearly instantaneously). With my Vera Edge, some of the devices take multiple seconds to turn on. Overall, things are noticeably slower on the Vera Edge. I suspect this isn’t due to the Vera Edge itself, but some issue with my zwave network configuration. I tried running a “heal” but that didn’t improve things.
I have included the logs generated when I turn on a single device (device #67) from the web UI. As you can see, it takes several seconds for the device to turn on. Any suggestions? What else can I do to troubleshoot this?
Edit: It is probably also worth noting that all of my devices have five stars in my heal report. Almost all of my devices are leviton switches.
Be sure to include your Vera unit serial number and the tech support access code. You can enable it by going to Settings > Tech Support and then clicking on the Enable button at the bottom of the page.We’ll look into it right away and get back to you shortly.
Be sure to include your Vera unit serial number and the tech support access code. You can enable it by going to Settings > Tech Support and then clicking on the Enable button at the bottom of the page.We’ll look into it right away and get back to you shortly.
Thanks.[/quote]
George-
Thanks, but I think I have this figured out. I disabled the energy (ergy?) plugin (which wasn’t working anyway) and also disabled verbose logging. Now things are responding as expected. Is this a known issue? I don’t feel like taking the time to experiment to confirm which of these items was causing the issue, but I don’t recall having this issue with verbose logging on my veralite so I suspect it was an issue with the energy plugin.