[Bug]:

[fabnavigator]

Contact Details (optional)

[email protected]

What happened?

I followed the instructions:

cd ~/.node-red
npm install node-red-contrib-zwave-js@beta --force

and node-red doesn't start now.

Note: I run node-red in a docker container.

*** I know you said "Please raise issues on PR #204", but I didn't see how to do that.

How to reproduce?

I restart the node-red docker container.

Version

7.0.0

Node-RED Version

2.2.2

What hardware are you seeing the problem on?

Raspberry Pi

Relevant Z-Wave-JS log output

> [email protected] start
> node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"
29 Apr 16:34:34 - [info] 
Welcome to Node-RED
===================
29 Apr 16:34:34 - [info] Node-RED version: v2.2.2
29 Apr 16:34:34 - [info] Node.js  version: v16.13.1
29 Apr 16:34:34 - [info] Linux 5.15.32-v8+ arm64 LE
29 Apr 16:34:35 - [info] Loading palette nodes
29 Apr 16:34:39 - [info] Dashboard version 3.1.6 started at /ui
29 Apr 16:34:39 - [info] Settings file  : /data/settings.js
29 Apr 16:34:39 - [info] Context store  : 'default' [module=localfilesystem]
29 Apr 16:34:39 - [info] Context store  : 'memory' [module=memory]
29 Apr 16:34:39 - [info] User directory : /data
29 Apr 16:34:39 - [warn] Projects disabled : editorTheme.projects.enabled=false
29 Apr 16:34:39 - [info] Flows file     : /data/flows.json
29 Apr 16:34:39 - [info] Server now running at http://127.0.0.1:1880/
29 Apr 16:34:39 - [info] Starting flows
29 Apr 16:34:40 - [info] Started flows
npm ERR! path /usr/src/node-red
npm ERR! command failed
npm ERR! signal SIGSEGV
npm ERR! command sh -c node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"
npm ERR! A complete log of this run can be found in:
npm ERR!     /data/.npm/_logs/2022-04-29T20_34_41_543Z-debug.log

/data/.npm/_logs/2022-04-29T20_34_41_543Z-debug.log:

0 verbose cli [
0 verbose cli   '/usr/local/bin/node',
0 verbose cli   '/usr/local/bin/npm',
0 verbose cli   '--no-update-notifier',
0 verbose cli   '--no-fund',
0 verbose cli   'start',
0 verbose cli   '--cache',
0 verbose cli   '/data/.npm',
0 verbose cli   '--',
0 verbose cli   '--userDir',
0 verbose cli   '/data'
0 verbose cli ]
1 info using [email protected]
2 info using [email protected]
3 timing npm:load:whichnode Completed in 1ms
4 timing config:load:defaults Completed in 6ms
5 timing config:load:file:/usr/local/lib/node_modules/npm/npmrc Completed in 3ms
6 timing config:load:builtin Completed in 3ms
7 timing config:load:cli Completed in 7ms
8 timing config:load:env Completed in 1ms
9 timing config:load:file:/usr/src/node-red/.npmrc Completed in 0ms
10 timing config:load:project Completed in 4ms
11 timing config:load:file:/.npmrc Completed in 0ms
12 timing config:load:user Completed in 1ms
13 timing config:load:file:/usr/local/etc/npmrc Completed in 1ms
14 timing config:load:global Completed in 1ms
15 timing config:load:validate Completed in 1ms
16 timing config:load:credentials Completed in 3ms
17 timing config:load:setEnvs Completed in 5ms
18 timing config:load Completed in 32ms
19 timing npm:load:configload Completed in 32ms
20 timing npm:load:setTitle Completed in 1ms
21 timing npm:load:setupLog Completed in 2ms
22 timing config:load:flatten Completed in 11ms
23 timing npm:load:cleanupLog Completed in 7ms
24 timing npm:load:configScope Completed in 0ms
25 timing npm:load:projectScope Completed in 2ms
26 timing npm:load Completed in 57ms
27 timing command:run-script Completed in 8490ms
28 timing command:start Completed in 8501ms
29 verbose stack Error: command failed
29 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/index.js:64:27)
29 verbose stack     at ChildProcess.emit (node:events:390:28)
29 verbose stack     at maybeClose (node:internal/child_process:1064:16)
29 verbose stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
30 verbose pkgid [email protected]
31 verbose cwd /usr/src/node-red
32 verbose Linux 5.15.32-v8+
33 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "--no-update-notifier" "--no-fund" "start" "--cache" "/data/.npm" "--" "--userDir" "/data"
34 verbose node v16.13.1
35 verbose npm  v8.1.2
36 error path /usr/src/node-red
37 error command failed
38 error signal SIGSEGV
39 error command sh -c node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"
40 verbose exit 1

[marcus-j-davies]

Hi @fabnavigator, zwave js V9 will convert files - does the container have write permissions.
Disclaimer; I know nothing about docker

[marcus-j-davies]

I currently can't think of anything else that would cause a black out like this.
nothing is pointing at the zwave module causing it - but the files write access is my only assumption

the only thing I can see is this:
29 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/index.js:64:27) which is not connected to anything zwave

Can you enable any further logging?

[fabnavigator]

I was able to get back to 6.5.5 and everything is working again. I will look into the permissions issue.

[fabnavigator]

If I recall, I initially had issues when I installed with npm. Everything worked when I installed using Manage Palette from with node-red. Is there a way to install the beta version from the Manage Palette UI?

[marcus-j-davies]

OK - it might be the serial port update (it now uses V10 of serial port), which changes compilation.
can you try the following in your Node-RED docker container?

npm install serialport - to see what happens?

Is there a way to install the beta version from the Manage Palette UI?

there isn't sadly (at least to my knowledge)

[fabnavigator]

bash-5.0# npm list
[email protected] /usr/src/node-red
+-- [email protected]
`-- [email protected]

It looks like it worked. What now?

[marcus-j-davies]

ok and a restart if NR is still fine?

again I know nothing about docker 😁

[fabnavigator]

I did a restart. NR is still okay.

[marcus-j-davies]

ok,

now npm install node-red-contrib-zwave-js@beta
Ensure your console environment is the one that NR is running under.

I don't know how docker works - but I do know console commands can use a different node version that NR its self is using -which can have complications.

I therefore suggest any console commands are under the same umbrella as NR - what ever that means 😅

installs are fine so far - but docker adds a layer that I don't know enough about, if needs be, I'll try it here

[marcus-j-davies]

Im going to move this to a convo - I like to keep things on issues related to release versions

[fabnavigator]

I'm not making any progress. What about: If I recall, I initially had issues when I installed with npm. Everything worked when I installed using Manage Palette from with node-red. Is there a way to install the beta version from the Manage Palette UI??

[marcus-j-davies]

There is currently no way todo it via the UI, until I release the main version.

OR may be there is......
can you add an exec node in your flow and run ls? and capture its output

[fabnavigator]

core
node_modules
package.json

[marcus-j-davies]

ok how about ls -a

[fabnavigator]

.
..
core
node_modules
package.json

[marcus-j-davies]

ls ./node_modules

[marcus-j-davies]

I was expecting to see /.node-red 😆

[fabnavigator]

@babel
@mapbox
@node-red
@sindresorhus
@szmarczak
@types
abbrev
accepts
acorn
acorn-walk
agent-base
ajv
ansi-colors
append-field
argparse
array-flatten
async
async-mutex
asynckit
axios
balanced-match
base64-js
basic-auth
bcryptjs
bl
body-parser
boolbase
brace-expansion
buffer
buffer-from
busboy
bytes
cacheable-lookup
cacheable-request
cheerio
cheerio-select
chownr
cli-table
clone
clone-response
colors
combined-stream
commist
concat-map
concat-stream
content-disposition
content-type
cookie
cookie-parser
cookie-signature
core-util-is
cors
cronosjs
css-select
css-what
debug
decompress-response
defer-to-connect
delayed-stream
denque
depd
destroy
dicer
dom-serializer
domelementtype
domhandler
domutils
duplexify
ee-first
encodeurl
end-of-stream
enquirer
entities
escape-html
esprima
etag
express
express-session
fast-deep-equal
finalhandler
follow-redirects
form-data
forwarded
fresh
fs-extra
fs-minipass
fs.notify
fs.realpath
get-stream
glob
got
graceful-fs
hash-sum
help-me
hpagent
htmlparser2
...

[marcus-j-davies]

OK how about core? ls ./core

[marcus-j-davies]

we are looking for the flows Nodes folder

[fabnavigator]

"ls .." returns "node-red"

[marcus-j-davies]

Ok can you do ls ./core/node-red - we might be getting close

[marcus-j-davies]

usually the node red user directory is /home/<User>/.node-red but docker messes with that

[fabnavigator]

In installed it that way, and the controller status is "[Net: 1] All nodes ready."

[marcus-j-davies]

Hooray!!

[marcus-j-davies]

you are now on V7 BETA 1

[marcus-j-davies]

the New UI is different but much better

[marcus-j-davies]

here is the new UI guide.

[marcus-j-davies]

Any problems add a small comment about the bug on the bottom of PR

#204

[marcus-j-davies]

"[Net: 1] All nodes ready."

Yep - as it now supports multiple networks

[fabnavigator]

Will do. Thank you!

[marcus-j-davies]

No - thank you.
I will make the guys aware of serilaport.

but in theory you can now stick to using ser2net - as your stick can be on a different computer if you wish (as long as you install ser2net on said machine)

[fabnavigator]

I will.

[marcus-j-davies]

Hi @fabnavigator
I am addressing some of the issues you raised.

One I am looking at currently is the errors you received when selecting nodes.

• This was not evident in Alpha tests or the current Beta test with others.

could you advise what browser you are using, so I can try and replicate it - we currently can't

[fabnavigator]

Google Chrome Version 101.0.4951.41 (Official Build) (64-bit).

[fabnavigator]

Interesting. Back when I said the target value is always FALSE, I noticed on another node that the target valus id always TRUE.

[marcus-j-davies]

Target Value is not really hooked into any event mechanism.
Target Value will be updated when you first open up the UI - we can't sync it, as no event is available to hook into.

in other words, the UI will show what was last set, when the device is selected.

Target Value - the value you asked to set
Current Value - the current known value that is Actually set.

[fabnavigator]

Is it possible that the cannot fetch value is related to the use of ser2net?

[marcus-j-davies]

so are you still getting it?
getValue does not use serial data - so it shouldn't be

[fabnavigator]

Yes. I just got it a few minutes ago.

[marcus-j-davies]

can you debug the browser (view console) - none of us are getting it 😭
I think its developer tools

[marcus-j-davies]

The only time the UI will use serial data is when sending a change to a device - anything other is all local data.

[marcus-j-davies]

I log errors in the browser - so it should be telling us why it errored.
you will get a "cannot get..." when;

• the browser got fed up of waiting
• there is an issue with the backend server (that helps the UI to run)

so Currently trying to find out why you get this.

I have slowed down my browser to 3G speeds - but yet it produces what I need - Its very strange

[fabnavigator]

I got this error in the console:

vendor.js?v=2.2.2:2 Uncaught Error: cannot call methods on editableList prior to initialization; attempted to call method 'addItem'
    at Function.error (vendor.js?v=2.2.2:2:2589)
    at HTMLOListElement.<anonymous> (vendor.js?v=2.2.2:10:5615)
    at Function.each (vendor.js?v=2.2.2:2:2976)
    at s.fn.init.each (vendor.js?v=2.2.2:2:1454)
    at s.fn.init.t.fn.<computed> [as editableList] (vendor.js?v=2.2.2:10:5357)
    at c (red.min.js?v=2.2.2:18:31920)
    at red.min.js?v=2.2.2:18:31985
error @ vendor.js?v=2.2.2:2
(anonymous) @ vendor.js?v=2.2.2:10
each @ vendor.js?v=2.2.2:2
each @ vendor.js?v=2.2.2:2
t.fn.<computed> @ vendor.js?v=2.2.2:10
c @ red.min.js?v=2.2.2:18
(anonymous) @ red.min.js?v=2.2.2:18
setTimeout (async)
c @ red.min.js?v=2.2.2:18
(anonymous) @ red.min.js?v=2.2.2:18
setTimeout (async)
c @ red.min.js?v=2.2.2:18
(anonymous) @ red.min.js?v=2.2.2:18
setTimeout (async)
c @ red.min.js?v=2.2.2:18
(anonymous) @ red.min.js?v=2.2.2:18
setTimeout (async)
c @ red.min.js?v=2.2.2:18
(anonymous) @ red.min.js?v=2.2.2:18
setTimeout (async)
c @ red.min.js?v=2.2.2:18
_addChildren @ red.min.js?v=2.2.2:18
(anonymous) @ vendor.js?v=2.2.2:10
_addSubtree @ red.min.js?v=2.2.2:18
(anonymous) @ vendor.js?v=2.2.2:10
addItem @ red.min.js?v=2.2.2:18
insertItemAt @ red.min.js?v=2.2.2:18
(anonymous) @ vendor.js?v=2.2.2:10
addItem @ red.min.js?v=2.2.2:18
(anonymous) @ vendor.js?v=2.2.2:10
(anonymous) @ vendor.js?v=2.2.2:10
each @ vendor.js?v=2.2.2:2
each @ vendor.js?v=2.2.2:2
t.fn.<computed> @ vendor.js?v=2.2.2:10
data @ red.min.js?v=2.2.2:18
(anonymous) @ vendor.js?v=2.2.2:10
(anonymous) @ vendor.js?v=2.2.2:10
each @ vendor.js?v=2.2.2:2
each @ vendor.js?v=2.2.2:2
t.fn.<computed> @ vendor.js?v=2.2.2:10
buildPropertyTree @ client.js:2699
(anonymous) @ client.js:2656
e @ vendor.js?v=2.2.2:2
t @ vendor.js?v=2.2.2:2

[fabnavigator]

But I didn't see the problem when that error came up.

[fabnavigator]

I just got the error, and this was in the console:

​  POST http://192.168.0.11:1880/zwave-js/1/cmd net::ERR_NETWORK_CHANGED
(anonymous) @ unknown
send @ vendor.js:2
ajax @ vendor.js:2
s.ajax @ vendor.js:4
ControllerCMD @ client.js:868
getValue @ client.js:2817
renderPropertyElement @ client.js:2777
(anonymous) @ client.js:2692
(anonymous) @ client.js:2691
buildPropertyTree @ client.js:2682
(anonymous) @ client.js:2656
e @ vendor.js:2
t @ vendor.js:2
setTimeout (async)
(anonymous) @ vendor.js:2
c @ vendor.js:2
fireWith @ vendor.js:2
fire @ vendor.js:2
c @ vendor.js:2
fireWith @ vendor.js:2
l @ vendor.js:2
(anonymous) @ vendor.js:2
load (async)
send @ vendor.js:2
ajax @ vendor.js:2
s.ajax @ vendor.js:4
ControllerCMD @ client.js:868
getProperties @ client.js:2649
selectNode @ client.js:2576
(anonymous) @ client.js:2464
setTimeout (async)
(anonymous) @ client.js:2459
dispatch @ vendor.js:2
v.handle @ vendor.js:2
​  POST http://192.168.0.11:1880/zwave-js/1/cmd net::ERR_NETWORK_CHANGED
...

[marcus-j-davies]

Right! - this is helpful!

There are LOTS of these.
http://192.168.0.11:1880/zwave-js/1/cmd net::ERR_NETWORK_CHANGED

The connection to the UI Server is being interrupted, and this will indeed throw up the error message on the UI.

Now here is the sad part, that's nothing I can control.
in essence, Google Chroms connection to zwave-j UI s is being changed mid communications.

Do you have a VPN, Proxy of any kind - filtering that type of thing?

I quote.

Google Chrome usually experiences this error when it detects a change in the IP address of your PC. Each device, on all networks, is assigned with a distinct IP address which helps in connecting to the internet. Your Internet Service Provider (ISP) and website owners apply certain restrictions based on your IP address.

https://www.troubleshootingcentral.com/how-to-fix-the-err-network-changed-error-in-google-chrome/

The UI now deals with errors in more structured way, and will halt if there is a problem, its very likely this has been happening for sometime, but the new UI is now letting you know.

I'm not sure what I can do here if I'm honest, as its unrelated to the UI specially.

do you use IPV6? - as I have seen this error be mentioned. when a browser is jumping between IPv4 and 6

[fabnavigator]

And what about this error?

Uncaught Error: cannot call methods on editableList prior to initialization; attempted to call method 'addItem'
    at Function.error (vendor.js?v=2.2.2:2:2589)
    at HTMLOListElement.<anonymous> (vendor.js?v=2.2.2:10:5615)
    at Function.each (vendor.js?v=2.2.2:2:2976)
    at s.fn.init.each (vendor.js?v=2.2.2:2:1454)
    at s.fn.init.t.fn.<computed> [as editableList] (vendor.js?v=2.2.2:10:5357)
    at c (red.min.js?v=2.2.2:18:31920)
    at red.min.js?v=2.2.2:18:31985
```

[fabnavigator]

I'm getting that even on 6.5.5 clicking on the nodes.

[marcus-j-davies]

I'm not sure, I can only imagine its something that the NR UI engine is doing, but can't.
addItem that seems to be the cause is being called when it shouldn't be.

We use a treeList not editableList therefore don't call addItem - so it's something internal to NR.

If this is happening on 6.5.5 also. - I wouldn't worry too much, but I wonder if ERR_NETWORK_CHANGED is actually causing this issue. i.e the NR UI engine is not able to fully initialise certain things because of the interruption. 🤷

It might just be debug tourettes and can be ignored

[fabnavigator]

I don't think that the network changed error is causing it, because it happens lots when there isn't a network changed error.

Maybe there is something you can check before you execute some of your treeList code to prevent this error.

[marcus-j-davies]

Yeah - the error is coming from deep within the jquery library, so will be very hard to find out why this is happening.
I will need to monitor other reports being raised to begin to understand why its happening 👍

[fabnavigator]

Breaking news: I connected the RPi to ethernet instead of wifi and haven't been able to reproduce the network changed error. That being said, this wasn't an issue on 6.5.5 and I've been on wifi all of the time.

I have Google fiber with their router/wifi, and I know it is a bit odd the way it handles things. Could be related to that.

[marcus-j-davies]

Oh that's good news 👍 - nice to know

7.0.0 protects against an error propagating down the stack (that will have a potential for the error to get worse) - its likely, it has been happening for sometime - but 7.0.0 is now handling it correctly.

Still good news!

[fabnavigator]

When I double-click on an item and get the information dialog, with the "Add to Filter Set" button, it doesn't work well if there isn't sufficient screen height to fit all of the information into the dialog box. Can the dialog check how much height is available and shrink down, and add a vertical scroll bar?

[fabnavigator]

The UI monitor dialog doesn't have this issue.

[marcus-j-davies]

I will look to size the windows based on screen size - but I need to account for the amount of data each of this windows are to show.
it won't be immediate

[fabnavigator]

Whatever you are doing with the UI monitor dialog is working, and that is able to contain lots of information.

[fabnavigator]

I imagine there is no easy way for the network map to keep track of where you position the nodes, so that they are where you moved them to the next time you open the map.

[marcus-j-davies]

There isn't,
There is a mathematical equation happening to keep the nodes distant from each other - which sadly does not give us control

There are networks with 180+ nodes - so we use an algorithm to strategically place the nodes in the mesh.

I will be pushing out BETA 2 shortly - which has map improvements. - Keep an eye on the PR for the update 👍

[fabnavigator]

So, I didn't have the console window open, so I didn't get to see if there was a network changed issue, but I got this dialog:

It's like what I saw before, but before there was no "Node undefined does not exist." message.

[marcus-j-davies]

BETA 2 also has a different mouse/keyboard combination

• Single click : Node Select (List CC/Values)
• A 2nd Click : Show Options
• Shift+Click : Show Options (Without Select) - i.e to remove a failed node

[fabnavigator]

I turned off node grouping and was fairly quickly single-clicking on different nodes, not waiting for the the properties to be fetched. It happened again, but I can't get it happen when I want.

[fabnavigator]

I think this has something to do with the toggle node grouping feature.

[fabnavigator]

Yes. Using that toggle and selecting nodes I can get it to error out pretty easily.

[marcus-j-davies]

In BETA 2 I have removed a purposeful delay, which is now no longer there, BETA 1 may have a race condition, but hopefully BETA 2 may have solved it.

[fabnavigator]

BTW. There are lots of things I like in 7.0.0.

[marcus-j-davies]

BTW. There are lots of things I like in 7.0.0.

V7 has undergone a review of various things - the extra message info/new UI etc etc

[fabnavigator]

I'm on Beta2.

When I select "Custom Path..." for the Serial Port, it would be nice for the edit box to be populated with whatever I had previously set in the custom path so I could edit it. If I want to change it I have to type in the entire value.

[marcus-j-davies]

@fabnavigator

it would be nice for the edit box to be populated with whatever I had previously set in the custom path so I could edit it

Should be no problem.

I have no reports of problems in BETA 2 with the discord community, could you also confirm?

[fabnavigator]

@marcus-j-davies,

Yes, I can confirm.