I upgraded from Version 3.60~85 to version 3.70~2, and the Bluetooth of the Cerbo did not re-establish itself. So, all my Ruuvies and Mopeka sensors are currently not displayed and hence not visible. Normally, it takes some time to re-establish the connection with all the sensors, but in this version, it started up and then dropped out. It did this a couple of times, and now no more Bluetooth connectivity.
The last OS version I used that appeared to be stable was version 3.60~85, so I reverted to that version. However, that did not restore the Bluetooth network. Does anyone have any suggestions on what to do next? Go back to the stable version of 3.60?
My version of the Cerbo dates back to 2020 (I believe); the serial number is HQ2084V17V3. I have now rebooted Cerbo multiple times; the latest reboot to version 3.62-1 brought back the Ruuvi tags for about 3 minutes, and then they disappeared again.
I have ordered the MK2 version of the Cerbo and an external USB Bluetooth dongle from TP-Link. I am sure that the internal Bluetooth is still working, as evidenced by the temporary display of the sensors after reboot. I suspect that there is a software issue in the firmware.
I will install the official stable version of 3.60 (without modifications) and see if that makes the Ruuvi sensors visible again.
Your issue is that you have a Cerbo GX with not reliable working Bluetooth radio module.
From the manual:
Note for Cerbo GX units built up to and including serial number HQ2207; The built-in Bluetooth connection is disabled when the internal CPU temperature exceeds 53 degrees C (influenced by load and/or ambient temperature). For reliable operation it is necessary to use a USB Bluetooth adapter. Devices manufactured later (HQ2208 and later) do not require an additional USB Bluetooth adapter.
Various people reported success by installing the TP Link UB500. I use the older UB400, now superseded.
Pwfarnell, perhaps it is dependent on temperature. The temperature has dropped a bit here (I am currently about 100km North-West of Toronto, Ontario, Canada), but the ambient temperature in the trailer is still around 26 °C. The Cerbo is installed under the bed, and last year during a long trip to Newfoundland and other maritime Provinces in Canada, the ambient temperature was significantly higher than 26 °C (I recorded some days with temps > 35 °C), and the Bluetooth of the Cerbo did not drop out. The Cerbo had at that time I think Version 3.50. If the newer firmware demands more from the CPU (more dissipation?), I can see that the internal temperature of the Cerbo can go beyond 53 °C.
The next couple of days it is going to be very warm here (a heatwave is forecasted), and I will wait and see if the Bluetooth drops out. For now, all appears to be working.
If the Bluetooth drops out, I will put a fan on the Cerbo in an attempt to cool it down. If that makes the Bluetooth enable again, we will have proof of the temperature cause.
22 June 2025 → Note: It appears that the internal Bluetooth chip gave up the ghost this past week. I tried many software versions, and sometimes the Bluetooth enabled, worked for an hour or so and then dropped out. I installed an TP-Link UB500 Plus USB Bluetooth adaptor and now all devices came back and it appears to be stable.