Why can I not use all three devices? They have different serial numbers. One a is SkyConnect stick, the other is a Z-Wave sticker, and the third one is a BT stick. I need all three of them to connect to my Home Assistant VM.

 

I can't help that they are internally the same device. What is the solution please?

 

Upon updating it says "XML Error:HostDev already exist in the domain configuration".

 

14 minutes ago, thany said:

Why can I not use all three devices? They have different serial numbers. One a is SkyConnect stick, the other is a Z-Wave sticker, and the third one is a BT stick. I need all three of them to connect to my Home Assistant VM.

 

I can't help that they are internally the same device. What is the solution please?

 

Upon updating it says "XML Error:HostDev already exist in the domain configuration".

 

VM template uses vendor product to map devices 10c4:ea60. 

Have a look at my usb manager plugin as supports mapping by bus devids. You remove from VM template if using usb manager

Have a look at my usb manager pl

That does indeed work quite a lot better! Also provides more fine grained control over how exactly a USB device gets connected, and when.

 

Of course, this undermines the fact that this problem should probably still be solved in the core VM manager - two devices with the same manufacturer and product ID should not be considered to be one and the same device, or even two identical devices.

2 hours ago, thany said:

That does indeed work quite a lot better! Also provides more fine grained control over how exactly a USB device gets connected, and when.

 

Of course, this undermines the fact that this problem should probably still be solved in the core VM manager - two devices with the same manufacturer and product ID should not be considered to be one and the same device, or even two identical devices.

VM manager just adds to xml and libvirt does the work. It is possible to use bus and device IDs but they changed all the time. USBM also supports automatic hot plugging and usbip so unlikely to be added to core.

I say it's very likely, but then USBM would be (or should be) added to the core. Why not? In light of making Unraid more user friendly, a more full featured USB config like USBM is needed in the core, as opposed to a couple of checkboxes that are probably a 1-to-1 translation of the QEMU config, but are ultimately just confusing to have as a GUI.

 

Assumptions of course. I just want Unraid to become better.

40 minutes ago, thany said:

Assumptions of course. I just want Unraid to become better.

 

Unraid is testing you.  Unraid just wants you to become better.  

 

😆

Sorry, I don't find it that funny when running into problems that don't exist on any other OS under the sun, server-oriented or otherwise.