You still don't know the problem, but state, there is no such.

I can think of one: 1-3W x 24h = 25 - 72Wh is quite another category of a 
problem to solve, without a grid backed power source, than 5-6 x 5 min x 
1-3W = 0.42 - 1.5Wh would be. One LiFePO4 18650 battery holds about 6Wh, so 
the difference between "always on" and "turning on only when needed" is one 
vs. 24 such batteries for the same running time. Now that's what I call a 
use case. Still, without knowing the problem, my idea of a use case isn't 
any better in terms of a possible solution than stating, that there isn't 
even a problem to solve.

vince schrieb am Donnerstag, 20. Juni 2024 um 19:37:08 UTC+2:

> Here's the problem...
>
>    - shutting weewx down does nothing to save power
>    - shutting the pi down saves 'almost' nothing because it draws so 
>    little
>    - the WLL is still on and using power to act as a datalogger in the 
>    interim
>    - and internet connectivity requires 'some' hardware powered on as well
>    - and any hardware solution will cost more than you'd save in power in 
>    3+ years probably
>
> So I'm not seeing any use case making any sense at all here to even bother 
> trying to over-optimize the 1-3W a pi draws.
>
> On Thursday, June 20, 2024 at 10:20:54 AM UTC-7 Greg Troxel wrote:
>
>> Indeed the real goal is important. 
>>
>> I can certainly see having weewx have some kind of status output (a MIB 
>> :) that indicates whether it has successfully processed all the archive 
>> records and written the database (and run reports), so that a supervisor 
>> process can shut it down. 
>>
>> I do not see most people wanting to spend time on that, so the OP has 
>> some code to write. 
>>
>>

-- 
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/61082e50-4ec8-4055-abca-632b8e5b2239n%40googlegroups.com.

Reply via email to