Re: [weewx-user] Wunderfixer (Development Version)

2020-02-10 Thread Thomas Keffer
No. The URL to get existing data is hardwired in wunderfixer, the URL to
post new data is hardwired in weewx/restx.py.

-tk

On Mon, Feb 10, 2020 at 6:04 PM Ernest Jillson  wrote:

> Nope. Not your fault. Does it pull the URL from the weewx.conf?  I know I
> put those back to the original after weather underground gave up (for now)
> on their re-organization.
>
>
> On Mon, Feb 10, 2020 at 5:01 PM Thomas Keffer  wrote:
>
>> That doesn't surprise me. Unfortunately, there is really nothing we can
>> do about it. 😕
>>
>> On Mon, Feb 10, 2020 at 11:28 AM Ernest Jillson 
>> wrote:
>>
>>> I grabbed the latest wunderfixer updated 2 hours ago. I just ran it, and
>>> as before, it says it's doing everything it's supposed to do. So far, after
>>> 5 minutes, nothing on weather underground. I'll keep checking.
>>>
>>>
>>>
>>> On Monday, February 10, 2020 at 11:38:31 AM UTC-5, Thomas Keffer wrote:

 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 
 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  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  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

 Usin

Re: [weewx-user] Wunderfixer (Development Version)

2020-02-10 Thread Ernest Jillson
Nope. Not your fault. Does it pull the URL from the weewx.conf?  I know I
put those back to the original after weather underground gave up (for now)
on their re-organization.


On Mon, Feb 10, 2020 at 5:01 PM Thomas Keffer  wrote:

> That doesn't surprise me. Unfortunately, there is really nothing we can do
> about it. 😕
>
> On Mon, Feb 10, 2020 at 11:28 AM Ernest Jillson 
> wrote:
>
>> I grabbed the latest wunderfixer updated 2 hours ago. I just ran it, and
>> as before, it says it's doing everything it's supposed to do. So far, after
>> 5 minutes, nothing on weather underground. I'll keep checking.
>>
>>
>>
>> On Monday, February 10, 2020 at 11:38:31 AM UTC-5, Thomas Keffer wrote:
>>>
>>> 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 
>>> 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  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  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 ba

Re: [weewx-user] Wunderfixer (Development Version)

2020-02-10 Thread Thomas Keffer
That doesn't surprise me. Unfortunately, there is really nothing we can do
about it. 😕

On Mon, Feb 10, 2020 at 11:28 AM Ernest Jillson  wrote:

> I grabbed the latest wunderfixer updated 2 hours ago. I just ran it, and
> as before, it says it's doing everything it's supposed to do. So far, after
> 5 minutes, nothing on weather underground. I'll keep checking.
>
>
>
> On Monday, February 10, 2020 at 11:38:31 AM UTC-5, Thomas Keffer wrote:
>>
>> 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  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  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  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 

Re: [weewx-user] Wunderfixer (Development Version)

2020-02-10 Thread Ernest Jillson
I grabbed the latest wunderfixer updated 2 hours ago. I just ran it, and as 
before, it says it's doing everything it's supposed to do. So far, after 5 
minutes, nothing on weather underground. I'll keep checking.
 


On Monday, February 10, 2020 at 11:38:31 AM UTC-5, Thomas Keffer wrote:
>
> 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  > 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  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  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 weewx...@googlegroups.com.
> To view this discussion o

Re: [weewx-user] Wunderfixer (Development Version)

2020-02-10 Thread Thomas Keffer
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  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  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  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 weewx...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/weewx-user/04c6f04e-502a-40a2-ad9d-62a4fad5a8b5%40googlegroups.com
 
 .

 --
>> 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...@googlegroups.com.
>> 

Re: [weewx-user] Wunderfixer (Development Version)

2020-02-10 Thread Ernest Jillson
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  > 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  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 weewx...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/04c6f04e-502a-40a2-ad9d-62a4fad5a8b5%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>> -- 
> 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...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/30ac8208-34d8-4b47-a8ac-636151c794c2%40googlegroups.com
>  
> 

Re: [weewx-user] Wunderfixer (Development Version)

2020-02-10 Thread Leon Shaner
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  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  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 weewx...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/04c6f04e-502a-40a2-ad9d-62a4fad5a8b5%40googlegroups.com.
> 
> -- 
> 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/30ac8208-34d8-4b47-a8ac-636151c794c2%40googlegroups.com.

-- 
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/2417BCC3-A907-4DF6-B374-6CF6DD577657%40isylum.org.


Re: [weewx-user] Wunderfixer (Development Version)

2020-02-09 Thread p q
Is this one of those Python 2 vs Python 3 unicode/byte string issues? Is
there anyway to tell what it's sending?

On Sun, Feb 9, 2020 at 6:59 PM Ernest Jillson  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  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 weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/04c6f04e-502a-40a2-ad9d-62a4fad5a8b5%40googlegroups.com
>>> 
>>> .
>>>
>>> --
> 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/30ac8208-34d8-4b47-a8ac-636151c794c2%40googlegroups.com
> 
> .
>


-- 
Peter Quinn
(415)794-2264

-- 
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/CAA1SM23NKuQbRCaJzS8-CL1kTc7tLW4xsnHz_8nuLotqx2Q57w%40mail.gmail.com.


Re: [weewx-user] Wunderfixer (Development Version)

2020-02-09 Thread Ernest Jillson
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  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 weewx...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/04c6f04e-502a-40a2-ad9d-62a4fad5a8b5%40googlegroups.com
>>  
>> 
>> .
>>
>>

-- 
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/30ac8208-34d8-4b47-a8ac-636151c794c2%40googlegroups.com.


Re: [weewx-user] Wunderfixer (Development Version)

2020-02-09 Thread Richard G

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 > 
> 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 weewx...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/04c6f04e-502a-40a2-ad9d-62a4fad5a8b5%40googlegroups.com
>  
> 
> .
>
>

-- 
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/cd91a9d6-05fb-46c6-ab68-eef6d6e27435%40googlegroups.com.


Re: [weewx-user] Wunderfixer (Development Version)

2020-02-09 Thread iain MacDonnell
Workaround works for me (thanks!). Is there an open issue for this?

~iain

-- 
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/0a31462f-0a9b-47ee-8d30-dac66e8fabec%40googlegroups.com.


Re: [weewx-user] Wunderfixer (Development Version)

2020-02-09 Thread Leon Shaner
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  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 weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/04c6f04e-502a-40a2-ad9d-62a4fad5a8b5%40googlegroups.com.

-- 
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/01A0DEC2-AFB3-400F-A30B-AE517FAB4BC9%40isylum.org.


[weewx-user] Wunderfixer (Development Version)

2020-02-09 Thread Richard G
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/04c6f04e-502a-40a2-ad9d-62a4fad5a8b5%40googlegroups.com.