I’ve seen someone else having the same error on my Discord server. Not using Conbee II, but error looks the same. Not sure why this would happen. Did you try rebooting Synology?
@robertklep I see that you used the 25426 branch which is not the version of the kernel that runs on the original released DSM 7.0 (there you have linux 4.4.59 and DSM 7.0 comes with 4.4.180; at least that what I can see on my DS718+).
Not sure how you convinced the module to load if the versions are different.
Did you tweak the Makefile manually and changed the version? Or it just worked also with a different version.
I’ve tried to cross compile the kernel from the 7.0 Beta folder and that one was even older and surely it did not load.
I only extract the relevant driver files from the sources on Sourceforge, the actual crosscompilation is done against the official Synology DSM 7 toolkit for the different platforms (as explained here).
So basically, I’m taking the driver source file from 4.4.59, but it’s compiled against 4.4.180 (at least, I assume that’s what the toolkit uses, I’m haven’t really looked at the specifics on how the crosscompilation process works 
).
I don’t think the sources for the actual current branch (41890) are available (yet).
By the way, I’m not compiling the actual kernel, just the two USB serial modules, using this project as a template: GitHub - SynologyOpenSource/HelloKernel: This is synology example package for cross-compiling kernel module.
I experienced this on DSM6 when i had to reboot the vm - but not always only sometimes …
That is te reason why I have my conbee connected to the docker container from Marthoc. That works 100% of the time.
It is also the reason that I’m not upgrading to DSM 7. To much uncertainty
Had some time today and figured why it worked. You basically used the old kernel files (the modules themselves) and compiled them (cross compiled) for the platform without using any kernel version information. And because the modules likely did not change (or better said the system calls in the modules are the same in the 4.4.59 and 4.4.180) and the kernel cannot check the module version (actually it just throws a warning that kernel version information is not present in the module) then it just works loading it.
Still waiting for Synology to publish the real kernel sources so I can properly compile them.
PS: A small tip for who wants to load @robertklep modules with modprobe: You need to run depmod -a but that is not present (at least not on my NAS). It is enough to create a symlink called depmod towards the real executable called kmod and then you can run it. That will allow you to use modprobe instead of insmod (which will load all the other needed kernel modules automatically, ie usbcore, if that is not loaded already)
2 Likes
Hi @jprates
Did you already upgrade to DSM7? If so - did your Aeotec Gen5 stick start to work out-of-the-box or you had to add these startup scripts provided by Carsten? I mean these ones
I’d really like to upgrade to DSM7 for a couple of reasons, but I’ll wait until the dust on DSM7 settles and the USB topic is clear.
I think if we don’t have USB support from Synology - adding it on our own may be risky as they may somehow cut it down with some DSM 7 upgrade and these solutions may stop working for good at some point.
Let me know how it went. I’ve got the same ZWave stick as you.
Thanks!
It worked out of the box, no scripts needed whatsoever, its working fine ever since the upgrade.
1 Like
Nice! Great to hear that. ZWave is my only show stopper for migrating to DSM7. Thanks for letting me know!
Oh maybe one more question: are you running HA within VMM or in DSM Docker?
Virtual Machine.
You’re welcome, glad to assist.
1 Like
After rebooting then, it’s been 24 days and never had any disconnection issues on the DSM7 so far.
1 Like
I believe the topic is clear: Synology stopped supporting these devices, and the community has to find its own ways to get them working again.
They can’t test every single device on earth to list as supported device.
As it stands, the device in question is working fine, no issues whatsoever, and the system is stable.
But the solution Synology chose for DSM7 (just remove all support) is a like trying to kill a fly with a sledgehammer.
Hi all
I’m have been a SmartThings user for 6 years, and I’m on the edge of trying out Home Assisstant using Docker on my Synology NAS, and with the Aeotec Z-Stick 7.
-
I have not updated to DSM 7 yet. It looks like many of you have had success of getting z-wave stick working on DSM 7, so would you recommend updating to DSM 7, or would you recommend to hold on?
-
I am NOT a linux person, at all!
Does anyone have a link to the best guide on how to install HA on Synology DSM 7 (if you can recommend updating to 7) AND getting connection to Zwave stick to work?
I find various guides out there, but they are for DSM 6.
Thank you in advance
Hi All, I noticed Jadahl published DSM 7.0 USB drivers. Anybody had a chance to try it? I am on DS918+ with zzh (CC2652R) and Aeotec Z-Stick Gen5 USB devices.
1 Like
sudo insmod /lib/modules/usbserial.ko > /dev/null 2>&1
sudo insmod /lib/modules/ftdi_sio.ko > /dev/null 2>&1
sudo insmod /lib/modules/cdc-acm.ko > /dev/null 2>&1
sudo insmod /lib/modules/cp210x.ko > /dev/null 2>&1
sudo insmod /lib/modules/ch341.ko > /dev/null 2>&1
I’m a relative newby when it comes this. I prepared to moved to DSM7 by moving from Docker to a VM. The move went smoothly. The Zwave stick worked. I thought that now was the time to upgrade. After the upgrade the USB stick still appears in the config for the VM, but I can’t seem to find in in HA. Is there a better thread or has any progress been made with this?
I updated to dms 7 today and my conbee2 and Aeotec Z-Stick Gen5 stick is not showing up 
edit
if i ssh with sudo and type this 3 lines after every nas reeboot it works:
modprobe usbserial
modprobe ftdi_sio
modprobe cdc-acm
Any better automatic way ?
1 Like