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.

  • just_another_person@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    10 days ago

    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.

    • Acamon@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      9 days ago

      Yeah, I was confused about some lamp always being on when I woke up, and realised I’d replaced it’s smart socket with one that had previously been used for a coffee machine. Deleting and repairing sounds like wisdom.

  • CocaineShrimp@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    10 days ago

    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.

  • shortwavesurfer@lemmy.zip
    link
    fedilink
    English
    arrow-up
    2
    ·
    9 days ago

    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.

  • fruitycoder@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 days ago

    I name them like the story about them … Its surely unsustanble but 12 nodes and three iot devices and it’s still going strong

    The AC is MrColdMizer The PC of cobled spare PC part is TheResurection One laptop is Wapwop and Gamer1 Etc, etc

    I then use labels to keep track of conditionals like location, circuits, functions, etc

  • CameronDev@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 days ago

    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.

  • spitfire@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 days ago

    I do exact that and rarely move stuff. When I do I rename it. Most of the stuff I have is Zigbee, so I rename it in Zigbee2MQTT, select the option to rename it in HA too.