New Install - HKZW-DWS01 Door/Windows Sensor not identified

I was using a real old version of HA, just as lovelace started. Decided to install the latest and start all over using the same system, with everything plugged in same USB ports.

I selected the NUC download (for my Dell thin-client), burned to SSD. Everything but the Monoprice/Hank Electronics HKZW-DWS01 was found. I selected configure device, but that just gave me a link. Looking at the link, I searched for HKZW-DWS01 and didn’t find it, so I entered DWS01 and found it under Hank Electronics as DWS01. I then selected Re-interview device on each, open/closed the windows and let it run over night, but no joy. Note that one sits near my Z-Wave-Plus Gen5 dongle.

Is there a manual way of entering them in the new version?

I assumed that the NUC download is the OS version, however I noticed that in the config/info page, it states core.

Thanks,
Concord.

|Version |core-2021.5.1|
|Installation Type |Home Assistant OS|
|Development |false|
|Supervisor |true|
|Docker |true|
|Virtual Environment |false|
|Python Version |3.8.9|
|OS Family |Linux|
|OS Version |5.4.109|
|CPU Architecture |x86_64|

I found the user manual on how to wake up the door/window sensor and tried that, then selected re-interview, but new Zwave-JS does not see it at all.

It seemed to find my older door/window sensor, garage tilt, HAVC thermostat, motion/temp sensors, AC switches and my RGB blub (which I can now reliably change color now).

So it appears the Monoprice/Hank Electronics HKZW-DWS01 sensors are not supported with Zwave-JS.

It’s probably a bad idea to try to run both the legacy Zwave and Zwave-JS at the same time :).

Wrong order, you need to click the re-interview button first, then wake it up. These devices never wake up on their own, so it is required to manually wake them to get discovered. Other sensors wake up automatically after a configurable time, so eventually they get discovered automatically.

Not true. I have one of these. It works fine with Z-Wave JS.

It’s probably a bad idea to try to run both the legacy Zwave and Zwave-JS at the same time :).

Yes, this is a very bad idea. :wink:

Thanks, no matter what I tried, they won’t show up. I un-installed ZwaveJS and installed ZwaveJSmqtt, as it was shown to give more information. Except for one that I screwed (up trying to wake, exclude, include, force reset, etc), when the tamper or window opens/closes, it registers in the zwavejsmqtt log and updates the Last Active, but will not wake up manually and be identified.

I have 4 of these, batteries last a long time in these probably because they don’t have a wakeup interval. Will replace them with ZD2102-5, as they seem to be found, though they are ugly :).

Log on one that I tampered with, open/closed

2021-05-19 08:27:48.965 INFO ZWAVE: Node 9: value updated: 113-0-Access Control-Door state 23 => 22
2021-05-19 08:27:50.905 INFO ZWAVE: Node 9: value updated: 113-0-Access Control-Door state 22 => 23
2021-05-19 08:27:56.598 INFO ZWAVE: Node 9: value updated: 113-0-Home Security-Cover status 3 => 0
2021-05-19 08:27:57.151 INFO ZWAVE: Node 9: value updated: 113-0-Access Control-Door state 23 => 22
2021-05-19 08:27:57.303 INFO ZWAVE: Node 9: value updated: 128-0-level 100 => 100
2021-05-19 08:27:57.305 INFO ZWAVE: Node 9: value updated: 128-0-isLow false => false
2021-05-19 08:27:57.402 INFO ZWAVE: Node 9: value updated: 113-0-Home Security-Cover status 0 => 3
2021-05-19 08:27:58.496 INFO ZWAVE: Node 9: value updated: 113-0-Access Control-Door state 22 => 23
2021-05-19 08:28:01.819 INFO ZWAVE: Node 9: value updated: 113-0-Home Security-Cover status 3 => 0
2021-05-19 08:28:02.087 INFO ZWAVE: Node 9: value updated: 113-0-Access Control-Door state 23 => 22
2021-05-19 08:28:02.221 INFO ZWAVE: Node 9: value updated: 113-0-Home Security-Cover status 0 => 3
2021-05-19 08:28:02.625 INFO ZWAVE: Node 9: value updated: 128-0-level 100 => 100
2021-05-19 08:28:02.627 INFO ZWAVE: Node 9: value updated: 128-0-isLow false => false
2021-05-19 08:28:03.316 INFO ZWAVE: Node 9: value updated: 113-0-Access Control-Door state 22 => 23
2021-05-19 08:28:04.919 INFO ZWAVE: Node 9: value updated: 113-0-Home Security-Cover status 3 => 0

How are you trying to wake it?

According to instruction (see below in VII.), press the z button, tamper button and then move it away from magnet.

https://fccid.io/2AIOC-DWS01/User-Manual/User-manual-3046912

Try holding it down for 4 or 5 seconds instead.

No luck, in fact it doesn’t register in the logs anymore and Last Active didn’t update. Thanks for the suggestion.

I also have some DWS01 devices which I would like to use with Zwave-js. My controller is A Zooz ZST10. The inclusion of the DWS01 devices works, but after inclusion the device states are stuck on DoorOpen=off and Tamper=Off. Then I tried the Re-interview, manual wakeup steps. Using this I was able to get the devices to detect the Tamper button but the DoorOpen stayed at Off, even though I applied a magnet on and off to the DWS01 and saw the blue light on the device indicating it was sending a message.

Is there some special wakeup steps that need to be done to have the important DoorOpen state be recognized correctlhy after Re-Interview?