Neo coolcam z-wave devices

zwave
Tags: #<Tag:0x00007fe05d87fd30>

(Chris Jackson) #247

It’s possible, but I think extremely unlikely.


(Dmit) #248

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?


(Bert) #249

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


(Scott Rushworth) #250

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


(Chris Jackson) #251

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.


(Bert) #252

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…


(Bert) #253

@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


(Chris Jackson) #254

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.


(Bert) #255

I am sorry but i can’t find a dbRefference in PaperUI or something that looks like that in the propperties.
I beleve this screen is the propperties of the device…


But if that’s not the case, can you please tell me where to look for this?
Or maybe there is a way via the Karaf console?


(Chris Jackson) #256

No - this isn’t the properties - this is the configuration. In the previous page (ie the main thing page which also shows the channels) there should be a properties list.


(Bert) #257

I’m sorry, but i can’t see a propperties button or menu item… This is my Items main screen:


I am searching the docs to find this dbRefference.


(Chris Jackson) #258

This is the things list - I meant the main page of a specific thing…

Don’t worry - I think I can work it out from other information.

This is not documented in the user documentation as it’s a low level bit of information, but you should find it in the properties list of the device along with all the other device properties.


(Bert) #259

I am looking at the node5.xml en find these parameters:

 <manufacturer>0x258</manufacturer>
  <deviceId>0x1083</deviceId>
  <deviceType>0x3</deviceType>

When i look in your online database then these correspond with this device: Shenzhen Neo Electronics Co., Ltd - 0003:1083


Would that be the info you needed? If so, i will find the Door/Window Sensor also.
EDIT:
For the Door/Window Sensor i found thisin de .xml file:

<manufacturer>0x258</manufacturer>
  <deviceId>0x1082</deviceId>
  <deviceType>0x3</deviceType>

And in your on-line database it corresponds with this one Door/Window sensor - 0003:1082

EDIT 2: Searching further i found this info in the openHAB Docs for the Zwave Binding for my devices:
Door/Window Sensor and Motion Sensor
They have a thing type UID of shenzhen_doorwindowsensor_00_000 and shenzhen_motionsensor_00_000. But i am not 100% sure about the last one.

Further testing, i created second items by one of the Door/Window Sensors and chose “Create new item…” and let the system decide the name.
By the Things definition, in the Channel for the Door/Window Contact the item is a Contact type. Unclear to me is whether i have to use Contact or Switch in the sitmap file. I’ve read some contradictory things about the Contact type… But i tried both, without success.

EDIT 3:

so i deleted the zwave binding and installed this one: org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar, which i downloaded 25/12 from: jfrog snapshot 2.5.0. Unfortunately, that did not change anything…
After that i made a log from the start of openHAB which is file: ZWave-3.log If i put this in the online Lof Viewer, i see for Node 6 (one of the Door/Window Sensors) much more traffic than for the other tree sensors…

And because two of the sensors have worked with v 2.4.0, i doubt my items/sitemap config. But i can’t see what’s wrong (see earlier post).
I did notice however one perculiarity in the definitions in PaperUI of the items at both Door/Window Sensor and PIR Sensor Things: they are named resp, zwave:device:651ad746:node7:sensor_door, zwave:device:651ad746:node7:alarm_access etc. and battere level items zwave:device:651ad746:node7:battery-level. Notice the difference in use of underscore and dash.

Hope this gives some more info and does not make it more fuzzy…


(Bert) #260

Ai, i see problems with the ZWave 2.5.0 binding which i installed. It seems that openhab reverts back to the included 2.4.0 binding (also a restart of the RPi dit not change this):

2018-12-26 10:34:06.648 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/share/openhab2/addons/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [274]
  Another singleton bundle selected: osgi.identity; type="osgi.bundle"; version:Version="2.4.0"; osgi.identity="org.openhab.binding.zwave"; singleton:="true"

        at org.eclipse.osgi.container.Module.start(Module.java:444) ~[?:?]
        at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) ~[?:?]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [10:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [10:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [10:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [10:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [10:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [10:org.apache.felix.fileinstall:3.6.4]
2018-12-26 10:34:16.814 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/share/openhab2/addons/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [274]
  Another singleton bundle selected: osgi.identity; type="osgi.bundle"; version:Version="2.4.0"; osgi.identity="org.openhab.binding.zwave"; singleton:="true"

        at org.eclipse.osgi.container.Module.start(Module.java:444) ~[?:?]
        at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) ~[?:?]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [10:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [10:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [10:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [10:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [10:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [10:org.apache.felix.fileinstall:3.6.4]
2018-12-26 10:34:47.891 [INFO ] [lipse.smarthome.model.script.weather] - Calculating time of day...
2018-12-26 10:34:48.708 [INFO ] [lipse.smarthome.model.script.weather] - Calculated time of day is DAY


(Chris Jackson) #261

I’m not sure that this is a problem with the binding is it? It looks like a problem with your system somehow. Probably you have multiple bindings installed (ie both 2.4 and 2.5)…


(Bert) #262

Think i found that: the ownership of the 2.5.0 bindig was openhabian:openhabian in stead of openhab:openhab.
Looking again to the zwave log…

Edit: There was an other problem. When i Uninstalled the Zwave binding in PaperUI, then as soon as i restarted openHAB it shows as Installed again, even with a reboot of the RPi. Found the files for the zwave 2.4.0 binding and moved them to a temp location; but that didn’t help as well. After a restart of openHAB the files where at the same location again.
So i upgraded the system to 2.5.0-SNAPSHOT. But as far as the Door/Window- and PIR Sensors concerns, nothing has changed… OK, i’l skip for tomorrow

Edit 2: I made a zwave debug log from the startup with 2.5.0 ZWave-250-1.log


(Scott Rushworth) #263

Did you by chance add the zwave binding to addons.cfg? This could have been why it reinstalled. Upgrading to OH 2.5 snapshot would have worked around this too. You’re past it, but this may help in the future.


(Bert) #264

@5iver, Hi Scott, you are absolutely right! I had forgotten about that; somewhere in version 2.3 i wanted to switch to as much as posible using the config files in stead of PaperUI. But i had forgotten about the addons.cfg… :frowning: Now this happened, i won’t forget about it. Don’t know if i should revert back to 2.4 with the snapshot binding… But I’l wait what Chris will think about that.
Would there be a way to specify a snapshot binding in the addons.cfg file?


(Chris Jackson) #265

Sorry - I’m not really sure what you want me to comment on at the moment? Are you now using the latest binding, and if so, have you deleted the thing and re-added it so that it picks up the new definitions? This is one of the devices we updated over the past few days and it was tested by others, so should be working now.


(Nakh Home) #266

Hi,

My Neo Door Sensor is in online but the Openhab items are not updated.

it worked in the past, on 2.3

i can open and close the door. The items are not updated.
My Neo Door Sensor is in online but the Openhab items are not updated.

My configuration:

  • RASPBERRY PI 3 MODEL B+

  • openHAB 2.4.0 Release Build

  • Controller: Aeon Labs Z-Stick - USB Adapter with Battery GEN 5

  • NEO Coolcam NAS-DS01Z Smart Home Z-Wave Plus Door Window Sensor Compatible with Z-wave 300 series and 500 series Home Automation

What i have done till now:
I have deleted the thing.
i have excluded
i have reincluded but it do not help

image

My items are well linked

The thing configuration:

The items properties:


https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/400

Any Ideas?