I give everything fun and whimsical names so when I have to actually fix something, it takes longer than necessary. 😃

@early_riser
Considering the fact that just like Apple Home, HA dashboards strip the first part of the display name if it’s identical to the area name, I use the „area device“ convention. So „Bathroom Leak Moisture“ is displayed as „Leak Moisture“ under the area „Bathroom“.
Furthermore HA allows to recreate entity Ids after renaming a device resulting in: „binary_sensor.bathroom_leak_moisture“.
So if I move my sensor to another location, I simply rename it to „Attic Leak „.

Entities I strongly recommend naming them like this:

{location}_{type}

For example

main_bedroom_temperature

This way if you change devices, you can swap entity names and everything works. Also YAML code is much easier to read and write.

Devices? That’s more difficult to name, but also way less important, IMO. Usually I try to follow the same scheme as for entities, but sometimes I just prefer something else, like the actual brand, date of install…

I name them James and Bob, then immediately forget which is which and get confused.

… you may wish to use a different strategy

I found someone a while ago that used this

floor - type - subtype - room - thing

You end up with a name like

00 - switch - plug - living room - lamp

i use a code like “nbrnw1” for like outlets and “nbrnw1&2” if its a dual outlet plug. Its a room code “nbr” and where/what device is, in this case “nelw” means "north wall. So “nbrnw1” is an outlet on the north wall of the north bedroom. “Ksw1” would be an outlet on the south wall of the kitchen.

I went with <function>_<room>. So like motion_garage, or door_office. The function of the device won’t change, so it seemed logical to have it in that order.

It’s also not hard to change names of devices in Zigbee2MQTT and propagate that through HA if a device moves.

I just rename them if they are moved

¯\_(ツ)_/¯

I separate the name from the ID, so the IDs are relative to the specific device only, and the names represent the device and location.

I’ve set the IDs for all my sensors to use a code. The letters identify the type of sensor, and the numbers are sequential when I got them. I also have a label maker and labeled all the devices with their codes.

Example:

AA##

So my first temperature sensor is

TS01

Then the name of the sensor is a little more elaborate, where it includes the type of the sensor, the code, and the location.

{Type} {ID} - {Location}

So my bedroom motion sensor is:

Motion MS02 - Bedroom

Then if I have to rearrange anything, I don’t update the device ID, just the name and how it’s used.

I recently moved and had to rearrange some of the devices. It wasn’t as bad as it could have been as I tried sticking the sensors in the proper rooms (ie all the old bedroom devices stayed in the bedroom). But there were some cases where I did have to rename them & update the integrations.

Generally, and for a number of different reasons, it’s best to disassociate a device that is meant to be permanent and re-pair with HA. There’s a whole lot of automation in the background that goes into pairing a device, or setting up schedules, automations, scenes, scripts …etc. Deleting forces a find/clear on that entity, and re-pairing creates clean new entries.

You can rename them later no? I name them after the sensor, and rely on the location field. But in esphome they are named location-sensor.