I tried to upgrade to OH 3.1.0 M4 and tried also 3.1.0 snapshot. In both environments the innogy binding does not connect at all. The binding connects with release 3.0.2, although it often gets disconnected in the night, followed by a timeout. It does not automatically reconnect without a restart of OH, but at least it’s running. Can I deliver logs? I can upgrade again and send you any logs for a further analysis of the problem, if this helps
BTW: if someone has an idea, why the binding goes offline in the release build, it is highly appreciated. I have installed the certificates as documented and followed all the instructions written in this forum. Without success. Interesting is, that the deconz binding goes offline as well, but this is reconnecting.
yes, problem is still present in 3.1.0-M5. 3.1.0-M3 still working
2021-06-03 17:03:51.916 [WARN ] [internal.handler.InnogyBridgeHandler] - Error starting websocket.
java.util.concurrent.ExecutionException: org.eclipse.jetty.websocket.api.UpgradeException: Failed to upgrade to websocket: Unexpected HTTP Response Status Code: 404 Site Not Found
I’m on the latest milestone (M5). Since there seems to be no quick solution in sight, is there a way how to go back to M3 via openhabian? If not, what would be a “manual” approach to “downgrade” to M3?
I can’t help you on openhabian.
I changed some months back to docker. This has saved me so much time since then. Not only for Openhab but also other applications. So just my feedback to maybe rethink the deployment strategy. Testing M4 and M5 builds and switching between them is a matter of changing a 3 to a 5, redeploy the container, see that it still gives the 404 error, then change 5 to 3 and redeploy. Very easy, little risk. Fantastic technology. I even changed from a raspberry to a amd64 platform. without huge reinstalls.
