Sorry - I just had a quick look at the log - it must be a debug log for it to be of any use at all. Please run the system in debug mode, wake up the device a few times with the device close to the controller (a few meters or so) and then provide the debug log…
I don’t see any issues in the log, however you are running an old version of the binding - as already pointed out by @anordvall, you should upgrade to a recent version. Other than this, it looks like it should be working fine - the device hasn’t completed initialisation, but it’s on the last stage, so I think everything would be green if you’d woken it up one more time…
It is - but there is no version information on this filename and 1.8-SNAPSHOT has been the ‘latest’ for 6 months or more so you need to make sure you are using a recent version and you can’t tell this from the filename, or the date on the file. The version information is contained within the file, and this is what is printed when the binding starts, and this tells me the binding is from August (as per the information in my previous post).
Make sure you have the latest version of the zwave binding file (org.openhab.binding.zwave-1.8.0-SNAPSHOT.jar). Download the latest build from https://openhab.ci.cloudbees.com/job/openHAB
Also make sure you have Habmin installed and functional
Remove the Z-stick from and press the action button to enable inclusion mode.
Remove both magnets from the Strips. This should include the Strips unit in the zwave network (which should be indicated by the controller).
Note: if this fails, just perform a factory reset of the Strips Unit (info here: http://products.z-wavealliance.org/products/1510)
Put the controller back into the host computer, The NUC in my case.
Reload Habmin and click the Configuration tab and the select the Bindings list. Select the Z-Wave bundle which loads in the right panel. Click the Devices tab which should display a list of all included units in the Z-Wave network. The new Strips Unit is most probably not initialized and ready yet, so there is no possibility to expand its Configuration Parameters.
Keep the Strips Unit close to the Z-Stick and wake the device a couple of times (info here: http://products.z-wavealliance.org/products/1510). If you want to understand what´s going on, run OpenHab in debug mode, by running start_debug.bat and monitor the console output.
Add this to your .items file: Contact Door_My_Door "My Door" (gMyGroup) { zwave="1337:command=sensor_binary" } Contact is the binding type Door_My_Door is the item variable name "My Door" is the item text (gMyGroup) is to which group it is added { zwave=“1337:command=sensor_binary” } is the Z-Wave binding info where 1337 is the Z-Wave node ID and command=sensor_binary tells OpenHab how to interpret the Strips messages. The sensor_binary is the detail that makes the Strips unit to handle OPEN and CLOSED.
This should make the Strips unit report OPEN and CLOSED which is what we want.
Finally, I got my sensative strip. I could follow your how-to-manual (thank you!!!) until step 8 but I don’t see any parameter #1
that I can set to "0".
Can you pls describe where I can find these parameter?
The strange thing going on here, is that you may have to repeat the init process until it gets recognized, which can take a couple of attempts. Another important thing is that you have to have a recent version of OpenHab, so that the device is available in “device dictionary”, which is compiled into the assembly.
Yes, that is the secret whereas “a couple” is a really undefined number of tries. In my case it was something around 10 attempts beside the fact that my log said “too many retries”.
Another issue was that the binding didn’t work properly. When I upgraded to the latest snapshot everything was working fine.
where do I find the latest snapshot of the zwave binding?
I have tried with the one comes in the 1.8.2 addons package and it didnt worked at all , got a-lot of java exceptions when tried to list the zwave devices in HABmin .
when I test with the Snapshot version that comes with HABmin i can list the zwave devices but i dont have the option to configure the device to use binary notification.