-
Notifications
You must be signed in to change notification settings - Fork 15
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
Idea: Alternative weather providers #47
Comments
Is there a particular one of these that you are keen on supporting? I'm pretty happy already with the forecasts from Weather Underground, at least in the US. |
I've been using forecaswatch2 for just a day, and WU seems to be working fine as well. (I used the older watchface for months until it stopped working.) I am confused by what you mean "hacky workaround" on the README page. I thought you were scraping the website or using a non-official API. I thought the hacky workaround was unstable. If it is stable enough, then there isn't much to do here in this issue. This issue is mostly a suggestion/research of alternative providers, in case WU and DarkSky stop working. If I were to choose to implement extra providers, I'd go for the first two. (met.no seems reliable and widely used in Home Assistant; while OpenWeatherMap should be simple to implement, based on existing DarkSky code.) |
The current implementation has been stable for the past year or so, but if it breaks at some point I'll look into those suggestions :) |
@denilsonsa or @mattrossman please could you update the description to mark OpenWeatherMap as completed and available in v1.19? |
Done, updated the description with checkboxes. |
Instead of scraping, the watchface could try some well-supported API. Examples:
You may even want to take a look at the weather services already implemented in Home Assistant.
The text was updated successfully, but these errors were encountered: