The same … 
openhab.xml (135.6 KB)
I am thinking to send back the sensor to the seller …
The log contains no debug information.
Sorry … et voilà!
openhab.xml (261.3 KB)
I don’t really know what is happening in this log, but your OH system is not running well and the binding is restarting every 15 to 20 seconds…
12:02:24.631 [INFO ] [rialApiGetInitDataMessageClass:72 ] - ------------Number of Nodes Found Registered to ZWave Controller------------
12:02:24.891 [INFO ] [rialApiGetInitDataMessageClass:73 ] - # Nodes = 2
12:02:25.181 [INFO ] [rialApiGetInitDataMessageClass:74 ] - ----------------------------------------------------------------------------
12:02:46.036 [INFO ] [rialApiGetInitDataMessageClass:72 ] - ------------Number of Nodes Found Registered to ZWave Controller------------
12:02:46.321 [INFO ] [rialApiGetInitDataMessageClass:73 ] - # Nodes = 2
12:02:46.651 [INFO ] [rialApiGetInitDataMessageClass:74 ] - ----------------------------------------------------------------------------
12:03:09.783 [INFO ] [rialApiGetInitDataMessageClass:72 ] - ------------Number of Nodes Found Registered to ZWave Controller------------
12:03:10.042 [INFO ] [rialApiGetInitDataMessageClass:73 ] - # Nodes = 2
12:03:10.381 [INFO ] [rialApiGetInitDataMessageClass:74 ] - ----------------------------------------------------------------------------
12:03:35.558 [INFO ] [rialApiGetInitDataMessageClass:72 ] - ------------Number of Nodes Found Registered to ZWave Controller------------
12:03:35.707 [INFO ] [rialApiGetInitDataMessageClass:73 ] - # Nodes = 2
12:03:35.850 [INFO ] [rialApiGetInitDataMessageClass:74 ] - ----------------------------------------------------------------------------
12:03:54.271 [INFO ] [rialApiGetInitDataMessageClass:72 ] - ------------Number of Nodes Found Registered to ZWave Controller------------
12:03:54.497 [INFO ] [rialApiGetInitDataMessageClass:73 ] - # Nodes = 2
12:03:54.781 [INFO ] [rialApiGetInitDataMessageClass:74 ] - ----------------------------------------------------------------------------
Could be something related to openhab.cfg?
Below parametres that i set …
zwave:port= /dev/ttyACM0
zwave:healtime=2AM
zwave:maseterController = true
zwave:networkKey=0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x10, 0x11, 0x12, 0x13, 0x14, 0x15
zwave:setSUC=true
Something other? Something wrong?
I’m not sure - it’s not something I’ve seen before. Maybe there’s an exception being thrown and it might be logged on the console rather than the logfile?
Not any exception …
“Note that some controllers register themselves as a modem (/dev/ttyACM) on Linux. In this case it is necessary to add user “openhab” to the group “dialout”. Else openHAB won’t be able to access the controller.”
Could be that above the reason? I don’t do that …
No - the port is opening ok, and data is sent and read back, but then something happens and it doesn’t process the response properly and it repeats.
I suspect that you are running this on VERY slow hardware. During the initialisation, we print out some information, and in your case, this is now taking a number of seconds (2 to 4 on your system) and this causes things to time out and repeat (the timeout is 5 seconds and everything is just running slowly). It normally takes a few milliseconds (on my computer it takes 4ms).
Can you confirm what the hardware is you are using, or if you’re running on a slow VM or what would cause this to happen.
I’am running on a UDOO … it’s slow … can be this the problem? It’s better a PI?
I sand you the last log …
openhab.xml (68.3 KB)
Do you think that it is better to change Sensor or HW?
Tks
Sorry - the log doesn’t have anything in it - it’s not debug level for starters.
I don’t know the UDOO so can’t comment. The newer PI are ok, but the original PI is also very slow and has some problems (I guess they probably aren’t available now anyway).
Does it means something for you?
3996 2016-11-20 22:21:34.011 [WARN ] [ApplicationCommandMessageClass] - NODE 8: Not initialized yet, ignoring message.
3997 2016-11-20 22:21:37.636 [WARN ] [i.p.s.IsFailedNodeMessageClass] - NODE 8: Is currently marked as failed by the controller!
3998 2016-11-20 22:21:44.030 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 8: Unsupported command class ZWAVE_PLUS_INFO
3999 2016-11-20 22:21:44.172 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 8: Unsupported command class ASSOCIATION_GROUP_INFO
4000 2016-11-20 22:21:44.396 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 8: Unsupported command class POWERLEVEL
4001 2016-11-20 22:21:44.432 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 8: Unsupported command class DEVICE_RESET_LOCALLY
4002 2016-11-20 22:21:44.483 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 8: Unsupported command class SECURITY
4003 2016-11-20 22:21:44.508 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 8: Unsupported command class FIRMWARE_UPDATE_MDYes, but it’s not an issue here. These are generally classes that aren’t required - at least for the sensor.
I’have an exception … Could be this the problem?
90 08:22:58.521 [INFO ] [sphere.cpr.AtmosphereFramework:639 ] - Installed AtmosphereHandler org.atmosphere.handler.ReflectorServletProcessor mapped to context-path /* and Broadcaster Class org.atmosphere.jersey.JerseyBroadcaster
91 08:22:58.529 [INFO ] [sphere.cpr.AtmosphereFramework:1945 ] - Auto detecting WebSocketHandler in /WEB-INF/classes/
92 08:22:58.854 [INFO ] [sphere.cpr.AtmosphereFramework:1602 ] - Installed WebSocketProtocol org.atmosphere.websocket.protocol.SimpleHttpProtocol
93 08:22:59.292 [INFO ] [.a.h.ReflectorServletProcessor:103 ] - Installing Servlet com.sun.jersey.spi.container.servlet.ServletContainer
94 08:22:59.608 [INFO ] [c.s.j.s.i.a.WebApplicationImpl:815 ] - Initiating Jersey application, version 'Jersey: 1.18.1 02/19/2014 03:28 AM'
95 08:22:59.631 [INFO ] [c.s.j.s.i.a.WebApplicationImpl:826 ] - Adding the following classes declared in META-INF/services/jersey-server-components to the resource configuration:
96 class org.atmosphere.jersey.AtmosphereResourceConfigurator
97 08:23:00.438 [INFO ] [j.s.i.a.DeferredResourceConfig:101 ] - Instantiated the Application class org.openhab.io.habmin.HABminApplication
98 08:23:10.827 [WARN ] [sphere.cpr.AtmosphereFramework:1097 ] -
99 java.lang.ClassNotFoundException: org.atmosphere.interceptor.DefaultHeadersInterceptor
100 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501) ~[org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]
101 at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421) ~[org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]
102 at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412) ~[org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]
103 at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) ~[org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]
104 at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ~[na:1.7.0_101]
105 at org.atmosphere.util.IOUtils.loadClass(IOUtils.java:309) ~[atmosphere-runtime-2.2.5.jar:2.2.5]
106 at org.atmosphere.cpr.AtmosphereFramework.configureAtmosphereInterceptor(AtmosphereFramework.java:1094) [atmosphere-runtime-2.2.5.jar:2.2.5]
107 at org.atmosphere.cpr.AtmosphereFramework.init(AtmosphereFramework.java:892) [atmosphere-runtime-2.2.5.jar:2.2.5]
108 at org.atmosphere.cpr.AtmosphereFramework.init(AtmosphereFramework.java:780) [atmosphere-runtime-2.2.5.jar:2.2.5]
109 at org.atmosphere.cpr.AtmosphereServlet.configureFramework(AtmosphereServlet.java:101) [atmosphere-runtime-2.2.5.jar:2.2.5]
110 at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:80) [atmosphere-runtime-2.2.5.jar:2.2.5]
111 at org.eclipse.equinox.http.servlet.internal.ServletRegistration.init(ServletRegistration.java:49) [org.eclipse.equinox.http.servlet_1.1.300.v20120522-1841.jar:na]
112 at org.eclipse.equinox.http.servlet.internal.ProxyServlet.registerServlet(ProxyServlet.java:179) [org.eclipse.equinox.http.servlet_1.1.300.v20120522-1841.jar:na]
113 at org.eclipse.equinox.http.servlet.internal.HttpServiceImpl.registerServlet(HttpServiceImpl.java:66) [org.eclipse.equinox.http.servlet_1.1.300.v20120522-1841.jar:na]
114 at org.openhab.io.habmin.HABminApplication.activate(HABminApplication.java:178) [bundlefile:na]
115 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_101]
116 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_101]
117 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_101]No - this isn’t anything to do with ZWave - it’s associated with the web interface.
I lost … I’ll send back the sensor and I’ll buy a Fibaro …
