# Raspberry PI3 Nodered launch error

**URL:** <https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393>\
**Category:** General\
**Created:** [29 October 2018 18:52 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393 "2018-10-29T18:52:13Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![wtrk](https://avatars.discourse-cdn.com/v4/letter/w/97f17d/32.png) [@wtrk](https://discourse.nodered.org/u/wtrk)\
**Post date:** [29 October 2018 18:52 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/1 "2018-10-29T18:52:13Z")

</div>

I have problem with my node-red in RPI3.

Why always gives an error, The error log is

29 Oct 21:38:57 - [info] Starting flows  
TypeError: Cannot read property 'config' of null  
at addWidget (/home/pi/.node-red/node\_modules/node-red-dashboard/index.js:63:39)  
at Object.addWidget (/home/pi/.node-red/node\_modules/node-red-dashboard/index.js:115:20)  
at new ListNode (/home/pi/.node-red/node\_modules/node-red-contrib-ui\_list/ui\_list.js:79:27)  
at createNode (/usr/lib/node\_modules/node-red/red/runtime/nodes/flows/Flow.js:305:18)  
at Flow.start (/usr/lib/node\_modules/node-red/red/runtime/nodes/flows/Flow.js:89:35)  
at start (/usr/lib/node\_modules/node-red/red/runtime/nodes/flows/index.js:328: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)

---

<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:** [29 October 2018 18:52 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/2 "2018-10-29T18:52:58Z")

</div>

what version of Node-red, nodejs and dashboard are you running?

---

<div class="post-metadata">

**Author:** ![wtrk](https://avatars.discourse-cdn.com/v4/letter/w/97f17d/32.png) [@wtrk](https://discourse.nodered.org/u/wtrk)\
**Post date:** [29 October 2018 18:59 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/3 "2018-10-29T18:59:08Z")

</div>

Node-RED version: v0.19.4  
[info] Node.js version: v8.11.1  
[info] Linux 4.14.78-v7+ arm LE  
[info] Dashboard version 2.10.1 started at /ui

---

<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:** [29 October 2018 19:07 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/4 "2018-10-29T19:07:05Z")

</div>

What happens if you start Node-RED with a new flows file?

copy your current flows file into a different directory and then restart Node-RED

---

<div class="post-metadata">

**Author:** ![wtrk](https://avatars.discourse-cdn.com/v4/letter/w/97f17d/32.png) [@wtrk](https://discourse.nodered.org/u/wtrk)\
**Post date:** [29 October 2018 19:10 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/5 "2018-10-29T19:10:22Z")

</div>

Problem is that node-red never start, if node-red start after deployment again stopping, and waiting always.  
So dont make a copy or move a copy

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [29 October 2018 19:12 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/6 "2018-10-29T19:12:44Z")

</div>

Delete the module node-red-contrib-ui\_list as it is causing the issue. You can do that by running `npm remove node-red-contrib-ui_list` in the directory `~/.node-red/`.

A question then from @dceejay and @nisiyama as to what could cause this error.

---

<div class="post-metadata">

**Author:** ![wtrk](https://avatars.discourse-cdn.com/v4/letter/w/97f17d/32.png) [@wtrk](https://discourse.nodered.org/u/wtrk)\
**Post date:** [29 October 2018 19:21 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/7 "2018-10-29T19:21:35Z")

</div>

> [@knolleary](#):
>
> npm remove node-red-contrib-ui\_list

I did uninstall but same again.

29 Oct 22:18:30 - [info] Starting flows  
TypeError: Cannot read property 'config' of null  
at addWidget (/home/pi/.node-red/node\_modules/node-red-dashboard/index.js:63:39)  
at Object.addWidget (/home/pi/.node-red/node\_modules/node-red-dashboard/index.js:115:20)  
at new ListNode (/home/pi/.node-red/node\_modules/node-red-contrib-ui\_list/ui\_list.js:79:27)  
at createNode (/usr/lib/node\_modules/node-red/red/runtime/nodes/flows/Flow.js:305:18)  
at Flow.start (/usr/lib/node\_modules/node-red/red/runtime/nodes/flows/Flow.js:89:35)  
at start (/usr/lib/node\_modules/node-red/red/runtime/nodes/flows/index.js:328: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)  
29 Oct 22:18:31 - [info] Started flows  
29 Oct 22:18:31 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/)

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [29 October 2018 19:39 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/8 "2018-10-29T19:39:57Z")

</div>

Can you see `/home/pi/.node-red/node_modules/node-red-contrib-ui_list` is mentioned in that stack trace? That tells me you haven't removed it... The module is still there.

What command did you run to remove that module and in what directory did you run it?

---

<div class="post-metadata">

**Author:** ![wtrk](https://avatars.discourse-cdn.com/v4/letter/w/97f17d/32.png) [@wtrk](https://discourse.nodered.org/u/wtrk)\
**Post date:** [29 October 2018 19:43 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/9 "2018-10-29T19:43:22Z")

</div>

> [@knolleary](#):
>
> Can you see `/home/pi/.node-red/node_modules/node-red-contrib-ui_list` is mentioned in that stack trace? That tells me you haven't removed it... The module is still there.
> 
> What command did you run to remove that module and in what directory did you run it?

I started this command but when I looked node\_modules, ui\_list is still there.

May I delete it manually ?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [29 October 2018 19:50 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/10 "2018-10-29T19:50:31Z")

</div>

> [@wtrk](#):
>
> I started this command but when I looked node\_modules, ui\_list is still there.

I asked what command you ran and what directory you ran it in. I want to make sure you ran what I said to run in the right directory - because if you had done so, it would have removed the module.

If you really doesn't work, then delete the `/home/pi/.node-red/node_modules/node-red-contrib-ui_list` directory manually.

---

<div class="post-metadata">

**Author:** ![nisiyama](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nisiyama/32/85_2.png) [@nisiyama](https://discourse.nodered.org/u/nisiyama)\
**Post date:** [30 October 2018 02:09 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/11 "2018-10-30T02:09:47Z")

</div>

The reason of the error seems that the belonging group of `ui_list` is not configured in node settings panel.

![conf](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/d/de5d1ca6ccbf0e3299c2a735c2455d91c56887b2.png)

I think the error will disappear if it is configured.  
But it would be better for error handling to be performed more appropriately. Will make PR on this.

---

<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:** [30 October 2018 09:52 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/12 "2018-10-30T09:52:29Z")

</div>

Umm shouldn't node-red-contrib-ui\_list be coded such that this isn't a problem??

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [30 October 2018 10:19 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/13 "2018-10-30T10:19:12Z")

</div>

Yes... which is why @Nisiyama said:

> [@nisiyama](#):
>
> Will make PR on this.

---

<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:** [30 October 2018 11:50 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/15 "2018-10-30T11:50:41Z")

</div>

@knolleary I may have assumed wrongly, I thought he was going to create a PR against NR itself.

Since he is the creator of the node-red-contrib-ui\_list node, I didn't think he would need a PR to add code to his new node to prevent this situation.

---

<div class="post-metadata">

**Author:** ![nisiyama](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nisiyama/32/85_2.png) [@nisiyama](https://discourse.nodered.org/u/nisiyama)\
**Post date:** [30 October 2018 13:02 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/16 "2018-10-30T13:02:13Z")

</div>

Hi, all  
Released new version of `ui_list` node with error handling of Dashboard group configuration .

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [30 October 2018 19:03 UTC](https://discourse.nodered.org/t/raspberry-pi3-nodered-launch-error/4393/17 "2018-10-30T19:03:51Z")

</div>

Though yes we should probably look to see if the core can help prevent this if at all possible. We’ve only just started to allow extra dashboard widgets so we are finding out as we go.