Best Practices for Naming Your Smart Home Devices – Learned the Hard Way

I’m a Smart Home enthusiast and have been working with this topic for over 20 years. Right now, I’m building my third Smart Home – and with over 400 Aqara devices plus dozens of other devices from different brands, it’s a pretty ambitious project. With this post, I’d like to share some of my experience. I hope it’s helpful.

One thing I learned the hard way: without a good naming convention, large setups quickly turn into chaos. Finding the right device in an app, writing an automation, or troubleshooting a scene becomes a nightmare if names are inconsistent, unclear, or duplicated.

Here’s the system I use today – it works just as well for small setups as for monster installs.

It’s based on three principles:

  1. Unique – No two devices share the same name.
  2. Self-explanatory – You can tell what it is, where it is, and what type it is at a glance.
  3. Scalable – Works for the small setups and the monster installs.

1. The Basic Formula
[Room].[Device type].[Number or detail]

Examples:
living.lt.ceiling1 → Living room, light, ceiling fixture #1
kitchen.sns.mmwave1 → Kitchen, sensor, mmWave #1
office.sw.scene2 → Office, switch, scene button #2
bedroom1.blind.main → Bedroom 1, main blind
garage.lock.entry → Garage, entry door lock

2. Room Names
Keep them short, lowercase, and without spaces:
kitchen, living, dining, bath1, bath2, bedroom1, hall, garage, garden

3. Device Type Codes

Code Meaning
lt Light (lighting)
sw Switch
sns Sensor (generic)
mmwave mmWave presence
pir PIR motion sensor
door Door contact sensor
window Window contact
blind Blind/shade
lock Lock
climate Climate/thermostat
plug Smart plug/outlet
cam Camera
siren Siren/alarm
media Audio/visual device

4. Numbering
ceiling1, ceiling2, scene1, scene2

For multiple floors or buildings, add a prefix:
main.kitchen.lt.ceiling1
guest.bedroom1.sns.pir1

5. Keep It Clean

  • Use lowercase and dots – no spaces or special characters.
  • Avoid manufacturer or model names in the device name (put those in your inventory).
  • For mobile devices, use mobile or portable instead of a room name.

:bulb: Pro tip:

If you have a large installation, create a small “prefix dictionary” (e.g., lt = light, sns = sensor, sw = switch) and keep it in your documentation.

Consistent naming makes automation rules easier to build, device searches faster, and troubleshooting far less painful.


What naming convention are you using in your smart home? Have you found any shortcuts or tricks to make it even easier?

Always remember: “If your car is smarter than your home… you’re driving into the future while living in the past” :red_car::house:

36 Likes

Thanks for sharing, great tips!

4 Likes

Some nice tips in there, tell me are these names within the Aqara app for names in 3rd party software?

3 Likes

I use these names in the Aqara app, but only as the “technical” names. For the dashboards and device cards I switch to something a bit more family-friendly – keeps the system organised, but still easy for everyone else at home to use.

6 Likes

Thanks for your tips, much appreciated.

3 Likes

Great work Rudy! I believe naming is very important too. In my case, accessory naming is simpler, just “<device_type> (<device_precise_location)”, where the “precise location” is within a room, for example, a water leak sensor under a “washing machine”. Full example: “Water Leak Sensor (Washing Machine)”. For the room I rely on the Location property of the device. But I see you way scales better. Thanks!

2 Likes

This is really useful, thank you

2 Likes

Thanks for the feedback! You’re absolutely right — the important thing is to have a naming system and stick to it.

I’ve just found that spaces and special characters like parentheses can sometimes make life harder in other environments, like Home Assistant.

Also, having both the location and device type in the name makes searches super easy — for example, finding all lights in my loft is just loft.lt*.

2 Likes

This is perfect. Thank you!

2 Likes

Good suggestions. I have something similar, but don’t have nearly the number of devices you have. It helps when devices go into other ecosystems, like Amazon Alexa and Google to keep names straight.

2 Likes

Some great tips in there for people just starting out. With only one or two items, I would have not thought of a naming convention.

1 Like

Same rules are applied to automation names.
1 my smart switch has 4 automations, and 100+ in total and here is name examples:

kitchen.sw:sc (lt.on) - single click when light is on
kitchen.sw:sc (lt.off) - … is off
kitchen.sw:lc - long click
kitchen.sw:dc - double click

4 Likes

That’s an excellent and important point. Naming your scenes and automations is just as crucial if you want to avoid chaos and keep a clear overview. Thanks for highlighting it!

My naming has gotten out of hand so I may need to adopt something like this. Especially trying to reconfigure stuff with unclear names and getting confused!

1 Like

Give it a try. Works great…

1 Like

Thanks for sharing, I have defiantly had problems in my HA setup naming thins and then not know witch device is actually witch.

1 Like

This is great advice. Thanks

1 Like

Thanks @RudyK - great ideas.

1 Like