I am trying to write an integration but am encountering an issue with integrating a USB device into my Home Assistant setup running on HAOS. While the device is correctly recognized by the system (as confirmed by dmesg logs showing successful identification and driver loading for the USB2CAN device), HAOS does not automatically create a CAN network interface (e.g., can0 ). This contrasts with my experience on a separate system running Debian, where the device works as expected and the CAN interface is readily available and configurable.
This is probably because of a HAOS restriction but I am hoping there is a work around.
[86253.408695] usb 1-1.1: new full-speed USB device number 3 using xhci_hcd
[86253.515914] usb 1-1.1: New USB device found, idVendor=1d50, idProduct=606f, bcdDevice= 0.00
[86253.515947] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[86253.515960] usb 1-1.1: Product: USB2CAN V3.3
[86253.515971] usb 1-1.1: Manufacturer: InnoMaker
[86253.515980] usb 1-1.1: SerialNumber: 0019003B4E46570420333538
[86253.543273] CAN device driver interface
[86253.547651] gs_usb 1-1.1:1.0: Configuring for 1 interfaces
[86253.549319] usbcore: registered new interface driver gs_usb
…
but
[core-ssh ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
20: eth0@if21: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
link/ether 02:42:ac:1e:21:01 brd ff:ff:ff:ff:ff:ff
and
[core-ssh ~]$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 02:42:AC:1E:21:01
inet addr:172.30.33.1 Bcast:172.30.33.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11747 errors:0 dropped:0 overruns:0 frame:0
TX packets:6955 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4078231 (3.8 MiB) TX bytes:1133519 (1.0 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
…