Rename of device containing "#" breaks automations and dashboards

If I rename the device "#T3 Device " to “#T3 Device Blabla” all automations and dashboards containing this device are broken.
Same problem wenn “#” is elswhere in the name
Is this a known problem with “#” in what ever? “#” as comment…

# and most symbols/special characters should not be used when naming devices

Is there a definition what characters are allowed for names?

Google Jinga or JavaScript and special characters. When coding those characters matter…

Especially when starting a line with #

I have to correct my post.
The renaming of devices does in general not work.
There might be special problems with special characters but it is also not working if there are no special characters involved,

Let’s walk through the method and the integration you are working with…

If I go to a device and select the device name, I get a prompt asking to rename all entities associated with that device.

This window is coming up. But the renaming is not working as expected.

Can you explain this (what you are seeing) in more detail?

It’s really quite simple.
I have a poweplug with name “zpp23” and entitites of this plug are displayed in one dashboard.
When I rename it to “New Name” he asked if I want to rename 9 Entities - I say yes.
After this in the dashboard “Entitiy not available: Old Name” appears for all 9 Entitites

Saying yes to rename the ids is why things break. If you also rename the ids of all the entities, then the automations refer to the old ids. That is great when you want to replace one device for another, because you can rename the old one to something else, and the new one to the old ids, and then all the automations refer to the replaced device. So it is by design.

So the short version is: don’t rename entities if you want all automations to keep pointing to the same device.

1 Like

Thank you very much for this information