Could you try the present version of wunderfixer? I just patched it this morning.
On Mon, Feb 10, 2020 at 6:50 AM Ernest Jillson <[email protected]> wrote: > Checking here: > https://www.wunderground.com/dashboard/pws/KFLRIVER11/graph/2020-01-29/2020-01-29/daily > > I pulled the weewx 4.0.0b11 down and used the wunderfixer from the bin > folder. My commands, minus my api key, were: > > cd /home/pi/weewx4/weewx-4.0.0b11/bin > ./wunderfixer /etc/weewx/weewx.conf --api-key="my_api_key" > --date=2020-01-29 > > I applied the logic fix to get around the "204" error code. It definitely > *thinks* it's sending the data. Lists every 5 minute observation and says > "...published." after each one. I've done this three times or more over > the last few days, so it's not a lag issue. > > It's looking like it may well be a WU problem that I'll just have to live > with. > > Thanks for all your help. > > > On Monday, February 10, 2020 at 9:35:34 AM UTC-5, Leon Shaner wrote: >> >> Hey, Ernest. >> >> If you check after some time has passed are the records there? >> There is always a "lag" between the time the records are uploaded and >> when they appear. >> Also, be sure to check via the WU web portal and not some app like >> WunderStation (which they've deprecated). >> >> Anyway, the wunderfixer is doing its job. What happens on the WU side is >> subject to their many bugs and infrastructure issues. :-/ >> >> Regards, >> \Leon >> -- >> Leon Shaner :: Dearborn, Michigan (iPad) >> >> On Feb 9, 2020, at 9:59 PM, Ernest Jillson <[email protected]> wrote: >> >> >> It "looks" like it's working for me, but doesn't. I get this message: >> >> "No results returned from Weather Underground (perhaps a bad station >> name??). >> Publishing anyway." >> >> It then proceeds to upload all my 5 minute obs. Only thing is, they >> never show up on wunderground. >> >> >> >> On Sunday, February 9, 2020 at 4:02:21 PM UTC-5, Richard G wrote: >>> >>> >>> Worked for me thanks. >>> >>> Richard >>> On Sunday, 9 February 2020 18:19:00 UTC, Leon Shaner wrote: >>>> >>>> Richard, >>>> It was a long thread. Here is my workaround for the 204 response when >>>> the request is valid, but there are no records to return: >>>> >>>> $ diff wunderfixer wunderfixer_tk >>>> 407,409c407 >>>> < # Valid response, it's just that WU has no records >>>> for the requested date >>>> < # Return an empty list of TimeStamps (as in WU has no >>>> records) >>>> < return {} >>>> --- >>>> > raise IOError("Probably a bad station ID or invalid >>>> date") >>>> >>>> Or if the line numbers don't match yours, it looks like this in context: >>>> >>>> if hasattr(response, 'code') and response.code != 200: >>>> if response.code == 204: >>>> # Valid response, it's just that WU has no records for >>>> the requested date >>>> # Return an empty list of TimeStamps (as in WU has no >>>> records) >>>> return {} >>>> else: >>>> raise IOError("Bad response code returned: %d" % >>>> response.code) >>>> >>>> Regards, >>>> \Leon >>>> -- >>>> Leon Shaner :: Dearborn, Michigan (iPhone) >>>> >>>> On Feb 9, 2020, at 12:40 PM, Richard G <[email protected]> wrote: >>>> >>>> >>>> I had an outage of a week where no data was uploaded to wunderground. I >>>> discovered all the posts about the change of API etc. so pulled down the >>>> development branch. This version with the api_key allowed me to fix data on >>>> partial days i.e. when there was some data but on days where there is no >>>> data at all then it fails >>>> >>>> Using database binding 'wx_binding', which is bound to database >>>> 'archive_sqlite' >>>> >>>> Weather Underground Station: INORFOLK** >>>> >>>> Date to check: 2020-02-07 >>>> >>>> Number of archive records: 288 >>>> >>>> Could not get Weather Underground data. >>>> >>>> Reason: Probably a bad station ID or invalid date >>>> >>>> Exiting. >>>> >>>> The message "could not get Weather Underground data" is correct as >>>> there isn't any for that day, but it then needs to upload so there is. >>>> Looks like a bug but I thought I would check before reporting. >>>> >>>> Thanks >>>> >>>> >>>> Richard >>>> >>>> -- >>>> 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/04c6f04e-502a-40a2-ad9d-62a4fad5a8b5%40googlegroups.com >>>> <https://groups.google.com/d/msgid/weewx-user/04c6f04e-502a-40a2-ad9d-62a4fad5a8b5%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> -- >> 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/30ac8208-34d8-4b47-a8ac-636151c794c2%40googlegroups.com >> <https://groups.google.com/d/msgid/weewx-user/30ac8208-34d8-4b47-a8ac-636151c794c2%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> -- > 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/31bc61de-9a1f-4fca-871f-6644f3717577%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/31bc61de-9a1f-4fca-871f-6644f3717577%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAPq0zEC%2B%3DnxTng62Gv4%3DpdaAmFGn7jh_Jz-A5n3nPLVpFVun2g%40mail.gmail.com.
