I have a concoction of devices from all kind of manufacturers with cryptic codes in their names. Each device exposes multitude of sensors which makes the dashboard look like a mess.

  1. Is there a best practice for renaming devices ? Do you name them by their location ? By their utility ? manufacturer ?
  2. How do you identify the devices later in case there’s a problem and one needs to be replaced / battery need to be replaced ?
  • Matt The Horwood@lemmy.horwood.cloud
    link
    fedilink
    English
    arrow-up
    7
    ·
    7 months ago

    For my Zigbee things I use this

    example:

    • 00 - Sensor - Hall - PIR - Motion
    • 01 - Switch - Bedroom 01 - Main Light

    So to break it down:

    • First 2 numbers represent the floor, 00 = Ground, 01 First Floor and so on.
    • Describes the type of device.
    • Room Name.
    • Describes the Function of Device, eg PIR, Temperature Sensor, Contact Sensor….
    • Used to describe the entities of the device.
  • limelight79@lemm.ee
    link
    fedilink
    English
    arrow-up
    5
    ·
    7 months ago

    Organize? Hahaha ohmygod best laugh I’ve had in a few days.

    Some devices have the generic names from the manufacturer because I had issues and had to re-join them a few times, so I got tired of typing the “correct” names. Also I have a light switch labeled “front porch” which is really inaccurate because I’m not turning the porch on and off, it’s the lights! And those lights are now zigbee bulbs of their own, but they at least got more sensible names (“porch light doorbell side” and “porch light right side”).

    But I may switch to zigbee2mqtt, so I’ll have a chance to redo all of it anyway.

    In general I don’t have so many devices that knowing what is what isn’t a major issue. I name them better in Lovelace, of course.

  • prenatal_confusion@lemmy.one
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    7 months ago

    Name is the functio, Like ceilinglight or ceiling light middle door middle etc. And then I assign the location. Seems to work.

  • cooljimy84@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    7 months ago

    Before areas was a thing in HASS I would name things with an area name. ESP32-5-Bedroom. Now I just leave it what ever it defaults to, then use HASS to name them, and then put them in an area.

  • StrawberryPigtails@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    3
    ·
    7 months ago

    I may be wrong, but I think best practice says it doesn’t matter how you name your whatevers, so long as the convention you use is consistant. Within HA I tend to use the format <DeviceType>.<Room>.<WhereOrWhat>.<NumberIfRestMatches>.

    For example, the plugs that control my space heaters in my livingroom are switch.livingroom.heater.1 and switch.livingroom.heater.2. The controls for the lights in the livingroom is button.livingroom.wall. Please don’t ask why I call plugs switches and controls buttons, I don’t have an answer, I just do. 🤷

  • Claude Flammang@dju.social
    link
    fedilink
    arrow-up
    2
    ·
    7 months ago

    @barbarosa
    For all those sensors (temp, current etc.) I always prefix the entity ID and friendly name with the area name.
    I create areas like “kitchen fridge” or “garage fridge” to keep my stuff organized.