Trying to get my head around the purpose of the two.
I know device label overrides device name but where are the two used differently?
For example, in the devices list I'm expecting it to show the device name for organizational purposes and I'm hoping that the label is used in things such as dashboards so we can have a more friendly name.
The dashboard does use the the label but the devices list also does use the label. Makes me wonder what the purpose of the name is then?
Sure. This is standard practice for any web input. Like I said, we do our best to sanitize the inputs, but I recommend avoiding special characters in any text input unless it specifically needs it.
For me, I use the Device Name as a way to identify the actual hardware I am using. It is really helpful since I use multiple manufacturers of dimmers, dual relays, in-wall switches, etc. That way I don't have to extract stuff out of the ceiling or wall boxes to remind me what I installed as I experiment with different drivers and such.
The Device Label is the friendly name of what Wife wants in Dashboard, Alexa, etc to used and see. I add a little description at the end of virtual labels to help remind me that this particular device is not physical item and it's purpose such as hueGroup or LifxGroup
Patrick,
I am trying to create a more universal zigbee device Handeler the way that smartthings does. I see the way that smartthings does this is to include a DeviceJoinName: in the fingerprint profileid. In smartthings, this is the Device Name used when adding the device (i.e. Ikea vs Amazon Smart zigbee switch use the same device handler, but the default name is either Ikea or Amazon based on the fingerprint). Using this, multiple devices made by different device manufacturers can use the same device handler. But, each differ fingerprint device, can have a basic default join name. How is this done in hubitat, it seems to simple use the driver name instead. Am i missing something or is this simply not supported in HE?
Most of our drivers contain at lease two separate fingerprint entries, some more than 10, each fingerprint defines a specific device that works with that driver, this works the same way in st. We just don't currently assign deviceJoinName to the driver name. Anoying, but not a high priority for us right now.
Since I have so many devices and device types I've started using emojis to identify certain things, like groups vs individual device. This doesn't appear to have broken anything... but will it?
Patrick has been gone for about a year, and Iām not sure when exactly this became available, but you can do this now. See my screenshot below for an example.
Yes, but I wanted to sort on both/either so I can use the names for something highly descriptive eg "Sensor - attic - window" and the labels for the short names on dashboards or voice assistants eg "window" ( as the dashboard would already be grouped by room). It's not really the searching I was after. And I don't even remember the names of half the things till I see them which is why logical sorting is so important to me
NB I knew Patrick was gone, I was just having a little affectionate dig at the prediction
Also BTW for some reason my device list doesn't look like yours. I don't have a Disable box