I confirm that the Aeotec Gen-5 is recognized when running DSM 7.0 providing you executed the three modprob commands mentioned earlier. Its device name is /dev/ttyACMx (x=1 for my setup since the Deconz USB stick appears as /dev/ttyACM0). The Aeotec S2 required extra modules that are not available today. They were available here: http://www.jadahl.com for DSM 6.2. Unfortunately, it seems that they will not be ported to DSM 7.0.
My setup: DS218+ running DSM 7.0. Openhab is hosted in a docker container with zigbee/zwave devices
But now I have to move all my zwave devices to the new USB stick…
Do you use “execute container using high privilege” when running the docker container ?
I can not get it to work unless I do that and I did not use to need that under DSM 6.2
I changed the permissions for the zwave and zigbee devices (/dev/ttyACMx) to allow the container to get access to the devices. But you have to do it each time you unplug/plug the USB sticks and after the boot. Not really optimal. But more secure than giving privilege mode to the container.
It looks like its is changed. I also tried setting the user and group to root with full premissions this does not work either.
To map the device into the container I use an docker import file with a modified json were I added
It looks like I go it working now. I am a bit unsure what made it work, I think there was something with the group that was wrong. I used your “sudo docker run …” command and that made the \dev\ttyACM0 work but because my openhab user does not have id 9001 I need set the -e “USER_ID=1042” -e “GROUP_ID=65539” also. When the container is created via the above commad it does
echo ‘Create user openhab with id 1042’
And a lot of other commands that I think it did not do that earlier and I think this is what makes the difference.
You can then plug and unplug the Aeotec Gen5 and you will see that the correct permissions have been applied. Moreover, it will always appear with the name ttyACM1 (this is important for me since I have also a zigbee USB stick and I am not sure at boot time, what will be its symbolic name: either ttyACM0 or ttyACM1. This can be done for other USB sticks but you will need to change the idVendor and the idProduct (use “lsusb -ciu” to get these ids).
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.
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 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.
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.
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.