Skip to content

Add Dark Sky documentation #992

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Oct 5, 2016
Merged

Add Dark Sky documentation #992

merged 5 commits into from
Oct 5, 2016

Conversation

fabaff
Copy link
Member

@fabaff fabaff commented Sep 26, 2016

With the name change the forecast platform will be deprecated and replaced by the dark_sky sensor platform.


The `dark_sky` platform uses the [Dark Sky](https://darksky.net/) web service as a source for meteorological data for your location. The location is based on the `longitude` and `latitude` coordinates configured in your `configuration.yaml` file. The coordinates are auto-detected but to take advantage of the hyper-local weather reported by Dark Sky, you can refine them down to your exact home address. GPS coordinates can be found by using [Google Maps](https://www.google.com/maps) and clicking on your home or [Openstreetmap](http://www.openstreetmap.org/).

You need an API key which is free but requires [registration](https://developer.forecast.io/register). You can make up to 1000 calls per day for free which means that you could make one approximately every 86 seconds.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Link should probaly be https://darksky.net/dev/register

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks


Configuration variables:

- **api_key** (*Required*): Your API key for http://forecast.io/.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

@@ -9,10 +9,14 @@ sharing: true
footer: true
logo: forecast.png
ha_category: Weather
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Category should probably be updated to Deprecated

Copy link
Member Author

@fabaff fabaff Sep 26, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. The platform would still work till the EOL of forecast.io but I guess that it would be simpler to get rid of the platform as soon the dependency is available.

@Landrash
Copy link
Contributor

Looks good! 🐬

@fabaff
Copy link
Member Author

fabaff commented Sep 27, 2016

I guess that we need to merge in the changes from #990 as those are going to the Forecast page.

@Landrash
Copy link
Contributor

This is the bigger change and should have priority.
#990 is a small addition and can be added afterwards. I can do that after this one is merged.
The Darksky change will wait until 0.30 or will you push it into 0.29?

@fabaff
Copy link
Member Author

fabaff commented Sep 29, 2016

We are waiting for the dependency and Paulus released 0.29 a couple of hours ago. So, it will be in 0.30 (i guess) but not sure if there is enough time to make it available as Weather component ;-)

@robbiet480
Copy link
Member

@fabaff @Landrash what's the status on this / #990? Good to merge?

@fabaff
Copy link
Member Author

fabaff commented Oct 3, 2016

First we need a new python-forecastio release.

@fabaff fabaff merged commit 55e6b5e into home-assistant:next Oct 5, 2016
@fabaff fabaff deleted the forecast-darksky branch October 5, 2016 22:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants