Skip to content

FlightAware showing far more "Other" aircraft since switching from dedicated PiAware OS — readsb vs. dump1090-fa? #564

Description

@FormelLMS

I recently migrated from a dedicated PiAware OS device to this add-on on HAOS (same location, same antenna/SDR setup, no other changes). Since then, FlightAware's stats page shows a much higher share of aircraft classified as "Other" instead of ADS-B or Mode-S (MLAT), compared to before the migration.
Piaware itself looks healthy — it connects via receiver-type relay to the local decoder on port 30005 (Beast), MLAT is synchronized with several hundred nearby receivers, and positions are being calculated fine.
While digging into this, I noticed the Dockerfile pulls in readsb (COMMIT_READSB) rather than dump1090-fa, even though the README/description still mentions dump1090-fa. My (unconfirmed) guess is that differences in how readsb vs. dump1090-fa decode/classify messages might affect how piaware/FlightAware end up categorizing them as ADS-B/Mode-S vs. "Other."
Does that sound plausible, or is there something else that changed with the migration that could explain this? And is there any way to configure/select dump1090-fa instead of readsb, or is that no longer supported since the switch?
Happy to share full piaware logs if useful.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions