Posts by rotala

  • Backend wieder down?

    Smarte Systeme sind nur smart wenn sie offen sind. Die aktuelle Performance von dem Team Innogy und Openhab ist ein Trauerspiel. Das hat schon mal über Monate gut funktioniert.

    2020-07-16 22:01:08.788 [WARN ] [internal.handler.InnogyBridgeHandler] - Error starting websocket. java.util.concurrent.ExecutionException: java.io.EOFException: HttpConnectionOverHTTP@c51fe6::DecryptedEndPoint@fb970e{api.services-smarthome.de/51.124.73.211:443<->/192.168.123.12:48784,OPEN,fill=-,flush=-,to=103/600000} at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) ~[?:1.8.0_201] at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895) ~[?:1.8.0_201] at org.openhab.binding.innogysmarthome.internal.InnogyWebSocket.start(InnogyWebSocket.java:84) ~[?:?] at org.openhab.binding.innogysmarthome.internal.handler.InnogyBridgeHandler.startWebsocket(InnogyBridgeHandler.java:272) ~[?:?] at org.openhab.binding.innogysmarthome.internal.handler.InnogyBridgeHandler.startClient(InnogyBridgeHandler.java:247) ~[?:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_201] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0_201] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_201] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0_201] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_201] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_201] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_201]

    java.util.concurrent.ExecutionException: org.eclipse.jetty.websocket.api.UpgradeException: Failed to upgrade to websocket: Unexpected HTTP Response Status Code: 503 Service Unavailable at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) ~[?:1.8.0_201] at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895) ~[?:1.8.0_201] at org.openhab.binding.innogysmarthome.internal.InnogyWebSocket.start(InnogyWebSocket.java:84) ~[?:?] at org.openhab.binding.innogysmarthome.internal.handler.InnogyBridgeHandler.startWebsocket(InnogyBridgeHandler.java:272) ~[?:?] at org.openhab.binding.innogysmarthome.internal.handler.InnogyBridgeHandler.startClient(InnogyBridgeHandler.java:247) ~[?:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_201] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0_201] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_201] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0_201] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_201] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_201] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_201]

  • openHab und innogy

    Quote from THellweg

    Können wir uns denn wenigstens darauf einigen, dass die Lösung dieses Problems v...

    Die Lösung gibt es schon. Die aktuelle Version läuft. Anwender müssen ein neues AUTH Token generieren. Wie beim Echo auch. Da wäre ein Hinweis von Seiten Livisi an die Anwender schon sinnvoll

  • openHab und innogy

    ich bekomme in OPENHAB immer noch Fehler

    grant type refresh_token to URL https://auth.services-smarthome.de/AUTH/token failed with HTTP response code 500

    Ich vermute da wird noch gebastelt...