Re: [weewx-development] Aggregated Values in MQTT Output

So I hope the topic of intervals is settled with Tom's post. Let us then go back to the original topic of this thread: - to make MQTT use the standard kind of intervals even for dayRain and - to provide a means to send aggregated values by MQTT. That is the goal of the PR #31

Re: [weewx-development] Aggregated Values in MQTT Output

In WeeWX, intervals are consistently open on the left, closed on the right. That means that the first archive interval of the day runs from a split second after and ends precisely at 0005. A temperature timestamped at will be included in the previous day's statistics. Same with rain: rain

Re: [weewx-development] Aggregated Values in MQTT Output

Karen K writes: > The general way of WeeWX is to think of an archive interval to be open at > the left end and closed at the right end. This is because it records the > readings of the last 5 minutes. Thanks; I was unclear on that and (] seems sensible. > Actually if you show yesterday rain

Re: [weewx-development] Aggregated Values in MQTT Output

May be I should give an additional example regarding rain. And this is the reason people were aware of that detail: Actually if you show yesterday rain ($yesterday.rain.sum) and today rain ( dayRain) then the rain between 23:55 and 00:00 ist included in the yesterday rain as well as in the today

Re: [weewx-development] Aggregated Values in MQTT Output

Karen K writes: > There is a comment in restx.py saying: > > # NB: The WU considers the archive with time stamp 00:00 > # (midnight) as (wrongly) belonging to the current day > # (instead of the previous day). But, it's their site, >