You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created a socketio server and tried to connect an esp32 to the server. On the server side, it is showing that it is connected but on the client side, on the esp32 by using the following code uri='http://192.168.56.1:5000' with usocketio.client.connect('http://127.0.0.1:5000/') as sio:
it shows an assertion error on line 123 of client.py File "usocketio/client.py", line 123 in connect Assertion Error
To test what was wrong, I added a print line before that line packet = socketio._recv() print("packet:",packet) ####### assert packet == (PACKET_NOOP, '')
which gives an output packet: (None,None)
I am new to websocket communication and event driven programming is best suited for my usage but I am unable to understand what the error is.
The text was updated successfully, but these errors were encountered:
It looks like you're possibly timing out before receiving a packet and it's not okay with that. I'm afraid you'll have to debug this on your own. If you want to try using more conventional web-driven programming, try the branch in this PR: #13
I created a socketio server and tried to connect an esp32 to the server. On the server side, it is showing that it is connected but on the client side, on the esp32 by using the following code
uri='http://192.168.56.1:5000' with usocketio.client.connect('http://127.0.0.1:5000/') as sio:
it shows an assertion error on line 123 of client.py
File "usocketio/client.py", line 123 in connect Assertion Error
To test what was wrong, I added a print line before that line
packet = socketio._recv() print("packet:",packet) ####### assert packet == (PACKET_NOOP, '')
which gives an output
packet: (None,None)
I am new to websocket communication and event driven programming is best suited for my usage but I am unable to understand what the error is.
The text was updated successfully, but these errors were encountered: