Z-Wave JS UI problems with port permission

Add-ons Bindings
1

Supplement: On my test system rasbian pi 3 B with razberry image on debian bullseye 11.1.

I installed z-wave js ui to test it for my usecase (instead of using z-way) befor i try out the openhab-z-wave js binding.

I can start the web-ui on port 8091 and i can set the detected serial port /dev/ttyAMA0

i get an error: opening serial port /dev/ttyAMA0
2026-10-19 20:08:43.120 DRIVER Failed to open the serial port: Error: Operation not permitted, cannot open /dev/ttyAMA0

I checked the permission for dialout user
i checked no other service connected to the port
tried chmod 666 or 777 /dev/ttyAMA0

but no success

Maybe there are no rights because accessing from another pc over web-ui?

Any ideas?

2

Based on your other thread, do you have Z-Way or the Zigbee binding running? Like I said on that thread, only one service can access physical device at a time.

3

Add OH with the zw binding installed to that list, for the same reason.

4

You’re right, in this thread i better had to explain that i used my test system (the other is the live system). In the tessystem i would like to try out the functions of the z-wave js ui software against the z-way software to manage my z-wave network.

The Test System in the moment is a raspberry pi 3 B with an z-way debian image, called razberry image. Its on bullseye 11.1.

Because only one service can access I disabled z-way-Server and zbw_connect. After that i installed the z-wave ui.

It seems tat the z-wave js ui can connect to the /ttyAMA0 port, but has no permission.
But i cant find help for that.

5

(post deleted by author)

6

Openhab is not running jet on that system.
First i tried to install z-wave js ui to check this out.

If this runs then i will try to install openhab with z-wave js binding.

7

I installed the z-wave js ui with snap.

Now i learned its a snap problem with raspi 3 getting port access?!

Dont know what snap is (docker? container?) and how to solve this.

8

Yes, snap is another system like docker except for packages, not containers (I use zwave-js-ui snap without issues). Sounds like your serial port is not configured correctly in zwave-js-ui settings. In settings there is a drop down under serial port. It should list available ports (something like /dev/serial/by-id/usb-xxxxxxxxxxx, and using this format vs /dev/ttyUSBX or /dev/ttyACMX is generally best practice for persistence). Your stick should show there. If it’s already selected and still not connecting, you may have another service using it and creating a conflict.

If you find the stick and it still doesn’t work, restarting the snap with the correct serial port can help:

sudo snap restart zwave-js-ui