3.60~65 has made my RuuviTag disappear, and the continuous scanning toggle is stuck (note the gray in the toggle). Was on 3.60~59 with working sensor. 3.60~66 is also not working. [Screenshot 2025-04-26 at 10.42.13 AM] Reverted to 3.55 official and it is back. [Screenshot 2025-04-26 at 10.52.…

I’m totally fine with an external USB Bluetooth adapter. On the plus side, I can move it to a better location for reception above my rack. Have one coming tomorrow that @nesswill used successfully for his 36 sensors (!), as documented in another thread. Fully expecting it to work.

It a Cerbo GX Mk2 [Screenshot_20250426_165408_Edge]

They may have a regression on the mk1. Or maybe it’s just me :grinning_face: Thanks for checking.

No worries sorry i can’t help maybe someone else might report the same issue.

Hi! Thanks for the report! What serial number and model of Cerbo? Using built-in bluetooth or usb ble adapter? Are you aware of the limitations of earlier production? (See manual).

Cerbo GX mk1 HQ2202G493A Built-In bluetooth The limitation I’m aware of in 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 te…

Weirdly, dbus-spy shows the following ruuvi tag entries, even though it does not show up in devices. Settings/Devices/ruuvi_e86f7f3423d8/ClassAndVrmInstance temperature:20 Settings/Devices/ruuvi_e86f7f3423d8/CustomName Outside Temperature Settings/Devices/…

Just loaded v3.60~66, I have one of the affected Cerbo mk1 from 2020 with an external Bluetooth dongle and that is picking up my single Ruuvi and 2 Mopeka level sensors OK.

Hi @ricardocello , strange indeed. But regardless: any Cerbo with a serial number prior to that date, we’re doing zero investigation. The amount of hours that went into that issue is already well beyond what is reasonable :sweat_smile:. I hope, and expect, that all will work well with a simple ext…

Confirmed! I plugged in a TP-LINK UB500 and 30 seconds later the Ruuvi tag was connected. Now that is plug and play! Also, the Cerbo GX also wasn’t available through Bluetooth on VictronConnect with the built-in Bluetooth. I just didn’t notice, as it is also on my LAN.

My Bluetooth stopped working with 65 and 66 ending firmware. Reverted to 3.55 and Bluetooth is back working. I don’t want to add a usb dongle. It has been under 19c in the location of the Cerbo.

Bluetooth Loss and Ruuvi Tag Missing v3.60~65 onwards

Beta testing Venus OS beta testing

Topic		Replies	Views
Cerbo GX Firmware 3.60 Ruuvi Sensors DIY marine , diy , gx_device , cerbo_gx	29	1339	25 June 2025
Ruuvi Tags only seen right after powering the cerbo back up DIY diy , ruuvi_sensors , cerbo_gx	13	174	1 May 2026
Cerbo GX serial no. HQ2207 or earlier - updated UI 3.50 bluetooth functions for Ruuvi New UI marine , diy , 350-new-ui , gx_device , cerbo_gx	35	1550	27 June 2025
Cerbo GX MK1 no bluetooth DIY beginner , temperature_sensor , cerbo_gx	2	143	11 September 2025
Cerbo GX bluetooth not working DIY victronconnect , diy , gx_device , cerbo_gx	8	976	4 August 2025

Bluetooth Loss and Ruuvi Tag Missing v3.60~65 onwards

Related topics