You don't need to do anything else.
Way back machine to get the documentation? You can't be serious.
But anyway, this is the link:
https://web.archive.org/web/20260430171315/https://www.home-assistant.io/integrations/template/#legacy-template-deprecation-migration-guide
My naive solution:
homeassistant:/config # grep -ris "\- platform: template" *
Am I wrong about that?
Yes, the way back machine. Y’all had six months. The migration guides don’t work with the current version of the software, so there’s no point to have them in the documentation. Next time, take care of repairs when they pop up instead of ignoring them for 6 months.
Yes, you’re wrong about that. The migration is not simple, that’s why there’s a custom integration that migrates for users.
Forgive my stupidity.
I have heaps of template code here.
So, if I didn't have any "repairs" (which was the case), then I don't need to adjust anything either?
You’re good if you don’t have repairs. If I remember correctly, the new repair is a generic one produced by HA core. It says something along the lines of “platform: template” is not supported for each domain.
Thank you!
One thing I think we want to clarify is that, no repair prior to the act of upgrading to 2026.6, is good.
If however I'm already on 2026.6, then no repair is expected - even when I have template issues... because IIRC the mechanism to detect the legacy templates would have been gone on 2026.6.
It’s not gone, it’s auto detected by core and it produces a different repair.
No repair, no need to worry about this.
Thanks for creating this process. Worked great for me,
Question: Can the Legacy Template Migration Helper integration be removed once this is done?
You can remove the integration
Just to clarify: when i installed every update of Home Assistant -which i did- the migration is automatically taken care of? So i don’t need to install additional tools to migrate and its safe for me to install the June versions of Home Assistant?
No, updating Home Assistant did not change your old configuration syntax.
If you had legacy syntax template entities, you should have received Repair notifications like those shown in the deprecation thread. Only you know if you received those Repair notices... If you are unsure, go to Settings>Repairs and use the breadcrumbs menu to show ignored repairs.
Thanks for the info. I didn’t had any hidden repairs, so installed the latest HA version. Went without any issues. I try to handle repairs every time if or when they occur (and I have time to investigate the issue(s)).
I only had 3 or 4 entities that needed migration, so I did it manually. However, I still see one error
sensor:
- platform: template
The thing is, there is no platform: template left in any of my yaml-files. How can I find out which file/line the error is reffering to, or if it's cached or something?
It's not cached, nothing in the configuration is cached for the backend. It exists somewhere. The issue will go away after a restart, not reload. Which could be your issue.
My bad, seems that I did a reload for the last fix rather than a restart. All good now, thanks!
This is a lie; the update did affect me, but I didn't receive any obsolescence message. My ESPresence presence system has stopped working, both due to platform:mqtt and device_tracker.see, and I don't know where the problem originates. I only know that after updating my entire system (which my alarm and cameras depend on), it stops working. The worst part: I can't find any help or support, and I don't understand the documentation.
I also understand that they haven't provided any alternatives to the device_trackers. I DON'T KNOW WHAT THE DEVELOPERS WERE THINKING.
The only solution I see now is to NEVER update Home Assistant again, no matter what breaks.
Those are not the template integration and they have nothing to do with the template entity deprecation.
The template entity deprecation only affects platform: template, nothing more. Your issues lie elsewhere.
So how do you explain that after updating Home Assistant, an error appears in Repairs, and at the same time, my presence system stops working correctly?
Previously, devices couldn't be marked as "away" if the door hadn't been opened. After the update, that does happen. Something has clearly changed in the system's behavior.
That's why I struggle to understand the claim that "there's no obsolescence." If an update introduces an error message and coincides with a setting that had been working for months suddenly stopping, from the user's perspective, it seems exactly like an incompatible change or an obsolete feature.
Do you notice how platform: template is not the same as platform: mqtt? The repairs and issues that were created specifically target platform: template. I know that they will not affect platform: mqtt because it's a completely separate code base and a separate integration.
The problem is that you don't understand. You think you understand and you are blaming anything that you find that remotely resembles your issue. I suggest you step back and try to debug what broke on your system and stop blaming things that look similar to your issue.
Drew attempted to help you yesterday, you should look into his advice. He's pointing you in the correct direction.
Lastly, your over-the-top anger towards developers is a bit much. If you want help, be kind.