I had a simple automation to turn the heating on if the forecast for the next day is < x deg. {{ state_attr(‘weather.home’, ‘forecast’)[1][‘temperature’] <= states.input_number.setpunt_verwarmen_aan.state|float}} Now we have to use the (awful) get_forecast service. Is there any way to do this wit…

Ah I see, the template should be this: value_template: >- {{weather_forecast['weather.home']['forecast'][1]['temperature'] <= states('input_number.setpunt_verwarmen')|float(0)}} I initially tested it with the weather.get_forecast service but that one is already depreciated. I …

Yes you can do it within that automation. The key part is to move the condition into the action part after you have called the get_forecast service. I choose personally to wrap it in a if/then action. alias: Nieuwe automatisering description: "" trigger: - platform: time at: "23:55:00" condit…

[image] [image] Doesn’t work (yet)

The response variable is only accessible if the full automation is triggered. If you manually trigger the automation each action is triggered separately, so each actions is unaware of previous actions. In your case it means you have to wait to 23:55:00 or change the time for testing purposes.

[image] basbrus: ch action is triggered separately, so each actions is unaware of previous act [image] Ok I changed the time to let the whole automation fire but the same result.

seems you are using the incorrect target entity-id in the forecast template. considering you have entity_id weather.home you should have {{weather_forecast('weather.home').forecast}} or, its attributes {{weather_forecast('weather.home').forecast[1].temperature}} see this: - trigger: - pl…

[image] basbrus: {{weather_forecast['weather.home']['forecast'][1]['temperature'] <= states('input_number.setpunt_verwarmen')|float}} [image] and @Mariusthvdb [image] Such a hassle to get such a simple task done. Unbelievable that they cut the forecast attribute away …

you are doing it wrong so it seems the template I suggested is inside the trigger based template for the service weather.get_forecasts. it can not be used like that in an automation. Why don’t you use the resulting template entity inside the automation? can you at least confirm the trigger based …

[image] Mariusthvdb: it ca not be used like that in an automation. Why don’t you use the template entity inside the automation? The main goal as from OP’s first post was to handle it within a single automation. Which can work with response variables. Second the last error is not caused becau…

[image] basbrus: The main goal as from OP’s first post was to handle it within a single automation. Which can work with response variables. well, it could, but it is a bit convoluted. And, it would be a pity to only use that response inside that single automation. if using that service and c…

[image] basbrus: {{weather_forecast['weather.home']['forecast'][1]['temperature'] <= states('input_number.setpunt_verwarmen')|float}} Yep that has done it. I’ll make the default something that doesn’t trigger heating nor cooling. @basbrus Thanks for helping @Mariusthvd…

Help I had a simple automation to turn the heating on if the forecast for the next day is < x deg

Configuration Frontend

SBeukers (Sjoerd Beukers) April 18, 2024, 10:11am 16

Just the met.no weather integration.

but the forecast attribute was deprecated and is now a service call.

Check (and please vote while you are there )