No Dashboard after Upgrade

Dashboard
1

Hi

I m using openhabian on a raspi device. After Upgrading to Openhab3 i upgraded node-red too (using the script) and even the nodes.
Now the Dashboard is still blank (Please add some UI nodes to your flow and redeploy.) Any idea ?

2

Is it showing the flows ok?

Please stop node-red and start it again in a terminal and post the full script you see in the terminal.

3

Hi flows showing ok, they work.

20 Jan 12:10:29 - [info]

Welcome to Node-RED

20 Jan 12:10:29 - [info] Node-RED version: v2.1.6
20 Jan 12:10:29 - [info] Node.js version: v12.22.9
20 Jan 12:10:29 - [info] Linux 5.10.63-v7l+ arm LE
20 Jan 12:10:31 - [info] Loading palette nodes
20 Jan 12:10:36 - [info] Dashboard version 2.23.2 started at /ui
20 Jan 12:10:36 - [warn] Missing node modules:
20 Jan 12:10:36 - [warn] - node-red-node-rbe (0.2.9): rbe
20 Jan 12:10:36 - [warn] - node-red-node-tail (0.1.1): tail
20 Jan 12:10:36 - [info] Removing modules from config
20 Jan 12:10:36 - [info] Settings file : /root/.node-red/settings.js
20 Jan 12:10:36 - [info] Context store : 'default' [module=memory]
20 Jan 12:10:36 - [info] User directory : /root/.node-red
20 Jan 12:10:36 - [warn] Projects disabled : editorTheme.projects.enabled=false
20 Jan 12:10:36 - [info] Flows file : /root/.node-red/start
20 Jan 12:10:36 - [info] Creating new flow file
20 Jan 12:10:36 - [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.

20 Jan 12:10:37 - [error] Unable to listen on http://127.0.0.1:1880/
20 Jan 12:10:37 - [error] Error: port in use

4

okay i think i did it

5

node-red (or something else using port 1880) is already running.
Stop that then try again (on a PI that would be node-red-stop)

Dont worry about these for now - easily fixed (RBE node replaced by the Filter node)

6

First was npm init to create package.json...

Finally i used to reinstall all dashboard related nodes. Now everything is working fine.

THX

7

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