V3.72 release, Node-RED problem with virtual battery control node

Node-RED
1

I have a number of virtual batteries, these were set up during V3.70 beta versions and were working as desired and they continue to function as expected as I have upgraded to V3.71 and V3.72.

The data is read into these using the battery control node.

Now I am on V3.72 and have decided to edit the flows but I can not do so because the battery control node can no longer see any of the virtual batteries and the control node states disconnected despite actually working properly. These battery control nodes were obviously working during V3.70 beta to have set the flow up.

IMG_20260330_164446
IMG_20260330_1644461264×556 90.2 KB

IMG_20260330_164339
IMG_20260330_164339795×1039 83.8 KB

2

Have you tried removing the old node and readding the new one?

3

I have now tested the following as I do not want to mess up the existing flow

I created a new virtual battery. I then added a new battery monitor control node, the battery monitor control node will not list the new or old virtual batteries in the battery monitor input, only the physical battery, the Lynx NG BMS.

IMG_20260330_185535
IMG_20260330_185535789×710 60.2 KB

I then created a new custom control node, this will accept the physical battery and the new and old virtual batteries as the target device. Starter Battery (103) is a virtual battery.

IMG_20260330_185808
IMG_20260330_185808800×900 85 KB

This suggests that the battery monitor control node is partially broken.

4

This sound very similar to the issue I’m having: Virtual Device Issue: Cannot GET /victron/virtual-device-types

I don’t have a fix for my issue, but if it’s the same there has been no progress either.

Update: I opened an issue on the git repo for @victronenergy/node-red-contrib-victron here: Issue · GitHub