Vera scene delay feature - not always working

Community Playground General Discussions
1

Hi guys. I built a very basic scene to turn my thermostat on, wait for 4 hours, and then turn it off. Very basic and I’m using the Vera in-built scene delay feature - no LUA. I’m finding that the scene always activates and turns the thermostat on as expected but only turns it off maybe 50% of the time and I can’t understand why.

Is a 4 hour delay too long for Vera to act reliably? Am I better off trying to use luup.call_delay(…) feature instead?

Thanks.

2

A scene delay of four hours is not likely to be very reliable. If Vera restarts (Luup Reload) during the period, the delayed action will not happen. This is the same whether you use the scene’s delayed actions or a luup.call_delay(…) function.

It would be more reliable to have a second scene triggered by a separate schedule.

The best solution would be to use PLEG. This is designed to restart its running Schedules/Timers after a Luup Reload. See PLEG Basics for an introduction.

3

Thanks for the reply. I agree a second scene would be best and not disputing anything you’re saying but I am 100% confident a luup reload or restart is not occurring and not the cause to my particular issue. There’s clearly better ways to tackle my problem but I suppose I’m just surprised this isn’t working as it should.

Thanks again.

4

Can somebody confirm that a luup reload would cause a delayed scene failure even in the most recent firmware?

5

I will confirm luup reloads are the heart of the problem.

Luup reloads are triggered when user data changes.

You should note a timesamp of the failed scene and determine in vera logs if the reload occurred during that time.

On average I notice on my system the reload is about 13 seconds. Pleg is the correct solution until vera integrates their own check for it.