When I start I get a :
C:\Users\tv\openhab>start.bat
Launching the openHAB runtime…
karaf.bat: Ignoring predefined value for KARAF_HOME
Could not resolve mvn:org.eclipse.platform/org.eclipse.osgi/3.11.3
But even then, after adding these it wouldn’t find my conf files and just gave me an empty system.
Spent a few hours trying to get an upgrade going, and now are going ot revert to a backup, can’t remember if it’s a 2.1 or 2.0 system.
I’m not sure if the experience is better under linux (but I’m constrained at the moment in that my usb stick for zwave must be attaced to the only physical machine I have.
If you are running a full blown Windows PC just to run openHAB, you will reduce your power bill big time with switching to a raspberry pi.
The initial costs are about 60 euro (pi:35; sd card: 10; power: 10; case: 5). If you have a spare usb power device, you can try to reuse.
Back on topic, using some debian based linux the upgrade process is handled by apt, the package manager. A package manager compares to windows update for each component handled by it. Usually you install everything via apt.
It’s not dedicated to openHAB, butnis a machine i already have running in an good position to anchor my zwave network.
I would actually prefer Linux for this, but my linux machines are virtual and can’t access the zwave Ian stick, and I don’t see the point of standing up an rPi just for this.
What hypervisor are you using? I’m pretty sure most type 2s will do USB pass through. I’m pretty sure I’ve seen people successfully running USB pass through for zwave using virtual box.
If you are on Windows 10, it would be interesting to see if you can make it work in Bashb for Windows (or whatever they call it these days).
But one thing I do want to mention is that most of your zwave configuration is stored on the controller itself. It is relatively painless to move the controller from one machine to another or even between home automation programs. If that is your biggest concern you don’t have to worry about that.