Weather Card

[OzGav]

Just made up a floorplan version of the HA weather card. SVG and yaml are attached. Modify it as you see fit!

weather_card.zip

You will see reference to an input_text in there. I use that to keep the current weather icon in a day or night mode if they are available. Here is the automation for that:

  - alias: Track Weather Icon Day vs Night     
    mode: restart
    trigger:
      - platform: state
        entity_id: sun.sun
      - platform: state
        entity_id: sensor.place_icon_descriptor_0
    action:
      - service: input_text.set_value
        data_template:
          entity_id: input_text.current_wx_icon
          value: >
            {% if is_state('sensor.place_icon_descriptor_0', 'sunny') %} day
            {% elif is_state('sensor.place_icon_descriptor_0', 'clear') and is_state('sun.sun', 'below_horizon') %} clear-night
            {% elif is_state('sensor.place_icon_descriptor_0', 'clear') and is_state('sun.sun', 'above_horizon') %} clear-day
            {% elif is_state('sensor.place_icon_descriptor_0', 'mostly_sunny') and is_state('sun.sun', 'above_horizon') %} fair-day
            {% elif is_state('sensor.place_icon_descriptor_0', 'mostly_sunny') and is_state('sun.sun', 'below_horizon') %} fair-night
            {% elif is_state('sensor.place_icon_descriptor_0', 'partly_cloudy') and is_state('sun.sun', 'above_horizon') %} cloudy-day-3
            {% elif is_state('sensor.place_icon_descriptor_0', 'partly_cloudy') and is_state('sun.sun', 'below_horizon') %} cloudy-night-3
            {% elif is_state('sensor.place_icon_descriptor_0', 'cloudy') %} cloudy
            {% elif is_state('sensor.place_icon_descriptor_0', 'light_rain') and is_state('sun.sun', 'above_horizon')%} rainy-2
            {% elif is_state('sensor.place_icon_descriptor_0', 'light_rain') and is_state('sun.sun', 'below_horizon')%} rainy-1-night
            {% elif is_state('sensor.place_icon_descriptor_0', 'wind') %} wind
            {% elif is_state('sensor.place_icon_descriptor_0', 'windy') %} wind
            {% elif is_state('sensor.place_icon_descriptor_0', 'dust') %} haze
            {% elif is_state('sensor.place_icon_descriptor_0', 'fog') %} fog
            {% elif is_state('sensor.place_icon_descriptor_0', 'shower') %} rainy-5
            {% elif is_state('sensor.place_icon_descriptor_0', 'rain') %} rainy-6
            {% elif is_state('sensor.place_icon_descriptor_0', 'rainy') %} rainy-6
            {% elif is_state('sensor.place_icon_descriptor_0', 'storm') %} scattered-thunderstorms
            {% elif is_state('sensor.place_icon_descriptor_0', 'stormy') %} scattered-thunderstorms
            {% elif is_state('sensor.place_icon_descriptor_0', 'light_showers') %} rainy-5
            {% elif is_state('sensor.place_icon_descriptor_0', 'light_shower') %} rainy-5
            {% elif is_state('sensor.place_icon_descriptor_0', 'heavy_showers') %} rainy-7
            {% elif is_state('sensor.place_icon_descriptor_0', 'heavy_shower') %} rainy-7
            {% elif is_state('sensor.place_icon_descriptor_0', 'clear_day') %} clear-day
            {% elif is_state('sensor.place_icon_descriptor_0', 'clear_night') %} clear-night
            {% elif is_state('sensor.place_icon_descriptor_0', 'partly_cloudy_day') %} partly-cloudy-day 
            {% elif is_state('sensor.place_icon_descriptor_0', 'partly_cloudy_night') %} partly-cloudy-night
            {% elif is_state('sensor.place_icon_descriptor_0', 'hail') %} severe-thunderstorm
            {% elif is_state('sensor.place_icon_descriptor_0', 'lightning') %} thunder
            {% elif is_state('sensor.place_icon_descriptor_0', 'thunderstorm') %} thunder
            {% else %} weather_sunset 
            {% endif %} 

[exetico]

Nice work 💪😁

[OzGav]

And here is a little change I made so that the Feels Like temp reflects the heat index or wind chill depending on which is relevant

        - entity: sensor.wupws_temp
          element: feelslike
          name: Feels Like Text
          state_action:
            - service: floorplan.text_set
              service_data: '${(hass.states["sensor.wupws_heatindex"].state > entity.state) ? "Feels like " + (hass.states["sensor.wupws_heatindex"].state) + "°C ☀" : "Feels like " + (hass.states["sensor.wupws_windchill"].state) + "°C ❄️"}'

[mdeweerd]

Interesting!

I think weather-card.yaml has a '"' too many in :

-            service_data: '/local/icons/weather_icons/animated/${entity.state}.svg"'

Files under 'icons/weather_icons' are needed as well. In my case some|those seem to be available under /local/community/ha-card-weather-conditions/icons/animated/ - when that card is installed using HACS.

[OzGav]

Yes I just use those icons. Thanks for pointing out the typo. I’ll try and fix that soon

[jtcookhome]

im trying to get this working. did you add it to your floorplan.yaml or just reference somehow? Not sure what I'm missing here? I did install Weather card from HACS and it works in my overview.

are you using this as a pop up or did you use it as a layer in your floorplan svg?

[jtcookhome]

ok, I don't have those entities, how do I add them? I thought I would get them from installing the Weather card from HACS.

[OzGav]

You need a weather integration. This floorplan or the weather card just shows them

[jtcookhome]

I installed Accuwether integration. It would require an extensive rewrite in order to get it to work. For example the conditions used to set the icons are not as simple as "Sunny" or "Partly Cloudy" see The screenshot. what integration are you using? although it may not work for me in the States.

[OzGav]

I use an Australian one. There are many offical ones https://www.home-assistant.io/integrations/#weather then there are lots more in HACS. A quick Google suggested maybe Pirate weather?

[exetico]

+1 on Pirate Weather, after Apple eat up the next option we previously had :-D

[Trzinka]

Hi!

Of course I have a question:

I looked at your settings in both files and as far as I can tell you were using Pirate Weather and some local Weather add-on.

The problem is that most Weather add-ons provide information in the form of the image:

or:

The question has how to name the elements in SVG and how to later call the entity in the floor plan card?

[OzGav]

I think I show how to do that in my opening post where I show the automation I have for setting input_text.current_wx_icon The automation converts the various states into a word which corresponds to the filename of a particular weather icon. I do that so I can use the night and day icons where they exist.

You can also look in the supplied yaml (in the zip) for how I handle the future day weather icons.

For the attributes you could pull them out with a template or can access the attribute like this hass.states["weather.weatherapi_doma"].attributes.pressure

[Trzinka]

Hi. Thanks for the reply.

If I understood correctly, it should name the elements in the SVG file so that I can understand them (to help me with the HA entity call) and they don't need to be the same as the HA entity ID!

I compared different weather add-ons and found a card that is the closest to yours:

As you know, I have no knowledge of programming, so I have to learn on the fly, and thank you for your help!

Now I have a question that you may think is funny, but actually I don't have enough knowledge, and when I don't have it, I ask someone smarter than me!

As the #1

entity in HA, it does not start with ID sensor, but is entity: weather.forecast_home!

Does it matter what ID name the entity has in HA or does it have to be a sensor?

entity: weather.forecast_home

state*: partlycloudy

State attributes (YAML, optional):
temperature: 5.7
dew_point: 3.1
temperature_unit: °C
humidity: 84
cloud_coverage: 63.3
pressure: 1009.5
pressure_unit: hPa
wind_bearing: 216
wind_speed: 6.8
wind_speed_unit: km/h
visibility_unit: km
precipitation_unit: mm
forecast:
  - condition: partlycloudy
    datetime: "2024-02-25T11:00:00+00:00"
    wind_bearing: 216
    temperature: 5.7
    templow: 0.9
    wind_speed: 8.3
    precipitation: 0
    humidity: 84
  - condition: cloudy
    datetime: "2024-02-26T11:00:00+00:00"
    wind_bearing: 227.2
    temperature: 10.3
    templow: 0.3
    wind_speed: 15.8
    precipitation: 0
    humidity: 55
  - condition: rainy
    datetime: "2024-02-27T11:00:00+00:00"
    wind_bearing: 30.8
    temperature: 7
    templow: 5.5
    wind_speed: 11.5
    precipitation: 4.8
    humidity: 95
  - condition: cloudy
    datetime: "2024-02-28T11:00:00+00:00"
    wind_bearing: 49.9
    temperature: 12.5
    templow: 4.8
    wind_speed: 10.8
    precipitation: 2.2
    humidity: 74
  - condition: rainy
    datetime: "2024-02-29T11:00:00+00:00"
    wind_bearing: 60.7
    temperature: 9.5
    templow: 7.2
    wind_speed: 10.8
    precipitation: 1.3
    humidity: 90
  - condition: rainy
    datetime: "2024-03-01T11:00:00+00:00"
    wind_bearing: 222
    temperature: 12
    templow: 6.7
    wind_speed: 3.6
    precipitation: 1.7
    humidity: 72
attribution: >-
  Weather forecast from met.no, delivered by the Norwegian Meteorological
  Institute.
friendly_name: Forecast Home
supported_features: 3

Now if all of the above is affirmative or the below entry is correct

- entities:
                - weather.forecast_home-temperature
                  name: Trenutna temperatura
                  state_action:
                    - service: floorplan.text_set
                      service_data: >-
                        ${hass.states["weather.weatherapi_doma"].attributes.temperature ?
                        Math.round(entity.state) : "?"}

[OzGav]

If I understood correctly, it should name the elements in the SVG file so that I can understand them (to help me with the HA entity call) and they don't need to be the same as the HA entity ID!

I generally do name the SVG element the same as the HA entity so it is clear when I look at the SVG but you don't have to and if you have one enttity affecting multiple elements then you cannot.

Yes I made the weather card example to look identical to this custom card to show people that you don't necessarily have to put the effort into making custom cards as ha-floorplan is very flexible.

entity in HA, it does not start with ID sensor, but is entity: weather.forecast_home!
Does it matter what ID name the entity has in HA or does it have to be a sensor?

It doesn't matter what the entitity is called in HA. You can still reference the attributes in the way that I showed.

I am not exactly sure what you are asking in your last question. The yaml I provided shows how you could add the attribute value to your floorplan. Just remember that will ONLY update when the STATE of the entity changes. So in this circumstance you might want to find an entity which changes often so you don't get the situation when the attribute changes but the floorplan does not. The entity you choose doesn't have to have anything to do with the weather, you just want the state to change which will fire the state_action rule and update your image.

[Trzinka]

Thanks for the reply.

I need another help related to the entity weather.forecast_home.

Under State attributes (YAML, optional) are the following options:

temperature: 2.9
dew_point: 2
temperature_unit: °C
humidity: 95
cloud_coverage: 89.8
pressure: 1008.4
pressure_unit: hPa
wind_bearing: 233.5
wind_speed: 9
wind_speed_unit: km/h
visibility_unit: km
precipitation_unit: mm

If I understood you correctly, I am calling these states:

state_action:
    - service: floorplan.text_set
      service_data: >-
        ${hass.states["weather.weatherapi_doma"].attributes.temperature ?
        Math.round(entity.state) : "?"}

.attributes.temperature is the State attributes (YAML, optional) of temperature.

Now I have a problem (ignorance) because I don't know how to call:

forecast:
  - condition: cloudy
    datetime: "2024-02-26T11:00:00+00:00"
    wind_bearing: 232.5
    temperature: 10.8
    templow: 2.9
    wind_speed: 17.3
    precipitation: 0
    humidity: 55
  - condition: rainy
    datetime: "2024-02-27T11:00:00+00:00"
    wind_bearing: 41.5
    temperature: 6.9
    templow: 4.3
    wind_speed: 13.3
    precipitation: 13.6
    humidity: 97
  - condition: rainy
    datetime: "2024-02-28T11:00:00+00:00"
    wind_bearing: 54.9
    temperature: 11.5
    templow: 4.6
    wind_speed: 12.6
    precipitation: 2.9
    humidity: 82
  - condition: rainy
    datetime: "2024-02-29T11:00:00+00:00"
    wind_bearing: 64.1
    temperature: 11
    templow: 5.4
    wind_speed: 16.9
    precipitation: 1.8
    humidity: 80
  - condition: rainy
    datetime: "2024-03-01T11:00:00+00:00"
    wind_bearing: 238.1
    temperature: 12.5
    templow: 7.1
    wind_speed: 5.8
    precipitation: 1.5
    humidity: 77
  - condition: rainy
    datetime: "2024-03-02T11:00:00+00:00"
    wind_bearing: 222
    temperature: 11.5
    templow: 4.3
    wind_speed: 11.5
    precipitation: 3.5
    humidity: 69

example:

`forecast:

• condition: cloudy
  datetime: "2024-02-26T11:00:00+00:00"
  wind_bearing: 232.5
  temperature: 10.8`

If I want to get the state of the entity: weather.forecast_home and below State attributes (YAML, optional) example above under state forecast and after that temperature

What the code to call this status should look like?

{hass.states["weather.weatherapi_doma"].attributes. what code should follow?

[OzGav]

I didn't look at your code closely enough so see below but I believe based on what you have written above that you understand the basic idea. The only thing is use an element to reference the SVG and use an entity which changes somewhat often (if you use sensor.time then the temperature will update every minute)

  - entity: sensor.time
    element: weather_forecast_home-temperature
    name: Trenutna temperatura
    state_action:
      - service: floorplan.text_set
        service_data: '${hass.states["weather.weatherapi_doma"].attributes.temperature}'

On your last question if I uderstand correctly forecast: is an attribute? So I assume I am looking at nested attributes? I haven't had to deal with that before but javascript supports nested arrays so you will likely want to reference it like is shown here https://dev.to/sanchithasr/understanding-nested-arrays-2hf7

So maybe something like hass.states["weather.weatherapi_doma"].attributes.forecast[0].temperature You might have to play with where the index goes.

[Trzinka]

Ooh. Thank you.

If I understand you correctly, if I don't set an entity (HAOS) to the element (SVG) it won't automatically update according to the change of hass.states["weather.weatherapi_doma"].attributes.forecast[0].temperature. Or so I'll ask, the previous code runs on first page load and only changes if its entity changes, but if no entity is specified the element doesn't update!

Just today I received https://www.aliexpress.com/item/1005005999388306.html?spm=a2g0o.order_list.order_list_main.5.41921802drBpPr and now I'm trying to connect to Weather Underground and I hope it will work, although there is very little data but there is a possibility about this weather station. I think then I will have an entity as a sensor and it will be much easier.

[OzGav]

if I don't set an entity (HAOS) to the element (SVG) it won't automatically update according to the change of hass.states

No you do not need to match the entity to the SVG, That is not what I am saying. It just happens to be that the weather entitity will only change once or maybe a couple of times per day. For example if the weather is fine all day then the state will remain sunny. However the temperature will be changing all day but the rule is looking for a STATE change. So what you would see is the temperature would not change on your floorplan unless you refreshed the page.

I am pretty sure you will get an error if you don't specify an entity.

Hopefully you can see from my example you can actually specify any entiity and use the hass object to get access to all the entities and their attributes that are available in HA. It is very powerful. You just don't normally do that because it far more convenient to use an entity which has the same name as the SVG element and you can reference that easily in your rules by using entity.state

[Trzinka]

Thanks, I think I understand now.

[Trzinka]

Hi OzGav!

What to do, it's me again.

I think this question will complete my project. ;=))

The current view is:

I'm currently using this file to graphically display the state of the weather:

Here are individual pictures of the weather conditions:
weather.zip

To be honest, I've been looking at your code and I can't even imagine what's what, so I'd like to ask if you can help me find a solution for this!

I have installed several sources of weather data:

Currently, the AccuWeather addon gives me the most accurate data, later when I install my weather station, which I bought a while ago, I will use WunderGroundpws to display an image (icon) next to the temperature in the floor plan card..

entities: weather.accuweather
state: sunny how do you find all states?

I don't think you will need it!
State properties (YAML, optional):

temperature: 17.5
apparent_temperature: 17.2
dew_point: 3.6
temperature_unit: °C
humidity: 39
cloud_coverage: 30
uv_index: 3
pressure: 1021
pressure_unit: hPa
wind_bearing: 248
wind_gust_speed: 17.3
wind_speed: 14.8
wind_speed_unit: km/h
visibility: 24.1
visibility_unit: km
precipitation_unit: mm
attribution: Data provided by AccuWeather
friendly_name: AccuWeather

What should the code look like to correctly show me the image from the entity state?

[Trzinka]

This is weather.accuweather entities state.

After I added the code that I assumed I had to add to automations.yaml, the thing doesn't work and this is how part of the code looks in DevTools.

Who determines what is seen in DevTools class="am-weather-cloud-1" ?

[Trzinka]

This is the DevTools view of the

type: custom:weather-card
entity: weather.accuweather
to me: Accu.

I downloaded the icons from: https://cdn.jsdelivr.net/gh/bramkragten/weather-card/dist/icons/

[OzGav]

Yes but you will need to keep on an eye on the different states and change the automation accordingly. For example, you show that current the state in partlycloudy but mine would be partly_cloudy_day or partly_cloudy_night so you will need to change that. Also the file names need to be adjusted to match yours

[Trzinka]

Hi thanks!

On the website https://www.home-assistant.io/integrations/weather/#condition-mapping I have our following conditions:

‘clear-night’
‘cloudy’
‘fog’
‘hail’
‘lightning’
‘lightning-rainy’
‘partlycloudy’
‘pouring’
‘rainy’
‘snowy’
‘snowy-rainy’
‘sunny’
‘windy’
‘windy-variant’
‘exceptional’

and in https://github.com/home-assistant/core/blob/dev/homeassistant/components/accuweather/const.py
I assume these are the states this add-on supports

from homeassistant.components.weather import (
    ATTR_CONDITION_CLEAR_NIGHT,
    ATTR_CONDITION_CLOUDY,
    ATTR_CONDITION_EXCEPTIONAL,
    ATTR_CONDITION_FOG,
    ATTR_CONDITION_HAIL,
    ATTR_CONDITION_LIGHTNING,
    ATTR_CONDITION_LIGHTNING_RAINY,
    ATTR_CONDITION_PARTLYCLOUDY,
    ATTR_CONDITION_POURING,
    ATTR_CONDITION_RAINY,
    ATTR_CONDITION_SNOWY,
    ATTR_CONDITION_SNOWY_RAINY,
    ATTR_CONDITION_SUNNY,
    ATTR_CONDITION_WINDY,

If I understand correctly the following means in automations.yaml! example :

{% elif is_state('weather.accuweather', 'mostly_sunny') and is_state('sun.sun', 'above_horizon') %} fair-day

weather.accuweather, 'mostly_sunny' the 'mostly_sunny' is state of weather.accuweather entity, and is_state('sun.sun', 'above_horizon') it just checks if it's day or night and the last fair-day is probably the name of the picture.

Am I right about the last one explanation?

[OzGav]

Yes. My icon set has some conditions that have day and night options hence those couple of lines that check the state of sun.sun. If you don’t have day and night icons you can remove those lines.

[Trzinka]

Hi OzGav!

I still have the problem. Now I've taken a different path, just like you.

I added this to fp.yaml and turned off the automation.yaml file. I appropriately changed the names of the SVG files to match the names of the state from the entity in HA.

            - element: weather.forecast_home
              entity: weather.accuweather
              state_action:
                action: call-service
                service: floorplan.image_set
                service_data: |
                  >
                    var imageName = '';
                    switch (entity.state) { 
                      case 'clear_night': imageName = 'clear_night'; break; 
                      case 'partlycloudy': imageName = 'partlycloudy'; break; 
                      case 'cloudy': imageName = 'cloudy'; break;      
                      case 'rainy': imageName = 'rainy; break; 
                      case 'windy': imageName = 'windy'; break;     
                      case 'fog': imageName = 'fog'; break;      
                      case 'exceptional': imageName = 'exceptional'; break;       
                      case 'hail': imageName = 'hail'; break;     
                      case 'lightning': imageName = 'lightning'; break;      
                      case 'lightning_rainy': imageName = 'lightning_rainy'; break;     
                      case 'pouring': imageName = 'pouring'; break;   
                      case 'snowy': imageName = 'snowy'; break;  
                      case 'snowy_rainy': imageName = 'snowy_rainy'; break;                       
                      default: imageName = 'sunny'; break; 
                      return '/local/img/fp/weather/' + imageName + '.svg';

element: weather.forecast_home is the ID name of the square in the SVG file!
entity: weather.accuweather is the entity ID name in HA!

This is what the fp card and data look like via devtools, where there is no link to the image.

SVG files are animated and with a name cloudy.svg:

An animated SVG file looks like this:

I don't have any image inserted in the SVG file (only the square as I mentioned earlier) because I assume that the code in fp.yaml should take care of inserting the *svg file into this framework.

Did I make a mistake somewhere or did I go about the manufacturing process incorrectly?

[OzGav]

Looks ok. Put <YOUR_HA_IP>:8123/local/img/fp/weather/cloudy.svg in your browser address bar and check the SVG is displayed. If not you have something wrong with the path

[Trzinka]

[Trzinka]

I looked in my #411 under Changing the background image based on the time of day, which I don't use!!! that I had background image images based on the time of day inserted (linked) in SVG.

I currently have a square called sensor.weather.forecast_home and I'm supposed to insert an image into that square via code?

[OzGav]

This

local/ha-card-weather-conditions/icons/static

is completely different to

local/img/fp/weather/

[Trzinka]

Yes, I saw it. Is it possible that the code does not consider the link from `return' but from the entity?

[Trzinka]

This link is weird because it doesn't follow the HA structure
https://homeassistant.local:8123/local/ha-card-weather-conditions/icons/static/cloudy.svg

This is the actual link
https://homeassistant.local:8123/local/community/ha-card-weather-conditions/icons/static/cloudy.svg

[OzGav]

If you have images in that folder then you must have something somewhere that calls for that. Just search for it. It may not be why the image you want to see isn't appearing but at least you can fix that problem.

[Trzinka]

I don't know what happened and what is still happening.

The ending is not the best but it works:

I made a sensor:

  - platform: template
    sensors:
      accuweather:
        value_template: >
          {%- set state = states('weather.accuweather') -%}
          {% if state == 'clear-night' %} clear-night
          {% elif state == 'cloudy' %} cloudy
          {% elif state == 'exceptional' %}exceptional
          {% elif state == 'fog' %} fog
          {% elif state == 'hail' %} hail
          {% elif state == 'lightning' %} lightning
          {% elif state == 'pouring' %} pouring
          {% elif state == 'rainy' %} rainy
          {% elif state == 'snowy' %} snowy
          {% elif state == 'snowy-rainy' %} snowy-rainy
          {% elif state == 'sunny' %} sunny
          {% elif state == 'windy' %} windy
          {% elif state == 'windy-variant' %} windy-variant
          {% else %} 
          {% endif %}

in fp.yaml

            - element: weather.accuweather.img
              entity: sensor.accuweather
              state_action:
                action: call-service
                service: floorplan.image_set
                service_data: '/local/img/fp/weather/${entity.state}.png'

[OzGav]

That is a solution so stick with that. Just note you have pouring three times.

[Trzinka]

What did you mean by poured three times?

[OzGav]

Look at your template

          {% elif state == 'pouring' %} 
          {% elif state == 'pouring' %} 
          {% elif state == 'pouring' %} pouring

[Trzinka]

Damn it. Too many times it happens to me, when I copy something from the Internet, I don't check it in detail. Thanks, I fixed it.

[Trzinka]

Hi OzGav!

I still have some confusion!
In the browser's DevTools (example below), where it is marked with a green arrow, I don't understand where it gets this information from?

  - platform: template
    sensors:
      accuweather:
        value_template: >
          {%- set state = states('weather.accuweather') -%}
          {{ state if state in ['clear_night', 'cloudy', 'exceptional', 'fog', 'hail', 'lightning', 'lightning_rainy', 'partlycloudy', 'pouring', 'rainy', 'snowy', 'snowy_rainy', 'sunny', 'windy'] else '' }}

I found this code online and it's originally for renaming, which I don't use. Is it possible that the code at the end of else '' adds this id="day" because I don't have it written anywhere?

I'm even more confused about the image below where id="cloudy-day-1" and title is State: partlycloudy.

in folder /local/community/ha-card-weather-conditions/icons/animated/ I found the images saved as an ID in the browser's DevTools:

in fp.yaml file i hawe written service_data: /local/img/fp/weather/${entity.state}.svg, which displays images:

Should I enter the names from the folder in the sensor template /local/community/ha-card-weather-conditions/icons/animated/ for correct display?

[Trzinka]

I think I solved the mystery around

<g filter="url(#blur)" id="cloudy-day-1" etc.
The id here is read from the weather svg file even though the svg file name is different. In short, irrelevant!

and

<title> accuweather State: partlycloudy friendly_name: accuweather Last changed: red 18 minutes ago Last updated: 18 minutes ago </title>

State: partlycloudy is important here because this calls the name of the image in the specified path in the fp.yaml file!

[OzGav]

I would be using /local/community/ha-card-weather-conditions/icons/animated/ as there are more icons so you will get a better reprentation of the weather state.

[Trzinka]

Hi!
I noticed that you forked Wundergroundpws v1.X.X!
Actual version nov is Wundergroundpws v2.X.X!

There is no upgrade to v2.x.x from earlier versions. You must: Delete the existing custom_components/wundergroundpws directory. Remove all configuration items for v1.1.x and earlier from configuration.yaml

As I mentioned, I bought a weather station that works through Weather Underground and followed the instructions that I should:
You must have a personal weather station registered and uploading data to Weather Underground. etc

Unfortunately, I'm more of a frosty person and it's still cold on our side of the earth and I'm waiting for nicer weather to mount outside.

When I succeed in this, I will have to delve into this addon to understand what data the station sends via Weather Underground and in what format.

And I know from experience that I will most likely need help again.