[s]Incorrect[/s] Confusing rain data shown on WeatherUnderground. **solved**

[DAP]

Please see the rain total graph for March 14th: https://www.wunderground.com/dashboard/ ... 3-14/daily

Total rainfall should always be increasing, and only drop to zero at midnight.

March 14th is the day that Daylight Savings Time starts here, and I know from experience that this is not always handled properly by software engineers. (difficult problem that only happens twice a year. I don't know if it is fixed yet in MythTV). I'm pointing this out so it does not get overlooked as a contributing factor. This problem might even be in the way that WeatherUndergound is handling this. March 14th is a 23 hour day, clock jumps directly from 1:59 AM to 3:00 AM.

I really wish we could get rid of Daylight Savings Time. It does not fix anything, and causes no end of trouble.

There is nothing of interest in the log file:

Code: Select all

oled (22.02.2021 04:22:29): process started.
database (24.02.2021 20:56:21): process started.
database (24.02.2021 20:56:21): Content of RAM database restored.
wnetd  (24.02.2021 20:56:24): process started.
system (24.02.2021 20:56:24): start of logging process initiated.
wnetd  (24.02.2021 20:56:24): send data thread started (pid:2298 tid:2299)
logger (24.02.2021 20:56:25): databases connected. Update interval 3600 seconds.
logger (24.02.2021 20:56:25): data logger (version 5.1e, build 14308) started.
logger (24.02.2021 20:56:26): connect station 0 (Meteostick Vantage via USB serial).
logger (24.02.2021 20:56:26): connect station 9 (System Data via Plug-in).
logger (24.02.2021 20:56:28): station 0 (Meteostick Vantage), transmitter 2 registered as ISS
logger (24.02.2021 20:56:28): station 0 (Meteostick Vantage), Meteostick Version 2.5.2
logger (24.02.2021 20:56:28): station 0 (Meteostick Vantage), debug off
logger (24.02.2021 20:56:28): station 0 (Meteostick Vantage), verbose off
logger (24.02.2021 20:56:28): station 0 (Meteostick Vantage), output raw (8 bytes)
logger (24.02.2021 20:56:28): station 0 (Meteostick Vantage), output raw (10 bytes)
logger (24.02.2021 20:56:28): station 0 (Meteostick Vantage), filter on
logger (24.02.2021 20:56:28): station 0 (Meteostick Vantage), rx threshold set to -55db
logger (24.02.2021 20:56:28): station 0 (Meteostick Vantage), listening to transmitter 2
logger (24.02.2021 20:56:28): station 0 (Meteostick Vantage), bandwidth narrow
logger (24.02.2021 20:56:29): station 0 (Meteostick Vantage), chip authentication ok: 14
logger (24.02.2021 20:56:29): station 0 (Meteostick Vantage), frequency band 915MHz (US)
logger (24.02.2021 20:56:30): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (24.02.2021 20:56:30): services paused.
database (24.02.2021 20:56:43): database sync done (47 tables, 143/1928 writes).
logger (24.02.2021 20:58:27): give up waiting for sensors after 120 secs.
logger (24.02.2021 20:58:27): services activated.

Edit: Looking at the graph a bit more closely, it covers 24 hours and the last hour is the first hour of the next day.
I REALLY hate Daylight Savings Time.

[admin]

I can't identify a Meteobridge issue here. Can we close this thread?

[DAP]

As far as I can tell, it is not a meteobrige issue (I thought it might be at first). Seems that Weather underground has a weird way of handling daylight savings time change.