Support for AccuWeather API?

Gathering Feedback

Follow

drmm8

June 20, 2019 22:50

Any plans to support the AccuWeather API? It has 50 free calls per day which should be plenty.

https://www.developer.accuweather.com/packages

1

• 

  RainMachine Nicholas October 15, 2020 07:47

  Taking this into account for future updates.

  1

  Comment actions Permalink
• 

  weatherzone83 August 04, 2021 19:23 (Edited August 04, 2021 19:33)

  I have just completed the development of a parser for AccuWeather and would be more than happy to share it, if there is any interest in it. It is posted on https://github.com/gitzone83/accuweather.rainmachine

  0

  Comment actions Permalink
• 

  Vasco Mesquita August 04, 2021 21:54

  Hello, thanks for sharing.

   

  Just some quick notes:

  * I think the the parser uses a forecast api, so it should be tagged has "Weather Forecast" and not as "Weather Stations".

  * I'm getting the error

  Error while connecting to http://dataservice.accuweather.com/forecasts/v1/daily/5day/locationKey=879789, error: HTTP Error 400: Bad Request

  because I'm afraid the correct URL service path is http://dataservice.accuweather.com/forecasts/v1/daily/5day/{locationKey} without the "locationKey=" string according to the api documentation: AccuWeather APIs | 5 Days of Daily Forecasts

  0

  Comment actions Permalink
• 

  weatherzone83 August 04, 2021 22:26

  Thank you, Vasco

  I will re-tag the parser so that it shows as "forecast" and not "stations". You're right there and I missed the fact when working off a weather station parser example. 

  As far as the URL error is concerned. I confirmed and the URL works just fine and I do get full JSON back. I just stripped by API key, but left the location key intact: http://dataservice.accuweather.com/currentconditions/v1/locationKey=35045_PC?apikey=<my-api-key>&details=true. It does seem that the API is not parsing the input correctly, since I am able to get the same correct JSON with http://dataservice.accuweather.com/currentconditions/v1/35045_PC?apikey=<my-api-key>&details=true. I will strip the extra "locationKey=" statement since it does not seem to be needed. 

  However, you're getting Error 400 likely because the location key is wrong. Did you obtain 879789 from the internal API?

  0

  Comment actions Permalink
• 

  Vasco Mesquita August 04, 2021 22:37

  The location key I used was just an example. I tried the parser after removing the “locationKey=“ string and it worked just fine, with my proper location ofc

  0

  Comment actions Permalink
• 

  RainMachine Nicholas August 05, 2021 05:32

  Thank you for your contribution ! The next update will include a lot of changes on how we install/update community parsers. It will be a great addition with your permission.

  The current list of community parsers: https://github.com/sprinkler/rainmachine-developer-resources/blob/master/version-metadata.json

   

  0

  Comment actions Permalink
• 

  weatherzone83 August 05, 2021 13:01

  Permission granted, Nicholas. All I ask is that it is credited by linking to the original source. Thank you!

  0

  Comment actions Permalink
• 

  RainMachine Nicholas August 06, 2021 09:20

  Thank you ! Your weather service has been integrated here: https://github.com/sprinkler/rainmachine-developer-resources

  It might have gone through some changes in the source code and it will be great if you could send us a pull request against this repository for any future updates.

  0

  Comment actions Permalink
• 

  weatherzone83 August 08, 2021 20:21

  I will keep you posted for sure 

  0

  Comment actions Permalink

Please sign in to leave a comment.