Updated Node-RED 0.19.5 = Waiting for missing types to be registered?

General
1

Hi,

.I am using Linux XFCE

I have updated Node-RED to latest version and updated Node.js to v8.13.0.

I then restarted, but it stopped flows, because of SQLite node not compatible with Node.js to v8.13.0 ?

I then changed Node.js back to 6.9.4 and did another sudo npm install -g --unsafe-perm node-red
.

Now I get most nodes awaiting registering ?

05
ScreenHunter_18822 Nov. 26 15.05.jpg507×520 29 KB

.

Is it because of this? as I did not understand what it meant ?
.

40
ScreenHunter_18823 Nov. 26 15.40.jpg1125×546 124 KB

.
.

Help required :hushed:

Thanks

2

Show us the whole of the startup log please. You can copy out of the terminal using Ctrl-Shift-C then paste it here. Put a line containing three backtick characters before it and another such line after, that stops the forum 'helpfully' re-formatting it.

3 
gb@HA-KINO-PC ~/Desktop $ node-red
26 Nov 16:20:41 - [info] 

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

26 Nov 16:20:41 - [info] Node-RED version: v0.19.5
26 Nov 16:20:41 - [info] Node.js  version: v8.13.0
26 Nov 16:20:41 - [info] Linux 3.16.0-38-generic ia32 LE
26 Nov 16:20:42 - [info] Loading palette nodes
26 Nov 16:20:44 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
26 Nov 16:20:44 - [warn] rpi-gpio : Cannot find Pi RPi.GPIO python library
26 Nov 16:20:47 - [warn] ------------------------------------------------------
26 Nov 16:20:47 - [warn] [node-red-node-sqlite/sqlite] Error: Cannot find module '/home/gb/.node-red/node_modules/sqlite3/lib/binding/node-v57-linux-ia32/node_sqlite3.node'
26 Nov 16:20:47 - [warn] ------------------------------------------------------
26 Nov 16:20:47 - [info] Settings file  : /home/gb/.node-red/settings.js
26 Nov 16:20:47 - [info] Context store  : 'default' [module=memory]
26 Nov 16:20:47 - [info] User directory : /home/gb/.node-red
26 Nov 16:20:47 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable
26 Nov 16:20:47 - [info] Flows file     : /home/gb/.node-red/flows_HA-KINO-PC.json
26 Nov 16:20:47 - [info] Server now running at http://127.0.0.1:1880/
26 Nov 16:20:47 - [warn] 

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

26 Nov 16:20:48 - [info] Waiting for missing types to be registered:
26 Nov 16:20:48 - [info]  - ui_base
26 Nov 16:20:48 - [info]  - ui_tab
26 Nov 16:20:48 - [info]  - ui_group
26 Nov 16:20:48 - [info]  - profile
26 Nov 16:20:48 - [info]  - sqlitedb
26 Nov 16:20:48 - [info]  - ui_gauge
26 Nov 16:20:48 - [info]  - ui_chart
26 Nov 16:20:48 - [info]  - ui_dropdown
26 Nov 16:20:48 - [info]  - ui_ui_control
26 Nov 16:20:48 - [info]  - throttle
26 Nov 16:20:48 - [info]  - thingspeak42
26 Nov 16:20:48 - [info]  - ui_text
26 Nov 16:20:48 - [info]  - sqlite
26 Nov 16:20:48 - [info]  - gate
26 Nov 16:20:48 - [info]  - moment
26 Nov 16:20:48 - [info]  - ui_template
26 Nov 16:20:48 - [info]  - ui_button
^C26 Nov 16:20:59 - [info] Stopping flows
26 Nov 16:20:59 - [info] Stopped flows
gb@HA-KINO-PC ~/Desktop $ ^C
gb@HA-KINO-PC ~/Desktop $
4

Actually I suspect I know the problem. I suspect you had not been using --save when installing nodes, and later versions of npm uninstall any nodes that are not referenced in package.json. If you go to Manage Palette in node-red you can re-install the nodes and now they will automatically be added to package.json so you will not get the problem again. The ui_ nodes are from node-red-dashboard so re-installing that will sort them.

5

This is all that is in package.json

    "name": "node-red-project",
    "description": "A Node-RED Project",
    "version": "0.0.1",
    "private": true
}
6

As I suspected, so npm has uninstalled all the other nodes. Not very user friendly of it to do that without warning, it caught me out a little while ago too. I am afraid you will just have to re-install the extra nodes you were using.
[Edit] Can you post the startup log too please, just to check there isn't anything else.

7

Hi Colin where would that log be found ?

8

Sorry, I missed the fact that you have already posted it. It must have arrived while I was typing I think. That looks ok.
What does npm -v show?

9 
npmgb@HA-KINO-PC ~/Desktop $ npm -v
6.4.1
10

Would it be best to delete all of 'node_modules' and then do a fresh install of Node_RED

As at the moment the basics are missing

11

That's fine. You should be ok if you re-install the missing nodes.

12

Node-RED seems to be locked i cannot re install things it says they are already installed ?

13

What do you see if you install using the command line, so

cd ~/.node-red
npm install node-red-dashboard
14 
gb@HA-KINO-PC ~/.node-red $ npm install node-red-dashboard
npm notice created a lockfile as package-lock.json. You should commit this file.
+ node-red-dashboard@2.11.0
added 56 packages from 48 contributors, removed 108 packages and audited 106 packages in 24.315s
found 0 vulnerabilities

gb@HA-KINO-PC ~/.node-red $ 

Getting better all thats missing is

26 Nov 16:49:33 - [info] Waiting for missing types to be registered:
26 Nov 16:49:33 - [info] - profile
26 Nov 16:49:33 - [info] - sqlitedb
26 Nov 16:49:33 - [info] - throttle
26 Nov 16:49:33 - [info] - thingspeak42
26 Nov 16:49:33 - [info] - sqlite
26 Nov 16:49:33 - [info] - gate
26 Nov 16:49:33 - [info] - moment
^C26 Nov 16:50:49 - [info] Stopping flows


Not sure what  profile  is ?
15

Install the ones you know about and the others may get installed automatically as the dashboard ones did.

16

OK

Thanks Colin for your help

much appreciated

17

By the way, if you are using a recent Debian based system such as Xubuntu then you can update to the latest version using the Pi install/upgrade script from https://nodered.org/docs/hardware/raspberrypi. That ensures that you get a consistent set of base nodes and tools. Also it will install a systemd startup script if you want it to run on boot.

18

Has this occured because you've updated npm, and the newer version has automatically removed those nodes that were originally installed via cmd and not included in the npm manifest.

19

Hi Paul,

Yesterday I did get it working with Node.js v6.9.4
Today I updated Node.js to v8.13.0

And once again ALL flows stopped and I had to reinstall all missing nodes.

Not sure if this is how this is supposed to work ?

Then everything worked again

20

No, you shouldn't need to do that. Having re-installed them what do you see in package.json and is there a file package-lock.json?