Missing Door State entity when adding Ecolink DWZWAVE25 sensors

Similar issue as what was described in this post, except the entity never appeared for new sensors I am trying to add, and the solution there (excluding and re-adding mulitple times) is not working for me.

Fresh install of HA OS on a Pi3B. Using the ZWaveJS2mqtt addon. Aeotec Z-stick 7. Also have the ZwaveJS integration installed. DriverVersion: 10.0.3, ServerVersion: 1.22.1

I have 5 of these Ecolink DWZWAVE25 sensors and successfully added the first three. For each of those there is a Door State entity (which was enabled after adding the device) and 6 hidden/disabled entities listed in the ‘Sensors’ section of the device screen in ZwaveJS.

When adding the last two devices, only the 6 hidden/disabled entities are added in sensors, and the Door State entity never appears. If I do a diff on the device diagnostics between the working and non-working devices, I see that the following entity is missing:

{
        "domain": "binary_sensor",
        "entity_id": "binary_sensor.z_wave_door_window_sensor_access_control_window_door_is_open",
        "original_name": "Z-Wave Door/Window Sensor: Access Control - Window/door is open",
        "original_device_class": "door",
        "disabled": false,
        "disabled_by": null,
        "hidden_by": null,
        "original_icon": null,
        "entity_category": null,
        "supported_features": 0,
        "unit_of_measurement": null,
        "primary_value": {
          "command_class": 113,
          "command_class_name": "Notification",
          "endpoint": 0,
          "property": "Access Control",
          "property_name": "Access Control",
          "property_key": "Door state",
          "property_key_name": "Door state",
          "state_key": 22
        }
      },

There is also a value that is missing one of the state descriptions:

{
          "endpoint": 0,
          "commandClass": 113,
          "commandClassName": "Notification",
          "property": "Access Control",
          "propertyKey": "Door state",
          "propertyName": "Access Control",
          "propertyKeyName": "Door state",
          "ccVersion": 5,
          "metadata": {
            "type": "number",
            "readable": true,
            "writeable": false,
            "label": "Door state",
            "ccSpecific": {
              "notificationType": 6
            },
            "min": 0,
            "max": 255,
            "states": {
              "23": "Window/door is closed"
            }
          }
        },

The states dict ought to have another entry ("22": "Window/door is open",)

Have tried re-interviewing both devices multiple times, and have also tried excluding and then re-including the devices multiple times. Neither strategy has worked.

1 Like

I am getting the exact same behaviour with Aeotec Door Sensor 7 (ZWA012). I’ve got existing devices which added fine previously (a couple of months ago) with their binary sensors still there and working ok.

It’s only all new devices that aren’t adding correctly now with the exact same behaviour of all sensors hidden, open/close reporting value 22 or “Window/door is closed” only and totally missing the binary open/close sensor.

One thing that occurred to me last night was that I installed the first three (working) devices before some updates to Z-waveJS and ZWaveJS2MQTT, and that could be the culprit. See, for example, this issue on the Home Assistant Core github page.

I think my setup started with 0.1.65 or 0.1.66 and 0.45.0, and is now at 0.1.68 and 0.46.0, respectively. My backups only show that I can roll back to 0.1.66 so that’s most likely where it was when I started.

In fact, while typing this out I decided to actually check. Just rolled back ZWaveJS2MQTT to the 0.45.0 release, then re-interviewed my device, and now it works! Geez I wish I had thought to try that before wasting 4 hours last night.

Anyway, give that a shot if you can. I added a bug report for the addon (hopefully the correct place, though I’m sure the friendly devs will inform me if not).

1 Like

Bump to this, I’m having same issue with gen7 stick and zwaveJS up to date.

Old door sensors (aeon DSB129 / SW120) were added and worked like a charmed, a new zooz ZSE41 never worked.
As I’m new with HA, i’ve started to mess around and uninstall/reinstall zwaveJS, then started to reinterview old sensors… and now I do not have any door sensor that works.

Just joined to add to this post:

I’ve just started my Home Assistant journey and already hitting a snag. Devices arrived today.

I have a Aeotec Z-Stick 7 (ZST10-700) and a Aeotec Door / Window Sensor 7 Pro (ZWA012). The closed state is displayed correctly, but the open state is shown as 22. This seems to cause the automation not to be able to save. After reopening an automation, the initial trigger state is empty.

The Z-Stick is running Firmware: 7.11.0. I will try to update to 7.17.2 but I doubt that this is the cause of the issue.

1 Like

Definitly upgrade the firmware of the stick, 7.17.2 is know to resolve a lot of issues, but indeed not what you are facing.
What zwavejs version are you running ?

For information, after downgrading to 0.1.64 my door sensors are now working fine again.

I’m really surprised this issue is not more popular. Maybe it’s related to 700 stick ?

I’m running into the same issues and seeing errors in the zwave logs.

2022-09-08 02:13:12.844 ERROR ZWAVE-SERVER: Node 23 does not support the Command Class Configuration! (ZW0302)
ZWaveError: Node 23 does not support the Command Class Configuration! (ZW0302)
at Object.get (/opt/node_modules/@zwave-js/cc/src/lib/API.ts:161:13)
at Object.get (/opt/node_modules/@zwave-js/cc/src/lib/API.ts:354:28)
at ZWaveNode.schedulePoll (/opt/node_modules/zwave-js/src/lib/node/Node.ts:1105:12)
at Driver.schedulePoll (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:2079:15)
at ConfigurationCCAPI.schedulePoll (/opt/node_modules/@zwave-js/cc/src/lib/API.ts:228:25)
at Proxy.ConfigurationCCAPI. (/opt/node_modules/@zwave-js/cc/src/cc/ConfigurationCC.ts:432:33)
at ZWaveNode.setValue (/opt/node_modules/zwave-js/src/lib/node/Node.ts:914:19)
at NodeMessageHandler.handle (/opt/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:24:33)
at Client.receiveMessage (/opt/node_modules/@zwave-js/server/dist/lib/server.js:96:62)
2022-09-08 02:13:12.897 ERROR ZWAVE-SERVER: Node 23 does not support the Command Class Configuration! (ZW0302)
ZWaveError: Node 23 does not support the Command Class Configuration! (ZW0302)
at Object.get (/opt/node_modules/@zwave-js/cc/src/lib/API.ts:161:13)
at Object.get (/opt/node_modules/@zwave-js/cc/src/lib/API.ts:354:28)
at ZWaveNode.schedulePoll (/opt/node_modules/zwave-js/src/lib/node/Node.ts:1105:12)
at Driver.schedulePoll (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:2079:15)
at ConfigurationCCAPI.schedulePoll (/opt/node_modules/@zwave-js/cc/src/lib/API.ts:228:25)
at Proxy.ConfigurationCCAPI. (/opt/node_modules/@zwave-js/cc/src/cc/ConfigurationCC.ts:432:33)
at ZWaveNode.setValue (/opt/node_modules/zwave-js/src/lib/node/Node.ts:914:19)
at NodeMessageHandler.handle (/opt/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:24:33)
at Client.receiveMessage (/opt/node_modules/@zwave-js/server/dist/lib/server.js:96:62)
2022-09-08 02:13:14.062 ERROR ZWAVE: Error while writing 0 on 23-112-0-1: Node 23 does not support the Command Class Configuration! (ZW0302)
2022-09-08 02:13:14.063 ERROR ZWAVE: Unable to write 0 on 23-112-0-1
2022-09-08 02:13:14.095 ERROR ZWAVE: Error while writing 255 on 23-112-0-1: Node 23 does not support the Command Class Configuration! (ZW0302)
2022-09-08 02:13:14.096 ERROR ZWAVE: Unable to write 255 on 23-112-0-1
2022-09-08 02:13:14.130 ERROR ZWAVE: Error while writing 0 on 23-112-0-1: Node 23 does not support the Command Class Configuration! (ZW0302)
2022-09-08 02:13:14.131 ERROR ZWAVE: Unable to write 0 on 23-112-0-1
2022-09-08 02:13:14.163 ERROR ZWAVE: Error while writing 255 on 23-112-0-2: Node 23 does not support the Command Class Configuration! (ZW0302)
2022-09-08 02:13:14.164 ERROR ZWAVE: Unable to write 255 on 23-112-0-2
2022-09-08 02:13:14.196 ERROR ZWAVE: Error while writing 255 on 23-112-0-1: Node 23 does not support the Command Class Configuration! (ZW0302)
2022-09-08 02:13:14.196 ERROR ZWAVE: Unable to write 255 on 23-112-0-1
2022-09-08 02:13:14.229 ERROR ZWAVE: Error while writing 255 on 23-112-0-1: Node 23 does not support the Command Class Configuration! (ZW0302)
2022-09-08 02:13:14.229 ERROR ZWAVE: Unable to write 255 on 23-112-0-1
2022-09-08 02:13:14.259 ERROR ZWAVE: Error while writing 255 on 23-112-0-2: Node 23 does not support the Command Class Configuration! (ZW0302)
2022-09-08 02:13:14.259 ERROR ZWAVE: Unable to write 255 on 23-112-0-2
2022-09-08 02:19:38.116 INFO ZWAVE-SERVER: Client disconnected
2022-09-08 02:24:47.831 INFO ZWAVE-SERVER: Client disconnected
2022-09-08 02:25:35.534 INFO ZWAVE-SERVER: Client disconnected
2022-09-08 02:40:46.439 INFO ZWAVE-SERVER: Client disconnected
2022-09-08 02:41:25.347 INFO ZWAVE-SERVER: Client disconnected
2022-09-08 02:43:29.932 INFO ZWAVE-SERVER: Starting logging event forwarder at debug level
2022-09-08 02:43:32.295 INFO ZWAVE-SERVER: Stopping logging event forwarder
2022-09-08 02:52:09.539 INFO ZWAVE-SERVER: Client disconnected
2022-09-08 03:04:12.616 ERROR ZWAVE: Error while writing ‘test’ on 25-119-0-location: Node 25 does not support the Command Class Node Naming and Location! (ZW0302)
2022-09-08 03:04:12.617 ERROR ZWAVE: Unable to write ‘test’ on 25-119-0-location
2022-09-08 03:04:12.834 ERROR ZWAVE: Error while writing ‘test’ on 25-119-0-location: Node 25 does not support the Command Class Node Naming and Location! (ZW0302)
2022-09-08 03:04:12.835 ERROR ZWAVE: Unable to write ‘test’ on 25-119-0-location
2022-09-08 03:08:43.246 INFO ZWAVE-SERVER: Client disconnected
2022-09-08 03:09:22.331 INFO ZWAVE-SERVER: Client disconnected
2022-09-08 03:09:28.260 ERROR ZWAVE-SERVER: Cannot check for firmware updates for node 7: Failed to query fingerprint from the node! (ZW0260)
ZWaveError: Cannot check for firmware updates for node 7: Failed to query fingerprint from the node! (ZW0260)
at ZWaveController.getAvailableFirmwareUpdates (/opt/node_modules/zwave-js/src/lib/controller/Controller.ts:4526:10)
at Function.handle (/opt/node_modules/@zwave-js/server/dist/lib/controller/message_handler.js:203:30)
at Client.receiveMessage (/opt/node_modules/@zwave-js/server/dist/lib/server.js:96:62)
2022-09-08 03:13:04.090 INFO ZWAVE-SERVER: Client disconnected
2022-09-08 03:13:04.095 INFO ZWAVE-SERVER: Server closed
2022-09-08 03:13:04.145 WARN BACKUP: Store backup is disabled
2022-09-08 03:13:04.145 WARN BACKUP: Nvm backup is disabled
2022-09-08 03:13:04.156 WARN BACKUP: Store backup is disabled
2022-09-08 03:13:04.156 WARN BACKUP: Nvm backup is disabled
2022-09-08 03:13:04.757 INFO ZWAVE-SERVER: ZwaveJS server listening on 0.0.0.0:3000
2022-09-08 03:13:05.587 INFO ZWAVE-SERVER: DNS Service Discovery enabled
2022-09-08 03:13:25.375 ERROR ZWAVE-SERVER: Cannot check for firmware updates for node 7: Failed to query fingerprint from the node! (ZW0260)
ZWaveError: Cannot check for firmware updates for node 7: Failed to query fingerprint from the node! (ZW0260)
at ZWaveController.getAvailableFirmwareUpdates (/opt/node_modules/zwave-js/src/lib/controller/Controller.ts:4526:10)
at Function.handle (/opt/node_modules/@zwave-js/server/dist/lib/controller/message_handler.js:203:30)
at Client.receiveMessage (/opt/node_modules/@zwave-js/server/dist/lib/server.js:96:62)

Also have this issues with Aeotec 5 stick and Aeotec door and window sensor 7

Glad I found this post was losing it as a total newbee moving to Home Assistant

Has this bug been logged with developers, not sure when this might get resolved.

This was fixed for me when I updated ZWaveJS2MQTT and then re-interviewed the node! See Door/window sensor issues in zwave-js 10.0.4 · Issue #2653 · zwave-js/zwave-js-ui · GitHub