I thought I’d add a status of the OH2 zwave situation here…
Currently, the zwave binding for OH1 is working fine under OH2, so this is currently the recommended path.
In the coming days (or so!) I hope to have a first version of the OH2 zwave binding ready for testing. There are still a few changes to be discussed that need to be merged into the ESH core that I’m waiting to get approved, but once this is done I should be able to release a test binding… This is related to the ability of the binding to provide binding defined options (rather than static options that are defined in the configuration file) - this is needed to provide association updates since the options are dependant on the device… We’re still discussing how to implement this, so this is the current blocker for zwave on OH2…
However, when available, the OH2 binding, in keeping with OH2 concepts, will have automatic binding of channels/items to zwave devices which should make the binding a LOT easier to use - especially for beginners. There will be no need to add complex binding strings - these will automatically be configured with the database - we’ve spent a some time over the past months adding functionality to ESH to support the features zwave needs. This means that the database needs updating - it’s a completely new format to the OH1 database, although I do have a converter to hopefully ease the job. Since the new database needs more information, it’s not a simple case of just converting all the files - I will make the converted files available, and when someone wants a device added they can use it as a starting point, but it will need some work and review…
There are still a few features that I need to implement. Most of this is related to the automatic configuration of the device that I added recently in the OH1 binding, and this makes use of the database. Since this is different in OH2, there’s always the chance that the database format might need to change a little, so I’d like to get a few people using it before we spend too much time adding loads of devices (there are currently 196 devices in the database!). There is some information on the new database format here.
Other things missing at the moment are the nightly heal, and polling (which again needs to be done differently than OH1).
There have also been a few changes in the code - not to the core of the zwave processing, but I have changed the converter concept. This needed to change in ESH due to us now dealing with channels and not items, but I’ve taken the opportunity to simplify this a little. This does mean that I’ve probably introduced some bugs in converters - they ought to be easy to fix, but again this adds to the desire to introduce the binding to a small number of users first…
I’ve also added some new command classes - namely the COLOR command class to support color bulbs.
Any questions etc, just ask
Cheers
Chris