Replies: 5 comments 4 replies
-
Does the user that is running the container has the permissions to access the serial device? If you could share your docker compose file it could be easier to debug this. |
Beta Was this translation helpful? Give feedback.
-
This is almost certainly a permissions issue. Either your docker instance can't access the by-id device file, or the process can't access the /dev/zwave one inside the container. Make sure your docker user is in the dialout group on the host. I agree that seeing your docker compose would help. |
Beta Was this translation helpful? Give feedback.
-
I don't know how containers work on TrueNAS Scale, so another possible problem could be the controller soft-reset. You can try disabling that in the Z-Wave settings. We need more information to provide any help. https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/app_crash |
Beta Was this translation helpful? Give feedback.
-
I'm having a similar problem. I'm running docker as rootless with the user 'ubuntu' which is in the dialout group. 'Silly' Level logs are below. I'm running from a Makefile like this:
Could this be because its rootless docker ? I know that there are limitations when running rootless but I cannot find anything that specifically mentions serial devices. |
Beta Was this translation helpful? Give feedback.
-
I am running mine native on Raspberry Pi OS with |
Beta Was this translation helpful? Give feedback.
-
I am attempting to set up zwavejs2mqtt on TrueNAS Scale. I have a Zooz zwave stick and in the container settings I have it mapped (by-id) to /dev/zwave. The container is running as the "apps" user (no sudo privs) but the container is privileged. However, I keep getting an error in the web ui that says the driver failed to open the serial port (permission denied). Any ideas what I can check/change to get through this?
Beta Was this translation helpful? Give feedback.
All reactions