Cerbo GX updated UI 3.50 bluetooth functions for Ruuvi

I’ve just updated the firmware (3.50) on my Cerbo GX and am now trying to find my Ruuvi tags, settings/bluetooth does not seem to be finding anything?
Anyone else managed to reconnect their fridges?
All the best

They are in settings/IO/Bluetooth Sensors
Is this what you are looking for?

Thanks Dave, I only see Analogue inputs and Digital inputs no Bluetooth sensors?
I have bluetooth listed in settings but only with the passcode underneath?
I wonder if its just signal strength…

Hi @Seamus - I’d you aren’t seeing the menu there the most likely explanation is a limitation in some older Cerbo GX hardware explained here - 5. Connecting supported non-Victron products

2 Likes

Hmm… I have been testing the 3.50 interface for the past month. Sometime in the past 3 days, all of my ruuvi tags stopped reporting and are no where to be seen on the Gerbo GX display.

The ruuvi tags were working all along with the 3.50 beta versions.

When I click on the “Bluetooth adapters” menu, all I get is a blank page.

Help!

Hi @MeltemiCaz ,

Pls check the link provided by Guy above, and match the serial number of your GX device (a Cerbo? ) to the one mentioned in the manual.

The part that matters is:

Note for Cerbo GX units built up to and including serial number HQ2207: 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.

What I don’t get is that the ruuvi tags were working just fine during the entire beta development of the 3.50 interface.

Did something change in the released version of the sw???

Do I read the serial number of my unit as mfg in 2022, week 11 and the cut off for the older devices is 2022, week 07?

I should also point out that the ruuvi tags have been working with my current Cerbo GX for the past 5 months. So, I do not think that it’s the hw version.

Hi,

That issue with Cerbos having a serial number of HQ2207 or lower often happens immediately after a firmware update (because fw update is CPU intense operation and causes the hardware to warm up). There have been a lot of support requests and posts around that - blaming the firmware update but actually its just that hardware series.

Hence we’re keen on ruling that out first.

But for you thats not relevant, you have newer hardware.

Nothing changed to the Bluetooth features. And the Ruuvis show up well in our test systems.

Can you post the VRM URL and enable remote support, then we’ll check!

All the best

Looks as if I bought unlucky, yours should be fine Bill, according to the serial no’s?

|Product|Cerbo GX|
|Firmware version|v3.50
|Serial number|HQ22064CKWR|

Sorry, I’m new at VRM. remote. What steps do I need to complete to provide access without posting here so that everyone can access my installation?

Is there an email address that I can use to send you an URL to my VRM instance?

This is my sailboat and home.

Thanks in advance!

well… My ruuvi tags have started working again. I have no idea what caused them to begin working. I see that there is an update to the GUI interface to 3.51~2 but I am still using 3.50. I am not on the boat at the moment, so will need to wait until the weekend to investigate further. Thanks to everyone that provided input!




But I am still not seeing them here. See this former UI screen shot from the VE manual.

I am still testing remotely with some local help on the boat, but the ruuvi tags have stopped being received, as soon as I powered on the MP-II inverters in charging mode. I am still checking the time stamps. I have no idea how the two could be related so my posting here might be a bit of a “red herring!”

Ok noted, thank you.

Many systems out there are fitted with Ruuvis, so in case there are real issues then I’m sure we’ll get more reports.

You could change the UI back to the Classic UI and see if that makes a difference.

That’s a good suggestion. I will try that switching back to the older UI when I am back on the boat at the end of the week.

1 Like

As a follow up I have moved two USB/VE’s into a 4 way USB hub to free up a slot for a USB BT dongle, bought the TP-Link UB-400 and it is now listed in I/O BT adapters. So fridge back on VRM/Raymarine bus, one issue has appeared, the Cerbo wants to close the 3.51 homepage sidebar down as its overloaded?
Just an FYI.

well, the ruuvi tags have started showing up on the Dashboard, but only one Mopeka tag is showing up on the Bluetooth page, not my other tags. However, the Mopeka tag is not even mine and must be on another boat in the harbor. Go figure…

Hi @MeltemiCaz , so the temperatures show on VRM, and I suppose locally on the GX as well (please confirm), but the sensors are not visible in the Bluetooth sensor config menu - right?

And what happens if you change the UI back to the Classic UI?

Ps. Two more questions: is this reproducible every time when you open New UI remote console on VRM?

Or only some times?

And how about on the local display, ie your GX Touch?

Lastly, is it ok if we login on the remote support feature? We can find the system by the name in the screenshot.

I spent several hours trying many different combinations of trying to get the the ruuvi tags to show up in the IO list.

I was able to finally get the ruuvi tags to show up on the VRM Dashboard Remote Console.

Let me explain what I tried.

  1. Over the past week while I was away from my boat, the ruuvi tags were showing occasionally on the VRM dashboard but not on the Remote Console
  2. I visited an Apple store yesterday and WAS able to bring up the Remote Console I/O page and have the ruuvi tags display.
  3. I went my boat and saw the ruuvi tags in the IO screen. No idea why this started working.
  4. While at the boat, I upgraded the UI to 3.52~2
  5. After rebooting, the ruuvi tags STOPPED showing up. Grrrr!
  6. I have two other Cerbo GX devices on the boat. Both are able to see the ruuvi tags.
  7. I checked on several browsers using both Apple and Windows laptops and was NOT able to see the ruuvi tags on the Remote Console.
  8. I deleted the caches from all of the browsers thinking that there was some residual cache parameter blocking access. However, nothing worked.
  9. Finally, I unplugged the Cerbo GX and power cycled the unit.
  10. The ruuvi tags started showing and the Bluetooth adapters finally started showing up again.

I wonder if there is some issue with the Bluetooth adapters not getting properly recognized.

However, I have a new issue.

On the VRM Dashboard, the ruuvi tags that are showing can no longer be expanded to show some of the other parameters such as air pressure and humidity. What has happened now?

However, I have a new issue.

On the VRM Dashboard, the ruuvi tags that are showing can no longer be expanded to show some of the other parameters such as air pressure and humidity. What has happened now?

Click on "Show Details " and you should see all the available data.