Cumulus Support

1st.. EXCELLENT job being able to backtrack and grab the missing data when Mx is stopped and restarted the next day with the Ecowitt stations. Good stuff.

But I Just noticed, my fault, I shut the laptop down this morning without exiting Cumulus and it didnt pick up the data after that and I noticed it was "still running" when I opened up the PC.

Just curious if there is a way to make it shut down when the PC goes to sleep or shuts down without physically entering Control-C? Or find a way to realize the PC woke up and grab the missing data?

Stop CumulusMX, restore from either a daily backup or a previous startup backup (both available in the backup folder) and restart and down will come the history.

Maybe....

I have a little script that sends Ctrl-C to the MX window to shut it down.
I use it in Task Scheduler to Close MX at certain times for backups etc, then start it with another Task.

viewtopic.php?f=40&t=18950&p=150417&hil ... wn#p150417

Task Scheduler can also be configured to run tasks based on Events logged in the Event Log.
In the case of Windows Sleeping Event ID 42 is written.

Not sure what the implication of triggering a task of that is though, as it's a bit of a Chicken & Egg situation.

"I'm going to Sleep, but I'm doing a Task first" which could trigger wake-up.

Will try & have a play with it later & see if it can be done.

Cheers.

water01 wrote: ↑Thu 10 Feb 2022 8:25 pm Stop CumulusMX, restore from either a daily backup or a previous startup backup (both available in the backup folder) and restart and down will come the history.

Great idea. Just did that (maybe wrong) and the chart is still showing missing data as well as the Feb22 log.

Phil23 wrote: ↑Thu 10 Feb 2022 8:30 pm Maybe....

I have a little script that sends Ctrl-C to the MX window to shut it down.
I use it in Task Scheduler to Close MX at certain times for backups etc, then start it with another Task.

viewtopic.php?f=40&t=18950&p=150417&hil ... wn#p150417

Task Scheduler can also be configured to run tasks based on Events logged in the Event Log.
In the case of Windows Sleeping Event ID 42 is written.

Not sure what the implication of triggering a task of that is though, as it's a bit of a Chicken & Egg situation.

"I'm going to Sleep, but I'm doing a Task first" which could trigger wake-up.

Will try & have a play with it later & see if it can be done.

Cheers.

Interesting! Keep us posted.

As 1/2 expected Event 42 is already too late....

Event 107 is logged on resume, so maybe it's an option...

If you run Cumulus as a service then the windows system will automatically stop the service when performing a shutdown or if the computer goes into standby. The service will automatically start again when you boot the computer and catch-up on historical data, however, it won't after coming out of standby (the preference is to never let your computer go to sleep when running Cumulus). There is a task script included in the distribution package in the CumulusMX\MXutils\windows directory to create a Scheduled Task to automatically restart the service on resume from standby/hibernate.

I use to run Cumulus on a Windows system and never had any issues while running it as a service (although I could never get the scheduled task to work on wake-up).

..