Dashboard is not working anymore

#1

Hi community,

First of all: sorry for my english…

i got a Problem with my Dashboard, after i finished programming some Nodes and adding their data to the Dashboard, i shut my raspberry down.
After i reboot it this morning again and wanted to check my Dashboard, it doesn t worked any longer.
There is always this message:
Welcome to the Node-RED Dashboard
Please add some UI nodes to your flow and redeploy.

but i already added some ui Dashboard notes…

could any one help my to fix this Problem?

#2

It would be useful to see the log that Node-RED prints when you start it.

Also have you installed any other nodes that include the word “dashboard”? If you have these unfortunately stop the node-red-dashboard from working. You should delete them and then restart Node-RED

#3

here is what node red prints:

Node-Red start

Start Node-RED

Once Node-RED has started, point a browser at http://192.168.1.44:1880
On Pi Node-RED works better with the Firefox or Chrome browser

Use node-red-stop to stop Node-RED
Use node-red-start to start Node-RED again
Use node-red-log to view the recent log output
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot

To find more nodes and example flows - go to http://flows.nodered.org

Starting as a systemd service.
Started Node-RED graphical event wiring tool.
14 Jun 10:42:53 - [info]
Welcome to Node-RED

14 Jun 10:42:53 - [info] Node-RED version: v0.18.6
14 Jun 10:42:53 - [info] Node.js version: v8.11.2
14 Jun 10:42:53 - [info] Linux 4.14.34-v7+ arm LE
14 Jun 10:42:54 - [info] Loading palette nodes
14 Jun 10:42:59 - [info] Dashboard version 2.9.4 started at /ui
14 Jun 10:43:00 - [warn] ------------------------------------------------------
14 Jun 10:43:00 - [warn] [node-red-bluemix-nodes/tcp] ‘tcp request’ already registered by module node-red
14 Jun 10:43:00 - [warn] [node-red-bluemix-nodes/udp] ‘udp out’ already registered by module node-red
14 Jun 10:43:00 - [warn] ------------------------------------------------------
14 Jun 10:43:00 - [info] Settings file : /home/pi/.node-red/settings.js
14 Jun 10:43:00 - [info] User directory : /home/pi/.node-red
14 Jun 10:43:00 - [warn] Projects disabled : editorTheme.projects.enabled=false
14 Jun 10:43:00 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
14 Jun 10:43:00 - [info] Server now running at http://127.0.0.1:1880/
14 Jun 10:43:00 - [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.

14 Jun 10:43:01 - [info] Starting flows
TypeError: Cannot read property ‘id’ of undefined
at createSubflow (/usr/lib/node_modules/node-red/red/runtime/nodes/flows/Flow.js:362:61)
at Flow.start (/usr/lib/node_modules/node-red/red/runtime/nodes/flows/Flow.js:97:41)
at start (/usr/lib/node_modules/node-red/red/runtime/nodes/flows/index.js:327:29)
at tryCatchReject (/usr/lib/node_modules/node-red/node_modules/when/lib/makePromise.js:845:30)
at runContinuation1 (/usr/lib/node_modules/node-red/node_modules/when/lib/makePromise.js:804:4)
at Fulfilled.when (/usr/lib/node_modules/node-red/node_modules/when/lib/makePromise.js:592:4)
at Pending.run (/usr/lib/node_modules/node-red/node_modules/when/lib/makePromise.js:483:13)
at Scheduler._drain (/usr/lib/node_modules/node-red/node_modules/when/lib/Scheduler.js:62:19)
at Scheduler.drain (/usr/lib/node_modules/node-red/node_modules/when/lib/Scheduler.js:27:9)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
14 Jun 10:43:02 - [info] Started flows
14 Jun 10:43:03 - [info] [sqlitedb:6573ca80.1e0d34] opened /tmp/sqlite ok
14 Jun 10:43:36 - [info] Stopping flows
14 Jun 10:43:36 - [info] Stopped flows
14 Jun 10:43:36 - [info] Starting flows
TypeError: Cannot read property ‘id’ of undefined
at createSubflow (/usr/lib/node_modules/node-red/red/runtime/nodes/flows/Flow.js:362:61)
at Flow.start (/usr/lib/node_modules/node-red/red/runtime/nodes/flows/Flow.js:97:41)
at start (/usr/lib/node_modules/node-red/red/runtime/nodes/flows/index.js:327:29)
at /usr/lib/node_modules/node-red/red/runtime/nodes/flows/index.js:164:21
at tryCatchReject (/usr/lib/node_modules/node-red/node_modules/when/lib/makePromise.js:845:30)
at runContinuation1 (/usr/lib/node_modules/node-red/node_modules/when/lib/makePromise.js:804:4)
at Fulfilled.when (/usr/lib/node_modules/node-red/node_modules/when/lib/makePromise.js:592:4)
at Pending.run (/usr/lib/node_modules/node-red/node_modules/when/lib/makePromise.js:483:13)
at Scheduler._drain (/usr/lib/node_modules/node-red/node_modules/when/lib/Scheduler.js:62:19)
at Scheduler.drain (/usr/lib/node_modules/node-red/node_modules/when/lib/Scheduler.js:27:9)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
14 Jun 10:43:38 - [info] Started flows

i don t have any other nodes including the word Dashboard…

#4

Do you need the following nodes that you have installed?

They are for use in Bluemix but you have it installed on a raspberry pi. Try deleting them and restarting node-red.

#5

i already tried to delet them but node red says they are in use, what they defenetly aren t…

#6

Unbenannt

#7

So that suggests you are using the mongoldb nodes. If you are definitely not…

In a terminal
node-red-stop

cd ~/.node-red

and then

npm uninstall node-red-bluemix-nodes

then restart Node-RED

#8

okay now the terminal says:

picture

Unbenannt

but i defenitly had no node in my flow which is called mongoDB

#9

If you look at the menubar in Node-RED there is a “Search flows” option and see if you can find it

Otherwise look at “Configuration nodes”

1 Like
#10

yes thank u i fix it now :slight_smile:

#11

Which one was it? A node or a configuration node?

#12

probably it was a configuration node which blocked my Dashboard ui. So i deleted all background nodes and stuff i don’t needed any more and now it works.
I hope it is still working tomorrow