Enclosing with quotes didn=E2=80=99t change anything and I logged out/in
from Wunderground and explicitly typed in the password. That worked.
enable = true
station = KCAPOWAY177
password ="AlphaNumericDataH3Re"
# Set the following to True to have weewx use the WU "Rapidfire"
# protocol. Not all hardware can support it. See the User's Guide.
rapidfire = True
Still failing. Debug is set to 1, is there anything else that could be
useful?
David
> On Jun 21, 2020, at 11:42 AM, Tom Keffer <tkef...@gmail.com> wrote:
>
> OK, now you have an upload problem, which suggests a password problem. Make
> sure you're using the right password. Does it have any special characters in
> it? If so, enclose with quotes in weewx.conf.
>
> -tk
>
> On Sun, Jun 21, 2020 at 11:32 AM David Barto <ba...@kdbarto.org
> <mailto:ba...@kdbarto.org>> wrote:
> Curl gets a 204. So my configuration ’should’ be working.
>
> password is set to the password I login with.
>
> Wunderfixer still returning a 503, so that is unusual.
>
> I’m now seeing.
>
> Jun 21 11:26:19 Magrathea weewx[23591]: restx: Wunderground-RF: Failed to
> publish record 2020-06-21 11:26:15 PDT (1592763975): Failed upload after 1
> tries
> Jun 21 11:26:24 Magrathea weewx[23591]: restx: Wunderground-RF: Failed to
> publish record 2020-06-21 11:26:19 PDT (1592763979): Failed upload after 1
> tries
> Jun 21 11:26:30 Magrathea weewx[23591]: restx: Wunderground-RF: Failed to
> publish record 2020-06-21 11:26:25 PDT (1592763985): Failed upload after 1
> tries
> Jun 21 11:26:35 Magrathea weewx[23591]: restx: Wunderground-RF: Failed to
> publish record 2020-06-21 11:26:29 PDT (1592763989): Failed upload after 1
> tries
> Jun 21 11:26:40 Magrathea weewx[23591]: restx: Wunderground-RF: Failed to
> publish record 2020-06-21 11:26:35 PDT (1592763995): Failed upload after 1
> tries
> Jun 21 11:26:45 Magrathea weewx[23591]: restx: Wunderground-RF: Failed to
> publish record 2020-06-21 11:26:39 PDT (1592763999): Failed upload after 1
> tries
> Jun 21 11:26:50 Magrathea weewx[23591]: restx: Wunderground-RF: Failed to
> publish record 2020-06-21 11:26:45 PDT (1592764005): Failed upload after 1
> tries
> Jun 21 11:26:55 Magrathea weewx[23591]: restx: Wunderground-RF: Failed to
> publish record 2020-06-21 11:26:49 PDT (1592764009): Failed upload after 1
> tries
> Jun 21 11:27:00 Magrathea weewx[23591]: restx: Wunderground-RF: Failed to
> publish record 2020-06-21 11:26:55 PDT (1592764015): Failed upload after 1
> tries
> Jun 21 11:27:05 Magrathea weewx[23591]: restx: Wunderground-RF: Failed to
> publish record 2020-06-21 11:27:01 PDT (1592764021): Failed upload after 1
> tries
>
> And https://www.wunderground.com/dashboard/pws/KCAPOWAY177
> <https://www.wunderground.com/dashboard/pws/KCAPOWAY177> still reports
> ‘offline’.
>
> I’ve got ‘debug = 1’ in my configuration, so what else would be useful to
> include to finish this up?
>
> David
>
>> On Jun 21, 2020, at 10:48 AM, Tom Keffer <tkef...@gmail.com
>> <mailto:tkef...@gmail.com>> wrote:
>>
>> Blank page is probably good, and hopefully means that it's accepting the API
>> key. To be sure, try curl:
>>
>> curl -i
>> 'https://api.weather.com/v2/pws/observations/all/1day?stationId=KCAPOWAY177&format=json&units=m&apiKey=XXXXX
>>
>> <https://api.weather.com/v2/pws/observations/all/1day?stationId=KCAPOWAY177&format=json&units=m&apiKey=XXXXX>'
>>
>> where, again, XXXXX is your API key. This will give you the returned status
>> code. I would expect 204.
>>
>> NB: the API key is necessary to download data, the password is necessary to
>> upload data. So, you want the API key.
>>
>> -tk
>>
>> On Sun, Jun 21, 2020 at 9:48 AM David Barto <ba...@kdbarto.org
>> <mailto:ba...@kdbarto.org>> wrote:
>> Weird, when presented my very long API key I get back a blank page. I’ll
>> assume that is good. When I give it the short key I get back
>>
>>
>> {"metadata":{"transaction_id":"##############"},"success":false,"errors":[{"error":{"code":"CDN-0001","message":"Invalid
>> apiKey."}}]}
>>
>> What debugging do I need to turn on (and where to look on the Mac) to see
>> the URL being sent when I’m using wunderfixer to see what it is sending?
>>
>> David
>>
>>
>>> On Jun 21, 2020, at 9:25 AM, Tom Keffer <tkef...@gmail.com
>>> <mailto:tkef...@gmail.com>> wrote:
>>>
>>> Odds are it's a WU thing.
>>>
>>> If you're comfortable manipulating URLs, you can try a GET request
>>> directly. Use the URL
>>>
>>> https://api.weather.com/v2/pws/observations/all/1day?stationId=KCAPOWAY177&format=json&units=m&apiKey=XXXXX
>>>
>>> <https://api.weather.com/v2/pws/observations/all/1day?stationId=KCAPOWAY177&format=json&units=m&apiKey=XXXXX>
>>>
>>> where XXXXX is your API key. Sometimes this will give you additional detail.
>>>
>>> Interestingly, when I try the above with my own API key, I get a 204 ("No
>>> Content") error, not a 403.
>>>
>>> -tk
>>>
>>>
>>>
>>> On Sun, Jun 21, 2020 at 8:58 AM David Barto <ba...@kdbarto.org
>>> <mailto:ba...@kdbarto.org>> wrote:
>>> The key, password, and API all match with the station name.
>>>
>>> When I look at the station under
>>> https://www.wunderground.com/member/devices
>>> <https://www.wunderground.com/member/devices> -> My Devices, it shows
>>> Offline.
>>>
>>> I’m assuming that is because I’m not sending data rather than some other
>>> step in the setup process that I’m not able to discern. Web searches don’t
>>> show any registration steps that I’ve missed.
>>>
>>> Is it just a WU thing, or am I really just missing something obvious?
>>>
>>> David
>>>
>>>> On Jun 20, 2020, at 5:59 PM, Tom Keffer <tkef...@gmail.com
>>>> <mailto:tkef...@gmail.com>> wrote:
>>>>
>>>> Normally, if you give the wrong API key, you get a 401 error. You are
>>>> getting a 403 error, which implies that the key may be right, but you do
>>>> not have authorization to access the data. Are you sure you have the right
>>>> station?
>>>>
>>>> Also, double check the API key. You can find it here
>>>> <https://www.wunderground.com/member/api-keys>. Does it match what you
>>>> have in weewx.conf?
>>>>
>>>> -tk
>>>>
>>>> On Sat, Jun 20, 2020 at 5:39 PM David Barto <ba...@kdbarto.org
>>>> <mailto:ba...@kdbarto.org>> wrote:
>>>> I’ve got a new Station KCAPOWAY177
>>>>
>>>> I’ve got an API key <very long string> and a ‘key’ <8 alpha numeric key>
>>>> and my password to log into the site.
>>>>
>>>> No matter which of the 3 I choose for my password, the response to
>>>> wunderfixer is always the same.
>>>>
>>>> $ ./bin/wunderfixer --test --config=$(pwd)/weewx.conf
>>>> --station=KCAPOWAY177 —password=<pick any one> --verbose
>>>> Using configuration file /Users/Shared/weewx/weewx.conf.
>>>> Using database binding 'wx_binding', which is bound to database
>>>> 'archive_sqlite'
>>>> Weather Underground Station: KCAPOWAY177
>>>> Date to check: 2020-06-20
>>>> Number of archive records: 1055
>>>> Unable to open Weather Underground station KCAPOWAY177 or HTTP Error
>>>> 403: Forbidden
>>>> Could not get Weather Underground data. Exiting.
>>>>
>>>>
>>>> Any idea of where to go now?
>>>>
>>>> David
>>>>
>>>>
>>>> --
>>>> 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
>>>> <mailto:weewx-user+unsubscr...@googlegroups.com>.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/weewx-user/4DA82895-538B-4EC3-9D85-4E148E4CFB29%40kdbarto.org
>>>>
>>>> <https://groups.google.com/d/msgid/weewx-user/4DA82895-538B-4EC3-9D85-4E148E4CFB29%40kdbarto.org?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 weewx-user+unsubscr...@googlegroups.com
>>>> <mailto:weewx-user+unsubscr...@googlegroups.com>.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEAE940H%3DAuHD30LC_Zx2oC1Myv041LbRGGv5hVshaxWQg%40mail.gmail.com
>>>>
>>>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEAE940H%3DAuHD30LC_Zx2oC1Myv041LbRGGv5hVshaxWQg%40mail.gmail.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 weewx-user+unsubscr...@googlegroups.com
>>> <mailto:weewx-user+unsubscr...@googlegroups.com>.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/ECC4C459-B688-49DD-B5E0-63EF36ED6DC6%40kdbarto.org
>>>
>>> <https://groups.google.com/d/msgid/weewx-user/ECC4C459-B688-49DD-B5E0-63EF36ED6DC6%40kdbarto.org?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 weewx-user+unsubscr...@googlegroups.com
>>> <mailto:weewx-user+unsubscr...@googlegroups.com>.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEBq5qNWc7JBW8bJijbmCCmhDTKNoOYEondU7EOSmiduVA%40mail.gmail.com
>>>
>>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEBq5qNWc7JBW8bJijbmCCmhDTKNoOYEondU7EOSmiduVA%40mail.gmail.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 weewx-user+unsubscr...@googlegroups.com
>> <mailto:weewx-user+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/EA981147-7FDC-40F5-B1BA-4BC55769D48A%40kdbarto.org
>>
>> <https://groups.google.com/d/msgid/weewx-user/EA981147-7FDC-40F5-B1BA-4BC55769D48A%40kdbarto.org?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 weewx-user+unsubscr...@googlegroups.com
>> <mailto:weewx-user+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEC0NLVriMbOUNLs8JP%3DHic4ybUOnqfGSPL2De1CjnGPOQ%40mail.gmail.com
>>
>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEC0NLVriMbOUNLs8JP%3DHic4ybUOnqfGSPL2De1CjnGPOQ%40mail.gmail.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 weewx-user+unsubscr...@googlegroups.com
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/5D0D970D-B82F-46C1-A947-A353F81B0E2C%40kdbarto.org
>
> <https://groups.google.com/d/msgid/weewx-user/5D0D970D-B82F-46C1-A947-A353F81B0E2C%40kdbarto.org?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 weewx-user+unsubscr...@googlegroups.com
> <mailto:weewx-user+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEBstfSSwpuZGcjjT1Q02u%2BJpw%3DaLgf90f%3Dx4OMyQkze8A%40mail.gmail.com
>
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEBstfSSwpuZGcjjT1Q02u%2BJpw%3DaLgf90f%3Dx4OMyQkze8A%40mail.gmail.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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/39383749-1A52-4013-A7E2-D04992998AE6%40kdbarto.org.
