Im using Pi 3B+, currently an external timer powers up the pi for 5
minutes, sufficient to wait for the NTP server, and start weewx to download
the console and upload to wu. But if I miss a couple of days then there's
too much data, and 5 minutes isn't enough, something smarter should be done.
As you were saying, I'm getting an RTC to start periodically my weewx, but
I need another process to shut it down. Will try to understand your
proposal.
On Sunday 23 June 2024 at 15:10:05 UTC-3 vince wrote:
Wow - very interesting setup. A lot of questions come to mind:
- what model pi are you running ?
- have you stripped the os down to the bare minimum number of processes
running ?
- have you stripped down the services weewx runs to the minimum ?
- what is the power savings you measure by killing weewx ?
- do any of those changes have measurable impact on power consumption ?
For a pi-only software solution I'd just use bash and cron periodically:
- check if weewx is running or not
- if not, start weewx up and await it running the WU upload after the
first archive period
- watch the weewx log to see if the WU upload has logged that it has
completed its upload. You could do this with a custom rsyslog.conf entry
and log only WU stuff to a particular file
- when the WU log is populated, rotate that logfile (for the next run)
and kill weewx and exit
- (and use cron to periodically start the script of course)
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/aae0aaca-94c6-4fab-974d-c30bc2272f46n%40googlegroups.com.
