Is it possible to get USBIP or socat on HASSOS?

brendan · September 10, 2022, 11:37pm

USBIP is a bit finicky and it is documented to only work on LINUX machines. I have found in VM’s on Synology it can be really hit and miss.

felix63 · September 11, 2022, 9:41am

I’m running zwave2mqtt (and zigbee2mqtt) on a separate machine using docker which is really, really ideal. If I need to upgrade either I just have to manipulate the container and getting it started was just like 123 because once you’ve worked out the correct command to start your docker it is done.

Paxy · September 15, 2022, 11:35am

Got same issue as you.
To solution was to exit docker and execute modprobe vhci-hcd in main shell, than return to docker for usbip attach.

Hitesh_Singh · September 15, 2022, 1:45pm

Hey @Paxy , Could you please explain what do you mean by “main shell” I mean where exactly ?

Paxy · September 15, 2022, 1:58pm

SSH access to HASSOS (ssh to port 2222 terminal). There you modprobe module. Than access to docker homeassistant and do usbip attach.

Hitesh_Singh · September 16, 2022, 2:09pm

Getting no such files or directory error

mobile.andrew.jones · September 16, 2022, 2:13pm

USBIP is built in to OS9:

USB/IP support (on Kernel level).

Hitesh_Singh · September 16, 2022, 2:16pm

Nicheeee, Let me upgrade to OS9 and check

labambadilem · September 17, 2022, 5:53pm

Has anyone figured out how to enable this on HAOS 9?

sithanas · September 30, 2022, 2:14am

Not quite fully baked yet apparently…

github.com/home-assistant/operating-system

USBIP binaries missing from hassio

opened 11:34PM - 08 Sep 22 UTC

irakhlin

os

### Describe the issue you are experiencing The most recent release of home a…ssistant made a few references to using USBIP modules to utilize as an option for remote bluetooth controllers, which I was able to get working in a core install of home assistant. Unfortunately the usbip kernel module and utility is missing from the build. Taking a look I was able to enable it in a few places and build the OS successfully https://github.com/ilya-ws/operating-system/tree/usbip I have also tested and it is verified working for a bluetooth dongle from a remote machine. Testing with 9.0 rc2 I am however unable to find the usbip binaries. ### What operating system image do you use? generic-x86-64 (Generic UEFI capable x86-64 systems) AND odroid-n2 (Hardkernel ODROID-N2/N2+) ### What version of Home Assistant Operating System is installed? 9.0rc2 ### Did you upgrade the Operating System. Fresh install tested on generic-x86-64 ### Steps to reproduce the issue USBIP modules not compiled by the build and is unavailable in the os. ### Anything in the Supervisor logs that might be useful for us? ```txt n/a ``` ### Anything in the Host logs that might be useful for us? ```txt n/a ``` ### System Health information _No response_ ### Additional information _No response_ EDIT: Reopening, tested 9.0rc2 and am unable to find the usbip kernel module / client. On my build of the OS I am able to get usbip working.

github.com/home-assistant/supervisor

Supervisor addon functionality lacks ability to allow usbip bind with home assistant os 9.0rc2

opened 08:34PM - 12 Sep 22 UTC

irakhlin

enhancement

### Describe the issue you are experiencing Supervisor does now allow interacti…ng with usbip /sys device with newest home assistant os (that includes usbip drivers). ### What is the used version of the Supervisor? 2022.09.0 ### What type of installation are you running? Home Assistant OS ### Which operating system are you running on? Home Assistant Operating System ### What is the version of your installed operating system? 9.0rc2 ### What version of Home Assistant Core is installed? 2022.9.1 ### Steps to reproduce the issue I had initially reported this issue to the home assistant OS repo [here](https://github.com/home-assistant/operating-system/issues/2119) but it would seem more fitting here. Home assistant OS 9.0 has added the kernel level usbip drivers to allow addon containers to mount usbip devices, unfortunately as it currently stands the addon config template does not provide enough functionality to fully implement this feature. To test I created a basic addon container that has usbip binaries along with ssh to navigate inside the container, [here](https://github.com/irakhlin/usbip-hassio). After correctly loading the vhci-hcd drivers, inside the container run the following: ``` root@7cbb8c6e-usbipclient:/sys/devices/platform/vhci_hcd.0# usbip list -r 10.0.0.77 Exportable USB devices ====================== - 10.0.0.77 1-1.4: Realtek Semiconductor Corp. : unknown product (0bda:a725) : /sys/devices/platform/soc/20980000.usb/usb1/1-1/1-1.4 : Wireless / Radio Frequency / Bluetooth (e0/01/01) : 0 - Wireless / Radio Frequency / Bluetooth (e0/01/01) : 1 - Wireless / Radio Frequency / Bluetooth (e0/01/01) ``` ``` root@7cbb8c6e-usbipclient:/sys/devices/platform/vhci_hcd.0# usbip --debug attach -r 10.0.0.77 -b 1-1.4 usbip: debug: usbip.c:129:[run_command] running command: `attach' libusbip: debug: vhci_driver.c:269:[usbip_vhci_driver_open] available ports: 16 libusbip: debug: vhci_driver.c:281:[usbip_vhci_driver_open] available controllers: 1 libusbip: debug: vhci_driver.c:128:[refresh_imported_device_list] controller 0 libusbip: debug: vhci_driver.c:67:[parse_status] hub hs port 0 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:67:[parse_status] hub hs port 1 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:67:[parse_status] hub hs port 2 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:67:[parse_status] hub hs port 3 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:67:[parse_status] hub hs port 4 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:67:[parse_status] hub hs port 5 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:67:[parse_status] hub hs port 6 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:67:[parse_status] hub hs port 7 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:67:[parse_status] hub ss port 8 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:67:[parse_status] hub ss port 9 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:67:[parse_status] hub ss port 10 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:67:[parse_status] hub ss port 11 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:67:[parse_status] hub ss port 12 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:67:[parse_status] hub ss port 13 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:67:[parse_status] hub ss port 14 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:67:[parse_status] hub ss port 15 status 4 speed 0 devid 0 libusbip: debug: vhci_driver.c:69:[parse_status] sockfd 0 lbusid 0-0 libusbip: debug: vhci_driver.c:104:[parse_status] exit usbip: debug: usbip_attach.c:100:[import_device] got free port 0 libusbip: debug: vhci_driver.c:367:[usbip_vhci_attach_device2] writing: 0 3 65541 2 libusbip: debug: vhci_driver.c:372:[usbip_vhci_attach_device2] attach attribute path: /sys/devices/platform/vhci_hcd.0/attach usbip: debug: sysfs_utils.c:18:[write_sysfs_attribute] error opening attribute /sys/devices/platform/vhci_hcd.0/attach libusbip: debug: vhci_driver.c:376:[usbip_vhci_attach_device2] write_sysfs_attribute failed usbip: error: import device ``` While I do see /sys/devices/platform/vhci_hcd.0/attach mounted in the container: ``` oot@7cbb8c6e-usbipclient:/sys/devices/platform/vhci_hcd.0# ls -l total 0 --w------- 1 root root 4096 Sep 12 16:00 attach --w------- 1 root root 4096 Sep 12 16:06 detach lrwxrwxrwx 1 root root 0 Sep 12 16:06 driver -> ../../../bus/platform/drivers -rw-r--r-- 1 root root 4096 Sep 12 16:06 driver_override -r--r--r-- 1 root root 4096 Sep 12 16:06 modalias -r--r--r-- 1 root root 4096 Sep 12 16:00 nports drwxr-xr-x 2 root root 0 Sep 12 16:06 power -r--r--r-- 1 root root 4096 Sep 12 16:00 status lrwxrwxrwx 1 root root 0 Sep 12 16:06 subsystem -> ../../../bus/platform -rw-r--r-- 1 root root 4096 Sep 12 16:00 uevent drwxr-xr-x 5 root root 0 Sep 12 16:06 usb3 drwxr-xr-x 5 root root 0 Sep 12 16:06 usb4 -rw-r--r-- 1 root root 4096 Sep 12 16:06 usbip_debug ``` My understanding is that /sys is mounted as read only: ``` root@7cbb8c6e-usbipclient:/sys/devices/platform/vhci_hcd.0# cat attach cat: attach: Permission denied root@7cbb8c6e-usbipclient:/sys/devices/platform/vhci_hcd.0# echo 'test' > attach -bash: attach: Read-only file system ``` I was able to manually modify the addon containers mount points by adding: ``` /sys/devices/platform/vhci_hcd.0:/sys/devices/platform/vhci_hcd.0 rw /sys/bus/platform/drivers/vhci_hcd:/sys/bus/platform/drivers/vhci_hcd rw ``` However I do not see a way to accomplish this via the addon config template. My understanding is that we would want to be able to mount /sys/devices/platform/vhci_hcd.0:/sys/devices/platform/vhci_hcd.[x] as the number would increase with each additional usbip device. ### Anything in the Supervisor logs that might be useful for us? ```txt Nothing of interest ``` ### Additional information _No response_

My read on those two threads is that the kernel module is there but an add-on would have to be constructed to load it and make it usable, and the add-on is actually impossible to make right now based on privilege restrictions on add-ons (looks like that’s going to be fixed).

der-graph · January 29, 2023, 5:06pm

Hey, is there some news with this? Does anybody know if and how it is possible to use usbip with HAOS? Or are there still the technical limitations at the moment?

TiagoTab · February 5, 2023, 3:47pm

For passing usb devices (Bluetooth and zigbee) from windows server hyper-v, usbip whould be the best solution, right?
I’m also having the libusbip errors described on this thread, is there a beta version of HA OS that comes with usbip enabled ?

tomerh2001 · March 16, 2023, 7:43pm

Any progress? I just got my SkyConnect and am running on hyper-v, looking for a way to pass it from my host to my hyper-v…

Brandoskey · March 23, 2023, 9:59pm

Also just got my skyconnect and run haos in a vm on proxmox. I’d like to be able to use it with Thread but having it physically attached to a remote machine ion my basement isn’t ideal. I’m hoping I can run it on the same pi that runs zwavejsui

blaal02 · April 6, 2023, 2:26am

I got it to work on a win 2022 host by passing through a pci expansion card with a couple of USB ports:https://community.home-assistant.io/t/ha-on-hyper-v-with-z-wave-and-zigbee-it-works/552529?u=blaal02

ency · October 16, 2023, 9:33pm

I am using usbip for a while now, see this add on (not perfect, but do the job) - GitHub - AverageJoe89/hassio-usbip-mounter

tjhart85 · December 15, 2023, 3:29am

Well, this might be gamechanging! Thank you very much!

Gerhard56 · February 14, 2024, 5:35pm

Hi,
is there any documentation how to install this addon, which a newbee can also follow?
Thanks a lot.
With best regards
Gerhard

nickrout · February 14, 2024, 6:29pm

Install the repository to the addon store, then add the addon from the addon store.

Gerhard56 · February 23, 2024, 9:41am

Thanks a lot