Problem with weather components

Hello, for the last 5 days I have a problem with fetching weather data. I was using weather underground and after the problem tried dark sky but again with no luck. This is the log:

2018-04-18 18:58:48 WARNING (MainThread) [homeassistant.setup] Setup of config is taking over 10 seconds.
2018-04-18 18:58:59 ERROR (SyncWorker_17) [homeassistant.components.sensor.darksky] Unable to connect to Dark Sky. HTTPSConnectionPool(host='api.darksky.net', port=443): Max retries exceeded with url: /forecast/d32e554133ac73d199dfc0fc204c9078/42.656171322525665,23.81725014547726?units=si&lang=en (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x736f16d0>: Failed to establish a new connection: [Errno -3] Try again',))
2018-04-18 18:59:19 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: ClientConnectorError(-3, 'Try again')
2018-04-18 18:59:19 WARNING (MainThread) [homeassistant.components.sensor] Platform wunderground not ready yet. Retrying in 60 seconds.

hassio has internet and I can ping from the terminal the url-s with no problem

Same problem here, but sadly no answer :frowning:

can you post your darksky config in configuration.yaml ?

Here are mine:

Weather prediction

sensor:

  • platform: wunderground
    api_key: xxxxxxxxxx
    monitored_conditions:

    • temp_high_record_c
    • temp_high_1d_c
    • temp_c
    • temp_low_1d_c
    • temp_low_record_c
    • precip_1d
    • precip_1d_mm
    • wind_kph
    • wind_1d_kph
    • alerts
    • weather_1d_metric
    • weather_1n_metric
    • weather_2d_metric
    • weather_2n_metric
    • weather_3d_metric
    • weather_3n_metric
    • weather_4d_metric
    • weather_4n_metric
  • platform: darksky
    api_key: xxxxxxxxxx
    monitored_conditions:

    • summary
    • icon
    • nearest_storm_distance
    • temperature
    • daily_summary

0rn0f do you have pi-hole installed?

Weather underground was working fine until it started to throw this error.

Yes I have pi-hole installed. But I think it worked a few days or even weeks with it. Im not sure anymore. But I think tried to disable it but the result was the same.

With me it’s the same. Had pi-hole for weeks without problem. Tried disableing it also, still the same. I’ll change the dns server to be sure it’s not pi-hole.

The only error I have from dark_sky in my log file is this from a few days ago

2018-04-13 23:02:36 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.dark_sky_visibility is taking over 10 seconds
2018-04-13 23:02:57 WARNING (MainThread) [homeassistant.components.sensor] Updating darksky sensor took longer than the scheduled update interval 0:00:30

so I think your problems are more likely to be local.

Having the same issue. I had some other issues that caused me to do a fresh install of HASS. When setting up again, Dark Sky is not working and gives the same error as OP. I’m having a similar issue with my Total Connect alarm control panel.

@TeNpoLe21
Do you use pi-hole?

I did, but I actually removed it before I started over. I updated my DNS entries on my router as well to remove my pi-hole box as primary DNS.

So, no solution in sight?

OK, so i found the answer if youre using pi-hole.
You need to assing a static ip with an other DNS server than the pi-hole.

  1. Mount the SD card on your pc
  2. Move to the folder ‘/system-connections’
  3. Edit the sample file and copy and paste the following if youre using a wired connection:
    (dont forget the change it to your own network parameters :wink: )
[connection]
id=resin-ethernet
type=ethernet
interface-name=eth0
permissions=
secondaries=

[ipv4]
address1=192.168.1.123/24,192.168.1.1;
dns=8.8.8.8;8.8.4.4;
dns-search=
method=manual

After that, i renamed the file to ‘resin-ethernet’ and put the card back in the pi.
Dark Sky is now working again :tada:

Hassio is now using the IP 192.168.1.123, the gateway 192.168.1.1 and the google DNS servers.

Can someone give more clear information how to do it on Hasio?

Are you using the pi-hole add-on? or a standalone pi-hole?

I’m getting the same error as OP, but can’t seem to find a system-connections folder, I think it is part of the add-on and I’m not seeing it because I run pihole on a standalone pi. Do you have any suggestions on how to fix the error?

I think the system-connections folder was found on the SD card in the old resinOS days.
But that changed with the new hassOS i think. Check the documentation for more infos.
Seems like you can also set a static ip via ssh now.