(2024-01-31, 02:30 PM)Sailoog Wrote: If I am not wrong mpstat is used only by signalk-rpi-monitor plugin: https://github.com/sberl/signalk-rpi-monitor
Could the wifi problem be a 2.4GHz / 5GHz issue?
I checked and found the setting on Auto. It is now fixed to B/G 2.4GHz with no metered connection. For good measures I rebooted and verified the new settings. Still no change on the SensESP device connections.
(2024-01-31, 02:15 PM)Boatingbaileys Wrote: If you monitor the console output on the ESP with a USB connected, what does It say? does it get an IP and can't find the Server or report any other issues? You could try a couple of things, change the OP4 IP address back to the OP3 network range or revoke the security access and make it request it again. Thats i think where I would start.
Just to confirm your Hotspot is set up in 2.4Ghz band?
I won't have access to the ESP32 console until I get back to the boat. I do have vnc and can ssh directly. As noted in my last reply, my hotspot was set to AUTO, but I fixed it to 2.4GHz. I was hoping this was the cause of the problems, but no fix even after a few reboots.
It will be a week or so before I get back to the boat. I am developing a new SenseESP device which I'll test at home. I have a second SenseESP device on the boat, but I have yet to reflash it and so it is still trying to connect to the old OP3 server (openplotter wifi on 10.10.10.1). I have not ruled out a bad ESP32 dev board as I had one of these fail previously.
Thanks for all insights.