WTH why can I not use my own temperature in weather forecast card

When I use a weather forecast card I want to use my own temperature data. But when I add the weather card I need to choose a weather entity that delivers everything. So I can choose what to show but not to disable the temperature.

So please add an option to choose a temperature entity to overwrite the setting. I want to use forecast data but not showing the actual temperature from that entity.

Weather entity data:

My temperature sensor data I have outside:

In case you want a work around, there are alternatives available from HACS. The weather-chart card allows you to override the entity that provides temperature. The platinum-weather-card also allows you to blend local weather data with forecast data.

the obvious answer here would be use the template weather entity.

it allows you to populate each of the config options with any template you desire, creating a weather entity, which you can then use in the UI for your card

2 Likes

But how to get the forecast data? The sample from the docs do not help here. I do not see any attributes for that data.

I u se the Meteorologisk institutt (Met.no) integration for the data. I have it and see the forecast when I open the entity but no idea where it is locate.

Again, this should be much easier and not only for deep divers of home assistant.

I also checked the cards in HACS but I do not like them and would like to stick with the core version.

yep, that is somewhat user unfriendly… easily found though because so many people struggle and post in the community :wink:

weather:

  - platform: template
    name: Composite
    unique_id: template_weather_composite
    condition_template: >
      {{states('weather.buienradar')}}
    temperature_template: >
      {{states('sensor.ws_5500_feels_like_temperature')|float(0)}}
    humidity_template: >
      {{states('sensor.ws_5500_humidity')|float(0)}}
    pressure_template: >
      {{states('sensor.ws_5500_pressure')|float(0)}}
    wind_speed_template: >
      {{state_attr('sensor.buienradar_woensdrecht','windspeed')|int(-5)}}
    wind_bearing_template: >
      {{state_attr('sensor.buienradar_woensdrecht','winddirectiondegrees')|int(-5)}}
    forecast_daily_template: >
      {{state_attr('sensor.buienradar_voorspelling_per_dag','voorspelling')}}

so dont use the response variable
{{buienradar_voorspelling_per_dag['weather.buienradar'].forecast}}

directly, but use the forecast attribute of the sensor entity, created by that trigger based response variable, see below.

The trigger based template creating the required response variable:

template:

# # per dag
  - trigger:
      - trigger: state
        entity_id: sensor.date
      - trigger: event
        event_type: event_template_reloaded
      - trigger: homeassistant
        event: start

    action:

      - action: weather.get_forecasts
        target:
          entity_id: weather.buienradar
        data:
          type: daily
        response_variable: buienradar_voorspelling_per_dag
   
    sensor:
      - unique_id: buienradar_voorspelling_per_dag
        state: >
          {{now()}}
        attributes:
          voorspelling: >
            {{buienradar_voorspelling_per_dag['weather.buienradar'].forecast}}