Betaflight & INAV CLI Diff Checker

What it checks

Every set name = value line of the pasted diff all is read against the firmware and release you pick, from the same files the settings reference (Betaflight, INAV) is built from:

• Not a setting of this release - the name is not in the release's settings.c (INAV: settings.yaml), so the CLI rejects the line with an invalid-name error.
• Renamed - the name is gone, and the firmware's own pull request or release documentation says a new name is the same setting (for example dshot_idle_value became motor_idle in Betaflight 2025.12, and controlrate_profile became use_control_profile in INAV 9.0). Change the name and keep the value.
• Out of range / not a value - a number outside the setting's minimum and maximum (INAV's decimal settings included), a word that is not in its value list, or an array with the wrong number of entries.
• Equals the default - the line sets what the firmware already sets, so it can go. Board configs can change defaults, so on a board whose target sets this value differently the line still matters.

Other commands (aux, serial, resource, feature, map...) are counted but not checked: they depend on the board, not on the release.

Moving a diff between releases

If the diff starts with its header line (# Betaflight / ... 4.5.1 or # INAV/MATEKH743 8.0.1), the checker reads the firmware and the version it came from, switches to that firmware, and tells removed settings apart from names that never existed. The per-release changes are listed in full on the Betaflight 4.4 → 4.5, 4.5 → 2025.12 and 2025.12 → 2026.6 pages, and the INAV 8.0 → 9.0 and 9.0 → 9.1 pages.

Profile commands (profile, rateprofile, INAV's control_profile, mixer_profile, battery_profile) only switch which profile the next lines write to, so they are skipped rather than counted.

Nothing is uploaded: the page downloads the release's params.json once and compares in your browser.