MeshCore 1.17.1.8 USA Cascade

This release uses 910.525 MHz, 62.5 kHz bandwidth, SF7, and CR5 with Cascade defaults. Saved radio settings take precedence. The firmware source is 9053038ffa7f481e4b0af2bb8382210683a2c317.

The release family contains 536 qualified firmware profiles on 5 GitHub release pages. The Companion page is GitHub's Latest release; supporting pages have the same version suffix. The firmware picker and Mesh America catalogs select this family.

Changes since 1.17.1.7

Full Companion Wi-Fi settings use the official app's commands. WebConfig uses gzip assets and includes the older Android Chrome startup fix. Full builds check these capabilities during qualification.
Companion get radio keeps upstream's four-field CSV response without a preamble field. CLI availability still depends on the image and the app's protocol support; a version number alone does not enable commands.
nRF52 builds preserve SoftDevice memory side effects under LTO. Full Companion BLE subscriptions persist across reboot. Optional USB-exported Bluetooth diagnostics are available for investigation and are disabled in ordinary release builds.
OTA relays restore temporary hop limits and radio settings, with corrected relayed retries and guarded legacy RAK3401 recovery.
Companion alerts add vibration, sound, LED, screen and GPIO controls, contact/channel rules, and trusted DM or room !notify requests. Preview audio keeps its opening notes.
Consent-gated private messaging can start with one known public key. Held-message queues preserve contact priority.
GPS power saving and RTC backup changes improve supported tracker wake-up behavior. Configurable nRF52 battery profiles include LiFePO4 cutoff settings; software does not change a board's charger voltage.
Upstream dev changes include the MAC block-alignment safety fix, ESP32 reset-time handling, Heltec T1 RTC detection and additional board support.
The ordinary public matrix keeps one ESP32 Full image per board and role. Exact older partition identities are included inside migration packages when required.

Installation and partition expansion

Match the exact board, radio, display and storage hardware.
An ESP32 merged .bin installs the bootloader, partition table and application over USB. An app-only .bin requires an already compatible partition layout and cannot expand partitions.
For an existing ESP32 that needs the expanded Full layout, use its exact board and role migration ZIP from the utility release. All 94 individual packages and the complete bundle are included. Read the package README before choosing its Wi-Fi or LoRa route. The bridge writes the partition table; loss of power during that write can require cable recovery. Back up identity and settings first. Use the Full application supplied inside that migration package after its bridge.
Run get storage.layout on the installed firmware when supported. It reports live partitions; firmware version alone cannot confirm the layout. For older firmware, see the partition lookup guide.
nRF52 UF2 and native DFU ZIP files contain application firmware, not a bootloader update. The picker links exact available OTAFIX bootloader files. OTAFIX 2.4.10 supports the documented matched routes. Standard RAK 3401_DFU / 4631_DFU bootloaders can receive a matching signed bootloader .mota with a compatible OTA application; older *_AUTO_DFU identities require the documented local recovery bridge first.
Four 256 KiB STM32WL USB Companion images (RAK 3x72, Tiny Relay, Wio-E5 Mini and Wio-E5) retain USB Companion transport and 32 KiB LittleFS. They omit packet diagnostics to stay within flash.

Verification and known limits

The original matrix passed 526 targets and failed ten. The 526 passing packages were preserved byte-for-byte; only the ten failures were rebuilt using corrected build configurations. Five ESP32 Full Companions use 100 contacts. Generic ESP-NOW and Heltec V3 retain 256-frame queues; CT62, Tracker V2 and XIAO C3 use 224-frame queues. Their Full transports remain enabled. Two Indicator LoRa Full images retain 350 contacts and 512 queued messages, with a 320x320 internal render canvas scaled to the 480x480 panel. Three STM32 USB Companions use branch-based switch code generation to fit the existing app boundary. The downloadable REPAIR-PROVENANCE.json records each repair and its tooling commit.

All published firmware passed capability, flash size and runtime memory qualification. nRF52 UF2 files passed address/format checks. All 94 ESP32 migration archives passed package integrity checks. Each release page includes target manifests and SHA-256 checksums. The unit-test workflow for this source passed.

The Test Results archive includes measured reports and 1.17.1.8 Preview 1 qualification evidence. Reports for older firmware remain historical and do not qualify this release.

Qualification does not establish physical compatibility on every supported board. Review the exact image's capability and memory manifests, especially sensor and contact-capacity reductions. Reduced nRF52 LoRa OTA profiles retain only their documented sensor set.

The reported T1000-E/iPhone Bluetooth state where iOS shows a connection but the app keeps waiting has not been conclusively reproduced or resolved. This release includes the verified Bluetooth fixes above; it does not claim that report is fully fixed.