I would like to migrate my current Hass.io setup from a raspberry pi to a virtual machine. My goal is to make a snapshot of my current setup and upload this in a fresh hass.io installation on the virtual machine.
The problem is that I now use the razberry GPIO board for my z-wave controller. On the virtual machine I will have to use a z-wave usb stick as a controller.
Is it possible to let the z-wave setup from my current snapshot to run with a z-wave usb controller? Or do I have te re add all my zwave devices?
Thats a good suggestion. I wonder how to connect it though…It’s a razzbery V1 z-wave board. I’ve contacted razzbery to see if they know if this is possible.
This part tells the functions of the pins on the card:
The Razberry daughter card only uses one 3.3V, one GND and the RX and TX pins of the Raspberry Pi, but for the sake of stability it plugs into 10 GPIO pins and further restricts access to an additional 4 pins, making a total of 14 GPIO pins inaccessible, which can be a bit annoying because access to 10 GPIO pins is lost for apparently no reason
If im correct I can connect the 3.3v, ground, RX and TX pins of the uart ttl to usb converter to pins of the razberry zwave card that use to connect to pins 1, 6, 8 en 10 of the Raspberry Pi?
Am I risking of distroying the razberry zwave card if I hook it up this way and connect it to a USB port?
I finally received my converter and connected it to my proxmox server running hassio in VM. I successfully passed the usb device to the VM and it shows up as /dev/ttyUSB0 under the hardware tab in Hassio.
I installed the hassio add-on for the openzwave control panel and I can connect to the zwave controller by entering /dev/ttyUSB0 as a path. All my zwave devices show up in the list. So the converter seems to work!
So far so good.
I then changed the zwave usb path in the configuration file to /dev/ttyUSB0 and rebooted.
But the zwave controller does not shows up in the wave menu of hassio?
/dev/ttyAMA0 is the old path of the zwave card when it was connected to the gpio’s of the pi. Some how this path is storred somewhere, but I don’t know how to change this?
The file should be located at /usr/local/lib/python3.7/site-packages/openzwave/option.py, but how can I acces this?
I found a solution. The old usb path was in the file .storage/core.config_entries. After updating the path in this file the zwave controller and zwave devices showed up.
That’s not really true. My HA is running inside an ESXI VM, and there’s no problem passing the USB z-wave stick to it. I have another VM on the same system that has a USB sound card and a PCI-x graphics card passed to it. All of them are just fine.
It makes the VM very difficult to move to other hardware, but that’s not the only reason to use a VM.
I just gave a general answer for those who don’t know exactly what they are doing. In other forums I see people spend days in vain with such experiments. Of course there are exceptions. @d3rax later said he wants to use Proxmox where it works too.
In my case I see more reasons to use a dedicated device for HA instead of mixing it with the rest of the IT infrastructure.
How did you do that?
I’m trying to see some USB device (as a /dev/ttyUSB0) under hass.io ‘Hardware’ button.
But I do not know how to set-up ‘proxmox’ (or ‘hass.io’?)…
I hope you may have worked it out by now, but in ProxMox you use the hardware options and add the USB to the VM, then you can see all your USB’s.
I, however, have a completely different issue where I can see my USB devices, such as the zwave.me and Conbee II, but none of my devices will connect correctly, even with correctly restored backups.
That is a little outside the scope of this thread though, so I will keep looking on that one.
