Hi Colin, I don't think this is skin related, but rather weewx and/or weewx-mqtt related.
I observed the same behavior early on when creating the skin. It seems as though the weewx-mqtt extension queues the LOOP packets if the broker is offline, then once the broker is online it dumps the queue to MQTT in a very rapid manner. I don't think there's any harm, but I agree it was interesting seeing the website update in such a rapid way. On Sunday, November 18, 2018 at 5:21:32 PM UTC-5, Colin Larsen wrote: > > Not 100% sure where this belongs but here goes; > > My home MQTT broker stopped yesterday around 1am. It's been nearly 36hrs > until I've been in a position to restart it, but when I did Weewx appeared > to start feeding it the real-time data from the point in time that the > broker stopped in some sort of catch-up mode. Watching the Poblabs skin > reporting the time of each update it was going to be quite some time before > it caught up and I was back in today :) > > A reboot of Weewx solved the issue but I'm not sure if there is a timeout > that can be applied when MQTT stops trying to send data to a dead broker? > Is that even a sensible thing to do? > > Cheers > Colin > -- 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.
