Hi, did anyone manage to find the fix? I found this warning a little late and now my Z2M is broken.
Yes they work quite fine - I am using them right now.
Yes they are working fine… just use the link provided above
use the link that I have provided above
I have followed the same steps but for my NAS 1621+ drivers (taken from V1000) but still issue not fixed. Not sure what I am doing wrong.
Followed below document as well.
There was a time my SONOFF dongle recognised in different name under ttyACM0 and I could use it to modify Z2M config. All worked for about 30 min and USB disappeared again.
I can confirm my set up is working now on my Synology DS920+ & cc2531usb zigbee adapter. @surge919 feel free to update the topic for this thread.
Drivers are available for 7.2!
Unfortunately I can’t confirm it’s working on my DS420+ with the SONOFF dongle after having updated to DSM 7.2
All 7.2 drivers for geminilake will fail with “Invalid module format” after “trying to insmod”.
Any updates or ideas? thx
Just found a hint that I had the wrong download link for the modules.
The files within “raw” instead of “blob” work beautifully!
i.e. https://github.com/robertklep/dsm7-usb-serial-drivers/raw/main/modules/geminilake/dsm-7.2/ch341.ko
With those the modules can be inserted into the kernel without any problem.
Up and running again and happy 
1 Like
Did the upgrade yesterday and ran also into this problem, my Arduino RFlink came back fine but my ZigBee II usb stick did not connect to DECONZ.
I can confirm I have it all working now on my Synology DS1019+ where I have HA running on a virtual machine. The VM did see both USB devices but DECONZ did see the stick disconnected.
I mainly used the link @haproby posted, thanks! this needed a few tweaks so for the not so techn ical users like me, this is what worked for me, off course all credits to the original poster Scrapix!
You need to have SynoCommunity installed in the package center on your
SynoCommunity https://synocommunity.com/
Then install the Git package.
connect with a terminal to the Synology and do next command one by one
git clone https://github.com/robertklep/dsm7-usb-serial-drivers.git ~/DSM-USB-DRIVER/
replace the xxxxxx with your CPU package arch name from What kind of CPU does my Synology NAS have? - Synology Knowledge Center
sudo cp ~/DSM-USB-DRIVER/modules/xxxxxxxx/dsm-7.2/cp210x.ko /lib/modules
sudo chmod 644 /lib/modules/cp210x.ko
sudo chmod +x ~/DSM-USB-DRIVER/usb-serial-drivers.sh
sudo sh ~/DSM-USB-DRIVER/usb-serial-drivers.sh start
sudo cp ~/DSM-USB-DRIVER/usb-serial-drivers.sh /usr/local/etc/rc.d/
sudo sh /usr/local/etc/rc.d/usb-serial-drivers.sh start
Optionally you can add these tasks to the task manager in Synology to run at start or manual when the device is rebooted.
cp ~/DSM-USB-DRIVER/modules/xxxxxxxx/dsm-7.2/cp210x.ko /lib/modules
bash ~/DSM-USB-DRIVER/usb-serial-drivers.sh start
After this I could start the DECONZ add-on and the Conbee II was seen again.
Hope this helps someone!
4 Likes
Hi @modderhut, many many thanks for your message. After my synology update earlier today my Conbee 2 stick did not work anymore.
After following your instruction, all was OK again. Thanks for taking the time to write such a clear and concise instruction. You saved me a lot of hours of troubleshooting.
Dear all, I have read all the post carefully but still can’t solve my issue.
I can’t maintain my mqtt2zigbee installation up. I always get same error:
Let me tell you that I’m running mosquito-mqtt docker with no issues under Synology NAS and that issue is after installing docker of zigbee2mqtt and try to start up the docker service.
I get this error even after following the steps on this feed and can see properly the ttyUSB0 device when listing under dev$ directory.
Zigbee2MQTT:error 2023-08-19 20:41:52: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-08-19 20:41:52: Failed to start zigbee
Zigbee2MQTT:error 2023-08-19 20:41:52: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-08-19 20:41:52: Exiting...
Zigbee2MQTT:error 2023-08-19 20:41:52: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyUSB0'
at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:200:28)
at SerialPort._error (/app/node_modules/@serialport/stream/dist/index.js:75:22)
at /app/node_modules/@serialport/stream/dist/index.js:111:18
I think the origin of the error could be here:
Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyUSB0'
at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:200:28)
at SerialPort._error (/app/node_modules/@serialport/stream/dist/index.js:75:22)
at /app/node_modules/@serialport/stream/dist/index.js:111:18
Can someone help me to find the solution to my issue?
Thank you so much! I have spent a few hours to understand why I got the insmod error!
Edit: found the culprit! It took me several hours to figure it out. The VM for some reason lost connection with the dongle. It got dismounted. All I had to do is to mount it again from DSM control panel!
https://kb.synology.com/en-sg/DSM/tutorial/How_do_I_use_usb_drives_in_VMM
Original post:
I followed the above steps and I believe that I’m on the right track, however Home Assistant is failing to see the SONOFF stick form Settings>Hardware>All Hardware.
Home Assistant is running in a Virtual Machine.
I can see ttyAMC1 in Synology SSH when I type lsusb
or when I’m in the dev directory.
But for some reason it disappeared from Home Assistant, and zigbee2mqtt is failing to connect.
Zigbee2MQTT:error 2023-08-27 00:13:57: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-08-27 00:13:57: Failed to start zigbee
Zigbee2MQTT:error 2023-08-27 00:13:57: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-08-27 00:13:57: Exiting...
Zigbee2MQTT:error 2023-08-27 00:13:58: Error: Connection not initialized
This all happened out of the blue. Didn’t update HA, nor did I change anything in Synology. It just suddenly disappeared and all the zigbee devices are stranded in the middle of the desert…
1 Like
I can see my usb device in the /dev folder (ttyUSB0), and I can see and select that device inside zwavejs-ui. However, I’m getting this error in zwavejs-ui:
Driver: Failed to open the serial port: Error: No such file or directory, cannot open /dev/ttyUSB0 (ZW0100)
Does this mean my drivers are working properly? Or are others seeing similar behavior?
I’m running zwave js ui 8.25 in a docker container. Home assistant is also running in a docker container and using 2023.9.2
Same issue i have updated to 7.2 *.ko files and updated the script but i’m getting No such file or directory: ‘/dev/ttyUSB0’
why oh why did i update my dsm
I got mine working with 7.2. First I used the raw files as suggested here: Warning.. Synology 7.2 USB support broken- Hold off on upgrading - #15 by stagovic
Then I redid everything using the guide here: Warning.. Synology 7.2 USB support broken- Hold off on upgrading - #16 by modderhut
Here’s my docker commandline just in case that’s helpful:
sudo docker run --name "zwavejs-ui_zwave700" --restart always -d -p 8092:8091 -p 3001:3000 --device=/dev/zwave700:/dev/zwave700 -v /volume1/docker/zwavejs700/store:/usr/src/app/store zwavejs/zwave-js-ui:latest
The device “zwave700” is a udev link to ttyUSB0.
Thanks. Spent a few hours on this. I have not had luck yet. I may ditch ZigBee and just move to wifi as I have fp2s now
Can confirm i got my SONOFF Zigbee 3.0 Dongle working again after simply-hearted 
upgrading to DSM 7.2.1-69057
working for me was this guide:
DSM 7 USB Support from Eddie dSuZa // Video Tutorial
1 Like
I followed the same guide (video tutorial) but it doesn’t work for my Synology 720+.
Of course I realized the given link are for DSM 7.0 files, so I found this other link which should contain DSM 7.2 files for my (geminilake infrastructure) 720+.
//github.com/robertklep/dsm7-usb-serial-drivers/tree/main/modules/geminilake/dsm-7.2
Then I run the commands I found on the video (of course I changed with the uplinked DMS 7.2 files)
sudo su
modprobe usbserial
modprobe ftdi_sio
modprobe cdc-acm
cd /lib/modules/
sudo wget https://github.com/robertklep/dsm7-usb-serial-drivers/raw/main/modules/apollolake/dsm-7.2/ch341.ko
sudo insmod /lib/modules/ch341.ko
sudo wget https://github.com/robertklep/dsm7-usb-serial-drivers/raw/main/modules/apollolake/dsm-7.2/cp210x.ko
sudo insmod /lib/modules/cp210x.ko
sudo wget https://github.com/robertklep/dsm7-usb-serial-drivers/raw/main/modules/apollolake/dsm-7.2/pl2303.ko*
sudo insmod /lib/modules/pl2303.ko
sudo wget https://github.com/robertklep/dsm7-usb-serial-drivers/raw/main/modules/apollolake/dsm-7.2/ti_usb_3410_5052.ko
sudo insmod /lib/modules/ti_usb_3410_5052.ko
The installation of ch341.ko went fine, but when I try to launch sudo insmod /lib/modules/ch341.ko i got this error:
insmod: ERROR: could not insert module /lib/modules/ch341.ko.3: Invalid module format
The same happens with other files (cp.210x.to, etc…)
What can I do?
1 Like