Occasionally, but not always, on connection to the Abode SocketIO server a packet is received:
b'2:401:3'
This packet results in a stack trace from the socketIO_client:
ValueError: invalid literal for int() with base 10: '2:401'
This is due to a minor logic bug in socketIO_client/parsers.py where in _read_packet_length() the logic needs to be that packet_length_string starts at the start index and not 0:
I believe I resolved this by correctly referencing the socketio_client3 version 0.8.0 -- or, at least, I can't recreate this particular issue any longer.
Occasionally, but not always, on connection to the Abode SocketIO server a packet is received:
b'2:401:3'
This packet results in a stack trace from the socketIO_client:
ValueError: invalid literal for int() with base 10: '2:401'
This is due to a minor logic bug in socketIO_client/parsers.py where in _read_packet_length() the logic needs to be that packet_length_string starts at the start index and not 0:
However, when the bug is fixed the socketIO_client seems to get stuck in some sort of reconnect loop. Further debugging is required.