After updating my Cerbo GX from v3.67 to v3.80, the Cerbo no longer connects to my WiFi network, and Bluetooth has stopped working.
Setup
Cerbo GX connected via WiFi (2.4 GHz) to a GL.iNet router
This setup had been running reliably for months on v3.67
What happened
During the update reboot, the Cerbo disassociated from the router. The router log confirms this, and it shows no reconnection attempt from the Cerbo since then.
The Cerbo’s WiFi scan first showed two foreign networks, but not mine. After a restart, it only showed its own access point.
After another restart, neither the access point nor Bluetooth was available. After a further restart the own access point came back, but Bluetooth still does not connect.
I rolled back to v3.67 using the backup firmware. No change: the Cerbo’s own access point works, but Bluetooth does not connect and the WiFi scan does not find my router.
Other 2.4 GHz devices (ESP32 etc.) connect to the same router without any problems, so the router side looks fine.
Questions
Is this a known issue with v3.80?
Is a full power cycle needed to reset the WiFi/Bluetooth chip?
Is there anything I should check via SSH (e.g. dmesg, connmanctl, hciconfig) to help narrow this down?
Have you tried to reboot your router? This can sometimes be the source of an issue.
Certainly no similar reports yet, it could be a coincidence (happens more often than you think).
Yes, I restarted the router, although to be honest I don’t understand why that should make a difference: all the other Wi-Fi devices on the same network (ESP32s, cameras, phones, laptops) worked without any problems the whole time. The only thing that changed was the Cerbo’s firmware. So I’d expect the cause to be on the Cerbo’s side.
A cold restart of the Cerbo (with the power disconnected for 30 seconds) didn’t help either.
In the end, this is what fixed it: I manually set the router’s 2.4 GHz Wi-Fi to channel 1. Immediately afterwards, the Cerbo found my network again and connected. M
I’m still convinced that something changed on the Cerbo with the update, because nothing was changed on the router. The sequence was simply:
Cerbo running stably on the router for months with v3.67
Firmware update to v3.80 with the automatic restart
From that moment on, the Cerbo could no longer see my network
The router log confirms this: the Cerbo disconnected when it restarted after the update and didn’t make a single connection attempt afterwards.
What I find interesting is that rolling back to v3.67 didn’t fix the problem. That makes me suspect that v3.80 changed a setting that was stored persistently and survives a rollback, for example the Wi-Fi country setting or the list of permitted channels. That would also explain why the Cerbo could only see my network again after I switched to channel 1.