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
Hi @mpuff, quick question on this one: I’m currently having a similar issue (my Aeotec Z-Wave Gen5+ Stick sometimes stays offline after I reboot my Raspi, and only re-deploying the container solves the problem, see here). Is this similar to what you experienced / have you found a solution to that?
Wouter built a fork of the library and applied a fix
see here for info
The fix is in 3.3.0-SNAPSHOT build #2849 or newer.
If you still think you are having an issue, try to reproduce it and report on github
There is a link to the issue on github somewhere in that thread
I would be really happy to help / contribute. However, since I’m not that much of a pro, and am very happy that my current setup is somehow running stable (except for this problem with frequent Raspi disconnect problems but which appears to be a Raspi-specific problem) I am very reluctant to switch to another openHAB snapshot (if this is what would be needed from my side).