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 :).
#USB dongle not recognised
71 messages · Page 1 of 1 (latest)
Sometimes hotplugging USB devices doesn't work well in HAOS.
Have you tried a full reboot (not just a restart of HA)?
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 😉
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.
The SSD has its own power supply. I had that problem before.
The add-on has a tutorial in which the guy from the movie runs HA from a synology drive. In the movie he had to assign the USB port to HA or something like that.
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.
Rebooted HA, but it still doesn't show up in "hardware".
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.
I rebooted the PI, but I got the "Unable to read partition as FAT" warning, so I think my SD-card died
Gotta love pis,
It was a sd card from, I think, 10 years old.
I don't know how to share the code
Now unplug the stick and compare what's missing.
Perform the command again?
Yes.
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
Use a proper SSH client.
And CTRL-C and CTRL-V also wont work
Or use the second way I explained.
Isn't the terminal the good one?
No.
I said client, not addon. Use putty or just plain ssh in the CLI to connect to the SSH server.
The good one is the advanced one. You need it for dmesg: #1288930743262773308 message
I'm sorry. Im just not a bit new with this. I don't have a background in IT, so if you say "Put your mouse in the upper right corner" I will put my physical mouse on the screen.
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.
It spits out an enourmous amont of info
docker run --rm --privileged --pid=host -it alpine nsenter -t 1 -m -u -n -i sh -c "dmesg -Tw"
That was the command
We only care about if it logs something new if you plug in the stick and what that is.
I put the stick in the PI and instantly, some extra rules appeared.
Succesfully initialized and connected it says
Based on this information (idvendor, idproduct, 1-1.3) you should be able to find it in hardware now, Now check lsusb -vvt again.
My ssd drive and zigbee dongle are clearly indicated, but the new stick isn't
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.
I don't have putty or something like that
The usb stick you mean?
See the port 003 with 0bda here? #1288930743262773308 message
Yes
Interesting, it shows up twice. I didn't notice at first. I blame my small display.
Yeah, 0bda:2838
I'm not familiar with this type of driver but it's certainly detected.
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?
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.
I have the usb's directly in the pi without a splitter or something like it
I only have some extension cables
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.
Possible but I'd imagine it would not show up in lsusb then. What does the addon say?
Anything in the addon logs?
[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
Not sure what's supposed to listen on 30005.
I also don't know what that means
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.