[PETITION] Don't delete the forecast attribute

[123 (Taras)]

@makai

Example in that PR:

Yup, I had copied that example from the PR when it was still a ‘request for comment’ (up until about 2 days ago when its development was rekindled and expedited).

Now it will be included in 2023.9.0’s documentation for the Template integration:

A big thanks to allenporter and emontnemery for implementing this feature in time for the September release; it will simplify the task of getting calendar events and weather forecasts (and other things).

---

BTW, this comment intrigues me:

Perhaps, as a side-effect, this PR also fulfills a long-standing Feature Request:

Support Variables in Template Sensors

Release 0.115 introduced Variables for automations and scripts. Variables would also be useful for creating Template Sensors, Template Binary Sensors, Template Switches, etc. For example, here’s a Template Sensor I use to report the quantity of open doors. It also has an attribute reporting the names of all open doors. The two templates it uses are nearly identical. open_doors: friendly_name: 'Open Doors' value_template: > {{ expand('group.doors_all') | selec…