616 Timer Issues

Community Playground General Discussions
1

Ahhh Vera, why can’t we get any update without introducing new problems. Very annoying :-\

616 now have timer issues, and my lights do no shut off consistently when scene is supposed to again. It appears that Vera cannot poll many of the nodes on my network.

2

Chimpware, I don’t think that this is caused by a change in 616. 616 is the same as 602, but with a few bug fixes that don’t have anything to do with timers. There are no known issues with timers. If you turn on Verbose logging (Advanced, Logs) and then submit a trouble ticket after a timer fails to go off, indicating which timer you expected to go off, we can tell you exactly why it didn’t. Note that Verbose Logging only stays on for 24 hours. If you want it to stay on longer to catch the problem, check ‘Lock log levels’ to lock verbose logging on indefinitely. Just remember to uncheck it once you’ve reported the timer issue otherwise your Vera will continue to use a ton of bandwidth archiving big log files on our server every couple minutes.

3

I just commented elsewhere that one of my scenes, which turns a lamp ON in response to the door being unlocked, fails (consistently) to “go back to prior setting” after the “2 minutes” wait time in the scene’s “Command”.

Instead, the lamp, which was ‘Off’ prior to scene, comes on and remains on forever after the scene runs.

I’m using firmware revision .616, also. Should I do a verbose log and submit?

This is 100% repeatable in my case.

4

Update:

I submitted verbose logging of this issue with original scene.

However, I then updated the scene, so that instead of “after 2 minutes” “go back to the prior setting”, it now reads:

“after 2 minutes” “off”

That works! However, it’s not the behavior I really want. :-
Just wanted to share this update with everyone.