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.

  • CocaineShrimp@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    5 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.