Issues with Victron MQTT Data Flow to Node-RED (Serial Number Only)

Modifications
, , , ,
1

Hello,

I’m having trouble receiving Victron device data (such as battery voltage, current, AC power, etc.) in Node-RED through MQTT.
We live completely off-grid using a 6kw wind turbine and 4kw solar but i would like to use Node-Red to automate loads, generator control etc.
My system comprises of a Quattro 10000, CCGX, 2xBYD battery box pro, Fronius Primo 5-0.1, and SMA Windy Boy.
The only device that is displaying on the Device List on the Raspberry pi VRM portal is the Fronius. (everything is fine on the CCGX and remote VRM portal)

Here’s what I’ve done so far:

Setup:

  • Device: Victron CCGX with the latest Venus OS Large image.
  • MQTT Broker: Mosquitto running on a Raspberry Pi with port 1883 configured.
  • Node-RED: Configured to connect to Mosquitto with the correct MQTT settings.

Steps Taken:

  1. Mosquitto Configuration:
  • Ensured Mosquitto was running and listening on the correct port using netstat.
  • Verified that Mosquitto was running correctly after several reboots.
  1. MQTT Topic Subscription:
  • In Node-RED, I subscribed to the topic N/Ac/Consumption/L1/Power (and other specific topics like N/Dc/Battery/Voltage).
  • Data wasn’t coming through. I only received the serial number of my CCGX in Node-RED and mosquitto_sub, despite the correct setup.
  1. Testing Data Flow:
  • Used MQTT Explorer and mosquitto_sub with the topic N/Ac/Consumption/L1/Power and N/#, but only the serial number is shown; no detailed data like voltage, current, or power.
  • Checked CCGX MQTT settings, which seem to be configured correctly for publishing data.
  1. Troubleshooting:
  • Killed the Mosquitto Bridge process to ensure the Mosquitto broker is handling data flow.
  • Restarted Mosquitto multiple times, as well as Node-RED, but no data flow changes.
  • Verified Mosquitto is receiving data from the CCGX, but it only receives the serial number.
  1. Logs: No error messages in Mosquitto or Node-RED logs that indicate a problem, except the lack of data on the expected topics.
  2. I have SSH access to the CCGX.

Questions:

  • Is there something I’m missing in the CCGX MQTT configuration that’s preventing the data from being published (such as specific topic configuration)? There doesn’t seem to be any options to configure this.
  • Are there additional permissions or settings in the Mosquitto or CCGX configuration I should check?
  • Any other advice on troubleshooting Victron MQTT setup or ensuring proper data flow to Node-RED?
  • I’m a beginner at all this so be gentle please!

Thanks for your help!

2

Hi,

first: Switch off the MQTT-Broker on the Raspi, as VenusOS has it’s own MQTT Broker.

Connect with MQTT-Explorer to the IP-Address of your CCGX and you see the entire tree of messages.

Best,
Wilm

3

Thanks, I’ll give that a go.

4

That still didn’t work.
I’m doing this over a home WiFi network, tomorrow I’ll try an Ethernet connection from raspi straight to same WiFi satellite as CCGX.
Also do I need to add it as an installation in the VRM portal using it’s portal id?

What’s baffling me is that my Fronius inverter was showing up in the device list earlier, and nothing else. The fronius is offline now as it’s dark so I guess that’s why it’s disappeared? But can’t work out why the Quattro and BYD batteries aren’t showing up when they are showing on the CCGX.

Finally, in Node Red when I try and use a Victron node, say AC Load there is an error in the node configuration window “ There are no ac load services available. Please check that a ac load is connected or try a different node.”
Or should I just be using the Victron “System” node? When I edit that it has Venus as the system and then underneath I can select the Measurement. It still doesn’t work though!
It worked once (battery SoC) and then stopped, now I just get either null or the id of the CCGX.

I’m a bit lost.

5

Shees…

Yes, I gues it was the Victron-System node, when you select Multiplus-XX. So you have to fiddle a little bit around. For me it was also a try-and-error walk to find out.

Best you use a Victron-Node and connect it with a Debug-Node, so you can see it quite easy.

Sorry not to give you the expertise you’ve expected…

Best,
Wilm

6

Thanks anyway.
It’s just very strange that some of it works!
I’m wondering is my mesh WiFi a culprit? :face_with_raised_eyebrow:

7

Meshes can be an issue, much like wifi repeaters.
There can be a huge variation in signal between AP’s which can disrupt comms.