Dashboard empty since new releases

Dashboard
21

I already asked: where can I find the log you are talking about?

Regarding the login: it’s the standard raspberry logging and it’s only for this test.

Other loggings are seriously different.

Thierry Eggen

Avenue Rogier 13

B-1030 Bruxelles

Tel : +32 2 215 27 74

thierry@eggen.be

22

Just run the commands as requested and copy/paste the full output here.
node-red-stop
Now check that the editor is not accessible in the browser
node-red-log
Break out of that output
node-red
Now copy/paste the whole output you see from and including the stop command to the end.

23

Another thought that may help us to understand what is going on. Before you do the test above, edit the file settings.js in your .node-red directory, and change the log level to Trace.

24

Hi Colin,

This is the same as what I sent previously. Nothing new.

Thanks for your patience.

Thierry

pi@marquise:~ $ node-red-stop

Stop Node-RED

Use node-red-start to start Node-RED again

pi@marquise:~ $ node-red-log

23 Sep 10:41:01 - [info] Dashboard version 3.2.0 started at /ui

23 Sep 10:41:01 - [info] Settings file : /home/pi/.node-red/settings.js

23 Sep 10:41:01 - [info] Context store : 'default' [module=memory]

23 Sep 10:41:01 - [info] User directory : /home/pi/.node-red

23 Sep 10:41:01 - [warn] Projects disabled : editorTheme.projects.enabled=false

23 Sep 10:41:01 - [info] Flows file : /home/pi/.node-red/flows.json

23 Sep 10:41:01 - [info] Server now running at http://127.0.0.1:1880/

23 Sep 10:41:01 - [warn]

25

Notice that after running node-red-stop that the log does not show that node-red has stopped. That probably means that your flows in node-red are hanging for some reason.

Run node-red-stop and node-red-log again and wait for several minutes and I expect you will see the flows stopped message appear.

26

Just to be clear, node-red-dashboard is the framework for the dashboard. In order to see things (like charts and gauges etc) you have to add them to your flow and send some data to them. Do you have ui nodes installed and being fed data?

Also, please export your flow and attach it to a reply.

In order to make code readable and usable it is necessary to surround your code with three backticks (also known as a left quote or backquote ```)

``` 
   code goes here 
```

You can edit and correct your post by clicking the pencil :pencil2: icon.

See this post for more details - How to share code or flow json

27

Hi Paul,

The last test seems to dhow that it stopped correctly, see below (start and then stop).

You”ll find the json code below.

In fact I am using Nodered with success since a couple year with some sophisticated UIs (I2C, UART, MQTT, delays, and node-red-dashboard with switches, leds, meters…).

The problem happens since an new PI OS release or Nodered release (or both that don’t like each other).

It’s only the dashboard that causes a problem. A test with MQTT to I2C and vice versa is OK.

Thanks for your time,

Thierry

i@marquise:~ $ node-red-start

Start Node-RED

Once Node-RED has started, point a browser at http://10.0.0.42: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.

23 Sep 16:11:52 - [info]

Welcome to Node-RED

28

What in there says that it was stopped?

In a separate window run
node-red-log
and leave it running. Then in the first window run
node-red-stop
and go back to the log window. Does it say node-red has stopped? You should see something like this in the log window when you run node-red-stop

Stopping Node-RED graphical event wiring tool...
23 Sep 16:38:41 - [info] Stopping flows
23 Sep 16:38:41 - [info] Stopped flows
nodered.service: Succeeded.
Stopped Node-RED graphical event wiring tool.
29

Where? I see no attache code.

30

Yes I got that and posted it.

Thierry Eggen

Avenue Rogier 13

B-1030 Bruxelles

Tel : +32 2 215 27 74

thierry@eggen.be

31

It was below the log but seems to be “forgotten” by the mail.

Anyway, it does not explain why it works since two years and suddenly stop working only with node-red-dashboard on 3 different new installations done “as it’s said in the book”.

So I’ll will wait until new releases are coming out.

Thanks a lot for you time and efforts.

Thierry

Thierry Eggen

Avenue Rogier 13

B-1030 Bruxelles

Tel : +32 2 215 27 74

thierry@eggen.be

32

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