question

@vt1py

Use the Victron input node, Settings Control then use the following

• Venus settings
• DVCC system max charge current (A DC)

Link that to an MQTT input node

I use this to limit a Fronius Symo 15kw to reduce the charge current when battery SOC goes higher than 85% or what ever I decide as a percentage limit on the Node red dashboard. Make sure to write the setting to file and read the value from file to safe guard the value after a reboot or restart.

Hi, thank you for your help. :-)
Node Red doesn't run on the Cerbo but on another RaspPi in my configuration.
Afaik I will need to use DBUS over TCP for the Victron input node. Can you confirm or do you use it in another way?

I'm also trying to get this to work, but no luck so far. I'm not familiar with Node Red at all, but I've been successfully using MQTT through Home Assistant via my Cerbo GX to control a lot of settings. I've even been able to publish a new value to the address below and can see the change in MQTT Explorer, but it doesn't ever actually pass through to the solar charger. It almost seems like this field/address is locked or read-only somehow between what I can see and change via MQTT and the actual Victron hardware. I'm willing to try to figure out Node Red for this if it's the only way, but I'm also trying to understand why this particular setting won't update to the solar charger even when I seem to be able to modify it via MQTT. Thanks in advance.

victron/N/############/solarcharger/279/Settings/ChargeCurrentLimit

@Olivier Hecht check to make sure the payload passed into the Victron node is a valid number and not text that displays a number. Text looking like a real number has tripped me up a few times. Format the payload with a function node

return {payload:Number(msg.payload)};

@Olivier Hecht Use the right mode to update value:

victron/W/############/solarcharger/279/Settings/ChargeCurrentLimit
       ^^^

N: Notify => subscribe topic => receive values
W: Write => write value => send value to device
R: Read => read value => trigger value to be sent, all subscribers will receive a fresh value

Hi all,

it might still be helpful for someone:

- I finally changed to v 3.30 on my Cerbo GX (normal image, not large as Node Red is running on a separate 'server')

- with version >= 3.x (don't know the exact version) you can set /Settings/Services/InsecureDbusOverTcp using dbus-spy (in console, i.e. using Putty (..) and SSH log in to your Cerbo). As derrick thomas mentioned above dbus-spy does show all the settings and channels

- no problems with the Github Fronius Smartmeter integration using firmware v 3.30

- setting of DVCC Charge Current Limit does work (using Node Red and Homeassistant)

- the topic in my case is as follows:

W/##VRM-ID##/settings/0/Settings/SystemSetup/MaxChargeCurrent

- there might be a problem with strings instead of numbers/integers - again as already mentioned by markus-001

- this can easily be checked by listening to your own W/##VRM-ID##/settings/0/Settings/SystemSetup/MaxChargeCurrent message in Node Red