Minor bug with Filter RBE nodes

General
1

Since the RBE node was renamed to Filter, I'm no longer seeing any of the strings in the Filter settings form.

See screenshot:

2022-02-16_12-29
2022-02-16_12-29772Ă—308 11.9 KB

Currently on the latest release of NodeRed, and can hack/fix it by manually installing the Filter Node Module into the node_modules folder. But it then says it's been installed twice in the admin UI.

Is there a correct method to reinstall the Filter node or another way to fix this?
This is a production system, so can't just reinstall everything.

Many thanks!

2

You have to remove all instances of the filter node as they are part of the core nodes.

3

No, you should not need to do anything.

This is usually a browser caching issue - where it is still using the old message catalog without the updated messages in.

A clear if the browser cache should resolve it.

4

Thanks for the suggestion.

I've tried clearing the cache, using a different browser and using Private mode, but they all have the same problem.

5

Did you do that via the browser menus?

6

Yes, via the Settings. Also tried on other machines, with no fix.

7

Can you stop node-red and start it again in a terminal and post the terminal output here please.

Also check in the browser developer console if you see any errors.

8

I fixed my problems in this way - and it was not a caching problem of the browser.

9

Which filter node did you remove?

10

I removed all dedicated rbe/filter nodes - so no dedicated filter/rbe node is available anymore. The rbe node is only part of the core nodes.

image
image432Ă—831 19 KB

1 Like
11

Restarting from the terminal outputs:

Welcome to Node-RED
===================

18 Feb 10:06:02 - [info] Node-RED version: v2.2.1
18 Feb 10:06:02 - [info] Node.js  version: v14.15.0
18 Feb 10:06:02 - [info] Linux 4.15.0-167-generic x64 LE
18 Feb 10:06:02 - [info] Loading palette nodes
18 Feb 10:06:03 - [info] Settings file  : /home/username/.node-red/settings.js
18 Feb 10:06:03 - [info] HTTP Static    : /home/username/.node-red/public
18 Feb 10:06:03 - [info] Context store  : 'default' [module=memory]
18 Feb 10:06:03 - [info] User directory : /home/username/.node-red
18 Feb 10:06:03 - [info] Projects directory: /home/username/.node-red/projects
18 Feb 10:06:03 - [info] Server now running at http://127.0.0.1:1880/
18 Feb 10:06:03 - [info] Active project : av-ubu-nodered
18 Feb 10:06:03 - [info] Flows file     : /home/username/.node-red/projects/av-ubu-nodered/flows_av-ubu-nodered.json
18 Feb 10:06:03 - [info] Starting flows
Tesla API: No token found. Getting new token now...
Tesla API: doing api call to fetch new access token
18 Feb 10:06:03 - [info] Started flows
18 Feb 10:06:04 - [info] [udp in:d51c3f7bb592c1b5] udp listener at 0.0.0.0:8081
18 Feb 10:06:04 - [info] [udp in:818b09a0530f10bd] udp listener at 0.0.0.0:1888
18 Feb 10:06:04 - [info] [udp in:3fc80d15.212f4a] udp listener at 0.0.0.0:22622
18 Feb 10:06:04 - [info] [mqtt-broker:AvMQTT] Connected to broker: mqtt://10.2.0.24:1883
Tesla API: access token OK
Tesla API: No token found. Getting new token now...
Tesla API: doing api call to fetch new access token

No obvious errors. (username sanitized)

In the browser the only error is:

DevTools failed to load source map: Could not load content for http://10.2.0.23:1880/vendor/purify.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
12

I think I've spotted the problem. Thanks to the post above.

In the palette nodes I have a separate entry for "node-red-node-rbe" outside the core nodes. The only option is to disable this, what is the process to manually remove this entry?

13

Look into the node_modules directories if there is a directory named "node-red-node-rbe". If there is one, change to the parent directory of the node_modules directory and remove the module with
npm remove node-red-node-rbe

May be you have several node_modules directories then you need to look in all if there is a node-red-node-rbe directory.

After this restart you node-red, clean browser cache and the nodes should work normal

14

There's no "node-red-node-rbe" directory in the node_modules directories.

There is an entry for "node-red-node-rbe" at the bottom of the .config.nodes.json file, and a quick search elsewhere seems to suggest this is the only reference. Is it safe to manually remove this entry? and would it fix the problem?

15

Can you share the full entry for that here?

Right now we don't know what the problem is. The way the RBE node is incorporated into the core and relabelled Filter was done in a way that should be completely transparent to end users. The runtime should be refusing to load the node-red-node-rbe module because it already has those node types now in the core palette. The editor should be using the core message catalog to get the text for those nodes.

16

Sure it's:

 },
    "node-red-node-rbe": {
        "name": "node-red-node-rbe",
        "version": "0.5.0",
        "local": false,
        "user": false,
        "nodes": {
            "rbe": {
                "name": "rbe",
                "types": [
                    "rbe"
                ],
                "enabled": false,
                "local": false,
                "user": false,
                "module": "node-red-node-rbe",
                "file": "/usr/local/lib/node_modules/node-red/node_modules/node-red-node-rbe/rbe.js"
            }
        }
    }

In case it helps, the file referenced doesn't exist.

17

Also found this entry in .config.json

,
  "node-red-node-rbe": {
   "name": "node-red-node-rbe",
   "version": "0.2.9",
   "local": true,
   "nodes": {
    "rbe": {
     "name": "rbe",
     "types": [
      "rbe"
     ],
     "enabled": true,
     "local": true,
     "module": "node-red-node-rbe",
     "file": "/home/username/.node-red/node_modules/node-red-node-rbe/rbe.js"
    }
   }
  },
18

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.