# Node Red starts very slow and Dashboard losts connection

**URL:** <https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976>\
**Category:** General\
**Created:** [31 August 2019 12:36 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976 "2019-08-31T12:36:48Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![RudiRuessel](https://avatars.discourse-cdn.com/v4/letter/r/919ad9/32.png) [@RudiRuessel](https://discourse.nodered.org/u/RudiRuessel)\
**Post date:** [31 August 2019 12:36 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/1 "2019-08-31T12:36:48Z")

</div>

Hello,  
i installed two ds18b20 sensors on my raspberry pi. I startet with one sensor about 2 weeks ago and created a node red flow so i have the temperature on my dashboard. But since today when i start node red with "sudo node-red" i go to the browser and node red is loading very very long. When it is loaded sucsessfully I go to the dashboard and then there is a red warning "connection lost" in the right corner. Please help me!

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [31 August 2019 12:42 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/2 "2019-08-31T12:42:46Z")

</div>

Why are you using sudo?

---

<div class="post-metadata">

**Author:** ![RudiRuessel](https://avatars.discourse-cdn.com/v4/letter/r/919ad9/32.png) [@RudiRuessel](https://discourse.nodered.org/u/RudiRuessel)\
**Post date:** [31 August 2019 12:44 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/3 "2019-08-31T12:44:42Z")

</div>

I have no idea but it worked fine until today.

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [31 August 2019 12:49 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/4 "2019-08-31T12:49:43Z")

</div>

Well there’s no real need to use sudo

When you start Node-RED it displays log messages. please copy and paste those here

---

<div class="post-metadata">

**Author:** ![RudiRuessel](https://avatars.discourse-cdn.com/v4/letter/r/919ad9/32.png) [@RudiRuessel](https://discourse.nodered.org/u/RudiRuessel)\
**Post date:** [31 August 2019 12:54 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/5 "2019-08-31T12:54:28Z")

</div>

Sorry, but it`is in german

pi@raspberrypi:~ $ sudo node-red  
31 Aug 14:52:48 - [info]

# Willkommen bei Node-RED!

31 Aug 14:52:48 - [info] Node-RED Version: v0.20.7  
31 Aug 14:52:48 - [info] Node.js Version: v10.15.2  
31 Aug 14:52:48 - [info] Linux 4.19.58-v7+ arm LE  
31 Aug 14:52:55 - [info] Paletten-Nodes werden geladen  
31 Aug 14:53:05 - [info] Dashboard version 2.15.5 started at /ui  
31 Aug 14:53:08 - [info] Einstellungsdatei: /root/.node-red/settings.js  
31 Aug 14:53:08 - [info] Kontextspeicher: 'default' [module=memory]  
31 Aug 14:53:08 - [info] Benutzerverzeichnis: /root/.node-red  
31 Aug 14:53:08 - [warn] Projekte inaktiviert: editorTheme.projects.enabled=false  
31 Aug 14:53:08 - [info] Flow-Datei: /root/.node-red/flows\_raspberrypi.json  
31 Aug 14:53:08 - [warn]

* * *

Die Datei mit den Datenflowberechtigungsnachweisen wird mit einem vom System generierten Schlüssel verschlüsselt.

Wenn der vom System generierte Schlüssel aus irgendeinem Grund verloren geht, werden Ihre Berechtigungsnachweise  
Die Datei kann nicht wiederhergestellt werden. Sie müssen sie löschen und erneut eingeben.  
Ihre Berechtigungsnachweise.

## Sie sollten Ihren eigenen Schlüssel mit Hilfe der Option 'credentialSecret' in Ihre Einstellungsdatei. Node-RED wird dann Ihre Berechtigungsnachweise erneut verschlüsseln. Datei mit dem ausgewählten Schlüssel beim nächsten Deployen einer Änderung verwenden.

31 Aug 14:53:08 - [info] Flows starten  
31 Aug 14:53:08 - [info] Flows gestartet  
31 Aug 14:53:08 - [info] Server wird jetzt auf [http://127.0.0.1:1880/](http://127.0.0.1:1880/) ausgeführt

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [31 August 2019 13:36 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/6 "2019-08-31T13:36:50Z")

</div>

Have you got a chart on the dashboard? If so then what is the time range of the chart and how often are you sending new values?

---

<div class="post-metadata">

**Author:** ![RudiRuessel](https://avatars.discourse-cdn.com/v4/letter/r/919ad9/32.png) [@RudiRuessel](https://discourse.nodered.org/u/RudiRuessel)\
**Post date:** [31 August 2019 14:21 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/7 "2019-08-31T14:21:01Z")

</div>

Yes i have a chart. And i get every second a new value.

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [31 August 2019 14:28 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/8 "2019-08-31T14:28:12Z")

</div>

Every second?

And how many seconds of data are you displaying?

---

<div class="post-metadata">

**Author:** ![RudiRuessel](https://avatars.discourse-cdn.com/v4/letter/r/919ad9/32.png) [@RudiRuessel](https://discourse.nodered.org/u/RudiRuessel)\
**Post date:** [31 August 2019 14:41 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/9 "2019-08-31T14:41:49Z")

</div>

what do you mean with displaying?  
And is the data recordet?  
So you think that it works when i adjust it to every 10 seconds?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [31 August 2019 15:19 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/10 "2019-08-31T15:19:44Z")

</div>

In the settings for the chart you setup a time range (or number of points). If you have specified a range then work out how many seconds there are in that range. That will tell you how many points have to be shuffled down every time a new point is added. If you have multiple lines that has to be done for each line. So what is the total number of points are there on the chart? If it is more than a few hundred then it is pointless as there are only a certain number of pixels across the chart.

---

<div class="post-metadata">

**Author:** ![RudiRuessel](https://avatars.discourse-cdn.com/v4/letter/r/919ad9/32.png) [@RudiRuessel](https://discourse.nodered.org/u/RudiRuessel)\
**Post date:** [31 August 2019 16:33 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/11 "2019-08-31T16:33:58Z")

</div>

Nice! I have an intervall of 10 secs and it works. But my next problem is that i dont know how i get two different temperature gauges. I have the rpi-ds18b20 in my nodes but i dont know how to get two different gauges in my dashboard!

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [31 August 2019 16:36 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/12 "2019-08-31T16:36:24Z")

</div>

Add two gauge nodes and feed one from one sensor and the other from the other sensor.

---

<div class="post-metadata">

**Author:** ![RudiRuessel](https://avatars.discourse-cdn.com/v4/letter/r/919ad9/32.png) [@RudiRuessel](https://discourse.nodered.org/u/RudiRuessel)\
**Post date:** [31 August 2019 16:44 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/13 "2019-08-31T16:44:27Z")

</div>

and what is with the timestamp?  
And do you mean that i take the ds18b20 two times?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [31 August 2019 16:57 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/14 "2019-08-31T16:57:27Z")

</div>

Sorry, I don't understand. A gauge doesn't need a timestamp.  
What node type are you using to read the sensors? node-red-contrib-something probably.

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [31 August 2019 17:12 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/15 "2019-08-31T17:12:38Z")

</div>

Please don’t have two threads for the same problem (how to add two sensors). It just wastes people’s time

---

<div class="post-metadata">

**Author:** ![wgkowala](https://avatars.discourse-cdn.com/v4/letter/w/2bfe46/32.png) [@wgkowala](https://discourse.nodered.org/u/wgkowala)\
**Post date:** [24 February 2020 15:28 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/16 "2020-02-24T15:28:25Z")

</div>

After having this problem I unchecked the array checkbox in the DS18B20 node and it resolved.

---

<div class="post-metadata">

**Author:** ![echavet](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/echavet/32/24894_2.png) [@echavet](https://discourse.nodered.org/u/echavet)\
**Post date:** [30 June 2020 13:29 UTC](https://discourse.nodered.org/t/node-red-starts-very-slow-and-dashboard-losts-connection/14976/17 "2020-06-30T13:29:15Z")

</div>

Hello,  
I've had the same issue. It was taking near 4 minutes to load the dashboard without any idea of what was happening.  
Tried everything. Even ssl certificate renew, disabled authentication...  
Then I decided to change the log levels.... nothing.

So I've wait the request to end. The dashboard finally displayed. I went on the "configuration node" menu. And I had many unused config nodes. Because of uitable examples I had tested on tabs. I had deleted the nodes and the tabs but the configuration nodes were still there.  
I deleted them. And some other group nodes (that I shouldn't have deleted!!).  
Every thing now works well.  
So I think unused config nodes were slowing dramatically the ui. Wanted to share my experience.

update: I've just realized one of the group I deleted had a 4 days graph. It was probably the guilty one.  
update: actually still digging....