Interesting! I really can’t find it in my manual. The only mentions of temperature I can see are operating and storage temperature.
It’s listed as firmware version 3.97 for comparison. It would be nice to get that working if it is available 
My firmware is also 3.97.
Temperature was the only reason why I chose the more expensive PIR2 over the PIR1. sigh
Does your manual mention PIR2? For ref, mine doesn’t - I’m wondering if you’ve been sent the wrong device. i.e. a PIR1 device with a PIR2 manual? You may be able to return it if you bought the PIR2?
Looking at my manual again and i find that you are absolutely right. It was the promotional wording on Aliexpress seller that stated that it was a PIR 2. The manual is generic. But my does physically look at the “golf ball” PIR 2, with the simple magnetic attachment.
Just to muddy the waters even further, mine’s the one with the “claw” holder.
Other external difference appears to be there’s no “dimples” around the sensor, like this one from the device page:
1 Like
The one with the magnagtic attachment is now discovered as PD03Z in openhab
These Neo Cam PIR´s are a mess. I have seen three different versions, and none of them seems to have a manual which relate to the actual device…
Look at this manual:
This version does not have temperature sensor (according to the manual), but it has a light/lux sensor.
I have seen the very same PIR (golf ball alike) and that one had a temperature sensor.
My Neo Coolcam sensor (the round one not looking golf ball alike) is detected with a temperature sensor from openhab. But it doesnt have one. It has a light/lux sensor. But it´s manual claim it does have a temperature sensor, and not the light/lux sensor…
No wonder if these PIR´s are beeing mixed up in the z-wave database. Sheshen (company of Neo Coolcam) hasn´t done a great job descriping their real features.
Hi,
one last thing regarding the v2.32 Wall Plug…
Measuring the kilowatt hours still behaves a little strange for me. The values always jump between a normal, plausible value and a large negative value. However, I think this is a bug in the firmware.
2019-03-05 02:38:14.916 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from 2.87 to 2.89
2019-03-05 04:18:15.250 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from 2.89 to 2.91
2019-03-05 05:53:14.585 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from 2.91 to 2.93
2019-03-05 07:28:15.007 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from 2.93 to -21474833.53
2019-03-05 09:03:14.348 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.53 to -21474833.51
2019-03-05 10:33:14.745 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.51 to -21474833.49
2019-03-05 12:08:14.078 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.49 to -21474833.47
2019-03-05 13:43:14.382 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.47 to -21474833.45
2019-03-05 15:18:14.680 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.45 to -21474833.43
2019-03-05 16:53:13.968 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.43 to -21474833.41
2019-03-05 17:38:38.611 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.41 to -21474833.4
2019-03-05 17:45:20.563 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.4 to -21474833.39
2019-03-05 17:51:28.527 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.39 to -21474833.38
2019-03-05 17:58:50.457 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.38 to -21474833.37
2019-03-05 18:03:46.435 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.37 to -21474833.36
2019-03-05 18:11:44.359 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.36 to 3.14
2019-03-05 18:15:16.507 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from 3.14 to 3.15
2019-03-05 18:18:12.321 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from 3.15 to 3.16
2019-03-05 18:19:16.305 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from 3.16 to 3.17
2019-03-05 18:25:36.264 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from 3.17 to -21474833.28
2019-03-05 18:27:28.246 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.28 to -21474833.27
2019-03-05 18:30:36.229 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.27 to -21474833.26
2019-03-05 18:32:06.226 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.26 to -21474833.25
2019-03-05 18:34:32.194 [vent.ItemStateChangedEvent] - Socket_Bedroom_Desk_Kwh changed from -21474833.25 to -21474833.24
Best,
Olli
Hi @dmit2k,
Did you solve the problems? Maybe the last Snapshot or at least 2.5 M1 help?
How did you mount it to the wall? Only with screws?
Do you have some pictures how to mount it?
Thanks in advance and Happy Easter!
HFM
I bought the door sensor and the golf-ball-like PIR. The PIR was included easily and started reporting temperature and motion right away. The light didn’t start because there is a threshold of 100 lumen. I waved with a flesh light and then it started.
The door sensor is giving me a headache though. First time it didn’t include but I was on Habian 2.5 snapshot. I went back to 2.4 stable and reseted the sensor (press the button for 10 seconds). After that I could include, but the device was never updated . I clicked the button to wake it up 50 times, I waited for a week, no success. Yesterday I excluded the device, and again included it. The device was included and started initialising right away! I see the vendor and item nr etc in Habmin.
But there is no info about opening the door. There is a led that flashes when I remove the magnate or when I put it back, but no info to the controler.
I have set the association group 1 to ‘controler’ and for what it’s worth the ‘Basic set level’ to ‘0’.
When I press the button to wake the sensor up, I see the message in the log (Debug level):
2019-05-31 18:40:02.574 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:512:node39' to inbox.
2019-05-31 18:40:02.575 [home.event.InboxAddedEvent] - Discovery Result with UID 'zwave:device:512:node39' has been added.
2019-05-31 18:40:13.231 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zwave:device:512:node39' has been removed.
2019-05-31 18:40:13.235 [hingStatusInfoChangedEvent] - 'zwave:device:512:node39' changed from UNINITIALIZED to INITIALIZING
2019-05-31 18:40:13.239 [hingStatusInfoChangedEvent] - 'zwave:device:512:node39' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2019-05-31 18:40:13.249 [hingStatusInfoChangedEvent] - 'zwave:device:512:node39' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to UNINITIALIZED
2019-05-31 18:40:13.268 [hingStatusInfoChangedEvent] - 'zwave:device:512:node39' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2019-05-31 18:40:13.312 **[hingStatusInfoChangedEvent] - 'zwave:device:512:node39' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING**
2019-05-31 18:40:13.322 [hingStatusInfoChangedEvent] - 'zwave:device:512:node39' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2019-05-31 18:40:13.323 [hingStatusInfoChangedEvent] - 'zwave:device:512:node39' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2019-05-31 18:40:13.349 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:40:13.368 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:40:13.398 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:40:13.417 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:40:13.420 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:40:27.616 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:40:44.223 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:41:39.424 [.ItemChannelLinkAddedEvent] - Link 'Achterdeur_sw-zwave:device:512:node39:sensor_door' has been added.
2019-05-31 18:41:39.427 [.ItemChannelLinkAddedEvent] - Link 'Batterij_achterdeur-zwave:device:512:node39:battery-level' has been added.
2019-05-31 18:48:20.208 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:48:28.894 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:49:23.064 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:52:30.490 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:52:41.830 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:54:05.068 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
What can I do to let it finish initialiding?
I have a 2.32 firmware version (100:1027) that does not show some config parameters. My manual does not agree with the device.
Should we split out the 100 type?
Most all Configuration Parameters do not match my manual. When I get home, I can see if Parameter 3 actually disables the LED. If not, we may need to split out my device.
I am not currently using these in Production so I have flexibility to test, assuming I do not brick it.
In a quick test, Parameter 3 disabled the LED as expected from the current device listing. The included manual says Parameter 3 is to configure maximum overload current, ovviously incorrect…
We changed this device already so many times. I have about 40 emails in my account regarding this device.
It looks like even the same firmware version has different functions. Also the manuals which come with the device do not match the device.
Sorry. I won’t touch this crappy device again and won’t make any approvals 
Please ask Chris.
Hi @sihui!
Before I buy any of these NEO coolcam devices (NEO Coolcam Z-wave EU Wireless Smart Control Light Switch 2CH): Is there any problem, that you won’t touch it, too?
Best regards
HFM
It is like all the work done here in the forum: it is volunteer work in our limited spare time.
If knowledge and time is available, people will help, if one of it lacks, there has to be some other solution (for example through the binding maintainer, who is doing this in his free time, too).
By the way, I have two of these devices (firmware 3.94), which are working fine.
But I would never buy them again. Range is much less than all the other devices (mostly Fibaro) I own.
You get what you pay for.
Hi @sihui,
I think because of my bad English there is a misunderstanding. I like openHAB and I know that there are many hours of developing, testing, documenting, supporting. It is a kind of doing something on a voluntary basis. And this ist fantastic! I do it myself within a citizens’ initiative against a landfill site.
What I meant is: Are there any known bugs with the NEO Coolcam Z-wave EU Wireless Smart Control Light Switch 2CH? I would not buy it if it is not usable. For the power plug I understood that it is not so good.
Thanks for your replies! 
HFM
I don’t have this device so I can’t tell.
1 Like
@sihui I meant to confirm the current manual is incorrect and the database appears correct.
Sorry for my poor communication.
I really appreciate all the hard work here. Sorry to frustrate you.
Apologizing is on my side, sorry.
German natives reading and writing in English language is sometimes not a good idea 
1 Like