sailingYOLO - I often (many times a week) get:...
I often (many times a week) get:
E (32728208) WEBSOCKET_CLIENT: Websocket client is not connected
In the serial output.
.Signal K server is up, running and working just fine.
.I can browse to the ESP's web-page, and the status states "Connected" to the SignalK server.
.But the ESP is not sending or receiving any data to/from the SignalK server.
.When rebooting the ESP everything works great again.
No difference if I have the power connected from the PC or a dedicated power source.
Any clues what the problem might be?2 Replies
Maybe WiFi connection dropped for a moment?
I’ve noticed myself that SensESP keeps trying to connect during startup until it succeeds. But if the connection breaks it will not get noticed in the running code (v2.7). I know because I’m making a tank monitor with display and tried to show an icon for the connection. Working fine but connection loss will not be noticed. Because I understand that development shifted to v3 I’m trying to amend my code atm (not much luck yet).
Thanks for your input. I'm using version 3.
It looks like a bug, when the message "websocket client is not connected" is rolling in the serial output I can still access the ESP:s web UI, so the ESP has a working connection at that time, but the SensESP does not recognize that the network is up (again? probably after a short down time).
The web UI even tells me that it indeed have connection to the SignakK server.
Where and how to report this bug please?