Confused about default setup for Fibaro motion sensor

[Fredrik_Karlsson]

Hi,

I am using the 2.3.0 version of the z-wave binding, which may matter here…

Ok. what I am seeing are three things, which may be related (?).

It seems that whatever I do I cannot get proper hold of the motion sensors that I am moving from another network to my new z-wave binding based network. What I mean by properly get hold of here is that I can include the devices fine, and they seem to work ok. I get all the sub-devices and can assign then to rooms and groups.

But, since I don’t want the led giving feedback when I pass by it, I want to disable it. That change in settings never “takes” however. I can apply it, save and wake the device, but I still get the cat eye when I pass the motion sensor.

Also, looking at the association groups, they are not set up properly (at least if I am not misunderstanding something here)

These should all, if I am not mistaken, at least include the openhab controller. And I dont know which nodes these 215 and so on are, since my list of nodes dont go higher than 50 at the moment.

The problem is then that I cant remove them either. I can set the lifeline to openhab controller, and then I get temperature readouts and so on. But, if I try to remove for instance noew_215_0 from group 2, I get an internal server error notification (and no change in the device of course) and I get this in the logs (device 53 is the one I tried to alter)

2018-08-26 09:58:54.875 [ERROR] [st.core.internal.thing.ThingResource] - Exception during HTTP PUT request for update config at 'things/zwave:device:edde6877:node53/config'
java.lang.NullPointerException: null
	at org.openhab.binding.zwave.handler.ZWaveThingHandler.handleConfigurationUpdate(ZWaveThingHandler.java:623) [230:org.openhab.binding.zwave:2.3.0]
	at org.eclipse.smarthome.core.thing.internal.ThingRegistryImpl.updateConfiguration(ThingRegistryImpl.java:92) [108:org.eclipse.smarthome.core.thing:0.10.0.oh230]
	at org.eclipse.smarthome.io.rest.core.internal.thing.ThingResource.updateConfiguration(ThingResource.java:425) [118:org.eclipse.smarthome.io.rest.core:0.10.0.oh230]
	at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source) ~[?:?]
	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) [170:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144) [170:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161) [170:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160) [170:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99) [170:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389) [170:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347) [170:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102) [170:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326) [170:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) [169:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) [169:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.internal.Errors.process(Errors.java:315) [169:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.internal.Errors.process(Errors.java:297) [169:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.internal.Errors.process(Errors.java:267) [169:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) [169:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305) [170:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154) [170:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473) [167:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) [167:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388) [167:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341) [167:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228) [167: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) [85:org.eclipse.jetty.servlet:9.3.21.v20170918]
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:584) [85:org.eclipse.jetty.servlet:9.3.21.v20170918]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) [183:org.ops4j.pax.web.pax-web-jetty:6.0.9]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) [82:org.eclipse.jetty.security:9.3.21.v20170918]
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:284) [183:org.ops4j.pax.web.pax-web-jetty:6.0.9]
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) [85:org.eclipse.jetty.servlet:9.3.21.v20170918]
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) [183:org.ops4j.pax.web.pax-web-jetty:6.0.9]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.server.Server.handle(Server.java:534) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) [84:org.eclipse.jetty.server:9.3.21.v20170918]
	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) [76:org.eclipse.jetty.io:9.3.21.v20170918]
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) [76:org.eclipse.jetty.io:9.3.21.v20170918]
	at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) [76:org.eclipse.jetty.io:9.3.21.v20170918]
	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) [87:org.eclipse.jetty.util:9.3.21.v20170918]
	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) [87:org.eclipse.jetty.util:9.3.21.v20170918]
	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) [87:org.eclipse.jetty.util:9.3.21.v20170918]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) [87:org.eclipse.jetty.util:9.3.21.v20170918]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) [87:org.eclipse.jetty.util:9.3.21.v20170918]
	at java.lang.Thread.run(Thread.java:748) [?:?]

So, I really cant get beyond the current state at the moment.

I should also add that I am seeing this in the logs. May be totally unrelated, but I cannot tell so I am including it here just the same - if it matters.

2018-08-26 10:15:22.854 [ERROR] [tocol.commandclass.ZWaveCommandClass] - Error extracting value - length=8, offset=6, size=7.
2018-08-26 10:15:22.915 [ERROR] [tocol.commandclass.ZWaveCommandClass] - Error extracting value - length=8, offset=6, size=6.
2018-08-26 10:15:23.158 [ERROR] [tocol.commandclass.ZWaveCommandClass] - Error extracting value - length=8, offset=6, size=3.
2018-08-26 10:15:23.434 [ERROR] [tocol.commandclass.ZWaveCommandClass] - Error extracting value - length=8, offset=6, size=3.
2018-08-26 10:15:23.553 [ERROR] [tocol.commandclass.ZWaveCommandClass] - Error extracting value - length=8, offset=6, size=3.

Any ideas on how to get hold of my motion sensors - they are included but not in my reach somehow…

[mstormi (Markus Storm)]

I used to encounter that behavior at times, too, but cannot explain.

First, re-initialize your node(s) using habmin. That(if successful) should remove those latter warnings you’re seeing. That might or might not help with your problem.

If it does not, to get rid of those “fake” associations, you can edit the jsondb (/var/lib/openhab2/jsondb/org.eclipse.smarthome.core.thing.Thing.json). You can right replace the fake nodes with the controller’s ID. But play it safe, i.e. shutdown OH before, and take backups of your full config, and safety copies of the jsondb file.

[Fredrik_Karlsson]

Not sure what to make of this (and sorry for altering the topic of the thread somewhat).

It seems that even in working devices, I get associations inserted (by the binding?) no matter what I do. In a well behaving node, I am able to insert the controller node into Lifeline. Then I will have associations to “node_202_0” or something like that in all other association groups. Now, I can “remove the tick” in the PaperUI GUI and get everything neat and tidy, but once I save the edits, there will be new associations to “fake” nodes (“node__0”) in the groups.

Is this normal behavior? Any ideas about why this is happening?

[mstormi (Markus Storm)]

@Fredrik_Karlsson

Is this normal behavior? Any ideas about why this is happening?

No it is not and as I wrote I don’t know why it is happening, but I explained how to fix it.

[Seaside]

I have about 10 fibaro motion sensors in my home, had my fair share of problems with them.
Anyway once properly included they function very well and have a lot of flexibility.

Would do the following:

1. Use habmin and not paper ui when you configure you zwave devices
2. Exclude it. Factory reset it and then include it again just to be sure. If it cannot be included, factory reset it.
3. When including it, wake it up manually by double clicking the button
4. When changing config and setting association groups, wake it up by double clicking it, otherwise
   it will take a lot of time before it wakes up and the settings will be applied.

Regards, S

[Fredrik_Karlsson]

@mstormi

No it is not and as I wrote I don’t know why it is happening, but I explained how to fix it.

Yes, sorry. I will look into doing that procedure. Do the “ghost” nodes come back if you change something in the Paper UI GUI after having edited the nodes away in the json files?

@Seaside

Use habmin and not paper ui when you configure you zwave devices

Thanks. I will try this also, as I have tried steps 2-4 as part of my earlier attempts.