Thats not the problem, everything seems fine at first.
But the device doesnt report temperatures and doesnt react to changed items or configuration parameters.
In fact its doing nothing at all unless i set it directly by the devices buttons, which kills the whole sense of a centrally managed thermostat.
On my device, the default settings for reporting temperature and valve status both were OFF. I both set them to ā1ā right from the start, meaning
- report temperature each time the temperature changes by 0.1Ā°C
- report valve position each time it changes by 1%
I havenāt tested the effect of reverting these settings to 0.
I would suggest that you try to apply the same settings for parameters 5 and 6 and confirm via debug log that these settings get sent across to the device. I have best experience setting device parameters via the habmin gui. There, you see a āpendingā¦ā indicator as long as the setting has not been applied to the device.
At 12:32:20 I changed the "temperature report " setting from 1 to 2. Below is a screenshot of what I see in the z-wave log viewer. You might want to compare to what you see.
I tried setting the config parameters. The node doesnt even show up via the log viewer, this is logged to the log file:
2018-01-06 16:01:16.401 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Configuration update received
2018-01-06 16:01:16.403 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Configuration update config_5_1 to 1
2018-01-06 16:01:16.404 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Error getting configurationCommandClass
2018-01-06 16:01:16.405 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Configuration update config_6_1 to 1
2018-01-06 16:01:16.406 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Error getting configurationCommandClass
Hi,
I thought about replacing some of my Danfoss LC13 with the new Eurotronic Spirit devices. Do they work now within OH2?
@FrankR I didnāt get them to work properly, yet. Hansvandammeās ones seem to work without any problems, i canāt give you a simple yes or no.
@hansvandamme In the node13.xml are no āconfigurationCommandClassā-Tags as they are in the other xmls.
Could this be the problem? In which constellation does this appear and is there a fix for this?
I now have two devices in active use, and they work quite OK. I had no problem adding them to the zwave network, using the standard binding with the current distro of OH2. Initial pairing via Paper UI and parameter setting via Habmin.
The only thing I changed compared to default settings, are the reporting settings ā see my post of Jan 6, above. This way, I want to ensure that the device reports its status often and until now this is working very well.
I am using openHABian op Raspberry PI 3 and Aeon z-stick gen 5.
The only thing that bothers me, is that one of the devices (my first one) sometimes goes offline for hours. But as soon as I send it a command (temp setpoint), it reappears after a few minutes. So, from a user perspective this is not an issue.
@Julian_Kuchlbauer I cannot really help you here. I only saw in your logs that there is an āError getting configurationCommandClassā, but according to this thread this is not really an error. I am still quite new to OH and have no real idea on how you could troubleshoot this one. I am adding here the XML of my second device. Maybe the differences with your XML will point you in the right direction.
node14.xml (11.2 KB)
Please explain the problem.
Iāve finally received a replacement to the faulty unit I bought to support testing, so will be able to test in a few days, but it would be good to understand why itās not working.
The problem hasnāt changed / wasnāt solved since i opened up this thread, so it is still this:
Hey guys,
I have some trouble as well. The device is included and works sometimes but it seems that it has no neighbours. There are 2 other nodes in the room, one with battery and one with permanent power. both have neigbours and are routing devices. Any idea what I could do. I treid āheal teh deviceā several times but nothing happened.
Thanks for your help.
Christian
I see the same happening. Sometimes one of the devices goes offline for minutes/hours and then suddenly reappears.
Yesterday I moved my controller (Raspberry Pi + Aeotec z-stick gen5) more centrally and I donāt see any disconnects for now. From this, I --preliminary-- conclude that zwave transmission strength of the devices is extremely weak, nowhere near the ā30m in buildingsā slogan. I would say something like 5 meters range. I wonder whether there is a way to prove this theory.
I, too, saw no trace of meshing behaviour until now. Nor in paper UI thing properties, nor in the zwave XMLs I see any device reporting any neighbours, except the z-stick which reports a small subset of zwave devices I have in use now. Maybe this is due to the relative proximity of my controller to all devices. But then I would not expect to see any device go offline intermittently.
Many Thanks for your feedback. I will contact the vendor regarding the meshing problem and will let you know when I receive an answer.
@chris Do you know a way to go on in investigating my problem? Unfortunately i have no idea how to continue.
Dear all the vendor has up to now answered nothing usefull. I still have the problem that the device doesnāt show any neghbors so most of the time there is no communication possibleā¦
Dear hansvandamme. Do you see any neighbours reportd in Habmin since you moved your controller?
Hi Christian. None of the devices reports any neighbours. Not in habmin, not in the XML files.
I now tried a āheal deviceā for the devices that are furthest away from the controller. These would benefit most from neighbouring. The XML file is rewritten, but still no neighbours detected.
I think I have the same problem. I just installed the Eurotronic Spirit with the Aeon Labs Z-stick Gen 5. Including the device went fine, but the device does not respond to commands (changing parameters, set point temperature or change of heating mode). In HABmin it has no neighbours either. The status shows āNode initialising: PINGā.
I will try moving the main controller closer to the Spirit, as I have the feeling itās a range problem after reading this topic. Or the mesh networking is not active, as like some of you I have multiple powered routing devices in the same room as the Spirit, whereas the main controller is about 10 meters away on another floor.
Actually, itās probably not a range issue, as including and excluding works perfectlyā¦
EDIT: No, thought it did but also including and excluding does not work with a long range to the controller, see below.
Iāve been looking at the logsā¦ Not sure what to make of it. When I just change the temperature or send other commands, with debugging enabled for Z-wave, this shows up in the logs:
20:35:00.655 [INFO ] [smarthome.event.ItemCommandEvent ] - Item 'FF_Bedroom_Heating' received command 9
20:35:00.656 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 6: Command received zwave:device:8c5f7ebe:node6:thermostat_setpoint_heating --> 9
20:35:00.686 [INFO ] [smarthome.event.ItemStateChangedEvent] - FF_Bedroom_Heating changed from 10 to 9
20:35:00.780 [DEBUG] [rter.ZWaveThermostatSetpointConverter] - NODE 6: Thermostat command received for 9
20:35:00.807 [INFO ] [home.event.GroupItemStateChangedEvent] - gHeating changed from 10 to 9 through FF_Bedroom_Heating
20:35:00.838 [DEBUG] [s.ZWaveThermostatSetpointCommandClass] - NODE 6: Creating new message for command THERMOSTAT_SETPOINT_SET
20:35:00.905 [DEBUG] [rter.ZWaveThermostatSetpointConverter] - NODE 6: Sending Message: Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=6, callback=0, payload=06 05 43 01 01 01 09
20:35:00.957 [DEBUG] [s.ZWaveThermostatSetpointCommandClass] - NODE 6: Creating new message for application command THERMOSTAT_SETPOINT_GET (Heating)
20:35:01.000 [DEBUG] [tocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
20:35:01.000 [DEBUG] [ave.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
20:35:01.028 [DEBUG] [zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0C 00 13 06 05 43 01 01 01 09 25 96 1B
20:35:01.057 [DEBUG] [ave.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
20:35:01.086 [DEBUG] [ding.zwave.handler.ZWaveSerialHandler] - NODE 6: Sending REQUEST Message = 01 0C 00 13 06 05 43 01 01 01 09 25 96 1B
20:35:01.159 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
20:35:01.184 [DEBUG] [ave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
20:35:01.207 [DEBUG] [zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
20:35:01.233 [DEBUG] [ave.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
20:35:01.259 [DEBUG] [ave.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
20:35:01.295 [DEBUG] [ol.serialmessage.SendDataMessageClass] - NODE 6: Sent Data successfully placed on stack.
20:35:04.675 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 96 01 01 61 1C
20:35:04.699 [DEBUG] [ave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
20:35:04.722 [DEBUG] [zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 96 01 01 61 00 00 12
20:35:04.749 [DEBUG] [ave.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 96 01 01 61 00 00 12
20:35:04.777 [DEBUG] [ave.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=96 01 01 61
20:35:04.812 [DEBUG] [ol.serialmessage.SendDataMessageClass] - NODE 6: SendData Request. CallBack ID = 150, Status = Transmission complete, no ACK received(1)
20:35:04.846 [DEBUG] [ol.serialmessage.SendDataMessageClass] - NODE 6: Node is DEAD. Dropping message.
20:35:04.872 [DEBUG] [ave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
20:35:04.900 [DEBUG] [ialization.ZWaveNodeInitStageAdvancer] - NODE 6: Node advancer - PING: Transaction complete (SendData:Request) success(false)
20:35:04.933 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 6: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
20:35:04.964 [DEBUG] [tocol.ZWaveController$ZWaveSendThread] - NODE 6: Response processed after 3815ms/4140ms.
20:35:04.989 [DEBUG] [tocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
20:35:05.016 [DEBUG] [zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 13 06 03 43 02 01 25 97 11
20:35:05.045 [DEBUG] [ding.zwave.handler.ZWaveSerialHandler] - NODE 6: Sending REQUEST Message = 01 0A 00 13 06 03 43 02 01 25 97 11
20:35:05.105 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
20:35:05.128 [DEBUG] [ave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
20:35:05.149 [DEBUG] [zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
20:35:05.174 [DEBUG] [ave.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
20:35:05.198 [DEBUG] [ave.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
20:35:05.231 [DEBUG] [ol.serialmessage.SendDataMessageClass] - NODE 6: Sent Data successfully placed on stack.
20:35:08.650 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 97 01 01 63 1F
20:35:08.675 [DEBUG] [ave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
20:35:08.697 [DEBUG] [zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 97 01 01 63 00 00 11
20:35:08.724 [DEBUG] [ave.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 97 01 01 63 00 00 11
20:35:08.749 [DEBUG] [ave.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=97 01 01 63
20:35:08.784 [DEBUG] [ol.serialmessage.SendDataMessageClass] - NODE 6: SendData Request. CallBack ID = 151, Status = Transmission complete, no ACK received(1)
20:35:08.817 [DEBUG] [ol.serialmessage.SendDataMessageClass] - NODE 6: Node is DEAD. Dropping message.
20:35:08.842 [DEBUG] [ave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
20:35:08.869 [DEBUG] [ialization.ZWaveNodeInitStageAdvancer] - NODE 6: Node advancer - PING: Transaction complete (SendData:Request) success(false)
20:35:08.901 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 6: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
20:35:08.932 [DEBUG] [tocol.ZWaveController$ZWaveSendThread] - NODE 6: Response processed after 3838ms/4140ms.
When I try to change a parameter using HABmin all the parameters are stuck at āPendingā¦ā and the log repeats this over and over:
20:41:50.677 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 B7 01 01 5D 01
20:41:50.707 [DEBUG] [ave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
20:41:50.733 [DEBUG] [zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 B7 01 01 5D 00 00 0F
20:41:50.769 [DEBUG] [ave.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 B7 01 01 5D 00 00 0F
20:41:50.801 [DEBUG] [ave.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=B7 01 01 5D
20:41:50.845 [DEBUG] [ol.serialmessage.SendDataMessageClass] - NODE 6: SendData Request. CallBack ID = 183, Status = Transmission complete, no ACK received(1)
20:41:50.887 [DEBUG] [ol.serialmessage.SendDataMessageClass] - NODE 6: Node is DEAD. Dropping message.
20:41:50.919 [DEBUG] [ave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
20:41:50.959 [DEBUG] [ialization.ZWaveNodeInitStageAdvancer] - NODE 6: Node advancer - PING: Transaction complete (SendData:Request) success(false)
20:41:51.003 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 6: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
20:41:51.045 [DEBUG] [tocol.ZWaveController$ZWaveSendThread] - NODE 6: Response processed after 3863ms/4600ms.
20:41:51.078 [DEBUG] [tocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 21
20:41:51.114 [DEBUG] [zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0C 00 13 06 05 70 04 05 01 04 25 B8 0A
20:41:51.153 [DEBUG] [ding.zwave.handler.ZWaveSerialHandler] - NODE 6: Sending REQUEST Message = 01 0C 00 13 06 05 70 04 05 01 04 25 B8 0A
20:41:51.204 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
20:41:51.238 [DEBUG] [ave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
20:41:51.264 [DEBUG] [zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
20:41:51.294 [DEBUG] [ave.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
20:41:51.339 [DEBUG] [ave.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
20:41:51.382 [DEBUG] [ol.serialmessage.SendDataMessageClass] - NODE 6: Sent Data successfully placed on stack.
Changing a parameter through PaperUI though gives me a nullpointer exception:
19:11:13.529 [ERROR] [est.core.internal.thing.ThingResource] - Exception during HTTP PUT request for update config at 'things/zwave:device:8c5f7ebe:node8/config'
java.lang.NullPointerException: null
at org.openhab.binding.zwave.handler.ZWaveThingHandler.handleConfigurationUpdate(ZWaveThingHandler.java:623) [204:org.openhab.binding.zwave:2.3.0.201802191719]
at org.eclipse.smarthome.core.thing.internal.ThingRegistryImpl.updateConfiguration(ThingRegistryImpl.java:94) [116:org.eclipse.smarthome.core.thing:0.10.0.201802191927]
at org.eclipse.smarthome.io.rest.core.internal.thing.ThingResource.updateConfiguration(ThingResource.java:413) [126:org.eclipse.smarthome.io.rest.core:0.10.0.201802191927]
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:497) ~[?:?]
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:745) [?:?]
I tried changing the temperature on the Eurotronic Spirit. This seems to wake up the device and the controller will receive the update (most of the time). After this I can change the value via UI for a few minutes an the Device will receive the change. After a few minutes it will not work anymore.
I repeated this several times and always the same behaviour. So I still guess the controller doesnāt know how to contact the device because neigbours are not available. But I canāt prove because the device is a blackbox. Due to the fact that I have no problem with other device I will return themā¦