flightaware / piaware Goto Github PK

Hey there,
Yesterday, I've completely disabled ipv6 on my raspberry (ipv6.disable=1 parameter in grub, it makes the protocol completely killed.).
This was resulted in the following bug:

*** buffer overflow detected ***: /usr/bin/piaware terminated

Thankfully I've found the simple solution which was to remove any IPv6 related entries from /etc/hosts.

After that, piaware launched.

However, you might want to look into it.

Piaware version: 3.6.3

Linux raspberrypi 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l GNU/ Linux

Could you pull the overrideMac changes (53a2906) from the mutability/piaware branch to the flightaware branch?

Thanks!

-- Ken

Hello!
This guy has images and route information shown directly on his piaware:
https://flight.f4ipo.fr/

How could I do something like that?

Presumably this should be caught before it propagates all the way out and kills the process.

pi@twopi ~/piaware $ sudo piaware -debug
05/27/2015 19:02:39 ****************************************************
05/27/2015 19:02:39 piaware version 1.20 is running, process ID 10541
05/27/2015 19:02:39 your system info is: Linux twopi 3.18.0-trunk-rpi #1 PREEMPT Debian 3.18.5-1~exp1+rpi16 (2015-03-28) armv6l GNU/Linux
05/27/2015 19:02:39 connecting to FlightAware eyes.flightaware.com/1200
05/27/2015 19:02:40 FlightAware server SSL certificate validated
05/27/2015 19:02:40 encrypted session established with FlightAware
05/27/2015 19:02:41 autoUpdate is not configured in /etc/piaware or by piaware-config
05/27/2015 19:02:41 manualUpdate is not configured in /etc/piaware or by piaware-config
05/27/2015 19:02:41 ADS-B data program 'dump1090-mutab' is listening on port 30005, so far so good
05/27/2015 19:02:41 i see nothing serving on port 10001, starting faup1090...
couldn't execute "/usr/bin/faup1090": no such file or directory
    while executing
"exec /usr/bin/faup1090 &"
    (procedure "start_faup1090" line 2)
    invoked from within
"start_faup1090"
    (procedure "connect_fa_style_adsb_port" line 19)
    invoked from within
"connect_fa_style_adsb_port"
    (procedure "setup_fa_style_adsb_client" line 6)
    invoked from within
"setup_fa_style_adsb_client"
    (procedure "main" line 86)
    invoked from within
"main $argv"
    invoked from within
"if {!$tcl_interactive} {
    main $argv
}"
    (file "/usr/lib/piaware/main.tcl" line 127)
    invoked from within
"source /usr/lib/piaware/main.tcl"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 source $path"
    from tcllauncher running "piaware -debug"
pi@twopi ~/piaware $

Please add a config option to override the "localhost" default for gpsd.

I'm getting an intermittent failure on startup of piaware (again using systemd under Arch with Tclsh8.6). My log reads the following repeatedly:

Oct 13 12:03:08 server piaware[210]: 10/13/2014 11:03:08 connecting to FlightAware eyes.flightaware.com/1200
Oct 13 12:03:08 server piaware[210]: 10/13/2014 11:03:08 got 'couldn't open socket: Name or service not known' to adept server at eyes.flightaware.com/1200, will try again soon...

I can't see why it can't resolve the address, given that if I stop and restart the service, the socket connects correctly. It's also pretty awkward to test since it only manifests at boot and not reliably so. Any pointers on what might be going wrong, or how to debug further?

Also possibly relevant is that my network interfaces, one of which is unconnected, seem to switch places in /dev so it might be somehow binding to the unconnected interface.

On the page that shows the table of aircraft with details like altitude, etc Airbus A220 aircraft show up with no value in the "Aircraft Type" column.

Clicking on the flight to go to flightaware.com does show that it is an A220, but it does not show up on the piaware UI

Cosmetic fix only.
Running ps ax displays /usr/bin/python3 /usr/sbin/fa-mlat-client but the client is actually located in /usr/bin

locate fa-mlat-client
/usr/bin/fa-mlat-client

Also, logging displays /usr/sbin for faup1090 and fa-mlat-client.

during dump1090 builds, optimization warnings are thrown. can these be implemented?

dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/dump1090-fa/usr/bin/dump1090-fa debian/dump1090-fa/usr/bin/view1090-fa were not linked against libtinfo.so.5 (they use none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/dump1090-fa/usr/bin/dump1090-fa debian/dump1090-fa/usr/bin/view1090-fa were not linked against ld-linux-armhf.so.3 (they use none of the library's symbols)

couldn't execute "ip": no such file or directory
    while executing
"open $cmd $mode"
    (procedure "open_nolocale" line 5)
    invoked from within
"open_nolocale "|ip address show dev $dev""
    (procedure "get_local_device_ip_address" line 2)
    invoked from within
"get_local_device_ip_address $iface"
    (procedure "get_default_gateway_interface_and_ip" line 14)
    invoked from within
"get_default_gateway_interface_and_ip gateway iface ip"
    (object "::adept" method "::fa_adept::AdeptClient::login" body line 25)
    invoked from within
"login"
    (object "::adept" method "::fa_adept::AdeptClient::connect" body line 63)
    invoked from within
"adept connect"
    (procedure "main" line 82)
    invoked from within

Should catch this one.

I have upgraded my PiAware to 6.0 (new SD card image due to failure on old SD card) the website still shows my station as having PiAware 5.0 vise the PiAware actually stating "welcome to PiAware 6.0!"; but that's another issue.

the real issue I am having is that the MLAT is stating "error" when I have it enabled in the software. is this a known issue or is there something I need to do?

Please change or add support to ss instead of using deprecated tool netstat.

sudo[29679]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
piaware[29674]: failed to run netstat:
piaware[29674]: child process 29679 exited with status 255

I've been running piaware on Arch linux with just a few minor patches. The latest commit 7b484a7 depends on dpkg existing. Arch uses pacman instead and the error from using dpkg is unhandled. Would it be possible to fix this? Or would patches be welcome? (Not that I've ever written Tcl before)

May 1 01:13:20 raspberrypi piaware[1983]: 40 msgs recv’d from pfclient (7 in last 5m); 0 msgs sent to FlightAware”

the count of msgs received goes up, but nothing get sent.

Some other log 👍
Apr 30 21:43:29 raspberrypi piaware[7370]: piaware version 3.5.3 is running, process ID 7370
Apr 30 21:43:29 raspberrypi piaware[7370]: your system info is: Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri
Apr 30 21:43:31 raspberrypi piaware[7370]: Connection with adept server at piaware.flightaware.com/1200 established
Apr 30 21:43:31 raspberrypi piaware[7370]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Apr 30 21:43:31 raspberrypi piaware[7370]: FlightAware server certificate validated
Apr 30 21:43:31 raspberrypi piaware[7370]: encrypted session established with FlightAware

Im having issues installing piaware on a raspberry pi 3 a+

I followed the guide on flight aware and the rpi 3 a+ gets stuck at boot, it only display the rainbow colored screen and nothing happens.
Did the exact same steps using the exact same image on a rpi 3 b+ and worked flawless.

I then tried to install piaware on the a+ using the packages instead. First i installed raspbian and that worked right out of the gate. Installed all the packaged worked aswell but when i try to access the website of the pi, i get "reserverd for lighttpd".

Hi all,

I'd like to add the shape of a military training airspace to the map. It yould be great if there was a direcory or a file where I can enter a polygon made of coordinates as in maps.google.com or GPS.

Example: tempory reserved airspace ed-r 205/305 aka TRA LAUTER in Germany:
((49.9344444,6.60888888888889),
(49.9427778,6.89888888888889),
(49.7108333,8.39416666666667),
(49.6697222,8.44888888888889),
(49.0763889,8.37416666666667),
(49.0044444,8.34833333333333),
(48.9677778,8.29166666666667),
(49.105,7.51583333333333),
(49.2183333,6.70194444444444),
(49.6297222,6.42527777777778),
(49.8091667,6.50277777777778))

Would be cool if that feature would be added in some future versions.

I have a problem installing Flightaware piaware. Running an Odroid XU4, ambrian bionic. Firstly, I am using Joe's ADSB receiver project scripts. First major error, 1090 Flightaware option is not offered as an OS only 1090 mutability. On installing PiAware flightaware, the following error is occuring;

debian/rules build
dh build --with=systemd
dh_update_autotools_config
debian/rules override_dh_auto_configure
make[1]: Entering directory '/home/pi/adsb-receiver/build/piaware_builder/package-jessie'
debian/check_versions
piaware version 3.5.3 matches changelog version 3.5.3, good!
cd tcllauncher && autoconf -f && ./configure --with-tcl=/usr/lib/tcl8.6
checking for correct TEA configuration... ok (TEA 3.9)
configure: configuring Tcllauncher 1.5
checking for Tcl configuration... found /usr/lib/tcl8.6/tclConfig.sh
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for existence of /usr/lib/tcl8.6/tclConfig.sh... loading
checking platform... unix
configure: --prefix defaulting to TCL_PREFIX /usr
configure: --exec-prefix defaulting to TCL_EXEC_PREFIX /usr
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking how to run the C preprocessor... gcc -E
checking whether make sets $(MAKE)... yes
checking for ranlib... ranlib
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking if the compiler understands -pipe... yes
checking whether byte ordering is bigendian... no
checking for sin... no
checking for main in -lieee... no
checking for main in -linet... no
checking net/errno.h usability... no
checking net/errno.h presence... no
checking for net/errno.h... no
checking for connect... yes
checking for gethostbyname... yes
checking dirent.h... yes
checking errno.h usability... yes
checking errno.h presence... yes
checking for errno.h... yes
checking float.h usability... yes
checking float.h presence... yes
checking for float.h... yes
checking values.h usability... yes
checking values.h presence... yes
checking for values.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/wait.h usability... yes
checking sys/wait.h presence... yes
checking for sys/wait.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking for Tcl public headers... /usr/include/tcl8.6
checking for pthread_mutex_init in -lpthread... yes
checking for building with threads... yes (default)
checking how to build libraries... shared
checking for ranlib... (cached) ranlib
checking if 64bit support is requested... no
checking if 64bit Sparc VIS support is requested... no
checking if compiler supports visibility "hidden"... yes
checking if rpath support is requested... yes
checking system version... Linux-4.9.99-odroidxu4
checking for ar... ar
checking for cast to union support... yes
checking for required early compiler flags... _LARGEFILE64_SOURCE
checking for 64-bit integer type... long long
checking for struct dirent64... yes
checking for struct stat64... yes
checking for open64... yes
checking for lseek64... yes
checking for off64_t... yes
checking for build with symbols... no
checking for tclsh... /usr/bin/tclsh8.6
checking for dtplite... /usr/bin/dtplite
configure: creating ./config.status
config.status: creating Makefile
config.status: creating pkgIndex.tcl
config.status: creating tcllauncher-support.tcl
dh override_dh_auto_configure --with=systemd
make[1]: Leaving directory '/home/pi/adsb-receiver/build/piaware_builder/package-jessie'
debian/rules override_dh_auto_build
make[1]: Entering directory '/home/pi/adsb-receiver/build/piaware_builder/package-jessie'
dh_auto_build -D tcllauncher
cd tcllauncher && make -j1
make[2]: Entering directory '/home/pi/adsb-receiver/build/piaware_builder/package-jessie/tcllauncher'
gcc -DPACKAGE_NAME="Tcllauncher" -DPACKAGE_TARNAME="tcllauncher" -DPACKAGE_VERSION="1.5" -DPACKAGE_STRING="Tcllauncher\ 1.5" -DPACKAGE_BUGREPORT="" -DPACKAGE_URL="" -DBUILD_Tcllauncher=/**/ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 -DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 -DTCL_THREADS=1 -DMODULE_SCOPE=extern\ attribute((visibility("hidden"))) -DHAVE_HIDDEN=1 -DHAVE_CAST_TO_UNION=1 -D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_TYPE=long\ long -DHAVE_STRUCT_DIRENT64=1 -DHAVE_STRUCT_STAT64=1 -DHAVE_OPEN64=1 -DHAVE_LSEEK64=1 -DHAVE_TYPE_OFF64_T=1 -DUSE_TCL_STUBS=1 -I./generic -I"/usr/include/tcl8.6" -g -O2 -fdebug-prefix-map=/home/pi/adsb-receiver/build/piaware_builder/package-jessie=. -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -c -O2 -fomit-frame-pointer -DNDEBUG -Wall
-DTCLLAUNCHER_FILE=""/usr/lib/Tcllauncher1.5/tcllauncher.tcl"" unix/tclAppInit.c
gcc -o tcllauncher tclAppInit.o -g -O2 -fdebug-prefix-map=/home/pi/adsb-receiver/build/piaware_builder/package-jessie=. -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -fomit-frame-pointer -DNDEBUG -Wall
-L/usr/lib/arm-linux-gnueabihf -ltcl8.6 -L/usr/lib/arm-linux-gnueabihf -ltclstub8.6 -lpthread
make[2]: Leaving directory '/home/pi/adsb-receiver/build/piaware_builder/package-jessie/tcllauncher'
make -C dump1090 RTLSDR=no BLADERF=no DUMP1090_VERSION="piaware-3.5.3" faup1090
make[2]: Entering directory '/home/pi/adsb-receiver/build/piaware_builder/package-jessie/dump1090'
cc -Wdate-time -D_FORTIFY_SOURCE=2 -DMODES_DUMP1090_VERSION="piaware-3.5.3" -DMODES_DUMP1090_VARIANT="dump1090-fa" -g -O2 -fdebug-prefix-map=/home/pi/adsb-receiver/build/piaware_builder/package-jessie=. -fstack-protector-strong -Wformat -Werror=format-security -std=c11 -O2 -g -Wall -Werror -W -D_DEFAULT_SOURCE -c faup1090.c -o faup1090.o
cc -Wdate-time -D_FORTIFY_SOURCE=2 -DMODES_DUMP1090_VERSION="piaware-3.5.3" -DMODES_DUMP1090_VARIANT="dump1090-fa" -g -O2 -fdebug-prefix-map=/home/pi/adsb-receiver/build/piaware_builder/package-jessie=. -fstack-protector-strong -Wformat -Werror=format-security -std=c11 -O2 -g -Wall -Werror -W -D_DEFAULT_SOURCE -c anet.c -o anet.o
cc -Wdate-time -D_FORTIFY_SOURCE=2 -DMODES_DUMP1090_VERSION="piaware-3.5.3" -DMODES_DUMP1090_VARIANT="dump1090-fa" -g -O2 -fdebug-prefix-map=/home/pi/adsb-receiver/build/piaware_builder/package-jessie=. -fstack-protector-strong -Wformat -Werror=format-security -std=c11 -O2 -g -Wall -Werror -W -D_DEFAULT_SOURCE -c mode_ac.c -o mode_ac.o
cc -Wdate-time -D_FORTIFY_SOURCE=2 -DMODES_DUMP1090_VERSION="piaware-3.5.3" -DMODES_DUMP1090_VARIANT="dump1090-fa" -g -O2 -fdebug-prefix-map=/home/pi/adsb-receiver/build/piaware_builder/package-jessie=. -fstack-protector-strong -Wformat -Werror=format-security -std=c11 -O2 -g -Wall -Werror -W -D_DEFAULT_SOURCE -c mode_s.c -o mode_s.o
cc -Wdate-time -D_FORTIFY_SOURCE=2 -DMODES_DUMP1090_VERSION="piaware-3.5.3" -DMODES_DUMP1090_VARIANT="dump1090-fa" -g -O2 -fdebug-prefix-map=/home/pi/adsb-receiver/build/piaware_builder/package-jessie=. -fstack-protector-strong -Wformat -Werror=format-security -std=c11 -O2 -g -Wall -Werror -W -D_DEFAULT_SOURCE -c net_io.c -o net_io.o
cc -Wdate-time -D_FORTIFY_SOURCE=2 -DMODES_DUMP1090_VERSION="piaware-3.5.3" -DMODES_DUMP1090_VARIANT="dump1090-fa" -g -O2 -fdebug-prefix-map=/home/pi/adsb-receiver/build/piaware_builder/package-jessie=. -fstack-protector-strong -Wformat -Werror=format-security -std=c11 -O2 -g -Wall -Werror -W -D_DEFAULT_SOURCE -c crc.c -o crc.o
cc -Wdate-time -D_FORTIFY_SOURCE=2 -DMODES_DUMP1090_VERSION="piaware-3.5.3" -DMODES_DUMP1090_VARIANT="dump1090-fa" -g -O2 -fdebug-prefix-map=/home/pi/adsb-receiver/build/piaware_builder/package-jessie=. -fstack-protector-strong -Wformat -Werror=format-security -std=c11 -O2 -g -Wall -Werror -W -D_DEFAULT_SOURCE -c stats.c -o stats.o
cc -Wdate-time -D_FORTIFY_SOURCE=2 -DMODES_DUMP1090_VERSION="piaware-3.5.3" -DMODES_DUMP1090_VARIANT="dump1090-fa" -g -O2 -fdebug-prefix-map=/home/pi/adsb-receiver/build/piaware_builder/package-jessie=. -fstack-protector-strong -Wformat -Werror=format-security -std=c11 -O2 -g -Wall -Werror -W -D_DEFAULT_SOURCE -c cpr.c -o cpr.o
cc -Wdate-time -D_FORTIFY_SOURCE=2 -DMODES_DUMP1090_VERSION="piaware-3.5.3" -DMODES_DUMP1090_VARIANT="dump1090-fa" -g -O2 -fdebug-prefix-map=/home/pi/adsb-receiver/build/piaware_builder/package-jessie=. -fstack-protector-strong -Wformat -Werror=format-security -std=c11 -O2 -g -Wall -Werror -W -D_DEFAULT_SOURCE -c icao_filter.c -o icao_filter.o
cc -Wdate-time -D_FORTIFY_SOURCE=2 -DMODES_DUMP1090_VERSION="piaware-3.5.3" -DMODES_DUMP1090_VARIANT="dump1090-fa" -g -O2 -fdebug-prefix-map=/home/pi/adsb-receiver/build/piaware_builder/package-jessie=. -fstack-protector-strong -Wformat -Werror=format-security -std=c11 -O2 -g -Wall -Werror -W -D_DEFAULT_SOURCE -c track.c -o track.o
cc -Wdate-time -D_FORTIFY_SOURCE=2 -DMODES_DUMP1090_VERSION="piaware-3.5.3" -DMODES_DUMP1090_VARIANT="dump1090-fa" -g -O2 -fdebug-prefix-map=/home/pi/adsb-receiver/build/piaware_builder/package-jessie=. -fstack-protector-strong -Wformat -Werror=format-security -std=c11 -O2 -g -Wall -Werror -W -D_DEFAULT_SOURCE -c util.c -o util.o
cc -g -o faup1090 faup1090.o anet.o mode_ac.o mode_s.o net_io.o crc.o stats.o cpr.o icao_filter.o track.o util.o -Wl,-Bsymbolic-functions -Wl,-z,relro -lpthread -lm -lrt
make[2]: Leaving directory '/home/pi/adsb-receiver/build/piaware_builder/package-jessie/dump1090'
pyvenv /home/pi/adsb-receiver/build/piaware_builder/package-jessie/debian/venv --without-pip
WARNING: the pyenv script is deprecated in favour of python3.6 -m venv
cd cx_Freeze-4.3.4 && /home/pi/adsb-receiver/build/piaware_builder/package-jessie/debian/venv/bin/python ./setup.py install
Traceback (most recent call last):
File "./setup.py", line 138, in
finder = cx_Freeze.ModuleFinder(bootstrap = True)
File "/home/pi/adsb-receiver/build/piaware_builder/package-jessie/cx_Freeze-4.3.4/cx_Freeze/finder.py", line 160, in init
self._AddBaseModules()
File "/home/pi/adsb-receiver/build/piaware_builder/package-jessie/cx_Freeze-4.3.4/cx_Freeze/finder.py", line 187, in _AddBaseModules
self.IncludeModule("traceback")
File "/home/pi/adsb-receiver/build/piaware_builder/package-jessie/cx_Freeze-4.3.4/cx_Freeze/finder.py", line 687, in IncludeModule
namespace = namespace)
File "/home/pi/adsb-receiver/build/piaware_builder/package-jessie/cx_Freeze-4.3.4/cx_Freeze/finder.py", line 355, in _ImportModule
deferredImports, namespace = namespace)
File "/home/pi/adsb-receiver/build/piaware_builder/package-jessie/cx_Freeze-4.3.4/cx_Freeze/finder.py", line 445, in _InternalImportModule
parentModule, namespace)
File "/home/pi/adsb-receiver/build/piaware_builder/package-jessie/cx_Freeze-4.3.4/cx_Freeze/finder.py", line 511, in _LoadModule
self._ScanCode(module.code, module, deferredImports)
File "/home/pi/adsb-receiver/build/piaware_builder/package-jessie/cx_Freeze-4.3.4/cx_Freeze/finder.py", line 597, in _ScanCode
arguments.append(co.co_consts[opArg])
IndexError: tuple index out of range
debian/rules:55: recipe for target 'build_cxfreeze' failed
make[1]: *** [build_cxfreeze] Error 1
make[1]: Leaving directory '/home/pi/adsb-receiver/build/piaware_builder/package-jessie'
debian/rules:83: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Installing the FlightAware PiAware client package...

dpkg: error: cannot access archive '/home/pi/adsb-receiver/build/piaware_builder/piaware_*.deb': No such file or directory

Checking that the FlightAware PiAware client package was installed properly...

INSTALLATION HALTED!
UNABLE TO INSTALL A REQUIRED PACKAGE.
SETUP HAS BEEN TERMINATED!

The package "piaware" could not be installed.

FlightAware PiAware client setup halted.

On current Gentoo, itcl-3.4 depends on tcl<8.6, but the only available version of tclx, 8.4.1, depends on tcl>8.6.

Hello

Are there best practices or documentation to enable basic auth on a piaware install for the web interface?

thanks

using piaware image. works fine with cable connection but i can't configure a wifi connection. entered passcode and everything in the piaware config txt.
But no luck with connecting to a wifi.
any idea?

I believe the new model can not boot using the current PiAware software, users having to update there card in the model B before using that card in a new 3 B+ and there are other issues arising with Pi Aware. Any idea on an update being released??

i've confingured piaware to connect to a locally running airspy_adsb (r-pi version 1.1 serving an AVR stream)

02/17/2016 17:56:45 mlat(5300): fa-mlat-client 0.2.4 starting up
02/17/2016 17:56:45 mlat(5300): Using UDP transport to 70.42.6.198:5110
02/17/2016 17:56:45 mlat(5300): Listening for Basestation-format results connection on port 31003
02/17/2016 17:56:45 mlat(5300): Input connected to localhost:30005
02/17/2016 17:56:45 mlat(5300): Unexpected exception on connection to localhost:30005
02/17/2016 17:56:45 mlat(5300): Traceback (most recent call last):
02/17/2016 17:56:45 mlat(5300): File "/usr/lib/python3.2/asyncore.py", line 83, in read
02/17/2016 17:56:45 mlat(5300): File "/usr/lib/python3.2/asyncore.py", line 449, in handle_read_event
02/17/2016 17:56:45 mlat(5300): File "/tmp/buildd/piaware-2.1/debian/venv/lib/python3.2/site-packages/mlat/client/receiver.py", line 129, in handle_read
02/17/2016 17:56:45 mlat(5300): ValueError: Lost sync with input stream: expected a 0x1A marker at offset 0 but found 0x2a instead
02/17/2016 17:56:45 mlat(5300): Lost connection to localhost:30005

I finally have gpsd up and running on the Orange Pi. Is it okay to run the dev version, or would you prefer that not be run until further testing is done? I'm aware that it may break my setup, I just don't want to break FA's setup. I'd be happy to beta the software for you as another data point.

Getting a "tuple index out of range" error when building PiAware on Ubuntu 17.10.

pyvenv /home/joe/adsb-receiver/build/piaware_builder/package-jessie/debian/venv --without-pip
WARNING: the pyenv script is deprecated in favour of `python3.6 -m venv`
cd cx_Freeze-4.3.4 && /home/joe/adsb-receiver/build/piaware_builder/package-jessie/debian/venv/bin/python ./setup.py install
Traceback (most recent call last):
  File "./setup.py", line 138, in <module>
    finder = cx_Freeze.ModuleFinder(bootstrap = True)
  File "/home/joe/adsb-receiver/build/piaware_builder/package-jessie/cx_Freeze-4.3.4/cx_Freeze/finder.py", line 160, in __init__
    self._AddBaseModules()
  File "/home/joe/adsb-receiver/build/piaware_builder/package-jessie/cx_Freeze-4.3.4/cx_Freeze/finder.py", line 187, in _AddBaseModules
    self.IncludeModule("traceback")
  File "/home/joe/adsb-receiver/build/piaware_builder/package-jessie/cx_Freeze-4.3.4/cx_Freeze/finder.py", line 687, in IncludeModule
    namespace = namespace)
  File "/home/joe/adsb-receiver/build/piaware_builder/package-jessie/cx_Freeze-4.3.4/cx_Freeze/finder.py", line 355, in _ImportModule
    deferredImports, namespace = namespace)
  File "/home/joe/adsb-receiver/build/piaware_builder/package-jessie/cx_Freeze-4.3.4/cx_Freeze/finder.py", line 445, in _InternalImportModule
    parentModule, namespace)
  File "/home/joe/adsb-receiver/build/piaware_builder/package-jessie/cx_Freeze-4.3.4/cx_Freeze/finder.py", line 511, in _LoadModule
    self._ScanCode(module.code, module, deferredImports)
  File "/home/joe/adsb-receiver/build/piaware_builder/package-jessie/cx_Freeze-4.3.4/cx_Freeze/finder.py", line 597, in _ScanCode
    arguments.append(co.co_consts[opArg])
IndexError: tuple index out of range
debian/rules:55: recipe for target 'build_cxfreeze' failed
make[1]: *** [build_cxfreeze] Error 1
make[1]: Leaving directory '/home/joe/adsb-receiver/build/piaware_builder/package-jessie'
debian/rules:83: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

If you need more output from the build let me know.

netstat without -n can take a long time to complete (minutes!) as it needs to do reverse-DNS on potentially a long list of addresses, many of which might time out.

piaware blocks while it waits for this output, which isn't great.

Best option would be to pass -n, but you'd have to do something about explicitly looking for "eyes.flightaware.com" then.

Hi there,

I've installed piaware using the piaware_builder repository for a Debian wheezy system, successfully. This was using the rtl_sdr repository from osmocom and the dump1090 repository from flightaware. The program installs fine, the startup service is ok, and I have successfully configured my username password so that I am connecting to/logging in to the FlightAware servers. I can see this from running the following command:

systemctl status piaware

(as per the last instruction in the piaware repo README). However, at the very end of the output from this command, I see the following message:

piaware[1172]: no ADS-B data program seen listening on port 30005 for 123 seconds, next check in 60s

I'm not sure what that means (what it means by ADS-B program). Perhaps related (but again, not understanding what this means) is the fact that https://flightaware.com/adsb/stats/user/charlesreid1 says "No Such ADS-B Site". I'm able to receive signals just fine, because I see signals from planes when I run:

dump1090 --interactive

which runs smoothly. Further confounding the issue is the fact that there is no /var/log/piaware log file generated. When I check the piaware claim your receiver site, I see the receiver show up in the list.

Any suggestions as to how to fix the ADS-B problem, or figure out what's going on with the log file, would be awesome & much appreciated.

Hi, there! I've met a probelm trying to config my feeder-id
When I tried:
sudo piaware-config feeder-id XXXXXXXXXXXXXXXXXXXXXXXXX
It shows: could not set option 'feeder-id' to value 'XXXXXXXXXXXXXXXXXXXXXXXXX' as all config files are read-only
It happens when I try to turn 'allow-auto-updates' to yes

I'm running on Debian Buster with dump1090-fa operating perfectly.

I've tried to chmod every file that looked like a config file related to piaware but that didn't make things any better.

So help me.

It would be great if you have a mobile friendly site if you open the local side in your Webbrowser.

Opened a new issue as there is a new version by @touil with beast support (-f beast) here http://airspy.com/downloads/airspy_adsb-linux-arm-beast.tgz
The stream is pushing 20MHz MLAT, could that give the issues below ?

mlat(7442): Problem reading receiver messages: Out of range timestamp seen (last 4142366797, now 553222221)
02/17/2016 22:07:42 mlat(7442): Traceback (most recent call last):
02/17/2016 22:07:42 mlat(7442): File "/usr/lib/python3.2/asyncore.py", line 83, in read
02/17/2016 22:07:42 mlat(7442): File "/usr/lib/python3.2/asyncore.py", line 449, in handle_read_event
02/17/2016 22:07:42 mlat(7442): File "/tmp/buildd/piaware-2.1/debian/venv/lib/python3.2/site-packages/mlat/client/receiver.py", line 129, in handle_read
02/17/2016 22:07:42 mlat(7442): ValueError: Lost sync with input stream: expected 0x1A after 0x1A escape

maybe issue like : mutability/mlat-client#1

The link to download the piaware image on flightaware is not via TLS. Can you publish a hash or signature to verify the build?
Thank you.

Hi!

Piaware reports back the internal IP address and exposes that as a link on the users flightaware page.

https://flightaware.com/adsb/stats/user/ shows the internal IP and port of the local webinterface
under "site information": "Web Interface: View live data (requires local network connection)"
which show something like: http://172.17.0.6:8080/

Especially with using docker this internal address might not even be accessible.

It would be nice if the behaviour could be set / overwritten.

Like behaviour:
default export any internal address)
manual (configure protocol (http/https), host/ip, port as whatever you like)
auto-docker (get the hosts ip/port if this is even possible

Does the receiver-port config setting work? I use a custom port (30054) and I have to go through the source code of each release and replace every instance of 30005 with 30054 to get it to work. Thanks!

Not sure if you know this, and it's probably a minor thing, but when looking at the local map (:8080) on my laptop, letting it pick up a bunch of planes, then I shut my laptop for a while, later when I open it again, the map doesn't seem to remove the old planes.

The only choice when entering your location is "I would like to pick my receiver's location on a map." Please add a choice "I know my exact location and would like to enter it directly" (or however you want to word it) for those of us who already know our precise latitude and longitude.

In the directory dump1090/public_html/db, a json repository contains the relation between the ICAO code, aircraft registration and type. Before this database was generated, using the scripts in the tools/ directory. However, these tools are obsolete as the source is no longer updated.

So how is this database generated these days? Is it possible to update the database myself? I guess a script is used, can you share this script?

When running in an unprivileged Docker container, everything functionally works fine as long as the proper USB device is passed in, but piaware-status reports:

root@98cec28c1d21:/# piaware-status 
PiAware master process (piaware) is running with pid 52.
PiAware ADS-B client (faup1090) is running with pid 90.
PiAware mlat client (fa-mlat-client) is running with pid 92.
Local ADS-B receiver (dump1090-fa) is running with pid 69.

unknown process (pid unknown) is listening for connections on port 30005.
faup1090 is NOT connected to the ADS-B receiver.
piaware is NOT connected to FlightAware.

dump1090 is producing data on localhost:30005.

Your feeder ID is [UUID] (configured at /etc/piaware.conf:9)

This is because socket to PID mappings aren't available:

root@98cec28c1d21:/# netstat --program --tcp --wide --all --numeric
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      -                   
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      -                   
tcp        0      0 0.0.0.0:30002           0.0.0.0:*               LISTEN      -                   
tcp        0      0 0.0.0.0:30003           0.0.0.0:*               LISTEN      -                   
tcp        0      0 0.0.0.0:30004           0.0.0.0:*               LISTEN      -                   
tcp        0      0 0.0.0.0:30005           0.0.0.0:*               LISTEN      -                   
tcp        0      0 0.0.0.0:30104           0.0.0.0:*               LISTEN      -                   
tcp        0      0 172.17.0.2:30002        172.17.0.1:55756        ESTABLISHED -                   
tcp        0      0 172.17.0.2:39529        70.42.6.198:1200        ESTABLISHED -                   
tcp        0      0 172.17.0.2:8080         10.9.8.4:59512          TIME_WAIT   -                   
tcp        0      0 127.0.0.1:46626         127.0.0.1:30005         ESTABLISHED -                   
tcp        0      0 127.0.0.1:55802         127.0.0.1:30104         ESTABLISHED -                   
tcp        0      0 127.0.0.1:30104         127.0.0.1:55802         ESTABLISHED -                   
tcp        0      0 172.17.0.2:8080         10.9.8.4:59504          TIME_WAIT   -                   
tcp        0      0 127.0.0.1:30005         127.0.0.1:46736         ESTABLISHED -                   
tcp        0      0 172.17.0.2:30005        172.17.0.1:39564        ESTABLISHED -                   
tcp        0      0 127.0.0.1:30005         127.0.0.1:46626         ESTABLISHED -                   
tcp        0      0 127.0.0.1:46736         127.0.0.1:30005         ESTABLISHED -                   
tcp        0      0 172.17.0.2:8080         10.9.8.4:59498          TIME_WAIT   -                   
tcp6       0      0 :::30002                :::*                    LISTEN      -                   
tcp6       0      0 :::30003                :::*                    LISTEN      -                   
tcp6       0      0 :::30004                :::*                    LISTEN      -                   
tcp6       0      0 :::30005                :::*                    LISTEN      -                   
tcp6       0      0 :::30104                :::*                    LISTEN      -                   
tcp6       0      0 :::30105                :::*                    LISTEN      -                   
tcp6       0      0 :::30106                :::*                    LISTEN      -                   

piaware-status should probably check for this situation; e.g. ":1200" and program "-" should report something like "piaware is probably connected to FlightAware, but cannot be certain due to environment restrictions." instead of "piaware is NOT connected to FlightAware."

My piaware seemed to have changed it's password from the actual password to 'olivertest' by itself at some point last week in piaware.conf. The username remained unchanged. Any idea what could have happened there ?

Hello,
I recently fired up my ads-b receiver, in the past I fed my data succesfully to FA, however now I cannot establish a connection with the server, probably because I am getting this message:

piaware[2276]: Certificate validation with adept server at piaware.flightaware.com/1200 failed: required field 'subject' is missing

Is something wrong with my configuration?

I'm running piaware-git on ArchLinux.

Wifi network contains a value utf-8 character (e-grave which prints as "è"). With this character entered in /boot/piaware-config.txt, resulting wpa-supplicant.conf is "??" instead of the e-grave character. None of the obvious quote patterns (quoting the string, single backslash, double backslash, unicode (u)) work. Looks like the character handling doesn't support utf-8 (and probably utf-16). Converting the SSID to hex in piaware-config.txt also doesn't work.

Is the relay type broken?
when I set receiver=other, I see 2 connections opened on the host, and data flows directly to FA.
if I then change the receiver type to relay, I never see any connections get opened on the host, and the piaware process keeps restarting itself due to no data.

This is with receiver= other
Jan 12 11:49:22 raspberrypi piaware[1206]: mlat-client(1225): Receiver status: connected
Jan 12 11:49:22 raspberrypi piaware[1206]: mlat-client(1225): Server status: not synchronized with any nearby receivers
Jan 12 11:49:22 raspberrypi piaware[1206]: mlat-client(1225): Receiver: 1685.6 msg/s received 429.0 msg/s processed (25%)
Jan 12 11:49:22 raspberrypi piaware[1206]: mlat-client(1225): Server: 0.0 kB/s from server 0.1kB/s TCP to server 0.1kB/s UDP to server
Jan 12 11:49:22 raspberrypi piaware[1206]: mlat-client(1225): Aircraft: 62 of 160 Mode S, 101 of 161 ADS-B used
Jan 12 11:49:53 raspberrypi piaware[1206]: 43972 msgs recv'd from the ADS-B data program at 192.168.3.11/30334 (14890 in last 5m); 43972 msgs sent to FlightAware
Jan 12 11:54:53 raspberrypi piaware[1206]: 58142 msgs recv'd from the ADS-B data program at 192.168.3.11/30334 (14170 in last 5m); 58142 msgs sent to FlightAware
Jan 12 11:59:53 raspberrypi piaware[1206]: 71728 msgs recv'd from the ADS-B data program at 192.168.3.11/30334 (13586 in last 5m); 71728 msgs sent to FlightAware

Changing the receiver to relay results in almost no data.
Jan 12 12:04:07 raspberrypi piaware[468]: mlat-client(912): Listening for Beast-format results connection on port 30105
Jan 12 12:04:07 raspberrypi piaware[468]: mlat-client(912): Listening for Extended Basestation-format results connection on port 30106
Jan 12 12:04:07 raspberrypi piaware[468]: mlat-client(912): Route MTU changed to 1500
Jan 12 12:04:07 raspberrypi piaware[468]: mlat-client(912): Input connected to localhost:30005
Jan 12 12:04:07 raspberrypi piaware[468]: mlat-client(912): Detected BEAST format input
Jan 12 12:04:07 raspberrypi piaware[468]: mlat-client(912): Input format changed to BEAST, 12MHz clock
Jan 12 12:04:07 raspberrypi piaware[468]: mlat-client(912): Beast-format results connection with ::1:30104: connection established
Jan 12 12:04:34 raspberrypi piaware[468]: 3 msgs recv'd from dump1090-fa; 2 msgs sent to FlightAware
Jan 12 12:04:55 raspberrypi piaware[468]: piaware has successfully sent several msgs to FlightAware!

and as I said, the host doesn't show an active connection. Is there something else I must do to get the relay working?

STATUS:

RECEIVER SOFTWARE: ON [stop, display log]
RAW FEED [30334]: UP, NUM CONNECTED: 0
BS FEED [30003]: UP, NUM CONNECTED: 0

With update to 3.0.2, piaware keeps disconnecting from the fa server every minute or so, no communication visible on the stats web page at all. Was working fine before the update from 2.1.5

Aug 02 01:21:03 inktomi piaware[28036]: piaware version 3.0.2 is running, process ID 28036
Aug 02 01:21:03 inktomi piaware[28036]: your system info is: Linux inktomi 4.1.18-2-ARCH #1 Thu Feb 25 19:27:02 MST 2016 armv6l GNU/Linux
Aug 02 01:21:05 inktomi piaware[28036]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Aug 02 01:21:05 inktomi piaware[28036]: Connection with adept server at piaware.flightaware.com/1200 established
Aug 02 01:21:06 inktomi piaware[28036]: FlightAware server SSL certificate validated
Aug 02 01:21:06 inktomi piaware[28036]: encrypted session established with FlightAware
Aug 02 01:21:08 inktomi piaware[28036]: ADS-B data program 'dump1090' is listening on port 30005, so far so good
Aug 02 01:21:08 inktomi piaware[28036]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
Aug 02 01:21:08 inktomi piaware[28036]: Started faup1090 (pid 28065) to connect to dump1090
Aug 02 01:21:09 inktomi piaware[28036]: Lost connection to adept server at piaware.flightaware.com/1200: server closed connection
Aug 02 01:21:09 inktomi piaware[28036]: reconnecting in 54 seconds...
Aug 02 01:21:10 inktomi piaware[28036]: piaware received a message from dump1090!
Aug 02 01:21:39 inktomi piaware[28036]: 1 msgs recv'd from dump1090; 0 msgs sent to FlightAware
Aug 02 01:22:03 inktomi piaware[28036]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Aug 02 01:22:03 inktomi piaware[28036]: Connection with adept server at piaware.flightaware.com/1200 established
Aug 02 01:22:04 inktomi piaware[28036]: FlightAware server SSL certificate validated
Aug 02 01:22:04 inktomi piaware[28036]: encrypted session established with FlightAware
Aug 02 01:22:05 inktomi piaware[28036]: Lost connection to adept server at piaware.flightaware.com/1200: server closed connection
Aug 02 01:22:05 inktomi piaware[28036]: reconnecting in 54 seconds...
Aug 02 01:22:59 inktomi piaware[28036]: Connecting to FlightAware adept server at 70.42.6.197/1200
Aug 02 01:22:59 inktomi piaware[28036]: Connection with adept server at 70.42.6.197/1200 established
Aug 02 01:22:59 inktomi piaware[28036]: FlightAware server SSL certificate validated
Aug 02 01:22:59 inktomi piaware[28036]: encrypted session established with FlightAware
Aug 02 01:23:00 inktomi piaware[28036]: Lost connection to adept server at 70.42.6.197/1200: server closed connection
Aug 02 01:23:00 inktomi piaware[28036]: reconnecting in 56 seconds...
Aug 02 01:23:56 inktomi piaware[28036]: Connecting to FlightAware adept server at 70.42.6.198/1200
Aug 02 01:23:56 inktomi piaware[28036]: Connection with adept server at 70.42.6.198/1200 established
Aug 02 01:23:57 inktomi piaware[28036]: FlightAware server SSL certificate validated
Aug 02 01:23:57 inktomi piaware[28036]: encrypted session established with FlightAware
Aug 02 01:23:58 inktomi piaware[28036]: Lost connection to adept server at 70.42.6.198/1200: server closed connection
Aug 02 01:23:58 inktomi piaware[28036]: reconnecting in 53 seconds...
Aug 02 01:24:51 inktomi piaware[28036]: Connecting to FlightAware adept server at 70.42.6.191/1200
Aug 02 01:24:51 inktomi piaware[28036]: Connection with adept server at 70.42.6.191/1200 established
Aug 02 01:24:52 inktomi piaware[28036]: FlightAware server SSL certificate validated
Aug 02 01:24:52 inktomi piaware[28036]: encrypted session established with FlightAware
Aug 02 01:24:52 inktomi piaware[28036]: Lost connection to adept server at 70.42.6.191/1200: server closed connection
Aug 02 01:24:52 inktomi piaware[28036]: reconnecting in 64 seconds...
Aug 02 01:25:56 inktomi piaware[28036]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Aug 02 01:25:57 inktomi piaware[28036]: Connection with adept server at piaware.flightaware.com/1200 established
Aug 02 01:25:57 inktomi piaware[28036]: FlightAware server SSL certificate validated
Aug 02 01:25:57 inktomi piaware[28036]: encrypted session established with FlightAware
Aug 02 01:25:58 inktomi piaware[28036]: Lost connection to adept server at piaware.flightaware.com/1200: server closed connection
Aug 02 01:25:58 inktomi piaware[28036]: reconnecting in 61 seconds...
Aug 02 01:26:39 inktomi piaware[28036]: 2 msgs recv'd from dump1090 (1 in last 5m); 0 msgs sent to FlightAware
Aug 02 01:26:59 inktomi piaware[28036]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Aug 02 01:27:00 inktomi piaware[28036]: Connection with adept server at piaware.flightaware.com/1200 established
Aug 02 01:27:00 inktomi piaware[28036]: FlightAware server SSL certificate validated
Aug 02 01:27:00 inktomi piaware[28036]: encrypted session established with FlightAware
Aug 02 01:27:01 inktomi piaware[28036]: Lost connection to adept server at piaware.flightaware.com/1200: server closed connection
Aug 02 01:27:01 inktomi piaware[28036]: reconnecting in 55 seconds...
Aug 02 01:27:56 inktomi piaware[28036]: Connecting to FlightAware adept server at 70.42.6.197/1200
Aug 02 01:27:56 inktomi piaware[28036]: Connection with adept server at 70.42.6.197/1200 established
Aug 02 01:27:57 inktomi piaware[28036]: FlightAware server SSL certificate validated
Aug 02 01:27:57 inktomi piaware[28036]: encrypted session established with FlightAware
Aug 02 01:27:58 inktomi piaware[28036]: Lost connection to adept server at 70.42.6.197/1200: server closed connection
Aug 02 01:27:58 inktomi piaware[28036]: reconnecting in 52 seconds...
Aug 02 01:28:50 inktomi piaware[28036]: Connecting to FlightAware adept server at 70.42.6.198/1200
Aug 02 01:28:50 inktomi piaware[28036]: Connection with adept server at 70.42.6.198/1200 established
Aug 02 01:28:50 inktomi piaware[28036]: FlightAware server SSL certificate validated
Aug 02 01:28:50 inktomi piaware[28036]: encrypted session established with FlightAware
Aug 02 01:28:51 inktomi piaware[28036]: Lost connection to adept server at 70.42.6.198/1200: server closed connection
Aug 02 01:28:51 inktomi piaware[28036]: reconnecting in 66 seconds...
Aug 02 01:29:57 inktomi piaware[28036]: Connecting to FlightAware adept server at 70.42.6.191/1200
Aug 02 01:29:58 inktomi piaware[28036]: Connection with adept server at 70.42.6.191/1200 established
Aug 02 01:29:58 inktomi piaware[28036]: FlightAware server SSL certificate validated
Aug 02 01:29:58 inktomi piaware[28036]: encrypted session established with FlightAware
Aug 02 01:29:59 inktomi piaware[28036]: Lost connection to adept server at 70.42.6.191/1200: server closed connection
Aug 02 01:29:59 inktomi piaware[28036]: reconnecting in 71 seconds...

Hello, ive been running piaware for just over a year and have only installed what I needed to run my pi. Recently ive installed mysql with phpmyadmin for localhost use only. Less than a day of having it installed I had noticed my tables were gone and replaced with 1 table for ransomware.(what ever it wasn't important) but of course im a bit on edge on what caused it.

Now of course I am not saying that it was caused by piaware but seeing as its the main os for my pi I thought id make a note of this and seek some help/advice on what to do.

I am interested in trying PiAware on my Raspberry Pi which is running FreeBSD-arm, and exploring the possibility to port PiAware to FreeBSD. I would like to know if there's a more generic build tool, or the requirements of successfully building a standalone PiAware and the required dependencies. Thanks!

With a non-english locale, netstat might report unexpected values for the connection states; this confuses piaware's parser.

Hi,
Not sure if you are aware but it looks like there is a bug with the local map display. I looked up the error code and it seems like it may be related to google changing their map API?

Thanks,
Joe

With 3.8.0~bpo9+1 (installed semiautomatically over time from an 3.5ish initial installation),
While the mlat* programs do know our location, the dump1080-fa program doesn't, so the web map lacks the proper location / range-rings,
apparently because /var/cache/piaware/location.env was not created with the correct PIAWARE_LAT/_LON variable settings.

ISTM there should be one central place where location coordinates are stored on piaware, and it should include the dump1080-fa AND the mlat daemons as readers.

The setup screen only allows me to enter my antenna height in feet. Please add the ability to select meters so those in countries that use metric measurements don't have to take the extra step to convert to feet.

Edit: never mind, my system was upgraded to PiAware 6.1 after installation which already has this feature. It didn't yesterday (that I noticed) when I first installed version 6.0.

Hello
I'm using translation because I'm not good at the English. sorry.
I'm trying to feed using the recently released pi3 a +. It seems that the cpu performance is better than pi2 and pi3, so basically I'm not dissatisfied, but for some reason I can't feed to flightaware. I have installed the package and dump1090-fa is working properly and is able to feed other services. However, even if I try using the top command, piaware is not working and it is not displayed on the flightaware management screen.
Is there any workaround for this?
I'm sorry for the rudimentary question. Thank you for reading the long text.