-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
Forecast.io SSL errors #3600
Comments
Having the same issue. The server is exposing a certificate with a primary subject of "CN=darksky.net" with a crapload of subjectAltNames. I'm wondering if the requests module is properly handling that. |
Seeing the same errors in my HASS log, running version 0.28.2. It seems Forecast.io changing their name to Dark Sky is already causing issues with the component... |
My guess is that this could be fixed with #3470 when the dependency is up-to-date. |
Seems like this may of been the cause, at least with all the SSL errors? http://status.darksky.net/2016/09/28/downtime-incident.html |
Ah, indeed. The last SSL error for Forecast.io in my HASS log was almost 8 hours ago. |
I'm going to close this as I'm no longer seeing the error anymore, and based on the message, it does appear to be related to the downtime incident that was reported. |
Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (
hass --version
):0.29.3
Python release (
python3 --version
):3.4.2
Component/platform:
components/sensor.forecast
Description of problem:
The component appears to still be working fine, I have weather data showing in HASS, however, the logs keep showing these errors. (pasted below)
Expected:
No errors
Problem-relevant
configuration.yaml
entries and steps to reproduce:Traceback (if applicable):
Additional info:
The text was updated successfully, but these errors were encountered: