search

zwave-js / node-red-contrib-zwave-js

The most powerful, high performing and highly polished Z-Wave node for Node-RED based on Z-Wave JS. If you want a fully featured Z-Wave framework in your Node-RED instance, you have found it.
MIT License
47 stars 6 forks source link

[Help]: File Location and meaning of error #272

Closed felafel closed 1 year ago

felafel commented 1 year ago

How can we help?

1_ "Z-Wave JS Logging" section shows the log filename but it does not show the folder location. You must know where the file is being saved. Please list that location. A hyperlink would be even better.

2_ "Error listing serial ports" is something I am seeing but since I am supplying the exact [usb] port that zwave JS is using I do not understand why this is listing anything. I also do not understand why this port is not being used.

A good tutorial would be helpful.

Thanks in advance

Version

March 2023 I think. Where do I find it?

Node-RED Version

3.0.2

What hardware are you using?

Other Linux

Any code to add?

No response

marcus-j-davies commented 1 year ago

1_ "Z-Wave JS Logging" section shows the log filename but it does not show the folder location. You must know where the file is being saved. Please list that location. A hyperlink would be even better.

You can't access the log file from the browser, so a hyperlink is pointless. The default log file is In the Node RED user directory /home/<user>/.node-red/zwave-js.log if using Node RED normally.

The log file name you see, is if you want to change its name and location, its an absolute path.

2_ "Error listing serial ports" is something I am seeing but since I am supplying the exact [usb] port that zwave JS is using I do not understand why this is listing anything. I also do not understand why this port is not being used.

Just because you set a custom port, doesn't mean it should stop listing what pots are found when opening up the configuration.

And if you're getting that error, then normally its a permissions problem in the OS, Setting a custom port to force it isn't going to solve a permissions issue.

You need to ensure the User that is running Node RED has the correct permission to access, read, and write to serial ports.

sudo usermod -a -G dialout some-user

If that does nothing, then some other OS (or layer) specific problem is preventing Node RED accessing serial ports.

A good tutorial would be helpful.

https://github.com/zwave-js/node-red-contrib-zwave-js/wiki/getting-started

felafel commented 1 year ago

I am using Node RED inside Home Assistant [HA}.

Thanks for the reply. I will try to find the log file and see what it says. I think it is not in the location you posted because HA is running inside Docker.

marcus-j-davies commented 1 year ago

If your using Home Assistant, your mileage is going to vary.

The serial port package is infamous for being problematic under Alpine that runs Node RED under Home Assistant, you need to rebuild the binary (as the serial port package, uses Native modules)

1) within the Shell of the Node RED image, run npm rebuild.

2) Ensure the ports are correctly mapped/setup in your docker file

Sadly I can't help with either, as I do not use Home Assistant.

See here

https://github.com/zwave-js/node-red-contrib-zwave-js/discussions/246#discussioncomment-4023531

felafel commented 1 year ago

I realized after starting this thread that I did not need this package since the devices are in Home Assistant.