#USB dongle not recognised

71 messages · Page 1 of 1 (latest)

turbid surge
#

Hey all, I bought an ADS-B dongle to connect with my Raspberry Pi to be able to upload data to flightradar24. There is a HA add-on, ADS-B Multi-Portal feeder, to send the data to them. The Ads-b dongle is just a usb stick with an antenna attached to it. The problem is that when I plug the stick in my PI4, the HA OS doesn't see that the stick is plugged in. Am I doing something wrong? If other info can be found somewhere, please redirect me to that info :).

oak fossil
#

Sometimes hotplugging USB devices doesn't work well in HAOS.
Have you tried a full reboot (not just a restart of HA)?

turbid surge
#

Nope. I also have a zigbee stick in the PI and I run it from an SSD, also connected by usb.

#

But to be sure, in no ways I should connect the stick via other ways to HA?

#

Restarting it rn 😉

oak fossil
#

In that case it might be the hotplugging issue or the USB ports of the Pi are not providing enough power to use them all.

#

What do you mean in other ways? It doesn't hurt to add a USB device (except it pulls too much power - in that case a powered USB hub would be needed).
It might just not be available and need a reboot.

turbid surge
#

The SSD has its own power supply. I had that problem before.

turbid surge
oak fossil
#

If you are running HAOS directly on a Pi, the add-on should get access to the attached USB stick. It might need to be selected in the add-on's settings.

turbid surge
#

Rebooted HA, but it still doesn't show up in "hardware".

wind otter
#

Rebooted HA
I'm not convinced you actually rebooted the OS.
Try powering the device down completely, then start it up again.

#

Also try running this in the SSH addon and share what it says

apk add usbutils
lsusb -vvt

Another thing you can do is to unplug the USB stick, then run this in the Advanced SSH addon with disabled protection mode

docker run --rm --privileged --pid=host -it alpine nsenter -t 1 -m -u -n -i sh -c "dmesg -Tw"

Then plug it in and see if anything is logged.

turbid surge
wind otter
#

Gotta love pis,

turbid surge
#

It was a sd card from, I think, 10 years old.

turbid surge
wind otter
#

Now unplug the stick and compare what's missing.

turbid surge
#

Perform the command again?

wind otter
#

Yes.

turbid surge
#

Check

#

I cant put in the second row and paste also wont work,

#

When I put in the first row and press enter, it gives another command

wind otter
#

Use a proper SSH client.

turbid surge
#

And CTRL-C and CTRL-V also wont work

wind otter
#

Or use the second way I explained.

turbid surge
wind otter
#

No.

turbid surge
#

Oh...

#

Which is the good one?

wind otter
#

I said client, not addon. Use putty or just plain ssh in the CLI to connect to the SSH server.

turbid surge
wind otter
#

Install the advanced SSH addon, disable its protection mode and then follow the steps in my link.

#

It's possible it will also show up if you do ha host logs -vf and then plug it in but I can't test this right now.

turbid surge
turbid surge
#

That was the command

wind otter
#

We only care about if it logs something new if you plug in the stick and what that is.

turbid surge
#

I put the stick in the PI and instantly, some extra rules appeared.

#

Succesfully initialized and connected it says

wind otter
#

Based on this information (idvendor, idproduct, 1-1.3) you should be able to find it in hardware now, Now check lsusb -vvt again.

stuck escarpBOT
#

Open your Home Assistant instance and show hardware information

turbid surge
wind otter
#

Can you show me lsusb -vvt again?

#

You can also search for terms like 2383 or 0bda or RTL28 there.

#

Nevermind. I saw it in the old picture in port 3.

turbid surge
turbid surge
wind otter
turbid surge
#

Yes

wind otter
#

Interesting, it shows up twice. I didn't notice at first. I blame my small display.

turbid surge
#

Yeah, 0bda:2838

wind otter
#

I'm not familiar with this type of driver but it's certainly detected.

turbid surge
#

But to be clear, port e is the physical usb port of the Pi?

#

And Port 001 says usb-storage, which is my SSD drive from which it is booted and runs?

wind otter
#

Not sure where e is coming from but these numbers refers to buses/ports on a USB HUB AFAIK.
Kinda like a tree with branches.

turbid surge
#

I have the usb's directly in the pi without a splitter or something like it

#

I only have some extension cables

wind otter
#

So what I can tell you is that the system can see the USB device and it seems it have a driver for it as well.

turbid surge
#

That's great!

#

Maybe not enough power for it to run?

wind otter
#

Possible but I'd imagine it would not show up in lsusb then. What does the addon say?

turbid surge
#

Nothing specific

#

And I can't select the location of the usb in the settings.

wind otter
#

Anything in the addon logs?

turbid surge
#

[fr24feed] 2024-09-27 00:54:57 | [feed][n]ping 67
[fr24feed] 2024-09-27 00:54:58 | [feed][n]syncing stream result: 1
[fr24feed] 2024-09-27 00:54:59 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
[fr24feed] 2024-09-27 00:54:59 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to tcp://127.0.0.1:30005

#

So, there is a connection between the add-pn and flightradr24, but not between the add-on and the usb dongle

wind otter
#

Not sure what's supposed to listen on 30005.

turbid surge
wind otter
#

Unless it says [dump1090] rtlsdr: no supported devices found. It's likely not an issue with the stick communication. I cant help you with the software/addon itself though.