search

MisterWil / abodepy

A thin Python wrapper for the Abode alarm API
MIT License
50 stars 17 forks source link

HASSIO Status Unavailable - SocketIO Exception: Expecting value: line 1 column 1 (char 0) #75

Closed FreeWillyB closed 4 years ago

FreeWillyB commented 4 years ago

The past week or so (sorry that I don't have more details on when exactly) I noticed that my Home Assistant was showing Abode as unavailable. I restarted the HA server and Abode came back. It happened again a day or so later, so I went ahead and updated to 113.1. It appears to fix it for a bit, but the same thing has happened again today. I have looked at the logs, but this is all I really found. I'm not sure if there are any other logs with more detail by default, but I'm going to try to increase the logging level to see if i can get some debug info for you.

2020-07-31 18:02:20 WARNING (SocketIOThread) [abodepy.socketio] Captured exception during SocketIO event callback: Expecting value: line 1 column 1 (char 0) 2020-07-31 18:02:20 WARNING (SocketIOThread) [abodepy.socketio] SocketIO Server Ping Timeout 2020-07-31 18:03:26 WARNING (SocketIOThread) [abodepy.socketio] Captured exception during SocketIO event callback: Expecting value: line 1 column 1 (char 0) 2020-07-31 18:04:26 WARNING (SocketIOThread) [abodepy.socketio] Captured exception during SocketIO event callback: Expecting value: line 1 column 1 (char 0) 2020-07-31 18:04:26 WARNING (SocketIOThread) [abodepy.socketio] SocketIO Server Ping Timeout 2020-07-31 18:05:26 WARNING (SocketIOThread) [abodepy.socketio] Captured exception during SocketIO event callback: Expecting value: line 1 column 1 (char 0) 2020-07-31 18:05:26 WARNING (SocketIOThread) [abodepy.socketio] SocketIO Server Ping Timeout 2020-07-31 18:05:32 WARNING (SocketIOThread) [abodepy.socketio] Captured exception during SocketIO event callback: Expecting value: line 1 column 1 (char 0)

MisterWil commented 4 years ago

https://github.com/home-assistant/core/issues/38136

Should be fixed in 0.113.3

On Sat, Aug 1, 2020 at 7:36 PM FreeWillyB notifications@github.com wrote:

The past week or so (sorry that I don't have more details on when exactly) I noticed that my Home Assistant was showing Abode as unavailable. I restarted the HA server and Abode came back. It happened again a day or so later, so I went ahead and updated to 113.1. It appears to fix it for a bit, but the same thing has happened again today. I have looked at the logs, but this is all I really found. I'm not sure if there are any other logs with more detail by default, but I'm going to try to increase the logging level to see if i can get some debug info for you.

2020-07-31 18:02:20 WARNING (SocketIOThread) [abodepy.socketio] Captured exception during SocketIO event callback: Expecting value: line 1 column 1 (char 0) 2020-07-31 18:02:20 WARNING (SocketIOThread) [abodepy.socketio] SocketIO Server Ping Timeout 2020-07-31 18:03:26 WARNING (SocketIOThread) [abodepy.socketio] Captured exception during SocketIO event callback: Expecting value: line 1 column 1 (char 0) 2020-07-31 18:04:26 WARNING (SocketIOThread) [abodepy.socketio] Captured exception during SocketIO event callback: Expecting value: line 1 column 1 (char 0) 2020-07-31 18:04:26 WARNING (SocketIOThread) [abodepy.socketio] SocketIO Server Ping Timeout 2020-07-31 18:05:26 WARNING (SocketIOThread) [abodepy.socketio] Captured exception during SocketIO event callback: Expecting value: line 1 column 1 (char 0) 2020-07-31 18:05:26 WARNING (SocketIOThread) [abodepy.socketio] SocketIO Server Ping Timeout 2020-07-31 18:05:32 WARNING (SocketIOThread) [abodepy.socketio] Captured exception during SocketIO event callback: Expecting value: line 1 column 1 (char 0)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/MisterWil/abodepy/issues/75, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIKRHNTSTEKWN3DTFC5IEDR6TGJFANCNFSM4PSIE6SA .

FreeWillyB commented 4 years ago

Awesome! Just curious, but what was the issue causing it?

MisterWil commented 4 years ago

When abodes servers are acting up it seems like sometimes the websocket connection will reconnect first before the api starts working again. When the web socket connects it first tries to update all devices and then does a callback to anything listening for the reconnect. The devices in home assistant would set themselves back to being available using this after connect callback. But, if the api call failed, the callback would never happen and thus the devices would never become available again.

On Sat, Aug 1, 2020 at 7:56 PM FreeWillyB notifications@github.com wrote:

Awesome! Just curious, but what was the issue causing it?

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/MisterWil/abodepy/issues/75#issuecomment-667617498, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIKRHMXMYFGYZJWBQWFSKTR6TIUXANCNFSM4PSIE6SA .