I have a Neo CoolCam Door/Window Detector sensor that only reports Sleeping (CacheLoad) in HASS (0.45-DEV)
In open-zwave-control panel it seems to report correctly on/off
Is there any configuration that needs to be done for it to work correctly in HASS?
EDIT: this seems to be a normal behavior on battery sensors. Thead can be closed
Hi frelev
I have the same door/window sensor. I am struggling to add it. I have tried both inside of HASS and outside of HASS using OWCP. How did you add the sensor? Did you have any trouble adding it?
Thanks,
//JM
After adding it to the network using my Z-wave stick it took a while for it to appear with correct name and such.
Try to keep it awake using the button for it to register in HASS properly. It goes to sleep very fast
Hi
Okay. I googled some more yesterday and I think it is the US version. It does not say either or on the package. It says E-D03-B3-505 and then a lot of numbers on the package. Inside the main component it says 20160326 E/U which might imply EU version but who knows.
This is the version I have: NAS-DS01Z
Thanks
I think I have the same, but NO I can´t include it. I have power plugs and motion sensor from same company and no problem to add them.
I connected my NEO Coolcam door sensor like this:
Hello,
I had the same issues with neo coolcam pir sensor and door sensors etc.
Then a read on this forum to add te zwave devices as secure node.
Since then i never had any problems like this anymore.
Maybe this will help some one.
Regards
Mike
I have the same, and added them the same way. Yet after a few minutes they stop working. Until I restart Home Assistant, then they work again… for again a few minutes…
Any thoughts what the problem could be?
Edit:
I’ve add them as secure node. Same issue, still not working after a few minutes.
Did you manage to fix this issue? I have a Neo CoolCam door/window sensor and I’m having issues adding it.
Are you using ESX 6.5?
If you are using Aeotech Zwave Z-Stick gen5 and are running ESXI 6.5 you need to disable the Newer (vmkusb driver) because this driver doesnt play well with the z-stick. You need to enable the legacy driver. Easy want to do this is to enable SSH on your ESXI server and start an SSH session enter “esxcli system module set -m=vmkusb -e=FALSE” (without quotes) then enter “esxcli system module list” (without quotes) and verify that the VMKUSB driver is set to FALSE. Reboot the ESXI host and start the ssh session one more time to verify that the driver is still sent to FALSE. Then all of your ZWAVE headaches will go away.
I’m using Hassio on Raspberi Pi 2
Sorry, than I don’t know how to help you.
I have the sensor included as a secure device, but moving the magnets does not generate on/off events. The sensor reports battery etc. so it is transmitting (sending/receiving). Only no binary sensor state change.
What’s wrong?
@metbril Exactly the same problem here: the binary sensor does not detect any state change. Dit you fix it?
Edit: silly me: apparently the door sensor only detects the magnet on one side and not the other. It does work for me now, changing the binary sensor state 
Thanks,
I was just searching the web for a solution and your description did the trick for me.
Great help!
Dietger
Hi all,
I had the same problem and I fixed it up when including the sensor very close to my HA.
The sensor works well when i’m are close to my HA but don’t receive any signal when far from my HA (3m for example).
I don’t find any solution so far even when installing a powered zwave device close to it.
If someone has an idea …
Hello,
I have three of these sensors. The furthest (but last to add) works. The others do not notify when the door is opened.
I do not know what it could be.
Did anyone of you manage to solve these issues?