vince writes:
> On Sunday, November 1, 2020 at 11:09:53 AM UTC-8, T Reid wrote:
>>
>> I am running weewx and Belchertown on an older rpi 3 model B version 1.2.
>> Cheetah takes around 20 seconds to generate the Belchertown reports. Time
>> for new hardware?
>
> "*I'm good. My computer is too
On Sunday, November 1, 2020 at 11:09:53 AM UTC-8, T Reid wrote:
>
> I am running weewx and Belchertown on an older rpi 3 model B version 1.2.
> Cheetah takes around 20 seconds to generate the Belchertown reports. Time
> for new hardware?
>
>
"*I'm good. My computer is too fast already*", said n
I am running weewx and Belchertown on an older rpi 3 model B version 1.2.
Cheetah takes around 20 seconds to generate the Belchertown reports. Time
for new hardware?
On Sunday, November 1, 2020 at 10:32:27 AM UTC-8 vince wrote:
> On Sunday, November 1, 2020 at 9:52:51 AM UTC-8, T Reid wrote:
On Sunday, November 1, 2020 at 9:52:51 AM UTC-8, T Reid wrote:
>
> > My guess is that your weewx instance is CPU bound and really is running
> behind.
>
> You may be on to something. I watched top for a while. CPU load on the
> python2 process runs under 10% when MQTT is posting loop records
> My guess is that your weewx instance is CPU bound and really is running
behind.
You may be on to something. I watched top for a while. CPU load on the
python2 process runs under 10% when MQTT is posting loop records. But
every five minutes, when the archive records and web pages are bei
T Reid writes:
> As I feared, the problem is not fixed. The lag between the posting of MQTT
> records by weewx and the current time has wandered all over the place over
> the past two days. It has gone from dead on time to 1.5 hours behind, and
> everything in between. Last night it was doi
As I feared, the problem is not fixed. The lag between the posting of MQTT
records by weewx and the current time has wandered all over the place over
the past two days. It has gone from dead on time to 1.5 hours behind, and
everything in between. Last night it was doing okay, this morning it w
Greg, I am not ready to declare victory yet, but after restarting my
mosquitto broker, I let weewx keep running and overnight the MQTT loop
records gradually caught up! Not all at once, but over time you could see
the delay shrinking. All day today, the display has been pretty much spot
on.
Thank you for your very thorough response, Greg. In response to your
questions and suggestions:
- I am publishing aggregate data. Here is the MQTT section of my
weeewx.conf:
[[MQTT]]
server_url = mqtts://user:passw...@mqtt.example.com:8883/
topic = weather/belmont
binding = a
T Reid writes:
> I am using the MQTT add-in to pipe real time loop entries from my Davis
> Vantage Pro into the Belchertown skin, using the standard instructions for
> that skin. It generally works great. But every couple of days the MQTT
> feed will fall behind, sometimes by as much as an
I am using the MQTT add-in to pipe real time loop entries from my Davis
Vantage Pro into the Belchertown skin, using the standard instructions for
that skin. It generally works great. But every couple of days the MQTT
feed will fall behind, sometimes by as much as an hour or more. To fix it,
11 matches
Mail list logo
