Weather.Darksky with daily forecast

Share your Projects! Dashboards & Frontend
1

image
image750×868 127 KB
I use weather.darksky:

#  configuration.yaml entry
weather:
  - platform: darksky
    api_key: YOUR_API_KEY

and in the ui-lovelace.yaml

- type: weather-forecast
  entity: weather.dark_sky

like this one: https://www.home-assistant.io/lovelace/weather-forecast/

My problem is that the forecast on the card is hourly- but not daily. Is it possible to change it to daily forecast?

Thank you

2
3 Likes
3

Is the mode (daily/hourly) implemented now? In the official doc, the is the configation variable mode listed.
But when I’m trying it in my configuration, only the hourly forecast appears.

weather:
  - platform: darksky
    api_key: YOUR_API_KEY
    mode: daily

Thank you

2 Likes
4

I’m using the mode option on 0.80.1. Works great - much easier than what was required to change it from hourly before.

Capture
Capture745×505 28.4 KB

5

Thanks for the topic! The mode option works indeed. :slight_smile:

6

To anyone who stumbles on this thread, the “mode” option does NOT work, or you will get errors like this:

Invalid config for [sensor.darksky]: [mode] is an invalid option for [sensor.darksky]. Check: sensor.darksky->mode. (See ?, line ?). Please check the docs at Removed integration - Home Assistant

It’s no wonder so many people are confused. Threads like this continue to be fully accessible even though it’s clearly inaccurate and outdated.

7

That is because you are using the sensor integration, the weather integration states mode as a valid option.

1 Like
8

To anyone who stumbles on this misleading post the “mode” option works EXACTLY as documented. If you don’t read / understand the documents you will get errors.

mode relates to the darksky platform -

NOT the darksky sensor -

they are two, different, things

1 Like
9

What is the reasoning behind the two different options that seem to give the same information?

10

I think (not sure) because the platform is quick & simple to configure, but the sensor is more customisable and can give you history of separate values.

11

For me, I run both. I use weather to populate my weather card, but I use a few items from the sensor such as the cloud_cover sensor. It returns cloud_cover as a numeric value that I use in a custom low light sensor that is in turn used with sun elevation to automatically determine if lights should be turned on when motion is detected.

12

Keep in mind that doubles the API usage, so if you are using the same API key for both you are essentially doubling your calls.

13

This is true. I only wanted the cloud_cover as a numeric percentage for automations, so that’s all I download from the sensor and only update every 15 minutes. I use the defaults for darksky weather. I average 560 API calls per day, well below the 1000 free ceiling.

In my sensor.yaml:

  - platform: darksky
    api_key: !secret darksky_api_key
    monitored_conditions:
      - cloud_cover
    scan_interval:
      # At least one of these must be specified:
      days: 0
      hours: 0
      minutes: 15
      seconds: 0
1 Like