Validate my naming strategy please

For the last 5 years naming of zwave entities the z-wave integration has annoyed me. I loved how MQTT / ZWAVEJS did it as i could specify a format. This is no longer possible as i want to use the integration for future compatibility / simplicity.

My issue stems from having three areas, each area having a z-wave deadbolt. I need / want the friendly name to be deadbolt in each area.

unfortunately this leads to devices where the entities are called lock.deadbolt, lock.deadbolt_2, lock.deadbolt_3 - this is not helpful when using things like pickers in the dashboard as i have no clue which rooms these are in (this is especially true for things like light switches where i have about 20 of them and they all appear as switch.x) - and don’t get me started on the sensor entities that don’t seem to use the friendly name at all - its impossible to figure out which sensor i need from some types of zwave devices as they are all named the same with just numerics

What i want is my deadbolts entities names to always start as follows:
lock.deadbolt.area.xxxxx

I see that when the z-wave js integration talks to an existing z-wave-js install the integration seems to use the name in zwave-js (but not the area name)

So my thought is:

1. delete my integration
2. rename all the names in zwave-js to be friendlyname+area
3. re-add the integration
4. remove the area portion by hand from the friendly name on each device and choose to not rename the related entities

then for future devices:

1. turn of home assistant setting in zwave-js-ui
2. initiate add from zwave-js-ui and use the naming convention i mention above
3. turn back on home assistant setting in zwave-js-ui wait for sync
4. remove the area name from the friendly device name and choose to not change entity names

I can’t think of a better way to achieve what i want and renaming the many devices and entities is not practical as some entities don’t get renamed when selecting the option ‘rename entities’.

Am i missing something? Is there a better way?

Here is another example, imagine i have 10 sink leak detectors - when using pickers in UI for entities how the heck am i supposed to know which of the 10 sensor_node_23_node_staus belongs to which friendly device? i will have 10 of these with v_2, v3_ etc… (i.e. i will have 10 of evey entry you see here with no name and all caled sink, sink_v2 etc if i use the integration as-is).

1 post - 1 participant

Read full topic