Device/Entity Naming Standards / Best Practices

[123 (Taras)]

I keep entity names as short as possible, containing just enough to understand their purpose. I don’t stuff lots of meta-data into the entity’s name. If I need to add meta-data, I use custom attributes because it’s not only neater but easier to reference when using a Jinja2 template. For more information see this post:

Recommended ways to manage devices and entities names

I’m not an advocate of using an entity’s name to store metadata. In other words, I don’t recommend creating an entity name packed with its characteristics. sensor.manufacturer_model_identifier_color_size_location_bla_bla_etc When the time comes to select entities based on their characteristics, the resulting template can become quite messy. What I suggest is to add metadata as custom attributes to an entity. Simple add them to customize.yaml or via Configuration > Customizations. For example…