well thats not something i can be doing 
ok i will look at using something else for the holiday location view
You could temporarily change the latitude & longitude in the configuration before you leave & revert when you get back home.
This could be accomplished with a single card by defining a template sensor for each of the sensors being passed in. The templates would need some sort of condition defined (possibly an input boolean or something based off your device’s location) that would tell the template which of the two (local or remote) dark sky sensor to use.
The drawback as has been pointed out is that it would double the number of sensors created by dark sky and you would need to make sure you didn’t over poll the api…
Hi all,
Could anyone point me in the right direction, I’ve got this now working in Safari, but when I use Chrome I get this;
What am I doing wrong?
Thanks
Safari may be using cached values to appear to work. I had that issue in the past
Unfortunately I have not done much troubleshooting on this card.
Ensure that your darksky sensors are working by checking them in the states panel of developer tools
1 Like
Hi, any news on the Finnish translation?
They all look to be working in the state panel. Also, if I look at my unused entities, they are all in there looking ok. Plus they work in Safari. just not when I use Chrome.
With Home Assistant NOT open, try clearing your cache in Chrome. I have found it can cause many strange issues.
Thanks bosborne & m p franklind, all sorted now!
1 Like
Can some one of you that have darksky running good (on an updated HA) to put your configuration, sensors, ui-lovelace, js and css file?
i have followerd this https://github.com/bramkragten/custom-ui/tree/master/weather-card
without any good result
thank you
That link uses darksky weather I think most here are using darksky sensor
my fault…thanks
If you’re interested in using darksky sensor I may be able to share an example if you need it.
1 Like
Yes, thank you
How about this? Remember to set your latitude & longitude.
From https://github.com/iammexx/home-assistant-config/tree/master/ui/darksky
configuation.yaml
# Dark Sky Sensor
- platform: darksky
api_key: !secret darksky_api_key
forecast:
- 0
- 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
# Template sensors
- platform: template
sensors:
dark_sky_alt_wind:
value_template: >-
{% set winddir = ['North','North-Northeast','Northeast','East-Northeast','East','East-Southeast','Southeast','South-Southeast','South','South-Southwest','Southwest','West-Southwest','West','West-Northwest','Northwest','North-Northwest','North'] %}
{{ states('sensor.dark_sky_wind_speed') | round }} mi/h from the {{ winddir[((states('sensor.dark_sky_wind_bearing') | float / 360)*16) | round]}}
dark_sky_current_text:
value_template: >-
{% if is_state("sensor.dark_sky_icon","clear-day") %} Clear
{% elif is_state("sensor.dark_sky_icon","clear-night") %} Clear
{% elif is_state("sensor.dark_sky_icon","rain") %} Rain
{% elif is_state("sensor.dark_sky_icon","snow") %} Snowy
{% elif is_state("sensor.dark_sky_icon","fog") %} Foggy
{% elif is_state("sensor.dark_sky_icon","sleet") %} Sleet
{% elif is_state("sensor.dark_sky_icon","wind") %} Windy
{% elif is_state("sensor.dark_sky_icon","cloudy") %} Cloudy
{% elif is_state("sensor.dark_sky_icon","partly-cloudy-day") %} Partly Cloudy
{% elif is_state("sensor.dark_sky_icon","partly-cloudy-night") %} Partly Cloudy
{% elif is_state("sensor.dark_sky_icon","hail") %} Hailing
{% elif is_state("sensor.dark_sky_icon","lightning") %} Lightning
{% elif is_state("sensor.dark_sky_icon","thunderstorm") %} Thunderstorm
{% endif %}
Now, the lovelace UI yaml. I use the UI editor.
views:
- cards:
- alt_wind: sensor.dark_sky_alt_wind
entity_forecast_low_temp_1: sensor.dark_sky_overnight_low_temperature_0
entity_humidity: sensor.dark_sky_humidity
entity_forecast_high_temp_1: sensor.dark_sky_daytime_high_temperature_1
entity_summary_2: sensor.dark_sky_summary_2
entity_pop_intensity: sensor.dark_sky_precip_intensity
entity_forecast_low_temp_2: sensor.dark_sky_overnight_low_temperature_1
entity_wind_speed: sensor.dark_sky_wind_speed
entity_forecast_icon_5: sensor.dark_sky_icon_5
entity_pop_1: sensor.dark_sky_precip_probability_1
entity_summary_4: sensor.dark_sky_summary_4
entity_apparent_temp: sensor.dark_sky_apparent_temperature
tooltip_border_width: 3
entity_forecast_low_temp_4: sensor.dark_sky_overnight_low_temperature_3
entity_summary_3: sensor.dark_sky_summary_3
entity_pop_5: sensor.dark_sky_precip_probability_5
entity_temperature: sensor.dark_sky_temperature
entity_daily_summary: sensor.dark_sky_daily_summary
entity_visibility: sensor.dark_sky_visibility
tooltip_caret_size: 10
type: 'custom:dark-sky-weather-card'
tooltip_fg_color: '#fff'
entity_forecast_high_temp_2: sensor.dark_sky_daytime_high_temperature_2
tooltip_border_color: orange
tooltip_bg_color: 'rgb( 75,155,239)'
entity_forecast_icon_3: sensor.dark_sky_icon_3
entity_forecast_icon_1: sensor.dark_sky_icon_1
entity_summary_1: sensor.dark_sky_summary_1
entity_forecast_high_temp_4: sensor.dark_sky_daytime_high_temperature_4
tooltips: true
tooltip_width: 100
entity_forecast_high_temp_5: sensor.dark_sky_daytime_high_temperature_5
entity_forecast_icon_2: sensor.dark_sky_icon_2
entity_forecast_high_temp_3: sensor.dark_sky_daytime_high_temperature_3
entity_summary_5: sensor.dark_sky_summary_5
entity_pop: sensor.dark_sky_precip_probability
entity_pop_3: sensor.dark_sky_precip_probability_3
entity_current_conditions: sensor.dark_sky_icon
entity_daytime_high: sensor.dark_sky_daytime_high_temperature_0
entity_sun: sun.sun
entity_wind_bearing: sensor.dark_sky_wind_bearing
entity_forecast_low_temp_5: sensor.dark_sky_overnight_low_temperature_4
entity_current_text: sensor.dark_sky_current_text
entity_pressure: sensor.dark_sky_pressure
entity_pop_4: sensor.dark_sky_precip_probability_4
entity_forecast_icon_4: sensor.dark_sky_icon_4
entity_forecast_low_temp_3: sensor.dark_sky_overnight_low_temperature_2
tooltip_left_offset: -12
entity_pop_2: sensor.dark_sky_precip_probability_2
1 Like
After update to 0.91.x you have to change the daily entity_id’s in your config.
https://github.com/iammexx/home-assistant-config/issues/18
Just for info!
2 Likes
Hello Guys, please help me…
After update hassio form 0.88.2 to 0.90.2 i have this problem
I use Chrome and I’ve already tried cleaning up the cache
This is my lovelace config:
resources:
- url: /local/custom_ui/dark-sky-weather-card.js?v=7.1
type: module
and…
- type: ‘custom:dark-sky-weather-card’
tooltips: true
tooltip_width: 100
tooltip_left_offset: -12
tooltip_fg_color: ‘#fff’
tooltip_caret_size: 10
tooltip_border_width: 3
tooltip_border_color: orange
tooltip_bg_color: ‘rgb( 75,155,239)’
time_format: 24
static_icons: false
show_beaufort: true
locale: it
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_apparent_temperature
entity_apparent_temp: sensor.dark_sky_apparent_temperature
entity_visibility: sensor.dark_sky_visibility
entity_wind_bearing: sensor.dark_sky_wind_bearing
entity_wind_speed: sensor.dark_sky_wind_speed
entity_daytime_high: sensor.dark_sky_daytime_high_temperature_0
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_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
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_summary_1: sensor.dark_sky_summary_1
entity_summary_2: sensor.dark_sky_summary_2
entity_summary_3: sensor.dark_sky_summary_3
entity_summary_4: sensor.dark_sky_summary_4
entity_summary_5: sensor.dark_sky_summary_5
entity_pop: sensor.dark_sky_precip_probability
entity_pop_intensity: sensor.dark_sky_precip_intensity
entity_pop_1: sensor.dark_sky_precip_probability_1d
entity_pop_2: sensor.dark_sky_precip_probability_2d
entity_pop_3: sensor.dark_sky_precip_probability_3d
entity_pop_4: sensor.dark_sky_precip_probability_4d
entity_pop_5: sensor.dark_sky_precip_probability_5d
in log:
Thanks in advance
Francesco
You should first update to the latest version
Also the darksky entities need the ‘d’ at the end when you’re on HA 0.91.x, in 0.90.x you can omit it.
See my post above.
Thanks VDRainer. All entities need the ‘d’ at the end or just some like the ones I’ve already done? (see lovelace config above)?