question

Hi @Paul LeBeau

You'll need a gx device or a multiplus GX model (for one built in). I find victron far more open that other providers so you've got a fair few more options for integrating these system.

GX devices can run node red so you could just forward the data in whatever format you want directly to you database by writing it in node red might be nice/quick solution to add lots of them in future ie just import prewritten node red code and it'll add to your system.

You could write a custom python driver installed on gx device to forward data directly from dbus (bit more involved), more details of which can be found on venus os github wiki.

The other option like you mentioned (probably easiest) is send the local MQTT data to whatever database you have.

If you want live/granular data I would install something locally or even on the GX device to forward the MQTT data if that's an option. GX devices run embedded linux (and allows root ssh access) so you can install pretty much anything (opkg package manager is preinstalled).

Here's documentation on how to access the MQTT and the topic structures:

GitHub - victronenergy/dbus-mqtt: Venus OS service mapping the D-Bus on Venus OS to MQTT

I also find the dbus paths useful for identifying the topics:

dbus · victronenergy/venus Wiki · GitHub

However you could also get the data via victron cloud (vrm) this might not be granular enough for your use case but here's the info just in case.

VRM API documentation (victronenergy.com)

EDIT: victron also supports ModbusTCP is that's preferred over MQTT.

EDIT2: i think there is remote access to MQTT externally via MQTT broker also. I'm not so familiar with this:

MQTT local & via MQTT broker - Victron Community (victronenergy.com)

Hi @matt1309

Thanks for the detailed answer. Much appreciated

However I don't see anything there that will allow us to send control signals to the inverter from outside the customer's local network.

We've connected inverters from six other manufacturers to our system. They all supply a REST API that allows us to get meter data and send control signals (such as charge/discharge). Victron has multiple interfaces (VRM API, MQTT, Modbus-TCP), but they all seem to be one-way only - out (AFAICS).

Is there something I'm missing? Does Victron simply not allow this?

The only possible solution I have come up with, is to use an HTTP Endpoint node in Node-RED. But that seems like a complicated solution.

Does anyone have an alternate suggestion?

Cheers

Paul

Ok. Thanks Matt. That's useful. So it looks like I'll need to get on the end customer's local network somehow (eg VPN) and send modbus packets to their GX device (?)

Does that sound right?

> Happy to give mqtt topic examples if you've got a list of data/required controls

We'll need basic info like charge/discharge rate, battery SOC, etc

Thanks for your help so far.

That method will work.

If you dont want to setup/install VPN then could use externally accessible MQTT that is used to send data to VRM (victron's cloud). No need to install anything extra in client networks then.

This post seems to give a good guide on getting MQTT address in python.

MQTT local & via MQTT broker - Victron Community (victronenergy.com)

For getting data VRM API can probably get that data. I've never used it so not sure if it allows as much control as direct MQTT will though.

The other option is rather than periodically querying API's you could get node red on the gx devices to live send the data to your servers/endpoints.

The MQTT topics follow same structure as dbus paths:

dbus · victronenergy/venus Wiki · GitHub

Just need to prefix them with W (write) or N and VRM ID. That's all explained here though:

GitHub - victronenergy/dbus-mqtt: Venus OS service mapping the D-Bus on Venus OS to MQTT