Some 24 hours ago I observed a 'freezing' of the WeeWX-picture at
https://vannwnhzn.nl/WeeWX0/index.html
Still continues.
First thought is that upload for the html-file has stopped.
Because for upload using the FTP-function in WeeWX, implicitly it means
that WeeWX has to be checked.
Observation in WeeWX is that all files of WeeWX still get actual
datestamp, but contents have completely been frozen on approx. June 8th,
16:25
Restart of WeeWX (regardless of route) has no effects: no further
visible processing.
This afternoon (as second thought) the penny dropped that this was also
the time that Weatherflow_Tempest as datafeeding sensor through UDP went
on strike:
Tempest hub shows red light, meaning that the dataflow from the sensor
(or the hub itself) has problems.
Also see at the Weatherflow-server that data & display has been frozen
at the time mentioned above.
Locally in Domoticz I see that since that time the data from the
UDP-sniffer is also solid as a rock.
Hard reset of the Tempest hub has no effect.
*_Question:_*
is it correct observation that when an interface-driver of WeeWX has no
inputs with changing time-validity, then all subsequent dataflows also
stop & freeze?
*_Or_* is this apparently simultaneous event just an unhappy coincidence?
*_Or_* some aspects specific for the Tempest hub & interface-driver?
--
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/34d0e582-ece0-3fcd-8c08-489a05700243%40gmail.com.
