question

d4h-ottmar avatar image
d4h-ottmar asked

(Solved) Node Red on external server broken after update to Venus 3.0

Hi Community,

as noted in the topic above i run in a prob with the external node red server, which is working flawlessly before update the Cerbo GX to Venus Version 3.0. I have edit the configuration parameter for the external node red access on the Cerbo once again and it seems after browsing the logs, that dbus connetion is working.

But now all victron nodes (in the flow) show disconnected and if a create a new victron node, a red triangle report listed: wrong properties -service -path

Is something changed in venus 3.0 that have an impact to external node red instance connection?

Thanks for ideas und suggestions


Node-REDModbus TCPVenus OS v3.00-32
1 comment
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Dirk-Jan Faber (Victron Energy) avatar image Dirk-Jan Faber (Victron Energy) ♦♦ commented ·

Some questions to clarify the problem. You are running Node-RED on another machine than the Cerbo GX and trying to connect to the Cerbo from that? Your used tags suggest that you are using modbus tcp to make that connection, correct?

Which node are you using to make the connection?

- https://flows.nodered.org/node/node-red-contrib-modbus ?

- https://flows.nodered.org/node/node-red-contrib-victron-modbus ?

Or even

- https://flows.nodered.org/node/@victronenergy/node-red-contrib-victron ?

0 Likes 0 ·
2 Answers
fish avatar image
fish answered ·

Really not sure but if your previous version was older than V3.0 the paths have changed..

This should help:

Version 3.0 released : Node-RED (nodered.org)

2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

d4h-ottmar avatar image
d4h-ottmar answered ·

Hi Dirk-Jan,

first thanks for all replies and sorry for the inconvenience.

I use dbus connection https://flows.nodered.org/node/@victronenergy/node-red-contrib-victron

Before upgrade to venus 3.0 (on Cerbo) connection from Node Red server and Cerbo GX is working as stated in my first post. Right after upgrade and reenter all config changes on the Cerbo, connectivity is broken.

please ignore my note adding a new victron node. This is normal behavior.

Any ideas what happend here.


2 comments
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Dirk-Jan Faber (Victron Energy) avatar image Dirk-Jan Faber (Victron Energy) ♦♦ commented ·

In that case I have a suspicion on what is causing the problem then. You've probably set `NODE_RED_DBUS_ADDRESS=venus.local:78` on the Node-RED server (or using the ip address instead of venus.local), pointing to the Cerbo.

In order to get that to work, previously you needed to adjust `/etc/dbus-1/system.conf` to have the Cerbo to listen to port 78. (As instructed here under point 4). With the firmware upgrade, the extra addition to that file is no longer needed. The new way is to set `com.victronenergy.settings /Settings/Services/InsecureDbusOverTcp` to 1. And then reboot the Cerbo to activate dbus over tcp.

1 Like 1 ·
Show more comments