Duplicate Aeotec Door / Window Sensor 7 (Pro)

[brodyhoskins]

I have two door/window sensors, one is an Aeotec Door/Window Sensor 7 (non-Pro) and the other is an Aeotec Door/Window Sensor 7 Pro.

At some point, a Z-Wave JS UI update caused both sensors to have two entities each in Home Assistant (I'm currently on UI v8.1.3.1.33a6f57 / 10.14.0):

• binary_sensor.front_door_window_door_is_open
• binary_sensor.front_door_window_door_is_open_2
• binary_sensor.patio_door_window_door_is_open
• binary_sensor.patio_door_window_door_is_open_2

This causes Home Assistant to think that all doors are closed all the time because the state is never updated on the non-_2 entities.

I've completely deleted the integration in Home Assistant, restarted it, and re-added JS Wave JS UI but the duplicate entities re-appear, and it doesn't appear to be Home Assistant's fault.

For reference, I've disabled the MQTT API and use only the WebSocket API.

How can I find the entities being provided to Home Assistant so that I can debug the issue?

[kpine]

1. Re-interview the device.
2. Disable the non-working entities.
3. Did you not see the issue template? Please submit HA related issues to HA.

You will see there is already an issue at HA: home-assistant/core#88060

But, HA is working as it is currently designed. The driver provides 4 different states for a door sensor (close, open, regular position open, tilt position open), and an additional "simple" value for simply open/close.