Both active provider catalogs now use 1.17.1.5 USA Cascade, published from firmware commit 26303793. They cover 94 device cards, 540 selectable entries, 539 unique firmware profiles, and 1,078 unique firmware files. One Full Companion image is listed under two compatible device/accessory cards. The MQTT simulation environment is a laboratory target and is not a device choice. Entries without a qualified replacement in this OTA-required release are omitted; no download silently points to an older firmware release.

Stable provider URLs

The v1.16.0 text in these filenames is part of the existing provider URL, not the firmware version. Keep these URLs in Mesh America; they now load 1.17.1.5 choices.

Provider name: Keymind Cascade
Catalog URL:   https://raw.githubusercontent.com/mikecarper/MeshCore/keymindCascade/mesh-america/keymind-cascade-v1.16.0-provider.json

Provider name: Keymind Cascade Logging
Catalog URL:   https://raw.githubusercontent.com/mikecarper/MeshCore/keymindCascade/mesh-america/keymind-cascade-logging-v1.16.0-provider.json

Logging and former variants

Both catalogs now select from the same canonical firmware set. Logging, power-saving, and controllable gain variants are runtime settings; selecting the logging provider does not itself change the device's saved settings. Each entry includes the appropriate commands, update methods, hardware requirements, and its actual GitHub release page.

Full Companion: ESP32 uses set usb.logging on / set usb.logging off; nRF52 uses set usb.logging on reboot / set usb.logging off reboot for its optional second USB port. MQTT-capable Full Companions use WebConfig broker cards, not infrastructure MQTT commands.
Infrastructure: set usb.logging on / set usb.logging off controls live USB logs. MQTT-capable unified Full images use set logging.output off, usb, wifi, or both; set bridge.enabled on / off toggles the bridge.
Open the USB web console at 115200 baud. Full Companion and infrastructure start in ASCII mode. Download-only board entries retain their external programming requirements.

See feature switches by role, the release guide, and the old-variant map. For nRF52 OTAFIX installations use the exact board/storage profile from OTAFIX 2.4.6.

Catalog maintenance

The 1.17.1.5 catalog download URLs were reconciled with release-plan.json and each group's qualified TARGET-MANIFEST.json, then verified against the published GitHub assets. Preserve the exact tag for each file: Companion, Repeater/Room Server, Sensor, LoRa OTA, and expanded Full profiles are on separate release pages. Do not update these catalogs by replacing version strings alone.

The older update-provider-release.py, update-logging-provider-release.py, and PowerShell generator target earlier flat release directories and tag layouts. Their default routing is not sufficient for the five-page 1.17.1.5 staging layout. Before using them for another release, reconcile canonical aliases, omitted targets, runtime feature descriptions, and release-group routing against that release's manifests.

Files ending in provider-backup.json are historical backups and intentionally retain their original versions. They are not the active provider URLs above.