Dark Sky Sensor Not Appearing

Configuration
1

I am trying to get Dark Sky setup. I tried the Dark Sky Platform and the Sensor both with zero success.
I setup my API and used the the following in my config.yaml:

sensor:
  - platform: darksky
    api_key: !secret darksky_api_key
    name: Weather
    forecast: 
      - 1
      - 2
      - 3
    monitored_conditions:
      - summary
      - icon
      - nearest_storm_distance
      - nearest_storm_bearing
      - precip_type
      - precip_intensity
      - precip_probability
      - temperature
      - apparent_temperature
      - dew_point
      - wind_speed
      - wind_bearing
      - cloud_cover
      - humidity
      - pressure
      - visibility
      - ozone
      - minutely_summary
      - hourly_summary
      - daily_summary
      - temperature_max
      - temperature_min
      - apparent_temperature_max
      - apparent_temperature_min
      - precip_intensity_max

Nothing shows up on my overview view. I checked the UI States and Dark Sky isn’t listed.

I also tried:

#Weather From Dark Sky Project      
weather:
  - platform: darksky
  api_key: My_API

but I got the same result. I’ve tried the sensor with the API in the secrets.yaml and directly in the config.yaml with no change.

I copied the sensor config from countless tutorials (ok maybe 5 or 6) that all say the same thing and that the weather info should just ‘appear’.

I’d appreciate any help

1 Like
2

What HA version are you running?

How have you installed HA? Hass.io? Docker?

Have you checked the error log?

3

Maybe try a new API key?

4

I am running Hass.io .68.1
I am running it in a docked on Ubuntu 16.04

I don’t know how to find the error logs. I am quite familiar with *nix OS’s but this dockers thing is throwing me for a loop, smb shares and ssh running seperately from the OS which also have smb and ssh running. Black Magic I’s tell ya

5

I will give that a try later tonight

6

This works for me. Start simple, and then build up to what you need

  - platform: darksky
    api_key: !secret dark_sky 
    units: ca
    update_interval: "00:15"
    monitored_conditions:
      - precip_probability
      - temperature
      - cloud_cover
      - visibility
      - icon
7

I gave your suggestion a try and I am not seeing any dark sky items on my overview.

Maybe I am mistaken but shouldn’t I see something on the overview screen automatically?

Thanks,

8

Not necessarily. I don’t know what the criteria is for this not to happen, but I know I have to add new items specifically under the default_view group.

The most accurate way of determining if you have created an entity is to search on the states page under developer tools for dark_sky

9

I’ve checked there and I do not have a Dark Skies entry in States.
I’ve also added a Torque sensor to my config.yaml and it doesn’t show up in States either.

10

Something is wrong with your configuration - it doesn’t seem to be reading the yaml file you are writing. But I don’t have any experience with hassio, so I’ll leave somebody else to help on that.

11

That’s what I thought too.
So I went back to the config file and uncommented the old YR Weather sensor that I had commented out and put the Darksky sensor in with it and the YR weather element showed up on the Overview and in States but the Dark Sky one did not show up in States.

sensor:
  - platform: yr
    name: "Weather_Prediction"
  - platform: darksky
    api_key: My_API_#

I would assume that the config.yaml is loading properly since the YR Weather is appearing. The config Check is also not showing any errors…

12

So I just got an opportunity to peak at the home-assistant.log file I found this:

Testing configuration at /config
Failed config
sensor.darksky:
- Invalid config for [sensor.darksky]: required key not provided @ data[‘monitored_conditions’]. Got None. (See ?, line ?). Please check the docs at Removed integration - Home Assistant
- platform: darksky
api_key: My_API_Key

Successful config (partial)
sensor.darksky:

It says my key is missing but it is clearly there.

13

I think it means monitored_conditions: is missing.

14

Could be, I added back in the monitored conditions you recommended earlier and now I am getting this error:

2018-05-22 15:19:08 ERROR (SyncWorker_8) [homeassistant.components.sensor.darksky] Unable to connect to Dark Sky. HTTPSConnectionPool(host=‘api.darksky.net’, port=443): Max retries exceeded with url: /forecast/My_API_#/Latitude#,Longitude#?units=ca&lang=en (Caused by NewConnectionError(‘<urllib3.connection.VerifiedHTTPSConnection object at 0x7f6c7ebca550>: Failed to establish a new connection: [Errno -3] Try again’,))

15

You have posted 2 similar threads

16

yah, figured it might be better in hass.io since I’m running hass.io

17

I’m facing exact situation. Did you find any solution @rlongfield ?

Edit: After reseting key on Dark Sky’s web UI, It appeared on next day.

18

Hey Sercanerhan,

No I never did find a solution. I ended up switching to Home Assistant.

19

I just had the same error. My solution was to refresh the API KEY on Darksky website and changing to the new Key on my YAML.

Restart Home Assistant and error was gone.

Just in case someone else is having same error.

1 Like
20

this worked like a charm for me too! thanks

1 Like