The latest version of the development binding dated 8th Sep 2018 is here . Toward the end of last year I spent some time doing some initial refactoring of the ZWave binding in OH2. This focussed on rewriting the way transactions work as this is an enabler for other areas of the code. At the same ti…

Finally, after a lot of trials, reboots, resets, reinclude, re-awake… it works ! I do not really understand what finally made the things up. Thank you for your help. Regards, Romain

I am using the UI to configure my things. Could never get the text files to work.

Hi @chris Sorry for the all the messages. I installed a fresh copy of OH 2.3 snapshot, enabled only your latest zwave binding and tested the inclusion. This is the result: http://www.faure.ca/~paul/openhab.mar1.log Inclusion doesn’t error out right away, but I still can’t add my lock.

When I downgraded to a fresh 2.2.0 stable with no other binding or configuration other than zwave, i got the immediate error upon starting zwave inclusion.

[image] paulfaure: This is the result: http://www.faure.ca/~paul/openhab.mar1.log Inclusion doesn’t error out right away, but I still can’t add my lock. Yes, unfortunately the stick is returning an error immediately when put into inclusion. [image] While the logs don’t show any other acti…

[image] 5iver: I have a rule for this and will create a post to share it. Saves a lot of time if you have more than a couple devices. But still a huge PITA to have to change 30+ temperature scales from Celsius to Fahrenheit. I know it can be done in the rule, but haven’t quite figured it out yet…

I waited overnight and still have the error our immediately on OH 2.2. But somehow this is fixed in OH 2.3 SNAPSHOT which is good. I dont see an error message in habmin. Should i be using 2.2 or 2.3 snapshot?

So long as you’re using the correct version of the binding, I don’t think it should matter. Maybe there were changes to the serial driver that I’m not aware of though, but otherwise either should be fine.

Interesting (but good I guess :wink: ).

Finally (again), it does not work anymore… After a system restart, now the node status is blocked on Node initialising: REQUEST_NIF and the famous NODE 2: SECURITY_ERR No valid NONCE! null is back at any message reception from the device :frowning:

OH2 Z-Wave refactoring and testing... and SECURITY

Add-ons Bindings

5iver (Scott Rushworth) March 2, 2018, 7:46am 2552

Here is the rule that I made to automate deleting and rediscovering Zwave Things. I finally figured out how to also reconfigure the temperature scale too!