Advice needed: naming in 2024

Configuration
1

Context

I’ve been using HA for years now and added devices along the way. I started almost purely with a configuration.yaml file and slowly, over the years and as HA was progressing in its features, moved towards using more and more UI-based configuration. This is now my preferred way to configure all devices.

My problem

The naming of my devices is a small mess and I want to rename them all, using features I have not really used so far (Areas, Labels, …). I also want to keep my automation and Google Asstant user-friendly.
I am therefore asking the community for their experiences in naming (I do not need any help per see (everything works and I have dug into .storage many times) but rather the experiences (good and bad) you had with naming, especially when it relates to automation and voice activation).

The Mighty Details ™

I have two main sets of devices I have doubts about (re: naming)

  • devices that do not move, usually wall switches that send a signal (push-button kind)
  • devices that usually do not move but whose actual usage does not match the names

I will use an example for the second case: a MEROSS power strip (managed by the fantastic integration of @krahabb ). This is a strip that has several power outlets that manage standalone lamps

  • device: seen as mss425f 2005281078830290814148e1e91d807b
  • example of an entity:

image

This is typically an entity I renamed. The original name was probably something built off the device name (which itself is something like a serial number or some hash of information) - I renamed it to meross02_outlet_5 where

  • meross02 is supposedly the name of the strip I should have written the name of with a pen (I just checked - I did not) and should have changed the name of the device to (which obviously I did not)
  • outlet_5 is supposedly the number of the outlet, which again I should have written on the strip with a pen which I did not do either

Then there is the Name, Show as which I chose to be Outlet (← this is probably a bad idea because “Outlet” is something that does not exist, it is always something connected to it that matters), and finally a Label that I did not delve into yet as it appeared in 2024.4.

As you can see it is messy and the other devices are similar.

So my question: how do you do it?
Specifically:

  • do you keep the autogenerated names as much as possible (this is something I am aiming at) and realy on the Name to manage stuff (the idea is that the ID does not matter)
  • do you have duplicate names such as big lamp and rely on the areas to make a difference (like in “hey Google, switch on big lamp in bedroom” (as opposed to “big lamp” in the garage)
  • any clever uses for Label, especially vs. Areas

Any comments welcome!

2 Likes
2

I point at a device and ask my wife what she calls something. (no, really)

The device name becomes a variant of that (usually roomname whatever)

Why?
Forcing the room name gives some indication where a device lives but at the end of the day I don’t want the argument with her later about why she can’t control it with voice and it’s a stupid name.

Outlets and plugs are a special case in HA I number the. Starting from the room main door clockwise. So master bedroom outlet 1 master bedroom outlet 2.etc.but in Alexa or Assist I also add an alias so she can call it by whatever it controls. (air freshener, etc.)

Because of this I’ve been in the habit of renaming everything like this as it comes in.
The device model etc are stored in the device attributes themselves. I don’t need them in the UI for me I can look them up if I need. Good luck.

4 Likes
3

I’ve read this somewhere already (in this forum) – and I recalled that when writing this question :slight_smile:

I do that too, except that my wife is not into using the voice commands (but is still annoyed by the naming if I choose it :))

2 Likes
4

I don’t use voice control. I have automated as much as possible to avoid manually doing anything.

That said, my naming convention is

  • domain.<room>_<thing>
  • domain.<room><thing_it’s_closest_to><thing> (if multiple)

so, for example:
lights in living room (multiple)

  • light.livingroom_sofa
  • light.livingroom_ceiling
  • …

lights in hallway (multiple)

  • light.hall_kitchen_end
  • light.hall_front_door_end
  • light.hall (grouping of the previous two and the entity I use)

switch in hallway (only one)

  • switch.hallway

cameras

  • camera_front_door
  • camera_garage
2 Likes
6

You mean that you

  • add a name (ex friendly_name) and keep the ID,
  • or rename the ID,
  • or rename the ID and add a name

Re automation (and other meanings) - I need to have a hard stare at name vs area vs label - what to put where.

7

So you do not use the name field?

9

Yes, but I rarely have to edit it as it defaults to the same name as the entity ID.

so sensor.living_room_motion defaults to a name of Living room motion.

10

I change the device name at the device level in the friendly name field and when it offers to rename the entities - I say yes

That slugifies the new name and changes each entity to domain.slugified_name_according to naming schema.

I like my entity id’s to resemble the friendly names but since earlier this month I’m extensively deploying labels for more organization.

2 Likes
11

yes, same here.