openHAB 2 innogy SmartHome binding (ALPHA)

[ollie]

Hallo Ollie,

er hat gestern nach knapp 6 Stunden das Websocket geschlossen und nicht wieder aufgebaut. Hier der Auszug vom Coding. Hilft dir das? Hast du hierzu eine Idee?

Code:

...
2016-12-20 14:03:38.375 [DEBUG] [gysmarthome.internal.InnogyWebSocket] - innogy WebSocket onMessage() - [{"type":"/event/Disconnect","timestamp":"2016-12-20T13:02:36.0353634Z","desc":"/desc/event/Disconnect","Properties":[{"name":"Reason","value":"SessionExpired"}]}]
2016-12-20 14:03:38.376 [DEBUG] [marthome.handler.InnogyBridgeHandler] - onEvent called. Msg: [{"type":"/event/Disconnect","timestamp":"2016-12-20T13:02:36.0353634Z","desc":"/desc/event/Disconnect","Properties":[{"name":"Reason","value":"SessionExpired"}]}]
2016-12-20 14:03:38.396 [DEBUG] [marthome.handler.InnogyBridgeHandler] - Event found: Type:/event/Disconnect Capability:(no link)
2016-12-20 14:03:38.398 [INFO ] [marthome.handler.InnogyBridgeHandler] - Websocket disconnected. Reason: SessionExpired
2016-12-20 14:03:38.399 [DEBUG] [marthome.handler.InnogyBridgeHandler] - onEventRunnerStopped called
2016-12-20 14:03:38.401 [INFO ] [marthome.handler.InnogyBridgeHandler] - Starting innogy web socket.
2016-12-20 14:03:38.404 [DEBUG] [marthome.handler.InnogyBridgeHandler] - WebSocket URL: wss://api.services-smarthome.de/API/1.0/events?token=eyJ0eXAiOiJKV1QiL...XoU3rgjXjQ
2016-12-20 14:03:38.409 [INFO ] [gysmarthome.internal.InnogyWebSocket] - Stopping innogy WebSocket...
2016-12-20 14:03:38.411 [DEBUG] [gysmarthome.internal.InnogyWebSocket] - Closing session...
2016-12-20 14:03:38.601 [INFO ] [gysmarthome.internal.InnogyWebSocket] - Connecting to innogy WebSocket...
2016-12-20 14:03:43.544 [INFO ] [gysmarthome.internal.InnogyWebSocket] - Connected to innogy WebSocket.
2016-12-20 14:03:43.563 [INFO ] [gysmarthome.internal.InnogyWebSocket] - Connection to innogy WebSocket was closed normally.
2016-12-20 14:04:02.635 [INFO ] [gysmarthome.internal.InnogyWebSocket] - Connection to innogy WebSocket was closed normally.

Hmm. Grundsätzlich ist das Verhalten richtig, dass bei einem SessionExpired der WebSocket neu verbunden wird. Allerdings wird anscheinend der neue auch direkt geschlossen. Sehr merkwürdig. Kann ich aktuell noch nicht richtig einordnen.