Hi, I wouldn't go so far as to say this is expected behaviour (well it is expected in as much as the code is doing what it ought to), but if you think a little about wee_reports I think the result is logical. wee_reports is a standalone utility that runs a weewx report cycle as per the [StdReport] stanza in weewx.conf. wee_reports has no idea whether weewx is running or not; sure wee_reports uses a pile of weewx API calls but it doesn't interact with any running instances of weewx. So as far as wee_reports is concerned the concept of how long weewx has been running for is meaningless, and in fact wee_reports does not even have the 'knowledge' to work it out. So in looking at wee_reports in that context, the fact that it returns '0 days, 0 hours, 0 seconds' makes sense (well it actually returns None but the weewx formatting applied means it is displayed as 0 days, 0 hours, 0 seconds).
Gary On Monday, 31 October 2016 13:43:56 UTC+10, erbenton07 wrote: > > I've seen this again since I posted, but this time I paid more attention. > It only happens if you use wee_reports to get a fast update. 'systemctl > reload weewx' doesn't alter the time displayed but wee_reports generates an > uptime of 0. After the next normal iteration of weewx update generation the > time reverts back to normal values. Probably wee_reports isnt generating an > uptime value? Anyway - its minor. > -- 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]. For more options, visit https://groups.google.com/d/optout.
