Neo coolcam door sensor issue

Hi,
I have 4 Neo Coolcam NAS-DS01Z z-wave door sensors. I am using “z-wave js to mqtt” HA add-on.
I have added them OK but I have noticed that a sensor called “Access Control - Door state” reports differently on each of them:
Device 1: when closed is showing as: “Window/door is closed” and when opened - “22”
Device 2: when closed is showing as: “23” and when opened - “Window/door is open”
Device 3: when closed is showing as: “Window/door is closed” and when opened - “Window/door is open”
Device 4: when closed is showing as: “23” and when opened - “22”

In the z-waveJS to mqtt addon control panel when I select the device in question (i.e. device 1) and browse the values , under Notification v8 I can see:
[12-113-0-Access Control-Door state] Door state → [23] Window/door is closed
and the value just changes to 22 when opened (no text)

How do I make the show the same info?
Thanks

1 Like

Re-interview may fix this, my experience with Neo Coolcam is, that some devices need to get re-interviewed even more times, until they get right. Keeping them awake during the re-interview increases the chance.

I am facing the same issue. Did you find a solution? Even after several re-interviews i am still getting the same error. I have 4 devices and all of them were working fine using OpenZwave. One workarround could be to use the “sensor state” on / off.

That is what I have done. Tried fixing it but without success.

Seeing a similar thing with a Vision Security ZD2105 (from Monoprice). After replacing the battery in this unit and updating ZWaveJS (not sure which of those things cause this) I see this in the debug info for the access control states:

      "states": [
        {
          "text": "Window/door is closed",
          "value": 23
        }
      ],

So there’s a mapping for value 23, but not 22 (when the door is opened).

Curious if you have a valid reading for the battery in your Monoprice/Vision ZD2105 ? Mine always shows 0%.
It also only shows the value 23 (door is closed), I don’t see text for the state at all.

I was messing with this again today and decided to do a re-interview and now it’s showing the battery at 100%. I don’t exactly believe that though either.
The device also failed to trigger the first time after the reinterview. Seems to be working now though.