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 ?
  • spongebue@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    10 months ago

    As a side note, I really wish folders were implemented for devices and automations and such. Especially since I have a scene controller (and another on the way) with several buttons, each of which can have 6 different triggers (pressing 1-5 times or holding the button down). Oh, and more for the LEDs.

    • Padook@feddit.nl
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 months ago

      Yes! Especially automations! I would rather have tags than folders, so an automation could fit into more than one category (eg. Location, action) but I’d take anything over alphabetical!!

      • Aiyub@feddit.de
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 months ago

        I have monthly problems with nodered. I have transitioned most of my automations away from it.

    • ShepherdPie@midwest.social
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      I thought this was implemented on the dashboard. I don’t recall what exactly it’s called (context cards?) but I recall you could click a button to show a separate card or click and have it open a second ‘tab’ on the dashboard to control more things like with your scene controller.