Problem with new Weatherlink (2.0)

[AbeteBianco]

In the coming months Weatherlink.com will be brought to version 2.0 (https://www.davisnet.com/weatherlink/), new users already use it.
I know that in the transition from 1.0 to 2.0 many weather networks have encountered problems, and they had to create a specific system for connect their stations to new Weatherlink 2.0 introduced in November 2017.

With the 2.0 version, the request of User and Password didn't work. Now for 2.0 version those networks require Weatherlink Device ID (DID) and Device Key, and not User and Password as in the classic version 1.0 and in the WLIP plugin necessary for upload data on Meteotemplate.

Because all users of Weatherlink IP will be migrated on that system soon, it's very probably that the WLIP plugin become complettly unusable from everyone!

A plugin update would be needed.

In my opinion the problem is quite simple to solve, but of course I'm not a developer.

Are there any users like me who use this system? What do you think?

Thank you.

Best regards

[Jachym]

Given I do not have WL I guess this is something I will deal with once the changes are made. Unless there are detailed instructions somewhere and possibility to test the upcoming version there is not much I can do at this point.

[AbeteBianco]

At the moment it is just a discussion because there is still time before the change. However on internet I found discussions very similar to the problem mentioned. They can be a starting point (or maybe the solution).

https://www.wxforum.net/index.php?topic=31970.0

https://www.wxforum.net/index.php?topic=33601.0

Eventually I could contact a friend who can provide us with his version 2.0 credentials to test.

[Jolumarali]

Bonjour
cette Url installé sur site (Prévimeteo.com) Testée et fonctionne OK
http://api.weatherlink.com/v1/NoaaExt.x ... oken=_KEY_

amitiés

José Luis

[AbeteBianco]

Bonjour
cette Url installé sur site (Prévimeteo.com) Testée et fonctionne OK
http://api.weatherlink.com/v1/NoaaExt.x ... oken=_KEY_

amitiés

José Luis

The plugin modified by me seems to work with Weatherlink 2.0.

The link XML to use is:

http://api.weatherlink.com/v1/NoaaExt.x ... Token=_KEY

The user need to insert DID, PASSWORD and KEY, changes little compared with the current structure of the WLIP plugin.

Someone can check if the structure of my files are free of bugs?

Thanks

[jntkwx]

I received this email from Davis on Monday, June 18, 2018:

As our move to WeatherLink 2.0 proceeds, we are approaching an important update that will affect anyone using the WeatherLink 1.0 API. This may affect you if you use the current API to:
• Display data on a personal or community web page.
• Share data with a 3rd party service that is dependent on the API.
• Access your weather data from our servers.

The current www.weatherlink.com/xml.php API is scheduled to be decommissioned at the end of July, 2018. The new api.weatherlink.com/v1, available in JSON and XML formats, will be the ONLY functioning API after July 2018. This API works for WeatherLink 1.0 and 2.0 and can be used immediately, but it requires the use of a unique API token.

To generate a unique API token: Watch the Generate API Token video

1. Log in to WeatherLink 2.0 using existing WeatherLink user credentials.
2. Access the account information in the right sidebar, under the username and account picture.
3. On the account information page, click Generate API Token.
4. Fill in the required fields and click the Generate button.
5. The unique API token will display in the API Token field.

These important changes will help us make continual improvements to the API so that you can access your personal weather station data or share it with 3rd party services faster and with maximum reliability.

If you are aware of any person or 3rd party that may use the WeatherLink 1.0 API, please help us spread the news of the upcoming changes.

Thank you,
All of us at Davis Instruments

----------------------

According to Davis' API documentation, the format for the API call to generate output in XML format is a URL that looks like: .

Code: Select all

https://api.weatherlink.com/v1/NoaaExt.xml?user=DID&pass=ownerPW&apiToken=tokenID

The DID (Device ID) should be listed on the online WeatherLink account, under My Account, and also printed on a sticker on the WeatherLinkIP dongle. The password is the same as your WeatherLink password, and the tokenID is the API token that now has to be generated.

I sent Davis support an email asking about how someone with an existing WeatherLink 1.0 account can generate an API token (the video assumes the user is logging into the new WeatherLink 2.0 website). I received an automated reply that they are getting a lot of inquiries about the new API. I will reply back here once I get an update.

[akiro]

Need the WL IP Plugin 4.0 and wIIPupdate2.php to be extended or customized to work with the new API and if so how and when will it be done?

regards
Daniel

[weather display]

the only change I would would be you get your api token code and use that in place of the Key (or is it the password)?

[weather display]

actually the api token is used instead of what was the key (from the side of the IP data logger)

[akiro]

So far I understand that. My question is now where do I have to replace the key by the api token (with wlIP username or wlIP password or at the weatherlink homepage ...)

[AbeteBianco]

My station now updates on meteotemplate using the new Weatherlink API with DID, Password account and API token (generated on the Weatherlink website).

You can see these credentials in the Weatherlink 2.0 account settings.

[jntkwx]

So far I understand that. My question is now where do I have to replace the key by the api token (with wlIP username or wlIP password or at the weatherlink homepage ...)

I know I am replying to a very old post, but if anyone else has this question/problem, since version 4.0 of the WL-IP Updates plugin has not yet (as of this post) been updated for the new WeatherLink 2.0 API, I had to edit two files to make WeatherLink 2.0 work with Meteotemplate:

1. First, if you have not done so already, set up the WL-IP Uploads plugin in your control panel, and click the Save button. Doing this creates or modifies a settings.php file. Manually edit the settings.php file by adding the following two variables to the template_root/plugins/wlIP/settings.php file:

Code: Select all

$DID = 'fill in device ID';
$tokenID = 'fill in new API token';

Notes:

• the dollar sign $ the single quotes ' and the colon ; are required characters.
• Ensure that there is no space between the characters in the DID and the tokenID and the single quotes.
• The $userName variable is no longer required. Therefore, you can keep the $userName line in the settings.php file, or delete that line (I chose to keep it, so I could remember what my WeatherLink username is).

As I mentioned in my previous post, the DID (device ID) can be found by logging into your Weatherlink.com account, click on the wrench icon in the upper righthand corner of the screen, and you'll see your Device Info, including your Device ID (the Device ID is also printed on a sticker on the WeatherLink-IP dongle). To my knowledge, if you previously had a WeatherLink 1.0 account, your data should now have been successfully imported into the new WeatherLink 2.0 website. You should be able to login to weatherlink.com with your existing Weather Link 1.0 username and password (note that this wasn't true in the spring of 2018 when I initially tried this).

To create or view your API Token, while logged into your Weatherlink.com account, click on the person icon in the upper righthand side of the screen. If you have previously requested a WeatherLink 2.0 API token, you'll see it listed on this page. If you have not requested a WeatherLink 2.0 API token, click the link to generate an API token, fill in the requested information (first name, last name, email, phone number, country, state), and an API token will be automatically generated for you. You'll receive an email confirmation almost immediately when this is complete.

2. Manually edit the line immediately after the "get data" line in the template_root/plugins/wlIP/wlIPupdate.php file so that it matches the new WeatherLink 2.0 API request format:

Code: Select all

$url = "https://api.weatherlink.com/v1/NoaaExt.xml?user=".$DID."&pass=".$WLPass."&apiToken=".$tokenID;

Note that the order of quotation marks " dollar signs $ periods . and the colon ; must match the line above. You could copy the line above and replace the existing line in your wlIPupdate.php file.

After doing this, and setting a CRON job to wlIPupadte.php, using your admin password like this: .../plugins/wlIP/wlIPupdate.php?pass=YOUR_UPDATE_PASSWORD you should see your current data being automatically updated.