Thanks for your input Karen, what I've been talking about is very skin
specific. The skin produces a JS File which is uploaded (This
one: https://www.kainzbauer.net/weather/Rif/de/ts.json) and the front end
handles everything else in javascript. If the front end finds an updated
timestamp (which is a very lightweight call) it fetches the updated data
(transfers several hundred kB or more, depending on the individual setup).
It's all about improving the watching-live-weather-data experience. The way
it is implemented now, is not "seamless" and I want to improve that.
Karen K schrieb am Montag, 21. August 2023 um 19:04:47 UTC+2:
> One fix: "interval" ("interval_minute" to be exact) is the only indicator
> for ARCHIVE records within the MQTT data. Or you compare the timestamps in
> dateTime.
>
> Karen K schrieb am Montag, 21. August 2023 um 18:28:37 UTC+2:
>
> [email protected] schrieb am Montag, 21. August 2023 um 14:48:30 UTC+2:
>
> I'll take a step back and describe the challenge more detailed:
>
>
> I am not sure I understand the problem.
>
> In MQTT you can distinguish between LOOP and ARCHIVE packets by the
> existence of the dateTime and interval key. If you want to always see the
> very last reading you want to make sure to process LOOP packets in MQTT
> only.
>
> In case there are no values to process that are included in the ARCHIVE
> packet only, you can configure MQTT to only send LOOP packets.
>
>
>
>
--
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/7ebb219c-765a-416d-8af2-ba6ac25c8c1dn%40googlegroups.com.
