Neo coolcam z-wave devices

Its actually a window/door contact sensor.

Anything in association groups that i need to set ? I just put all 4 groups to the Z wave Controller?

That could give you lots of trouble: if you need to control other devices outside from openHAB, use Group 2-4. If you want to control everything through openHAB, use only Group 1 (set to the controller)

Same game: I have one of those. You can speed up sending the battery level if you use a shorter time for the wakeup configuration: default is 43200 seconds. But then battery life will be way shorter …

Please bear with my noobieness.

If I only have 1 contact sensor and its node 4. Is my Z Wave Stick Node 1?
Everytime I do a inclusion scan , it shows up node 2 and 3, but I ignore it as they look like my Z wave serial controller but could it be something else? Does it matter for this matter?
When you say use Group 2-4, what exactly do you mean?

Could you give an example of your properties and settings for one of your Coolcam contact sensors?

In a standard setup with one controller: yes.

This can happen if you tried to include the same sensor several times. Every new inclusion counts the node number up by one digit.

It is possible to control other zwave devices directly, without openHAB between them.
If you have a zwave siren and want to sound that siren even if openHAB is down or shut off, you put the siren into the appropriate association group of your door sensor. On the other side that can have unpredictable effects if you don’t know exactly what your are doing.
So if you want a clean setup of openHAB and your zwave network, just set the Lifeline group (sometimes that group is called differently) to your controller. Leave all other association groups empty.

Sure:

Contact Neo_DW_1_C <siren> (gRestore) { channel="zwave:device:uzb:node46:sensor_door" }
Number Neo_DW_1_Bat <battery> (gBattery) { channel="zwave:device:uzb:node46:battery-level" }

Thank you so much!

Are the last 2 sentences the items to be put in the items file??
Can you also share your association groups?

update:
I just got these errors after making the changes to the configuration parameters (from 255 to -1), and leaving association groups 2-4 blank

2018-11-21 19:10:59.228 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.

2018-11-21 19:11:00.054 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.

2018-11-21 19:11:00.885 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.

2018-11-21 19:11:01.716 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.

It’s the same, just set it to 255:

Yes. If you have Simple Mode turned off you need to link the channels of your things to items manually.
Don’t forget to put a label format either in your items definition or in your sitemap definition:

Should be [%s] for a contact itemtype.

It won’t help you because it is empty: with the 2.4 version the binding sets the association automatically.

Edit: I’ve edited the post above because there were some strange characters in the item definition (from copy and paste)

Thanks again.
Are you on OH 2.4 snapshot or M5?
I am still on OH 2.3 stable. Is that why I am having more trouble than u did setting the z wave stuff up?

On snapshot #1433 which is basically Milestone M6.

Not necessarily, it depends: Zwave had a major restructuring between 2.3 and 2.4.
But more important is the zwave database: 2.3 is almost 6 month old, so your version won’t have any new devices or any devices changed in the database.
For the battery level: just be patient for one day and don’t restart openHAB, that channel always has worked and so it will on your system.

I also have the 2 gang EU switch

Direction Device > report to OH is not working and only one of the switches works from OH to Switch

You solved it by using the inclusionn by the stick and not Habmin?

Yep :slight_smile:

This will not make any difference - all the binding does is to put the stick into inclusion mode - the same as using the button.

If the device is not reporting, it is not related to inclusion - this is related to association configuration which is performed by the binding during initialisation. Again, this is not related to how it was included in any way at all.

thats what I would have expected.

As I only connected Live and Neutral and NO actual load to the outputs (I only want to use the 2 buttons to actually get on off by a rule and control not directly to the switch connected stuff) is it possible that the device is then differently discovered ?

It’s possible, but I think extremely unlikely.

Hello,

having problems setting up the Association groups for Neo Coolcam Light switch EU2 (OpenHab 2.4):

When adding target devices either to Association Group 2 (left gauge) or Group 3 (right gauge) of the switch, it does not send commands to target devices for ON / OFF events.

Tried to link one switch buttons with another same unit, but with no success.

At the same time it does properly respond when being added to Association Groups of other brand devices (tried with Fibaro motion sensor).

Any ideas?

Hi all,
Since i upgraded my system to 2.4.0 i am having problems with my Neo Coolcam Door/Window (4) and PIR (1) sensors. I followed the procedure described by @Chris in this thread ZWave binding updates , so i deleted all Things and let the binding discover them again. Then i added my item definitions from the items file to the Thing items.
At first the Window/Door sensors where working OK in v 2.4.0, however the PIR sensor never worked not even in 2.3.0.

I found some examples in threads and use the the following items:

//   Shinzen Electronics Neo Coolcam Door/Window Sensors    *****
//
Contact DeurSensor_1_Contact            "Voordeur is: [%s]"                                 <door>  (gAlarm,gSensors)           {channel="zwave:device:651ad746:node4:sensor_door"}
Switch  DeurSensor_1_Alarm_Access       "Voordeur Alarm (access)"                           <door>  (gAlarm,gSensors)           {channel="zwave:device:651ad746:node4:alarm_access"}
//Number  DeurSensor_1_Battery_Level      "Voordeur Battery Level [MAP(neobattery.map):%s]" <door>  (gAlarm,gSensors,gBattery)  {channel="zwave:device:651ad746:node4:battery-level"}
Number  DeurSensor_1_Battery_Level      "Voordeur Battery Level [%d %%]"                    <door>  (gAlarm,gSensors,gBattery)  {channel="zwave:device:651ad746:node4:battery-level"}
//
Contact DeurSensor_2_Contact            "Garagedeur is: [%s]"                               <door>  (gAlarm,gSensors)           {channel="zwave:device:651ad746:node6:sensor_door"}
Switch  DeurSensor_2_Alarm_Access       "Garagedeur Alarm (access)"                         <door>  (gAlarm,gSensors)           {channel="zwave:device:651ad746:node6:alarm_access"}
Number  DeurSensor_2_Battery_Level      "Garadedeur Battery Level [%d %%]"                  <door>  (gAlarm,gSensors,gBattery)  {channel="zwave:device:651ad746:node6:battery-level"}
//
Contact DeurSensor_3_Contact            "Serredeur is: [%s]"                                <door>  (gAlarm,gSensors)           {channel="zwave:device:651ad746:node7:sensor_door"}
Switch  DeurSensor_3_Alarm_Access       "Serredeur Alarm (access)"                          <door>  (gAlarm,gSensors)           {channel="zwave:device:651ad746:node7:alarm_access"}
Number  DeurSensor_3_Battery_Level      "Serredeur Battery Level [%d %%]"                   <door>  (gAlarm,gSensors,gBattery)  {channel="zwave:device:651ad746:node7:battery-level"}
//
Contact DeurSensor_4_Contact            "Schuifpui is: [%s]"                                <door>  (gAlarm,gSensors)           {channel="zwave:device:651ad746:node8:sensor_door"}
Switch  DeurSensor_4_Alarm_Access       "Schuifpui Alarm (access)"                          <door>  (gAlarm,gSensors)           {channel="zwave:device:651ad746:node8:alarm_access"}
Number  DeurSensor_4_Battery_Level      "Schuifpui Battery Level [%d %%]"                   <door>  (gAlarm,gSensors,gBattery)  {channel="zwave:device:651ad746:node8:battery-level"}
//
//    Shinzen Electronics Neo Coolcam PIR sensors     *****
// Vb. https://community.openhab.org/t/zwave-coolcam-motion-sensor-not-working/48827/24
//
Switch	NeoPIR_1_Sensor                 "Neo PIR sensor 1 - Sensor"                 <pir>   (gAlarm,gSensors,gBattery)          { channel="zwave:device:651ad746:node5:sensor_binary" }
Number  NeoPIR_1_Luninance              "Neo PIR sensor 1 - Luminance [%s]"         <pir>   (gAlarm,gSensors,gBattery)          { channel="zwave:device:651ad746:node5:sensor_luminance" }
Number  NeoPIR_1_Temperature            "Neo PIR sensor 1 - Temperature [%.1f °C]"  <pir>   (gAlarm,gSensors,gBattery)         { channel="zwave:device:651ad746:node5:sensor_temperature" }
Number  NeoPIR_1_Bat_Level              "Neo PIR sensor 1 - Battery_Level [%d %%]"  <pir>   (gAlarm,gSensors,gBattery)          { channel="zwave:device:651ad746:node5:battery-level" }
Switch  NeoPIR_1_Burglar                "Neo PIR sensor 1 - Burglar_Alarm"          <pir>   (gAlarm,gSensors,gBattery)          { channel="zwave:device:651ad746:node5:alarm_burglar" }
//

Att: I also tried it with the Contact item type replaced with the Switch item type, with no success.

This ia my sitemap snippet:

Group item=gTest 					  label="Test pagina sensors" 	icon="sensor" {
                Switch  item=DeurSensor_1_Contact           label="Voordeur Contact (1)"    icon="frontdoor"
                Switch  item=DeurSensor_1_Alarm_Access      label="Voordeur Alarm"          icon="frontdoor"    mappings=[ON="OPEN/CLOSE"]    
                Text    item=DeurSensor_1_Battery_Level     label="Schuifpui Sensor battery level [%s %%]"   icon="batterylevel"
                Default item=DeurSensor_1_Battery_Level     label="Sensor battery level [%s %%]"    icon="batterylevel" 
                //
                Switch  item=DeurSensor_2_Contact          label="Garagedeur Contact (2)"           icon="frontdoor"
                Switch  item=DeurSensor_2_Alarm_Access     label="Garagedeur Alarm: "               icon="frontdoor"  mappings=[ON="OPEN/CLOSE"]
                Text    item=DeurSensor_2_Battery_Level    label="Garagedeur Sensor battery level [%s %%]"  icon="batterylevel"
                Text    item=placeholder
                //
                Switch  item=DeurSensor_3_Contact           label="Serredeur Contact (3)"    icon="frontdoor"
                Switch  item=DeurSensor_3_Alarm_Access      label="Serredeur Alarm"          icon="frontdoor"    mappings=[ON="OPEN/CLOSE"]    
                Text    item=DeurSensor_3_Battery_Level     label="Serredeur Sensor battery level [%s %%]"   icon="batterylevel"
                Default item=DeurSensor_3_Battery_Level     label="Serredeur battery level"    icon="batterylevel"
                //
                Default item=DeurSensor_4_Contact           label="Schuifpui Contact (4)"           icon="frontdoor"
                Switch  item=DeurSensor_4_Alarm_Access      label="Schuifpui Alarm"                 icon="frontdoor"    mappings=[ON="OPEN/CLOSE"]    
                Text    item=DeurSensor_4_Battery_Level     label="Schuifpui Sensor battery level [%s %%]"  icon="batterylevel"
                Default item=DeurSensor_4_Battery_Level     label="Sensor battery level (Default)"  icon="batterylevel"
                //
                Switch  item=NeoPIR_1_sensor            label="PIR1 Beweging detectie"          icon="movecontrol"  mappings=[ON="OPEN/CLOSE"]
                Switch  item=NeoPIR_1_burglar           label="PIR1 Inbraak detectie"           icon="motion"       mappings=[ON="OPEN/CLOSE"]
                Text    item=NeoPIR_1_temperature       label="PIR1 Temperatuur [%s]"           icon="temperature"  
                                                        valuecolor=[Last_Update=="Uninitialized"="gray", >=25="orange", >=15="green", 0="white", <15="blue"]
                Text    item=NeoPIR_1_level             label="PIR1 Level [%s]"                 icon="battery"
                Text    item=NeoPIR_1_luninance         label="PIR1 Luminance"                 icon="licht"
                     
        }


Beacause i was doubting the ZWave configuration, i did put the ZWave binding in DEBUG and created a separate ZWave.log file and restarted openhab. This log file is here: ZWave.log
I am not knowledge enough with this, but when i scan through the log-file i think it looks OK… But i might mis a lot.
When i look at PaperUI, at the Things i see this: Status: ONLINE Node initialising: REQUEST_NIF

I use two other Z-Wave devices, Fibaro Wall Plug and Danfoss LC-13, and they seem to work OK in v 2.4.0.
At the moment i do not know what i can do…
Hopefully someone can help me with tihis?
Kind regards, Bert

You made a very detailed post :+1:, but left out the configuration parameters and associations used.

Can you please post the database references for these devices - just so we know exactly what they are.

I would also recommend using the latest snapshot as there was quite a bit of work to update some of these devices in the past couple of days.

Hi Scott, Thanks for you quick response. But i’m afraid i amstill a noob on this subject.
can you tell me where i can find these items? I scanned the tread from Chris and other threads, but could find these…

@Chris, I think these are the devices: Shenzhen Neo Electronics Co., Ltd - Door/Window Sensor
and the Shenzhen Neo Electronics Co., Ltd - PIR Motion Sensor
I have seen threads where other people using these devices too… I put links to the .xml-files of both devices here: Link to node4.xml and node5.xml Maybe that gives you some indication?

Later today i will copy the latest binding to the system.
And thank you very much for responding and for the enormous amount of work you have put in the ZWave binding.
Regards, Bert

Ok, just to confirm, can you look in PaperUI in the properties for the device, and you should see something like dbReference - can you quote those numbers.

Looking at the door sensor, I will make a change to the database to change the channels type as the alarm type is wrong and won’t work properly I’ve not looked at the PIR yet, but will check once you confirm these references.