4079 Commits
Author SHA1 Message Date
Florent 798b719caf CommonCLI: get/set loc to replace gps advert command 2026-11-11 09:52:03 -04:00
fdlamotte f349ead541 Merge pull request #3813 from fdlamotte/gps_guard_telem_removal
gps_guard: remove time alert telemetry
2026-11-11 08:06:44 -04:00
fdlamotte 092da136dc Merge pull request #3811 from fdlamotte/mdns_using_char
companion_radio: rewrite mdns part removing String class
2026-11-11 07:58:59 -04:00
Florent 7de440c0d3 gps_guard: remove time alert telemetry 2026-11-11 07:58:39 -04:00
fdlamotte d901822bdf Merge pull request #3812 from fdlamotte/revert-3784
Revert "Merge pull request #3784 from Maxwell456/feature/repeater-his…
2026-11-11 07:52:27 -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
Florent 5662e79a78 companion_radio: rewrite mdns part removing String class 2026-11-11 07:37:24 -04:00
fdlamotte 067fb64994 Merge pull request #3810 from fdlamotte/revert_rak13302_tests
tests: revert rak13302 tests
2026-11-11 07:30:25 -04:00
Florent b3b227b773 tests: revert rak13302 tests 2026-11-11 07:26:01 -04:00
Liam Cottle 401fd6c037 Merge pull request #3807 from Valentin-Metz/fix/cli-reply-buffer-overflow
Fix stack-buffer overflow in CLI reply buffers
2026-11-11 17:37:42 +13:00
Valentin Metz f02d9d9e47 Fix stack-buffer overflow in CLI reply buffers
The remote-CLI reply buffers in onPeerDataRecv() (repeater, room server,
sensor) and BaseChatMesh were sized temp[166] for a 5-byte datagram
header plus 161 bytes of reply. But MyMesh::handleCommand() first
reflects a 3-byte correlation prefix (e.g. 'aa|') into the reply, after
which CommonCLI commands may write up to 160 chars + NUL into the
remaining 158 bytes -- overflowing the buffer by 2 bytes (e.g. a full
'regions' listing via exportTo(reply, 160)).

Triggering this remotely crashes the node (observed as an unresponsive
repeater after a prefixed 'regions' query); the 2 out-of-bounds bytes
are a printable region-name character and a NUL.

Size the buffers for the full worst case instead:
5 header + 3 prefix + 160 reply + 1 NUL = 169.

Verified with a host ASan harness reproducing the exact layout:
prefixed 'regions' with a 25-region listing overflowed temp[166]
(BufStream::write, RegionMap.cpp) and now passes clean with temp[169];
unprefixed (serial) path unaffected.
2026-11-11 05:30:54 +01: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 06719e6877 Merge pull request #3798 from AlexandrTyshchenko/feature/gps-baud-probe-list
GPS: GPS_BAUD_PROBE_LIST as a build flag for any NmeaGpsDriver; enable on Station G2/G3
2026-11-10 18:57:35 -04:00
Olexandr Tyshchenko 790f4d3f08 GPS: GPS_BAUD_PROBE_LIST as a build flag for any NmeaGpsDriver; enable on Station G2/G3
The probe list was wired only in variants/promicro/target.cpp. It is now the
default list of NmeaGpsDriver when GPS_BAUD_PROBE_LIST is set, so a variant
enables baud autodetection with a build flag alone.

Station G2 and G3 enable it: their Grove UART connector is used with M5Stack
Unit GPS modules, which default to 115200.
2026-11-10 23:51:29 +02:00
Florent 8f0da87099 Remove waveshare_c3_zero
- the PR was made against main instead of dev
- the board does not have a LORA chip, and there is no LORA
  daughterboard associated with waveshare Zero ecosystem
2026-11-10 13:05:59 -04:00
fdlamotte 084a0700b2 Merge pull request #3677 from mloszand/Add-Waveshare-ESP32-C3-Zero-support
Add Waveshare ESP32-C3-Zero support
2026-11-10 12:51:15 -04: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 1c4b237d73 Merge pull request #3770 from lihardyextreme/feature-mdns
feat: mDNS ESP32 - enable local network discovery over mDNS
2026-11-10 12:07:18 -04:00
fdlamotte 095bd8c311 Merge pull request #3793 from fdlamotte/eink_hibernate_when_off
eink: some updates (busy loop + hibernate when screen off)
2026-11-10 12:00:43 -04:00
Florent 474021f10a eink: some updates (busy loop + hibernate when screen off) 2026-11-10 11:52:38 -04:00
fdlamotte 684d960e6f Merge pull request #3778 from dahuib/rak16000-v1.18.0-clean
Support RAK16000 (INA219 at 0x41)
2026-11-10 11:45:43 -04:00
dahuib 6ce010fbfe Support RAK16000 (INA219 at 0x41) on dev 2026-11-10 15:57:32 +01:00
fdlamotte 3e84250e44 Merge pull request #3623 from BeGiBue/feature/wio-l1-eink-repeater
Add repeater environment for Wio Tracker L1 E-Ink
2026-11-10 09:06:45 -04:00
fdlamotte 41540f1642 Merge pull request #3664 from Martin-hub1/dev
Add DFRobot LoRaWAN ESP32-S3 Companion BLE firmware
2026-11-10 09:06:07 -04:00
fdlamotte 98cfba42b9 Merge pull request #3613 from agessaman/feat/rak13302-auto-onboard-sleep
feat(rak3401): automatically sleep the RAK4631’s onboard SX1262 when paired with a RAK13302
2026-11-10 09:01:51 -04:00
fdlamotte 573037fd77 Merge pull request #3792 from recrof/revert-3756-rp2350_pico2
Revert "Support for RP2350 board"
2026-11-10 08:48:11 -04:00
Rastislav Vysoky 46606a4b03 Revert "Support for RP2350 board" 2026-11-10 13:43:09 +01:00
fdlamotte be36c02d5b Merge pull request #3724 from akalinin-softvelum/feature/eink-busy-hook-v2
companion: keep mesh/BLE running during e-ink refresh
2026-11-10 08:40:43 -04:00
fdlamotte 8d56dcc877 Merge pull request #3725 from Blake-Latchford/fix/espnow-no-lora-build
Fix Generic_ESPNOW_* builds on boards without a LoRa radio
2026-11-10 08:25:37 -04:00
fdlamotte d4fcba9dd0 Merge pull request #3648 from olimexsmart/feature/lilygo-t3-stm32
Add LilyGO T3 STM32 support
2026-11-10 08:23:03 -04:00
fdlamotte f40e13a425 Merge branch 'dev' into feature/lilygo-t3-stm32 2026-11-10 08:22:52 -04:00
fdlamotte 9cafb91f7f Merge pull request #3756 from nminaylov/rp2350_pico2
Support for RP2350 board
2026-11-10 08:16:29 -04:00
fdlamotte 16d4cbfd1d Merge pull request #3762 from wmacgreg/feature/nucleo-wl55jc
Add variant for ST Nucleo-WL55JC1 (STM32WL55JC) 🤖🤖
2026-11-10 08:14:51 -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
fdlamotte 41eb344511 Merge pull request #4 from AlexandrTyshchenko/feature/gps-guard-refactor
GPS: optional anti-spoofing guard for position and time (GPS_GUARD)
2026-11-09 18:02:06 -04:00
Olexandr Tyshchenko 3da13dd91a GPS guard: gps guard on/off, saved in the GPS prefs 2026-11-09 23:50:48 +02:00
fdlamotte 8363b347b7 Merge pull request #3 from AlexandrTyshchenko/feature/gps-baud-autodetect-refactor
NmeaGpsDriver: optional UART baud rate detection from a per-board list
2026-11-09 17:38:29 -04:00
Olexandr Tyshchenko 6291f9156a GPS guard: save gps fence in the GPS prefs 2026-11-09 23:16:29 +02:00
Olexandr Tyshchenko ca5ccddc85 NmeaGpsDriver: baud rates to probe come from the board, not a build flag 2026-11-09 22:59:47 +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 1c9adb46cb GpsGuard: do not show a stale time ok without a current trusted fix 2026-11-09 22:15:45 +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 978f2662c6 NmeaGpsDriver: optional UART baud rate autodetection (GPS_BAUD_AUTODETECT)
Bytes arriving on the UART does not mean the baud rate is right: at the
wrong rate the parser only sees garbage and never gets a fix. Modules
such as the M5Stack GROVE GPS now default to 115200, while boards
configure 9600.

With GPS_BAUD_AUTODETECT, detect() probes common GNSS rates, starting
with the configured one, and keeps the first one that yields an NMEA
sentence with a valid checksum. The rate is stored in the driver, so
later power cycles reopen the UART with it. Without the flag nothing
changes.

Ported from #3729 onto the GpsDriver refactor.
2026-11-08 23:24:29 +02:00
upstream-sync-bot aa30e3734e Merge upstream/dev (6 commits) [upstream-sync]
pub-release / release (push) Successful in 23m16s
2026-11-08 17:06:05 +00: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
Martin Boissonneault 017005d1cf rak4631: let the serial GPS switch the WB_IO2 rail (opt-in)
On a RAK19007 the RAK12501's supply is 3V3_S, switched by WB_IO2, so
gps off, periodic mode and shutdown left it powered. Pass WB_IO2 to the
NMEA driver as peripheralPower under GPS_RAIL_POWER_CONTROL, set by the
new RAK_4631_repeater_gps_power env. It is opt-in because the rail feeds
every slot module, and refused with ETHERNET_ENABLED (RAK13800).

The RAK12500 (I2C) driver keeps switching its own power pin, so this
only applies on the NMEA path.

RefCountedDigitalPin now sets OUTPUT on claim and release: WB_IO2 left
as an input (as probeRak12500() leaves it after a failed probe) keeps
3V3_S in its last state, so writing the latch alone did not cut it.

Measured with a KM003C, battery and panel out: gps off 40.5 -> 12.4 mA,
shutdown 29.7 -> 1.30 mA.
2026-11-08 08:47:35 -04: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