Did you check the correct setup of IO lines after Venus update in the relay menue?
Did you use the “deploy” button in Node Red to restart node after venus update?
I let the firmware update to 3.6~46 and after the reboot checked on remote console to ensure relay 2 was still in Manual mode. It was. Maybe 30 seconds after this I got an error message on the console about device not connected to VRM, before I could screen shot it, it disappeared…
Then I fired up Node Red.
I checked the operation of the relay control: It was no longer working
I ran into exactly the same problem using 3.60~46.
Downgraded to 3.54, now everything works again.
What i found is that Relay node’s that were already made, linked and deploy do stay working in 3.60~46.
So a workaround for now is downgrading to 3.54 (official version), creating the wanted flow and then upgrading to the newest beta. Then you have a working relay flow while still being able to use the beta.
I can confirm the bug.
In v3.54 and v3.60~39 there’s no problem reading or writing the relay state in Node Red.
In v3.60~46 I can still read the relay state but can’t set it from a freshly deployed relay control node.
After deploying a relay control flow in v3.54 or v3.60~39 and then upgrading to v3.60~46, the control node gets status “disconnected”.
" The device is no longer available via the stored service path. Please (re)select the device from the dropdown and deploy again."
However, setting the relay(s) while running v3.60~49 from a flow deployed in v3.54 or v3.60~39 still works.
Setting the relay via Remote Console or VRM also works.
My test setup:
Raspberry Pi3 running VenusOS v3.60~39 / v3.60~46 (my test device)
CerboGX MK2 running VenusOS v3.54 / v3.60~46 (couldn’t find v3.60~39 download to test against that)
I’m running the same versions as you are.
What do you get when you double click on a Relay Control Node ?
From the regular flow screen on v3.60~46 everything looks fine here, but when I double click a Relay Control Node, it says it’s disconnected.
Dragging a new Relay Control Node to a flow and double clicking that gives a “There are no relay services available. Please check that a relay is connected or try a different node.” message.
Quick update: in node-red-contrib-victron v1.6.20, as shipped with VenusOS v3.60~47, the bug is also present.
(For reference: v3.60~46 shipped with node-red-contrib-victron v1.6.19)
FWIW, yesterday I upgraded to 3.60~46 and love the UI changes, but I was trying to do some work in Node-RED and it was super flaky. It kept disconnecting and giving me a red message at the top of VRM saying it was trying to reconnect. Eventually it would, but not for long. The Node-RED UI wouldn’t work at all. I forgot the error message. I rebooted to .54 and everything was back to normal - although now the UI feels old .
Im having issues with remote connection to vrm portal, and thus node red bith yesterday and today - think I will leave everything alone for a while until it is stable, and consider hard wiring and a manual control for my project rather than rely on this.
The Read “Relay Node”, as in your screenshot, is not impacted by the bug.
It’s the “Relay Control Node” that is impacted, the one used to set relay status instead of reading relay status.
They sort of broke the Node Red dashboard in v3.60~49 though
Hopefully Victron can quickly find a solution, I’ll be testing any new version that comes out.
.
