When adding a door/window sensor device using ZwaveJS, I end up with one duplicated entity for the door_window_is_open type entity. For the other entities of the device, there are no duplicates.
I have the MQTT Gateway disabled in the ZwaveJS Control Panel, so the Z-Wave JS UI should be acting only as a Control Panel.
This happens with at least Zooz and Ecolink door sensors. (See Screenshots below)
This has only started happening since I recently updated both HomeAssistant and ZwaveJS instances. I run both as docker containers Does anyone have any ideas on what is causing this and how to prevent it? I’d appreciate any suggestions.
You can just disable the ones you don’t need. The extra ones are because of the way Z-Wave JS exposes the values to the applications.
It’s not possible to determine whether a device supports “tilt” or “regular” position door status notifications, so it just generates all the possibilities.
@freshcoast Thanks for the explanation. That does make sense. I’ll mark your response as a solution. Unfortunately, I’ll need to rename as well as disable the ones I don’t need.
Otherwise, the numerical suffixes will all be inconsistent with the other entities of that device - the first device would have both binary_sensor.door_window_is_open and binary_sensor.door_window_is_open_2 (even if the second is disabled), and so the second device couldn’t use binary_sensor.door_window_is_open_2 and would end up with binary_sensor.door_window_is_open_3 and binary_sensor.door_window_is_open_4 - while all its other entities such as its battery level and node status will have a _2 suffix.
However, HA does not have any special discovery logic or naming for this new sensor, so it will appear identical in naming to the existing one (original name). Therefore, there will be a total of 4 entities. Depending on the device, some will have duplicate functionality (open/close and simple), and some not work at all (regular position, tilt position). You can just disable the entities that aren’t useful. To determine which entity corresponds to the “Simple” value, you can download the device diagnostic and find the binary_sensor entity that maps to “Door state (simple)”.
I’m really hoping someone will take up the task of adding discovery logic or naming for the open/close vs simple door status updates - since the lack of it causes a good bit of confusion with the inconsistent entity_id suffixes.
Same here with all my zooz window sensors.
Also seeing a lot of extra sensor/config items with other devices like the zcombo smoke alarms. Not end of the world but really a pain to try to keep things clean.
I get duplicates mysteriously turning up for my z-wave Devolo TRVs. It’s not the end of the world but pretty irritating, they annoy my significant other.
Thank you for your response. I’m referring to the Devolo TRV in “Bedroom Steve” as an example. In the images I’ve provided, you’ll notice that there’s a duplicated control in the overview. Additionally, the device information now shows a new device named “climate.bedroom_steve_devolo_2”. I’m aware that it’s possible to disable these duplicate controls, but I’m actually struggling to find an option to completely remove them. Could you guide me on where to find the removal option, or is disabling them the only solution available? Your advice would be much appreciated!
