320 Commits
Author SHA1 Message Date
tthandClaude Opus 5.5 b30cda7936 Repeater, room server, sensor (nRF52): get chip tells the silicon and whether SWD can read the flash
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 20:42:59 +01:00
upstream-sync-bot ac49cd6621 Merge upstream/dev (2 commits) [upstream-sync]
pub-release / release (push) Successful in 33m10s
2026-11-19 17:05:35 +00:00
fdlamotte 6e47ba6fa6 Merge pull request #3776 from Blake-Latchford/docs/stats-core-error-flags
docs: describe stats-core output and its error flags
2026-11-19 12:42:00 -04:00
tthandClaude Opus 5.5 b7249f449a Repeater, room server, sensor, companion: build flag LOCKED_NODE for a node that keeps its secrets from whoever holds it
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 17:21:29 +01:00
tthandClaude Opus 5.5 961547c7d2 README, docs: replay floor for admins only (de92ca9b), capped wrong passwords and the blank-login floor (dbdae145) -- LOGIN_FAIL_MAX/SECS, upstream candidates
pub-release / release (push) Successful in 38m32s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 13:04:29 +01:00
tthandClaude Opus 5.5 c8d75947f8 README, docs: the replay floor that survives a reboot (1171d8f9) -- core fix, ACL_TS_MAX_AHEAD, upstream candidate
pub-release / release (push) Successful in 34m9s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 10:31:04 +01:00
tthandClaude Opus 5.5 41d3ba93ea docs/tth-commands.md: every console command of the fork, where it exists, defaults
pub-release / release (push) Canceled after 22s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 02:11:04 +01:00
tthandClaude Opus 5.5 0a88dda5f8 README: the fork's extras as they really ship -- watchdogs, defaults, what is release vs own build
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 02:08:33 +01:00
tthandClaude Opus 5.5 4b2da2924f README: experimental firmware, not meant for regular users -- said first
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 01:56:56 +01:00
tthandClaude Opus 5.5 27949062df docs: OTA side channel, the one engine in tth.meshcore, the phone app
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 00:18:28 +01:00
tthandClaude Opus 5.5 a69e97583e ota_mesh_push.py, ota_push.py: run the tth.meshcore OTA engine instead of their own copies
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 23:17:55 +01:00
tthandClaude Opus 5.5 f6e792f1bb ota_mesh_push.py: --side F,BW,SF,CR carries the transfer on a side channel
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 22:23:27 +01:00
tthandClaude Opus 4.8 a80e68186d docs/ota.md: watchdog recovery, and flag it as a rolling dev release
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-11-16 22:02:39 +01:00
upstream-sync-bot 8c11154a3a Merge upstream/dev (6 commits) [upstream-sync]
pub-release / release (push) Successful in 36m41s
2026-11-15 17:06:10 +00:00
Liam Cottle 04afba03ba Merge pull request #3754 from netrunnereve/bluetooth-name
Allow the user to set a custom bluetooth name using the cli
2026-11-15 20:01:46 +13:00
Eve 7416193a76 change prefix as well 2026-11-14 15:17:32 -05:00
tthandClaude Opus 5.5 d9c7b9c008 Repeater: TX stall watchdog -- packets queued, nothing sent for 15 min: re-arm, then reboot
pub-release / release (push) Successful in 39m1s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 11:02:58 +01:00
tthandClaude Opus 5.5 01d66a66ce docs/power.md: rxps failed on the live mesh (fewer packets, TX stall); tickless loop sleep measured at zero
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 10:49:16 +01:00
upstream-sync-bot fbefa417b9 Merge upstream/dev (16 commits) [upstream-sync]
pub-release / release (push) Successful in 37m31s
2026-11-14 05:06:06 +00:00
Eve de721bcb4b use ble.name 2026-11-13 20:35:32 -05:00
tthandClaude Opus 5.5 d22005a6fd OTA phase 5: tools and docs ready for the public export
pub-release / release (push) Successful in 32m57s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 18:07:39 +01:00
tthandClaude Opus 5.5 845a228209 tools/ public with a local config, private tools to .tth/tools/
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 16:03:03 +01:00
Olexandr Tyshchenko 407cb9abac GPS: first fix timeout as a saved setting (gps firstfix), 1 h by default
A cold start can take up to ~30 min with a weak sky view, so the default
limit before the first fix since boot goes from 15 min to 1 h.

The limit is now a GPS preference, set with `gps firstfix <duration>`
(0 = no limit, at most 1 day) and saved with the other GPS settings, so
repeaters and companions can use different values without a rebuild.
GPS_FIRST_FIX_TIMEOUT_MS stays as the build default.
2026-11-13 14:29:02 +02:00
tthandClaude Opus 5.5 e6a3184423 pub-release, README: formatted flashing notes, release names, dutycycle
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 19:16:42 +01:00
Eve 9e70d32f79 add cli option to set custom bluetooth name 2026-11-12 11:09:43 -05:00
tthandClaude Opus 5.5 0d3cb6051d rxps: measured on the bench, documented, built into the public releases
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 16:53:44 +01:00
tthandClaude Opus 5.5 507842cea2 sensors: INA shunt set at runtime -- sensor set ina.shunt <mOhm>, kept in prefs
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 13:58:39 +01:00
tthandClaude Opus 5.5 6fe0c0f8e1 docs: power, budka sensor and BLE/LoRa coexistence notes under public paths
pub-release / release (push) Failing after 22s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 11:56:30 +01:00
tthandClaude Opus 5.5 3c7d947887 gps duty: sync once a day, retry a failed window after 6 h
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 09:49:46 +01:00
Olexandr Tyshchenko be9d278a96 Limit the first periodic GPS acquisition after boot
Before the first fix since boot, a periodic acquisition had no timeout. If no
fix is accepted (no sky view, no antenna, or a guard rejecting spoofed fixes),
the receiver then stayed on until a fix was accepted.

Give that window its own limit, GPS_FIRST_FIX_TIMEOUT_MS (15 min by default,
enough for a full almanac; 0 keeps the old behaviour). It counts as a miss and
the next acquisition starts after the configured period.
2026-11-12 10:48:10 +02:00
tthandClaude Opus 5.5 84e4136a84 docs: gps duty vs upstream gps period; advert.loc, not "set loc"
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 09:27:26 +01:00
tthandClaude Opus 5.5 8d0b0dd164 Merge upstream/dev (80 commits) [upstream-sync]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 09:22:19 +01:00
Olexandr Tyshchenko ace5230ff0 GPS guard: drop leftovers of the alert telemetry channel
#3813 removed the telemetry channel for the GPS time alert. Remove the
docs sentence that still described it and the now unused
GpsGuard::getAlertOffset().
2026-11-11 16:18:58 +02:00
fdlamotte 0ed9ba5724 Merge pull request #3801 from AlexandrTyshchenko/feature/gps-guard-time-wait
GPS guard: show "time wait" instead of "rej nofix" between fixes
2026-11-11 10:13:11 -04:00
Florent 798b719caf CommonCLI: get/set loc to replace gps advert command 2026-11-11 09:52:03 -04:00
Florent cefd4c76cf Revert "Merge pull request #3784 from Maxwell456/feature/repeater-history"
This reverts commit 66d404eac8, reversing
changes made to 1c4b237d73.
2026-11-11 07:49:41 -04:00
Olexandr Tyshchenko e1a445b967 GPS guard: show "time wait" instead of "rej nofix" between fixes
When the last GPS time check passed but there is no current trusted fix
(e.g. the GPS is asleep between periodic fixes), gps guard showed
"time rej nofix", which reads like a rejection although the clock is fine.
Show "time wait" instead. A real rejection without a trusted fix (GPS time
arriving while fixes are rejected) still shows "rej nofix".
2026-11-11 01:48:12 +02:00
fdlamotte 66d404eac8 Merge pull request #3784 from Maxwell456/feature/repeater-history
Add min/max/avg history queries to repeaters
2026-11-10 12:42:53 -04:00
fdlamotte 8b16d8eb5e Merge pull request #3785 from AlexandrTyshchenko/feature/companion-adc-multiplier
Companion: set/get adc.multiplier CLI command
2026-11-10 08:11:33 -04:00
fdlamotte 822bea7b7c Merge pull request #3753 from fdlamotte/gps_refactor
Big GPS refactor
2026-11-10 07:44:00 -04:00
Olexandr Tyshchenko 3da13dd91a GPS guard: gps guard on/off, saved in the GPS prefs 2026-11-09 23:50:48 +02:00
Olexandr Tyshchenko 6291f9156a GPS guard: save gps fence in the GPS prefs 2026-11-09 23:16:29 +02:00
Olexandr Tyshchenko faabf34950 GpsGuard: let GPS correct a clock outside the plausible window 2026-11-09 22:54:18 +02:00
Olexandr Tyshchenko f5cbc18b83 GPS guard: drop time force, it goes to a separate PR 2026-11-09 22:30:24 +02:00
Olexandr Tyshchenko 6b3da8a2b1 GPS: optional anti-spoofing guard for position and time (GPS_GUARD)
A spoofed GPS signal can move a fixed node anywhere and set its clock to
any time; the clock only moves forward, so a time pushed into the future
breaks timestamps and replay protection until fixed by hand.

With GPS_GUARD, MicroNMEALocationProvider asks a GpsGuard before a fix is
stored as the last fix (satellites, HDOP, optional region box, fence
around the configured position, jump speed, N stable fixes) and before
GPS time is written to the clock (trusted fix current, not before the
build date, small steps once the clock is valid, drift-sized after the
first sync). Without a trusted fix no live position is reported.

CLI in CommonGpsPrefs: 'gps guard', 'gps guard accept', 'gps fence',
'gps ref'; CommonCLI keeps the reference on set lat/lon and gps setloc,
resets the time anchor on manual clock sets and adds 'time force'.

Ported from #3736 onto the GpsDriver/LocationProvider refactor.
2026-11-09 20:43:09 +02:00
Olexandr Tyshchenko 3f23ba9b2d Companion: set/get adc.multiplier CLI command, persisted in prefs
Repeaters, room servers and sensors already let the battery ADC multiplier be tuned with 'set adc.multiplier' (CommonCLI). The companion firmware had no equivalent, so a board whose divider differs from the build default (common on DIY ProMicro / Faketec boards) always reported a wrong battery voltage.

Adds the same command to the companion CLI. The value is stored in the companion prefs (comp.adc_mult, 0 = board default) and applied at startup via MainBoard::setAdcMultiplier().
2026-11-08 18:07:58 +02:00
Maxwell 64f75005b5 Add min/max/avg history queries to repeaters
Move TimeSeriesData from simple_sensor into src/helpers and drive it with
monotonic uptime, so RTC changes cannot stall recording or break queries.
Keep the old RTCClock* overloads as deprecated for custom sensor sketches.

Record 24h of battery, noise floor, TX/RX airtime % and MCU temperature on
repeaters and answer the existing 0x04 min/max/avg request using the same
format as sensor nodes. No packets are sent by this feature.
REPEATER_HISTORY_SLOTS=0 removes it; default off on STM32/RP2040.

Add native tests for TimeSeriesData and document the request and channels.
2026-11-08 16:34:54 +02:00
Florent b2e46335e5 ui_task: let user choose if enter in gps screen toggles or triggers gps 2026-11-08 08:47:35 -04:00
Florent 6b34ae96df gps: Rework the CLI
- more consistency with other cli commands
- new format for gps fix
- gps format accepts postfix (s/m/d/h)
- documentation
2026-11-08 08:47:35 -04:00
Florent 47959b8960 gps: fix_stats command 2026-11-08 08:47:34 -04:00