Java Runtime Environment: which java platform is used and what version
openHAB version: 2.1.0
Issue of the topic: I have run OpenHAB 2.1.0 in a Docker container on a synology DSM and when i will add the z-wave stick i get the status error OFFLINE - COMMUNICATION_ERROR zwave.thingstate.serial_notfound
This is my docker run command:
sudo docker run --name openHAB2test -u root --net=host -e “EXTRA_JAVA_OPTS=-Dgnu.io.rxtx.SerialPorts=-Dgnu.io.rxtx.SerialPorts=/dev/ttyUSB0:/dev/ttyS0:/dev/ttyS2:/dev/ttyACM0:/dev/ttyAMA0” -v /etc/localtime:/etc/localtime:ro -v /etc/TZ:/etc/timezone:ro -v /volume1/docker/openHAB2test/addons/:/openhab/addons -v /volume1/docker/openHAB2test/conf/:/openhab/conf -v /volume1/docker/openHAB2test/userdata/:/openhab/userdata --device=/dev/ttyACM0 --privileged=true openhab/openhab:2.1.0-amd64-debian
Maybe someon has the same issue, i also tried to add sudo adduser openhab dialout and sudo adduser openhab tty
But this not solved the problem for me.
in the shell of openhab i can find the /dev/ttyACM0 folder.
I have now added these 2 scribts on the syno, in the docker container i have now the same rights (crw-rw---- 1 root dialout 166, 0 Feb 26 09:40 /dev/ttyACM0) but i have not the openhab user on the synology, the openhab user is only in the container, in the docker container i have added the user to the groups, but the problem is the same, i will try today to give the stick on the synology full acces ( chmod 777 /dev/ttyAM0)
This was working, but when i has stopped the container and startet it, the zwave stick was not working anymore, then you need to restart the synology, than i had to run the commando always after a DSM reboot.
It was a great experience with docker, but there were always such small issues.
It was never so easy to expand the system with new sticks etc., so i have installed openhab on a raspberry pi.
Just stopping and starting the container works for me.
But after each DSM restart I have to execute the chmod command again.
So I think I have to start looking for some config to make this persistent. Maybe udev rules are a way to go…
I am also struggling with the Aeotec Gen5 USB stick.
chmod 777 /dev/ttyACM0 helps for me; but doing that after each restart is not a solution.
The udev rule is great - but somehow it is not working for me. After each restart the stick is still dev/ttyACM0 and not “USBzwave”
I did not create the homeautomation group and therefore removed the “GROUP=homeautomation” part in the rules-file.
Is this necessary? If yes; how do I add user root the group? Any other hints what I might do wrong?
I probably have the same problem that was solved here a year and a half ago.
Unfortunately my technical understanding is at the level that is assumed here.
Perhaps I may go back and check again (ah, I forgot to say that I am trying out Openhab3/Mileston 2 in the container):
Basically I don’t know how I can enter the CMOD command in the Docker App in the DSM? It looks like this for me:
is the stick online if you restart the container or do you need to restart to synology?
this was also a problem the time i used it, when i have done some changes and need to reboot openhab (container), than zwave was not working anymore