Greg Albrecht W2GMD

I can confirm that running `systemctl stop zerotier-one` before running wifi-connect is a work-around.

With the help of someone who speaks Rust, I was able to drill down from wifi-connect -> balena-networkmanager -> dbus 0.5. Balena's network-manager calls ListConnections: https://github.com/balena-io-modules/network-manager/blob/4da2e6a57de16b6ae911f74321f929d78af8b1ba/src/dbus_nm.rs#L86 Here's what the call...

If you're also seeing this on AirTAK, it's running adsbcot, and the bug was reported with adsbxcot. It could be we're not converting from ADS-B values to CoT values correctly...

Here's how dump1090-fa spits out heading ``` if (mm->heading_valid && mm->heading_source == HEADING_TRUE && accept_data(&a->heading_valid, mm->source, now)) { a->heading = mm->heading; } if (mm->heading_valid && mm->heading_source == HEADING_MAGNETIC && accept_data(&a->heading_magnetic_valid,...

From the CoT Spec: ``` Direction of motion with respect to true north. Measured in degrees. ```

it shouldn't be crashing, it should just ignore the bad data. if you're seeing it crash, can you send me the stack trace? On Wed, Feb 15, 2023 at 6:01...

What ADS-B source are you using? (mind sharing your config.ini?)

Hey @gncnpk, if you're running locally, I recommend switching to the new ``file://`` based behavior, see: https://adsbcot.readthedocs.io/en/latest/config.html

@daskalovst Are you running adsbcot on an Adsbexchange Pi image?

I believe there is a mismatch between what I interpreted as 'raw' vs 'beast' and what dump1090 puts out, so try to switch the flags from 'tcp+beast' to 'tcp+raw' across...