Hi, Rod, Yes and thanks for adding yet another confirmation of the issue. =D
I can show that if I do the query within X hours of my offset of UTC, what actually happens is they report 288 records from the day PRIOR to the one I am asking about. For example, I ask for 20190528 and they give me records for 20190527, so *that* is why wunderfixer "thinks" it needs to re-upload everything. I am in contact with IBM about it and have shown them irrefutable proof of the issue. They didn't respond back yet, which I expect is because the proof was irrefutable. Ha! ;-) I expect that they're investigating and would rather respond from a position of understanding, or with any luck maybe even a quick fix. =D I meant to follow-up with IBM again this morning, but got waylaid, so I'll do that now. Thanks again, and for the reminder. =D Regards, \Leon -- Leon Shaner :: Dearborn, Michigan (iPad Pro) > On May 29, 2019, at 6:14 PM, Rod Yager <r...@yager.net.au> wrote: > > There is definitely a time zone issue. I am in the Sydney Australia timezone > (UTC +10 hours). > > It is currently 8am local time on May 30, 2019. (10pm May 29, 2019 UTC) > > If I execute > > ./wunderfixer --verbose --date=2019-05-29 --epsilon=125 > > > > I get > > > > Using configuration file /home/weewx/weewx.conf. > > Using database binding 'wx_binding', which is bound to database > 'archive_mysql' > > Weather Underground Station: xxxxxxx > > Date to check: 2019-05-29 > > Number of archive records: 288 > > Number of WU records: 97 > > Number of missing records: 288 > > > > Now WU actually has 288 records for 2019-05-29. > > But it only has 97 records for 2019-05-30. > > > > So it is clear that wunderfixer is downloading the record data for 2019-05-30 > from WeatherUnderground and trying to match them with the local records for > 2019-30-29. > > Of course, they all mismatch, and so wunderfixer concludes that it must > upload all the data for 2019-05-29. > > > > Hope this narrows down the search for a solution. > > > > Rod > > > > >> On Monday, May 27, 2019 at 9:35:25 PM UTC+10, Leon Shaner wrote: >> >>> On May 27, 2019, at 12:12 AM, gjr80 <gjrod...@gmail.com> wrote: >>> >>>> On Monday, 27 May 2019 13:16:53 UTC+10, Leon Shaner wrote: >>>> [snip] >>>> If you can see any shorter paths to a more reliable outcome than I have >>>> achieved so far, then you know know know I will be very grateful. =D >>> >>> I am not sure what local/UTC issue you refer to. When I do a >>> api.weather.com/v2/pws/history query on a station to the east of Greenwich >>> I am returned all records for the date specified (eg 20190525 gives me all >>> records for 25 May 2019), each record contains an epoch timestamp which is >>> correct and consistent with 25 May 2019. Everything is as I would expect. >>> However, when I perform the same query on a station to the west of >>> Greenwich I am returned records for the day before the date specified (ie >>> 20190525 gives me all records for 24 May 2019 not 25 May 2019), again each >>> record contains an epoch timestamp but the timestamp is for the previous >>> day Ie 24 May 2019. I have checked a number of data records in the stations >>> history table and WU is definitely returning the midnight to midnight data >>> for the day before. I have confirmed this behaviour with a number of >>> stations both east and west of Greenwich. >>> >>> I don't think there is a local/UTC time issue, I think WU is having some >>> implementation issues and for stations west of Greenwich they are returning >>> the wrong day of data. >> >> Thanks, Gary! This was all very helpful. >> In addition to what you've described across the east vs west of GMT, I get >> similar behavior if I am within X hours of my local UTC offset when querying >> my own station. >> Last night as soon as localtime rolled over midnight, the queries for the >> previous day were correct. >> >> --Leon >> >>> >>> Gary > > -- > 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/683a28af-35e4-474e-95a0-f684b9926af0%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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/FD8C60DC-D403-4411-8A6D-B088AFFC90FC%40isylum.org. For more options, visit https://groups.google.com/d/optout.
