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

Month of "What the heck?!"
5

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}}
1 Like