Closed brystmar closed 2 years ago
Your USB path in settings is incorrect. You've mapped the device as /dev/zwave
inside the container. Your configuration should use /dev/zwave
.
Ahh, so because I mapped the device to /dev/zwave
in the docker run
command, I should use that mapped location as the path to the serial port. Learning new things every day, thank you :)
Checklist
Deploy method
Docker
Z-Wave JS UI version
8.2.2.4dd1414
ZwaveJS version
10.3.0
Describe the bug
When starting the container, it throws an error message about not being able to open the serial port, then appears to restart the service restarts every 12 seconds. I see error messages in both the Raspberry Pi terminal, and in red at the top of the UI.
The UI loads properly so I can navigate around and update settings, so I'm unsure if this is an issue with the UI or the backend.
The serial port name is copy/pasted directly from File Manager. I even tried setting
/dev/ttyUSB0
as the Z-Wave serial port in the UI, which throws the same error.I suspect this is a container permissions issue, but I don't know enough about containers to troubleshoot.
To Reproduce
Raspberry Pi 3B running Raspbian GNU/Linux 10 (buster). Per #2725, I also installed
libseccomp2
run
command:Expected behavior
I'd expect to not see the service throw errors and restart every ~12s. Eventual goal is for this Z-Wave stick to work with HASS, but we're definitely a few steps away from even thinking about that yet.
Additional context
Driver logs:
Here's my UI settings file w/keys truncated, in case it helps: