Weather Summary Icon Status

Configuration
1

Hello,

I have the following weather information trigger:

- platform: forecast
  api_key: 123456789
  monitored_conditions:
    - summary

Somehow, it only shows on the GUI an “eye” as icon and the “status” in clear text. I would like to change the icon depending to the status. Has anyone an idea how to do this? Would be nice to have those symbols used from material design.

2

We have an open story for this. A weather component could translate the textual summaries into standardized output and the frontend show icons according the state.

3

I was going to ask this very question, you beat me to it!

I noticed one of the variables was…

- platform: forecast
  api_key: ##############
  monitored_conditions:
    - icon

but instead of displaying an icon it just outputs the name of the material design icon for the current conditions e.g.

 partly-cloudy

I was also wondering if it is possible to get an actual forecast for the weather instead of the current conditions. I’d like to set up notifications / automations based on the forecast for the next week for example, but none of the listed variables appear to be anything other than current conditions.

1 Like
4

Was answered here

Only the OWM supports forecasts.

5

Thanks for this.

Is there any way that a variable could be called within the customise.yaml…

sensor.weather_icon
  icon: mdi:{get current state: sensor.weather_icon}
2 Likes
6

worked for me by setting up the group :wink:

customize:
group.forceast:
icon: ‘{{ “mdi:”+states(“sensor.weather_icon”) | d(“mdi:weather-rainy”) }}’

7

Your template method doesn’t appear to work for me, can you provide a more detailed example config?

8

What I noticed is that there are sufficient mdi icons related to weather on https://materialdesignicons.com made by Austin Andrews.

Why is it that I cannot add them?

9

Will show a symbol for the current weather:

sensor:
platform: yr

10

The OWM component docs state that the data is only available in Metric at the present time; is this still true?

11

Yes, it’s still only metric.

12

I’m loading icon from the sensor Forecast.IO and weather forecast from OWM as I noticed the OWM icons don’t match the MDI names.

  • platform: forecast
    scan_interval: 900
    friendly_name: forecastio
    api_key: [redacted]
    units: auto
    monitored_conditions:
    • icon
13

Do you mean the other way around maybe? I noticed the Forcast IO icon names don’t match the HASS used mdi icons.

f.i. forcast.io (clear-day), hass (weather-sunny)

1 Like
14

Came up with this after some reading up. Possible for the forecast.py component?


incoming_icons_value = {
'clear-day;weather-sunny'
'clear-night;weather-night'
'partly-cloudy-day;weather-partlycloudy'
'partly-cloudy-night;weather-cloudy'
'cloudy;weather-cloudy'
'rain;weather-pouring'
'sleet;weather-hail'
'snow;weather-snowy'
'wind;weather-windy'
'fog;weather-fog'
}

elif self.type == 'icon':
	for icon in incoming_icons_value:
		if icon.split(';') .......

…lost after this since not skilled enoughto do this myself…yet.

Got the forcast values and put them next to the ones I found in the mdi.html

2 Likes
15

I didn’t pay close attention to it and that’s why I set a default icon (to avoid getting errors), but thanks for the mapping, probably easy to do with simple {% if %} {% elif %} {% endif %} in my template… Am working now on grouping my automations and creating scripts to allow delay based on input sliders, but I’ll sure come back to your findings and post the results (if you don’t beat me to it :wink: )

1 Like
16

Okay. Good looking out.

17

Tried this:
group.weather: icon: > {% set weatherIcons = {"clear-day":"weather-sunny", "clear-night":"weather-night", "partly-cloudy-day":"weather-partlycloudy", "partly-cloudy-night":"weather-cloudy","cloudy":"weather-cloudy","rain":"weather-pouring","sleet":"weather-hail","snow":"weather-snowy","wind":"weather-windy","fog":"weather-fog"} %} {{"mdi:"+weatherIcons[states("sensor.weather_icon")]|d("mdi:weather-partlycloudy")}}

But the icon doesn’t seem to ever be set…

18

Did you try without the “>”?

19

Yeah, talked with devs, templating the icon is not currently possible. I’m going to look into implementing it and pushing it up if I can.

1 Like
20

I wonder if instead of templating the icon you could try setting the entity_picture:?

Use one of the png weather icon sets that are available - some of which are already named appropriately - and then just did a substitution on the image name.