You have absolutely right! That wasn’t error in card config, but in darksky sensor. My config in forecast part was starting from 1, not from 0. Thats why there was no
sensor.dark_sky_overnight_low_temperature_0
Thank you! 
1 Like
change update_interval to scan_interval… there was a breaking change in the release notes for this!
It still gives error for the other two entities but did remove the update_interval.
It still doesn’t like forcast and monitored conditions…
I have yet to see this card, never shows up 
well you haven’t bothered to format your code so it’s a bit hard to see what you are doing wrong with that
Yeah couldn’t format my post properly, anyhow the issue was that I had to place the code under sensor: and not weather:
Can someone see my problem?
i try it with the lovelace-Editor (i think this thing is very helpful)
i load the sensor (with the scan_interval - Update)
- platform: darksky
api_key: xxx
language: de
forecast:
- 1
- 2
- 3
- 4
- 5
monitored_conditions:
- icon
- summary
- nearest_storm_distance
- nearest_storm_bearing
- humidity
- temperature
- temperature_high
- temperature_low
- apparent_temperature
- apparent_temperature_high
- apparent_temperature_low
- wind_speed
- wind_bearing
- precip_type
- precip_probability
- precip_accumulation
- precip_intensity
- precip_intensity_max
- uv_index
- daily_summary
- pressure
- visibility
scan_interval:
minutes: 5
i create a “manuel card”
type: 'custom:dark-sky-weather-card'
entity_sun: sun.sun
entity_daily_summary: sensor.dark_sky_daily_summary
entity_current_conditions: sensor.dark_sky_icon
entity_humidity: sensor.dark_sky_humidity
entity_pressure: sensor.dark_sky_pressure
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
entity_forecast_high_temp_1: sensor.dark_sky_daytime_high_temperature_1
entity_forecast_high_temp_2: sensor.dark_sky_daytime_high_temperature_2
entity_forecast_high_temp_3: sensor.dark_sky_daytime_high_temperature_3
entity_forecast_high_temp_4: sensor.dark_sky_daytime_high_temperature_4
entity_forecast_high_temp_5: sensor.dark_sky_daytime_high_temperature_5
entity_forecast_low_temp_1: sensor.dark_sky_overnight_low_temperature
entity_forecast_low_temp_2: sensor.dark_sky_overnight_low_temperature_1
entity_forecast_low_temp_3: sensor.dark_sky_overnight_low_temperature_2
entity_forecast_low_temp_4: sensor.dark_sky_overnight_low_temperature_3
entity_forecast_low_temp_5: sensor.dark_sky_overnight_low_temperature_4
entity_forecast_icon_1: sensor.dark_sky_icon_1
entity_forecast_icon_2: sensor.dark_sky_icon_2
entity_forecast_icon_3: sensor.dark_sky_icon_3
entity_forecast_icon_4: sensor.dark_sky_icon_4
entity_forecast_icon_5: sensor.dark_sky_icon_5
and edit with the “RAW-Configurationeditor” the ui-lovelace
i don’t receive any errors?
You need to set resource type as module
Add - 0 to forecast as well.
1 Like
Is there a way to hide the future forecasts? I want to hide them and just have the current condition and temp. I’ve hidden the other elements, just kind of stuck having the future forecasts.
I am a newbie.
Adding tooltips gives me the forecast summmaries. Add
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: -12
tooltip_width: 100
tooltips: trueand where?
To your card in the UI Editor.
See https://github.com/iammexx/home-assistant-config/blob/master/ui/darksky/README.md
ahh!
i add:
entity_sun: sun.sun
entity_visibility: sensor.dark_sky_visibility
entity_daytime_high: sensor.dark_sky_daytime_high_temperature_0
entity_wind_bearing: sensor.dark_sky_wind_bearing
entity_wind_speed: sensor.dark_sky_wind_speed
entity_humidity: sensor.dark_sky_humidity
entity_pressure: sensor.dark_sky_pressure
entity_apparent_temp: sensor.dark_sky_apparent_temperature
entity_daily_summary: sensor.dark_sky_daily_summary
entity_pop: sensor.dark_sky_precip_probability
entity_pop_intensity: sensor.dark_sky_precip_intensity
entity_pop_1: sensor.dark_sky_precip_probability_1
entity_pop_2: sensor.dark_sky_precip_probability_2
entity_pop_3: sensor.dark_sky_precip_probability_3
entity_pop_4: sensor.dark_sky_precip_probability_4
entity_pop_5: sensor.dark_sky_precip_probability_5
and now it’s work! thanks!
1 Like
Hello,
Sorry for the late reply. I was able to test it only today.
So, I have updated to Hass.io 0.88.2 and used the latest version of the card (0.10.2) and still have issues with automatic update.
The chrome debugger throws me these errors
Hope it can be helpful to solve this problem !
I got the TypeError messages. It appears to be about some Polymer elements remaining in Lovelace.
See https://github.com/home-assistant/home-assistant-polymer/issues/2095
OK, So that helps narrow it down…
based on the exception it looks like the issue is on line 735 which is this:
if (this.config.entity_pop && !this.config.alt_pop) { root.getElementById("pop-text").textContent = `${Math.round(this._hass.states[this.config.entity_pop].state)}` }
So that line is looking to find the “pop” current value somewhere in the card. Its doing that because you have entity_pop defined in your configuration.
The issue I see based on your screen shot of the card is that you are not showing “pop”. I am guessing you are using the slot configuration flags for all eight slots with some of them set to “empty” or “remove” and none of them set to “pop”.
Therefore you are telling the card you want to use pop but then not showing it. Remove the entity_pop: line from your configuration and see if that helps. Based on your card screen shot you should also make sure you are not defining any of the other optional entities that you are not showing. (entity_sun and entity_daytime_high) as they will have the same issue.
In a future version of the card I will add some logic to prevent it from trying to update items that are intentionally hidden while still being configured.
2 Likes
Yes ! That was it ! thank you so much for your help and patience !
I would like to suggest you two things to improve your card:
- “Feels like” translation in French should be “Température ressentie” or simply “Ressenti”
- What about a card “name” or “title” to add the location on top of the card ?
Once again, thank you and great job !