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.
Reverted to 3.55 official and it is back.
Hi Rick.
Odd i have just checked both of my systems and i can see all of mine on 3.60~66.
I guess you have tried rebooting you’re Cerbo GX?
Yes, just rebooted 3.60~66, no Ruuvi.
I think the grayed out continuous scanning toggle is a clue.
Is yours grayed out as well?
I’m going to bring it inside next to the Cerbo GX (mk 1) and see if that makes a difference.
1 Like
No change with the Ruuvi 3 feet away.
Also tried Disabling and Enabling the Bluetooth sensors, no change.
Yes, that looks good. I’ve only got one device.
Are you on a Cerbo GX mk1 or mk2 or something else?
They may have a regression on the mk1.
Or maybe it’s just me 
Thanks for checking.
1 Like
No worries sorry i can’t help maybe someone else might report the same issue.
1 Like
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 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.
So I guess it is possible that it is running hotter on 3.60~65 due to the kernel upgrade? maybe?
I’ll order an external BLE USB adapter, no problem.
Thanks Matthijs
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/ruuvi_e86f7f3423d8/Enabled 1
Settings/Devices/ruuvi_e86f7f3423d8/TemperatureType 4
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.
1 Like
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 
.
I hope, and expect, that all will work well with a simple external usb-bluetooth adapter.
2 Likes
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.
3 Likes
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.
2 Likes
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.
Well, then it wasn’t just me, sorry to hear that.
Clearly, Victron recommends a USB Bluetooth dongle for these older devices.
The UB500 was $9.99 on Amazon in USA, a negligible cost for better performance.
In use my other USB ports and don’t want to add a hub and a dongle. Was working fine in 3.55 and all beta up till now. Something else is wrong.
If you have an older Cerbo the internal board/ processor gets too hot and Bluetooth shuts down. As the firmware size and complexity increases the cpu load increases and the internal temperature rises. If you have the older device then it is inevitable that at some point this problem will occur as firmware develops and the answer is proven.
I have a simple Y splitter USB cable for my TP Link UB400 dongle because the other device is a GPS so both very low power.
As above, Devices manufactured before serial number HQ2208 are affected