diff --git a/build.sh b/build.sh index c9612f01..49e36797 100755 --- a/build.sh +++ b/build.sh @@ -2878,6 +2878,11 @@ declare_build_capability_contract() { if [ "$env_platform" = "NRF52_PLATFORM" ] && ! is_kiss_modem_target "$env_name"; then # Prove the real DFU service is linked, not merely a generic OTA CLI stub. record_build_expectation "ota.update.bluetooth" "_ZN6BLEDfu5beginEv" + if is_lora_ota_build "$env_name" && ! is_companion_build "$env_name"; then + # nRF52 applies mOTA in its bootloader, so the ESP32 decoder marker is + # absent. The checker also verifies the packaged app's EndF/storage layout. + record_build_expectation "ota.update.lora" "invalid in-place patch geometry" + fi fi if [ "$env_platform" = "ESP32_PLATFORM" ]; then diff --git a/docs/_data/firmware_controls.json b/docs/_data/firmware_controls.json index ade65c05..fcbc3b3e 100644 --- a/docs/_data/firmware_controls.json +++ b/docs/_data/firmware_controls.json @@ -160,8 +160,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "GAT562_30S_Mesh_Kit_room_server": { @@ -214,8 +232,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "GAT562_Mesh_EVB_Pro_room_server": { @@ -286,8 +322,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "GAT562_Mesh_Tracker_Pro_room_server": { @@ -1618,8 +1672,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Internal storage accepts in-place application deltas, not full application packages." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash" + } + }, "webconfig": false }, "Heltec_mesh_solar_room_server": { @@ -1690,8 +1762,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "Heltec_t096_room_server": { @@ -1780,8 +1870,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "Heltec_t114_room_server": { @@ -1852,8 +1960,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "Heltec_t114_without_display_room_server": { @@ -1924,8 +2050,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "Heltec_t1_room_server": { @@ -1996,8 +2140,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "Heltec_tower_v2_room_server": { @@ -2032,8 +2194,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_sd" + } + }, "webconfig": false }, "Heltec_v2_companion_radio_full": { @@ -2402,8 +2583,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "KeepteenLT1_room_server": { @@ -2492,8 +2691,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Internal storage accepts in-place application deltas, not full application packages." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash" + } + }, "webconfig": false }, "LilyGo_T-Echo-Lite_room_server": { @@ -2564,8 +2781,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Internal storage accepts in-place application deltas, not full application packages." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash" + } + }, "webconfig": false }, "LilyGo_T-Echo_Card_room_server": { @@ -2618,8 +2853,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "LilyGo_T-Echo_repeater_lora_ota_no_external_sensors": { @@ -2636,8 +2890,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "LilyGo_T-Echo_room_server": { @@ -3441,8 +3714,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Internal storage accepts in-place application deltas, not full application packages." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash" + } + }, "webconfig": false }, "LilyGo_Tlora_C6_companion_radio_full_": { @@ -3639,8 +3930,26 @@ "rxps": false, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Internal storage accepts in-place application deltas, not full application packages." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash" + } + }, "webconfig": false }, "MeshTracker_X1_room_server": { @@ -3711,8 +4020,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "Mesh_pocket_room_server": { @@ -4110,8 +4437,26 @@ "rxps": false, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "Minewsemi_me25ls01_room_server": { @@ -4182,8 +4527,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Internal storage accepts in-place application deltas, not full application packages." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash" + } + }, "webconfig": false }, "Nano_G2_Ultra_room_server": { @@ -4270,8 +4633,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "ProMicro_room_server": { @@ -4360,8 +4741,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "R1Neo_room_server": { @@ -4633,8 +5032,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "RAK_3401_repeater_rak13302_w25q16_lora_ota": { @@ -4651,8 +5068,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "RAK_3401_room_server": { @@ -4757,8 +5193,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "RAK_4631_repeater_bridge_rs232_serial2_lora_ota_no_external_sensors": { @@ -4775,8 +5229,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "RAK_4631_repeater_ethernet": { @@ -4811,8 +5283,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "RAK_4631_repeater_rak15001_slot_c_lora_ota": { @@ -4829,8 +5319,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "RAK_4631_repeater_w25q16_lora_ota": { @@ -4847,8 +5356,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "RAK_4631_room_server": { @@ -4955,8 +5483,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "RAK_WisMesh_Tag_room_server": { @@ -5081,8 +5627,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "SenseCap_Solar_repeater_lora_ota_no_external_sensors": { @@ -5099,8 +5664,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "SenseCap_Solar_room_server": { @@ -5892,8 +6476,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ThinkNode_M1_repeater_lora_ota_no_external_sensors": { @@ -5910,8 +6513,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ThinkNode_M1_room_server": { @@ -6110,8 +6732,26 @@ "rxps": false, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "ThinkNode_M3_room_server": { @@ -6292,8 +6932,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ThinkNode_M6_repeater_lora_ota_no_external_sensors": { @@ -6310,8 +6969,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ThinkNode_M6_room_server": { @@ -6493,8 +7171,26 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Internal storage accepts in-place application deltas, not full application packages." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash" + } + }, "webconfig": false }, "ThinkNode_M8_room_server": { @@ -6748,8 +7444,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "WioTrackerL1_repeater_lora_ota_no_external_sensors": { @@ -6766,8 +7481,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "WioTrackerL1_room_server": { @@ -7317,8 +8051,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "Xiao_nrf52_repeater_lora_ota_no_external_sensors": { @@ -7335,8 +8088,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "Xiao_nrf52_room_server": { @@ -8669,8 +9441,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ikoka_handheld_nrf_e22_30dbm_repeater_lora_ota_no_external_sensors": { @@ -8687,8 +9478,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ikoka_handheld_nrf_e22_30dbm_room_server": { @@ -8741,8 +9551,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ikoka_nano_nrf_22dbm_repeater_lora_ota_no_external_sensors": { @@ -8759,8 +9588,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ikoka_nano_nrf_22dbm_room_server": { @@ -8813,8 +9661,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ikoka_nano_nrf_30dbm_repeater_lora_ota_no_external_sensors": { @@ -8831,8 +9698,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ikoka_nano_nrf_30dbm_room_server": { @@ -8885,8 +9771,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ikoka_nano_nrf_33dbm_repeater_lora_ota_no_external_sensors": { @@ -8903,8 +9808,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ikoka_nano_nrf_33dbm_room_server": { @@ -8957,8 +9881,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ikoka_stick_nrf_22dbm_repeater_lora_ota_no_external_sensors": { @@ -8975,8 +9918,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ikoka_stick_nrf_22dbm_room_server": { @@ -9029,8 +9991,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ikoka_stick_nrf_30dbm_repeater_lora_ota_no_external_sensors": { @@ -9047,8 +10028,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ikoka_stick_nrf_30dbm_room_server": { @@ -9101,8 +10101,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ikoka_stick_nrf_33dbm_repeater_lora_ota_no_external_sensors": { @@ -9119,8 +10138,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "ikoka_stick_nrf_33dbm_room_server": { @@ -9596,8 +10634,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "solarxiao_30S_room_server": { @@ -9650,8 +10707,27 @@ "rxps": true, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader." + ], + "package_types": [ + "full", + "in_place_delta" + ], + "storage": "external_qspi" + } + }, "webconfig": false }, "solarxiao_33S_room_server": { @@ -9722,8 +10798,26 @@ "rxps": false, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash_and_retained_ram" + } + }, "webconfig": false }, "t1000e_room_server": { @@ -9842,8 +10936,26 @@ "rxps": false, "snmp": false, "updateMethods": [ - "bluetooth" + "bluetooth", + "lora" ], + "updateRequirements": { + "lora": { + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": [ + "Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device.", + "Internal storage accepts in-place application deltas, not full application packages." + ], + "package_types": [ + "in_place_delta" + ], + "storage": "internal_flash" + } + }, "webconfig": false }, "wio_wm1110_room_server": { diff --git a/docs/releases/1.17.1.5.md b/docs/releases/1.17.1.5.md index f69c657f..4a28f0ff 100644 --- a/docs/releases/1.17.1.5.md +++ b/docs/releases/1.17.1.5.md @@ -103,6 +103,18 @@ push commits, create remote tags, or publish a GitHub release. ## Published release set and small-slot Heltec V4 updates +The capability JSON and target inventories now report both Bluetooth DFU and +LoRa mOTA for all 60 nRF52 receiver profiles. The original report omitted the +nRF52 LoRa method. Each affected manifest includes `ota_update_requirements.lora` +with its storage type, accepted package types, exact-base requirement for deltas, +and the matching OTAFIX bootloader link. Internal-flash receivers accept in-place +deltas; supported QSPI/SD receivers also accept full application packages. The +20 retained-RAM receivers require OTAFIX 2.4.6's matching handoff support. +These reports verify the released application bytes and storage layout; they +do not certify the bootloader installed on a physical device. Firmware binaries +and tags are unchanged. Full Companion mOTA sending remains separate from +self-update capability. + Published firmware tags remain at source commit `26303793`. Documentation can advance independently. The original matrix qualified 540 profiles (1,080 firmware files) from 551 attempts; 11 oversized portable attempts have expanded diff --git a/mesh-america/keymind-cascade-logging-v1.16.0-provider.json b/mesh-america/keymind-cascade-logging-v1.16.0-provider.json index c423d305..929552a8 100644 --- a/mesh-america/keymind-cascade-logging-v1.16.0-provider.json +++ b/mesh-america/keymind-cascade-logging-v1.16.0-provider.json @@ -285,7 +285,7 @@ "subTitle": "ThinkNode_M1_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M1_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M1_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -309,7 +309,7 @@ "subTitle": "ThinkNode_M1_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -587,7 +587,7 @@ "subTitle": "ThinkNode_M3_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M3_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M3_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -841,7 +841,7 @@ "subTitle": "ThinkNode_M6_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M6_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M6_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -865,7 +865,7 @@ "subTitle": "ThinkNode_M6_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M6_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M6_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -1270,7 +1270,7 @@ "subTitle": "GAT562_30S_Mesh_Kit_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - GAT562_30S_Mesh_Kit_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - GAT562_30S_Mesh_Kit_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -1349,7 +1349,7 @@ "subTitle": "GAT562_Mesh_EVB_Pro_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - GAT562_Mesh_EVB_Pro_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - GAT562_Mesh_EVB_Pro_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -1452,7 +1452,7 @@ "subTitle": "GAT562_Mesh_Tracker_Pro_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - GAT562_Mesh_Tracker_Pro_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - GAT562_Mesh_Tracker_Pro_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -2653,7 +2653,7 @@ "subTitle": "Heltec_t096_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t096_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t096_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -2780,7 +2780,7 @@ "subTitle": "Heltec_t1_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -2883,7 +2883,7 @@ "subTitle": "Mesh_pocket_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Mesh_pocket_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Mesh_pocket_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -2986,7 +2986,7 @@ "subTitle": "Heltec_mesh_solar_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_mesh_solar_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_mesh_solar_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -3089,7 +3089,7 @@ "subTitle": "Heltec_tower_v2_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_tower_v2_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_tower_v2_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -3137,7 +3137,7 @@ "subTitle": "Heltec_tower_v2_sdcard_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_tower_v2_sdcard_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSD REQUIREMENT \u2014 MeshTower V2 LoRa OTA stages updates on the onboard microSD. Keep the card inserted through installation and use FAT16/FAT32/exFAT on an MBR card whose first partition starts after sector 1; the matching SD-aware OTAFIX bootloader is mandatory.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_tower_v2_sdcard_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSD REQUIREMENT \u2014 MeshTower V2 LoRa OTA stages updates on the onboard microSD. Keep the card inserted through installation and use FAT16/FAT32/exFAT on an MBR card whose first partition starts after sector 1; the matching SD-aware OTAFIX bootloader is mandatory.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -3607,7 +3607,7 @@ "subTitle": "Heltec_t114_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t114_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t114_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -3703,7 +3703,7 @@ "subTitle": "Heltec_t114_without_display_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t114_without_display_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nHARDWARE \u2014 Match the display/accessory variant to the hardware actually installed.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t114_without_display_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nHARDWARE \u2014 Match the display/accessory variant to the hardware actually installed.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -6060,7 +6060,7 @@ "subTitle": "ikoka_handheld_nrf_e22_30dbm_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_handheld_nrf_e22_30dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_handheld_nrf_e22_30dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -6084,7 +6084,7 @@ "subTitle": "ikoka_handheld_nrf_e22_30dbm_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_handheld_nrf_e22_30dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_handheld_nrf_e22_30dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -6163,7 +6163,7 @@ "subTitle": "ikoka_nano_nrf_22dbm_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_22dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_22dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -6187,7 +6187,7 @@ "subTitle": "ikoka_nano_nrf_22dbm_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_22dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_22dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -6259,7 +6259,7 @@ "subTitle": "ikoka_nano_nrf_30dbm_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_30dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_30dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -6283,7 +6283,7 @@ "subTitle": "ikoka_nano_nrf_30dbm_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_30dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_30dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -6355,7 +6355,7 @@ "subTitle": "ikoka_nano_nrf_33dbm_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_33dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_33dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -6379,7 +6379,7 @@ "subTitle": "ikoka_nano_nrf_33dbm_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_33dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_33dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -6458,7 +6458,7 @@ "subTitle": "ikoka_stick_nrf_22dbm_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_22dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_22dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -6482,7 +6482,7 @@ "subTitle": "ikoka_stick_nrf_22dbm_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_22dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_22dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -6554,7 +6554,7 @@ "subTitle": "ikoka_stick_nrf_30dbm_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_30dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_30dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -6578,7 +6578,7 @@ "subTitle": "ikoka_stick_nrf_30dbm_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_30dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_30dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -6650,7 +6650,7 @@ "subTitle": "ikoka_stick_nrf_33dbm_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_33dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_33dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -6674,7 +6674,7 @@ "subTitle": "ikoka_stick_nrf_33dbm_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_33dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_33dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -6777,7 +6777,7 @@ "subTitle": "KeepteenLT1_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - KeepteenLT1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - KeepteenLT1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -7834,7 +7834,7 @@ "subTitle": "LilyGo_T-Echo_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -7858,7 +7858,7 @@ "subTitle": "LilyGo_T-Echo_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -7961,7 +7961,7 @@ "subTitle": "LilyGo_T-Echo_Card_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo_Card_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo_Card_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -8088,7 +8088,7 @@ "subTitle": "LilyGo_T-Echo-Lite_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo-Lite_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo-Lite_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -8342,7 +8342,7 @@ "subTitle": "LilyGo_T_Impulse_Plus_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T_Impulse_Plus_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T_Impulse_Plus_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -9430,7 +9430,7 @@ "subTitle": "Minewsemi_me25ls01_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Minewsemi_me25ls01_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Minewsemi_me25ls01_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -9533,7 +9533,7 @@ "subTitle": "R1Neo_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - R1Neo_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - R1Neo_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -10010,7 +10010,7 @@ "subTitle": "ProMicro_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ProMicro_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ProMicro_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -10199,7 +10199,7 @@ "subTitle": "RAK_4631_repeater_bridge_rs232_serial1_lora_ota_no_external_sensors \u2014 RS232 bridge, Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_bridge_rs232_serial1_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nGPS / RS232 - This explicit Serial1 bridge omits the combined GPS provider. Canonical GPS-enabled RAK4631 repeater images use UART2 for the optional bridge.\n\nCAPACITY - selected optional environmental/ranging drivers and GPS omitted; INA219/INA226/INA260/INA3221 and board display/RTC retained; GPS conflicts with RS-232 on Serial1.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_bridge_rs232_serial1_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nGPS / RS232 - This explicit Serial1 bridge omits the combined GPS provider. Canonical GPS-enabled RAK4631 repeater images use UART2 for the optional bridge.\n\nCAPACITY - selected optional environmental/ranging drivers and GPS omitted; INA219/INA226/INA260/INA3221 and board display/RTC retained; GPS conflicts with RS-232 on Serial1.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -10223,7 +10223,7 @@ "subTitle": "RAK_4631_repeater_bridge_rs232_serial2_lora_ota_no_external_sensors \u2014 RS232 bridge, Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_bridge_rs232_serial2_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; INA219/INA226/INA260/INA3221 and board display/RTC/GPS retained; RAK12500 and INA3221 require distinct configured I2C addresses.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_bridge_rs232_serial2_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; INA219/INA226/INA260/INA3221 and board display/RTC/GPS retained; RAK12500 and INA3221 require distinct configured I2C addresses.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -10271,7 +10271,7 @@ "subTitle": "RAK_4631_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; INA219/INA226/INA260/INA3221 and board display/RTC/GPS retained; RAK12500 and INA3221 require distinct configured I2C addresses.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; INA219/INA226/INA260/INA3221 and board display/RTC/GPS retained; RAK12500 and INA3221 require distinct configured I2C addresses.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -10295,7 +10295,7 @@ "subTitle": "RAK_4631_repeater_rak15001_slot_c_lora_ota", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_rak15001_slot_c_lora_ota. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSTORAGE - Requires RAK15001 in WisBlock sensor slot C and its matching OTAFIX profile. Do not combine it with conflicting Ethernet/SD/SPI modules. https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/ota_nrf52_qspi.md\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_rak15001_slot_c_lora_ota. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSTORAGE - Requires RAK15001 in WisBlock sensor slot C and its matching OTAFIX profile. Do not combine it with conflicting Ethernet/SD/SPI modules. https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/ota_nrf52_qspi.md\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -10319,7 +10319,7 @@ "subTitle": "RAK_4631_repeater_w25q16_lora_ota", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_w25q16_lora_ota. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSTORAGE - Requires the externally wired W25Q16 and exact board/radio pin map plus the matching OTAFIX bootloader. https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/ota_nrf52_qspi.md\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_w25q16_lora_ota. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSTORAGE - Requires the externally wired W25Q16 and exact board/radio pin map plus the matching OTAFIX bootloader. https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/ota_nrf52_qspi.md\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -10693,7 +10693,7 @@ "subTitle": "RAK_3401_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_3401_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; INA219/INA226/INA260/INA3221 and board display/RTC/GPS retained; RAK12500 and INA3221 require distinct configured I2C addresses.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_3401_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; INA219/INA226/INA260/INA3221 and board display/RTC/GPS retained; RAK12500 and INA3221 require distinct configured I2C addresses.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -10717,7 +10717,7 @@ "subTitle": "RAK_3401_repeater_rak13302_w25q16_lora_ota", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_3401_repeater_rak13302_w25q16_lora_ota. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSTORAGE - Requires the externally wired W25Q16 and exact board/radio pin map plus the matching OTAFIX bootloader. https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/ota_nrf52_qspi.md\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_3401_repeater_rak13302_w25q16_lora_ota. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSTORAGE - Requires the externally wired W25Q16 and exact board/radio pin map plus the matching OTAFIX bootloader. https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/ota_nrf52_qspi.md\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -10844,7 +10844,7 @@ "subTitle": "RAK_WisMesh_Tag_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_WisMesh_Tag_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_WisMesh_Tag_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -11040,7 +11040,7 @@ "subTitle": "SenseCap_Solar_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - SenseCap_Solar_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - SenseCap_Solar_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -11064,7 +11064,7 @@ "subTitle": "SenseCap_Solar_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - SenseCap_Solar_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - SenseCap_Solar_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -11167,7 +11167,7 @@ "subTitle": "t1000e_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - t1000e_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - t1000e_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -11246,7 +11246,7 @@ "subTitle": "WioTrackerL1_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - WioTrackerL1_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - WioTrackerL1_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -11270,7 +11270,7 @@ "subTitle": "WioTrackerL1_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - WioTrackerL1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - WioTrackerL1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -11373,7 +11373,7 @@ "subTitle": "wio_wm1110_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - wio_wm1110_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - wio_wm1110_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "download", @@ -11737,7 +11737,7 @@ "subTitle": "Xiao_nrf52_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Xiao_nrf52_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Xiao_nrf52_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -11761,7 +11761,7 @@ "subTitle": "Xiao_nrf52_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Xiao_nrf52_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Xiao_nrf52_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -12317,7 +12317,7 @@ "subTitle": "solarxiao_30S_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - solarxiao_30S_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nHARDWARE \u2014 Match the listed radio module, output stage, and pin map to the exact board; a similarly named radio variant is not a safe substitute.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - solarxiao_30S_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nHARDWARE \u2014 Match the listed radio module, output stage, and pin map to the exact board; a similarly named radio variant is not a safe substitute.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -12389,7 +12389,7 @@ "subTitle": "solarxiao_33S_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - solarxiao_33S_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nHARDWARE \u2014 Match the listed radio module, output stage, and pin map to the exact board; a similarly named radio variant is not a safe substitute.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - solarxiao_33S_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nHARDWARE \u2014 Match the listed radio module, output stage, and pin map to the exact board; a similarly named radio variant is not a safe substitute.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -12722,7 +12722,7 @@ "subTitle": "Nano_G2_Ultra_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Nano_G2_Ultra_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Nano_G2_Ultra_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -13230,7 +13230,7 @@ "subTitle": "MeshTracker_X1_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - MeshTracker_X1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - MeshTracker_X1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", @@ -13642,7 +13642,7 @@ "subTitle": "ThinkNode_M8_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M8_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M8_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793\n\nLOGGING CATALOG - These are the same canonical release binaries as the standard catalog. Enable the desired USB/MQTT logging paths at runtime; selecting this catalog does not change saved settings.", "files": [ { "type": "flash", diff --git a/mesh-america/keymind-cascade-v1.16.0-provider.json b/mesh-america/keymind-cascade-v1.16.0-provider.json index 865fc339..2c04a9da 100644 --- a/mesh-america/keymind-cascade-v1.16.0-provider.json +++ b/mesh-america/keymind-cascade-v1.16.0-provider.json @@ -285,7 +285,7 @@ "subTitle": "ThinkNode_M1_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M1_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M1_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -309,7 +309,7 @@ "subTitle": "ThinkNode_M1_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -587,7 +587,7 @@ "subTitle": "ThinkNode_M3_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M3_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M3_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -841,7 +841,7 @@ "subTitle": "ThinkNode_M6_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M6_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M6_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -865,7 +865,7 @@ "subTitle": "ThinkNode_M6_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M6_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M6_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -1270,7 +1270,7 @@ "subTitle": "GAT562_30S_Mesh_Kit_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - GAT562_30S_Mesh_Kit_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - GAT562_30S_Mesh_Kit_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -1349,7 +1349,7 @@ "subTitle": "GAT562_Mesh_EVB_Pro_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - GAT562_Mesh_EVB_Pro_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - GAT562_Mesh_EVB_Pro_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -1452,7 +1452,7 @@ "subTitle": "GAT562_Mesh_Tracker_Pro_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - GAT562_Mesh_Tracker_Pro_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - GAT562_Mesh_Tracker_Pro_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -2653,7 +2653,7 @@ "subTitle": "Heltec_t096_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t096_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t096_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -2780,7 +2780,7 @@ "subTitle": "Heltec_t1_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -2883,7 +2883,7 @@ "subTitle": "Mesh_pocket_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Mesh_pocket_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Mesh_pocket_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -2986,7 +2986,7 @@ "subTitle": "Heltec_mesh_solar_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_mesh_solar_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_mesh_solar_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -3089,7 +3089,7 @@ "subTitle": "Heltec_tower_v2_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_tower_v2_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_tower_v2_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -3137,7 +3137,7 @@ "subTitle": "Heltec_tower_v2_sdcard_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_tower_v2_sdcard_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSD REQUIREMENT \u2014 MeshTower V2 LoRa OTA stages updates on the onboard microSD. Keep the card inserted through installation and use FAT16/FAT32/exFAT on an MBR card whose first partition starts after sector 1; the matching SD-aware OTAFIX bootloader is mandatory.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_tower_v2_sdcard_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSD REQUIREMENT \u2014 MeshTower V2 LoRa OTA stages updates on the onboard microSD. Keep the card inserted through installation and use FAT16/FAT32/exFAT on an MBR card whose first partition starts after sector 1; the matching SD-aware OTAFIX bootloader is mandatory.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -3607,7 +3607,7 @@ "subTitle": "Heltec_t114_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t114_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t114_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -3703,7 +3703,7 @@ "subTitle": "Heltec_t114_without_display_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t114_without_display_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nHARDWARE \u2014 Match the display/accessory variant to the hardware actually installed.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Heltec_t114_without_display_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nHARDWARE \u2014 Match the display/accessory variant to the hardware actually installed.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -6060,7 +6060,7 @@ "subTitle": "ikoka_handheld_nrf_e22_30dbm_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_handheld_nrf_e22_30dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_handheld_nrf_e22_30dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -6084,7 +6084,7 @@ "subTitle": "ikoka_handheld_nrf_e22_30dbm_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_handheld_nrf_e22_30dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_handheld_nrf_e22_30dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -6163,7 +6163,7 @@ "subTitle": "ikoka_nano_nrf_22dbm_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_22dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_22dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -6187,7 +6187,7 @@ "subTitle": "ikoka_nano_nrf_22dbm_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_22dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_22dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -6259,7 +6259,7 @@ "subTitle": "ikoka_nano_nrf_30dbm_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_30dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_30dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -6283,7 +6283,7 @@ "subTitle": "ikoka_nano_nrf_30dbm_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_30dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_30dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -6355,7 +6355,7 @@ "subTitle": "ikoka_nano_nrf_33dbm_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_33dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_33dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -6379,7 +6379,7 @@ "subTitle": "ikoka_nano_nrf_33dbm_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_33dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_nano_nrf_33dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -6458,7 +6458,7 @@ "subTitle": "ikoka_stick_nrf_22dbm_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_22dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_22dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -6482,7 +6482,7 @@ "subTitle": "ikoka_stick_nrf_22dbm_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_22dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_22dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -6554,7 +6554,7 @@ "subTitle": "ikoka_stick_nrf_30dbm_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_30dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_30dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -6578,7 +6578,7 @@ "subTitle": "ikoka_stick_nrf_30dbm_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_30dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_30dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -6650,7 +6650,7 @@ "subTitle": "ikoka_stick_nrf_33dbm_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_33dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_33dbm_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -6674,7 +6674,7 @@ "subTitle": "ikoka_stick_nrf_33dbm_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_33dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ikoka_stick_nrf_33dbm_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -6777,7 +6777,7 @@ "subTitle": "KeepteenLT1_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - KeepteenLT1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - KeepteenLT1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -7834,7 +7834,7 @@ "subTitle": "LilyGo_T-Echo_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -7858,7 +7858,7 @@ "subTitle": "LilyGo_T-Echo_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -7961,7 +7961,7 @@ "subTitle": "LilyGo_T-Echo_Card_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo_Card_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo_Card_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -8088,7 +8088,7 @@ "subTitle": "LilyGo_T-Echo-Lite_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo-Lite_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T-Echo-Lite_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -8342,7 +8342,7 @@ "subTitle": "LilyGo_T_Impulse_Plus_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T_Impulse_Plus_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - LilyGo_T_Impulse_Plus_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -9430,7 +9430,7 @@ "subTitle": "Minewsemi_me25ls01_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Minewsemi_me25ls01_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Minewsemi_me25ls01_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -9533,7 +9533,7 @@ "subTitle": "R1Neo_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - R1Neo_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - R1Neo_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -10010,7 +10010,7 @@ "subTitle": "ProMicro_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ProMicro_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ProMicro_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -10199,7 +10199,7 @@ "subTitle": "RAK_4631_repeater_bridge_rs232_serial1_lora_ota_no_external_sensors \u2014 RS232 bridge, Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_bridge_rs232_serial1_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nGPS / RS232 - This explicit Serial1 bridge omits the combined GPS provider. Canonical GPS-enabled RAK4631 repeater images use UART2 for the optional bridge.\n\nCAPACITY - selected optional environmental/ranging drivers and GPS omitted; INA219/INA226/INA260/INA3221 and board display/RTC retained; GPS conflicts with RS-232 on Serial1.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_bridge_rs232_serial1_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nGPS / RS232 - This explicit Serial1 bridge omits the combined GPS provider. Canonical GPS-enabled RAK4631 repeater images use UART2 for the optional bridge.\n\nCAPACITY - selected optional environmental/ranging drivers and GPS omitted; INA219/INA226/INA260/INA3221 and board display/RTC retained; GPS conflicts with RS-232 on Serial1.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -10223,7 +10223,7 @@ "subTitle": "RAK_4631_repeater_bridge_rs232_serial2_lora_ota_no_external_sensors \u2014 RS232 bridge, Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_bridge_rs232_serial2_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; INA219/INA226/INA260/INA3221 and board display/RTC/GPS retained; RAK12500 and INA3221 require distinct configured I2C addresses.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_bridge_rs232_serial2_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; INA219/INA226/INA260/INA3221 and board display/RTC/GPS retained; RAK12500 and INA3221 require distinct configured I2C addresses.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -10271,7 +10271,7 @@ "subTitle": "RAK_4631_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; INA219/INA226/INA260/INA3221 and board display/RTC/GPS retained; RAK12500 and INA3221 require distinct configured I2C addresses.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; INA219/INA226/INA260/INA3221 and board display/RTC/GPS retained; RAK12500 and INA3221 require distinct configured I2C addresses.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -10295,7 +10295,7 @@ "subTitle": "RAK_4631_repeater_rak15001_slot_c_lora_ota", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_rak15001_slot_c_lora_ota. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSTORAGE - Requires RAK15001 in WisBlock sensor slot C and its matching OTAFIX profile. Do not combine it with conflicting Ethernet/SD/SPI modules. https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/ota_nrf52_qspi.md\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_rak15001_slot_c_lora_ota. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSTORAGE - Requires RAK15001 in WisBlock sensor slot C and its matching OTAFIX profile. Do not combine it with conflicting Ethernet/SD/SPI modules. https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/ota_nrf52_qspi.md\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -10319,7 +10319,7 @@ "subTitle": "RAK_4631_repeater_w25q16_lora_ota", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_w25q16_lora_ota. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSTORAGE - Requires the externally wired W25Q16 and exact board/radio pin map plus the matching OTAFIX bootloader. https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/ota_nrf52_qspi.md\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_4631_repeater_w25q16_lora_ota. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSTORAGE - Requires the externally wired W25Q16 and exact board/radio pin map plus the matching OTAFIX bootloader. https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/ota_nrf52_qspi.md\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -10693,7 +10693,7 @@ "subTitle": "RAK_3401_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_3401_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; INA219/INA226/INA260/INA3221 and board display/RTC/GPS retained; RAK12500 and INA3221 require distinct configured I2C addresses.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_3401_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; INA219/INA226/INA260/INA3221 and board display/RTC/GPS retained; RAK12500 and INA3221 require distinct configured I2C addresses.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -10717,7 +10717,7 @@ "subTitle": "RAK_3401_repeater_rak13302_w25q16_lora_ota", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_3401_repeater_rak13302_w25q16_lora_ota. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSTORAGE - Requires the externally wired W25Q16 and exact board/radio pin map plus the matching OTAFIX bootloader. https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/ota_nrf52_qspi.md\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_3401_repeater_rak13302_w25q16_lora_ota. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nSTORAGE - Requires the externally wired W25Q16 and exact board/radio pin map plus the matching OTAFIX bootloader. https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/ota_nrf52_qspi.md\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -10844,7 +10844,7 @@ "subTitle": "RAK_WisMesh_Tag_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_WisMesh_Tag_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - RAK_WisMesh_Tag_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -11040,7 +11040,7 @@ "subTitle": "SenseCap_Solar_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - SenseCap_Solar_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - SenseCap_Solar_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -11064,7 +11064,7 @@ "subTitle": "SenseCap_Solar_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - SenseCap_Solar_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - SenseCap_Solar_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -11167,7 +11167,7 @@ "subTitle": "t1000e_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - t1000e_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - t1000e_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware. OTAFIX 2.4.6 retained-RAM handoff support is required.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -11246,7 +11246,7 @@ "subTitle": "WioTrackerL1_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - WioTrackerL1_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - WioTrackerL1_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -11270,7 +11270,7 @@ "subTitle": "WioTrackerL1_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - WioTrackerL1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - WioTrackerL1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -11373,7 +11373,7 @@ "subTitle": "wio_wm1110_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - wio_wm1110_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - wio_wm1110_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "download", @@ -11737,7 +11737,7 @@ "subTitle": "Xiao_nrf52_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Xiao_nrf52_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Xiao_nrf52_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -11761,7 +11761,7 @@ "subTitle": "Xiao_nrf52_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Xiao_nrf52_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Xiao_nrf52_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -12317,7 +12317,7 @@ "subTitle": "solarxiao_30S_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - solarxiao_30S_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nHARDWARE \u2014 Match the listed radio module, output stage, and pin map to the exact board; a similarly named radio variant is not a safe substitute.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - solarxiao_30S_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nHARDWARE \u2014 Match the listed radio module, output stage, and pin map to the exact board; a similarly named radio variant is not a safe substitute.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -12389,7 +12389,7 @@ "subTitle": "solarxiao_33S_repeater", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - solarxiao_33S_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nHARDWARE \u2014 Match the listed radio module, output stage, and pin map to the exact board; a similarly named radio variant is not a safe substitute.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - solarxiao_33S_repeater. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This external-storage profile accepts full application packages or in-place deltas; deltas require the exact running firmware as their base.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nHARDWARE \u2014 Match the listed radio module, output stage, and pin map to the exact board; a similarly named radio variant is not a safe substitute.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/repeater-room-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -12722,7 +12722,7 @@ "subTitle": "Nano_G2_Ultra_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Nano_G2_Ultra_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - Nano_G2_Ultra_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -13230,7 +13230,7 @@ "subTitle": "MeshTracker_X1_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - MeshTracker_X1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - MeshTracker_X1_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", @@ -13642,7 +13642,7 @@ "subTitle": "ThinkNode_M8_repeater_lora_ota_no_external_sensors \u2014 Compact LoRa OTA; selected optional sensors omitted", "version": { "standard-v1.17.1.5-halo-keymind-cascade-dev-26303793": { - "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M8_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", + "notes": "Keymind Cascade MeshCore v1.17.1.5 development prerelease. USA/Canada 910.525 MHz / BW62.5 / SF7 / CR5; Cascade defaults. Saved settings take precedence.\n\nROLE - Repeater: Relays mesh traffic to extend coverage.\n\nEXACT TARGET - ThinkNode_M8_repeater_lora_ota_no_external_sensors. Match the radio, display, memory and storage hardware before flashing.\n\nUSB CONSOLE / LOGGING - ASCII terminal at 115200 baud: https://flasher.meshcore.io/console. Use board and ver. set usb.logging on enables live logs; set usb.logging off disables them (no reboot suffix on infrastructure). log start/log stop controls a separate stored RX capture where compiled.\n\nFEATURES - Repeater forwarding uses set repeat on/off separately from logging/MQTT. RXPS uses set radio.rxps on/off. Device power saving uses powersaving on/off or set powersaving on/off with different USB/bridge guards; follow the role guide before enabling sleep. WebConfig uses set webui on/off only when compiled. The USB console does not require WebConfig.\n\nSELF-UPDATE - Qualified wireless methods: bluetooth, lora. Read the capability manifest for this exact artifact. WiFi uses start ota (or start ota ap), then the returned /update URL; stop ota closes the uploader. On nRF52, start ota invokes Bluetooth DFU. LoRa installation requires an exact destination .mota package; it cannot be flashed as a web-install file.\n\nBOOTLOADER - nRF52 OTAFIX installations require the exact board/storage profile from OTAFIX 2.4.6: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. Hybrid internal-flash MOTA receivers require its retained-RAM handoff; QSPI/microSD targets require the matching external-storage bootloader. Full Companion is source-only and keeps its Companion storage layout. LoRa mOTA requires the matching board/storage OTAFIX bootloader: https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6. This internal-storage profile accepts in-place deltas built against the exact running firmware.\n\nINSTALL - Use the exact board UF2/DFU package or platform-specific USB procedure. An application update does not install a missing OTAFIX bootloader.\n\nCAPACITY - selected optional environmental/ranging drivers omitted; generic I2C and exact-target board peripherals remain unchanged.\n\nCOMMANDS / BOARD EXCEPTIONS - https://github.com/mikecarper/MeshCore/blob/eb4ca56f1ba87bf08741b6c479ed601cccdb1d84/docs/role_feature_switches.md\n\nRELEASE - https://github.com/mikecarper/MeshCore/releases/tag/lora-ota-v1.17.1.5-halo-keymind-cascade-dev-26303793", "files": [ { "type": "flash", diff --git a/scripts/check_firmware_capabilities.py b/scripts/check_firmware_capabilities.py index 39c6a4d1..e0724d93 100644 --- a/scripts/check_firmware_capabilities.py +++ b/scripts/check_firmware_capabilities.py @@ -11,6 +11,39 @@ import sys import struct import zipfile +sys.path.insert(0, str(Path(__file__).resolve().parents[1] / "tools" / "mota")) +from motalib import parse_nrf52_layout + + +def nrf52_lora_details(application): + """Inspect application bytes, not just an ELF symbol or an OTA CLI stub.""" + if b"invalid in-place patch geometry" not in application or b"OTA: status" not in application: + raise ValueError("nRF52 LoRa OTA receiver/apply implementation is missing") + layout = parse_nrf52_layout(application) + if layout is None: + raise ValueError("nRF52 LoRa OTA requires a valid EndF and storage-layout record") + if len(application) > layout.linked_app_end - layout.app_base: + raise ValueError("nRF52 LoRa OTA application exceeds its linked flash region") + storage = ("external_qspi" if layout.qspi_backed else "external_sd" if layout.sd_backed + else "internal_flash_and_retained_ram" if layout.hybrid_ram else "internal_flash") + notes = ["Use a destination-specific .mota package matching the board, target, and storage layout.", + "An in-place delta requires the exact firmware currently running as its base.", + "The package must fit the receiver's staging and apply workspace.", + "Artifact inspection verifies compiled support; it does not verify the bootloader installed on a physical device."] + if layout.hybrid_ram: + notes.append("Requires OTAFIX 2.4.6 retained-RAM handoff support; a transfer cannot resume after the receiver restarts.") + elif layout.external_backed: + notes.append("Requires the matching external-storage hardware, wiring, and storage-aware OTAFIX bootloader.") + else: + notes.append("Internal storage accepts in-place application deltas, not full application packages.") + return { + "storage": storage, + "package_types": ["full", "in_place_delta"] if layout.external_backed else ["in_place_delta"], + "bootloader": "Matching board/storage OTAFIX bootloader", + "bootloader_release": "https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6", + "notes": notes, + } + def parse_args() -> argparse.Namespace: parser = argparse.ArgumentParser() @@ -69,17 +102,27 @@ def verify_ota_artifacts(args, methods): if image_size <= 0 or any(image_size > size for _, size in ordered): return False, "ESP32 firmware does not fit both OTA application slots" return True, "firmware fits both OTA application slots; otadata present" - if args.platform == "NRF52_PLATFORM" and "bluetooth" in methods: + if args.platform == "NRF52_PLATFORM" and set(methods) <= {"bluetooth", "lora"}: if args.dfu_package is None: - return False, "Bluetooth DFU requires its application ZIP" + return False, "nRF52 OTA verification requires its application DFU ZIP" with zipfile.ZipFile(args.dfu_package) as package: manifest = json.loads(package.read("manifest.json"))["manifest"] application = manifest["application"] - if not package.read(application["bin_file"]) or not package.read(application["dat_file"]): + image = package.read(application["bin_file"]) + if not image or not package.read(application["dat_file"]): return False, "Bluetooth DFU application ZIP is empty" if package.testzip() is not None: return False, "Bluetooth DFU application ZIP is corrupt" - return True, "application DFU ZIP verified; matching BLE DFU bootloader required" + evidence = [] + if "bluetooth" in methods: + evidence.append("application DFU ZIP verified; matching BLE DFU bootloader required") + if "lora" in methods: + if "companion" in args.target.lower() or "comp_radio" in args.target.lower(): + return False, "Companion MOTA sending does not qualify as LoRa self-update" + details = nrf52_lora_details(image) + evidence.append("LoRa mOTA receiver/apply code and EndF storage layout verified: " + details["storage"] + + "; matching board/storage OTAFIX bootloader and compatible destination package required") + return True, "; ".join(evidence) except (OSError, ValueError, KeyError, zipfile.BadZipFile) as exc: return False, str(exc) return False, "no qualified wireless update artifact for this platform" @@ -140,6 +183,10 @@ def main() -> int: "ota_update_evidence": ota_evidence, "verified": not malformed and not missing and (not args.require_ota or ota_verified), } + if ota_verified and args.platform == "NRF52_PLATFORM" and "lora" in ota_methods: + with zipfile.ZipFile(args.dfu_package) as package: + app = json.loads(package.read("manifest.json"))["manifest"]["application"] + manifest["ota_update_requirements"] = {"lora": nrf52_lora_details(package.read(app["bin_file"]))} args.output.parent.mkdir(parents=True, exist_ok=True) temporary = args.output.with_name(f".{args.output.name}.{os.getpid()}.tmp") diff --git a/scripts/generate_picker_controls.py b/scripts/generate_picker_controls.py index e4fed4e7..83160e0d 100644 --- a/scripts/generate_picker_controls.py +++ b/scripts/generate_picker_controls.py @@ -56,6 +56,8 @@ def generate(stage, config): 'snmp': enabled('WITH_SNMP'), 'updateMethods': manifest.get('ota_update_methods', []), } + if manifest.get('ota_update_requirements'): + controls['updateRequirements'] = manifest['ota_update_requirements'] for name in manifest['files']: if not name.endswith(('.bin', '.uf2', '.zip', '.hex')): continue diff --git a/test/test_build_profiles.sh b/test/test_build_profiles.sh index 29b74c34..afee220f 100644 --- a/test/test_build_profiles.sh +++ b/test/test_build_profiles.sh @@ -1087,6 +1087,8 @@ for rak_target in \ BUILD_EXPECTATIONS=() declare_build_capability_contract "$rak_target" NRF52_PLATFORM expectations=" ${BUILD_EXPECTATIONS[*]} " + [[ "$expectations" == *"ota.update.lora=invalid in-place patch geometry"* ]] \ + || fail "$rak_target OTA contract omitted LoRa self-update" [[ "$expectations" == *"sensor.gps=meshcore.capability.rak_wisblock_gps.v1"* ]] \ || fail "$rak_target reduced OTA contract omitted retained GPS" [[ "$expectations" != *"sensor.gps=gps setloc"* ]] \ diff --git a/test/test_firmware_capabilities.py b/test/test_firmware_capabilities.py index 261ff192..e13bf078 100644 --- a/test/test_firmware_capabilities.py +++ b/test/test_firmware_capabilities.py @@ -13,6 +13,8 @@ import zipfile ROOT = Path(__file__).resolve().parents[1] CHECKER = ROOT / "scripts" / "check_firmware_capabilities.py" +sys.path.insert(0, str(ROOT / "tools" / "mota")) +import motalib as mota class FirmwareCapabilityCheckerTest(unittest.TestCase): @@ -136,6 +138,55 @@ class FirmwareCapabilityCheckerTest(unittest.TestCase): self.assertTrue(manifest["verified"]) self.assertFalse(manifest["ota_update_verified"]) + def nrf_dfu(self, flags=16, *, receiver=True, corrupt=False): + body = b"OTA: status" + (b"invalid in-place patch geometry" if receiver else b"source only") + layout = mota.Nrf52Layout(0x26000, 0xED000, 0xED000, flags) + body = mota.ensure_nrf52_layout(body, layout) + image = body + mota.build_endf(body) + if corrupt: + image = b"X" + image[1:] + archive = io.BytesIO() + with zipfile.ZipFile(archive, "w") as package: + package.writestr("manifest.json", json.dumps({"manifest": { + "application": {"bin_file": "app.bin", "dat_file": "app.dat"}}})) + package.writestr("app.bin", image) + package.writestr("app.dat", b"init packet") + return {"dfu-package": archive.getvalue()} + + def test_nrf52_lora_requires_packaged_receiver_and_valid_layout(self): + for artifacts in [self.nrf_dfu(receiver=False), self.nrf_dfu(corrupt=True)]: + result, manifest = self.run_checker( + b"dfu invalid in-place patch geometry", "--platform", "NRF52_PLATFORM", + "--require-ota", "--expect", "ota.update.bluetooth=dfu", + "--expect", "ota.update.lora=invalid in-place patch geometry", artifacts=artifacts) + self.assertEqual(result.returncode, 1) + self.assertFalse(manifest["ota_update_verified"]) + self.assertNotIn("ota.update.lora", manifest["capabilities"]) + + def test_nrf52_lora_reports_storage_specific_requirements(self): + for flags, storage, types in [(16, "internal_flash_and_retained_ram", ["in_place_delta"]), + (0, "internal_flash", ["in_place_delta"]), + (4, "external_qspi", ["full", "in_place_delta"]), + (1, "external_sd", ["full", "in_place_delta"])]: + result, manifest = self.run_checker( + b"dfu invalid in-place patch geometry", "--platform", "NRF52_PLATFORM", + "--require-ota", "--expect", "ota.update.bluetooth=dfu", + "--expect", "ota.update.lora=invalid in-place patch geometry", artifacts=self.nrf_dfu(flags)) + self.assertEqual(result.returncode, 0, result.stderr) + self.assertEqual(manifest["ota_update_methods"], ["bluetooth", "lora"]) + details = manifest["ota_update_requirements"]["lora"] + self.assertEqual(details["storage"], storage) + self.assertEqual(details["package_types"], types) + self.assertTrue(details["bootloader_release"].endswith("0.11.0-OTAFIX2.4.6")) + + def test_nrf52_full_companion_cannot_claim_lora_self_update(self): + result, manifest = self.run_checker( + b"invalid in-place patch geometry", "--platform", "NRF52_PLATFORM", + "--target", "RAK_4631_companion_radio_full", "--require-ota", + "--expect", "ota.update.lora=invalid in-place patch geometry", artifacts=self.nrf_dfu()) + self.assertEqual(result.returncode, 1) + self.assertEqual(manifest["ota_update_methods"], []) + if __name__ == "__main__": unittest.main()