Virtual Device Issue: Cannot GET /victron/virtual-device-types

Node-RED
, ,
1

I have an issue trying to use the Node-Red Virtual Device node when editing the node it does not display device types.

When troubleshooting the issue, the browser debug console shows that there is a 404 error trying to access the /victron/virtual-device-types url from the Cerbo’s.

These errors exist either accessing locally via IP or through VRM.

To produce the issue all that is needed is to drag the Virtual device node to the flow and open the node for editing.

Browser console errors:

vendor.js?v=0f32a4553afe:2 GET http://x.x.x.x:3000/victron/virtual-device-types 404 (Not Found)

VM299:148 Failed to load virtual device types

Victron_CerboGX_NodeRed_Failed
Victron_CerboGX_NodeRed_Failed1272×317 46.1 KB

When testing the url (http://x.x.x.x:3000/victron/virtual-device-types) directly, get this response from the cerbo:

Cannot GET /victron/virtual-device-types

Now for the system details.

I work as a Network Engineer / Systems Engineer and have a degree in Electronic Engineering.

When a typical MFG device doesn’t do or have the features of what I want or looking for, I design my own electronics for the need/feature.

(just to establish a baseline of my knowledge level and experience).

I have 2 Cerbos doing the exact same thing. Cerbo GX and CerboS-GX.

GX at home, and S GX on the boat. Both are running 3.71 (20260315163256)

Victron_CerboGX_Firmware
Victron_CerboGX_Firmware771×389 23.9 KB

SignalK is exactly the same plugins, version, and status on both:

Victron_Cerbo_Both_SignalK_Plugins
Victron_Cerbo_Both_SignalK_Plugins1167×1033 204 KB

Victron_Cerbo_Both_SignalK_Plugin_Status
Victron_Cerbo_Both_SignalK_Plugin_Status1012×373 60.9 KB

Node-Red is almost the same on both devices:

Only exception is a mssql-plus plugin extra on the Home GX.

And I am not sure why the Home is 1.7.3 and Boat is 1.7.4 for the @victronenergy/node-red-contrib-victron. During my troubleshooting I have also uninstalled/reinstalled the plugin. (though I believe this is of no concern since the issue exists on both devices and the Virtual Device node has been around since before the current version)

Victron_Cerbo_Both_NodeRed_Palette
Victron_Cerbo_Both_NodeRed_Palette1199×672 72.8 KB

2

Same problem here after update Node-red in Signal K

3

I am having exactly the same problem / issue. I have been using the victron virtual device node in node red, embedded in signalk, for more than 12 months now and not experienced this problem previously. am currently running cerbo gx firmware v3.71, signalk v2.24.0, node red v4.1.7

4

Just thought I would add the details that with the Node-Red updates (4.3.0 as of today/this post) it still is not working.

5

Thank you WarrenKD. I am attaching the browser console error that shows up in my case, just demonstrating that it is the same as you have encountered.

image
image1350×526 76.8 KB

What is the process from here? Can it be anticipated that someone from say Victron may take a look and post some further insights as to what the problem maybe?

6

I’m not actually sure of what the process should be. I posted in the forum hoping someone (Victron or otherwise anyone) maybe already had a work around or solution. I was really hoping someone from Victron would have seen my post and made some sort of reply they are looking into it or aware of it or anything/something would have been nice as I thought this was sort of a support forum since they link to it directly within the Node-Red nodes themselves.

You said you opened an official ticket? I would think that should/would probably get faster attention maybe?

I thought about opening a ticket but wasn’t sure if it would get any full support as it’s ‘node-red’ even though Victron includes it in their images for the Cerbo or document how to use the embedded version.

7

You could just log an issue on Git,.
We’re quite clear about the purpose of this forum in the guidelines.

8

Thanks for the reply. I have no problem doing that.

Since I’m not sure exactly where the issue is at, which Git repo should it be logged to?

@signalk/signalk-node-red, @signalk/node-red-embedded, @victronenergy/node-red-contrib-victron, or some other repo?

9

Start here.
Thanks

10

I created it here: https://github.com/victronenergy/node-red-contrib-victron/issues/443

11

In case anyone is not following the issue created, it appears that they found the issue and a fix will be coming soon.

12

It looks like version 1.7.7 has been released that is showing the fix for this issue.

On both my Cerbo’s the Palette Manager in Node-Red is not showing the update yet. I have restart SignalK and still not showing.

Does anyone know how to force the refresh or the install of the new version of @victronenergyvictronenergy/node-red-contrib-victron?

13

Thank you for the update and to those that have carried out the fix. much appreciated. I look forward to v1.7.7 being available in the pallet. I dont have the knowledge as to how to force an update when its not yet showing as available.