I have a Aeotec stick running on an Raspberry Pi 3B acting as a server using the usbip serial drivers. It works fine when everything is just running - never quits or crashes or loses communication. And that lets me run Hass.io in a HyperV VM server with all the nice things that provides.
It is fragile during startups, upgrades, etc. I have put in a lot of steps to auto-restart the other side with changes in one side (thanks to suggestions in various threads here). That helps. It is still not quite there.
The good news is I don’t have to touch the zwave box often; the bad news is hass.io gets upgraded a lot.
Most times I upgrade Hass.io I need to reboot both a few times, or log in and restart services a couple times to get it all going again. It is annoying.
There are three servers listed in the documentation, they all seem to carry a lot of overhead and attempt to sell themselves be hubs. I hope for simple as simple is usually more reliable over time. But maybe – Vera in particular looks fairly simple (in fact it looks like an rPi case).
Are these better solutions? Do they remain stable during reboots, upgrades, etc.?
Anyone using Vera as a pure zwave server? Like it?
Are there any better solutions for getting zwave access that’s not fragile during restarts/transitions?