MeshCore Ninja
← ZephCore

ZephCore · Releases

from GitHub · updated 2026-06-21

20 releases

  1. v20260619.094253 # 2 days ago · 2026-06-19 09:43 UTC
    View release ↗

    ZephCore v1.16.3-zephyr

    (re-re-re-release(last time I swear) with the "smearing fix on eink after the full update" and "automount error on a freshly formatted node")

    [!IMPORTANT]

    Before you upgrade

    Updating from v1.16.2 — clean flash, no re-bond required, bonds survive.

    Updating from v1.16.1 or older — flash the firmware; the firmware detects the old installation on first boot and clears the BLE bond storage automatically. Your identity, contacts, channels, and prefs are preserved. You will need to re-bond your phone/desktop once (old pairings were stored in a different location that v1.16.2 moved away from). No formatter tool required.

    Coming from Arduino MeshCore — flash the firmware; it detects the incompatible filesystem on first boot and formats automatically. Everything starts fresh (new identity, clean storage). No formatter tool required.

    Take this with a grain of salt tho… try the formatters if anything anomalous happens with your node.

    This is a GPS-focused release: it stops a battery-killing bug on GPS trackers, puts the GPS duty cycle under your control, and follows up the v1.16.2 ESP32 pairing work with a fix for recent Android phones.

    Highlights

    Fixed: ThinkNode M1 draining its battery in a day

    On the ThinkNode M1, the GPS module was never actually powered down between fixes — the reset line was mislabeled in the board definition and held permanently released, so the receiver kept drawing current even when the firmware thought it was asleep. A full battery could disappear in roughly a day with GPS enabled.

    The M1 now asserts the GPS hardware reset on standby, so the GPS genuinely stops between fixes. If you run an M1 with GPS on, this is the fix you want.

    New: configurable GPS duty cycle — set gps duty <seconds>

    You can now decide how your node handles GPS, instead of it being baked in:

    • set gps duty <seconds> — how long the GPS sleeps between fixes. Persists to flash and applies immediately.
    • set gps duty 0 — always-on: the GPS never sleeps. It streams fresh fixes (so telemetry is always current) and stays on long enough to download a full almanac.
    • set gps duty default — reset to the role default.
    • get gps duty — show the now-effective interval.

    This unifies repeaters and companions behind one knob. Repeaters default to 48 h (GPS wakes only for periodic time-sync) and companions to 5 minutes — both now adjustable. Existing repeaters are migrated automatically; nothing to do.

    Bad input is rejected with a usage hint, and the value is clamped to a sane range (10 s … 1 week, or 0 for always-on).

    Fixed: GPS no longer pins itself on waiting for a first fix

    Previously, after enabling GPS a companion would keep the receiver powered indefinitely until it got its first fix — so a node left somewhere without sky view (indoors, in a bag) could quietly drain its battery forever. The first cold-start acquisition is now bounded (5 minutes by default, enough for a genuine cold start), after which the node drops into its normal duty cycle whether or not it got a fix.

    Fixed: ESP32 Secure Connections pairing (Pixel 7 / recent Android)

    Following the v1.16.2 ESP32 pairing fix, SC-capable centrals — notably recent Android phones like the Pixel 7 — still failed to bond: the controller's encryption table was left uninitialized because the relevant code was guarded on an ESP-IDF symbol that never exists in a Zephyr build, so the link dropped with a MIC failure at encryption start. The guard is corrected (carried as a managed hal_espressif patch), and SC pairing now completes. Legacy-pairing devices were unaffected and continue to work. Thanks @seagull9000.

    Other fixes and improvements

    • Fixed: GPS always-on on a freshly flashed companion — a new install would default gps_interval to 0 (always-on) instead of the intended 5-minute duty cycle, causing the …
  2. v20260616.202853 # 5 days ago · 2026-06-16 20:29 UTC
    View release ↗

    ZephCore v1.16.2-zephyr

    [!IMPORTANT]

    Before you upgrade — please read

    This release changes where devices store their BLE pairing data. The change affects all platforms, but the upgrade steps differ:

    All boards (nRF52 and ESP32): you must re-bond. Existing phone/desktop pairings will not carry over. After flashing, remove the old pairing from your device's Bluetooth settings (and from the ZephCore app), then pair again from scratch.

    nRF should update cleanly, but I recommend doing a flash erase + flash fw + import backup to be absolutely sure. Formatters can be found in the repo's formatter folder. Check your softdevice version before using one.

    Highlights

    Critical fix: ESP32 Bluetooth pairing restored

    On the updated Zephyr 4.4.1 base, ESP32 boards could advertise but never completed pairing — the Espressif Bluetooth controller would assert the moment a phone began to pair. This release restores the controller's link-layer encryption so pairing works again. If you have an ESP32-based node (Heltec, XIAO, Station G2, T-Beam, etc.), this is the fix you've been waiting for.

    Additionally, Android "connect from app" now works on ESP32. Advertising now always exposes the stable identity address, so the Android companion app's in-app connect flow succeeds while iOS pairing continues to work.

    BLE pairing data moved to its own storage area

    Bluetooth bonds previously shared the same filesystem as your identity, preferences, and contacts. They now live in a dedicated, isolated storage partition (NVS) on both nRF52 and ESP32. This means a busy pairing store can no longer corrupt your contacts or settings, and pairing writes never touch your user data.

    A factory reset (erase) now also clears stored BLE bonds, then reboots automatically so everything comes back up clean — previously bonds could survive an erase.

    New board: Heltec Wireless Tracker V1.1 (ESP32-S3 + SX1262), thanks to @seagull9000

    Full support for the Heltec Wireless Tracker V1.1 companion (ESP32-S3 + SX1262 radio + ST7735R TFT + UC6580 GPS), including:

    • Correct battery ADC routing (avoids a wiring conflict in the upstream board definition that otherwise broke all LoRa SPI reads)
    • Battery voltage/percentage readings
    • Onboard GNSS
    • Status-LED heartbeat
    • OLED/TFT display and BLE companion transport

    New board: LilyGo T-Beam v1.2 (SX1262)

    Full support for the classic-ESP32 LilyGo T-Beam v1.2 with the SX1262 radio, including:

    • AXP2101 power management (LoRa + GPS rails brought up automatically at boot)
    • Battery fuel-gauge readings over I2C — accurate battery voltage and percentage, even though this board has no battery ADC
    • Onboard GNSS (NEO-6M / NEO-M8N)
    • The user button wired up (short press = page/select, long press = action)
    • OLED display, BLE companion transport, and CLI-based repeater mode

    Note: classic-ESP32 repeaters (e.g. T-Beam) run CLI-only and do not include WiFi-AP OTA — the WiFi driver buffers plus OTA heap don't fit the classic ESP32's RAM. ESP32-S3 / C-series repeaters keep WiFi OTA.

    E-paper anti-ghosting

    E-paper displays now perform a periodic full refresh (every 8 partial updates by default) to clear the faint "ghost" images that build up where text changes most often, like the status bar. The interval is configurable build-time, and the feature is automatically ignored on OLED/TFT screens that don't ghost.

    More reliable companion connection (Linux / native transport)

    The native TCP transport now applies the same congestion control already used over Bluetooth. Instead of silently dropping data when the connection is briefly saturated (for example, an incoming message arriving during a large contact/channel import), it now back-pressures and retries, and important protocol responses are never dropped. A stalled peer that stops reading is cleanly dis …

  3. v20260613.205222 # 8 days ago · 2026-06-13 20:52 UTC
    View release ↗

    DO NOT DOWNLOAD THIS RELEASE JUST TO UPDATE, YOU NEED A FLASH ERASE FOR IT TO WORK PROPERLY. I'LL RE-RELEASE IT SOON AS I CATCH THE BUG! (it seems devices with multiple bondings are affected only)

    So if something is broken: delete bond, erase flash and try again.

    What's New

    • RX duty cycle (power saving) reworked — now properly tested against the datasheet, gives ~40-55% radio-off time with no packet loss on up-to-date nodes. Toggle with set rxduty on/off. (Mixed old/new meshes: keep it off on infra nodes for now. Needs preamble 32 on adjacent nodes)
    • Joystick UI now shows accented characters (Hungarian/Slovak/Czech/Polish/etc. names display correctly), emojis are stripped instead of showing garbage. Unlock gesture changed to Left -> OK -> Right (easier/faster than the old Back-OK-Back).
    • set rxduty / set radio.rxgain now also accept on / off, not just 1/0.

    Fixes

    • WisMesh Tag battery percentage was reading high — calibration corrected.
    • RTC clock could get permanently stuck blank after battery loss — now recovers and re-syncs.
    • Clock source indicator (GPS/App/Local) and display now update correctly/immediately.
    • Auto-shutdown no longer triggers on a brief voltage dip during transmit (needs 3 low readings in a row now).
    • Fixed a race in MQTT "online" status reporting on repeaters/observers.
    • Several small crash/overflow hardening fixes from ongoing code audit (no user-visible behavior change).
  4. v20260608.105434 # 13 days ago · 2026-06-08 10:54 UTC
    View release ↗

    New

    Hardware RTC auto-discovery

    Out-of-the-box nodes with a battery/cap-backed I2C RTC (DS3231, PCF8563, RV3028, RX8130CE) now restore the clock at boot — shown tagged L until the next GPS / app / CLI sync — and write the time back on every sync so it survives power-off. Boards opt in via boards/common/rtc-i2c.dtsi; on boards without it, this compiles to nothing.

    First wired up on LilyGo T-Echo and ThinkNode M1.

    Buttonless BLE DFU (legacy Nordic/Adafruit OTA jump)

    A paired phone can now trigger the jump into the bootloader's BLE OTA mode directly from the DFU Firmware Upgrade app — no button press needed (nRF52 only). The service exposes the full legacy DFU characteristic set (Control Point, Packet, Revision) so iOS's DFU library can discover and identify the device correctly.

    Companion needs disconnecting from MeshCore app first!

    This was only tested with a handful of nodes and an iOS! This change can introduce errors in other phones I'm not aware of. A BLE bond delete + re-pair should solve it.

    BLE TX power bumped to +8 dBm

    Raised from +4 dBm → +8 dBm, the max output the nRF52840 / nRF54L high-power radio front-end supports — better range and link margin for the companion connection. This is still under test, but should not cause excessive/noticeable battery drain.

    MIT license formalized

    Added zephcore/LICENSE (MIT, same as upstream MeshCore) and flipped the SPDX-License-Identifier header across the source tree from Apache-2.0 to MIT. Vendored dependencies that carry their own compatible licenses (Monocypher, Zephyr patches) are noted at the bottom of the license file.

    Fixed

    • Companion startup races — initial-advert handling and contact-table iteration were running on sysworkq while the main thread mutated the same mesh/contact state, a race that could corrupt state or wedge the contact dump. Both now run on the main thread, driven through the event loop (MESH_EVENT_CONTACT_ITER), same as the rest of the mesh state machine.

    • Hardware-RTC writes no longer race the main loop — zephcore_rtc_save() is now routed through the same deferred-to-main-thread mechanism as prefs flushes (MESH_EVENT_RTC_SAVE). GPS fixes land on the GNSS modem-chat thread and just stash the latest epoch; the actual blocking I2C write happens on the main thread, coalescing multiple pending fixes into one save.

    • MAX_ANON_CONTACTS cap fixed — transient/anon contact slots (e.g. created for BLE direct-message lookups to non-contact pubkeys) were being capped by MAX_CONTACTS instead of their own larger allotment, causing premature slot exhaustion/eviction.

    • XIAO nRF54L15 build fixed.

    Internals

    • ZephyrCompanionUSB — assembled V3 frames now wake the main thread via k_event instead of k_work_submit on sysworkq, matching the BLE RX path and removing a parse-vs-loop() race.

    • Buttonless DFU now hard-depends on SOC_SERIES_NRF52 (was a soft default y). Other nRF52-only paths (bootloader-version scan, VBUS detect, formatter/updater tools) were cleaned up to drop the redundant SOC_SERIES_NRF52X checks.

    • West Update — Zephyr updated to 4.4.1-rc1

  5. v20260606.150211 # 15 days ago · 2026-06-06 15:02 UTC
    View release ↗

    Synced with upstream vanilla MeshCore v1.16.0

  6. v20260605.132226 # 16 days ago · 2026-06-05 13:22 UTC
    View release ↗

    New

    USB serial console for companions Configure companion devices (e.g. Wio Tracker L1) by typing commands over USB, no phone app needed. Works in the flasher.meshcore.io serial console (or any terminal), just like the repeater CLI. Stays out of the way of the Bluetooth/USB app — only one connection is active at a time.

    Battery gauge calibration (adc.multiplier) Correct the battery voltage reading so the % is accurate for your device:

    • set adc.multiplier full — calibrate at full charge (easiest)
    • set adc.multiplier target <mV> — calibrate to a multimeter reading (most accurate)
    • set adc.multiplier 0 — reset to default
    • get adc.multiplier — show current

    Per-device battery curves Battery % now uses a real, device-specific voltage curve instead of a rough estimate, so readings are far more accurate. Included for Wio Tracker L1, T1000-E, SenseCAP Solar, ThinkNode M6, and RAK WisMesh Tag (others use a sensible default).

    Low-battery auto-shutdown Battery-powered companions now power down automatically when the cell runs low (default 3.3 V, ~10% on the new curves) to protect it from over-discharge. Shows a brief "Low Battery — Shutting Down" notice first (3 s on OLED; e-paper just leaves it on screen), and is skipped while charging or on USB power so it never cuts out a plugged-in device. On by default for nRF52 companions. Tune it over the USB console:

    • set autoshutdown <mV> — set the cutoff (1–5000 mV)
    • set autoshutdown 0 — turn it off
    • get autoshutdown — show current

    Clock source indicator The time in the top bar now shows a tiny letter telling you where it was last synced from: G (GPS), A (phone app), N (network), or L (local). If the device hasn't heard from GPS or the app in the last 12 hours, it falls back to L — the clock is just free-running on the device's own crystal at that point (drift is only a few seconds a day, so it stays accurate, but you know it isn't being checked against an outside source). After a restart it shows L until the first sync.

    Fixed

    Device name no longer overlaps the clock On the home screen, a long device name used to run underneath the time and battery in the top bar, making both unreadable. The name is now trimmed to fit the space before the clock, on any screen size.

  7. v20260603.123327 # 18 days ago · 2026-06-03 12:33 UTC
    View release ↗

    (Re-Released because of native linux bugfixes)

    New

    • Room Server (BBS) role (no auto-build, no repeater function)
    • GAT562 30S Mesh Kit board support (nRF52840 + SX1262, RAK4631 core, 30 dBm PA) — one image for both the full kit and the screenless solar repeater.
    • Production is now the default build — no more prod.conf; debug.conf is the opt-in for logging.
    • USB companion decoupled from logging — CDC ACM transport now compiles independently of CONFIG_LOG. (companions are USB+BLE hybrid from now, only one type can be connected at a time)
    • Linux native target — built and shipped as executables (companion + repeater).
    • Battery reading should be more precise with board specific curve support and a standard lipo curve for devices that does not have any data on the internet about it's curve

    Bug Fixes

    • USB cable-yank no longer strands the companion on USB and blocks BLE until reboot.
    • BLE/USB transport handoff reworked to first-come-first-served, made thread-safe.
    • Zero-delay direct/zero-hop sends over BLE/USB no longer stall.
    • Channel reply from the Unread screen now sends instead of silently failing.
    • Repeater anon reply with a malformed return path now floods (safe fallback) instead of emitting a corrupt direct packet.
    • Header-error frames now counted as receive errors (and no more zombie packet receptions triggered)
    • Airtime/LDRO estimate fixed to track the driver across every SF/BW.
    • RNG seed derivation hardened against hash failure.

    Internals

    • Crypto: orlp/ed25519 → Monocypher 4.0.2 — audited, single-file. Existing identities load/sign/verify unchanged — no re-key, no migration, full wire compatibility.
    • Bumped west / pinned Zephyr tree.
    • Synced with vanilla MeshCore dev.
    • Split RepeaterMesh into Uplink + RegionCLI; deduped app-layer response/telemetry/JSON builders.
    • Simplified the packet manager, dispatcher, and radio config paths.
  8. v20260528.133858 # 24 days ago · 2026-05-28 13:39 UTC
    View release ↗

    Security

    • Hardened login password comparison against timing side-channel attacks
    • Fixed weak entropy at first boot — initial device identity is now properly random
    • Fixed 3 RNG edge cases that could produce predictable output under certain startup conditions

    Bug Fixes

    • Fixed repeater + observer mode combo not working together
    • USB: unified CDC ACM init across companion and repeater, removed unnecessary boot delays

    New

    • Native Linux target — initial port for desktop testing
  9. v20260522.140428 # 1 month ago · 2026-05-22 14:04 UTC
    View release ↗

    Wio Tracker — completely new joystick UI (thanks @Calvario) — new screen lifecycle, DM retry, channel send with feedback, GPS screen with altitude, lock screen, time sync, path hash bytes setting, and more.

    Heltec T114 board support (thanks @Calvario) — with and without screen.

    PSRAM activation on capable devices — enables OTA on boards that support it.

    Sync with vanilla MeshCore dev

    Bug Fixes BLE disabled state now correctly honoured — watchdog was silently re-enabling BLE on every housekeeping tick Fixed out-of-bounds read in path-decoding (BLE + LoRa-anon paths) Null-termination fix in Add/Update Contact command Fixed overflow frame being clobbered under BLE congestion Fixed T114 long press Several BLE audit hardening fixes (error codes, length checks, buffer sizing)

  10. v20260514.205836 # 1 month ago · 2026-05-14 20:58 UTC
    View release ↗
    • New experimental RX-busy latch: ZephCore now tracks an in-progress reception across the full packet, so the transmitter won't step on a packet that's already being decoded.
    • Improved CAD (Listen-Before-Talk) behavior: the radio re-enters listening mode faster between TX retries on busy channels, and a stuck channel-busy state recovers automatically instead of requiring a reset.
    • updated default prefs to advert less and loop detect moderate
  11. v20260511.125830 # 1 month ago · 2026-05-11 12:58 UTC
    View release ↗
    • Channel deletion safety: fixed bug where deleting the public channel could wipe other channels after reboot.
    • LBT retry priority: preserved flood packet priority during LBT-based retransmissions.
    • CAD/LBT mode switching: fixed radio reconfiguration so mode changes are fully applied.
    • rx_boost init: set deterministic startup state to avoid undefined boot behavior.
    • Atomic contact saves (QSPI): contacts now use temp+sync+rename on external flash devices.
    • Atomic write refactor: unified temp-file atomic write flow used by datastore save paths.
    • promicro_sx1262 build support: fixed/added board build wiring and related project metadata.
    • Vanilla sync (CompanionMesh): aligned local logic with upstream baseline changes.
    • SX1262 patch updates: refined Zephyr SX126x native patch and related ignore rules.
  12. v20260507.103840 # 2 months ago · 2026-05-07 10:38 UTC
    View release ↗

    In one of my ravings trying to shorten rx-rx and tx-rx path I accidentally disabled hardware CAD. This release just does that: re-enables it.

    Also added formatters for nRF here: https://github.com/liquidraver/ZephCore/tree/master/formatter

    Hardware CAD test:

    Nothing catched in that 2 symbol CAD check:

    sx126x_irq_work_handler: IRQ status: 0x0080 sx126x_irq_work_handler: CAD done: free sx126x_irq_work_handler: IRQ status: 0x0001 sx126x_handle_irq_tx_done: TX done lora_radio_base: TX complete, RX restarted

    Something was in our channel during CAD check:

    sx126x_irq_work_handler: IRQ status: 0x0180←[0m sx126x_irq_work_handler: CAD done: activity←[0m sx126x_lora_send_async: LBT: channel busy←[0m lora_radio_base: hwSendAsync failed: -16←[0m zephcore_dispatcher: checkSend: startSendRaw failed! re-queuing delay=240 ....same goes on for 3-4 times then: sx126x_irq_work_handler: IRQ status: 0x0080 sx126x_irq_work_handler: CAD done: free sx126x_irq_work_handler: IRQ status: 0x0001 sx126x_handle_irq_tx_done: TX done lora_radio_base: TX complete, RX restarted

  13. v20260506.102120 # 2 months ago · 2026-05-06 10:21 UTC
    View release ↗

    • Duty cycling is now disabled by default. Further research showed that preamble 16 is NOT enough for a reliable duty cycle in noisy environments, so we'll wait for most of the mesh switching to preamble 32 to test it further

    • SX driver had some serious issues with CAD so it is recommended to update to this version as soon as possible

    • GPS will not be disabled if no GNSS message comes in (on repeaters), that was a test-code that stuck

  14. v20260505.131914 # 2 months ago · 2026-05-05 13:19 UTC
    View release ↗

    Kistarcsa-edition

    Tested in the depths of the tarcsa-cauldron with weak/noisy/who-knows-whats-the-problem-of-that-heltecv3 repeater, optimized for the aforementioned use-case.

    • Duty cycle is 13/3 now. Slightly more battery consumption, but better RX error margin. No use for extra battery time if packets are lost in noisy/weak link environments.
    • hwconfig now has a fail-safe so no more edge-case unsaved radio settings
    • SX TX Ramp time increased to 800µs from 200µs. expect very heavy latency increase if you can sense time in a different way normal humans do! (also expect cleaner spectral mask at 22 dBm. nobody cares about it, doesn't change anything in a meaningful way, but it's a playground, we optimize even things that doesn't really need optimizing) (ask your favourite AI what are the benefits of 800µs vs 200µs if interested)
    • Companions had too much initial jitter with zero benefit, so it was tuned down to RNG20-150msec
    • Claude noticed some line ending stuff by itself, without asking, so I gave him credit (heh)
  15. v20260502.112307 # 2 months ago · 2026-05-02 11:23 UTC
    View release ↗

    This release only removes the "hot path" after finishing TX. It was an attempt to eliminate "Sent" but not "Heard X repeats" messages. I re-did the math, we don't need to stay in full RX after TX for any reason, immediately back to duty cycling is fine until someone starts to use SF7/BW500. Getting back to duty cycling is in the ms range, no preamble can be missed, so "Sent" but not "Heard" packets are seems to be truly RF collision/repeater listening to other packets etc.

  16. v20260501.191026 # 2 months ago · 2026-05-01 19:10 UTC
    View release ↗
    • Fixed a freeze that could happen on startup or when changing channels
    • Fixed receive sensitivity boost not being applied (it was always off regardless of settings)
    • Fixed interference filtering not being recalibrated correctly on 868/433/779 MHz — improves range and reliability
    • Fixed a rare bug where packets could be missed or processed twice
    • After sending a message, the radio now stays in receive mode for 3 seconds before going back to sleep — reduces chance of missing a reply
    • Various tuning improvements to how the radio sleeps and wakes while listening
  17. v20260430.112448 # 2 months ago · 2026-04-30 11:25 UTC
    View release ↗
    • Added explicit "none" scope handling so companion sends stay unscoped even when a default scope exists.
    • Hardened packet and mesh security paths with multiple small fixes, including validation/handling updates in Packet.cpp and Mesh.cpp.
    • Fixed small BLE behavior issues in companion message handling.
    • Fixed an SX126x native driver race condition (via Zephyr patch update) to improve radio stability under concurrent events.
    • Increased LoRa preamble settings to align behavior with vanilla baseline. (increased to 32)
  18. v20260429.104549 # 2 months ago · 2026-04-29 10:46 UTC
    View release ↗

    BLE

    • Major BLE improvements for companion connectivity, behavior, and reliability. (you can switch on Experimental Settings > Faster Channel Syncing in official app now)
    • Internal BLE stack refinements and protocol handling cleanups.

    Radio / LoRa (SX126x)

    • Fixed SX126x duty-cycle RX recovery to properly re-arm after BUSY timeout conditions.
    • Fixed SX126x TX-enable GPIO handling when dio2-tx-enable is active. (Heltecs were behaving badly because of this!)

    Board / Hardware Fixes

    • Fixed rak4631 handling to avoid toggling SX1262 power-enable pin unexpectedly. (#18)
    • Added full display reset after splash screen to improve display bring-up stability. + stole vanilla's refresh algo
  19. v20260428.134456 # 2 months ago · 2026-04-28 13:45 UTC
    View release ↗

    -disable GPS cycle until reboot if no GNSS messages present -make our sx driver more aligned with radiolib's logics (BUSY-line timeout protection, Wake-from-sleep robustness) -runtime guard agc reset if rx duty cycle is enabled -tune delay knobs (move closer to vanilla values) -refactor repeater prefs changes (fix prefs not stored / overwritten on a second "set" command AND don't apply new radio prefs before reboot) -micro-tweak: skip APC math when APC is off -port vanilla duty cycling logic and replace our coarse method -fix RX duty cycling logic (it was 9symbol rx / 6symbol sleep instead of 10/6)

  20. v20260427.083554 # 2 months ago · 2026-04-27 08:36 UTC
    View release ↗

    -Fix repeater prefs not persisting path.hash.mode, loop.detect, radio.rxgain, rxduty, APC settings across reboots -Fix stack overflow in prefs load (8-byte buffer for 25-byte read) that silently corrupted owner.info on every boot -Fix get radio.rxgain always returning radio frequency/BW settings instead of RX gain boost value -Repeater first-boot and firmware-upgrade now correctly default radio.rxgain and rxduty to ON for SX1262 boards -Fix setting new repeater radio preset/individual settings applying immediately instead only after reboot