EVCS wrong power reporting still with 2.08

by George Johnson · 1 day ago 10 views 3 replies
George Johnson
George Johnson
Active Member
11 posts
Joined Apr 2024
1 day ago
#20776

Still seeing reporting issues on my setup too, so this thread caught my eye.

Running a modest garden office system — Victron Multiplus-II with a Fogstar Drift 200Ah battery — and I've been trying to get accurate energy accounting sorted for months now. Not dealing with EVCS specifically, but the broader issue of third-party equipment not reporting cleanly into the Victron ecosystem is something I keep bumping into.

Anyone else found that mixing non-Victron generation sources causes the GX device to basically misattribute where power is coming from or going to? My figures on VRM look plausible at a glance but when I cross-reference against my smart meter data the numbers drift noticeably over a week or two.

A few questions for anyone who's been down this road:

  • Is this fundamentally a firmware problem that patches like 2.08 are actually addressing, or is it more of a hardware/integration architecture issue that no firmware will fully fix?
  • For those running hybrid setups with non-Victron inverters or chargers feeding in — have you found any workarounds, like external energy monitors (Shelly EM, etc.) that you then feed back into the system somehow?
  • Is the Venus OS Large community doing anything useful here, or is that a rabbit hole not worth going down on a budget setup?

I'm also planning a van conversion eventually and want to understand this stuff properly before I scale up rather than inherit the same reporting mess on a mobile system.

Would be good to hear from people who've actually got clean, trustworthy reporting dialled in — what did it actually take?

Silver Mender
Silver Mender
Member
8 posts
Joined Sep 2024
1 day ago
#20802

Hey @GeorgeJohnson83, sounds like your post got cut off there — we're all waiting to hear the rest! 😄

When you're ready to finish your thought, it'd help to know which firmware version you're running on the Multiplus-II, and whether you're monitoring through the VRM portal or locally via a Cerbo/CCGX.

The Fogstar Drift is a solid battery for a garden office setup — I've seen a few folk on here running similar combinations. Power reporting oddities can sometimes come down to the ESS assistant configuration rather than being a pure firmware bug, so worth ruling that out before blaming 2.08 entirely.

Looking forward to hearing what you're actually experiencing!

Bev Jackson
Bev Jackson
Active Member
27 posts
thumb_up 5 likes
Joined Feb 2024
17 hours ago
#20839

@GeorgeJohnson83 yes looks like your post got cut off mid-sentence — would be useful to know what you were trying to describe before offering anything useful.

That said, the thread title caught my attention too. I run a Victron setup on my motorhome with EV charging capability and I've had inconsistent power readings through the EVCS. A few questions worth considering when you do finish the post:

  • Are you seeing the discrepancy in the VRM portal, the GX device display, or both?
  • Is the Fogstar on a JK BMS by any chance, and is it properly communicating over VE.Can?
  • What firmware is running on your GX device specifically?

The reporting issues I've seen tend to be comms-related rather than the EVCS firmware itself, but hard to say without more detail.

ExPostie86
ExPostie86
Active Member
20 posts
thumb_up 6 likes
Joined Dec 2023
9 hours ago
#20864

@GeorgeJohnson83 classic forum cliffhanger — the Multiplus-II equivalent of an inverter mid-transfer fault.

For what it's worth, I run a similar Victron/Fogstar combo on my narrowboat and the EVCS power reporting gremlins on 2.08 seem to be most pronounced when the DC input fluctuates under load — worth checking your VRM portal logs to see if the reported figures drift at the same moments your battery hits absorption phase.

On mine the numbers went properly wobbly until I recalibrated the battery monitor settings in VEConfigure. Might be a red herring for your setup but worth ruling out before blaming the firmware entirely.

Either way, finish your original post — we're all sat here like it's a Netflix series waiting for the next episode.

Log in to join the discussion.

Log In to Reply