If you’re on 0.90.x you don’t need them.
Go to Dev Tools/states 
, lookup your darksky sensors and edit the card config with these entities.
1 Like
From 0.91, anything with a _ and a day number eg _0 or _1 etc, will change to _0d , _1d etc. That is the only change you need to make and the card will work again.
1 Like
Hello David, I really appreciate your help!
I’m using Hass.io 0.90.2, can I avoid this change or can I already do it?
The change in darksky is only from 0.91 on so don’t change until you are on that.
1 Like
Solved thanks
Do I only need to change them on the Lovelace card? I added a ‘d’ to all of the entries and hard-refreshed but it’s still not coming up.
cards:
- entity_current_conditions: sensor.dark_sky_icon
entity_daily_summary: sensor.dark_sky_daily_summary
entity_forecast_high_temp_1: sensor.dark_sky_daytime_high_temperature_1d
entity_forecast_high_temp_2: sensor.dark_sky_daytime_high_temperature_2d
entity_forecast_high_temp_3: sensor.dark_sky_daytime_high_temperature_3d
entity_forecast_high_temp_4: sensor.dark_sky_daytime_high_temperature_4d
entity_forecast_high_temp_5: sensor.dark_sky_daytime_high_temperature_5d
entity_forecast_icon_1: sensor.dark_sky_icon_1d
entity_forecast_icon_2: sensor.dark_sky_icon_2d
entity_forecast_icon_3: sensor.dark_sky_icon_3d
entity_forecast_icon_4: sensor.dark_sky_icon_4d
entity_forecast_icon_5: sensor.dark_sky_icon_5d
entity_forecast_low_temp_1: sensor.dark_sky_overnight_low_temperature_0d
entity_forecast_low_temp_2: sensor.dark_sky_overnight_low_temperature_1d
entity_forecast_low_temp_3: sensor.dark_sky_overnight_low_temperature_2d
entity_forecast_low_temp_4: sensor.dark_sky_overnight_low_temperature_3d
entity_forecast_low_temp_5: sensor.dark_sky_overnight_low_temperature_4d
entity_humidity: sensor.dark_sky_humidity
entity_pressure: sensor.dark_sky_pressure
entity_summary_1: sensor.dark_sky_summary_1d
entity_summary_2: sensor.dark_sky_summary_2d
entity_summary_3: sensor.dark_sky_summary_3d
entity_summary_4: sensor.dark_sky_summary_4d
entity_summary_5: sensor.dark_sky_summary_5d
entity_sun: sun.sun
entity_temperature: sensor.dark_sky_temperature
entity_visibility: sensor.dark_sky_visibility
entity_wind_bearing: sensor.dark_sky_wind_bearing
entity_wind_speed: sensor.dark_sky_wind_speed
locale: it
static_icons: false
sunset: true
tooltip_bg_color: 'rgb( 75,155,239)'
tooltip_border_color: orange
tooltip_border_width: 3
tooltip_caret_size: 10
tooltip_fg_color: '#fff'
tooltip_left_offset: -5
tooltip_width: 100
tooltips: true
type: 'custom:dark-sky-weather-card'
type: vertical-stackYou need to change the sensors as well if you have any… I had some template sensors. Check that those new sensors exist. You’ve updated to 0.91.0?
Yep I’ve updated to 0.91.0. I don’t have any template sensors or anything else related to darksky apart from the setup info.
Hi,
how can I choose the starting day for the forecast row?
By default it shows the next 5 days. I would like to begin with today.
While I can already set the correct values if I begin with the “_0” values instead of “_1” in the config, the day names don’t reflect this.They start with FR (Friday) instead of today (Thursday).
Is there a way to configure this?
IMO. this is more elegant and space-saving than adding the same info above the forecast row. And predictions for more than 3 days in the future are inaccurate anyway.
Thanks!
1 Like
Please add feature requests to the Github page noted in the 1st post of this thread. I will look into adding this as a feature in a future update.
Until then you can change the following lines in the js file
get forecast() {
var forecastDate1 = new Date();
forecastDate1.setDate(forecastDate1.getDate()+1);
var forecastDate2 = new Date();
forecastDate2.setDate(forecastDate2.getDate()+2);
var forecastDate3 = new Date();
forecastDate3.setDate(forecastDate3.getDate()+3);
var forecastDate4 = new Date();
forecastDate4.setDate(forecastDate4.getDate()+4);
var forecastDate5 = new Date();
forecastDate5.setDate(forecastDate5.getDate()+5);
to
get forecast() {
var forecastDate1 = new Date();
forecastDate1.setDate(forecastDate1.getDate()+0);
var forecastDate2 = new Date();
forecastDate2.setDate(forecastDate2.getDate()+1);
var forecastDate3 = new Date();
forecastDate3.setDate(forecastDate3.getDate()+2);
var forecastDate4 = new Date();
forecastDate4.setDate(forecastDate4.getDate()+3);
var forecastDate5 = new Date();
forecastDate5.setDate(forecastDate5.getDate()+4);
3 Likes
This works, thank you!
What I’m I missing here? I keep getting “please define entities”. If i goto my “states” page I see all my sensors there.
I do not know what YOU are missing.
We are missing what Home Assistant version you are on and your configuration details . 
I’m running 0.91.0 I copied the darksky config from the guide to my configuration.yaml. All the sensors show up as entities.
I copied the card definition from the github to a manual card in lovelace but i keep getting “please define entities”
If you open the console (F12 in FF), you will see what is missing.
For testing i changed
entity_summary_1: sensor.dark_sky_summary_1d
to
entity_summary_1: sensor.dark_sky_summary_1
The “d” on the end is needed for 0.91.0
Is the .js file installed and referenced? Did they restart Home Assistant after defining the sensors?
There is too much information missing. Only @Alex_Yeoman knows the answers so they are the best to troubleshoot, at this point in time.
i have the following resources in my lovelace…
resources:
- type: module
url: /local/surveillance-card.js?v=3
- type: module
url: /local/button-card.js
- type: module
url: /local/slider-entity-row.js
- type: module
url: /local/mini-media-player-bundle.js
- url: /local/custom_ui/dark-sky-weather-card.js?v=7.1
type: module
the dark sky is in the custom_ui folder. My other custom cards are currently working. Ive restarted home assistant several times since defining the sensors. Maybe I’m not creating the card correctly.
see this statement from above:
check your forecast, etc sensors to see if they have the ‘d’ (or ‘h’, etc) on the end.
If they do then make sure your config entries also have the ‘d’ (or ‘h’, etc) on the end.
Thanks for your guys help…I missed something stupid. I forgot to put 0 in my forecast in config.yaml
1 Like