Growatt Wechselrichter werden als AC Last angezeigt

Been down a similar rabbit hole recently — got a Growatt unit talking to my Victron Cerbo via Node-RED and it works brilliantly... right up until it decides to show itself as an AC load rather than a proper AC input/generator source on the VRM dashboard. 🤦

Spent an embarrassing number of evenings on the narrowboat squinting at MQTT topics wondering why my carefully crafted Node-RED flow was effectively lying to the GX about what the Growatt actually is.

The core issue seems to be around which com.victronenergy service path you're publishing to — if you're hitting com.victronenergy.acload instead of com.victronenergy.pvinverter (or whichever is appropriate for your setup), the Cerbo just lumps it in with the kettle and the telly on the load side. Completely throws off your consumption figures.

A few things worth checking:

• Device instance numbering — duplicates cause chaos
• The /Connected and /ProductId keys — Victron is surprisingly fussy about these
• Whether you're running Venus OS Large — makes a difference to what services are actually available

Anyone else managed to get multiple Growatt inverters playing nicely as distinct sources rather than being swallowed up as phantom loads? Curious whether having two units makes the device instance conflict worse, because on my single-unit setup it took long enough to sort out as it was.

Feels like there should be a cleaner driver for this rather than bodging it through Node-RED, but here we are.

@OffGridJulie had exactly this with my motorhome setup. The Growatt was appearing as an AC load on the Cerbo dashboard which completely threw off my consumption figures.

Fixed it by making sure the DVCC settings were correct and the Growatt was properly registered as a multi-phase inverter rather than just a generic load. Also worth checking your Node-RED flow — if the device class isn't explicitly set in the MQTT payload going to the Cerbo, it'll just dump it as an AC load by default.

Victron's VRM portal was showing my solar numbers as totally wrong until I sorted it.

What firmware are you running on the Cerbo? Some of the older versions had quirks with third-party inverter classification.

@OffGridJulie classic Victron moment — your inverter identity crisis is basically just the Cerbo having an existential meltdown about what counts as a "real" inverter vs a freeloading AC squatter on the bus.

Check your Device Instance numbering in the VRM portal — if your Growatt's instance is clashing with the Multiplus, the Cerbo just lumps it in with the loads like a confused bouncer who can't read the guest list.

Sorted mine by reassigning the DVCC settings and making sure the Growatt was properly declared via the dbus-serialbattery path rather than letting Node-RED do the heavy lifting on device classification — Node-RED's brilliant but it won't fight the VE.Bus hierarchy for you.

Took me a wet Welsh Tuesday afternoon to figure that out, so consider yourself warned.

Had this exact headache last summer sorting out my barn conversion setup. The culprit for me was the device instance numbering in VRM — when the Growatt's MQTT data doesn't include the right AC_Position value, the Cerbo just lumps it in with loads by default.

Worth checking your Node-RED flow and making sure you're explicitly publishing AC_Position: 0 (for AC input) or 1 (for AC output) to the correct Venus OS MQTT topic. Once I added that single parameter to my flow it sorted itself immediately.

@OffGridJulie also double-check you're writing to com.victronenergy.pvinverter rather than a generic device path — that classification matters enormously for how the Cerbo interprets the data on the dashboard.

Happy to share my Node-RED flow if it'd help! 🙂

@BevOliver that's interesting about the device instance numbers — is that something you sort within the Cerbo's remote console, or do you need to dig into VRM portal settings to fix it?

Asking because I'm mid-build on my van conversion and I've got a Growatt sat on my bench waiting to go in alongside a Victron MultiPlus. Really don't want to bodge the Node-RED integration and end up with the same misidentification issue down the line. Would rather get it right first time before everything's buried behind panels.

Does the device instance conflict only show up once you've got multiple inverter-type devices on the VE.Can/VE.Bus network, or can it happen even with just the one Growatt talking over Modbus?