Homematic ip Bridge geht offline ohne ersichtlichen

Einrichtung der openHAB Umgebung und allgemeine Konfigurationsthemen.

Moderatoren: seppy, udo1toni

Antworten
AndyRPi
Beiträge: 68
Registriert: 3. Jan 2021 11:06
Answers: 0
Wohnort: Wörlitz / Obertshausen

Homematic ip Bridge geht offline ohne ersichtlichen

Beitrag von AndyRPi »

Seit heute morgen geht die Bridge für die ccu3 nach 20 Minuten offline. In den Logs ist nichts zu finden. Ich habe schon alles neu gestartet. Ich verstehe es nicht bis gestern lief alles ohne Probleme und ich habe nichts verändert.
folgende Fehlermeldung steht im LOG

Code: Alles auswählen

2023-02-12 17:37:35.711 [WARN ] [ommunicator.AbstractHomematicGateway] - Connection lost on gateway '3014F711A0001F9BE9A3C867', cause: "IOException java.util.concurrent.TimeoutException"
2023-02-12 18:43:00.594 [WARN ] [ternal.handler.HomematicThingHandler] - Could not reinitialize the device '000A9F298FD5B9': java.util.concurrent.TimeoutException java.io.IOException: java.util.concurrent.TimeoutException
	at org.openhab.binding.homematic.internal.communicator.client.XmlRpcClient.send(XmlRpcClient.java:121) ~[?:?]
	at org.openhab.binding.homematic.internal.communicator.client.XmlRpcClient.sendMessage(XmlRpcClient.java:73) ~[?:?]
	at org.openhab.binding.homematic.internal.communicator.client.RpcClient.setChannelDatapointValues(RpcClient.java:244) ~[?:?]
	at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.setChannelDatapointValues(AbstractHomematicGateway.java:522) ~[?:?]
	at org.openhab.binding.homematic.internal.communicator.CcuGateway.setChannelDatapointValues(CcuGateway.java:109) ~[?:?]
	at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.loadChannelValues(AbstractHomematicGateway.java:492) ~[?:?]
	at org.openhab.binding.homematic.internal.handler.HomematicThingHandler.loadHomematicChannelValues(HomematicThingHandler.java:485) ~[?:?]
	at org.openhab.binding.homematic.internal.handler.HomematicThingHandler.updateStatus(HomematicThingHandler.java:503) ~[?:?]
	at org.openhab.binding.homematic.internal.handler.HomematicThingHandler.deviceLoaded(HomematicThingHandler.java:669) ~[?:?]
	at org.openhab.binding.homematic.internal.handler.HomematicBridgeHandler.onDeviceLoaded(HomematicBridgeHandler.java:339) ~[?:?]
	at org.openhab.binding.homematic.internal.handler.HomematicBridgeHandler.onNewDevice(HomematicBridgeHandler.java:301) ~[?:?]
	at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.newDevices(AbstractHomematicGateway.java:771) ~[?:?]
	at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleNewDevice(RpcResponseHandler.java:108) ~[?:?]
	at org.openhab.binding.homematic.internal.communicator.server.RpcResponseHandler.handleMethodCall(RpcResponseHandler.java:57) ~[?:?]
	at org.openhab.binding.homematic.internal.communicator.server.XmlRpcServer$ResponseHandler.handle(XmlRpcServer.java:125) ~[?:?]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) ~[bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.server.Server.handle(Server.java:516) ~[bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487) ~[bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732) [bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479) [bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277) [bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) [bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105) [bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104) [bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338) [bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315) [bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173) [bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131) [bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409) [bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883) [bundleFile:9.4.46.v20220331]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034) [bundleFile:9.4.46.v20220331]
	at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: java.util.concurrent.TimeoutException
	at org.eclipse.jetty.client.util.FutureResponseListener.get(FutureResponseListener.java:109) ~[?:?]
	at org.openhab.binding.homematic.internal.communicator.client.XmlRpcClient.send(XmlRpcClient.java:111) ~[?:?]
	... 31 more
Gesendet von iPhone mit Tapatalk
Openhab 4.0.0 RPi SSD
Homematic CCU3
Phoscon
Shelly
FRITZ!Box
Alexa

bodo@riepl.eu
Beiträge: 1
Registriert: 30. Nov 2019 01:04
Answers: 0

Re: Homematic ip Bridge geht offline ohne ersichtlichen

Beitrag von bodo@riepl.eu »

did you resolve the issue?

same on my installatoin, oh4.1.0#3760 with CCU3. Tried many thingd, cleaned cache and tmp on OH, moved CCU to another switchport, changed timeouts on binding ... no success so far

Antworten