05-01-2017, 10:31:22
(04-01-2017, 00:35:22)timdeluxe schrieb: ... nun habe ich wie hier schon mehrfach gemeldet ebenfalls das Websocket Problem, welches sich aber nach dem reinitialisieren nach zwei Minuten von selber löst:
Code:2017-01-03 23:21:42.565 [DEBUG] [marthome.handler.InnogyDeviceHandler] - handleCommand called for channel 'innogysmarthome:PSS:SMARTHOME09:37a7620b8c89433d8bd15ac4739449cb:switch' of type 'PSS' with command 'ON'
2017-01-03 23:21:42.567 [DEBUG] [home.internal.DeviceStructureManager] - getDeviceById 37a7620b8c89433d8bd15ac4739449cb:true
2017-01-03 23:21:43.043 [ERROR] [marthome.handler.InnogyBridgeHandler] - Unexcepted API error: Session not found
2017-01-03 23:21:43.050 [DEBUG] [marthome.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR): Session not found
2017-01-03 23:21:43.052 [DEBUG] [marthome.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:PSS:SMARTHOME09:45291127821640e581cc74dac44942be bridge status OFFLINE
2017-01-03 23:21:43.057 [DEBUG] [marthome.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR): Session not found
2017-01-03 23:21:43.058 [DEBUG] [marthome.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:WDS:SMARTHOME09:56d318accade4790851f3fe4806ab8ef bridge status OFFLINE
2017-01-03 23:21:43.061 [DEBUG] [marthome.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR): Session not found
2017-01-03 23:21:43.062 [DEBUG] [marthome.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR): Session not found
2017-01-03 23:21:43.063 [DEBUG] [marthome.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR): Session not found
2017-01-03 23:21:43.063 [DEBUG] [marthome.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:WDS:SMARTHOME09:3a3239e205f245e0a3092559a262a1b2 bridge status OFFLINE
2017-01-03 23:21:43.064 [DEBUG] [marthome.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:PSS:SMARTHOME09:37a7620b8c89433d8bd15ac4739449cb bridge status OFFLINE
2017-01-03 23:21:43.064 [DEBUG] [marthome.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:WDS:SMARTHOME09:87300a2f9d51439a947874335763a835 bridge status OFFLINE
2017-01-03 23:21:43.068 [DEBUG] [marthome.handler.InnogyBridgeHandler] - Disposing innogy SmartHome bridge handler 'SMARTHOME09'
2017-01-03 23:21:43.075 [INFO ] [gysmarthome.internal.InnogyWebSocket] - Stopping innogy WebSocket...
2017-01-03 23:21:43.076 [DEBUG] [gysmarthome.internal.InnogyWebSocket] - Closing session...
2017-01-03 23:21:43.135 [INFO ] [gysmarthome.internal.InnogyWebSocket] - Connection to innogy WebSocket was closed (code: 1006). Reason: WebSocket Read EOF
2017-01-03 23:21:43.136 [DEBUG] [marthome.handler.InnogyBridgeHandler] - onEventRunnerStopped called
2017-01-03 23:21:43.137 [INFO ] [marthome.handler.InnogyBridgeHandler] - Starting innogy web socket.
2017-01-03 23:21:43.138 [DEBUG] [marthome.handler.InnogyBridgeHandler] - WebSocket URL: wss://api.services-smarthome.de/API/1.0/events?token=eyJ0eXAiOiJKV1QiL...m_USsnDB-Q
2017-01-03 23:21:43.201 [INFO ] [gysmarthome.internal.InnogyWebSocket] - Connecting to innogy WebSocket...
2017-01-03 23:21:43.465 [INFO ] [marthome.handler.InnogyBridgeHandler] - innogy SmartHome bridge handler shut down.
2017-01-03 23:21:43.466 [INFO ] [marthome.handler.InnogyBridgeHandler] - Scheduling reinitialize in 120 seconds.
2017-01-03 23:21:43.478 [INFO ] [gysmarthome.internal.InnogyWebSocket] - Connected to innogy WebSocket.
2017-01-03 23:23:43.467 [DEBUG] [marthome.handler.InnogyBridgeHandler] - Initializing innogy SmartHome BridgeHandler...
2017-01-03 23:23:43.469 [DEBUG] [marthome.handler.InnogyBridgeHandler] - Config [clientId=24635748, clientSecret=no secret, authCode=, accessToken=eyJ0eXAiOi...m_USsnDB-Q, refreshToken=f7b87...68ebc]
2017-01-03 23:23:43.477 [INFO ] [marthome.handler.InnogyBridgeHandler] - Initializing innogy SmartHome client...
2017-01-03 23:23:44.734 [DEBUG] [home.internal.DeviceStructureManager] - Starting device structure manager.
Interessanterweise passiert das alles nur wenn ich aktiv ein Gerät schalte, nicht von selber (sprich erst dann merkt es den verlorenen Websocket). Ich habe noch keine Regeln und keine Zeitsteuerungen mit den Innogy Geräten, daher kann ich das relativ genau sehen.
Den Session not found error hatte ich neulich auch. Und zwar nicht nur über openHAB, sondern auch die innogy-App hakte und wenn ich die Schnittstelle mit Postman direkt angesprochen habe, gab es den Fehler auch. Es war also ein Problem bei innogy.