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

Exelant · May 8, 2018, 6:35pm

Yes, i have the version from Cloudbees
I hope this is the correct link and actual snapshot version.

chris · May 8, 2018, 7:01pm

No - this is not the correct version. As I said above, you’re not running the version with security.

Please read through the top 6 or so messages in this thread which explains how to install the development version.

Exelant · May 8, 2018, 7:34pm

Ok perfect, i have found the correct version on the top.

After the installation of the new version from 7. May , i have a new Problem:

2018-05-08 20:46:57.952 [ERROR] [org.openhab.binding.zwave] - FrameworkEvent ERROR - org.openhab.binding.zwave
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [245]
  Unresolved requirement: Import-Package: javax.measure.quantity
	at org.eclipse.osgi.container.Module.start(Module.java:444) [?:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620) [?:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599) [?:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571) [?:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514) [?:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) [?:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) [?:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) [?:?]

Is the Development Binding compatible with Openhab 2.2.0.1?

chris · May 8, 2018, 7:35pm

Unfortunately not - there are a few breaking changes in 2.3 so you’ll need to update the runtime.

Boycee · May 9, 2018, 2:23pm

Seemed to be working fine with Openhab 2.2 until last binding release. With latest I get:

[ERROR] [org.openhab.binding.zwave ] - FrameworkEvent ERROR - org.openhab.binding.zwave
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [15]
Unresolved requirement: Import-Package: javax.measure.quantity

at org.eclipse.osgi.container.Module.start(Module.java:444)

chris · May 9, 2018, 2:40pm

As I said earlier (2 days ago when I released the latest version), I’ve just added the UoM features in the latest version. This feature is not available in 2.2 so you need to use 2.3.

I hope that makes sense.

Danonym1 · May 10, 2018, 10:46am

Is it possible to download the last working development build for 2.2? Been looking for it but not able to find anything

chris · May 10, 2018, 11:21am

No - There have been a number of changes that could impact the ability to run with older versions so I’d just suggest to use the last version that you had that works with your system. For the snapshot/development version, the assumption is that you are using the latest runtime.

Danonym1 · May 10, 2018, 8:05pm

Well the issue is that I’ve bought a Danalock V3 so as I understand I am in need for the posibility to include with security. And the developmemt binding is the way to go then. I was also hoping to not upgrade to 2.3 yet. So I guess Im reaching out for the last working developmemt branch for 2.2. Since there has been a working version earlier this should be doable. Or am I wrong? Maybe someone would like to share a working version with me?

DubZ · May 10, 2018, 8:30pm

so using the zwave 2.3 snapshot on oh 2.2 stable edition could run into trouble?

chris · May 10, 2018, 8:34pm

If you are using the snapshot binding, it might work ok with 2.2 - I’m not 100% sure as the framework has been upgraded a lot. Generally though, the snapshot has not had many changes so it will likely work fine.

The development binding is a different story - it HAS had a number of changes that need the latest runtime.

DubZ · May 10, 2018, 8:39pm

until what date it was a snapshot? I think I’m using a jar file from begin of may on a OH 2.2 installation. didnt recognized the move of keywork snapshot -> development binding good to know

chris · May 10, 2018, 8:41pm

I’m not sure I understand you.

There are two versions of the ZWave binding - the master branch which comes with the nightly snapshot, and the development branch. It’s been like this for over 1 year and I hope to merge this once 2.3 is released (ie very soon now!).

Lolodomo · May 11, 2018, 11:12am

@chris : I have now added few Z-Wave devices to my network and I encounter 2 major (blocking) issues:

My everspring ST814 temperature/humidity sensor is not working. At startup, the thing is first ONLINE then it appears OFFLINE for ever with the following message: COMMUNICATION_ERROR Node is not communicating with controller. The thing was discovered and added using Paper UI and the device is at less than 2 meters form the Z-Stick. I am using the default configuration paramleters.
For Fibaro FGD211 and Aeon Labs DSC06 Smart Energy Switch, any local control leads to no change in openHAB ! This is something that works perfectly in the Vera, at least for the Fibaro FGD. Is is a feature not yet implemented in the binding ? Is it just a parameter problem ? I have to mention that the local control for the Nodon Micro Smart Plug is working well on its side. The Fibaro FGD thing was discovered and added using Paper UI. I only changed the configuration parameter 14 to set it to 1.

As mentioned in the other thread, the fact to not be able to configure a device in a things file is very annoying but not blockling.

chris · May 11, 2018, 11:28am

You’d need to check the logs, but it very likely means that the device is not responding to messages that the controller is sending. It could be out of range?

Please check the association configuration. Ideally, this should be configured automatically for ZW+ devices, and any device for which the database is properly configured to set this.

Yes, agreed, but as I hope I’ve explained, I don’t think there’s any nice solution to this at the moment. My solution was to allow configuration to be sent to devices configured in things, but this PR was rejected by ESH. There is a plan to implement a new configuration system for configuring devices, but I think it’s probably still a little while away (sorry again for this).

Lolodomo · May 11, 2018, 11:47am

The Nodon Micro Smart Plug is my only ZW+ device and it is working.

For the Aeon Labs DSC06 Smart Energy Switch, I can see the value “node_1” for Association Groups => “1: Status Reports”. Should I set it to another value ?

For the FGD211, I can see no value set for Association Groups => “1: Switch 1”, “2: Switch 2” and “3: Controller Updates”. Is it expected ? What values should I set ? I can see"openHAB Controller" as possible value for the last parameter.

I imagine it is not possible to change these values from my config file…

chris · May 11, 2018, 12:04pm

Should be fine (I’m assuming your controller is node 1). I’d suggest to check the logs to see if anything is being returned.

No - I think you should have group 3 set (I have many of these at home).

Correct .

Lolodomo · May 11, 2018, 12:26pm

After setting the parameter “3: Controller Updates” to the value “openHAB Controller”, the thing is ONLINE again but when I reopen the configuration, the value is gone (no value displayed) and the problem is still there.

Lolodomo · May 11, 2018, 12:39pm

For my Aeon Labs DSC06 Smart Energy Switch, here are logs when I switch it off from the local button:

14:33:51.028 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 13 00 49 84 03 0D 04 10 01 25 31 32 27 70 85 72 86 EF 82 57
14:33:51.042 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationUpdate[73], type=Request[0], dest=3, callback=132, payload=84 03 0D 04 10 01 25 31 32 27 70 85 72 86 EF 82
14:33:51.051 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationUpdate[73], type=Request[0], dest=3, callback=132, payload=84 03 0D 04 10 01 25 31 32 27 70 85 72 86 EF 82
14:33:51.060 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationUpdate[73], type=Request[0], dest=3, callback=132, payload=84 03 0D 04 10 01 25 31 32 27 70 85 72 86 EF 82
14:33:51.068 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - lastTransaction null
14:33:51.075 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 0
14:33:51.082 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Last transaction: null
14:33:51.088 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - ****************** Transaction not correlated
14:33:51.097 [DEBUG] [ave.internal.protocol.ZWaveController] - Incoming Message: Message: class=ApplicationUpdate[73], type=Request[0], dest=3, callback=132, payload=84 03 0D 04 10 01 25 31 32 27 70 85 72 86 EF 82
14:33:51.105 [DEBUG] [message.ApplicationUpdateMessageClass] - NODE 3: Application update request. Node information received. Transaction null
14:33:51.112 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 3: resetResendCount initComplete=true isDead=false
14:33:51.119 [DEBUG] [message.ApplicationUpdateMessageClass] - NODE 3: Application update - no transaction.
14:33:51.127 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
14:33:51.134 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
14:33:51.140 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction from controllerQueue
14:33:51.146 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage nothing
14:33:51.377 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 3: Node is listening - ignore wakeup

Something seems to be received.

Lolodomo · May 11, 2018, 12:43pm

For the Fibaro FGD211, even if the parameter is not displayed correctly in Paper UI, it is now working as expected (well). One problem solved.