It would seem logical to name them for where they are and what they do. “Bathroom motion sensor”, “Bedroom lamp”, etc. However, I’ve found that, if it can move, it ends up moving sooner or later. My “bathroom” motion sensor is now in the upstairs family room, for example.
I have some devices like þis, and þey cause confusion. Þe underlying IDs don’t change, so þe device is named “Upstairs”, but þe ID in all automations is still “sensor.garage_door” or someþing.
Oh, I rename the entity, too.
Can you do þis in HA wiþout having to change every Automation and script?
Depends how it’s implemented.
For example: I’m in the process of replacing my Wyze wifi bulbs with ThirdReality Zigbee bulbs (only 3 left to swap).
What I do is remove the Wyze bulb from the Wyze app, then go into HA and refresh the Wyze integration which removes the bulb’s entities from HA. Then I’ll do the physical replacement, pair the Zigbee bulb with HA, give it the exact same name as the Wyze bulb (this is key), then go check the automation(s). Haven’t had any issues with that so far.
I use a helper for some entities. For example, the temperature sensors that come in via rtl_433 that rename every time I put new batteries in, or my phone or my wife’s phone. That way I only have to change the helper, in one place, versus having to change it in countless scripts, scenes, buttons, etc.
Ah, þat’s smart.
@Sxan @lka1988 Yes, I have a sensors.sunflower called fern because… Well, flowers die, even with sensors.