Migrated HA to NUC, USB PIM is seen, but not assigned to port

Installation
1

Hello, I did a search for UPB not recognized and nothing was found… scrolled through a lot of threads here and didn’t see any related so I hope I’m not repeating something already here.

I moved my HA over to a NUC from a PI3B… Everything was working great on pi (aside from OTBR skyconnect dongle). Migrated over to NUC (HAOS) and restored the backup. All worked great except for my UPB USB PIM isn’t enumerated. using LSUSB command… I can see it listed (and removed when i remove it)… last it gave me was /dev/bus/usb/001/013, But doesn’t actually appear in the “All Hardware” section I tried using the /dev above but it doesn’t connect to it (didn’t expect it to).
Is there anyway to manually mount it or whatever is required so I can use it?
Both setups used HAOS so I don’t think it’s a driver issue. But that’s only a guess since I really don’t know.
Any help would be greatly appreciated. Thank you!

So far things I’ve tried:
-Many reboots
-different USB ports (all of them)
-Different cables
-Was using a USB over Cat 6 extender… moved to directly connect the PIM
-Deleted all instances of UPB to try to start over… but now stuck since it doesn’t see PIM

2

What driver does it use on rpi?

Is that driver included in the NUC kernel?

3

I honestly do not know. I didn’t install anything except HAOS

4

Also, how are you running HA on your NUC? Any kind of virtualized install will require you to pass the usb to the VM.

5

It’s the generic x86-64 build of HAOS. No pass through needed (as far as I know). The ZBT-1 connected right away

6

If you can get into your NUC/HA console you’ll be at the HA linux root shell, unplug the USB, then plug it back in, then type dmesg and see what it says (at the end of the output) about the USB device.

7

IMG_0325
IMG_03251903×1320 429 KB

The 4 port hub is the usb extender via cat 6 and the PIM is the only device plugged in to hub. Sees it as the manufacturer is simply automated

8

… I was hoping to see a line that says something like:

usbcore: registered new interface driver XXXXX

where XXXX is the name of the driver assigned.
So I’m not sure what (if any) driver is actually getting assigned to it.
If you still have your Pi3B w. HAOS, maybe try it there to see what driver got assigned to it.

9

Was actually going to reply I’ll try just that Not sure when I’ll get to try. But I’ll let you know when I do. Thank you

10

Here is the result :slight_smile: Same HAOS build (13.2)

HAOS
HAOS796×327 11.1 KB

11

biggest difference I see is Pi uses dwc_otg to discover devices and generic 64 build uses xchi_hcd

12

Try again in the NUC and wait a bit.
It might be that the driver store needs to be searched first for the right driver.

13

What driver store do you refer to?

14

The one in the OS.

A driver store is a driver database that links device identification strings with drivers and the files related to these drivers.

15

It was over 24 hrs before I plugged it in. Initially forgot when I first migrated. How long should I wait beyond probably 35ish hours?

16

I meant plug it in and wait a minute or two while watching the logs.

17

usbcore: registered new interface driver cypress_m8

Digging around a little bit, my thinking is that your NUC based HAOS does not have the cypress_m8 kernel driver. I’m running HAOS in a VM on a NUC which is x86 based, and the cypress_m8 driver is not there. However on my Ubuntu Host (hosting the HAOS VM), the driver is there.

If I look at the HAOS build config the driver is not in the build (at least its not there now for kernel version 6.6.y-haos).

Its possible that for the Pi3B, it is uses an older version of the build which contains the cypress_m8 driver. One thing to check is in your Pi3B console/ssh, enter uname -r. If the version is 6.6.y-haos then I don’t have an explanation for why the driver is not there, but if it is older, then that could be the reason. Either way, I would recommend writing up an issue on this at

and see what they say.

18

Wally … thank you for the suggestion. It’s been plugged in now for a little over 31 hrs and still a no go.

19

Thank you. I’ll do as you suggested