Re: [weewx-user] WU "capacity" issues, wunderfixer constantly finding missing records, et al
Bingo! Okay, sorry for the noise. Yes, "wunderfixer --epsilon 180" was exactly what was needed. In this case even just "wunderfixer --epsilon 125" would have been enough! I hope this was as educational to someone as it was to me. LOL pi@nixie:/usr/share/weewx $ /usr/share/weewx/wunderfixer --date `date +\%Y-\%m-\%d` --epsilon 120 --verbose --test Using configuration file /etc/weewx/weewx.conf. Using database binding 'wx_binding', which is bound to database 'archive_sqlite' Weather Underground Station: KMIDEARB5 Date to check: 2019-05-01 Number of archive records: 757 Number of WU records: 172 Number of missing records: 10 Missing records: 2019-05-01 09:57:00 EDT (1556719020); 29.226"; 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ... skipped. 2019-05-01 10:17:00 EDT (1556720220); 29.223"; 52.0F; 92%; 2.0 mph; 136 deg; 3.6 mph gust; 49.9F; 0.00" rain ... skipped. 2019-05-01 10:27:00 EDT (1556720820); 29.214"; 52.9F; 92%; 2.5 mph; 115 deg; 6.5 mph gust; 50.6F; 0.00" rain ... skipped. 2019-05-01 10:32:00 EDT (1556721120); 29.214"; 53.2F; 91%; 2.5 mph; 113 deg; 2.5 mph gust; 50.7F; 0.00" rain ... skipped. 2019-05-01 11:02:00 EDT (1556722920); 29.196"; 56.5F; 89%; 3.1 mph; 141 deg; 3.1 mph gust; 53.3F; 0.00" rain ... skipped. 2019-05-01 11:47:00 EDT (1556725620); 29.184"; 61.0F; 84%; 3.6 mph; 156 deg; 3.6 mph gust; 56.1F; 0.00" rain ... skipped. 2019-05-01 11:52:00 EDT (1556725920); 29.179"; 61.3F; 84%; 2.0 mph; 164 deg; 5.1 mph gust; 56.4F; 0.00" rain ... skipped. 2019-05-01 12:12:00 EDT (1556727120); 29.182"; 61.9F; 84%; 3.6 mph; 184 deg; 5.1 mph gust; 56.9F; 0.00" rain ... skipped. 2019-05-01 12:17:00 EDT (1556727420); 29.182"; 62.1F; 84%; 3.6 mph; 184 deg; 4.7 mph gust; 57.2F; 0.00" rain ... skipped. 2019-05-01 12:32:00 EDT (1556728320); 29.184"; 62.7F; 84%; 2.0 mph; 191 deg; 4.0 mph gust; 57.8F; 0.00" rain ... skipped. pi@nixie:/usr/share/weewx $ /usr/share/weewx/wunderfixer --date `date +\%Y-\%m-\%d` --epsilon 180 --verbose --test Using configuration file /etc/weewx/weewx.conf. Using database binding 'wx_binding', which is bound to database 'archive_sqlite' Weather Underground Station: KMIDEARB5 Date to check: 2019-05-01 Number of archive records: 758 Number of WU records: 172 Number of missing records: 0 pi@nixie:/usr/share/weewx $ /usr/share/weewx/wunderfixer --date `date +\%Y-\%m-\%d` --epsilon 125 --verbose --test Using configuration file /etc/weewx/weewx.conf. Using database binding 'wx_binding', which is bound to database 'archive_sqlite' Weather Underground Station: KMIDEARB5 Date to check: 2019-05-01 Number of archive records: 761 Number of WU records: 173 Number of missing records: 0 Regards, Leon -- Leon Shaner :: Dearborn, Michigan (iPad Pro) > On May 1, 2019, at 12:36 PM, Leon Shaner wrote: > > Hmm. Looking more closely at that query: > > https://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=KMIDEARB5=5=1=2019=1 > > Although timestamp are often a little off, WU appears to only ever report > data normalized to every 5-minute bucket. > > So this morning 9:50, ~9:55, and 10:00 are all they're going to show, and > those data points are already there in the query. > > Therefore, I expect that the record locally stamped at 9:57 is likely to > NEVER show in the query. > > Is this a case where increasing the wunderfixer --epsilon to say 180 seconds > would suppress the attempt to upload the record from 9:57? > > Regards, > Leon > -- > Leon Shaner :: Dearborn, Michigan (iPad Pro) > >> On May 1, 2019, at 12:10 PM, Leon Shaner wrote: >> >> Here is a bit more analysis on one record that has been found missing >> consistently / won't stick. Seeking a second opinion on my analysis. =D >> >> The missing record has timestamp 1556719020 and has been found missing every >> 10 minutes when wunderfixer runs against "today". >> That record is from from 9:57 a.m. EDT (my local time). >> >> Further down, I show the WU query via a similar method that wunderfixer uses. >> >> There are no records from between ~9:54 a.m. and 10:00 a.m. EDT. >> So I trust wunderfixer is correct, here. =D >> >> The WU record from 10:00 a.m. has values "close" to the missing 9:57 a..m >> record, but the values are just far enough off that I do not suspect the 120 >> second "epsilon" is causing the "miss" on validation (the 9:57 record is not >> being mis-matched against 10:00 record). >> >> Are we in agreement, that wunderfixer is correct and WU is simply failing to >> show the record even up multiple attempts to re-upload? >> >> Here are the wunderfixer reported misses: >> >> pi@nixie:/usr/share/weewx $ grep 1556719020 /var/log/weewx.log >> Wed 1 May 10:05:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; >> 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain >> ...published. >> Wed 1
Re: [weewx-user] WU "capacity" issues, wunderfixer constantly finding missing records, et al
Hmm. Looking more closely at that query: https://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=KMIDEARB5=5=1=2019=1 Although timestamp are often a little off, WU appears to only ever report data normalized to every 5-minute bucket. So this morning 9:50, ~9:55, and 10:00 are all they're going to show, and those data points are already there in the query. Therefore, I expect that the record locally stamped at 9:57 is likely to NEVER show in the query. Is this a case where increasing the wunderfixer --epsilon to say 180 seconds would suppress the attempt to upload the record from 9:57? Regards, Leon -- Leon Shaner :: Dearborn, Michigan (iPad Pro) > On May 1, 2019, at 12:10 PM, Leon Shaner wrote: > > Here is a bit more analysis on one record that has been found missing > consistently / won't stick. Seeking a second opinion on my analysis. =D > > The missing record has timestamp 1556719020 and has been found missing every > 10 minutes when wunderfixer runs against "today". > That record is from from 9:57 a.m. EDT (my local time). > > Further down, I show the WU query via a similar method that wunderfixer uses. > > There are no records from between ~9:54 a.m. and 10:00 a.m. EDT. > So I trust wunderfixer is correct, here. =D > > The WU record from 10:00 a.m. has values "close" to the missing 9:57 a..m > record, but the values are just far enough off that I do not suspect the 120 > second "epsilon" is causing the "miss" on validation (the 9:57 record is not > being mis-matched against 10:00 record). > > Are we in agreement, that wunderfixer is correct and WU is simply failing to > show the record even up multiple attempts to re-upload? > > Here are the wunderfixer reported misses: > > pi@nixie:/usr/share/weewx $ grep 1556719020 /var/log/weewx.log > Wed 1 May 10:05:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; > 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. > Wed 1 May 10:15:02 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; > 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. > Wed 1 May 10:25:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; > 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. > Wed 1 May 10:35:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; > 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. > Wed 1 May 10:45:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; > 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. > Wed 1 May 10:55:02 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; > 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. > Wed 1 May 11:05:02 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; > 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. > Wed 1 May 11:15:02 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; > 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. > Wed 1 May 11:25:02 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; > 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. > Wed 1 May 11:35:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; > 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. > Wed 1 May 11:45:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; > 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. > Wed 1 May 11:55:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; > 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. > > > Here is what WU shows around that time... > > pi@nixie:/usr/share/weewx $ curl -L > "http://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=KMIDEARB5=5=1=2019=1; > 2>/dev/null | grep '^2019-05-01 09:' > 2019-05-01 > 09:00:00,48.6,46.6,29.26,ESE,112,3.1,4,93,0,,,0.91,weewx-3.9.1,2019-05-01 > 13:00:00, > 2019-05-01 > 09:05:00,48.7,46.8,29.25,ESE,108,2,2.5,93,0,,,0.91,weewx-3.9.1,2019-05-01 > 13:05:00, > 2019-05-01 > 09:10:00,48.7,46.8,29.25,ESE,108,2,0,93,0,,,0.91,weewx-3.9.1,2019-05-01 > 13:10:00, > 2019-05-01 > 09:15:00,48.9,47,29.25,ESE,102,2,5.4,93,0,,,0.91,weewx-3.9.1,2019-05-01 > 13:15:00, > 2019-05-01 > 09:20:00,48.9,47,29.25,ESE,102,2,0,93,0,,,0.91,weewx-3.9.1,2019-05-01 > 13:20:00, > 2019-05-01 > 09:25:00,48.9,47,29.25,ESE,108,2.5,5.4,93,0,,,0.91,weewx-3.9.1,2019-05-01 > 13:25:00, > 2019-05-01 > 09:30:00,49.3,47.3,29.25,ESE,108,2.5,1.3,93,0,,,0.91,weewx-3.9.1,2019-05-01 > 13:30:00, > 2019-05-01 > 09:35:00,49.3,47.3,29.24,ESE,108,2.9,3.6,93,0,,,0.91,weewx-3.9.1,2019-05-01 > 13:35:00, > 2019-05-01 > 09:40:00,49.5,47.5,29.24,ESE,108,2.9,1.3,93,0,,,0.91,weewx-3.9.1,2019-05-01 > 13:40:00, > 2019-05-01 > 09:45:00,49.6,48,29.24,ESE,118,2.9,4,94,0,,,0.91,weewx-3.9.1,2019-05-01 > 13:45:00, >
Re: [weewx-user] WU "capacity" issues, wunderfixer constantly finding missing records, et al
Here is a bit more analysis on one record that has been found missing consistently / won't stick. Seeking a second opinion on my analysis. =D The missing record has timestamp 1556719020 and has been found missing every 10 minutes when wunderfixer runs against "today". That record is from from 9:57 a.m. EDT (my local time). Further down, I show the WU query via a similar method that wunderfixer uses. There are no records from between ~9:54 a.m. and 10:00 a.m. EDT. So I trust wunderfixer is correct, here. =D The WU record from 10:00 a.m. has values "close" to the missing 9:57 a..m record, but the values are just far enough off that I do not suspect the 120 second "epsilon" is causing the "miss" on validation (the 9:57 record is not being mis-matched against 10:00 record). Are we in agreement, that wunderfixer is correct and WU is simply failing to show the record even up multiple attempts to re-upload? Here are the wunderfixer reported misses: pi@nixie:/usr/share/weewx $ grep 1556719020 /var/log/weewx.log Wed 1 May 10:05:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. Wed 1 May 10:15:02 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. Wed 1 May 10:25:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. Wed 1 May 10:35:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. Wed 1 May 10:45:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. Wed 1 May 10:55:02 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. Wed 1 May 11:05:02 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. Wed 1 May 11:15:02 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. Wed 1 May 11:25:02 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. Wed 1 May 11:35:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. Wed 1 May 11:45:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. Wed 1 May 11:55:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. Here is what WU shows around that time... pi@nixie:/usr/share/weewx $ curl -L "http://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=KMIDEARB5=5=1=2019=1; 2>/dev/null | grep '^2019-05-01 09:' 2019-05-01 09:00:00,48.6,46.6,29.26,ESE,112,3.1,4,93,0,,,0.91,weewx-3.9.1,2019-05-01 13:00:00, 2019-05-01 09:05:00,48.7,46.8,29.25,ESE,108,2,2.5,93,0,,,0.91,weewx-3.9.1,2019-05-01 13:05:00, 2019-05-01 09:10:00,48.7,46.8,29.25,ESE,108,2,0,93,0,,,0.91,weewx-3.9.1,2019-05-01 13:10:00, 2019-05-01 09:15:00,48.9,47,29.25,ESE,102,2,5.4,93,0,,,0.91,weewx-3.9.1,2019-05-01 13:15:00, 2019-05-01 09:20:00,48.9,47,29.25,ESE,102,2,0,93,0,,,0.91,weewx-3.9.1,2019-05-01 13:20:00, 2019-05-01 09:25:00,48.9,47,29.25,ESE,108,2.5,5.4,93,0,,,0.91,weewx-3.9.1,2019-05-01 13:25:00, 2019-05-01 09:30:00,49.3,47.3,29.25,ESE,108,2.5,1.3,93,0,,,0.91,weewx-3.9.1,2019-05-01 13:30:00, 2019-05-01 09:35:00,49.3,47.3,29.24,ESE,108,2.9,3.6,93,0,,,0.91,weewx-3.9.1,2019-05-01 13:35:00, 2019-05-01 09:40:00,49.5,47.5,29.24,ESE,108,2.9,1.3,93,0,,,0.91,weewx-3.9.1,2019-05-01 13:40:00, 2019-05-01 09:45:00,49.6,48,29.24,ESE,118,2.9,4,94,0,,,0.91,weewx-3.9.1,2019-05-01 13:45:00, 2019-05-01 09:50:00,49.8,47.9,29.23,ESE,118,2.9,4,93,0,,,0.91,weewx-3.9.1,2019-05-01 13:50:00, 2019-05-01 09:54:59,50.2,48.2,29.23,ESE,111,2.9,7.6,93,0,,,0.91,weewx-3.9.1,2019-05-01 13:54:59, pi@nixie:/usr/share/weewx $ curl -L "http://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=KMIDEARB5=5=1=2019=1; 2>/dev/null | grep '^2019-05-01 10:' 2019-05-01 10:00:00,50.5,48.6,29.23,ESE,111,2.9,4.3,93,0,,,0.91,weewx-3.9.1,2019-05-01 14:00:00, 2019-05-01 10:05:00,51.1,49.4,29.22,ESE,122,3.6,0,94,0,,,0.91,weewx-3.9.1,2019-05-01 14:05:00, 2019-05-01 10:10:00,51.4,49.5,29.22,ESE,122,3.6,1.8,93,0,,,0.91,weewx-3.9.1,2019-05-01 14:10:00, 2019-05-01 10:14:59,52,50,29.22,SE,136,2,4.3,93,0,,,0.91,weewx-3.9.1,2019-05-01 14:14:59, 2019-05-01 10:20:00,52.2,49.9,29.21,SE,136,2,4.3,92,0,,,0.91,weewx-3.9.1,2019-05-01 14:20:00, 2019-05-01
[weewx-user] WU "capacity" issues, wunderfixer constantly finding missing records, et al
Hey, WeeWX'ers, I wonder how many folks are experiencing issues with WU timing out / not responding / failing to accept station updates from weewx? I've resorted to running wunderfixer roughly every 10 minutes against "today" and "yesterday" and it's almost always finding missing records throughout "today" which after enough wunderfixer re-uploads, they do eventually "stick." I can see from my "weewx_watchdog" logs that wunderfixer was timing out almost every attempt to run against the "yesterday" date, but was usually fine when running against the "today" date. I'm guessing that WU may have some optimizations in place to respond quickly to "current" day queries, and maybe they have intentionally allocated less "capacity" to historical queries. That might explain the timeouts I was seeing mainly when querying the prior day. I found that increasing the wunderfixer timeout from 10 seconds to 20 seconds was helpful in working around the WU connection issues. There is an updated wunderfixer in the that accepts a --timeout option, over here. Thanks, Tom! =D https://github.com/weewx/weewx/blob/master/bin/wunderfixer Now, because wunderfixer is pretty much always finding missing records, I am wondering of weewx itself is falling victim to the WU "capacity issues" during the normal uploading of records? As in could the records be missing on the WU side due to similar timeouts that wunderfixer is experiencing? I have debug = 1, but there are no issues being reported, so do I need a higher debug, such as debut = 3? Could it be that the connections are going through but WU is losing the data, anyway? And/or could it be that running wunderfixer every 10 minutes isn't allowing WU enough time to process the data, such that is is available by the next query, 10 minutes later? Here are some logs of what I am seeing re: the trend of missing WU data. You can see the "overlap" in that multiple runs of wunderfixer 10 minutes apart are finding and re-uploading the exact same missing records until eventually they do "stick" in that they are not shown missing / not re-uploaded. In the below, you can see that a record from 1556709420 did get posted properly, because it was not mentioned again 10 minutes later. However, there are three other records in bold, which did not "stick" between those wunderfixer runs, 10 minutes apart. And then 10 minutes later, two more overlapping re-uploads, which didn't "stick." Wed 1 May 10:15:11 EDT 2019 Weather Underground Station: KMIDEARB5 Wed 1 May 10:15:11 EDT 2019 Date to check: 2019-04-30 Wed 1 May 10:15:11 EDT 2019 Number of archive records: 1438 Wed 1 May 10:15:11 EDT 2019 Number of WU records: 381 Wed 1 May 10:15:11 EDT 2019 Number of missing records: 0 Wed 1 May 10:25:01 EDT 2019 Using configuration file /etc/weewx/weewx.conf. Wed 1 May 10:25:01 EDT 2019 Using database binding 'wx_binding', which is bound to database 'archive_sqlite' Wed 1 May 10:25:01 EDT 2019 Weather Underground Station: KMIDEARB5 Wed 1 May 10:25:01 EDT 2019 Date to check: 2019-05-01 Wed 1 May 10:25:01 EDT 2019 Number of archive records: 624 Wed 1 May 10:25:01 EDT 2019 Number of WU records: 144 Wed 1 May 10:25:01 EDT 2019 Number of missing records: 5 Wed 1 May 10:25:01 EDT 2019 Wed 1 May 10:25:01 EDT 2019 Missing records: Wed 1 May 10:25:01 EDT 2019 2019-05-01 07:17:00 EDT (1556709420); 29.297"; 47.7F; 93%; 4.7 mph; 98 deg; 7.6 mph gust; 45.7F; 0.00" rain ...published. Wed 1 May 10:25:01 EDT 2019 2019-05-01 09:57:00 EDT (1556719020); 29.226"; 50.4F; 93%; 2.9 mph; 111 deg; 6.9 mph gust; 48.4F; 0.00" rain ...published. Wed 1 May 10:25:01 EDT 2019 2019-05-01 10:17:00 EDT (1556720220); 29.223"; 52.0F; 92%; 2.0 mph; 136 deg; 3.6 mph gust; 49.9F; 0.00" rain ...published. Wed 1 May 10:25:01 EDT 2019 2019-05-01 10:23:00 EDT (1556720580); 29.214"; 52.4F; 92%; 2.5 mph; 115 deg; 4.3 mph gust; 50.1F; 0.00" rain ...published. Wed 1 May 10:25:01 EDT 2019 2019-05-01 10:24:00 EDT (1556720640); 29.214"; 52.5F; 92%; 2.5 mph; 115 deg; 5.4 mph gust; 50.3F; 0.00" rain ...published. Wed 1 May 10:25:14 EDT 2019 Using configuration file /etc/weewx/weewx.conf. Wed 1 May 10:25:14 EDT 2019 Using database binding 'wx_binding', which is bound to database 'archive_sqlite' Wed 1 May 10:25:14 EDT 2019 Weather Underground Station: KMIDEARB5 Wed 1 May 10:25:14 EDT 2019 Date to check: 2019-04-30 Wed 1 May 10:25:14 EDT 2019 Number of archive records: 1438 Wed 1 May 10:25:14 EDT 2019 Number of WU records: 381 Wed 1 May 10:25:14 EDT 2019 Number of missing records: 0 Wed 1 May 10:35:01 EDT 2019 Using configuration file /etc/weewx/weewx.conf. Wed 1 May 10:35:01 EDT 2019 Using database binding 'wx_binding', which is bound to database 'archive_sqlite' Wed 1 May 10:35:01 EDT 2019 Weather Underground Station: KMIDEARB5 Wed 1 May 10:35:01 EDT 2019 Date
