Abode SocketIO Server Ping Timeout

My Abode integration keeps going offline and will not reconnect until I restart HA. Not sure where to go. Started after 0.112 and still happening even faster in 0.113.1,

Getting the following in the logs.

020-07-25 16:16:34 WARNING (SocketIOThread) [abodepy.socketio] Captured exception during SocketIO event callback: Expecting value: line 1 column 1 (char 0)
2020-07-25 16:16:34 WARNING (SocketIOThread) [abodepy.socketio] SocketIO Server Ping Timeout
2020-07-25 16:16:34 WARNING (SocketIOThread) [lomond] disconnecting websocket
2020-07-25 16:16:34 WARNING (SocketIOThread) [abodepy.socketio] Captured exception during SocketIO event callback: Expecting value: line 1 column 1 (char 0)
2020-07-25 16:16:34 WARNING (SocketIOThread) [abodepy.socketio] SocketIO Server Ping Timeout
2020-07-25 16:16:34 WARNING (SocketIOThread) [lomond] disconnecting websocket

Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/core.py”, line 1276, in catch_exceptions
await coro_or_task
File “/usr/src/homeassistant/homeassistant/core.py”, line 1295, in _execute_service
await handler.func(service_call)
File “/usr/src/homeassistant/homeassistant/helpers/entity_component.py”, line 209, in handle_service
self._platforms.values(), func, call, required_features
File “/usr/src/homeassistant/homeassistant/helpers/service.py”, line 454, in entity_service_call
future.result() # pop exception if have
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 595, in async_request_call
await coro
File “/usr/src/homeassistant/homeassistant/helpers/service.py”, line 485, in _handle_entity_call
await result
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 621, in async_turn_on
await self.hass.async_add_executor_job(ft.partial(self.turn_on, **kwargs))
File “/usr/local/lib/python3.7/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/homeassistant/homeassistant/components/abode/switch.py”, line 36, in turn_on
self._device.switch_on()
File “/usr/local/lib/python3.7/site-packages/abodepy/devices/switch.py”, line 12, in switch_on
success = self.set_status(CONST.STATUS_ON_INT)
File “/usr/local/lib/python3.7/site-packages/abodepy/devices/init.py”, line 40, in set_status
method=“put”, url=url, data=status_data)
File “/usr/local/lib/python3.7/site-packages/abodepy/init.py”, line 432, in send_request
return self.send_request(method, url, headers, data, True)
File “/usr/local/lib/python3.7/site-packages/abodepy/init.py”, line 410, in send_request
self.login()
File “/usr/local/lib/python3.7/site-packages/abodepy/init.py”, line 136, in login
oauth_token_object = json.loads(oauth_token.text)
File “/usr/local/lib/python3.7/json/init.py”, line 348, in loads
return _default_decoder.decode(s)
File “/usr/local/lib/python3.7/json/decoder.py”, line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File “/usr/local/lib/python3.7/json/decoder.py”, line 355, in raw_decode
raise JSONDecodeError(“Expecting value”, s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

I’m having the same issue. It started a few days ago. I also see:


Logger: abodepy.socketio
Source: /usr/local/lib/python3.8/site-packages/abodepy/socketio.py:180 
First occurred: July 25, 2020, 11:18:36 AM (1 occurrences) 
Last logged: July 25, 2020, 11:18:36 AM

SocketIO Error: "Not Authorized"

After rolling back to 0.112 the issue persisted. I’ve now rolled back to 0.111.4 and the connection has stabilized. Looks like something in the 0.112 version broke it.

I’m seeing the same issue on 0.111.3. It goes as long as 24 hours or so before it happens again sometimes.

I updated to 0.113.2 on Friday and last night it looks like the Abode connection became unavailable for a few minutes and then reconnected. The release notes for 0.113.2 don’t mention anything specific around it but I’m wondering if 0.113.2 may have resolved something with the SocketIO connection. I did notice that 0.113.3 is out now and the release notes mention support for Abode cameras so maybe that has a potential fix in it as well. I’m going to try updating to 0.113.3 later today. Wondering if anyone else who was experiencing this issue is still experiencing it after 0.113.2.

Was just told that the fix is in 0.113.3. I’ve deployed yesterday and it has been stable so far.