With my new flight feeder (blue) is getting stuck when I am connecting over Wi-Fi. And finally disconnected. But with Ethernet connection it’s working properly without any issue. Anyone experienced the same situation?
Any solution for this? Thank you in advance.
Contact the supportteam at adsbsupport@flightaware.com
They can investigate what is happening with your flightfeeder.
3 Likes
Thanks Tom. I have informed them also. Just wanted to know whether is anyone had this issue.
Meantime I have tested with different WIFI connections and external WIFI adaptor also. Still no luck.
Lets see.
Does it freeze/lock up on the wifi menu or it just attempts to connect to wifi but never succeeds?
Mine locks up when attempting to do anything with wifi but since I planned on using ethernet it doesn’t bother me much. Also a new FlightFeeder Blue.
1 Like
It’s getting stuck when device booted up and after few minutes. If I try to navigate to network menu, then it will stuck before then that. To recovery that I have to manually turn off my router and then I can peacefully switch back to wired connection. And what I am doing is disabling the Wi-Fi connection on the device. After that device is working fine… only the issue in Wi-Fi.
I disable wifi and Bluetooth on all of my RPi’s.
Here are some commands to handle it.
Turn Off/On WiFi or Bluetooth
Turn off sudo rfkill block wifi
Turn on sudo rfkill unblock wifi
Status sudo rfkill
sudo ifconfig wlan0 down
sudo ifconfig wlan0 up
Turn Off WiFi or Bluetooth hardware until config.txt is edited.
Edit /boot/firmware/config.txt file.
Add under [All]
dtoverlay=disable-wifi
dtoverlay=disable-bt
Reboot
1 Like
It’s not a Raspberry Pi device 
, he has a blue flightfeeder.
As far as I’m aware that’s slightly different hardware.
2 Likes
…and user doesnt have admin access
2 Likes
Yes, I don’t have admin access to module.
The case is at this time it is possible to provide ethernet connection to device what FlightAware recommended. But I have a plan to move the device to an upper location later and it’s easy to connect via WIFI than extends a Ethernet cable to that place.
With my understanding, there seems to be an issue in the device.
Depending on your environment (interference from neighbours wifi, channel congestion) running pi / flightfeeder on wifi can be “challenging”.
I did some testing early on in this hobby and quickly determind that “wired” was going to be significantly more dependable, and haven’t looked back.
Put in dedicated network drops for my flightfeeder and piaware stations, assigned static IP addresses, and zero issues.
(Clean power for feeders & network equipment is also important to consider and often overlooked)
I run a small UPS for ads-b equipment to protect pi/flightfeeder equipment (& the microSD cards from voltage spikes and sags) and a larger UPS covers modem/router/switch infrastructure)
My Site 1526 streak has surpassed 3,600 days, so i must be doing “ok” as far as demonstrating what seems to work dependably.
2 Likes