I am running exactly this setup successfully for over a year.
My RasPi is sitting in the middle of the house with a Razberry-Me-GPIO-Module and even a zigbee-dongle connected to USB.
On my Windows Hyper-V-Server I have a debian VM running OH 2.5.
The RPI uses ser2net for the razberry-dongle with the following /etc/ser2net.conf
“zigwave.space.flo” is the hostname of my RPi.
The Z-Wave-Binding uses /dev/ttyUSB0 for the Z-Wave-dongle and everything works as expected.
I have both, ser2net on the RPi and socat on my debian VM set to autostart on reboot - nevertheless, if socat loses connection to ser2net it wont reconnect automatically . at least I was not able to configure that correctly…
zwave2mqtt is another option. Means the zwave instance can run on somethign with the physical zwave controller, and mqtt is used for all your openhab items. Probably very manual with mqttv2 binding as I doubt there is discoverability from 2wave2mqtt
Not an answer directly to what you’re asking, but might be relevant. I’m running OH on Windows Server 2016 in a Hyper-V environment and have had no issues with a Silex SX-3000GB USB network device server. They’re going for under $20 on eBay (US) now and just worked for me (in Windows at least). No issues auto-reconnecting on startup/plugging back in or anything like that.
Edit: Maybe not useful at all if you’re using the RPi-integrated z-wave rather than a USB stick
Well It seems to me that I got some testing to do.
I got some connection between my OH and Pi with ser2net & socat but it jumps up & down like an bungy jumper. At least I got this far.
Hmm another OH to handle z-wave as a slave OH sounds interesting. Will look in to that aswell. Is there autodetection?
I know there is the Z-way binding and it’s also an alternative .
Is there any prefered solution regarding to reliability, speed and ease of handling?
I personally am VERY happy with the Z-Wave binding and the support from the developer here. He is very capable and the community maintained device database works quite well, much better than the openzwave (non-OH) system I tried earlier.
In fact, Chris, the developer’s assistance was instrumental in me coming to OH as a user.
On the “slave” instance you will get autodetection of the Zwave devices per usual from the Zwave binding. You will need to create Items and add them to one or two Groups (see the Event Bus link above). The Rules will publish all updates and all commands to the Items that are members of the two respective Groups to a well known topic structure.
On the “master” instance you need to create a Trigger Channel on the MQTT Broker Thing with a wild card subscription to the root of that well known topic structure and create Items of the same type and same name as those that are on the “slave”. The Rules on the “master” will figure out what Item the message is from and update or command the local Item of the same name as necessary.
I’ve seen lots of reports that the Z-Way binding is kind of slow and not super reliable. But that was a long time ago. Maybe it has improved since then.
Yeah the Z-way to it self had some issue in the past and I know the first version of the Z-way binding had some issue but what I know sens the rework it works fine. Latency I dont know… Still if the Z-way it self stops nothing else will work.
I will go deeper into OH to OH and read more. Sound to me like something I really want to try out. Thanks.