NEO COOLCAM NAS-PD01Z Z-wave PIR Motion Sensor Detector problems

[Smiggel]

Hi,

Does anyone here have a NEO COOLCAM NAS-PD01Z Z-wave PIR Motion Sensor Detector?

I have added one to my network, but it does not seems to work at all. I am really disappointed with the device. It can be added to the z-wave network really easy, but that is basically it.

I enabled lux measuring, but the value returned is 1 and after the first value 45 minutes it has not changed. It's not updating. Also the detection is not working. The sensor does not do anything at all, when I move in front of it. Sensor does not pick up anything at all even with sensitivity set to 8.
The sensor is in a sleep modus almost instantly and constantly.

Does anyone else here have the same problems? Am I doing something wrong with the sensor? Any help would be appreciated.

[heggink]

Not sure about the Lux side but I have a bunch of them all with working pir sensors.

[Smiggel]

Hmmm ok. I set the lux level update to 5 minutes, but it does not update at all. Value is also way too low. The Xiaomi lux sensor in the hub, has the correct value.

[heggink]

I never bought these for their Lux capacity and if seems like the ones I have don't report it correctly if at all.

[Smiggel]

Ok. Well they advertise with it. Even on the box it says they measure light. Guess they really don’t or that it’s not stable. Sucks, as I really wanted them to measure light too.

[heggink]

I'll mess around with the settings and see what it does. There are a couple of parameters that define how it reports Lux changes.

[Smiggel]

Thanks. Perhaps you can find something. I have no luck so far. Perhaps I just received a bad version.

[heggink]

Weird: 2 out of 3 have a different parameter 9. Only 1 has devices it as lux level change but this is the one that works the best... Reduced it from 100 to 20. Maybe exclude and reinclude...

[akamming]

I just (last friday) installed the same sensor. I had some problems like this at first as well. I solved them by doing a hardware reset (push the button for 10 secs) and then reinclude in the network. Now it seems to work fine.

The only thing i noticed is that temperature is only reported if it was changed more than 0.5 degree celcius. This results often in domoticz reporting showing the sensor in red, because the update was more than 2 hours ago if the temperature does not change.

Does anyone now how to increase this 2 hour timeslot in domoticz?

[Smiggel]

Weird: 2 out of 3 have a different parameter 9. Only 1 has devices it as lux level change but this is the one that works the best... Reduced it from 100 to 20. Maybe exclude and reinclude...

Excluded and included many times already. Lux value is set at registration and then does not update anymore.

[Smiggel]

I just (last friday) installed the same sensor. I had some problems like this at first as well. I solved them by doing a hardware reset (push the button for 10 secs) and then reinclude in the network. Now it seems to work fine.

The only thing i noticed is that temperature is only reported if it was changed more than 0.5 degree celcius. This results often in domoticz reporting showing the sensor in red, because the update was more than 2 hours ago if the temperature does not change.

Does anyone now how to increase this 2 hour timeslot in domoticz?

Hmmm ok. Thanks for the tip. Will try that tomorrow.

[heggink]

If both pir and Lux don't work then the unit does look faulty.

[Smiggel]

I just (last friday) installed the same sensor. I had some problems like this at first as well. I solved them by doing a hardware reset (push the button for 10 secs) and then reinclude in the network. Now it seems to work fine.

The only thing i noticed is that temperature is only reported if it was changed more than 0.5 degree celcius. This results often in domoticz reporting showing the sensor in red, because the update was more than 2 hours ago if the temperature does not change.

Does anyone now how to increase this 2 hour timeslot in domoticz?

Hardware reset failed. Does not help either.

[Smiggel]

If both pir and Lux don't work then the unit does look faulty.

Pir is working. Lux is not.

[heggink]

ONe thing I found is that I have different versions of settings. I have 2 where parameter 9 on the config page says "basic set level" and I have one where it says "Ambient illumination Lux Level Report". The last reports reasonably well, the other 2 do not report by any means. I had one spare lying around so included it and it also gives the "Ambient..." as parameter 9 (This parameter defines by how much Lux Level must change, in lux, to be reported to the main controller.) so I suspect that the zwave xml file changed somewhere during including these. I also changed parameter 9 from the default 100 to 20 for the backup PIR. It reports LUX already but let's see if it behaves. If it does then I may exclude and re-include them again to get a better definition file.

Question then is what OS you are on and what version domoticz you run. Pls check what your parameter 9 says when you click the PIR on the zwave devices page.

Herman
ps: I suspect that lowering the lux reporting will drain the battery...

[Smiggel]

@heggink Thanks for testing it too.

My parameter 9 (Ambient illumination Lux Level Report) is set to 20.

I run Domoticz version 4.9700 stable on a Raspberry Pi 3 with Raspbian. My z-wave devices are connection to an Aeotec Z‑Stick ‑ Gen 5. My Fibaro dimmer 2 works fine. Same for the Neo Power plugs. No issues with them at all.

[heggink]

Ok.. So much for that thought . Anyways, let's see...

[Smiggel]

I think my pir is just not ok. Can’t think of anything else.

[heggink]

My test PIR does give readings although infrequent. Based on what I see, I would not trust the device's lux capabilities. My couple of philio's are way better but probably twice as expensive as well.

[Smiggel]

Hmmm. Ok. Guess it’s not only my unit then. Sucks that it does not do what they advertise. Guess I have to look into some other lux sensors then.