The default is 12 hours, yes.
I have set it to 4 hours and turned off the LED. It was 2 days ago. It still wakes up every 12 hour, and the LED is still on.
I have not tried yet, but I suspect if i take it down and do a manual wake up, it will probably process the changes. I know battery devices are difficult. I have a few of them. And they´re all suffering from not really updating the configuration when I suspect them to. I also have a Aeotec Multisensor 6, which is driven from USB. It works like a dream. And then I have a 230volt dimmer (Fibraro FDG212), which is working like a dream as well.
The good thing is, they´re all working when it comes to their functions. But it makes me wonder if battery z-wave devices is really worth it. I also wonder if the zwave controller has an influence. I´m using a UZB1 dongle. Maybe this just isn´t good enough.
In my setup I have used thing and items configuration in Paper UI. Did you setup items in Paper UI or configuration files? I suspect that there is something wrong with PaperUI because switch linked to sensor_binary channel shows only label in control section (no switch on the right side of the label). In the same time this item works properly in Basic UI.
I´ll have to look later tonight, cause I´m in the middel of converting all my PaperUI items to configurations files. And I don´t remember if I have done this Neo Coolcam yet.
But… I did start with PaperUI items, so I know it works for sure, from PaperUI.
I suspect that there might be something wrong with the device itself. I tried one more time to wake it and then battery level 100 % and constant 0 in luminance appeared. But in the same time log stopped showing movement detection from binary sensor. Then I have excluded and included device into network and now switch works correctly in PaperUI and Basic UI but rest of the data is not shown. I am not sure if it is worth to debug this further… Thanks for your support.
I had to wake up my Coolcam quite a few times, before it got fully included. Also, make sure you´re close to your zwave controller when doing so. This is a highly important part specially the first times when you add a battery driven device to your network.
Also you could try using the “refresh” option from Habmin. Pick the device, and below the general, This tend to update the values when there are problems.
I had issues getting a couple of these sensors added completely. The first one added with no problems, so at least I knew what to expect when it was done. Another did not, but I found that re-entering include mode multiple times in succession near the controller resulted in it finishing discovery relatively quickly. To watch it happen I ran ‘tail’ against the event.log and watched for logs for the device status change while hitting the button to enter inclusion mode. For me, simply waking up the device multiple times didn’t seem to work, but re-entering inclusion mode on the device was the trick.
I really want to order and test one of these motion sensors. I think they are really balanced between cost and functionalities (including temperature, luminance, etc.). Who is using them could you please tell me if you are using the Z-Wave Motion Sensor(PIR) or the Z-Wave Motion Sensor(PIR)2? Any more difficulties encountered besides the ones stated above? Where did you buy them from?
Thank you very much in advanced for your feedback.
I’m not sure which is which, but I have both models of neo coolcam pir sensors connected with Z-wave. Both works good except temperature. I’ve never seen this value properly received.
Apologies to bump and old thread, but I’ve been attempting to add one of these for an hour or two.
I think mine may be a slightly newer model, though it looks the same as here: Z wave DB
The manufacturer is the same 0258, DevType and ID 0003:608d which I don’t see in the DB. Is it a matter of adding it? or am I misinterpreting what is in there?
Are you aware of any other changes between your device and what is in the database (e.g., configuration options, association groups, etc.)? The XML does not always show that there is a difference. If there is nothing different, then the type:id just needs to be added to this device type. If there is a difference, then a new entry needs to be created.