Upgrade from 6.9.2 -> 6.10.RC4 USB in VM problem

[Magic815]

15 minutes ago, stefan.tomko said:

Same happened to me when I was once playing with VM and adapters. But it happened for devices that I passed normally and as serial. At some point, I had 3 "virsh error" messages for 3 adapters. That was already on 6.11.0. Rebooted Unraid, rebooted VM... no luck. After few moments, I did detach and attach devices again, and virsh error was gone.

Hmm, so I tried a couple detach/attach, and it didn't seem to help.

 

However, I toggled off 'Connect as Serial Only' for both USBs - to put them back into device mode - and it seems to be working ok now? unRAID shows "Connected(Device)" again for both USBs - see below. And as far as I can tell, Z-Wave JS and Zigbee2MQTT inside HA don't show any errors - and my Z-Wave and Zigbee devices seem to be all in working order and connected. What behavior/error should I be on the lookout for to determine if switching to 'Serial Only' is even required for me? Was that only needed for Conbee II, and doesn't apply to the types of USB devices I have?

 

In case it matters: In my specific case, my two USBs have the exact same controller/ID: "Silicon Labs CP210x UART Bridge". Does that preclude me from being able to run both as serial or something? Or does it mean I don't even need to bother with serial-only in the first place?

 

Edited October 1, 2022 by Magic815

[SimonF]

7 minutes ago, Magic815 said:

Hmm, so I tried a couple detach/attach, and it didn't seem to help.

 

However, I toggled off 'Connect as Serial Only' for both USBs - to put them back into device mode - and it seems to be working ok now? unRAID shows "Connected(Device)" again for both USBs - see below. And as far as I can tell, Z-Wave JS and Zigbee2MQTT inside HA don't show any errors - and my Z-Wave and Zigbee devices seem to be all in working order and connected. What behavior/error should I be on the lookout for to determine if switching to 'Serial Only' is even required for me? Was that only needed for Conbee II, and doesn't apply to the types of USB devices I have?

 

In case it matters: In my specific case, my two USBs have the exact same controller/ID: "Silicon Labs CP210x UART Bridge". Does that preclude me from being able to run both as serial or something? Or does it mean I don't even need to bother with serial-only in the first place?

 

If you get a Virsh error if you hover over it will give more details.

 

Did you set each serial mapping to a unique device ID, defaults to 04 but they need to be different and also those need to be available on the guest.

 

Only device I know that needs to be serial is Conbee II

[Magic815]

59 minutes ago, SimonF said:

If you get a Virsh error if you hover over it will give more details.

 

Did you set each serial mapping to a unique device ID, defaults to 04 but they need to be different and also those need to be available on the guest.

 

Only device I know that needs to be serial is Conbee II

Can you expand on "needs to be available on the guest"? On one of my attempts, I thought I tried changing the 04 to 05 on one of the USBs, but it still didn't seem to work. Maybe there was an additional step I needed to take for the guest availability aspect?

 

Knowing that I'm not using Conbee II, are there other benefits of switching to serial-only? I'm starting to wonder if device-mode seems to work with my USBs in unRAID 6.10.3, should I just let it lie as-is?

Edited October 1, 2022 by Magic815

[SimonF]

6 minutes ago, Magic815 said:

Knowing that I'm not using Conbee II, are there other benefits of switching to serial-only? I'm starting to wonder if device-mode seems to work with my USBs in unRAID 6.10.3, should I just let it lie as-is?

The only benefit of serial and the reason I added it to the plugin is Conbee II doesnt seem to work correctly on later kernels if passed through as a device. My ZWAVE Stick is mapped as a device and works fine.

 

 

the following command will show the guest ports, replace Linux4 with your VM name.

 

root@computenode:/mnt/user/appdata# virsh qemu-monitor-command Linux4 --hmp info usb
  Device 0.2, Port 1, Speed 480 Mb/s, Product QEMU USB Tablet, ID: input0
  Device 0.0, Port 2, Speed 1.5 Mb/s, Product USB Host Device, ID: hostdev0
  Device 0.0, Port 3, Speed 1.5 Mb/s, Product USB Host Device, ID: hostdev1


root@computenode:/mnt/user/appdata# virsh qemu-monitor-command HA  --hmp info usb
  Device 0.2, Port 1, Speed 480 Mb/s, Product QEMU USB Tablet, ID: input0
  Device 0.2, Port 4, Speed 12 Mb/s, Product QEMU USB Serial, ID: ua-serial001011
  Device 0.2, Port 2, Speed 12 Mb/s, Product host:1.4, ID: hostdev0

 

If you have the USB option in the VM defined as

 

 

There are only 4 ports as I have on my HA vm. So Dev ID 5 will fail.

 

Hope that helps.

[Magic815]

Ah, I see. This is the result I get:

 

I do indeed have USB Controller set to 2.0 (EHCI).

 

I think for now I'll keep the two USBs linked as devices. However, if I run into issues in the future (like those with Conbee II are), and want to switch to serial-only for both USBs - what port numbers do you recommend I assign to each of those USBs (based on my above screenshot)?

 

As an aside (and a dumb question): I am expecting to finally get a Coral TPU next week to use with Frigate in my Home Assistant VM. It will be USB connected, and I was planning to run it in 'device' mode via USB manager. Am I "out of" USB ports that I can pass through to my HA VM? Is that an issue whether I run it via device mode or serial-only?

Edited October 1, 2022 by Magic815

[SimonF]

5 minutes ago, Magic815 said:

Ah, I see. This is the result I get:

 

I do indeed have USB Controller set to 2.0 (EHCI).

 

I think for now I'll keep the two USBs linked as devices. However, if I run into issues in the future (like those with Conbee II are), and want to switch to serial-only for both USBs - what port numbers do you recommend I assign to each of those USBs (based on my above screenshot)?

 

As an aside (and a dumb question): I am expecting to finally get a Coral TPU next week to use with Frigate in my Home Assistant VM. It will be USB connected, and I was planning to run it in 'device' mode via USB manager. Am I "out of" USB ports that I can pass through to my HA VM? Is that an issue whether I run it via device mode or serial-only?

I would say yes. You have an option to change to 3.0 which will give 14 ports but not sure if will create an issue with the existing ones.

 

If you have a spare USB flash device try and connect to the VM I suspect you will get a error of no available ports.

 

You can use hotplug part of my plugin to do that on VM tab without defining a map, you may have to enable hotplug in config for it to show.

Edited October 1, 2022 by SimonF

[Magic815]

So I changed it to "3.0 (qemu XCHI)" - hopefully that is the recommended one out of the two 3.0 options that were listed?

 

After changing, I restarted the VM, and it seems like Z-Wave JS and Zigbee2MQTT connections are holding strong in Home Assistant, and I can still see all the end devices. Hopefully that means the switch didn't cause any issues with the existing ports? One interesting thing is my list only shows 3 line items now when I ran the command you gave me again:

 

Is there any command I can run to verify I have 11 open USB ports now? Or I guess just something I'll find out for sure on when I plug in the Coral TPU via USB next week?

Edited October 1, 2022 by Magic815

[SimonF]

1 hour ago, Magic815 said:

So I changed it to "3.0 (qemu XCHI)" - hopefully that is the recommended one out of the two 3.0 options that were listed?

 

After changing, I restarted the VM, and it seems like Z-Wave JS and Zigbee2MQTT connections are holding strong in Home Assistant, and I can still see all the end devices. Hopefully that means the switch didn't cause any issues with the existing ports? One interesting thing is my list only shows 3 line items now when I ran the command you gave me again:

 

Is there any command I can run to verify I have 11 open USB ports now? Or I guess just something I'll find out for sure on when I plug in the Coral TPU via USB next week?

Yes that is the correct one. I dont know if they is a way to check free ports will have a look. You may have been ok on 2.0 as ome of the devices was a serial map and if you change back without disconnectimg first it womt be removed but is now as you restarted vm

[Keith Morden]

Does the Conbee II Stick work with version 6.11 and HASS? I'm still running 6.9.2 because the workarounds don't work.

[jeroen123456]

Nope. I couldn't get it to work, just downgraded again to 6.9.2, very unfortunate. 

[SimonF]

8 hours ago, Björn Schwarz said:

Does the Conbee II Stick work with version 6.11 and HASS? I'm still running 6.9.2 because the workarounds don't work.

Yes it works for me on 6.11.1 using serial attach.

[jejsun]

57 minutes ago, SimonF said:

Yes it works for me on 6.11.1 using serial attach.

I'm also using Conbee II and 6.11.1, follow the guide linked, worked for me. 

 https://community.home-assistant.io/t/solved-conbee-2-fails-to-connect-to-zha-ha-in-unraid-vm/431276

[Pixelpaule]

Hey, might it be better and more stable to switch to a Sonoff ZB dongle-E?

[canedje]

I try to use this method for using the ConbeeII to ZHA in HA in a VM.
I can install ZHA but is giving:

 

The device is disabled and so not usable

[NiapApa]

Hey!

Got the same problem when upgrading above 6.9.2.
Any news around this topic? Will this be "patched/resolved" in future updates?
 

🙃

[Grsh]

Hey!

I am still on 6.9.2
Upgraded a year ago and could not fix it so downgraded again.

I am trying to figure out if this is still a problem and if there is a good solution if it is?

Thanks!

[Grsh]

To answer ,y own question:

Wasn't "fixed" but it didn;t take me long to actually do it.
Used the USB plugin to connect the Conbe stick to the vm. Took it off in the VM settings before that.

Home assistant couldn't find the old one but I clicked through to mirgrate to a new radio inm ZHA and switch to the "new" connected one.

Please make a Home Assistant backup. First try all zigbee devices had the default name. Started again from a backup and then it worked.

 

Good luck.