WHen starting Node-Red I see this message in the log #60
Comments
|
Hey @Just-another-pleb ! 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? |
|
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. |
|
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 ***@***.***> 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
<#60 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAV45WNCHTSONDAIT7JD7LSZTATVANCNFSM4VZZSWNQ>
.
--
Sent from a bad keyboard
|
|
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. There is more above it, but this is maybe of interest. |
|
This is with the latest version 0.4.2?
On Tue, Jan 12, 2021 at 2:49 PM Just-another-pleb ***@***.***> 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 ***@***.***/runtime/lib/flows/util.js:493:31)
at Flow.start ***@***.***/runtime/lib/flows/Flow.js:194:48)
at start ***@***.***/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
<#60 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAV45UTQ6RYHN6AKKOW3NDSZTGV7ANCNFSM4VZZSWNQ>
.
--
Sent from a bad keyboard
|
|
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) Different, but your node still gets a mention. Again: not sure if this is a problem or not. I am only mentioning it. |
|
It shouldn't be doing that, def gonna try to track it down |
|
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 Is it possible a node is assigned to an invalid group? Maybe a result of copy and pasting? |
|
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 I'll update the faulty machine to 2.26.2 now. Being a RasPi Z (W) it takes a while to update. |
|
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 |
|
I'll continue on the other thread. |
|
Now that the other issue is resolved are you still seeing the |
|
Hey @Just-another-pleb want to follow up and see if this is still an issue! |
|
I haven't heard back so closing for now. Let me know if we should look into it! |
|
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 I don't know how to force an update of NR in UBUNTU. Error seen when starting NR: |
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.
The text was updated successfully, but these errors were encountered: