Community Support

[This post is marked as unsolved] Weatherlink API key format problem  

  RSS
Kent
 Kent
(@kent)
Eminent Member

Hi

Tried to add a Davis weatherlink station, but when adding the API key it's cut after 20 characters, seems as field for API key input only is 20 char. long..

Problem is that API key is 32 characters long, like this sample key from API doc

demo0a002bc5272033001d0a002bc527

If trying with the 20 char. i get error no such station exist, so i suppose the 32 char string is needed.

Don't know if this worked in 3.8, i tested this in 3.8.3

Br

Kent

Quote
Posted : 25/04/2019 8:27 pm
daguilera
(@daguilera)
Eminent Member

I added two Davis weather stations using 3.8.3, and both uses a 20-character long API Token obtained from WeatherLink website. Did you check if Device ID parameter (12-character long) and password are correct?

Best regards.

David.

David Aguilera-Riquelme (@davidagriq).
https://redmeteo.cl - an Open Chilean hobbyist weather network

ReplyQuote
Posted : 26/04/2019 4:00 am
Kent
 Kent
(@kent)
Eminent Member

Hi

Found the problem.

Tested the API call myself and got the same error, so it wasn't this software..

But i used # as last character in psw, when changing this it works..

/Kent

ReplyQuote
Posted : 26/04/2019 9:25 am
Pierre Lannoy
(@pierre-lannoy)
Member Admin

Hello to both of you.

I confirm this key must be 20 car long, you're right David. This demo key is a sort-of-bullshit that never worked for me 😐 

If you like Weather Station, please consider to make a review to help make it known. That would be the best way to thank me...

ReplyQuote
Posted : 26/04/2019 10:49 am
OakHammock
(@oakhammock)
New Member

I am not a programmer, just trying to use Weather Station. I have had the same problem as Kent. I have a 32 character API token and it does not fit into the slot assigned to (ADD a Station connected to Weatherlink) It only takes a 20 character Token. I do Not have a password with # or any other such special car, it ends with a lower cap letter, so changing the last character or any special character in the password is not an option, which solved his problem. I called Weatherlink and found out that I cannot change the 32 character API token to a 20 character Please can you tell me in non programmer language what I can try? I am going through  Weather Station 3.8.5  It is up to date.

ReplyQuote
Posted : 04/05/2019 9:27 pm
OakHammock
(@oakhammock)
New Member

I did not do anything and it suddenly added the station with the 20 character API number truncated from the 32 character number with no change in the psw.

ReplyQuote
Posted : 04/05/2019 9:48 pm
Kent
 Kent
(@kent)
Eminent Member

Hi

I also only get a 32 character key, but for some reason it works with the first 20 only.

Don't know if 32 is the new key format but first 20 still works as backward compability.

Check so you don't have space/blank first if you copy/ paste, and actually only get 19 as input (it was not only a bad character in psw issue i had, i also managed to do this..

/Kent

 

ReplyQuote
Posted : 04/05/2019 10:06 pm
daguilera liked
daguilera
(@daguilera)
Eminent Member
Posted by: Kent

Hi

I also only get a 32 character key, but for some reason it works with the first 20 only.

Don't know if 32 is the new key format but first 20 still works as backward compability.

Check so you don't have space/blank first if you copy/ paste, and actually only get 19 as input (it was not only a bad character in psw issue i had, i also managed to do this..

/Kent

 

It's a good thing to know!! We expect to put new Davis weather stations on our website, so I'm guess that some of these could have a 32-char-long API token.

Best regards.

David Aguilera-Riquelme (@davidagriq).
https://redmeteo.cl - an Open Chilean hobbyist weather network

ReplyQuote
Posted : 04/05/2019 10:33 pm
OakHammock
(@oakhammock)
New Member

Thanks Kent,  The station is now added.  I may have had a space before or it may have been I was using version 3.8.4 not 3.8.5.  Anyway it does take the 32 character API token in WeatherLink  by truncation to 20 characters.

Madeleine

ReplyQuote
Posted : 04/05/2019 10:42 pm
Berryguy
(@berryguy)
New Member

I just tried adding a WeatherLink Live weather station to my website today using version 3.8.9 of Weather Station and I'm having no luck getting it to work.  No matter what I do I keep getting the "Unable to access this station: no station with this credentials" error message. The API token generated by WeatherLink is 32 characrters long.  The generated password is also longer than 20 chars as well.  Both fields in Weather Station still seem to have a 20 character limit.  I don't understand why, because it's been about a year since the problem was first reported.  Why hasn't the code been changed to accept longer API  token and password values?  Anyways, I've tried replacing the 20th character of the token with # as suggested by other users, but this does not work for me. I also tried replacing the 20th charactor of the password with # as well, but that had no effect.  I've also checked to make sure that I don't have any spaces at the beginning of the token or password fields.  Can somebody suggest something else to try?   Or is it possible to quickly fix the code so that the plugin accepts longer token and password values so we don't have this problem... 🙂 

ReplyQuote
Posted : 30/05/2020 4:58 am
Berryguy
(@berryguy)
New Member

Update:  I finally got my station to add into Weather Station.  Yay!  I was confused as what password to use because the Weatherlink API has two versions.  An old V1 version which is used with WeatherLink data loggers (WeatherLinkIP, WeatherLinkUSB, and WeatherLinkSER), and Vantage Connect and only uses an API Key,  and a new V2 version for use with EnviroMonitor and WeatherLink Live (which is what I have) uses an API Key and an API Secret Key.  The V2 API has a 32 character API Key and a new API Secret Key (which seems to vary in length, but I've seen generated keys that appear longer than 32 chars).  I naturally assumed that the Weather Station setup was asking for the API Secret Key as the password (which of course didn't work).  I finally tried using the password to my Weatherlink account and that is what actually worked.  

Unfortunately, now I have run into a different problem.  Now I get an error 500 - "Inconsistent data to insert in data table", being reported by the Data Manager 3.8.9 which I've pasted below:

Inconsistent data to insert in data table: Array
(
[device_id] => wl:1d:0a:74:11:00
[device_name] => Farm Weather Station
[module_id] => wl:1d:0a:74:11:00
[module_type] => NAMain
[module_name] => Station
[measure_timestamp] => 2020-06-01 05:40:46
[measure_type] => firmware
[measure_value] =>
)

In the event log, there are two events that get generated every few minutes.  The first is a Weather Collector 3.8.9 event says that data was retrieved, and a second event from Data Manager 3.8.9 which has the above error 500 in it.

Does anybody have any idea what's going on with this or how to resolve this?  Is this possibily still related to the above API Key issue? At this point I'm not trying to do anything super complicated here.  All I want to do is to display an Outdoor Weather Summary on a webpage and unfortunately I get no data being displayed at all in the widget.  Thanks for your assistance!

ReplyQuote
Posted : 01/06/2020 8:13 am
Dinant
(@dinant)
New Member

Here the same errors.

My API Key v2 and the API Secret are both 32 charachter long.

Also the temperature, humidity, etc. are not logged.

A suggestion might be to rename the text API Token to API Secret and password to Password Weatherlink account.

ReplyQuote
Posted : 29/07/2020 10:02 pm

To participate, please connect first!