search

Adorkable / node-red-contrib-ui-led

A simple LED status indicator for the Node-RED Dashboard
MIT License
16 stars 12 forks source link

WHen starting Node-Red I see this message in the log #60

Closed Just-another-pleb closed 3 years ago

Just-another-pleb commented 3 years ago

Jan 08 12:49:19 TelePi Node-RED[1429]: While constructing LEDNode widget: TypeError: Cannot read property 'config' of null

Node-Red: 1.2.6 RasPi: ZW Stretch.

Not sure if it is really a problem, but it looks like one.

yoiang commented 3 years ago

Hey @Just-another-pleb ! Thanks for pointing this out. I've just pushed a new rewritten version 0.4.2 using the latest node-red and node-red-dashboard.

Let me know if this resolves the issue for you, if not can you see if there are any logs in the browser console or in the Node-RED console?

Just-another-pleb commented 3 years ago

When I check via node-red I am only seeing 0.3.3. I have 0.3.1.

I guess that update hasn't propagated through to that part of the system yet.

Oh, sorry but I am seldom at that that part of the scheme and don't see that message very often.

yoiang commented 3 years ago

Strange! Flows has been updated, I think that should be node-red palette’s source for latest versions. I’ll look into it!

On Tue, Jan 12, 2021 at 1:57 PM Just-another-pleb notifications@github.com wrote:

When I check via node-red I am only seeing 0.3.3. I have 0.3.1.

I guess that update hasn't propagated through to that part of the system yet.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/Adorkable/node-red-contrib-ui-led/issues/60#issuecomment-759061651, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAV45WNCHTSONDAIT7JD7LSZTATVANCNFSM4VZZSWNQ .

-- Sent from a bad keyboard

Just-another-pleb commented 3 years ago

Um, not sure if this is related.

I just updated the LED node.

Now when I run NR, it is maxed out at 100% cpu load and I see this being displayed when I start NR.

13 Jan 09:37:32 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable
13 Jan 09:37:33 - [info] Flows file     : /home/pi/.node-red/flows_TelePi.json
13 Jan 09:37:34 - [info] Server now running at http://127.0.0.1:1880/
13 Jan 09:38:18 - [info] Starting flows
While constructing LEDNode widget: TypeError: Cannot read property 'config' of null
    at addWidget (/home/pi/.node-red/node_modules/node-red-dashboard/index.js:73:39)
    at Object.addWidget (/home/pi/.node-red/node_modules/node-red-dashboard/index.js:137:48)
    at new LEDNode (/home/pi/.node-red/node_modules/node-red-contrib-ui-led/led.js:41:28)
    at Object.createNode (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/util.js:493:31)
    at Flow.start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:194:48)
    at start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/index.js:345:33)
    at process._tickCallback (internal/process/next_tick.js:68:7)
13 Jan 09:39:10 - [info] [cronplus:Monthly] createTask - index: 0, static: true, opt:

There is more above it, but this is maybe of interest.

yoiang commented 3 years ago

This is with the latest version 0.4.2?

On Tue, Jan 12, 2021 at 2:49 PM Just-another-pleb notifications@github.com wrote:

Um, not sure if this is related.

I just updated the LED node.

Now when I run NR, it is maxed out at 100% cpu load and I see this being displayed when I start NR.

13 Jan 09:37:32 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable 13 Jan 09:37:33 - [info] Flows file : /home/pi/.node-red/flows_TelePi.json 13 Jan 09:37:34 - [info] Server now running at http://127.0.0.1:1880/ 13 Jan 09:38:18 - [info] Starting flows While constructing LEDNode widget: TypeError: Cannot read property 'config' of null at addWidget (/home/pi/.node-red/node_modules/node-red-dashboard/index.js:73:39) at Object.addWidget (/home/pi/.node-red/node_modules/node-red-dashboard/index.js:137:48) at new LEDNode (/home/pi/.node-red/node_modules/node-red-contrib-ui-led/led.js:41:28) at Object.createNode (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/util.js:493:31) at Flow.start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:194:48) at start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/index.js:345:33) at process._tickCallback (internal/process/next_tick.js:68:7) 13 Jan 09:39:10 - [info] [cronplus:Monthly] createTask - index: 0, static: true, opt:

There is more above it, but this is maybe of interest.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/Adorkable/node-red-contrib-ui-led/issues/60#issuecomment-759086659, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAV45UTQ6RYHN6AKKOW3NDSZTGV7ANCNFSM4VZZSWNQ .

-- Sent from a bad keyboard

Just-another-pleb commented 3 years ago

No sorry all the palette updater will offer me is (Argh!) I went and looked and it now is offering the latest version.

Hang on.

(I won't waste time posting this and then updating the result.)

Ok, its booted.

This is what I now see:

(exert)

13 Jan 10:18:59 - [info] Starting flows
TypeError: Cannot read property 'config' of null
    at addWidget (/home/pi/.node-red/node_modules/node-red-dashboard/index.js:73:39)
    at Object.addWidget (/home/pi/.node-red/node_modules/node-red-dashboard/index.js:137:48)
    at new LEDNodeConstructor (/home/pi/.node-red/node_modules/node-red-contrib-ui-led/dist/nodes/ui_led/ui_led.js:25:29)
    at Object.createNode (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/util.js:493:31)
    at Flow.start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:194:48)
    at start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/index.js:345:33)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Different, but your node still gets a mention.

Again: not sure if this is a problem or not. I am only mentioning it.

yoiang commented 3 years ago

It shouldn't be doing that, def gonna try to track it down

yoiang commented 3 years ago

Offhand do you know what version of Node-RED Dashboard you have installed?

If it is a recent version it looks like this is where it Node-RED Dashboard tries to pull up information about the group and tab that any dashboard node is placed within and it's balking because it can't find the group assigned to a node:

https://github.com/node-red/node-red-dashboard/blob/31ad2c1ca396f63eabd1916c31fc28d5d6cdb49b/index.js#L72-L75 (either the group.config.tab access or the group.config.width)

Is it possible a node is assigned to an invalid group? Maybe a result of copy and pasting?

Just-another-pleb commented 3 years ago

Sorry. It is 2.26.0 I think on this machine.

I have 2.26.1 on another but am not going to risk installing it there.

This machine (just done) has few LEDs and isn't too off put by them being 2x1. Other machines have more detailed displays and need them to be 1x1 so it isn't worth me risking it.

I'll update the faulty machine to 2.26.2 now. Being a RasPi Z (W) it takes a while to update. Then I will have to restart NR. That too takes a while.

yoiang commented 3 years ago

If it is an invalid group I suspect updating won't fix the error you're seeing above which will affect a node's performance. Def don't worry about wrecking your other dashboard, I'll look into #63 and follow up there regarding the 2x1 vs 1x1

Just-another-pleb commented 3 years ago

I'll continue on the other thread.

yoiang commented 3 years ago

Now that the other issue is resolved are you still seeing the TypeError: Cannot read property 'config' of null log statement or any other error? I expect you should still be, #63 shouldn't affect it. If so and you haven't already I do think that maybe an LED node somewhere has an invalid group or tab assigned to it, however that could be possible!

yoiang commented 3 years ago

Hey @Just-another-pleb want to follow up and see if this is still an issue!

yoiang commented 3 years ago

I haven't heard back so closing for now. Let me know if we should look into it!

Just-another-pleb commented 3 years ago

Sorry, I was away for 2 weeks and you asked me just after I left. Thus no reply.

So there is no confusion, I will get my machine brought up to date and post back what I see.

Node-Red 1.2.6 UBUNTU Dashboard 2.26.2 LED 0.4.6

I don't know how to force an update of NR in UBUNTU. There is an easy peasy command for RasPi, but not Ubuntu, and if I run that, it errors. (I wonder why)

Error seen when starting NR:

me@me-desktop:~/.node-red$ node-red-start

Start Node-RED

Once Node-RED has started, point a browser at http://192.168.0.6: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.
29 Jan 12:23:15 - [info]
Welcome to Node-RED
===================
29 Jan 12:23:15 - [info] Node-RED version: v1.2.6
29 Jan 12:23:15 - [info] Node.js  version: v12.20.1
29 Jan 12:23:15 - [info] Linux 5.8.0-38-generic x64 LE
29 Jan 12:23:16 - [info] Loading palette nodes
29 Jan 12:23:17 - [info] +-----------------------------------------------------
29 Jan 12:23:17 - [info] | uibuilder initialised:
29 Jan 12:23:17 - [info] |   root folder: /home/me/.node-red/uibuilder
29 Jan 12:23:17 - [info] |   version . .: 2.0.1
29 Jan 12:23:17 - [info] |   packages . : vue,bootstrap,bootstrap-vue,jquery,socket.io
29 Jan 12:23:17 - [info] +-----------------------------------------------------
29 Jan 12:23:17 - [info] Dashboard version 2.26.2 started at /ui
29 Jan 12:23:17 - [warn] ------------------------------------------------------
29 Jan 12:23:17 - [warn] [node-red-node-sqlite/sqlite] Error: Cannot find module '/home/me/.node-red/node_modules/sqlite3/lib/binding/node-v72-linux-x64/node_sqlite3.node'
Require stack:
- /home/me/.node-red/node_modules/sqlite3/lib/sqlite3.js
- /home/me/.node-red/node_modules/node-red-node-sqlite/sqlite.js
- /usr/lib/node_modules/node-red/node_modules/@node-red/registry/lib/loader.js
- /usr/lib/node_modules/node-red/node_modules/@node-red/registry/lib/index.js
- /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/index.js
- /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/index.js
- /usr/lib/node_modules/node-red/lib/red.js
- /usr/lib/node_modules/node-red/red.js
29 Jan 12:23:17 - [warn] ------------------------------------------------------
29 Jan 12:23:17 - [info] Settings file  : /home/me/.node-red/settings.js
29 Jan 12:23:17 - [info] HTTP Static    : /home/me/.node-red/public
29 Jan 12:23:17 - [info] Context store  : 'default' [module=memory]
29 Jan 12:23:17 - [info] User directory : /home/me/.node-red
29 Jan 12:23:17 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable
29 Jan 12:23:17 - [info] Flows file     : /home/me/.node-red/flows_me-desktop.json
29 Jan 12:23:17 - [info] Server now running at http://127.0.0.1:1880/
29 Jan 12:23:17 - [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.
---------------------------------------------------------------------
29 Jan 12:23:18 - [info] Starting flows
TypeError: Cannot read property 'config' of null
    at addWidget (/home/me/.node-red/node_modules/node-red-dashboard/index.js:73:39)
    at Object.addWidget (/home/me/.node-red/node_modules/node-red-dashboard/index.js:137:48)
    at new LEDNodeConstructor (/home/me/.node-red/node_modules/node-red-contrib-ui-led/dist/nodes/ui_led/ui_led.js:27:29)
    at Object.createNode (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/util.js:493:31)
    at Flow.start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:194:48)
    at start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/index.js:345:33)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
TypeError: Cannot read property 'config' of null
    at addWidget (/home/me/.node-red/node_modules/node-red-dashboard/index.js:73:39)
    at Object.addWidget (/home/me/.node-red/node_modules/node-red-dashboard/index.js:137:48)
    at new LEDNodeConstructor (/home/me/.node-red/node_modules/node-red-contrib-ui-led/dist/nodes/ui_led/ui_led.js:27:29)
    at Object.createNode (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/util.js:493:31)
    at Flow.start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:194:48)
    at start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/index.js:345:33)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
29 Jan 12:23:18 - [error] [change:AUX] Invalid 'to' JSON property
29 Jan 12:23:18 - [info] Started flows
29 Jan 12:23:18 - [info] [udp in:d3745e21.23d568] udp listener at 0.0.0.0:6722
29 Jan 12:23:18 - [info] [udp in:b33c21bd.7a57c8] udp listener at 0.0.0.0:6723
29 Jan 12:23:18 - [info] [udp out:ff1b54c.cf5b5a8] udp re-use socket:  -> 192.168.0.21:6723
29 Jan 12:23:18 - [info] [mqtt-broker:TIMEPI MQTT] Connected to broker: mqtt://192.168.0.99:1883
29 Jan 12:23:18 - [warn] [function:Variable repeat time] Value set
29 Jan 12:23:18 - [warn] [function:Variable repeat time] Value set
29 Jan 12:23:21 - [warn] [function:Push Button] Setting up