Victron SolarSense 750 Battery

Anyone managed to find the SolarSense 750 battery value anywhere in the Victron ecosystem without resorting to MQTT?

Running a fairly standard off-grid setup here — Victron MPPT, Multiplus II, and I've just added the SolarSense to monitor the battery bank in my garden office. All on VRM portal and the iOS app (latest stable, not messing about with betas after last time).

The problem is I simply cannot locate where the SolarSense battery reading actually surfaces in VRM. The device shows up fine, firmware updated, no errors flagged — but the actual battery value it's supposedly measuring is nowhere obvious. Checked under:

• Device list
• Advanced tab in VRM
• The dashboard widgets

Nothing. It's as if VRM knows the device exists but doesn't quite know what to do with the data it's sending.

I've seen mentions of pulling it via MQTT but that feels like overkill just to see a single sensor value. Surely Victron have exposed this somewhere sensible?

Using a Fogstar Drift 200Ah as the main battery if that's relevant — though I'd have thought the SolarSense is agnostic about chemistry.

Is this a known limitation with the current VRM firmware, or am I just looking in completely the wrong place? Wouldn't be the first time tbh.

@Wez1961 never heard of a "SolarSense 750" — pretty sure Victron don't make that, so you're essentially asking where to find a value that doesn't exist in the ecosystem natively.

If you've got a third-party battery bolted onto a Victron setup, your best bet is a Venus GX / Cerbo GX with the battery's BMS talking over VE.Can or Modbus TCP — that'll surface the data in VRM without touching MQTT. Check the Victron compatible BMS list first though, half these branded batteries aren't on it and you'll be writing a custom driver before teatime.

What's actually managing your BMS comms currently? If it's just a dumb battery with no protocol support, MQTT honestly might be your least painful option regardless.

@Rob1963 is right — there's no such thing as a Victron SolarSense 750, so whatever's labelling itself that in your system is either a third-party battery with dodgy integration or a custom parameter someone's invented in Venus OS.

Check your GX device → Device List and see what's actually reporting — if it's a third-party LiFePO4 (Fogstar, Pylontech, etc.) connected via CAN-bus or VE.Direct, the value you're hunting might live under a completely different register than you'd expect.

If you're on Venus OS Large, Node-RED gives you a cleaner view of everything the MQTT broker is serving without having to go full terminal — essentially MQTT with a nice GUI frock on.

What GX device are you running? That'll narrow it down considerably.

@Wez1961 worth clarifying what you're actually seeing — is "SolarSense 750" appearing as a device name somewhere in your system, or is it a third-party battery with a BMS that's communicating over VE.Can or VE.Bus?

If it's the latter, the value you're after might be surfacing under battery monitor in the GX device rather than as a named Victron product. Check your Cerbo/CCGX under Device List and see what's registered there.

If you're on VRM, the battery aggregated data should appear under the dashboard without needing MQTT — assuming the BMS is properly integrated. What GX device are you running? That'll narrow things down considerably.

@Wez1961 just to add to what the others are saying — I've got a Victron setup across my static caravan and the boat, and I've never come across that label anywhere in VRM, the GX device menus, or even Venus OS. Is it possible you're looking at a third-party battery with a BMS that's reporting under a custom device name? Some of the Fogstar and similar LiFePO4 packs can show up with odd identifiers depending on how the BMS is communicating over VE.Can or DVCC. What GX device are you running — Cerbo or something older? That might narrow down where the string is coming from.

@Wez1961 spent a good while chasing a similar ghost value on my narrowboat last winter — turned out a third-party battery BMS was broadcasting a custom label over VE.Can that Victron's own tools simply didn't know what to do with. The name "SolarSense 750" sounds very much like it could be a BMS firmware string from a non-Victron lithium pack trying to handshake with the ecosystem. Worth diving into your VE.Can device list and checking what's actually announcing itself. If you're running VRM, the device list tab will sometimes surface the raw identifier. Might also be worth a factory reset of whatever battery monitor you're using — I did exactly that with a Fogstar unit and the phantom labelling vanished completely.