I would like to start using Z-Wave devices with Openhab.
I had purchased a USB Dongle to use but my host system, Synology, no long supports USB.
Has anyone had luck with a USB Hub outside the Host that connects to Openhab?
This is working for me with DSM7 & OH4.3.
I don’t know if this is applicable to your situation, but I use usbipd, set up in this video.
tl;dr I had been using OH on a 32-bit Rpi3 to capture some remote ZW nodes in a separate network (connected to my main OH (in docker) via remote OH binding). With OH5 needing 64-bit, the 1GB rpi3 is too small. Last week I followed the video on a fresh Raspi Lite 64-bit OS to install usbip on both the Rpi3 and the main OH device. The remote ZW stick shows up on the main OH just like it did on the Rpi3 (dev/ttyACM0) or /dev/serial/by-id/usb-0658_0200-if00. There is a different ZW stick (800 chip) on the main device using ZWave-js, but there doesn’t seem to be any conflicts. I looked into usbipd because it was the default with windows to connect with WSL where I run OH in docker for testing.
Edit: you could also just run a separate OH instance on your outside host (if it is big enough) and use the OH remote binding like I did before.
What works very well for me is running openHAB on a VM using Virtual Machine Manager. DSM passes the USB devices through that can be “attached” to the (QEMU) VM. I use a minimal Debian Bookworm on top of which I install openHABian. This has the advantage that you can “unplug” the Z-Wave dongle and "attach is to Windows VM for example to run Z-Wave PC Controller to update OTA firmware or remove dead nodes without having to physically touch anything.
Above you can see my attached DSMR, RFXCom, Bluetooth and Z-Wave dongles.
Additionally you have all advantages of taking snapshots prior to updates or changes and you can backup the entire VM to deploy it on another device. I have allocated 2 CPU’s and 4GB of which half is used on my RS1221+ with 32GB and CPU usage is below 3%.
For others info I did get this working using the following Synology posts…
Interestingly cdc-acm.ko does not seem to be required.
In addition allowing the Docker Container “Run with High Privilege”. If this is a concern for you you can use the command line device flag to do this.
You must setup a script to do this at DSM startup as these don’t persist over reboots.