I also have a rflink gateway that needs a ch341.ko driver therefore I had to install the drivers described here: GitHub - robertklep/dsm7-usb-serial-drivers: Synology DSM 7 USB serial drivers
This fixed the loading both of the drivers after a restart for me.
The rules for setting access rights are also needs as @gd35 describes.
Thanks for the info. It should work with the Aeotec S2.
I recently updated my synology with DSM 7.0.1-42218 and my USB sticks (Aeotec S2 + conbee) do not work anymore… I did all the steps I mentioned in my previous posts but nothing works this time.
When I run the lsusb command, I got this:
|__usb1 1d6b:0002:0404 09 2.00 480MBit/s 0mA 1IF (Linux 4.4.180+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub
|__1-2 0463:ffff:0100 00 1.10 1.5MBit/s 20mA 1IF (EATON Ellipse PRO P354L35PYT)
|__1-3 05e3:0610:9224 09 2.10 480MBit/s 100mA 1IF (GenesysLogic USB2.0 Hub ffffffd6ffffffa3ffffffebffffffc0) hub
|__1-3.3 0658:0200:0000 02 2.00 12MBit/s 100mA 2IFs ( ffffffd1ffffffb2ffffffdbffffffad)
|__1-3.4 1cf1:0030:0100 02 2.01 12MBit/s 100mA 2IFs (dresden elektronik ingenieurtechnik GmbH ConBee II DE2407255)
|__1-4 f400:f400:0100 00 2.00 480MBit/s 200mA 1IF (Synology DiskStation 6500822839CA6049)
|__usb2 1d6b:0003:0404 09 3.00 5000MBit/s 0mA 1IF (Linux 4.4.180+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub
|__2-1 0bc2:231a:0710 00 3.00 5000MBit/s 896mA 1IF (Seagate Expansion NAAR8ZK1)
|__2-3 05e3:0612:9224 09 3.00 5000MBit/s 0mA 1IF (GenesysLogic USB3.0 Hub ffffffd6ffffffa3ffffffebffffffcb) hub
I have the two devices created with the correct permissions
/dev/ttyACM1
/dev/ttyACM2
But OpenHab (in a container managed by Docker) cannot access the zwave device…
Are there anybody having the same problem ?
Eventually, it works but it seems that the new version of DSM does not really take into account my "50-usb-zwave.rules” file in /lib/udev/rules.d
SUBSYSTEM==“tty”, ATTRS{idVendor}==“0658”, ATTRS{idProduct}==“0200”, SYMLINK+=“ttyACM1”, MODE=“0666”
SUBSYSTEM==“tty”, ATTRS{idVendor}==“1cf1”, ATTRS{idProduct}==“0030”, SYMLINK+=“ttyACM2”, MODE=“0666”
So the devices do no appear with the correct names. I have had to modify the environment variables in the two containers (Deconz and OpenHAB) to provide the correct ones. But there is a chance to have different device names in a next reboot of my synology…
I have something similar.
I could map the devicenames with the 99-rules and access this names directly at the Synology console.
But if I try to map my devices via the json-import at the Docker-UI, Docker removes the device section at any startup. No chance to map the sys-link device names to UI. If I run the Container privileged, I could access the device by system name /dev/ttyacm0 at least.
I did no progress on this issue waiting a reboot of my synology to try to see what is the cause of the problem. I am thinking to move OpenHAB from my Synology to a rpi4 in a din box installed in the electrical board of my house.
Updating OpenHAB with newer version will be much easier by the way.
Hi
I have had some issues with using the “docker run” command.
I then switched to create the docker container from the command line and run it from the Web UI this has worked better. I use this command.
sudo docker create --name openhab-3.1 --no-healthcheck --net=host --device=/dev/ttyACM0 --device=/dev/ttyUSB0 -v /etc/localtime:/etc/localtime:ro -v /etc/TZ:/etc/timezone:ro -v /volumeUSB1/usbshare/docker/openhab-3.1/addons:/openhab/addons -v /volumeUSB1/usbshare/docker/openhab-3.1/conf:/openhab/conf -v /volumeUSB1/usbshare/docker/openhab-3.1/userdata:/openhab/userdata -e "EXTRA_JAVA_OPTS=-Duser.timezone=Europe/Copenhagen" -e "JAVA_HOME=/usr/lib/jvm/default-jvm" -e "OPENHAB_HTTP_PORT=8089" -e "OPENHAB_HTTPS_PORT=8449" -e "USER_ID=1042" -e "GROUP_ID=65539" openhab/openhab:3.1.0
The “–no-healthcheck” can be removed I added it to try and reduce the disk activity and allow hibernation of the disks.
You properly need to change the USER_ID and GROUP_ID to match your system.
Thanks to have shared this. I used “run” instead of “create”. I have had to stop the container and then run it with the UI. I will use this command when I will update OpenHAB with the next milestone version.
By the way, is there something specific to use the HomeKit service while running OpenHAB within a docker container ? I have the known issue of the HomeKit service that stopped working after a couple of days. I tried the solution mentioned in the community forum, but the problem is still not solved. I have to restart the HomeKit bundle on a regular basis.
For the new update on DSM 7 and missing the ttyACM0 a nice tutorial is written by Marius Bogdan Lixandru, see Synology: How to Add USB Support on DSM 7 – Marius Hosting