Seite 1 von 1

HM-ES-TX-WM Communication Error

Verfasst: 10. Jun 2018 22:35
von 1kayzer
Hallo zusammen,

ich nutze openhab schon seit etwa einem halben Jahr und konnte bislang jedes Problem irgendwie lösen. Durch ein Update auf 2.3 habe ich nun jedoch meinen Stromzähler HM-ES-TX-WM im Binding verloren.
Das Gerät funktioniert an der CCU einwandfrei, nach der Integration des Things steht das Gerät Offline mit Communication Error.
Status aus der PaperUI:
Status: OFFLINE - COMMUNICATION_ERROR -1 Failure (sending <?xml version="1.0" encoding="ISO-8859-1"?> <methodCall><methodName>getValue</methodName> <params><param><value>NEQ0863610:1</value></param><param><value>GAS_POWER</value></param></params></methodCall>)

Andere Geräte gehen einwandfrei.

Im Log:

2018-06-10 14:40:59.504 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Boolean) value 'true' for 'NEQ0863610:1#BOOT' from gateway with id 'c1e6902b'
2018-06-10 14:40:59.582 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Double) value '63625.1' for 'NEQ0863610:1#ENERGY_COUNTER' from gateway with id 'c1e6902b'
2018-06-10 14:40:59.632 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loading values for channel HmChannel[number=1,type=POWERMETER_IGL,initialized=false] of device 'NEQ0863610'
2018-06-10 14:40:59.695 [DEBUG] [ternal.communicator.client.RpcClient] - RpcResponse unknown RPC failure (-1 Failure), fetching values with another API method for device: NEQ0863610, channel: 1, paramset: VALUES
2018-06-10 14:40:59.766 [ERROR] [ematic.handler.HomematicThingHandler] - -1 Failure (sending <?xml version="1.0" encoding="ISO-8859-1"?>
<methodCall><methodName>getValue</methodName>
<params><param><value>NEQ0863610:1</value></param><param><value>GAS_POWER</value></param></params></methodCall>)
org.openhab.binding.homematic.internal.communicator.client.UnknownRpcFailureException: -1 Failure (sending <?xml version="1.0" encoding="ISO-8859-1"?>
<methodCall><methodName>getValue</methodName>
<params><param><value>NEQ0863610:1</value></param><param><value>GAS_POWER</value></param></params></methodCall>)
at org.openhab.binding.homematic.internal.communicator.parser.RpcResponseParser.parse(RpcResponseParser.java:43) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.client.XmlRpcClient.sendMessage(XmlRpcClient.java:99) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.client.XmlRpcClient.sendMessage(XmlRpcClient.java:73) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.client.RpcClient.setChannelDatapointValues(RpcClient.java:206) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.client.RpcClient.setChannelDatapointValues(RpcClient.java:188) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.setChannelDatapointValues(AbstractHomematicGateway.java:477) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.loadChannelValues(AbstractHomematicGateway.java:458) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.handler.HomematicThingHandler.loadHomematicChannelValues(HomematicThingHandler.java:268) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.handler.HomematicThingHandler.updateChannelState(HomematicThingHandler.java:247) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.handler.HomematicThingHandler.updateDatapointState(HomematicThingHandler.java:226) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.handler.HomematicBridgeHandler.onStateUpdated(HomematicBridgeHandler.java:233) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.lambda$0(AbstractHomematicGateway.java:615) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.misc.DelayedExecuter.start(DelayedExecuter.java:61) [249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.eventReceived(AbstractHomematicGateway.java:612) [249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleEvent(RpcResponseHandler.java:94) [249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleMethodCall(RpcResponseHandler.java:47) [249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleMethodCall(RpcResponseHandler.java:64) [249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.server.XmlRpcServer$ResponseHandler.handle(XmlRpcServer.java:119) [249:org.openhab.binding.homematic:2.2.0]
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) [?:?]
2018-06-10 14:41:01.090 [DEBUG] [ommunicator.AbstractHomematicGateway] - Received new (Double) value '244.0' for 'NEQ0863610:1#POWER' from gateway with id 'c1e6902b'
2018-06-10 14:41:01.132 [DEBUG] [ommunicator.AbstractHomematicGateway] - Loading values for channel HmChannel[number=1,type=POWERMETER_IGL,initialized=false] of device 'NEQ0863610'
2018-06-10 14:41:01.193 [DEBUG] [ternal.communicator.client.RpcClient] - RpcResponse unknown RPC failure (-1 Failure), fetching values with another API method for device: NEQ0863610, channel: 1, paramset: VALUES
2018-06-10 14:41:01.264 [ERROR] [ematic.handler.HomematicThingHandler] - -1 Failure (sending <?xml version="1.0" encoding="ISO-8859-1"?>
<methodCall><methodName>getValue</methodName>
<params><param><value>NEQ0863610:1</value></param><param><value>GAS_POWER</value></param></params></methodCall>)
org.openhab.binding.homematic.internal.communicator.client.UnknownRpcFailureException: -1 Failure (sending <?xml version="1.0" encoding="ISO-8859-1"?>
<methodCall><methodName>getValue</methodName>
<params><param><value>NEQ0863610:1</value></param><param><value>GAS_POWER</value></param></params></methodCall>)
at org.openhab.binding.homematic.internal.communicator.parser.RpcResponseParser.parse(RpcResponseParser.java:43) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.client.XmlRpcClient.sendMessage(XmlRpcClient.java:99) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.client.XmlRpcClient.sendMessage(XmlRpcClient.java:73) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.client.RpcClient.setChannelDatapointValues(RpcClient.java:206) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.client.RpcClient.setChannelDatapointValues(RpcClient.java:188) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.setChannelDatapointValues(AbstractHomematicGateway.java:477) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.loadChannelValues(AbstractHomematicGateway.java:458) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.handler.HomematicThingHandler.loadHomematicChannelValues(HomematicThingHandler.java:268) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.handler.HomematicThingHandler.updateChannelState(HomematicThingHandler.java:247) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.handler.HomematicThingHandler.updateDatapointState(HomematicThingHandler.java:226) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.handler.HomematicBridgeHandler.onStateUpdated(HomematicBridgeHandler.java:233) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.lambda$0(AbstractHomematicGateway.java:615) ~[249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.misc.DelayedExecuter.start(DelayedExecuter.java:61) [249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.eventReceived(AbstractHomematicGateway.java:612) [249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleEvent(RpcResponseHandler.java:94) [249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleMethodCall(RpcResponseHandler.java:47) [249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleMethodCall(RpcResponseHandler.java:64) [249:org.openhab.binding.homematic:2.2.0]
at org.openhab.binding.homematic.internal.communicator.server.XmlRpcServer$ResponseHandler.handle(XmlRpcServer.java:119) [249:org.openhab.binding.homematic:2.2.0]
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) [87:org.eclipse.jetty.server:9.3.22.v20171030]

Hat hier jemand einen Ansatz? Vielen Dank für eure Hilfe!
BG Kayzer

Re: HM-ES-TX-WM Communication Error

Verfasst: 2. Aug 2018 18:36
von Cyrelian
Hi Kayzer,

sieht so aus als wurde dein Binding nicht richtig "upgedated".

Code: Alles auswählen

249:org.openhab.binding.homematic:2.2.0
Schau mal bitte in der Karaf Console nach

Code: Alles auswählen

ssh -p 8101 openhab@localhost
und dort machst Du mal bitte ein:

Code: Alles auswählen

bundle:list
Das sollte dann das stehen:

Code: Alles auswählen

226 │ Active   │  80 │ 2.3.0                  │ Homematic Binding
CU
Cyrelian