Still having a routine failure with a simple scene function.
I have three outside lights set to come on 30 minutes after sunset (thanks MCV for adding this function). Command then turns two of them off 4 hours and this works consistently. Third has command to turn off after 7 hours and this always fails. Just a random guess, but I am wondering if vera is not complete the tasks in the scene because the OFF occurs on the next day. Vera is not dead in the morning like it was before upgrades.
Similar.
One lamp module / dimmer that is commanded on by a scene will not turn off after 4 hours as configured. Also, does not seem to turn off by a different scene set to turn all lights off before morning. Works fine when commanded manually from vera.
Can you please go to Advanced, Logs, check ‘verbose logging’ before the scene starts (click save), and then after it fails after the 7 hour thing, go to advanced tech support and submit a trouble ticket? Put ‘for aaron’ in the comments.
all three lights in my NIGHT scene turned ON at 30 minutes after SUNSET and failed to turn OFF. i was thinking only one of the lights that has a 7 rather than 4 hour delay routinely failed to turn off. as per MCV request i submitted a trouble ticket - # 1160.
I looked through your logs. First comment is that for really long delays, like you have with a 7 hour delay, it’s better to create 2 timers (one at night, the other in the morning), rather than a ‘do something at 11pm’ and then ‘after 7 hours’ ‘do something else’. When you have 1 scene and 1 timer that does something and then “after x hours” does something else, we call that a delayed timer. As opposed to dual timers.
It should work the way you created it with delayed timers, but, when the timer runs at 11pm if anything happens between 11pm and 7am that causes Vera to restart abnormally, you’ll lose the ‘after 7 hours’ part because delayed timers aren’t stored in the database. Rather the ‘pending’ part is stored in memory, and gets lost if there’s a power failure, etc. With dual timers this isn’t an issue because both timers are stored in the database. So if you had another timer that ran at 6am, it would always work.
Vera has some ‘watchdog’ programs that check that CPU load is OK, memory usage is OK, that the main application (the Luup engine) is responding fast, like it should, and that there are no other errors. If there is an error, the watchdog kills the Luup engine and restarts it, which means the delayed timers get lost, but the dual timers still work. Your Luup engine was reset at approx 3am. This is a bug in our code somewhere. Since verbose logging wasn’t enabled, I can’t tell exactly what happened. Only that Vera was polling your ‘Courtyard light’ at 3am, got back a bad response that we didn’t know how to handle, and this caused an error condition which reset the Luup engine. I’ll take a copy of your database and run it in a stress test on our box to see if I can reproduce the exact circumstances. But, in the meantime, you might want to consider dual timers since that’s safer when you’re on a “beta” software release.
Using dual timer approach is a better idea. I had not considered this but it should at least allow me to get my outside lights on schedule.
I am almost certain that verbose logging was checked. I only recently disabled verbose logging to see if that would decrease lockups. I will let the failure occur again tonight after selecting verbose logging on the off chance that it may help.
Best Home Automation shopping experience. Shop at Ezlo!