Closed fabnavigator closed 2 years ago
Hi @fabnavigator, zwave js V9 will convert files - does the container have write permissions. Disclaimer; I know nothing about docker
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?
I was able to get back to 6.5.5 and everything is working again. I will look into the permissions issue.
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?
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)
bash-5.0# npm list
node-red-docker@2.2.2 /usr/src/node-red
+-- node-red@2.2.2
`-- serialport@10.4.0
It looks like it worked. What now?
ok and a restart if NR is still fine?
again I know nothing about docker 😁
I did a restart. NR is still okay.
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
Im going to move this to a convo - I like to keep things on issues related to release versions
Contact Details (optional)
wcmarinelli@gmail.com
What happened?
I followed the instructions:
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