We should be able to add them into a channel, and hence an item so they can be processed in a rule. I’ve not actually done this myself as I don’t get much time to actually work on my own system 
.
Yes - clearly it should work…
Maybe the following entry in your log is related -:
When adding the controller, I can’t get to the configuration section (it doesn’t load after clicking save) and instead have to go to the things page after hitting save. I then edit it and set the port (see line #10). After that the rest of the output is sent to the log but it shows the controller as being offline. The attributes for the controller never seem to get filled in and are all blank or have a question mark.
I don’t really see anything especially wrong - the communications with the stick is working fine and the responses all look ok as far as I can see from a quick look. The controller is talking to the binding fine. The only strange thing I can see in the log is the message -:
ZWave product zwave:serial_zstick has no references!
I’ll have another look tonight, but there’s nothing obviously wrong.
@mdcollins05: Just to cross-check: Have you already tried to add the stick when you are running the regular zwave binding? Does it work there or does the same error occur?
1 Like
I am using the Aeotec Gen5 stick here with this binding just fine. Did you delete all existing Zwave devices including your controller from Habmin first?
My steps were to remove all Zwave Devices first. Then uninstalled the existing Zwave binding. Then stopped OH2, added the JAR to addons folder and restarted.
Then re-added the controller, set the USB port and then re-scanned for all Zwave devices.
So far so good, and all is working.
1 Like
Chris. Let me know when you may want to try something with this. From what I have learned, and also now looking within OZCP, there is an ‘Alarm Type’. And if that can be added as a channel like you mention, then you check with a rule when that changes to also update your Lock Status in a SiteMap etc.
Let me know if you need any XML info. I do have a Kwikset 916 that like others has always shown as a 914TRL model.
Image from OZCP for the lock.
I need some help with my 916 to get alarms to be read from manual and code lock/unlocks
Yes - as I said we can hook this up to a channel - it’s just something I’ve not yet done as I’ve not had the chance. I’ll take a look at it in the coming days. I don’t need anything as my lock also does this - I tested it a few months back but haven’t had the time to finish it (there’s always something else someone wants 
).
OZCP? I don’t see this on my openhab
It’s a different software - not OH.
Open-Zwave-Contol-Panel. Like Chris mentioned, it is a separate software that one can use to pair devices to your controller. It is not a home automation type software like OpenHab. It just has its usefulness in some ways to access your Zwave controller.
I cannot access the jar url at the moment:
The following error was encountered while trying to retrieve the URL: http://www.cd-jackson.com/downloads/openhab2/org.openhab.binding.zwave-2.1.0-SNAPSHOT.jar
Nieudane połączenie z 86.186.169.244.
System zwrócił wartość: (111) Connection refused
Ping also unsuccessful.
Is it online?
I am using jar downloaded earlier during the day. I deleted all z-wave things while using previous version of binding (kar provided 2.0.0), deleted zwave from the list of active bindings in addons.cfg and uploaded jar into addons directory.
When adding things, most of the are added as unknown device (which was not the case previously). Upon Add command this is what appears in the log:
2017-02-02 19:49:56.991 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 15: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:56.991 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 17: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:56.992 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 19: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:56.993 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 20: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:56.993 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 21: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:56.994 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 22: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:56.994 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 23: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:56.995 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 24: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:56.995 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 25: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:56.996 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 28: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:56.997 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 29: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:56.998 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 30: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:56.999 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 31: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:57.000 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 32: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:57.001 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 37: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:57.002 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 38: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:57.003 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 39: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:57.003 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 40: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:57.004 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 41: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:57.004 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 42: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:57.005 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 44: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:57.005 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 45: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-02-02 19:49:57.006 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 52: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
Any hints?
Did you delete your existing zwave controller and turn off the existing Zwave 2.0 addon before installing and start the experimental one here?
I think so. While running KAR provided version I deleted all zwave related things in PaperUI, including controller, deleted zwave from the list of bindings in addons.cfg and restarted OH2. Then I uploaded experimental zwave jar.
Or it should be done some other way?
That may or may not be correct depending on your setup. Most of us have bindings installed and uninstalled either through the PaperUI or via Habmin (Extensions).
Make sure the existing 2.0 Zwave binding is not still installed.
Looks like the download link is down at the moment - I’m getting 503: Service Unavailable.
I uninstalled zwave binding and the zwave controller itself from things shutdown, moved the JAR, started service back up, and then installed the zwave controller back, set port then reinstalled the binding itself.
James. What do you mean when you say you re-installed the binding itself?
After you uninstall the existing binding from PaperUI or Habmin. Stop OH2 and then add the JAR file to your addons folder. That is all. You do not actually than re-install the binding, and that is likely causing a conflict.
And just in case the binding in the addon’s folder doesn’t start, look towards the top of the topic on how to log into Karaf and manually start it.