Restoring Z-Wave and Zigbee networks after Synology VMM upgrade/USB loss

Installation
1

I am trying to get my Z-Wave and Zigbee connections back after a Synology upgrade. I'm running HA on a VMM and have had my networks up and running with a CP210x dongle for the last 5-6 years. I posted over here about getting my USB re-established in Synology, and I think I've made some progress as I'm now seeing /dev/ttyUSB0 and /dev/ttyUSB1.

The problem I'm having now is getting my add-ins to recognize the stick. For one (and, I'm not sure this is something I can fix), I have no /dev/serial/ folder, so no persistent mapping to the stick.

Here are my ZWave JS UI logs on startup... just constant attempts to connect to the stick:

  ______  __          __                      _  _____     _    _ _____ 
 |___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
    / /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |  
   / /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |  
  / /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_ 
 /_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
2026-06-27 05:56:40.958 WARN STORE: scenes.json not found
2026-06-27 05:56:40.963 WARN STORE: configurationTemplates.json not found
2026-06-27 05:56:40.983 INFO APP: Listening on port 44920 protocol HTTP
2026-06-27 05:56:40.992 INFO ZNIFFERMANAGER: Zniffer is DISABLED
2026-06-27 05:56:40.995 INFO MQTT: MQTT is disabled
2026-06-27 05:56:40.997 WARN BACKUP: Store backup is disabled
2026-06-27 05:56:40.998 WARN BACKUP: Nvm backup is disabled
[05:56:41] INFO: Starting NGinx...
2026-06-27 05:56:41.018 INFO Z-WAVE: Connecting to /dev/ttyUSB0
2026-06-27 05:56:50.229 INFO Z-WAVE: Controller status: Driver: Failed to open the serial port: Error: No such file or directory, cannot open /dev/ttyUSB0 (ZW0100)
2026-06-27 05:56:50.230 INFO Z-WAVE: Restarting client in 1 seconds, retry 1
2026-06-27 05:56:51.232 INFO Z-WAVE: Client closed
2026-06-27 05:56:51.236 INFO Z-WAVE: Connecting to /dev/ttyUSB0
2026-06-27 05:57:00.265 INFO Z-WAVE: Restarting client in 2 seconds, retry 2
2026-06-27 05:57:02.269 INFO Z-WAVE: Client closed
2026-06-27 05:57:02.275 INFO Z-WAVE: Connecting to /dev/ttyUSB0
2026-06-27 05:57:11.333 INFO Z-WAVE: Restarting client in 4 seconds, retry 3
2026-06-27 05:57:11.413 INFO APP: ::ffff:127.0.0.1 GET /health/zwave 301 162 - 14.937 ms
2026-06-27 05:57:15.338 INFO Z-WAVE: Client closed
2026-06-27 05:57:15.342 INFO Z-WAVE: Connecting to /dev/ttyUSB0
2026-06-27 05:57:24.381 INFO Z-WAVE: Restarting client in 8 seconds, retry 4
2026-06-27 05:57:32.384 INFO Z-WAVE: Client closed
2026-06-27 05:57:32.388 INFO Z-WAVE: Connecting to /dev/ttyUSB0
2026-06-27 05:57:41.415 INFO Z-WAVE: Restarting client in 15 seconds, retry 5
2026-06-27 05:57:41.534 INFO APP: ::ffff:127.0.0.1 GET /health/zwave 301 162 - 6.845 ms

Under System-->Hardware, I don't have my tty/USB* devices shown:

image
image1047×363 8.23 KB

I don't know where to go from here. While I have both Zigbee and Z-Wave running, my Z-Wave devices are far more critical to get started. Any help would be great.

2

I seem to remember something about Synology disabling the USB drivers or something like that in an update, is that perhaps what you are facing? Not too sure about the details, maybe Google has something on the topic.

3

You're right--but I think I've gotten past that using instructions from Marius and some other resources. I did it once after upgrading to DSM 7 some years ago, and now I'm having to do it again after a (probably ill-opted) DSM upgrade to 7.3. I haven't had to do it again until now. This should be evidence that I'm past that point:

image
image1028×158 17.8 KB

4

Where did you do this? In the synology os? Container? Do you see it in the HA container/OS?
Did you pass it through correctly?

5

This is SSH into the Synology. Here's the VMM config in Synology:

image
image530×411 12.1 KB

This is how I've had it configured for many years. I've done a VMM restart to make sure it takes (and doesn't lose the config). The hardware screen in HA doesn't show ttyUSB0 or ttyUSB1.

6

Remove and readd?

7

I'm pleased to be able to say... NO! I found the problem:

image
image690×502 17.6 KB

This was it. After shutting down the VM, setting this to USB 2.0, then restarting... everything came back. I could be imagining things, but I think I recall doing this last time. Maybe I should write this down. Or, bookmark this post.

Thanks for your input, though.