Hi, WeeWX'ers! =D For those on WeeWX 4.0 / development, ONLY... I am done with changing wunderfixer to use the new wunderground API KEY way of doing the WU query to see what records they have for comparison to those in the archive DB. Yay! =D
Please see the comments in the pull request over here: https://github.com/weewx/weewx/pull/416 And until that gets merged you can grab a copy from here -- again this is the 4.0 / development version, ONLY: https://raw.githubusercontent.com/UberEclectic/weewx/development/bin/wunderfixer Now, I'm off to work on the backport to WeeWX 3.9.1. Fun fun! =D Regards, \Leon -- Leon Shaner :: Dearborn, Michigan (iPad Pro) > On May 24, 2019, at 1:35 PM, Leon Shaner <l...@isylum.org> wrote: > > FYI, all, I am currently hot on the trail to converting the wunderfixer query > to use the new API instead. The new API is going to be much easier than the > old query, because the output is neatly formatted as JSON, and crucially for > each record they even include the "epoch" i.e. Unix timestamp, which is all > we care about in that query anyway. > The use of "epoch" means I won't even have to convert the date strings to do > the matching. =D > Even the input date parameter is cleaner a la 20190524. =D > > What I am slightly undecided about is how/where to store the API key. > I think for compatibility reasons I'll add a new field in the weewx.conf for > the API key. > That way existing code based on a password can still use that method, and > over time newer code can use the API key explicitly instead of a password. > > Once I have the new wunderfixer working, for weewx 4.0, I'll work to backport > the changes to weewx 3.9.1. > > Hopefully I don't forget also to update wee_debug to obfuscate the API key, > before I'm done with all of this. LOL > > Docs on the new API are over here... This is for people like us who have a > PWS, as opposed to other people who have to pay for API usage: > > https://docs.google.com/document/d/1eKCnKXI9xnoMGRRzOL1xPCBihNV2rOet08qpE_gArAY/edit > The API Key is generated in the "Member Settings" section of wunderground.com > ("My Profile" > "Member Settings" > "API Keys"). > > > With any luck I'll have this banged out in a few hours. =D > > Regards, > \Leon > -- > Leon Shaner :: Dearborn, Michigan (iPad Pro) > >> On May 23, 2019, at 9:33 PM, Leon Shaner <l...@isylum.org> wrote: >> >> I am in contact with IBM. This whole interface is entirely for THEIR >> benefit. >> I am persistent SOB. It'll be fixed. LOL >> >> Regards, >> \Leon >> -- >> Leon Shaner :: Dearborn, Michigan (iPad Pro) >> >>> On May 23, 2019, at 9:22 PM, Jarom Hatch <jsha...@gmail.com> wrote: >>> >>> Even after that none of the backfilled data made it in. If they are no >>> longer accepting backfilled data then fixing wunderfixer might not be >>> possible. >>> >>> -- >>> 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/76f9aa83-37ac-4014-aa04-7f675d63a6e1%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/36EA4E1E-EEAE-4210-A18E-5024653E6F09%40isylum.org. >> 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/2C6BD081-290F-4FE7-81F7-76D9FCE230DF%40isylum.org. For more options, visit https://groups.google.com/d/optout.
