I can only offer some generic advice, but have you looked in Supervisor > System > Host System > dot menu > Hardware (as per the docs) to see which device paths are available?
I don’t have HA blue myself but I have been reading that the back plate of the blue is to thick. The conbee seems to physically not connecting removing the backplate solves the problem.
Does using a USB extension cable resolve this problem?… It looks like it would.
(should it be the case that the enclosure preventing the Conbee II from fully plugging in as described above by @proton999 )
Since anyway, as you may already be a familiar: the Conbee II’s manufacturer recommends using a usb 2.0 extension cable so strongly that The support request template specifically asks if the customer is using one
Thank you @carver and @proton999 for your tips and @robertklep for taking the time to comment. Took myself to the local store and bought an extension cord. The ConBee II was directly recognized Problem solved.
The USB stick was recognized automatically on my Raspberry Pi3B+ but not on the HA Blue.
Had to order an USB extension cable too to get it working. Crazy technology.
Yapp. That was the problem. Used 3 hours before I found this post. Taking the back plate off the Blue recognized the ConBeeII. Now, have to find a grinder to shave some mm of the back plate. Sig…
UPDATE:
For the power cord drilled out the opening to 10 mm diameter so the power plug goes all the way in.
Filed down the section for the USBs so the ConBeeII was able to connect.
I think an extension cable is preferable although not as neat. All USB3 ports generate interference that impacts plug in RF devices. Moving them a little distance away helps considerably.