A "Firmware update (OTA)" tile in the repeater hub (admins, tth fork switch kOtaUpdate) pushes a delta of a meshcore-tth -ota image over the mesh: the package that starts from the node's image is picked from the chosen .mcfw files, binary chunks with text as the fallback, an airtime budget, verify and apply. Optionally on a side channel: the node goes to another preset by tempradio, the companion follows (checked), the chunks go zero-hop and both come back at the end. A port of the reference engine of the tth.meshcore Ansible collection (module_utils/meshcore_ota_engine.py); test/services/ota/ota_vectors.json is its test-vector file. Bench 16. 11. 2026: the connector over TCP to a USB companion, side channel 866.0/SF7, applied a 2.7 kB delta, 20 s airtime, companion back on its preset. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
20 lines
905 B
Dart
20 lines
905 B
Dart
/// Build switches of the tth fork (git.rfa.cz/tth-pub/meshcore-open).
|
|
library;
|
|
|
|
/// On-device ML is stubbed out (stubs/README.md): translation and the neural
|
|
/// image codec cannot work, so their settings - and the model downloads
|
|
/// behind them - are hidden.
|
|
const bool kOnDeviceMl = false;
|
|
|
|
/// Opening a repeater/room screen (status, telemetry, neighbours) does NOT
|
|
/// query the node over the mesh: each screen waits for its refresh button.
|
|
/// Upstream fetches on open. The settings screen (a dozen CLI requests on
|
|
/// open) is no longer ours: upstream #614 made that fetch opt-in, off by
|
|
/// default (app setting "auto fetch repeater settings").
|
|
const bool kFetchRemoteOnOpen = false;
|
|
|
|
/// Admin-pushed OTA firmware update of meshcore-tth `-ota` nodes over the mesh
|
|
/// (lib/services/ota, screens/repeater_ota_screen.dart): a tile in the
|
|
/// repeater hub for admins.
|
|
const bool kOtaUpdate = true;
|