Survive a reboot

[lalisingh]

Forgive me if this has been answered.

How fo you have a timer state survive a reboot.

[matt (support)]

I don't believe there is a good/simple solution to this. Currently upon server startup all device Timers are reset to the inactive state. I'll talk to Jay and we'll consider adding a device level property, like "Preserve timer status across restarts", that let's the user specify at the device level what behavior they want.

[lalisingh]

Thanks Matt,

Managing occupancy triggers is my crtical use case for timers. Having the timers survive a power flicker is important.

Workaaround is using variables ofcourse.

[FlyingDiver]

Thanks Matt,

Managing occupancy triggers is my crtical use case for timers. Having the timers survive a power flicker is important.

Workaaround is using variables ofcourse.

A better workaround is to put the Indigo server on a UPS.

[kw123]

In pibeacon plugin nothing gets set to off in the first 90 seconds after start of plugin.

That should cover any restart reboot timing issues.

Karl


Sent from my iPhone using Tapatalk

[Vaillant]

Has this ever been resolved?

On restart Timers are reset to the inactive state.
This triggers a few actions for me.
Problem is that the external plugins are not loaded yet so I get errors.

I prevent the errors using Event Timer Expired in my triggers.
However I do somehow want to trigger my actions when the external plugins are loaded and set to inactive.

So: Timer Test Active > Restart > Trigger Timer Test > Execute Action External Plugin

Adrian

[jay (support)]

We haven't done any work on this. TBH, the priority is quite low compared to many other things.

[whmoorejr]

One thing I love about indigo.... there is a way to do everything any anything.

First, i'll +1 on the UPS comment. That will close the gap on any power flickers. Aside from that...

It sounds like the trick is knowing the state of each device prior to a power outage. You may be able to get close.

Step one:
A couple variables for each timer device that are updated with the timer state and timestamp of the statechange.

Step two:
"Indigo Server Startup" trigger. When fired, it does three things:
1) Set a variable, "Server_Startup" to "true"

(all your other triggers you will need to add the condition, "Server_Startup" = "false" )

2) Use the data from the variables in step one to put all the timer devices into the correct state. The documentation on this plugin is good enough, you should be able to get them going with a script. Use datetime python math to get new timer start times, set device states, etc.

now all the devices should be back in sync with where they should be.

3) delay action on the same trigger to change the variable, "Server_Startup" to "false"

Something like that (depending on your case use), might get you in the ball park.

[kw123]

The sql plugin stores that info for each dev/state and variable.

And the plugin utilities supports an action that triggers after indigo start and and an action that triggers at indigo shutdown

Karl.
Sent from my iPhone using Tapatalk