v1.0.25
Three installer safety fixes
1. Fix BIN_DIR/CLI_DIR mismatch (critical)
install_services() was still referencing ${BIN_DIR} after it was renamed to CLI_DIR in v1.0.18. Without set -u, the variable expanded to empty string and droneaware-bt-select was silently written to /droneaware-bt-select instead of /usr/local/bin/droneaware-bt-select. This likely caused intermittent install failures that were hard to diagnose.
2. Active interface safety check
pin_wifi_unmanaged now checks whether the detected USB WiFi adapter is currently the active network interface (via ip route get 1.1.1.1). If it is, the installer exits with a clear error message rather than marking it unmanaged and killing SSH. Prevents the scenario where a headless Pi loses all network access mid-install.
3. NetworkManager rollback trap
If the installer fails after writing /etc/NetworkManager/conf.d/droneaware.conf, a trap handler automatically removes the file and restores the adapter to managed state. The Pi's WiFi connection should recover without manual intervention.
install.sh only — no binary changes.