Here, have a look at these as an example of the difference:
The battery value is undefined, is that all? You can try a re-interview. If it doesn’t update, watch the driver logs to see what is reported, maybe the device is not returning a proper value.
The values are sorted in a different order? Report a bug to zwavejs2mqtt if that’s a concern. Lexicographical sorting (the second screenshot) always probably makes more sense.
Yes. Having things in the same order would be a good start!!
Bought one of these door sensors and had same problem tonight. Everything looked good in logs and dbug.
(But No sensors appeared on inclusion but everthing looked like it was communicating fine, even seen open door msging in dbug) I tried 20 times using button to add sensor to dashboard at no avail. But I found if you click the “+ entities not shown” then you see grayed out “sensor state” when you click it. Under advanced click “enable” it will add the sensor status. Takes about 30 seconds and it will show up after you go out and come back.
I also am having a very similar issue.
I had these sensors working on an older install that was not recently updated and accidentally deleted and I was forced to setup a new install…
on the new install (hass VM via Virtualbox) the sensors are picked up nearly seamlessly but as Peter noted the “access control” entity is disabled by default. When I follow the steps that Peter describes to enable it, it works almost as expected, except when the door is open it’s being reported as “Z-Wave Door/Window Sensor: Access Control - Door state changed to 22” where as seen previously in this thread 22 is supposed to be “open”
any clues how to remap this so all my new automations are not tied to state “22”? 
2 Likes
I’m also now noticing that the entity in question isn’t available for automations either
I think you are experiencing a different issue, which is related to the recent updates. See the thread here for more details.
AFAIK, no workaround yet other than rolling back to an earlier version if you have a backup.
Yes, I am on that thread as well. The error below was what I was receiving with that device.
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!
I found my issue, the z-wave sensors are not on by default. I have to enable them explicitly. Its working now, thanks.
Note: I do see a code 22 when the door is open and a description of it being closed. This is occurring with my ecolink and aerotec door sensors which I recently added.
1 Like
I’m also running into this issue. I removed and added back the DWZWAVE25 numerous times, and also tried re-interviewing. Agree with onl1kairiKai that you can enable the door state, and it correctly shows the “Window/door is closed” state when closed, but when you open it, the door state reports “22.” The automations don’t like the “22.” My Z-Wave JS version is 0.1.70. The firmware for the DWZWAVE25 is 10.1
2 Likes