Devolo MT2792 Home Control Metering Plug - No Response

Hi all together.

I’ve got openhab2 stable (2.1.0) running on a raspberry pi with debian. All works as expected, including the z-wave binding. My Fibaro rollershutter 2 work perfect, also via the Devolo MT2792 Home Control Metering Plugs as repeater. So I think the Devolo work in princible.

At first I got the problem that my Smart Plugs won’t be recognized as right device, only unknown. So I updated my z-wave-binding to the the 2.2.0-snapshot-version with the kar-file. Therefore I’m not sure, if I’ve got the latest version of the binding because of the issue discribed here.

Nevertheless, after deleting the node*.xml-files and removing the things, re-adding the two things (plugs) brought me the right definitions, I think. There were recognized as “MT2792 Home Control Metering Plug”.

I got 11 channels which I linked via text-file.

Switch LampeCouchOnOff "Lampe Couch [%s]" <lamp> (gSteckdosen,gEG_Wohnzimmer) { channel="zwave:device:24fb13569f4:node4:switch_binary"  }
Number LampeCouchSzene "Lampe Couch Szene" { channel="zwave:device:24fb13569f4:node4:scene_number"}
Number LampeCouchAmpere "Lampe Couch Ampere" { channel="zwave:device:24fb13569f4:node4:meter_current"}
Number LampeCouchVolt "Lampe Couch Volt" { channel="zwave:device:24fb13569f4:node4:meter_voltage"}
Number LampeCouchkWH "Lampe Couch kWh" { channel="zwave:device:24fb13569f4:node4:meter_kwh"}
Number LampeCouchFaktor "Lampe Couch Energie Faktor" { channel="zwave:device:24fb13569f4:node4:meter_powerfactor"}
Number LampeCouchWatt "Lampe Couch Watt" { channel="zwave:device:24fb13569f4:node4:meter_watts"}
Number LampeCouchkVAh "Lampe Couch kVAh" { channel="zwave:device:245fb13569f4:node4:meter_kvah"}
Number LampeCouchPulses "Lampe Couch Puls" { channel="zwave:device:24fb13569f4:node4:meter_pulse"}
Switch LampeCouchAlarm "Lampe Couch Alarm" { channel="zwave:device:24fb13569f4:node4:alarm_general"}

In PaperUI they are shown with a dot in the circle, so I think the links are right.

My problem is, that I can’t see anything going on with the devices in openHAB and can’t control the switch via UI. Clicking the switch changes the item (log-files) but nothing happens. Neither switching in the UI or pressing the button on the plug itself nor the any values about metering like voltage, kWh and so on are recognized in openHAB.

I can configure the things over HABmin, except the “Associations Group”. After changing this value to “openHAB controller” I got the follwing in the log-files:

==> /var/log/openhab2/openhab.log <==
2017-12-08 14:59:06.740 [ERROR] [ome.io.rest.core.thing.ThingResource] - Exception during HTTP PUT request for update config at 'things/zwave:device:24fb13569f4:node4/config' for thing 'zwave:device:24fb13569f4:node4': null

Does anyone have the same problem or knows what to do about this issue? Because of the plug attached to the power socke, it it would not be a battery-wakeup-problem.

Thanks in advance.

Hi all together,

meanwhile I installed the actual official Version of openHAB 2.2 completly clean from scratch and tried the zwave-binding 2.2 which was delivered with it. Then I uninstalled this and putted the newest testing binding from 2017-12-29 in the addons-folder. But still no success.

I tried adding the things by file and by paperUI. They always show up, but no response. I can’t activate the switches and can’t read the volt, etc.

Bridge zwave:serial_zstick:controller "Z-Wave Controller" [ port="/dev/ttyACM0", controller_softreset="false", controller_master="true", heal_enable="true", security_networkkey="XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX" ]
{
    Thing devolo_mt2792_00_000 node3 "Lampe Couch" [ node_id=3 ]
    Thing devolo_mt2792_00_000 node4 "Waschmaschine" [ node_id=4 ]
    Thing fibaro_fgrm222_00_000 node5 "Rollladen Wohnzimmertür" [ node_id=5 ]
}

The rollershutter works perfect, but the switches don’t. They are recognized with 11 channels, but none of them gives response.

Addition:
If I try to set the “association group” to “openHAB controller” the log gives me:

2017-12-31 12:25:04.154 [ERROR] [st.core.internal.thing.ThingResource] - Exception during HTTP PUT request for update config at 'things/zwave:device:controller:node4/config'

java.lang.NullPointerException: null

	at org.openhab.binding.zwave.handler.ZWaveThingHandler.handleConfigurationUpdate(ZWaveThingHandler.java:677) [231:org.openhab.binding.zwave:2.2.0.201712290701]

	at org.eclipse.smarthome.core.thing.internal.ThingRegistryImpl.updateConfiguration(ThingRegistryImpl.java:94) [116:org.eclipse.smarthome.core.thing:0.10.0.b1]

	at org.eclipse.smarthome.io.rest.core.internal.thing.ThingResource.updateConfiguration(ThingResource.java:413) [126:org.eclipse.smarthome.io.rest.core:0.10.0.b1]

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]

	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]

	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]

	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]

	at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) [177:org.glassfish.jersey.core.jersey-common:2.22.2]

	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) [177:org.glassfish.jersey.core.jersey-common:2.22.2]

	at org.glassfish.jersey.internal.Errors.process(Errors.java:315) [177:org.glassfish.jersey.core.jersey-common:2.22.2]

	at org.glassfish.jersey.internal.Errors.process(Errors.java:297) [177:org.glassfish.jersey.core.jersey-common:2.22.2]

	at org.glassfish.jersey.internal.Errors.process(Errors.java:267) [177:org.glassfish.jersey.core.jersey-common:2.22.2]

	at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) [177:org.glassfish.jersey.core.jersey-common:2.22.2]

	at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473) [175:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]

	at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) [175:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]

	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388) [175:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]

	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341) [175:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]

	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228) [175:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]

	at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76) [15:com.eclipsesource.jaxrs.publisher:5.3.1.201602281253]

	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848) [88:org.eclipse.jetty.servlet:9.3.22.v20171030]

	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:584) [88:org.eclipse.jetty.servlet:9.3.22.v20171030]

	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) [191:org.ops4j.pax.web.pax-web-jetty:6.0.7]

	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) [85:org.eclipse.jetty.security:9.3.22.v20171030]

	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:284) [191:org.ops4j.pax.web.pax-web-jetty:6.0.7]

	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) [88:org.eclipse.jetty.servlet:9.3.22.v20171030]

	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) [191:org.ops4j.pax.web.pax-web-jetty:6.0.7]

	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.server.Server.handle(Server.java:534) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) [79:org.eclipse.jetty.io:9.3.22.v20171030]

	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) [79:org.eclipse.jetty.io:9.3.22.v20171030]

	at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) [79:org.eclipse.jetty.io:9.3.22.v20171030]

	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) [90:org.eclipse.jetty.util:9.3.22.v20171030]

	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) [90:org.eclipse.jetty.util:9.3.22.v20171030]

	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) [90:org.eclipse.jetty.util:9.3.22.v20171030]

	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) [90:org.eclipse.jetty.util:9.3.22.v20171030]

	at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) [90:org.eclipse.jetty.util:9.3.22.v20171030]

	at java.lang.Thread.run(Thread.java:748) [?:?]

Does anybody have a hint.

Thanks in advance.

What binding is this? Is this the development binding that you downloaded from the security discussion thread? If so, please use the latest version.

If the problem persists, then Id suggest to look at the debug logs to see what communications is going on with these devices. You can use the viewer here.

Thanks. Now I deleted the jar in the addons-folder, restarted openhab and downloaded the jar from 2017-12-30 out of the Security Thread.

Still no success, rollershuter perfect, but switches won’t do anything. Will try the debug log viewer you suggested.

I think you don’t mean these files, don’t you?

/var/log/openhab2/openhab.log /var/log/openhab2/events.log

Another issue:
If I configure all by textfiles, the things appear in the list, but also in the inbox. Did I configured it false? Also got this error by trying to edit in HABmin.

2017-12-31 13:15:06.772 [INFO ] [st.core.internal.thing.ThingResource] - Received HTTP PUT request for update configuration at 'things/zwave:devolo_mt2792_00_000:controller:node4/config' for an unmanaged thing 'zwave:devolo_mt2792_00_000:controller:node4'.

zwave.things:

Bridge zwave:serial_zstick:controller "Z-Wave Controller" [ port="/dev/ttyACM0", controller_softreset="false", controller_master="true", heal_enable="true", security_networkkey="XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX" ]
{
    Thing devolo_mt2792_00_000 node3 "Lampe Couch" [ node_id=3 ]
    Thing devolo_mt2792_00_000 node4 "Waschmaschine" [ node_id=4 ]
    Thing fibaro_fgrm222_00_000 node5 "Rollladen Wohnzimmertür" [ node_id=5 ]
}

z-wave.items

//Items-Datei
//Rollladen
Rollershutter EG_WZ_Tuer_Rollladen "Wohnzimmertür [%.0f %%]" <rollershutter> (gRollladen,gEG_Wohnzimmer) { channel="zwave:fibaro_fgrm222_00_000:controller:node5:blinds_control"  }

// Waschmaschine
Switch WaschmaschineOnOff "Waschmaschine [%s]" <whitegood> (gSteckdosen,gKG_Technikraum) {channel="zwave:devolo_mt2792_00_000:controller:node4:switch_binary"}
Number WaschmaschineSzene "Waschmaschine Szene" { channel="zwave:devolo_mt2792_00_000:controller:node4:scene_number"}
Number WaschmaschineAmpere "Waschmaschine Ampere" { channel="zwave:devolo_mt2792_00_000:controller:node4:meter_current"}
Number WaschmaschineVolt "Waschmaschine Volt" { channel="zwave:devolo_mt2792_00_000:controller:node4:meter_voltage"}
Number WaschmaschinekWH "Waschmaschine kWh" { channel="zwave:devolo_mt2792_00_000:controller:node4:meter_kwh"}
Number WaschmaschineFaktor "Waschmaschine Energie Faktor" { channel="zwave:devolo_mt2792_00_000:controller:node4:meter_powerfactor"}
Number WaschmaschineWatt "Waschmaschine Watt" { channel="zwave:devolo_mt2792_00_000:controller:node4:meter_watts"}
Number WaschmaschinekVAh "Waschmaschine kVAh" { channel="zwave:devolo_mt2792_00_000:controller:node4:meter_kvah"}
Number WaschmaschinePulses "Waschmaschine Puls" { channel="zwave:devolo_mt2792_00_000:controller:node4:meter_pulse"}
Switch WaschmaschineAlarm "Waschmaschine Alarm" { channel="zwave:devolo_mt2792_00_000:controller:node4:alarm_general"}
Switch WaschmaschineMeterReset "Waschmaschine Reset Zähler" {channel="zwave:devolo_mt2792_00_000:controller:node4:meter_reset"}

// Lampe Couch
Switch LampeCouchOnOff "Lampe Couch [%s]" <lamp> (gSteckdosen,gEG_Wohnzimmer) {channel="zwave:devolo_mt2792_00_000:controller:node3:switch_binary"}
Number LampeCouchSzene "Lampe Couch Szene" { channel="zwave:devolo_mt2792_00_000:controller:node3:scene_number"}
Number LampeCouchAmpere "Lampe Couch Ampere" { channel="zwave:devolo_mt2792_00_000:controller:node3:meter_current"}
Number LampeCouchVolt "Lampe Couch Volt" { channel="zwave:devolo_mt2792_00_000:controller:node3:meter_voltage"}
Number LampeCouchkWH "Lampe Couch kWh" { channel="zwave:devolo_mt2792_00_000:controller:node3:meter_kwh"}
Number LampeCouchFaktor "Lampe Couch Energie Faktor" { channel="zwave:devolo_mt2792_00_000:controller:node3:meter_powerfactor"}
Number LampeCouchWatt "Lampe Couch Watt" { channel="zwave:devolo_mt2792_00_000:controller:node3:meter_watts"}
Number LampeCouchkVAh "Lampe Couch kVAh" { channel="zwave:devolo_mt2792_00_000:controller:node3:meter_kvah"}
Number LampeCouchPulses "Lampe Couch Puls" { channel="zwave:devolo_mt2792_00_000:controller:node3:meter_pulse"}
Switch LampeCouchAlarm "Lampe Couch Alarm" { channel="zwave:devolo_mt2792_00_000:controller:node3:alarm_general"}
Switch LampeCouchMeterReset "Lampe Couch Reset Zähler" {channel="zwave:devolo_mt2792_00_000:controller:node3:meter_reset"}

Screenshot Inbox
Screenshot Things
Screenshot Channels

Just to note that the security thread binding is the only one that will work correctly for text file definitions, so if you weren’t using that before, then it wouldn’t work…

Yes - it’s the openhab.log file. You will need to enable debug logging for the zwave binding though (karaf command log:set debug org.openhab.binding.zwave).

I think there’s a setting somewhere to disable discovery, but this is currently an issue that I think is being looked at in ESH.

Thanks for your quick response.

Okay, great. A little more infos.

LogViewer gives me only the info, that command was sent.
Log in Frontail has more infos.

Updating the association group gives me:

2017-12-31 14:46:44.634 [INFO ] [st.core.internal.thing.ThingResource] - Received HTTP PUT request for update configuration at 'things/zwave:devolo_mt2792_00_000:controller:node3/config' for an unmanaged thing 'zwave:devolo_mt2792_00_000:controller:node3'.

Well, it shows that the command was sent, and there was no response. Yes, the detailed log give a LOT more detailed information, but the log viewer will allow you to see what is happening with communications with the device a LOT easier than trying to decode the logfile.

This is what I use for diagnosing everyones zwave problems - yes, I may look at the detailed log as well, but for 95% of the issues, the log viewer gives the best information.

Yes - you will need to find some other software to configure the device - sorry. Since you are using text configuration, it is not possible to configure the device through OH. I tried to convince the ESH people to change this, but my suggestion was rejected and there’s currently no alternative.

Okay, you mean, if I can configure the plugs via another software or maybe by the stable addon and set the association group to node_1, everthing should be okay? Or is there another reason, that there is no response?

The reason is that you are using text files to configure your devices. If you use text files, you can not configure devices via the UI - it doesn’t matter if you use the stable addon or the snapshot, or the development version - it’s the same constraint as it’s imposed by ESH.

At first, Happy New Year all together.

Thank You @chris for your sustaining help.

Yesterday I changed the version to the delivered stable version 2.2 and installed everything via PaperUI. I got the things and items, channels seemed to link (dot inside circle).

But if I switch the binary-switch-channel nothing physically happens.

Configuring the Association Channel throwes an error. The log-viewer looks like:

Screenshot

2018-01-01 13:55:17.690 [ERROR] [st.core.internal.thing.ThingResource] - Exception during HTTP PUT request for update config at 'things/zwave:device:e46951b9:node4/config'

java.lang.NullPointerException: null

	at org.openhab.binding.zwave.handler.ZWaveThingHandler.handleConfigurationUpdate(ZWaveThingHandler.java:625) [236:org.openhab.binding.zwave:2.2.0]

	at org.eclipse.smarthome.core.thing.internal.ThingRegistryImpl.updateConfiguration(ThingRegistryImpl.java:94) [116:org.eclipse.smarthome.core.thing:0.10.0.b1]

	at org.eclipse.smarthome.io.rest.core.internal.thing.ThingResource.updateConfiguration(ThingResource.java:413) [126:org.eclipse.smarthome.io.rest.core:0.10.0.b1]

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]

	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]

	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]

	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]

	at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) [177:org.glassfish.jersey.core.jersey-common:2.22.2]

	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) [177:org.glassfish.jersey.core.jersey-common:2.22.2]

	at org.glassfish.jersey.internal.Errors.process(Errors.java:315) [177:org.glassfish.jersey.core.jersey-common:2.22.2]

	at org.glassfish.jersey.internal.Errors.process(Errors.java:297) [177:org.glassfish.jersey.core.jersey-common:2.22.2]

	at org.glassfish.jersey.internal.Errors.process(Errors.java:267) [177:org.glassfish.jersey.core.jersey-common:2.22.2]

	at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) [177:org.glassfish.jersey.core.jersey-common:2.22.2]

	at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154) [178:org.glassfish.jersey.core.jersey-server:2.22.2]

	at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473) [175:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]

	at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) [175:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]

	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388) [175:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]

	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341) [175:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]

	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228) [175:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]

	at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76) [15:com.eclipsesource.jaxrs.publisher:5.3.1.201602281253]

	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848) [88:org.eclipse.jetty.servlet:9.3.22.v20171030]

	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:584) [88:org.eclipse.jetty.servlet:9.3.22.v20171030]

	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) [191:org.ops4j.pax.web.pax-web-jetty:6.0.7]

	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) [85:org.eclipse.jetty.security:9.3.22.v20171030]

	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:284) [191:org.ops4j.pax.web.pax-web-jetty:6.0.7]

	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) [88:org.eclipse.jetty.servlet:9.3.22.v20171030]

	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) [191:org.ops4j.pax.web.pax-web-jetty:6.0.7]

	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.server.Server.handle(Server.java:534) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) [87:org.eclipse.jetty.server:9.3.22.v20171030]

	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) [79:org.eclipse.jetty.io:9.3.22.v20171030]

	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) [79:org.eclipse.jetty.io:9.3.22.v20171030]

	at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) [79:org.eclipse.jetty.io:9.3.22.v20171030]

	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) [90:org.eclipse.jetty.util:9.3.22.v20171030]

	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) [90:org.eclipse.jetty.util:9.3.22.v20171030]

	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) [90:org.eclipse.jetty.util:9.3.22.v20171030]

	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) [90:org.eclipse.jetty.util:9.3.22.v20171030]

	at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) [90:org.eclipse.jetty.util:9.3.22.v20171030]

	at java.lang.Thread.run(Thread.java:748) [?:?]

Now I can finally conclude this thread :blush:

I got it working by doing the following steps.

  1. installed zensys-tools from here
    1.1 plugged the controller in a windows pc
    1.2 read the security-key from the controller
    1.3 set the key in the PaperUI-Config for the controller
  2. Installed the latest version of the security-enabled z-wave binding from this thread
    2.1 Put the devices in energy plugs nearby the controller.
    2.2 HABmin
    2.3 Excluded the plugs from the installation
    2.4 things --> controller --> advanced settings --> set inclusion mode to “high”, not "network wide"
    2.5 included the devices
  3. working perfectly

Why not using the easy way in HABmin (after switching to advanced settings of your zwave controller):

1

Because it showed me the wrong key somehow. Don’t know why. This was the problem. Once I copied the right key to PaperUI, I could include it correctly with no errors in the log anymore.

HABmin uses exactly the same interface to get the data as PaperUI so it’s no really possible for the data to be different.

That’s correct. But Zensys tools showed me another Secure key stored on the stick. Maybe I did something wrong before all of that, but once changed the key, all is fine.

Ok, so I guess somewhere along the lines the secure inclusion was done with other software and that’s presumably why it wasn’t working. OH doesn’t store the security key on the stick - it’s only known to the binding itself.