\n\n[!CAUTION]\nThis is a pre-release. ESP32 light sleep is enabled by default on Heltec repeaters and has not\nbeen validated on hardware yet — see the light-sleep section for what to check and how to build it\nout. It is deliberately not published to the apps.meshamerica.com configurator, which keeps\noffering v1.16.7; flash this one manually from the assets below if you want to help test it.\nThe nRF based boards should be fine.
\n
\n\n[!IMPORTANT]
\nBefore you upgrade
\nFrom v1.16.5 / v1.16.6 / v1.16.7 — clean flash, no re-bond, bonds and data survive.
\nFrom v1.16.2 / v1.16.3 / v1.16.4 — clean flash, bonds and data survive. If you are on an\nESP32-S3 / ESP32-C board and have not yet taken the v1.16.5 update, you still owe the one-time\nserial reflash: the app moved to flash offset
\n0x10000in v1.16.5, and a board on the old layout\ncannot cross that update over WiFi-OTA or the browser flasher — flash the-merged.binonce over\nUSB/serial. Affected boards: Heltec V3 / V4 / V4.3, Station G2, Wireless Tracker / V2, XIAO\nESP32-S3 / C3 / C6, LilyGo T-Lora C6, ThinkNode M9. Identity, contacts, channels, prefs, and BLE\nbonds are preserved. nRF52, classic ESP32 (T-Beam / PICO-D4 / TTGO LoRa32), STM32WL, and native\nLinux are unaffected.From v1.16.1 or older — flash it; on first boot it clears BLE bonds automatically (identity,\ncontacts, channels, prefs preserved). Re-bond your phone/desktop once.
\nComing from Arduino MeshCore — flash it; auto-formats on first boot (new identity, clean storage).
\nHeltec ESP32 repeaters now light-sleep, and their USB CLI stops answering 10 minutes after boot\nas a result. Reconnecting your terminal normally resets the node and gives you another 10 minutes;\nif it doesn't, power-cycle. Details in the light-sleep section below.
\nOne CLI rename:
\nset/get cad.probe.intervalis nowset/get probe.interval— the same setting,\nrenamed because one measurement now feeds both the noise floor and the CAD probe. Your stored value\ncarries over; only the command name changed.set/get agc.reset.intervalis gone (see below).Take this with a grain of salt — try the formatters if anything anomalous happens with your node.
\n
A power and radio-measurement release. Repeaters no longer wake on a fixed 5 s tick — they sleep\nuntil their next real deadline. Every ESP32 build drops to 80 MHz, and Heltec repeaters now light-sleep\nbetween packets. The noise-floor sampler and CAD probe were unified into one measurement, the\nSX126x RSSI/AGC calibration is now band-correct, and the observer role got a batch of fixes for settings\nthat silently never reached the hardware.
\nEvery repeater woke five times a second-and-a-bit forever: a fixed 5 s \"housekeeping\" timer that ran the\nnoise-floor sample, the CAD probe, advert timers and the tempradio revert. None of that actually needs a\npoll — each item is either a deadline or a sampler with its own interval.
\nThe new mesh/Maintenance.h contract lets the event loop ask \"when does maintenance next have work?\"\nand arm one one-shot wake for exactly that moment. An idle repeater now sleeps until its soonest real\ndeadline instead of on a fixed cadence. A hard ceiling (CONFIG_ZEPHCORE_MAINTENANCE_BACKSTOP_MS,\ndefault 60 s) clamps the wake as a safety net against a missed deadline — it should never bind in\nnormal operation.
Companions and room servers keep their periodic tick deliberately: the companion block contains genuine\npollers (contact-dump progress, BLE advertising watchdog) with no deadline to arm, and the room server is\npaced by its own 500 ms push timer regardless.
\nEspressif parts have no equivalent of the nRF52's \"idle at microamps in WFI\" — WAITI gates the core\nclock but le\n…
\n\n[!IMPORTANT]
\nBefore you upgrade
\nFrom v1.16.6 / v1.16.5 — clean flash, no re-bond, bonds and data survive.
\nFrom v1.16.2 / v1.16.3 / v1.16.4 — clean flash, bonds and data survive. If you are on an\nESP32-S3 / ESP32-C board and have not yet taken the v1.16.5 update, you still owe the one-time\nserial reflash: the app moved to flash offset
\n0x10000in v1.16.5, and a board on the old layout\ncannot cross that update over WiFi-OTA or the browser flasher — flash the-merged.binonce over\nUSB/serial. Affected boards: Heltec V3 / V4 / V4.3, Station G2, Wireless Tracker / V2, XIAO\nESP32-S3 / C3 / C6, LilyGo T-Lora C6. Identity, contacts, channels, prefs, and BLE bonds are\npreserved. nRF52, classic ESP32 (T-Beam / PICO-D4 / TTGO LoRa32), STM32WL, and native Linux are\nunaffected.From v1.16.1 or older — flash it; on first boot it clears BLE bonds automatically (identity,\ncontacts, channels, prefs preserved). Re-bond your phone/desktop once.
\nComing from Arduino MeshCore — flash it; auto-formats on first boot (new identity, clean storage).
\nTake this with a grain of salt — try the formatters if anything anomalous happens with your node.
\n
A stability-and-hardware release. The headline is a whole-node wedge fixed in the GPS power-management\npath that shipped in v1.16.6, plus RX duty cycle finally working on LR1110 boards and a new safety\nmargin that stops signal-independent duty-cycle packet drops on every radio. Rounded out by joystick-UI\nfixes and a color-display improvement for the Heltec T114.
\nv1.16.6 introduced GPS-UART suspend to save power (an armed nRF UARTE receiver costs ~0.5–1 mA even with\nthe GPS module powered down). It had a race that could hang the entire node — no LoRa, no USB, no BLE,\nCLI answering -> busy, recoverable only by reboot.
The upstream nRF UARTE suspend path spins forever waiting for an RXTO event after issuing STOPRX. In\ninterrupt-driven mode the receiver runs one byte at a time and re-arms from its ISR; if a byte happened to\nfinish in the narrow window where the driver had already disabled the ENDRX interrupt, the receiver was\nleft stopped-and-un-rearmed, STOPRX produced no RXTO, and the wait never returned — with the main mesh\nthread stuck inside it. Any nRF board that powers its GPS module down and suspends the port on standby\ncould hit this.
Fixed in two independent layers, so neither alone is load-bearing:
\nZephyrGPSManager settles ~5 ms before suspending the GPS UART, letting the last in-flight byte\nfinish and the RX ISR re-arm, so the receiver is armed-and-idle when STOPRX fires — the state that\nreliably yields RXTO. Standby happens at most every few minutes, so the cost is negligible.0010 bounds the driver's RXTO wait to 4 ms instead of spinning forever. On timeout it\nfalls through to the unconditional nrf_uarte_disable() that force-stops the receiver anyway — so even\nif a byte still lands in the race window, the node can never hang.LR1110 boards (T1000-E, ThinkNode M9, and other LR11xx radios) now get real RX duty-cycle sniff mode\ninstead of sitting in continuous receive — a substantial receive-power saving on battery nodes, the same\nmechanism SX126x boards have had. This took a significant rework of the LR11xx LoRa driver to land\ncorrectly.
\nset-able via CONFIG_ZEPHCORE_LORA_DC_MARGIN_PCT (default 15%), shared by every radio\n(SX126x / LR11xx / LR20xx).
The theoretical per-cycle \"deaf-time\" budget that duty cycle is computed from assumes the sleep clock and\nthe wake transition are exact. They are not: the chip's sleep timer runs on an internal RC oscillator\n(RC64k on SX126x, RTC on LR11xx) that drifts several\n…
\n" }, { "version": "1.16.6-zephcore", "name": "Firmware 1.16.6-zephcore", "datetime": "2026-07-23T15:33:05Z", "url": "https://github.com/liquidraver/ZephCore/releases/tag/1.16.6-zephcore", "prerelease": false, "notes": "# ZephCore 1.16.6-zephcore\r\n\r\n> [!IMPORTANT]\r\n> ## Before you upgrade\r\n>\r\n> **From v1.16.5** — clean flash, no re-bond, bonds and data survive.\r\n>\r\n> **From v1.16.2 / v1.16.3 / v1.16.4** — clean flash, bonds and data survive. If you are on an\r\n> **ESP32-S3 / ESP32-C board** and have *not* yet taken the v1.16.5 update, you still owe the one-time\r\n> serial reflash described there: the app moved to flash offset `0x10000` in v1.16.5, and a board on the\r\n> old layout cannot cross that update over WiFi-OTA or the browser flasher — **flash the `-merged.bin`\r\n> once over USB/serial.** Affected boards: *Heltec V3 / V4 / V4.3, Station G2, Wireless Tracker / V2,\r\n> XIAO ESP32-S3 / C3 / C6, LilyGo T-Lora C6.* Identity, contacts, channels, prefs, and BLE bonds are\r\n> preserved. nRF52, classic ESP32 (T-Beam / PICO-D4 / TTGO LoRa32), STM32WL, and native Linux are\r\n> unaffected.\r\n>\r\n> **From v1.16.1 or older** — flash it; on first boot it clears BLE bonds automatically (identity,\r\n> contacts, channels, prefs preserved). Re-bond your phone/desktop once.\r\n>\r\n> **Coming from Arduino MeshCore** — flash it; auto-formats on first boot (new identity, clean storage).\r\n>\r\n> Take this with a grain of salt — try the formatters if anything anomalous happens with your node.\r\n\r\n---\r\n\r\nA maintenance release: an important **admin-password fix**, a substantial **identity-key randomness\r\nhardening** on ESP32, **GPS standby power savings**, and the removal of **Adaptive Power Control** —\r\nplus two new boards, **muzi works R1 Neo** and an experimental first cut at the **ThinkNode M9** in dev.\r\n\r\n## Highlights\r\n\r\n### 2-tap and 5-tap are switched\r\nAfter a lot of inadvertently sent adverts, the functions of the 2 and 5 clicks were switched, so a double click with the user button now only enables/disables the LEDs and no longer accidentally sends a flood advert.\r\n\r\n### Fixed: uppercase letters in an admin password were silently lowercased\r\n\r\n**If you set or changed an admin password on v1.16.5 and can no longer log in, this is why.** v1.16.5\r\nintroduced case-insensitive CLI keywords by lowercasing the first two words of every command before\r\nmatching them. That is safe for `get cad` — but `password\n\n[!IMPORTANT]
\nBefore you upgrade
\nFrom v1.16.5 — clean flash, no re-bond, bonds and data survive.
\nFrom v1.16.2 / v1.16.3 / v1.16.4 — clean flash, bonds and data survive. If you are on an\nESP32-S3 / ESP32-C board and have not yet taken the v1.16.5 update, you still owe the one-time\nserial reflash described there: the app moved to flash offset
\n0x10000in v1.16.5, and a board on the\nold layout cannot cross that update over WiFi-OTA or the browser flasher — flash the-merged.bin\nonce over USB/serial. Affected boards: Heltec V3 / V4 / V4.3, Station G2, Wireless Tracker / V2,\nXIAO ESP32-S3 / C3 / C6, LilyGo T-Lora C6. Identity, contacts, channels, prefs, and BLE bonds are\npreserved. nRF52, classic ESP32 (T-Beam / PICO-D4 / TTGO LoRa32), STM32WL, and native Linux are\nunaffected.From v1.16.1 or older — flash it; on first boot it clears BLE bonds automatically (identity,\ncontacts, channels, prefs preserved). Re-bond your phone/desktop once.
\nComing from Arduino MeshCore — flash it; auto-formats on first boot (new identity, clean storage).
\nTake this with a grain of salt — try the formatters if anything anomalous happens with your node.
\n
A maintenance release: an important admin-password fix, a substantial identity-key randomness\nhardening on ESP32, GPS standby power savings, and the removal of Adaptive Power Control —\nplus two new boards, muzi works R1 Neo and an experimental first cut at the ThinkNode M9 in dev.
\nAfter a lot of inadvertently sent adverts, the functions of the 2 and 5 clicks were switched, so a double click with the user button now only enables/disables the LEDs and no longer accidentally sends a flood advert.
\nIf you set or changed an admin password on v1.16.5 and can no longer log in, this is why. v1.16.5\nintroduced case-insensitive CLI keywords by lowercasing the first two words of every command before\nmatching them. That is safe for get cad — but password <value> puts the value in the second word,\nso password MyPass was stored as mypass, and the password you typed afterwards never matched.\n(set guest.password <value> has three words and was never affected.)
The normalizer has been removed and CLI commands are case-sensitive again, matching upstream Arduino\nMeshCore. If you are locked out, re-flash and reconfigure, or log in with the all-lowercase form of the\npassword you set.
\nThe one place autocapitalization genuinely hurts — typing commands to the V-Contact from a phone keyboard,\nwhich capitalizes the first letter of every line — is handled narrowly instead: only character 0 of a\nV-Contact chat line is folded. No command takes an argument at position 0, so no value can be touched.
\nYour node's identity — the Ed25519 keypair that is your node on the mesh — is generated once, on first\nboot, and kept for life. An investigation into how the randomness behind that key is gathered found that\nESP32 boards were generating identities with far less entropy than intended. Two independent problems,\nboth fixed in this release:
\n\n\n[!IMPORTANT]
\nBefore you upgrade
\nESP32-S3 / ESP32-C boards — one-time serial reflash required; WiFi-OTA cannot bridge this update.\nThis release moves the application to a new flash location (
\n0x10000). A board on the old layout can't\nupdate to this build over WiFi-OTA or the browser flasher — flash the-merged.binonce over USB/serial.\nAffected boards: Heltec V3 / V4 / V4.3, Station G2, Wireless Tracker / V2, XIAO ESP32-S3 / C3 / C6, LilyGo T-Lora C6.\nYour identity, contacts, channels, prefs, and BLE bonds are preserved. After this reflash, OTA and\napp-updates work again.nRF52, classic ESP32 (T-Beam / PICO-D4 / TTGO LoRa32), STM32WL, and native Linux are unaffected — upgrade as usual.
\nFrom v1.16.2 / v1.16.3 / v1.16.4 — clean flash, no re-bond, bonds and data survive.
\nFrom v1.16.1 or older — flash it; on first boot it clears BLE bonds automatically (identity, contacts, channels, prefs preserved). Re-bond your phone/desktop once.
\nComing from Arduino MeshCore — flash it; auto-formats on first boot (new identity, clean storage).
\nTake this with a grain of salt — try the formatters if anything anomalous happens with your node.
\n
The headline of this release:\nAdaptive CAD, a self-tuning listen-before-talk that calibrates itself to each site;\nV-Contact, an in-app admin \"channel\" for companions; and a batch of LoRa-driver reliability fixes.
\nOn ESP32-S3 / ESP32-C boards, the app and MCUboot bootloader were using different flash partition tables,\nso each OTA update landed at an address the bootloader never checked. Every upload \"succeeded\" and then\nquietly did nothing. Both images now share one partition map, and OTA works correctly. (The XIAO C3/C6 and\nT-Lora C6 used the stock layout and were never affected.)
\n0x10000The ESP32 app slot moved from 0x20000 to 0x10000 — matching the Arduino / ESP-IDF offset. This is the\nchange that fixes OTA above, and it also enables the configurator's fast app-only update (rewrites just\nthe app, keeps your settings). Requires the one-time serial reflash (see Before you upgrade).
Every transmission is preceded by a Channel Activity Detection (CAD) check that listens for other LoRa\ntraffic and holds off if the channel is busy. How sensitive that check is has always been a single\nhardcoded number — but the right value depends on where the node lives. A quiet valley node and a\n50-network hilltop need very different thresholds: too sensitive and the node keeps deferring for phantom\ntraffic (wasted airtime, latency); not sensitive enough and it transmits over real packets (collisions).
\nNodes now measure their own RF environment and adjust automatically. In the background, between\ntransmissions, the radio runs short calibration probes, tracks how often each sensitivity level produces a\nfalse \"busy\", and settles on the lowest false-positive threshold for that site — responding to a\nchanging environment within an hour or two. It runs on repeaters and companions, and it is on by\ndefault; there is nothing to configure.
\nget cad — watch what it's doing: the current threshold and per-level false-positive statistics.set cad.auto off — turn off the auto-adjust to observe or hand-tune with set cad.offset.Quiet sites end up more sensitive than the old fixed default (fewer stomped packets); noisy sites back\noff until the false alarms stop. CAD also now uses 4 detection symbols everywhere, which improves detection\nof an in-progress packet's payload (not just its preamble). Full guide, including the honest limitation\nthat the \"missed detection\" side isn't locally observable, is in\n**[ADAPTIVE_CAD.md](https://github.com/liquidraver/ZephCore/blob/master/zephcore/ADAPTIVE\n…
\n" }, { "version": "v20260714.095706", "name": "Firmware v20260714.095706", "datetime": "2026-07-14T09:57:21Z", "url": "https://github.com/liquidraver/ZephCore/releases/tag/v20260714.095706", "prerelease": false, "notes": "# ZephCore v1.16.5-zephyr\r\n\r\n(re-release because vContact caused regression in settings import / update)\r\n\r\n> [!IMPORTANT]\r\n> ## Before you upgrade\r\n>\r\n> **ESP32-S3 / ESP32-C boards — one-time serial reflash required; WiFi-OTA cannot bridge this update.**\r\n> This release moves the application to a new flash location (`0x10000`). A board on the old layout can't\r\n> update to this build over WiFi-OTA or the browser flasher — **flash the `-merged.bin` once over USB/serial.**\r\n> Affected boards: *Heltec V3 / V4 / V4.3, Station G2, Wireless Tracker / V2, XIAO ESP32-S3 / C3 / C6, LilyGo T-Lora C6.*\r\n> Your identity, contacts, channels, prefs, and BLE bonds are preserved. After this reflash, OTA and\r\n> app-updates work again.\r\n>\r\n> **nRF52, classic ESP32 (T-Beam / PICO-D4 / TTGO LoRa32), STM32WL, and native Linux are unaffected** — upgrade as usual.\r\n>\r\n> **From v1.16.2 / v1.16.3 / v1.16.4** — clean flash, no re-bond, bonds and data survive.\r\n>\r\n> **From v1.16.1 or older** — flash it; on first boot it clears BLE bonds automatically (identity, contacts, channels, prefs preserved). Re-bond your phone/desktop once.\r\n>\r\n> **Coming from Arduino MeshCore** — flash it; auto-formats on first boot (new identity, clean storage).\r\n>\r\n> Take this with a grain of salt — try the formatters if anything anomalous happens with your node.\r\n\r\n---\r\n\r\nThe headline of this release:\r\n\r\n### New: flash ZephCore from your browser — Mesh America configurator\r\nZephCore is now a listed provider in the **[Mesh America Device Configurator](https://apps.meshamerica.com)**.\r\nPick your board and flash directly — companion (BLE and USB) or repeater — no toolchain, no drag-and-drop.\r\n\r\n**Adaptive CAD**, a self-tuning listen-before-talk that calibrates itself to each site;\r\n\r\n**V-Contact**, an in-app admin \"channel\" for companions; and a batch of LoRa-driver reliability fixes.\r\n\r\n## Highlights\r\n\r\n### Fixed: ESP32 WiFi-OTA silently reverted — upload hit 100%, then booted the *old* firmware\r\nOn ESP32-S3 / ESP32-C boards, the app and MCUboot bootloader were using different flash partition tables,\r\nso each OTA update landed at an address the bootloader never checked. Every upload \"succeeded\" and then\r\nquietly did nothing. Both images now share one partition map, and OTA works correctly. (The XIAO C3/C6 and\r\nT-Lora C6 used the stock layout and were never affected.)\r\n\r\n### ESP32 app slot moved to `0x10000`\r\nThe ESP32 app slot moved from `0x20000` to `0x10000` — matching the Arduino / ESP-IDF offset. This is the\r\nchange that fixes OTA above, and it also enables the configurator's fast **app-only update** (rewrites just\r\nthe app, keeps your settings). Requires the one-time serial reflash (see *Before you upgrade*).\r\n\r\n### New: Adaptive CAD — listen-before-talk that tunes itself to your site\r\nEvery transmission is preceded by a Channel Activity Detection (CAD) check that listens for other LoRa\r\ntraffic and holds off if the channel is busy. How sensitive that check is has always been a single\r\nhardcoded number — but the right value depends on where the node lives. A quiet valley node and a\r\n50-network hilltop need very different thresholds: too sensitive and the node keeps deferring for phantom\r\ntraffic (wasted airtime, latency); not sensitive enough and it transmits over real packets (collisions).\r\n\r\nNodes now **measure their own RF environment and adjust automatically**. In the background, between\r\ntransmissions, the radio runs short calibration probes, tracks how often each sensitivity level produces a\r\nfalse \"busy\", and settles on the lowest false-positive threshold for *that* site — responding to a\r\nchanging environment within an hour or two. It runs on repeaters and companions, and it is **on by\r\ndefault**; there is nothing to configure.\r\n\r\n- `get cad` — watch what it's doing: the current threshold and per-level false-positive statistics.\r\n- `set cad.auto off` — turn off the auto-adjust to observe or hand-tune with `set cad.offset`.\r\n\r\nQuiet sites end up *more* sensitive tha\n…", "notesHtml": "(re-release because vContact caused regression in settings import / update)
\n\n\n[!IMPORTANT]
\nBefore you upgrade
\nESP32-S3 / ESP32-C boards — one-time serial reflash required; WiFi-OTA cannot bridge this update.\nThis release moves the application to a new flash location (
\n0x10000). A board on the old layout can't\nupdate to this build over WiFi-OTA or the browser flasher — flash the-merged.binonce over USB/serial.\nAffected boards: Heltec V3 / V4 / V4.3, Station G2, Wireless Tracker / V2, XIAO ESP32-S3 / C3 / C6, LilyGo T-Lora C6.\nYour identity, contacts, channels, prefs, and BLE bonds are preserved. After this reflash, OTA and\napp-updates work again.nRF52, classic ESP32 (T-Beam / PICO-D4 / TTGO LoRa32), STM32WL, and native Linux are unaffected — upgrade as usual.
\nFrom v1.16.2 / v1.16.3 / v1.16.4 — clean flash, no re-bond, bonds and data survive.
\nFrom v1.16.1 or older — flash it; on first boot it clears BLE bonds automatically (identity, contacts, channels, prefs preserved). Re-bond your phone/desktop once.
\nComing from Arduino MeshCore — flash it; auto-formats on first boot (new identity, clean storage).
\nTake this with a grain of salt — try the formatters if anything anomalous happens with your node.
\n
The headline of this release:
\nZephCore is now a listed provider in the Mesh America Device Configurator.\nPick your board and flash directly — companion (BLE and USB) or repeater — no toolchain, no drag-and-drop.
\nAdaptive CAD, a self-tuning listen-before-talk that calibrates itself to each site;
\nV-Contact, an in-app admin \"channel\" for companions; and a batch of LoRa-driver reliability fixes.
\nOn ESP32-S3 / ESP32-C boards, the app and MCUboot bootloader were using different flash partition tables,\nso each OTA update landed at an address the bootloader never checked. Every upload \"succeeded\" and then\nquietly did nothing. Both images now share one partition map, and OTA works correctly. (The XIAO C3/C6 and\nT-Lora C6 used the stock layout and were never affected.)
\n0x10000The ESP32 app slot moved from 0x20000 to 0x10000 — matching the Arduino / ESP-IDF offset. This is the\nchange that fixes OTA above, and it also enables the configurator's fast app-only update (rewrites just\nthe app, keeps your settings). Requires the one-time serial reflash (see Before you upgrade).
Every transmission is preceded by a Channel Activity Detection (CAD) check that listens for other LoRa\ntraffic and holds off if the channel is busy. How sensitive that check is has always been a single\nhardcoded number — but the right value depends on where the node lives. A quiet valley node and a\n50-network hilltop need very different thresholds: too sensitive and the node keeps deferring for phantom\ntraffic (wasted airtime, latency); not sensitive enough and it transmits over real packets (collisions).
\nNodes now measure their own RF environment and adjust automatically. In the background, between\ntransmissions, the radio runs short calibration probes, tracks how often each sensitivity level produces a\nfalse \"busy\", and settles on the lowest false-positive threshold for that site — responding to a\nchanging environment within an hour or two. It runs on repeaters and companions, and it is on by\ndefault; there is nothing to configure.
\nget cad — watch what it's doing: the current threshold and per-level false-positive statistics.set cad.auto off — turn off the auto-adjust to observe or hand-tune with set cad.offset.Quiet sites end up more sensitive tha\n…
\n" }, { "version": "v20260704.220543", "name": "Firmware v20260704.220543", "datetime": "2026-07-04T22:06:03Z", "url": "https://github.com/liquidraver/ZephCore/releases/tag/v20260704.220543", "prerelease": false, "notes": "# ZephCore v1.16.4-zephyr\r\n\r\n> [!IMPORTANT]\r\n> ## Before you upgrade\r\n>\r\n> **Updating from v1.16.2 or v1.16.3** — clean flash, no re-bond required, bonds and data survive.\r\n>\r\n> **Updating from v1.16.1 or older** — flash the firmware; on first boot it detects the old installation 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.\r\n>\r\n> **Coming from Arduino MeshCore** — flash the firmware; it detects the incompatible filesystem on first boot and formats automatically (new identity, clean storage). No formatter tool required.\r\n>\r\n> Take this with a grain of salt though — try the formatters if anything anomalous happens with your node.\r\n\r\n---\r\n\r\n(re-release because meshtimesync command's reply needed a facelift, UI lost uptime and had some offset quirk, nothing more)\r\n\r\nThe headline of this release is **Mesh Time Sync**: an optional, off-by-default feature that lets a node fix its own clock from the mesh — no GPS, no phone. Alongside it: two new board ports, a color-TFT UI pass, a flash-wear fix on GPS nodes, and a batch of multi-byte-path-hash bug fixes.\r\n\r\n## Highlights\r\n\r\n### New: Mesh Time Sync — self-correcting clocks from the mesh (simulated from EmpireMesh live data)\r\nYour node can now listen to the timestamps inside other nodes' signed adverts and, if its own clock is clearly wrong, gently correct itself. No GPS and no phone required. It works on every role (repeater, room server, observer, companion).\r\n\r\nWhy it matters: a node with a wrong clock shows garbage \"last heard\" times, and after a reboot without a time sync its own adverts can be silently ignored by every node that already knows it. On the live mesh today, almost half of all repeaters are more than an hour off — this fixes that whole class of problem automatically.\r\n\r\n**It is OFF by default. Nothing changes unless you enable it.**\r\n\r\n- `set meshtimesync on` — enable (USB serial CLI or remote admin on repeaters/room servers/observers; on companions toggle the `meshtimesync` custom variable from the app, or use the same command over the USB text CLI).\r\n- `get meshtimesync` — live view, even while the feature is off: how many trustworthy senders it sees, how many agree, and what correction it *would* make. Worth watching this dry-run for a day before (and after) you enable.\r\n\r\nGuardrails, in short: any clock set protects the node for 7 days — a GPS fix and a manual `time`/`clock sync` use the exact same 7-day suppression window, so a GPS-synced node is left alone just like a manually-set one (a live GPS re-arms it on every fix); it steps at most ±1 h at a time and at most once per 6 h; it does nothing without a quorum (default 6) of tenured, agreeing senders; and room servers/companions never step backward.\r\n\r\nFull documentation — how to switch it on, the honest limitations, and the recovery recipe — is in **[MESHTIMESYNC.md](https://github.com/liquidraver/ZephCore/blob/master/MESHTIMESYNC.md)**. Design details (consensus algorithm, security model, why the limits are what they are) are in ARCHITECTURE.md §4.9.\r\n\r\n### New boards\r\n- **Heltec Mesh Node T096** (nRF52840) — SX1262 + KCT8103L PA/FEM, UC6580 GNSS, ST7735S 160×80 color TFT, button, LED, battery ADC.\r\n- **Seeed LoRa-E5 mini** (STM32WLE5JC) — integrated sub-GHz radio (SX1262-class). No BLE/USB: runs as a companion + CLI over USART1 (serial companion transport).\r\n- **TTGO LoRa32** (ESP32 PICO-D4, **SX1276**) — added as the SX127x reference board (loramac-node backend), USB-UART CLI.\r\n- **LilyGo T-Impulse Plus** (nRF52840) — LoRa wristband: SX1262 (S62F module, embedded 32 MHz TCXO, GPIO antenna switch), u-blox MIA-M10Q GNSS, SSD1315 128×64 OLED, TTP223 touch button, haptic vibration motor, ZD25WQ32C 4 MB QSPI flash, battery ADC. Companion + repeater. Ported from LilyGo's official sources and builds clean; on-device bring-up pending (see the board README for the hardware-verify checklist).\r\n- **Helte\n…", "notesHtml": "\n\n[!IMPORTANT]
\nBefore you upgrade
\nUpdating from v1.16.2 or v1.16.3 — clean flash, no re-bond required, bonds and data survive.
\nUpdating from v1.16.1 or older — flash the firmware; on first boot it detects the old installation 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.
\nComing from Arduino MeshCore — flash the firmware; it detects the incompatible filesystem on first boot and formats automatically (new identity, clean storage). No formatter tool required.
\nTake this with a grain of salt though — try the formatters if anything anomalous happens with your node.
\n
(re-release because meshtimesync command's reply needed a facelift, UI lost uptime and had some offset quirk, nothing more)
\nThe headline of this release is Mesh Time Sync: an optional, off-by-default feature that lets a node fix its own clock from the mesh — no GPS, no phone. Alongside it: two new board ports, a color-TFT UI pass, a flash-wear fix on GPS nodes, and a batch of multi-byte-path-hash bug fixes.
\nYour node can now listen to the timestamps inside other nodes' signed adverts and, if its own clock is clearly wrong, gently correct itself. No GPS and no phone required. It works on every role (repeater, room server, observer, companion).
\nWhy it matters: a node with a wrong clock shows garbage \"last heard\" times, and after a reboot without a time sync its own adverts can be silently ignored by every node that already knows it. On the live mesh today, almost half of all repeaters are more than an hour off — this fixes that whole class of problem automatically.
\nIt is OFF by default. Nothing changes unless you enable it.
\nset meshtimesync on — enable (USB serial CLI or remote admin on repeaters/room servers/observers; on companions toggle the meshtimesync custom variable from the app, or use the same command over the USB text CLI).get meshtimesync — live view, even while the feature is off: how many trustworthy senders it sees, how many agree, and what correction it would make. Worth watching this dry-run for a day before (and after) you enable.Guardrails, in short: any clock set protects the node for 7 days — a GPS fix and a manual time/clock sync use the exact same 7-day suppression window, so a GPS-synced node is left alone just like a manually-set one (a live GPS re-arms it on every fix); it steps at most ±1 h at a time and at most once per 6 h; it does nothing without a quorum (default 6) of tenured, agreeing senders; and room servers/companions never step backward.
Full documentation — how to switch it on, the honest limitations, and the recovery recipe — is in MESHTIMESYNC.md. Design details (consensus algorithm, security model, why the limits are what they are) are in ARCHITECTURE.md §4.9.
\n\n\n(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\")
\n
\n\n[!IMPORTANT]
\nBefore you upgrade
\nUpdating from v1.16.2 — clean flash, no re-bond required, bonds survive.
\nUpdating 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.
\nComing 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.
\nTake this with a grain of salt tho… try the formatters if anything anomalous happens with your node.
\n
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.
\nOn 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.
\nThe 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.
\nset gps duty <seconds>You can now decide how your node handles GPS, instead of it being baked in:
\nset 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.
\n\n\nBad 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).
\n
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.
\nFollowing 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.
gps_interval to 0 (always-on) instead of the intended 5-minute duty cycle, causing the \n…\n\n[!IMPORTANT]
\nBefore you upgrade — please read
\nThis release changes where devices store their BLE pairing data. The change affects all platforms, but the upgrade steps differ:
\nAll 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.
\nnRF 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.
\n
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.
\nAdditionally, 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.
\nBluetooth 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.
\nA factory reset (erase) now also clears stored BLE bonds, then reboots automatically so everything comes back up clean — previously bonds could survive an erase.
Full support for the Heltec Wireless Tracker V1.1 companion (ESP32-S3 + SX1262 radio + ST7735R TFT + UC6580 GPS), including:
\nFull support for the classic-ESP32 LilyGo T-Beam v1.2 with the SX1262 radio, including:
\n\n\nNote: 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.
\n
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.
\nThe 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\n…
\n" }, { "version": "v20260613.205222", "name": "Firmware v20260613.205222", "datetime": "2026-06-13T20:52:38Z", "url": "https://github.com/liquidraver/ZephCore/releases/tag/v20260613.205222", "prerelease": false, "notes": "DO NOT DOWNLOAD THIS RELEASE JUST TO UPDATE, YOU NEED A FLASH ERASE FOR IT TO WORK PROPERLY.\r\nI'LL RE-RELEASE IT SOON AS I CATCH THE BUG!\r\n(it seems devices with multiple bondings are affected only)\r\n\r\nSo if something is broken: delete bond, erase flash and try again.\r\n\r\n\r\n\r\n\r\n\r\n## What's New\r\n\r\n- **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)\r\n- **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).\r\n- `set rxduty` / `set radio.rxgain` now also accept `on` / `off`, not just `1`/`0`.\r\n\r\n## Fixes\r\n\r\n- WisMesh Tag battery percentage was reading high — calibration corrected.\r\n- RTC clock could get permanently stuck blank after battery loss — now recovers and re-syncs.\r\n- Clock source indicator (GPS/App/Local) and display now update correctly/immediately.\r\n- Auto-shutdown no longer triggers on a brief voltage dip during transmit (needs 3 low readings in a row now).\r\n- Fixed a race in MQTT \"online\" status reporting on repeaters/observers.\r\n- Several small crash/overflow hardening fixes from ongoing code audit (no user-visible behavior change).", "notesHtml": "DO NOT DOWNLOAD THIS RELEASE JUST TO UPDATE, YOU NEED A FLASH ERASE FOR IT TO WORK PROPERLY.\nI'LL RE-RELEASE IT SOON AS I CATCH THE BUG!\n(it seems devices with multiple bondings are affected only)
\nSo if something is broken: delete bond, erase flash and try again.
\nset rxduty on/off. (Mixed old/new meshes: keep it off on infra nodes for now. Needs preamble 32 on adjacent nodes)set rxduty / set radio.rxgain now also accept on / off, not just 1/0.Out-of-the-box nodes with a battery/cap-backed I2C RTC (DS3231, PCF8563,\nRV3028, RX8130CE) now restore the clock at boot — shown tagged L until\nthe next GPS / app / CLI sync — and write the time back on every sync so it\nsurvives power-off. Boards opt in via boards/common/rtc-i2c.dtsi; on boards\nwithout it, this compiles to nothing.
\n\nFirst wired up on LilyGo T-Echo and ThinkNode M1.
\n
A paired phone can now trigger the jump into the bootloader's BLE OTA mode\ndirectly from the DFU Firmware Upgrade app — no button press needed (nRF52 only). The\nservice exposes the full legacy DFU characteristic set (Control Point, Packet,\nRevision) so iOS's DFU library can discover and identify the device correctly.
\nCompanion needs disconnecting from MeshCore app first!
\nThis 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.
\nRaised from +4 dBm → +8 dBm, the max output the nRF52840 / nRF54L\nhigh-power radio front-end supports — better range and link margin for the\ncompanion connection.\nThis is still under test, but should not cause excessive/noticeable battery drain.
\nAdded zephcore/LICENSE (MIT, same as upstream MeshCore) and flipped the\nSPDX-License-Identifier header across the source tree from Apache-2.0 to\nMIT. Vendored dependencies that carry their own compatible licenses\n(Monocypher, Zephyr patches) are noted at the bottom of the license file.
Companion startup races — initial-advert handling and contact-table\niteration were running on sysworkq while the main thread mutated the same\nmesh/contact state, a race that could corrupt state or wedge the contact\ndump. Both now run on the main thread, driven through the event loop\n(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()\nis now routed through the same deferred-to-main-thread mechanism as prefs\nflushes (MESH_EVENT_RTC_SAVE). GPS fixes land on the GNSS modem-chat thread\nand just stash the latest epoch; the actual blocking I2C write happens on the\nmain thread, coalescing multiple pending fixes into one save.
MAX_ANON_CONTACTS cap fixed — transient/anon contact slots (e.g.\ncreated for BLE direct-message lookups to non-contact pubkeys) were being\ncapped by MAX_CONTACTS instead of their own larger allotment, causing\npremature slot exhaustion/eviction.
XIAO nRF54L15 build fixed.
\nZephyrCompanionUSB — assembled V3 frames now wake the main thread via\nk_event instead of k_work_submit on sysworkq, matching the BLE RX path\nand removing a parse-vs-loop() race.
Buttonless DFU now hard-depends on SOC_SERIES_NRF52 (was a soft\ndefault y). Other nRF52-only paths (bootloader-version scan, VBUS detect,\nformatter/updater tools) were cleaned up to drop the redundant\nSOC_SERIES_NRF52X checks.
West Update — Zephyr updated to 4.4.1-rc1
\nSynced with upstream vanilla MeshCore v1.16.0
\n" }, { "version": "v20260605.132226", "name": "Firmware v20260605.132226", "datetime": "2026-06-05T13:22:43Z", "url": "https://github.com/liquidraver/ZephCore/releases/tag/v20260605.132226", "prerelease": false, "notes": "## New\r\n\r\n**USB serial console for companions**\r\nConfigure companion devices (e.g. Wio Tracker L1) by typing commands over USB, no phone app needed.\r\nWorks 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.\r\n\r\n**Battery gauge calibration (`adc.multiplier`)**\r\nCorrect the battery voltage reading so the % is accurate for your device:\r\n- `set adc.multiplier full` — calibrate at full charge (easiest)\r\n- `set adc.multiplier targetUSB serial console for companions\nConfigure companion devices (e.g. Wio Tracker L1) by typing commands over USB, no phone app needed.\nWorks 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.
\nBattery gauge calibration (adc.multiplier)\nCorrect 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 defaultget adc.multiplier — show currentPer-device battery curves\nBattery % now uses a real, device-specific voltage curve instead of a rough estimate, so readings are far more accurate.\nIncluded for Wio Tracker L1, T1000-E, SenseCAP Solar, ThinkNode M6, and RAK WisMesh Tag (others use a sensible default).
\nLow-battery auto-shutdown\nBattery-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.\nShows 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.\nOn by default for nRF52 companions.\nTune it over the USB console:
\nset autoshutdown <mV> — set the cutoff (1–5000 mV)set autoshutdown 0 — turn it offget autoshutdown — show currentClock source indicator\nThe 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).\nIf 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).\nAfter a restart it shows L until the first sync.
\nDevice name no longer overlaps the clock\nOn the home screen, a long device name used to run underneath the time and battery in the top bar, making both unreadable.\nThe name is now trimmed to fit the space before the clock, on any screen size.
\n" }, { "version": "v20260603.123327", "name": "Firmware v20260603.123327", "datetime": "2026-06-03T12:33:43Z", "url": "https://github.com/liquidraver/ZephCore/releases/tag/v20260603.123327", "prerelease": false, "notes": "(Re-Released because of native linux bugfixes)\r\n\r\nNew\r\n\r\n- Room Server (BBS) role (no auto-build, no repeater function)\r\n- 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.\r\n- Production is now the default build — no more prod.conf; debug.conf is the opt-in for logging.\r\n- 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)\r\n- Linux native target — built and shipped as executables (companion + repeater).\r\n- 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\r\n\r\nBug Fixes\r\n\r\n- USB cable-yank no longer strands the companion on USB and blocks BLE until reboot.\r\n- BLE/USB transport handoff reworked to first-come-first-served, made thread-safe.\r\n- Zero-delay direct/zero-hop sends over BLE/USB no longer stall.\r\n- Channel reply from the Unread screen now sends instead of silently failing.\r\n- Repeater anon reply with a malformed return path now floods (safe fallback) instead of emitting a corrupt direct packet.\r\n- Header-error frames now counted as receive errors (and no more zombie packet receptions triggered)\r\n- Airtime/LDRO estimate fixed to track the driver across every SF/BW.\r\n- RNG seed derivation hardened against hash failure.\r\n\r\nInternals\r\n\r\n- Crypto: orlp/ed25519 → Monocypher 4.0.2 — audited, single-file. Existing identities load/sign/verify unchanged — no re-key, no migration, full wire compatibility.\r\n- Bumped west / pinned Zephyr tree.\r\n- Synced with vanilla MeshCore dev.\r\n- Split RepeaterMesh into Uplink + RegionCLI; deduped app-layer response/telemetry/JSON builders.\r\n- Simplified the packet manager, dispatcher, and radio config paths.", "notesHtml": "(Re-Released because of native linux bugfixes)
\nNew
\nBug Fixes
\nInternals
\nSecurity
\nBug Fixes
\nNew
\nWio 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.
\nHeltec T114 board support (thanks @Calvario) — with and without screen.
\nPSRAM activation on capable devices — enables OTA on boards that support it.
\nSync with vanilla MeshCore dev
\nBug Fixes\nBLE disabled state now correctly honoured — watchdog was silently re-enabling BLE on every housekeeping tick\nFixed out-of-bounds read in path-decoding (BLE + LoRa-anon paths)\nNull-termination fix in Add/Update Contact command\nFixed overflow frame being clobbered under BLE congestion\nFixed T114 long press\nSeveral BLE audit hardening fixes (error codes, length checks, buffer sizing)
\n" }, { "version": "v20260514.205836", "name": "Firmware v20260514.205836", "datetime": "2026-05-14T20:58:46Z", "url": "https://github.com/liquidraver/ZephCore/releases/tag/v20260514.205836", "prerelease": false, "notes": "- 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.\r\n- 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.\r\n- updated default prefs to advert less and loop detect moderate", "notesHtml": "In one of my ravings trying to shorten rx-rx and tx-rx path I accidentally disabled hardware CAD.\nThis release just does that: re-enables it.
\nAlso added formatters for nRF here: https://github.com/liquidraver/ZephCore/tree/master/formatter
\nHardware CAD test:
\nNothing catched in that 2 symbol CAD check:
\nsx126x_irq_work_handler: IRQ status: 0x0080\nsx126x_irq_work_handler: CAD done: free\nsx126x_irq_work_handler: IRQ status: 0x0001\nsx126x_handle_irq_tx_done: TX done\nlora_radio_base: TX complete, RX restarted
\nSomething was in our channel during CAD check:
\nsx126x_irq_work_handler: IRQ status: 0x0180←[0m\nsx126x_irq_work_handler: CAD done: activity←[0m\nsx126x_lora_send_async: LBT: channel busy←[0m\nlora_radio_base: hwSendAsync failed: -16←[0m\nzephcore_dispatcher: checkSend: startSendRaw failed! re-queuing delay=240\n....same goes on for 3-4 times\nthen:\nsx126x_irq_work_handler: IRQ status: 0x0080\nsx126x_irq_work_handler: CAD done: free\nsx126x_irq_work_handler: IRQ status: 0x0001\nsx126x_handle_irq_tx_done: TX done\nlora_radio_base: TX complete, RX restarted
\n" }, { "version": "v20260506.102120", "name": "Firmware v20260506.102120", "datetime": "2026-05-06T10:21:30Z", "url": "https://github.com/liquidraver/ZephCore/releases/tag/v20260506.102120", "prerelease": false, "notes": "- Duty cycling is now disabled by default. \r\n 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\r\n\r\n- SX driver had some serious issues with CAD so it is recommended to update to this version as soon as possible\r\n\r\n- GPS will not be disabled if no GNSS message comes in (on repeaters), that was a test-code that stuck", "notesHtml": "Duty cycling is now disabled by default. \nFurther 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
\nSX driver had some serious issues with CAD so it is recommended to update to this version as soon as possible
\nGPS will not be disabled if no GNSS message comes in (on repeaters), that was a test-code that stuck
\nKistarcsa-edition
\nTested 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.
\n