Yeah, I think tonight I may move the zwave stick back to the server and see if it behaves. Its nice that its working on my Pi and I know that the zwave stuff doesn’t need to be returned but all my automations for the sensor dont work because they are on the wrong instance, connecting the two is a bit of a pain.
Im pretty sure Im on 6.5, it installed nicely on the dell. This is the first issue I have run into related to that server.
I’ve noticed on some occasion that ESXi will drop the USB passthru for no reason intermittently or just stop communication with the device all together.
I’m not sure that a zwave stick would be considered an ideal candidate for ESXi passthrough. You might want to try dedicating CPU / RAM to the HA VM?? Maybe Since business devices aren’t restricted as much for RF shielding, you might want to try a USB extension to get it away from the box???
I have just started up my HA VM and will do some looking.
@silvrr I thought I would check back. I did move my install from the Pi to a dedicated Debian VM. I did a straight install with no Python virtual_env. I have ESXi 6.5 running on an Intel Skull Candy NUC. There are 6 to 10 VMs on this NUC with nothing significantly active besides a MythTV recorder. I don’t know how this compares with your VM load. My install seems to be working well for now. I will update this if I experience any issues.
Posting just incase anyone is having issues in the future with this. @firstof9 posted a fix that has provided zwave stability in my virtual instance.