USB serial drivers and sonoff zigbee dongle

Hello everyone,
I’m experiencing a problem with the Sonoff Zigbee USB Dongle and the USB serial drivers, if I have the stick connected the NAS cannot shutdown or reboot (it hangs stopping the apps forever) and I have to hard power off, when rebooted all the usb are unavailable (I have to unplug the power cord, wait a while and then plug it again and power on).

I found in the old forum that other people had the same problem months ago, maybe someone has found a workaround?

My NAS is a TS-464
FW: QTS 5.2.5.3145
USB serial drivers v. 5.0.1

We’ll be testing the Sonoff Zigbee USB Dongle internally, and we’ll update you with any new findings.

From my personal experience, even if a device isn’t fully compatible, it usually doesn’t cause a shutdown issue. Have you tried using the dongle on any other devices?

Dear @claudio.ridolfi
Could you kindly share the exact details of the Sonoff Zigbee dongle you are using? If possible any link with detailed model number and specs, we would like to buy the one to evaluate the issue you have raised.

Thank you.

Hello, thanks for the replies.

I tried the same stick with my PC (OS Windows 11) and doesn’t seem to give problems.

The dongle is a Sonoff Zigbee 3.0 USB Dongle Plus (Model ZBDongle-E v2) bought from amazon (here), with the NPC firmware (see here)

For reference, here the old forum thread where other pointed out the same problem, also I found it happend to some people even in older realeases (i.e. here)

Thank you for sharing these details, we shall try to procure the same dongle and update you here.

1 Like

I can confirm this problem. Yesterday I received exactly this USB dongle Sonoff Zigbee 3.0 USB Dongle Plus (Model ZBDongle-E v2) and tested it on my QNAP TS-464. The dongle usually has the effect that the system can no longer shut down as described by other users and can only be switched off with the button. In addition, USB seems to be completely faulty in this state.

This also affects the connected UPS: This is no longer recognized via USB or if it is recognized, a safe shutdown can no longer be performed in the event of a power failure (as the QNAP hangs).

NAS Model: QNAP TS-464
Firmware: QTS 5.2.5.3145
USB serial drivers v. 5.0.1

Hello,
I have a QNAP TS-262 running QTS with Linux kernel 5.10.60.
I’m connecting a USB-UART adapter based on the CP2102 (Silicon Labs) chip:
Sonoff Zigbee 3.0 USB Dongle Plus – Model “ZBDongle-E”.

The device is not being assigned to /dev/ttyUSB0 even though:

  1. The cp210x kernel module is loaded
  2. lsusb detects the correct VID/PID: idVendor = 10c4 idProduct = ea60
    I tried manually binding it using: sh echo 10c4 ea60 > /sys/bus/usb-serial/drivers/cp210x/new_id But systemd-udevd hangs or kills the handler. Questions: Is CP2102 officially supported in this NAS model? Is there a kernel patch or fix to enable this device? Will support for all CP210x VID/PIDs be added? I need this USB-UART bridge for Zigbee/MQTT integration.

Please see more details from below commands:
uname -a
Linux NAS8769AF 5.10.60-qnap #1 SMP Mon May 26 02:14:19 CST 2025 x86_64 GNU/Linux

lsmod | grep cp210x
cp210x 53248 2 usbserial 40960 29 xsens_mt,wishbone_serial,visor,usb_wwan,upd78f0730,ti_usb_3410_5052,symbolserial,ssu100,safe_serial,oti6858,navman,mos7720,mct_u232,kobil_sct,kl5kusb105,iuu_phoenix,ipaq,io_edgeport,garmin_gps,ftdi_sio,f81232,empeg,digi_acceleport,cypress_m8,cp210x,ch341,ark3116,aircable,pl2303

lsusb
Bus 001 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

dmesg | grep tty
[ 0.076110] Kernel command line: consoleblank=0 console=ttyS0,115200n8 intel_iommu=on,igfx_off i915.enable_hd_vgaarb=1 iommu=pt i915.disable_power_well=0 i915.enable_rc6=0 i915.enable_guc=2 memmap=2M$0x8000000 ramoops.mem_address=0x8000000 ramoops.mem_size=0x200000 ramoops.console_size=0x100000 usbcore.autosuspend=-1 zswap.enabled=1 zswap.compressor=lz4 BOOT_IMAGE=/boot/bzImage root=/dev/ram0 rw
[ 0.196729] printk: console [ttyS0] enabled
[ 5.022440] printk: console [ttyS0] disabled
[ 5.022697] 00:08: ttyS0 at MMIO 0xfe032000 (irq = 20, base_baud = 115200) is a 16550A
[ 9.566850] printk: console [ttyS0] enabled

There is another thread related to this dongle. Please search for that thread as it may have more information for you.

Here you go. I found it:

Moved new posts to existing topic.