Node-RED Victron extension is not working. (node-red-contrib-victron)

[denmroot]

Hi, I’m trying to install and use Node-red installed on an external Home Assistance machine.
Went through all instructions about setting up Cerbo GX superuser, passwords, modbus TCP access.
Cerbo SSH Venus OS: Root Access [Victron Energy]

Installed Node-red with Victron

And it seems that something is working, at least I’m getting logs from Node-red about dbus connection.

2025-01-08T19:10:23.229Z node-red-contrib-victron:victron-client Retrying dbus connection.
2025-01-08T19:10:23.229Z node-red-contrib-victron:dbus Connecting to TCP address tcp:host=192.168.1.22,port=78.
2025-01-08T19:10:23.347Z node-red-contrib-victron:dbus Connected to D-Bus.

but also there’s some failed logs

2025-01-08T19:10:23.523Z node-red-contrib-victron:dbus initService com.victronenergy.settings : Method "GetValue" with signature "" on interface "com.victronenergy.BusItem" doesn't exist
deviceInstance could not be assigned because res[1][0] is undefined :1.88/[object Object] (com.victronenergy.hub4)
deviceInstance could not be assigned because res[1][0] is undefined :1.44/[object Object] (com.victronenergy.system)
2025-01-08T19:10:23.536Z node-red-contrib-victron:dbus initService com.victronenergy.fronius : No such object path '/DeviceInstance'
2025-01-08T19:10:23.536Z node-red-contrib-victron:dbus initService com.victronenergy.platform : No such object path '/DeviceInstance'
2025-01-08T19:10:23.536Z node-red-contrib-victron:dbus initService com.victronenergy.digitalinputs : Method "GetValue" with signature "" on interface "com.victronenergy.BusItem" doesn't exist

When I’m trying to import example flow from node-red-contrib-victron it’s working and showing correct values from my Victron system.

But I’m unable to work with Victron nodes from @victronenergy/node-red-contrib-victron, if I try to add any node to Flow it shows error

Unable to access the service endpoint:/endpoint/victron/services/input-accharger

and there are no working parameters in any node.

What am I missing?

[dfaber (Dirk-Jan Faber (Victron Energy))]

That /endpoint part looks weird to me. You usually should be able to attach to https://venus.local:1881/victron/services/input-charger to get some (json) data. Depending on the configuration of your system, that does required the charger to be present. So the safer check is to look at the output of, in your case, https://192.168.1.22:1881/victron/services/input-system, as the system service is available on all Victron systems.

[denmroot]

Thank you.
Here are some updates about my investigation. It looks like this Victron integration is not working correctly in the HAOS Home Assistant installation type that I tried.

Any Victron node that I’m trying to add shows (service and path is not set with this service endpoint error)

I’m using Proxmox to run Home Assistant with 2 different types of machines:

1. VM with HAOS Home Assistant installation with Node-RED addon installed through supervisor
2. LXC container with Linux and manually installed Node-RED

This weird stuff (errors in @victronenergy/node-red-contrib-victron) is happening in the VM with HAOS, but there are no problems when I’m trying an identical setup in the LXC container with standalone Node-RED.

So I ended up using separate installations of HA and Node-RED and integrating them with node-red-contrib-home-assistant-websocket plugin.