What is best way to detect event stopping by computer reboot

[cowinger]

Can anyone help with an event (not sure I can use event) or a script that would detect an event being interrupted by the computer being re-booted?
During a watering cycle last night somehow the computer was re-booted in the middle of it and of course it never finished. It had to be MSoft even though I have set the time for updates in the AM!

Is there a way to know if this happens? thanks

[Michael McSharry]

The application/plugin/script that is running needs to have logic that can detect its state at time of startup and know if it should continue at some point. mcsSprinklers records it state every minute for situations like this and any other unexpected event.

[randy]

Can anyone help with an event (not sure I can use event) or a script that would detect an event being interrupted by the computer being re-booted?
During a watering cycle last night somehow the computer was re-booted in the middle of it and of course it never finished. It had to be MSoft even though I have set the time for updates in the AM!

Is there a way to know if this happens? thanks

The only way I know of is to trigger an event when the system starts up through your startup script. That is the only time HomeSeer can execute actions. I have these lines in my startup script:

hs.triggerevent("StartupCleanup") this runs an event immediately
hs.DelayTrigger (60, "StartupCleanupDelayed") this runs an Event with a delay

These two lines call Events named "StartupCleanup" and "StartupCleanupDelayed". A single Event is all that is needed, but I chose to do it in two with a 60 second delay before launching the second. The first event does a couple of actions, starts my uptime timer and optionally sends me a pushover message. I have this message disabled for now.


The second one is delayed by 60 seconds to give the system time for everything to get running then it takes care of getting everything synchronized with the time, sets virtual devices, polls Z-Wave devices, various other tasks and sends a Pushover message. You could also send an email or SMS message.

You could either act on the system manually when you get the message, or you could have HomeSeer perform some action at startup that would stop your sprinkler program.



I also have a shutdown script that will execute when I ask for an orderly shutdown, but I found it only runs when I shutdown HomeSeer. Obviously on a disorderly shutdown (power or hardware failure) will not run it. This event could also send a Pushover (or email) notification.

[cowinger]

The application/plugin/script that is running needs to have logic that can detect its state at time of startup and know if it should continue at some point. mcsSprinklers records it state every minute for situations like this and any other unexpected event.

Thanks Michael, I will download a trial and take a look.

[cowinger]

The only way I know of is to trigger an event when the system starts up through your startup script. That is the only time HomeSeer can execute actions. I have these lines in my startup script:

hs.triggerevent("StartupCleanup")
hs.DelayTrigger (60, "StartupCleanupDelayed")

The first event does a couple of actions, starts my uptime timer and optionally sends me a pushover message. I have this message disabled for now.

[ATTACH]69949[/ATTACH]

The second one is delayed by 60 seconds to give the system time for everything to get running then it takes care of getting everything synchronized with the time, sets virtual devices, polls Z-Wave devices, various other tasks and sends a Pushover message. You could also send an email or SMS message.

You could either act on the system manually when you get the message, or you could have HomeSeer perform some action at startup that would stop your sprinkler program.

[ATTACH]69950[/ATTACH]

I also have a shutdown script that will execute when I ask for an orderly shutdown, but I found it only runs when I shutdown HomeSeer. When it is shutdown by the O/S for an update, it hasn't run the shutdown script. This event could also send a Pushover (or email) notification.

[ATTACH]69948[/ATTACH]

Thanks Randy, I can see how this script thing might be a little above my pay grade. All of those Then statements are intimidating. I am not sure where I would start. Would I start by polling the z-wave devices? But how would HS know where the event left off and how would it continue from where it left off? Sounds complicated.

[randy]

Thanks Randy, I can see how this script thing might be a little above my pay grade. All of those Then statements are intimidating. I am not sure where I would start. Would I start by polling the z-wave devices? But how would HS know where the event left off and how would it continue from where it left off? Sounds complicated.

The script thing could simply trigger a startup event. For your use the event could simply send a message letting you know the system had restarted. Then you could manually intervene with irrigation. I don't know how your sprinkler program works. Since my irrigation schedule is offloaded to the controller, it will continue to run even when HomeSeer is stopped. For that reason I do not need to do anything on a restart. When HomeSeer runs my Irrigation Event, a virtual device is updated, so it will always "know" when it last ran.

In your original post you said "of course it never finished". What would you like to see happen. How is your irrigation controlled by HomeSeer? If you want it to continue where it left off, I'm sure you could figure a way or as Mike suggests, have a script update every minute or so as to what its status is. You could store it in a virtual device or text file.

[cowinger]

The script thing could simply trigger a startup event. For your use the event could simply send a message letting you know the system had restarted. Then you could manually intervene with irrigation. I don't know how your sprinkler program works. Since my irrigation schedule is offloaded to the controller, it will continue to run even when HomeSeer is stopped. For that reason I do not need to do anything on a restart. When HomeSeer runs my Irrigation Event, a virtual device is updated, so it will always "know" when it last ran.

In your original post you said "of course it never finished". What would you like to see happen. How is your irrigation controlled by HomeSeer? If you want it to continue where it left off, I'm sure you could figure a way or as Mike suggests, have a script update every minute or so as to what its status is. You could store it in a virtual device or text file.

I have the GoControl Sprinkler unit. It is controlled by HS through an event that turns the valves on/off. You said a script could be used to run an event that would alert me. That would work. Are there any scripts out there that I could copy that will do that? You said it could be included in the startup script in HS, right? I think I can figure out how to write the event, maybe. thanks

EDIT: Ok, so would I create like a subroutine in the start.vb file that would call an event if HS is rebooted? Then create an event called ex. HSreboot, put that name in the sub as to be called and the event would be named that and if manually triggered, then do this? Am I close?

[Uncle Michael]

I have the GoControl Sprinkler unit. It is controlled by HS through an event that turns the valves on/off. You said a script could be used to run an event that would alert me. That would work. Are there any scripts out there that I could copy that will do that? You said it could be included in the startup script in HS, right? I think I can figure out how to write the event, maybe. thanks

All you need is a single line added to your Startup.vb script. This is mine. (I cleverly named my event 'Startup Stuff'. )

    ' You may add your own commands to this script.
    ' See the scripting section of the HomeSeer help system for more information.
    ' You may access help by going to your HomeSeer website and clicking the HELP button,
    ' or by pointing your browser to the /help page of your HomeSeer system.

    hs.TriggerEvent("Startup Stuff")

[cowinger]

All you need is a single line added to your Startup.vb script. This is mine. (I cleverly named my event 'Startup Stuff'. )

    ' You may add your own commands to this script.
    ' See the scripting section of the HomeSeer help system for more information.
    ' You may access help by going to your HomeSeer website and clicking the HELP button,
    ' or by pointing your browser to the /help page of your HomeSeer system.

    hs.TriggerEvent("Startup Stuff")

Thanks Mike. I assume it doesn't matter where in the startup.vb it goes or just at the end? Now for another question. Is there a way to get the watering event to resume where it left off?

[cowinger]

GOT IT TO WORK! How do I get it to honor the conditions in the event if it is manually triggered?

[Uncle Michael]

GOT IT TO WORK! How do I get it to honor the conditions in the event if it is manually triggered?

To do that have the script run an intermediate event, which would run the target event only if the conditions are true.

[cowinger]

To do that have the script run an intermediate event, which would run the target event only if the conditions are true.

Great, thanks. I didn't think of that.

Also, is there a way to get it to resume where it left off in the watering cycle? Or does that get complicated.

One more thing, I shouldn't put a manually triggered IF statement in the second event, right?

Event A is in that script you gave me in the startup.vb file

Event A:
IF this event is manually triggered
Then if conditions are true run another event B

Event B:
IF time is within waterstopped time range
then send email
then speak
then....

[randy]

Great, thanks. I didn't think of that.

Also, is there a way to get it to resume where it left off in the watering cycle? Or does that get complicated.

One more thing, I shouldn't put a manually triggered IF statement in the second event, right?

Event A is in that script you gave me in the startup.vb file

Event A:
IF this event is manually triggered
Then if conditions are true run another event B

Event B:
IF time is within waterstopped time range
then send email
then speak
then....

Triggers are ALWAYS ignored when the Event is run manually, so it doesn't matter what the Trigger is. Thata way you can have a single Event that runs autonomously by a time or some other Trigger and you can run it manually when needed. The only reason you would need "This Event is Manually Triggered" is if you want it to ONLY be manually triggered.

You wrote "I have the GoControl Sprinkler unit. It is controlled by HS through an event that turns the valves on/off". Is this a single Event or a series of events? If it is a series of single Events that each control a valve, I'm sure we could figure out a way to have it catch up. One way would be with Power Fail recovery.

If you would describe or provide screenshots of your irrigation Events, it would help.

[cowinger]

Triggers are ALWAYS ignored when the Event is run manually, so it doesn't matter what the Trigger is. Thata way you can have a single Event that runs autonomously by a time or some other Trigger and you can run it manually when needed. The only reason you would need "This Event is Manually Triggered" is if you want it to ONLY be manually triggered.

So would my two events above be correct?

You wrote "I have the GoControl Sprinkler unit. It is controlled by HS through an event that turns the valves on/off". Is this a single Event or a series of events? If it is a series of single Events that each control a valve, I'm sure we could figure out a way to have it catch up. One way would be with Power Fail recovery.

Here is an event. It is all under one event as you can see. Would I need to separate it into individual events to get it to resume?

[cowinger]

Randy, I created separate events for the sprinklers. Do you think this would be usable to create a script that would resume the watering if the computer got rebooted?