VRM dashboard shows orange exclamation mark on "AC loads" icon, but not on Cerbo GX

Seen this exact thing on my static caravan setup last winter and it drove me absolutely spare for about three days.

Turned out the Cerbo GX itself was perfectly happy — no alarms, no warnings, nothing in the device list. But VRM was throwing that orange exclamation on the AC loads tile like something was catastrophically wrong. Very reassuring when you're trying to monitor emergency backup remotely, cheers Victron. 🙄

From what I eventually pieced together (after reading approximately four hundred forum posts in three different languages):

• The orange icon on VRM doesn't always mirror what the Cerbo GX displays locally
• It can be triggered by a measurement threshold rather than a hard alarm — VRM applies its own logic on top of what the GX reports
• In my case it was because my AC load reading was occasionally spiking above what VRM considered "normal" for my system configuration, even briefly

Worth checking:

1. VRM portal → Advanced → widgets — see if the AC load value is occasionally going daft, even momentarily
2. Whether your CT clamp or energy meter (I've got a Victron Energy Meter VM-3P75CT) is reading cleanly with no dropouts
3. Whether it coincides with anything switching on — my immersion on a timer was the culprit, briefly confusing the reading

Anyone else seen this? Particularly curious whether it's worse on certain firmware versions — mine's been more settled since the last Cerbo update but I wouldn't exactly call it solved.

@ForestDaz classic VRM vs local display desync — seen this on my narrowboat Multiplus II setup.

Nine times out of ten it's a stale data / cloud-side alarm state that hasn't cleared properly after the original fault resolved. VRM holds onto alarm conditions longer than the Cerbo does locally.

Quick fix checklist:

1. Force a VRM alarm reset — go into VRM → Alarm Settings → clear any latched AC-related alarms manually
2. Check your firmware is current on both the Cerbo and VRM portal (yes, VRM has its own versioning)
3. If the Cerbo lost internet briefly during the original fault, VRM sometimes gets confused about what's "live" vs historical

Worth noting: Victron's VRM portal is brilliant but it absolutely does hold grudges. That orange icon can persist days after the underlying issue is completely resolved.

@ForestDaz three days is nothing, mate — I lost a fortnight of my life to this exact rabbit hole before realising VRM was just being dramatic about a phantom AC load reading that existed entirely in the cloud and nowhere near my actual tiny house.

Check your VRM alarm rules under Settings → Alarm Rules — sometimes they're set stupidly sensitive out of the box and will throw an orange fit over a load spike that the Cerbo already forgave and forgot about in milliseconds.

The local Cerbo is the source of truth here; VRM is just a gossip who embellishes everything slightly.

@ForestDaz had almost the exact same thing on my shepherd's hut Multiplus setup — orange exclamation on VRM but the Cerbo sat there looking completely unbothered.

What finally sorted it for me was checking the AC load metering settings in VRM itself rather than chasing hardware. There's a threshold configuration buried in the dashboard settings that can flag "unusual" load patterns based on historic averages — if your consumption profile changed (mine did after I added a small chest freezer), VRM essentially thinks something's wrong even when nothing is.

Worth checking:

• VRM portal → Settings → Alarm rules
• Compare against what the Cerbo actually reports locally via Remote Console

The Cerbo doesn't trigger because it's just reporting raw data. VRM applies its own logic layer on top. Two different things talking slightly different languages, basically.

@ForestDaz worth checking whether your AC loads sensor threshold is configured differently between local CCGX/Cerbo settings and what VRM is interpreting. There's a known quirk where VRM applies its own alarm logic against the same data stream the Cerbo receives — the Cerbo might sit below its local warning threshold whilst VRM flags it using a different baseline.

On my shepherd's hut build I found the culprit was a mismatch between the "AC input current limit" setting and what VRM expected to see as "normal" load behaviour. Navigate to Device List → MultiPlus → AC Current Sensor and verify the input limits are consistent with your VRM alarm configuration under Settings → Alarm Rules.

Victron's own documentation is frustratingly vague on this specific desync scenario, but the VRM changelog for v2.89 onwards does acknowledge the separate alarm evaluation engine.