IP Symcon warten auf Pong fehlgeschlagen

Programmierung der HomeMatic CCU mittels IP-Symcon

Moderator: Co-Administratoren

Antworten
Heiko77
Beiträge: 1
Registriert: 18.11.2023, 11:13
System: CCU

IP Symcon warten auf Pong fehlgeschlagen

Beitrag von Heiko77 » 18.11.2023, 11:34

Hallo zusammen
Ich habe eine CCU3 (3.71.12) in Verbindung mit IP-Symcon (6.4) auf Windows 10.
Bisher hat die Verbindung auch ohne Problem funktioniert.
Seit Mittwoch kommt auf Symcon der Fehler
HomeMatic Socket (KeepAlive): Warten auf "Pong" von HomeMatic IP fehlgeschlagen.
Der Fehler tritt etwas alle 5 Minuten auf.
Parallel kommt auf der CCU3 folgendes:

Code: Alles auswählen

2023-11-18 11:23:07,079 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: 0 Accesspoints in Queue 
2023-11-18 11:23:07,080 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
2023-11-18 11:23:07,081 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used 
2023-11-18 11:23:45,144 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url:  
2023-11-18 11:23:45,147 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [IPS-192.168.188.20_WorkerPool-0] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
2023-11-18 11:23:45,150 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [IPS-192.168.188.20_WorkerPool-0] init finished 
2023-11-18 11:23:45,151 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-0] Added InterfaceId: IPS-192.168.188.20 
2023-11-18 11:23:45,153 io.vertx.core.impl.ContextImpl ERROR [vert.x-worker-thread-0] Unhandled exception 
java.lang.IllegalArgumentException: Expected authority at index 7: http://
	at java.net.URI.create(URI.java:852) ~[?:1.8.0_202]
	at org.apache.http.client.methods.HttpPost.<init>(HttpPost.java:76) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.communication.rpc.internal.transport.http.HttpTransport.sendRequest(HttpTransport.java:104) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.sendRequest(RpcClient.java:94) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.RpcClient.invoke(RpcClient.java:82) ~[HMIPServer.jar:?]
	at com.sun.proxy.$Proxy39.listDevices(Unknown Source) ~[?:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendClient.listDevices(LegacyBackendClient.java:139) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.synchronizedBackendDevices(DeviceUtil.java:161) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.handle(InterfaceInitializer.java:112) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer.handle(InterfaceInitializer.java:26) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:100) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.WorkerContext.lambda$emit$0(WorkerContext.java:59) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.WorkerContext.lambda$execute$2(WorkerContext.java:104) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76) ~[HMIPServer.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_202]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_202]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[HMIPServer.jar:?]
	at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_202]
Caused by: java.net.URISyntaxException: Expected authority at index 7: http://
	at java.net.URI$Parser.fail(URI.java:2848) ~[?:1.8.0_202]
	at java.net.URI$Parser.failExpecting(URI.java:2854) ~[?:1.8.0_202]
	at java.net.URI$Parser.parseHierarchical(URI.java:3102) ~[?:1.8.0_202]
	at java.net.URI$Parser.parse(URI.java:3053) ~[?:1.8.0_202]
	at java.net.URI.<init>(URI.java:588) ~[?:1.8.0_202]
	at java.net.URI.create(URI.java:850) ~[?:1.8.0_202]
	... 17 more
2023-11-18 11:23:45,180 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-3] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.188.20:5544 
2023-11-18 11:23:45,183 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [IPS-192.168.188.20_WorkerPool-1] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
2023-11-18 11:23:45,185 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [IPS-192.168.188.20_WorkerPool-1] init finished 
2023-11-18 11:23:45,186 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-2] Added InterfaceId: IPS-192.168.188.20 
2023-11-18 11:23:45,252 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-2] updateDevicesForClient IPS-192.168.188.20 -> 65 device addresses will be added 
Unter 192.168.188.20 läuft Symcon.
Auch mehrfache Neustarts beider Systeme haben nix gebracht.
Wäre echt prima, wenn mir jemand helfen könnte.
Viele Grüße
Heiko

Antworten

Zurück zu „IP-Symcon“