This is missing for me too
It did. A 3-hourly and a daily.
I now have a fully-working Template Weather entity using DataHub RESTful sensors and my own temperature sensor as the inputs.
I’ll share details next week when I have time…
4 Likes
Thanks fantastic! …looking forward to it!
1 Like
I definitely wait for them, hoping that your example will help me create mine😊
2 Likes
I use the 3 hourly met office entity but is this still available? I’m using the met office intergration but on the intergration page it shows all the 3 hourly entities have been disabled.
Yes it is… but did you gather the weather service has changed? You need to create a template if you want to access the information below…
The documentation says the hourly and daily entity is now combined but not how to use it.
Anyone know the new syntax or location of info to replace
{{ state_attr(‘weather.met_office_chester_daily’, ‘forecast’)[0].condition }},
{{ state_attr(‘weather.met_office_chester_daily’, ‘forecast’)[1].condition }},
{{ state_attr(‘weather.met_office_chester_daily’, ‘forecast’)[2].condition }},
{{ state_attr(‘weather.met_office_chester_daily’, ‘forecast’)[3].condition }}
where "forecast’).condition where x used to give today tomorrow etc
Covered at length in various topics on here: the forecast attribute has been replaced with the get_forecasts() service. See the first example here:
You’ll need to set up a template sensor like this:
template:
- trigger:
- platform: time_pattern
hours: /1
action:
- service: weather.get_forecasts
data:
type: hourly
target:
entity_id: weather.met_office_chester_daily
response_variable: hourly
sensor:
- name: Temperature forecast next hour
unique_id: temperature_forecast_next_hour
state: "{{ hourly['weather.met_office_chester_daily'].forecast[0].temperature }}"
unit_of_measurement: °C
attributes:
forecast: "{{ hourly['weather.met_office_chester_daily'].forecast }}"
Thank you so much. I snese your frustration but in my defence none of the links take you to the location you highlighted. Met Office Integation tells you nothing, the github page tells you little and the “Weather” link on the documentation for met office takes you back to met office. Maybe I should have thought of looking at the generic weather page so grateful for you adcive and code snippet. Thanks again
It was a change made in 2024.4: the forecast attribute had been “deprecated” (planned to remove) for a few months, then it happened. It’s buried under "Backward-incompatible changes on the release page:
It’s always worth reading through these before updating, although I do recognise that you might not always be able to identify a looming problem from the notes if you’re not that “techie”.
Thanks will keep an eyeout now on the release info.
I have sucessfully set up the template sensors and they report the next 4 days temps.
However I cant quite fogure out the templete to display it now.
Can I seek you indulgance one more time
The code to print the results was as below
- alias: "Display "
trigger:
platform: state
entity_id: input_boolean.display
to: 'on'
action:
- service: notify.notify_lounge
data:
message: "Conditons for next 4 days"
- service: notify.notify_lounge
data:
message: "Conditons for next 4 days
{{ state_attr('weather.met_office_chester_daily', 'forecast')[0].condition }},
{{ state_attr('weather.met_office_chester_daily', 'forecast')[1].condition }},
{{ state_attr('weather.met_office_chester_daily', 'forecast')[2].condition }},
{{ state_attr('weather.met_office_chester_daily', 'forecast')[3].condition }}"
- service: input_boolean.turn_off
entity_id: input_boolean.display_clouds
so for day [0] I tried
{{ state_attr(daily[‘weather.met_office_chester_daily’].forecast[0].temperature) }}
but in the template editor it says daily undefined.
You need to put the template sensor you’ve created in place of weather.met_office_chester_daily in your action template.
Perfect, Thanks
{{ states(‘sensor.temperature_forecast_day_0’) }}
did the trick 