I recently upgraded to Cerbo GX firmware 3.60 and all my Ruuvi sensors disappeared. The only way to get them back was to revert to firmware 3.55. I did notice that my USB bluetooth adapter had disappeared when I upgraded to firmware 3.60 which would probably explain why the Ruuvi sensors disappeared. Any help on this issue would be appreciated.
regards
Craig
I’m using a 3rd party USB Bluetooth dongle and a Ruuvi - currently on the beta 3.60… and everything seems to be talking ok. But I’m pretty sure there was a kernel update with 3.6 so maybe the Bluetooth adapter you are using? How does it work with the built-in Bluetooth (yes, I know that is not ideal).
Thanks for your reply. I too am using an a 3rd party Bluetooth dongle. I tried turning on the internal Bluetooth but it still didn’t work. One thing I didn’t do when turning on the internal Bluetooth was to do a hard reset (ie: remove power). I’ll try that tomorrow morning and advise.
Regards
Craig
@cwsymons I have a unit on my test bench markings CPU A10 and it is as you described, missing device. Factory reset, re-imaged etc. without success. Tested with earlier A9 boards and my own later test units appear fine. (6 ruuvi’s in use on the test bench)
Thank you for your input. I am pleased I’m not the only person experiencing this issue.
Regards
Craig
Did you test with the internal bluetooth of the mk2 or only a dongle?
I did try the internal Bluetooth. It didn’t work. What I didn’t try is doing a hard reset. I’ll try that tomorrow and let you know.
Regards
Craig
The bluetooth sensors section under the integration menu is where the devi hci0 is missing, but returns when reverting to 3.55. Bluetooth can be turned on/ off but not sure to what effect as I swapped my unit out for now. It is the internal bluetooth that no longer works.
Please confirm the external BT adapter that is being used?
Please also go to general modifications and confirm the status is “OK”
I agree. I noticed that too.
Regards
Craig
I’m experiencing the exact same behaviour with 2 Ruuvi sensors that went missing after upgrade to v3.60. Reverting to v3.55 has restored the connection to the sensors. I am using the internal USB-Sensor on a Cerbo with the serial number HQ2146…
@sven66 You are lucky that you have gone so long with that Cerbo connecting with the internal Bluetooth module. There is a known issue with your serial number as explained in the manual Section 5.9. As the firmware has got larger, the CPU load has increased and you should swap to using an external Bluetooth USB dingle. The manual has a list of adapters but it is some years old now so some are no longer produced.
The TP Link UB500 was found to work well during beta testing by some of the testers when this problem arose with older Cerbos.
Extract 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. Note that this limitation does not apply to the Cerbo-S GX.
During Beta testing several of the testers had this happen on the older Cerbos and added USB Bluetooth dongles and found that the TP Link UB500 worked, info in the beta thread. The info may also apply if an existing USB Bluetooth dongle has stopped working because of firmware upgrades.
If anyone has a Bluetooth USB adapter that works with v3.55, and no longer works or appears in v3.60 then please post here.
We can see what the issue his, hopefully fix it.
Can you share the specific model? Victron obviously test the supported list but with kernel and module upgrades its not impossible others may have issues.
Hi Nick,
The specific model is not displayed on the device. I purchased it years ago. Prior to purchasing the device I did refer to the list of BT adapters was on the Victron site that had been tested
I don’t know if this will help you but I see that you are using a USB adapter and I had a problem with a USB adapter of this type which made me raise the dongle above 40° which had the effect of putting panic on the Ruuvi display.
I noticed it with the thermal camera, you should maybe try to check this because I have the same TP-Link as you and it works well
Hello all,
I’ve experincing this trouble with an Ekrano device.
Did you try to do a power off (unplug the power) wait few seconds… replug and see…
After that the Ruuvi sensors were back …
Xabi
