My other Mopeka and Ruuvi sensors work fine, including a Mopeka Pro 200. But I just bought a Mopeka Pro 200B which essentially looks the same as the 200, but the “B” is for battery powered instead of wired into 12V. My Cerbo GX does not recognize this sensor and this one only, even though the Mopeka app has it connected and with a super strong signal and quality. Like doesn’t show up at all as if it doesn’t exist to the Cerbo GX. I even sat it right next to the Cerbo thinking maybe it was a signal issue.
Interested if anyone else has the new Pro 200B synced with their Cerbo GX?
If not, how do I get in touch with Victron to add it as a recognizable bluetooth sensor? Mopeka insists it’s a Victron issue.
Because the Pro 200B has a different id code in its Bluetooth advertisement packet than the Pro 200, it is indeed not recognized by Venus OS v3.70. We will probably add support in a future version, but cannot say anything about when this will be available.
Thanks for the insight. I wish Mopeka would have told me this - I’d have just wired in a Pro 200 instead. Does it require a firmware update or does it just “happen” and I should keep trying to connect through the Cerbo every so often?
Support for the Pro 200B will require an update of Venus OS if that is what you mean. It should not require an update of the Mopeka. When support is added to Venus OS, it will be probably be mentioned in the changelog / announcement on this platform.
I’m in the same situation with the 200b. I wish I would have known and I would have just gotten the wired one. I don’t know who to reach out to at Victron to get them to include the Pro 200B integration on the next firmware. Have you had any contact with victron about this?
Yes someone responded in this thread from Victron. Hopefully it will be in future firmware. Bit burned at Mopeka for not stating this before I purchased. I would have just wired the 200 in had I known. Mopeka blames Victron. Guess I’ll just wait it out until it’s added.
@wasson1 This is Jonathan with Mopeka. Sorry for the confusion - I know it doesn’t help you now, but we will get a note added to our web listing to indicate something along the lines of “Cerbo GX support coming soon”. Let me know if there’s anything I can do in the meantime to help, but I understand that once installed in your tank, it may be easiest to wait.
We have a prior email chain with some of the higher-ups that we will refresh too, to hopefully help put more visibility on this.
@thiemovanengelen - Let me know if you’d like a unit to validate with and we can send some to your respective developer(s) free of charge.
As I think you’re aware, the bluetooth message structure should be 100% identical to our other sensors. The one change is that the “Hardware ID” now reports the product code for Pro-200B. So treating this identically to other top-down sensors e.g. the TD-40, TD-200, or similar would be sufficient.
@jkaufmann Thanks so much. The fault is on my end because I didn’t even know I ordered the 200B. I didn’t know there was such a thing and I already have a 200 on my fresh water tank. I just clicked on the first 200 pro I saw. The 200B I bought is on my diesel heater tank so it’s kinda crucial I’m able to monitor it remotely in addition to on board the RV for the days/weeks during the winter when the heater triggers on - so I know when I need to get to the RV to fill the tank.
The funny thing is, I prewired it for the 200 before I ended up with the 200B, but after it arrived I was like, “This is cool anyhow and should work the same, so I’ll give it a go”. Only to find out this Cerbo issue. I just terminated the +/- wires adding a busbar in case I need 12v somewhere around there in the future. So, I’d happily trade the 200B in for a 200 replacement, but I can’t gaurantee what shape it would be in after prying off. It won’t ruin the tank, but it may the sensor.
But yeah, I’d rather have the 200. Appreciate you addressing it, regardless. Cheers!
V3.72 is now out and still isn’t visible. The Pro 200 (wired version) does work (I have one on my fresh water tank). I bought a Pro 200B in error for my diesel heater fuel tank, not realizing there is a difference in bluetooth signatures between the two and installed it thinking it would function the same as all my other Mopeka sensors (I run seven in total). It does not. We just have to wait it out and keep updating firmware until it shows up. Since the season is changing, my diesel heater is not used, so it’s not a big deal, but if we make it to the next fall season without it being added to Cerbo firmware I’m gonna be a little upset with Mopeka. They should have noted that it wasn’t integrated with Victron yet. I need to monitor diesel fuel remotely during cold months when I’m not accessing my RV often enough to manually check.
Hi all,
I’ve now found a temporary workaround. An ESP32 is used as a BLE scanner and for translating the data into a format compatible with the Victron Cerbo GX. The ESP32 then sends the data directly to the Cerbo via MQTT.
If there’s interest, I’d be happy to share the project.