Converter · runs in your browser
Legacy template sensor converter
Your sensors show up as unavailable, or your automations sit there enabled and never fire. Paste the old YAML below and get the modern syntax back.
Why this broke. The old platform: template syntax was removed. Home Assistant does not shout about it — the entity just stops updating, or quietly gets a different entity ID, and every automation pointing at it stops working with no error in the log.
Waiting for your YAML…
What changed, key by key
| Old key | New key |
|---|
Questions people actually ask
My sensor says "unavailable" after updating. Is this the same thing?
Usually yes. If the sensor was defined with platform: template, it is no longer being created at all. Converting it to the modern block brings it back.
My automation is enabled but never runs.
That is the nastier version of the same problem. When a template entity is recreated, its entity ID can change — and an automation pointing at an entity ID that no longer exists fails silently. Convert the sensor first, then check the entity ID in Developer Tools and update the automation.
Do I still need entity_id: in my templates?
No. The old entity_id list told Home Assistant what to watch. Modern templates work that out on their own, so the converter drops it.
Is my configuration sent anywhere?
No. The conversion happens entirely in your browser. There is no server, no logging and no account.