{ "schemaVersion": 3, "generatedAt": "2026-06-21T10:28:38.575Z", "counts": { "firmwares": 20, "devices": 97, "vendors": 23, "compatibility": 2 }, "firmwares": [ { "id": "meshcore-official", "name": "MeshCore (Official)", "type": "official", "maintainer": "meshcore-dev (community project, originated by Scott Powell / ripplebiz)", "maintainers": [ { "name": "meshcore-dev", "url": "https://github.com/meshcore-dev" }, { "name": "Scott Powell" }, { "name": "ripplebiz", "url": "https://github.com/ripplebiz" } ], "description": "The official MeshCore firmware — a lightweight C++ library and firmware for multi-hop packet routing over LoRa radios. It powers decentralized, self-healing mesh networks for off-grid, emergency and tactical communication, with prebuilt images and a web flasher.\n", "repository": "https://github.com/meshcore-dev/MeshCore", "website": "https://meshcore.io", "license": "MIT", "changelog": { "source": "script", "script": "fetch-changelog.js" }, "status": "active", "lifecycle": "active", "maturity": "stable", "distribution": "official", "lineage": { "kind": "upstream" }, "runtime": { "framework": "arduino", "language": "cpp" }, "roles": [ "companion", "repeater", "room-server", "sensor" ], "features": [ "Multi-hop packet routing", "End-to-end encrypted DMs", "BLE / USB / TCP companion clients", "Web, iOS, Android, Python & NodeJS clients", "Native flood-advert traffic management (1.16+)", "Web-based flasher" ], "capabilities": { "protocol": { "meshcoreCompatible": true, "rawPacketSend": true, "rawPacketObserve": true }, "transports": { "ble": true, "usbSerial": true, "nativeTcp": true, "wifiAp": true }, "operations": { "webFlasher": true, "ota": true, "bleDfu": true, "configurationBackup": true }, "networking": { "repeater": true, "roomServer": true, "observer": false, "mqtt": false, "kissModem": true }, "hardware": { "gps": true, "display": true, "sensors": true, "lowPowerRx": true } }, "devices": [ { "id": "ebyte-eora-s3", "status": "supported", "target": "ebyte_eora_s3", "platformio_board": "ebyte_eora-s3" }, { "id": "gatiot-gat562-30s", "status": "supported", "target": "gat562_30s_mesh_kit", "platformio_board": "rak4631" }, { "id": "gatiot-gat562-evb-pro", "status": "supported", "target": "gat562_mesh_evb_pro", "platformio_board": "rak4631" }, { "id": "gatiot-gat562", "status": "supported", "target": "gat562_mesh_tracker_pro", "platformio_board": "rak4631" }, { "id": "gatiot-gat562-tracker-pro", "status": "supported", "target": "gat562_mesh_tracker_pro", "platformio_board": "rak4631" }, { "id": "gatiot-gat562-watch13", "status": "supported", "target": "gat562_mesh_watch13", "platformio_board": "rak4631" }, { "id": "generic-e22", "status": "supported", "target": "generic-e22", "platformio_board": "esp32doit-devkit-v1" }, { "id": "generic-espnow", "status": "supported", "target": "generic_espnow", "platformio_board": "esp32-c3-devkitm-1" }, { "id": "heltec-ct62", "status": "supported", "target": "heltec_ct62", "platformio_board": "esp32-c3-devkitm-1" }, { "id": "heltec-e213", "status": "supported", "target": "heltec_e213", "platformio_board": "heltec_e213" }, { "id": "heltec-e290", "status": "supported", "target": "heltec_e290", "platformio_board": "heltec_e290" }, { "id": "heltec-mesh-solar", "status": "supported", "target": "heltec_mesh_solar", "platformio_board": "heltec_mesh_solar" }, { "id": "heltec-t096", "status": "supported", "target": "heltec_t096", "platformio_board": "heltec_t096" }, { "id": "heltec-t1", "status": "supported", "target": "heltec_t1", "platformio_board": "heltec_t1" }, { "id": "heltec-t114", "status": "supported", "target": "heltec_t114", "platformio_board": "heltec_t114" }, { "id": "heltec-t190", "status": "supported", "target": "heltec_t190", "platformio_board": "heltec_t190" }, { "id": "heltec-wt3", "status": "supported", "target": "heltec_tracker", "platformio_board": "esp32-s3-devkitc-1" }, { "id": "heltec-wt2", "status": "supported", "target": "heltec_tracker_v2", "platformio_board": "heltec_tracker_v2" }, { "id": "heltec-v2", "status": "supported", "target": "heltec_v2", "platformio_board": "heltec_wifi_lora_32_V2" }, { "id": "heltec-v3", "status": "supported", "target": "heltec_v3", "platformio_board": "esp32-s3-devkitc-1" }, { "id": "heltec-wsl3", "status": "supported", "target": "heltec_v3", "platformio_board": "esp32-s3-devkitc-1" }, { "id": "heltec-v4", "status": "supported", "target": "heltec_v4", "platformio_board": "heltec_v4" }, { "id": "heltec-v4-exp", "status": "supported", "target": "heltec_v4", "platformio_board": "heltec_v4" }, { "id": "heltec-paper", "status": "supported", "target": "heltec_wireless_paper", "platformio_board": "esp32-s3-devkitc-1" }, { "id": "ikoka-handheld", "status": "supported", "target": "ikoka_handheld_nrf", "platformio_board": "seeed-xiao-afruitnrf52-nrf52840" }, { "id": "ikoka-nano", "status": "supported", "target": "ikoka_nano_nrf", "platformio_board": "seeed-xiao-afruitnrf52-nrf52840" }, { "id": "ikoka-stick", "status": "supported", "target": "ikoka_stick_nrf", "platformio_board": "seeed-xiao-afruitnrf52-nrf52840" }, { "id": "keepteen-lt1", "status": "supported", "target": "keepteen_lt1", "platformio_board": "keepteen_lt1" }, { "id": "lilygo-t3-s3-sx126x", "status": "supported", "target": "lilygo_t3s3", "platformio_board": "t3_s3_v1_x" }, { "id": "lilygo-t3-s3-sx127x", "status": "supported", "target": "lilygo_t3s3_sx1276", "platformio_board": "t3_s3_v1_x" }, { "id": "lilygo-t-impulse-plus", "status": "supported", "target": "lilygo_t_impulse_plus", "platformio_board": "lilygo_t_impulse_plus_nrf52840" }, { "id": "lilygo-tbeam-1w", "status": "supported", "target": "lilygo_tbeam_1w", "platformio_board": "t_beam_1w" }, { "id": "lilygo-t-beam-sx1262", "status": "supported", "target": "lilygo_tbeam_SX1262", "platformio_board": "ttgo-t-beam" }, { "id": "lilygo-t-beam-1-2-sx1276", "status": "supported", "target": "lilygo_tbeam_SX1276", "platformio_board": "ttgo-t-beam" }, { "id": "lilygo-tbeam-supreme", "status": "supported", "target": "lilygo_tbeam_supreme_SX1262", "platformio_board": "t_beams3_supreme" }, { "id": "lilygo-t-deck-community", "status": "supported", "target": "lilygo_tdeck", "platformio_board": "t-deck" }, { "id": "lilygo-t-deck", "status": "supported", "target": "lilygo_tdeck", "platformio_board": "t-deck" }, { "id": "lilygo-techo", "status": "supported", "target": "lilygo_techo", "platformio_board": "t-echo" }, { "id": "lilygo-techo-card", "status": "supported", "target": "lilygo_techo_card", "platformio_board": "t-echo" }, { "id": "lilygo-techo-lite", "status": "supported", "target": "lilygo_techo_lite", "platformio_board": "t-echo" }, { "id": "lilygo-teth-elite", "status": "supported", "target": "lilygo_teth_elite", "platformio_board": "esp32s3box" }, { "id": "lilygo-tlora-c6", "status": "supported", "target": "lilygo_tlora_c6", "platformio_board": "esp32-c6-devkitm-1" }, { "id": "lilygo-tlora-1-6", "status": "supported", "target": "lilygo_tlora_v2_1", "platformio_board": "ttgo-lora32-v1" }, { "id": "m5stack-unit-c6l", "status": "supported", "target": "m5stack_unit_c6l", "platformio_board": "esp32-c6-devkitm-1" }, { "id": "heltec-meshpocket", "status": "supported", "target": "mesh_pocket", "platformio_board": "heltec_mesh_pocket" }, { "id": "meshadventurer", "status": "supported", "target": "meshadventurer", "platformio_board": "esp32doit-devkit-v1" }, { "id": "meshtiny", "status": "supported", "target": "meshtiny", "platformio_board": "meshtiny" }, { "id": "minewsemi-me25ls01", "status": "supported", "target": "minewsemi_me25ls01", "platformio_board": "minewsemi_me25ls01" }, { "id": "muziworks-r1-neo", "status": "supported", "target": "muziworks_r1_neo", "platformio_board": "rak4631" }, { "id": "nano-g2", "status": "supported", "target": "nano_g2_ultra", "platformio_board": "nano-g2-ultra" }, { "id": "nibble-screen-connect", "status": "supported", "target": "nibble_screen_connect", "platformio_board": "esp32-s3-zero" }, { "id": "faketec", "status": "supported", "target": "promicro", "platformio_board": "promicro_nrf52840" }, { "id": "rak-11310", "status": "supported", "target": "rak11310", "platformio_board": "rakwireless_rak11300" }, { "id": "rak-3112", "status": "supported", "target": "rak3112", "platformio_board": "esp32-s3-devkitc-1" }, { "id": "rak-13302", "status": "supported", "target": "rak3401", "platformio_board": "rak3401" }, { "id": "rak-3x72", "status": "supported", "target": "rak3x72", "platformio_board": "rak3172" }, { "id": "rak-4631", "status": "supported", "target": "rak4631", "platformio_board": "rak4631" }, { "id": "rak-wismesh-tag", "status": "supported", "target": "rak_wismesh_tag", "platformio_board": "rak4631" }, { "id": "rpi-picow", "status": "supported", "target": "rpi_picow", "platformio_board": "rpipicow" }, { "id": "sensecap-indicator-espnow", "status": "supported", "target": "sensecap_indicator-espnow", "platformio_board": "esp32-s3-devkitc-1" }, { "id": "sensecap-solar-p1", "status": "supported", "target": "sensecap_solar", "platformio_board": "seeed_sensecap_solar" }, { "id": "sensecap-solar-p1-pro", "status": "supported", "target": "sensecap_solar", "platformio_board": "seeed_sensecap_solar" }, { "id": "station-g2", "status": "supported", "target": "station_g2", "platformio_board": "station-g2" }, { "id": "station-g3", "status": "supported", "target": "station_g3_esp32", "platformio_board": "station-g3-esp32" }, { "id": "sensecap-t1000e", "status": "supported", "target": "t1000-e", "platformio_board": "tracker-t1000-e" }, { "id": "tenstar-c3", "status": "supported", "target": "tenstar_c3", "platformio_board": "esp32-c3-devkitm-1" }, { "id": "thinknode-m1", "status": "supported", "target": "thinknode_m1", "platformio_board": "thinknode_m1" }, { "id": "thinknode-m2", "status": "supported", "target": "thinknode_m2", "platformio_board": "ESP32-S3-WROOM-1-N4" }, { "id": "thinknode-m3", "status": "supported", "target": "thinknode_m3", "platformio_board": "thinknode_m3" }, { "id": "thinknode-m5", "status": "supported", "target": "thinknode_m5", "platformio_board": "ESP32-S3-WROOM-1-N4" }, { "id": "thinknode-m6", "status": "supported", "target": "thinknode_m6", "platformio_board": "thinknode_m6" }, { "id": "tiny-relay", "status": "supported", "target": "tiny_relay", "platformio_board": "tiny_relay" }, { "id": "uart-solar-node-station", "status": "supported", "target": "rak4631", "platformio_board": "rak4631" }, { "id": "waveshare-rp2040-lora", "status": "supported", "target": "waveshare_rp2040_lora", "platformio_board": "pico" }, { "id": "wio-e5-dev", "status": "supported", "target": "wio-e5-dev", "platformio_board": "lora_e5_dev_board" }, { "id": "wio-e5-mini", "status": "supported", "target": "wio-e5-mini", "platformio_board": "lora_e5_mini" }, { "id": "wio-tracker-l1", "status": "supported", "target": "wio-tracker-l1", "platformio_board": "seeed-wio-tracker-l1" }, { "id": "wio-tracker-l1-pro", "status": "supported", "target": "wio-tracker-l1", "platformio_board": "seeed-wio-tracker-l1" }, { "id": "wio-tracker-l1-eink", "status": "supported", "target": "wio-tracker-l1-eink", "platformio_board": "seeed-wio-tracker-l1" }, { "id": "wio-wm1110", "status": "supported", "target": "wio_wm1110", "platformio_board": "seeed-xiao-afruitnrf52-nrf52840" }, { "id": "xiao-esp32c3", "status": "supported", "target": "xiao_c3", "platformio_board": "seeed_xiao_esp32c3" }, { "id": "xiao-esp32c6", "status": "supported", "target": "xiao_c6", "platformio_board": "esp32-c6-devkitm-1" }, { "id": "xiao-nrf52", "status": "supported", "target": "xiao_nrf52", "platformio_board": "seeed-xiao-afruitnrf52-nrf52840" }, { "id": "xiao-rp2040", "status": "supported", "target": "xiao_rp2040", "platformio_board": "seeed_xiao_rp2040" }, { "id": "xiao-esp32s3-plain", "status": "supported", "target": "xiao_s3", "platformio_board": "seeed_xiao_esp32s3" }, { "id": "xiao-esp32s3", "status": "supported", "target": "xiao_s3_wio", "platformio_board": "seeed_xiao_esp32s3" }, { "id": "lilygo-tdeck-pro", "status": "supported" }, { "id": "lilygo-t5-pro", "status": "supported" }, { "id": "lilygo-tdisplay", "status": "supported" }, { "id": "lilygo-pager", "status": "supported" }, { "id": "lilygo-twatch-plus", "status": "supported" }, { "id": "lilygo-twatch-s3", "status": "supported" } ], "latest_version": "1.16.0", "released": "2026-06-06", "releases": [ { "version": "room-server-v1.16.0", "name": "Room Server Firmware v1.16.0", "datetime": "2026-06-06T15:54:36Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/room-server-v1.16.0", "prerelease": false, "notes": "## Download\n\nLatest firmwares are in the [flasher.meshcore.io](https://flasher.meshcore.io/)\n\n## Change Log\n\n### New Features\n\n- New CLI config var ‘flood.max.unscoped’ [#2661](https://github.com/meshcore-dev/MeshCore/pull/2661)\n- New CLI config var ‘flood.max.advert’ [#2702](https://github.com/meshcore-dev/MeshCore/pull/2702)\n- longer preamble now for lower SF. (32 for SF<=8, 16 for SF>8) [#1954](https://github.com/meshcore-dev/MeshCore/pull/1954)\n- app/companion can now do anon\\_req/response with non-contact nodes [#2672](https://github.com/meshcore-dev/MeshCore/pull/2672)\n- companion auto-shutdown, disabled when on external power, new UI warning on display [#2663](https://github.com/meshcore-dev/MeshCore/pull/2663)\n- new ‘region def …’ CLI command [#2540](https://github.com/meshcore-dev/MeshCore/pull/2540)\n- extended ACK support [#2594](https://github.com/meshcore-dev/MeshCore/pull/2594)\n- app/companion can now compose and send raw packets [#2543](https://github.com/meshcore-dev/MeshCore/pull/2543)\n- companion can now override default scope to explicit unscoped [#2492](https://github.com/meshcore-dev/MeshCore/pull/2492)\n\n### Enhancements\n\n- All ESP repeaters, power saving improvements [#1687](https://github.com/meshcore-dev/MeshCore/pull/1687)\n- nRF companions, power saving [#2286](https://github.com/meshcore-dev/MeshCore/pull/2286)\n\n### New device support\n\n- NEW: LilyGo T-Echo Card support [#2517](https://github.com/meshcore-dev/MeshCore/pull/2517)\n- NEW: LilyGo T-Impulse Plus support [#2522](https://github.com/meshcore-dev/MeshCore/pull/2522)\n- NEW: Station G3 support [#2515](https://github.com/meshcore-dev/MeshCore/pull/2515)\n- NEW: Heltec Mesh Node T1 support [#2520](https://github.com/meshcore-dev/MeshCore/pull/2520)\n- new Xiao S3 variants (repeater, companion, etc) [#2383](https://github.com/meshcore-dev/MeshCore/pull/2383)\n\n### Bug fixes and Other\n\n- RP2040 target build fixes. [#2684](https://github.com/meshcore-dev/MeshCore/pull/2684)\n- companion protocol max frame size increase (now 176) [#2022](https://github.com/meshcore-dev/MeshCore/pull/2022)\n- RAK Wismesh Tag fixes [#2664](https://github.com/meshcore-dev/MeshCore/pull/2664)\n- Bug fix: repeater neighbor discovery fail when path.hash.mode != 0\n- RAK4631, now using Bosch driver for BME680 sensor [#2634](https://github.com/meshcore-dev/MeshCore/pull/2634)\n- enable radio.rxgain CLI command for LR1110 (T1000e) [#2235](https://github.com/meshcore-dev/MeshCore/pull/2235)\n- default flood advert interval now 47 hours (was 12) [#2608](https://github.com/meshcore-dev/MeshCore/pull/2608)\n- Client repeat (off-grid) EU freq change (from 869.0 to 869.495) [#2604](https://github.com/meshcore-dev/MeshCore/pull/2604)\n- CLI validation on rxdelay, txdelay and direct.txdelay [#2443](https://github.com/meshcore-dev/MeshCore/pull/2443)\n- Heltec T096, sensor node support [#2576](https://github.com/meshcore-dev/MeshCore/pull/2576)\n- Heltec E290 USB companion fix [#2562](https://github.com/meshcore-dev/MeshCore/pull/2562)\n- WiFi companion, reconnect logic redesigned for non-blocking [#2493](https://github.com/meshcore-dev/MeshCore/pull/2493)\n- RAM usage reduced for older boards [#2497](https://github.com/meshcore-dev/MeshCore/pull/2497)\n- nRF variants, CustomLFS lib upgrade to v2.2 [#2519](https://github.com/meshcore-dev/MeshCore/pull/2519)\n- T-Echo Lite, fixes to RXEN, TXEN and TCXO [#2511](https://github.com/meshcore-dev/MeshCore/pull/2511)\n- KISS modem frame timeout fixes [#2490](https://github.com/meshcore-dev/MeshCore/pull/2490)\n- sensor manager redesign [#2327](https://github.com/meshcore-dev/MeshCore/pull/2327)\n- startup tune suppressed if sound pref off [#2460](https://github.com/meshcore-dev/MeshCore/pull/2460)\n- added KISS Modem variants for most boards [#2620](https://github.com/meshcore-dev/MeshCore/pull/2620) [#2432](https://github.com/meshcore-dev/MeshCore/pull/2432)\n- Adafruit nRF BLE fork, to prevent lockup during rapid connect/disconnect [#2430](https://github.com/meshcore-dev/MeshCore/pull/2430)\n- RAK3401 companion, analog button support [#2436](https://github.com/meshcore-dev/MeshCore/pull/2436)\n- Heltec boards, LNA disabled by default [#2439](https://github.com/meshcore-dev/MeshCore/pull/2439)\n- new splash screens [#2424](https://github.com/meshcore-dev/MeshCore/pull/2424)\n- Sensecap Solar Tx LED fix [#2157](https://github.com/meshcore-dev/MeshCore/pull/2157)\n- new repeater variant: Heltec V4 expansion kit [#2326](https://github.com/meshcore-dev/MeshCore/pull/2326)\n- new T-Echo Lite non-shell companion variants [#2503](https://github.com/meshcore-dev/MeshCore/pull/2503) [#2353](https://github.com/meshcore-dev/MeshCore/pull/2353)\n- T-Echo Lite, battery measure fix [#2287](https://github.com/meshcore-dev/MeshCore/pull/2287)\n- RAK4631, sx1262 reset pin fix [#2008](https://github.com/meshcore-dev/MeshCore/pull/2008)\n- Heltec T096, Wireless Tracker: FEM/LNA enable by default [#2340](https://github.com/meshcore-dev/MeshCore/pull/2340)\n- R1 Neo, shutdown fix [#2371](https://github.com/meshcore-dev/MeshCore/pull/2371)\n- Heltec V4, set adc.multiplier support [#2335](https://github.com/meshcore-dev/MeshCore/pull/2335)\n\n## Limiting Unscoped Traffic\n\nThe new `flood.max.unscoped` CLI config variable is specifically for limiting unscoped flood traffic. Like `flood.max`, it drops unscoped flood packets which have already had a given number of hops. By default it is 64, which is essentially _off_.\n\n## Limiting Advert Traffic\n\nThe new `flood.max.advert` CLI config variable is specifically for limiting adverts. Like `flood.max`, it drops advert packets which have already had a given number of hops. By default it is **8**.\n\n## New Preamble\n\nWhen using the lower Spreading Factors, the radio has less time to _lock onto_ an incoming packet, so this change gives the faster SF’s a longer preamble, and thus decreasing the chance of the preamble being missed. For SF <= 8, the preamble is now 32 symbols.\n\n## Improved Region Discovery in Mobile App\n\nThe new companion firmware, and latest app, will be able to do ad-hoc requests to near by repeaters _without_ having to add them to contacts first. This will streamline both repeater discovery, and region discovery.\n\n## New `region def` Command\n\nDefining regions via the CLI is currently quite verbose, and the latest CLI handling introduces a new `region def...` command which has a short-hand notation for defining regions, especially ones which have deep nesting.\n\nSee the [CLI Command Reference](https://docs.meshcore.io/cli_commands/) for more details.\n\n## Extended ACK Support\n\nThe latest firmwares introduce support for ‘extended ACKs’, which are 6 bytes instead of 4. The extra bytes contain an extended attempt number, and additional random byte. This is in preparation for a later app feature which will enable much more than 4 attempts for direct messages. For now, repeaters will have to be updated first.\n\n## Companion Raw Packets\n\nThe latest companion firmwares now enable apps to compose the _full_ packet, ie. headers, path and payload. This can correspond with the existing RxLog ability, so app can do its own raw send and receive of packets.", "notesUrl": "https://blog.meshcore.io/2026/06/06/release-1-16-0", "notesHtml": "

Download

\n

Latest firmwares are in the flasher.meshcore.io

\n

Change Log

\n

New Features

\n\n

Enhancements

\n\n

New device support

\n\n

Bug fixes and Other

\n\n

Limiting Unscoped Traffic

\n

The new flood.max.unscoped CLI config variable is specifically for limiting unscoped flood traffic. Like flood.max, it drops unscoped flood packets which have already had a given number of hops. By default it is 64, which is essentially off.

\n

Limiting Advert Traffic

\n

The new flood.max.advert CLI config variable is specifically for limiting adverts. Like flood.max, it drops advert packets which have already had a given number of hops. By default it is 8.

\n

New Preamble

\n

When using the lower Spreading Factors, the radio has less time to lock onto an incoming packet, so this change gives the faster SF’s a longer preamble, and thus decreasing the chance of the preamble being missed. For SF <= 8, the preamble is now 32 symbols.

\n

Improved Region Discovery in Mobile App

\n

The new companion firmware, and latest app, will be able to do ad-hoc requests to near by repeaters without having to add them to contacts first. This will streamline both repeater discovery, and region discovery.

\n

New region def Command

\n

Defining regions via the CLI is currently quite verbose, and the latest CLI handling introduces a new region def... command which has a short-hand notation for defining regions, especially ones which have deep nesting.

\n

See the CLI Command Reference for more details.

\n

Extended ACK Support

\n

The latest firmwares introduce support for ‘extended ACKs’, which are 6 bytes instead of 4. The extra bytes contain an extended attempt number, and additional random byte. This is in preparation for a later app feature which will enable much more than 4 attempts for direct messages. For now, repeaters will have to be updated first.

\n

Companion Raw Packets

\n

The latest companion firmwares now enable apps to compose the full packet, ie. headers, path and payload. This can correspond with the existing RxLog ability, so app can do its own raw send and receive of packets.

\n" }, { "version": "repeater-v1.16.0", "name": "Repeater Firmware v1.16.0", "datetime": "2026-06-06T15:54:59Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/repeater-v1.16.0", "prerelease": false, "notes": "## Download\n\nLatest firmwares are in the [flasher.meshcore.io](https://flasher.meshcore.io/)\n\n## Change Log\n\n### New Features\n\n- New CLI config var ‘flood.max.unscoped’ [#2661](https://github.com/meshcore-dev/MeshCore/pull/2661)\n- New CLI config var ‘flood.max.advert’ [#2702](https://github.com/meshcore-dev/MeshCore/pull/2702)\n- longer preamble now for lower SF. (32 for SF<=8, 16 for SF>8) [#1954](https://github.com/meshcore-dev/MeshCore/pull/1954)\n- app/companion can now do anon\\_req/response with non-contact nodes [#2672](https://github.com/meshcore-dev/MeshCore/pull/2672)\n- companion auto-shutdown, disabled when on external power, new UI warning on display [#2663](https://github.com/meshcore-dev/MeshCore/pull/2663)\n- new ‘region def …’ CLI command [#2540](https://github.com/meshcore-dev/MeshCore/pull/2540)\n- extended ACK support [#2594](https://github.com/meshcore-dev/MeshCore/pull/2594)\n- app/companion can now compose and send raw packets [#2543](https://github.com/meshcore-dev/MeshCore/pull/2543)\n- companion can now override default scope to explicit unscoped [#2492](https://github.com/meshcore-dev/MeshCore/pull/2492)\n\n### Enhancements\n\n- All ESP repeaters, power saving improvements [#1687](https://github.com/meshcore-dev/MeshCore/pull/1687)\n- nRF companions, power saving [#2286](https://github.com/meshcore-dev/MeshCore/pull/2286)\n\n### New device support\n\n- NEW: LilyGo T-Echo Card support [#2517](https://github.com/meshcore-dev/MeshCore/pull/2517)\n- NEW: LilyGo T-Impulse Plus support [#2522](https://github.com/meshcore-dev/MeshCore/pull/2522)\n- NEW: Station G3 support [#2515](https://github.com/meshcore-dev/MeshCore/pull/2515)\n- NEW: Heltec Mesh Node T1 support [#2520](https://github.com/meshcore-dev/MeshCore/pull/2520)\n- new Xiao S3 variants (repeater, companion, etc) [#2383](https://github.com/meshcore-dev/MeshCore/pull/2383)\n\n### Bug fixes and Other\n\n- RP2040 target build fixes. [#2684](https://github.com/meshcore-dev/MeshCore/pull/2684)\n- companion protocol max frame size increase (now 176) [#2022](https://github.com/meshcore-dev/MeshCore/pull/2022)\n- RAK Wismesh Tag fixes [#2664](https://github.com/meshcore-dev/MeshCore/pull/2664)\n- Bug fix: repeater neighbor discovery fail when path.hash.mode != 0\n- RAK4631, now using Bosch driver for BME680 sensor [#2634](https://github.com/meshcore-dev/MeshCore/pull/2634)\n- enable radio.rxgain CLI command for LR1110 (T1000e) [#2235](https://github.com/meshcore-dev/MeshCore/pull/2235)\n- default flood advert interval now 47 hours (was 12) [#2608](https://github.com/meshcore-dev/MeshCore/pull/2608)\n- Client repeat (off-grid) EU freq change (from 869.0 to 869.495) [#2604](https://github.com/meshcore-dev/MeshCore/pull/2604)\n- CLI validation on rxdelay, txdelay and direct.txdelay [#2443](https://github.com/meshcore-dev/MeshCore/pull/2443)\n- Heltec T096, sensor node support [#2576](https://github.com/meshcore-dev/MeshCore/pull/2576)\n- Heltec E290 USB companion fix [#2562](https://github.com/meshcore-dev/MeshCore/pull/2562)\n- WiFi companion, reconnect logic redesigned for non-blocking [#2493](https://github.com/meshcore-dev/MeshCore/pull/2493)\n- RAM usage reduced for older boards [#2497](https://github.com/meshcore-dev/MeshCore/pull/2497)\n- nRF variants, CustomLFS lib upgrade to v2.2 [#2519](https://github.com/meshcore-dev/MeshCore/pull/2519)\n- T-Echo Lite, fixes to RXEN, TXEN and TCXO [#2511](https://github.com/meshcore-dev/MeshCore/pull/2511)\n- KISS modem frame timeout fixes [#2490](https://github.com/meshcore-dev/MeshCore/pull/2490)\n- sensor manager redesign [#2327](https://github.com/meshcore-dev/MeshCore/pull/2327)\n- startup tune suppressed if sound pref off [#2460](https://github.com/meshcore-dev/MeshCore/pull/2460)\n- added KISS Modem variants for most boards [#2620](https://github.com/meshcore-dev/MeshCore/pull/2620) [#2432](https://github.com/meshcore-dev/MeshCore/pull/2432)\n- Adafruit nRF BLE fork, to prevent lockup during rapid connect/disconnect [#2430](https://github.com/meshcore-dev/MeshCore/pull/2430)\n- RAK3401 companion, analog button support [#2436](https://github.com/meshcore-dev/MeshCore/pull/2436)\n- Heltec boards, LNA disabled by default [#2439](https://github.com/meshcore-dev/MeshCore/pull/2439)\n- new splash screens [#2424](https://github.com/meshcore-dev/MeshCore/pull/2424)\n- Sensecap Solar Tx LED fix [#2157](https://github.com/meshcore-dev/MeshCore/pull/2157)\n- new repeater variant: Heltec V4 expansion kit [#2326](https://github.com/meshcore-dev/MeshCore/pull/2326)\n- new T-Echo Lite non-shell companion variants [#2503](https://github.com/meshcore-dev/MeshCore/pull/2503) [#2353](https://github.com/meshcore-dev/MeshCore/pull/2353)\n- T-Echo Lite, battery measure fix [#2287](https://github.com/meshcore-dev/MeshCore/pull/2287)\n- RAK4631, sx1262 reset pin fix [#2008](https://github.com/meshcore-dev/MeshCore/pull/2008)\n- Heltec T096, Wireless Tracker: FEM/LNA enable by default [#2340](https://github.com/meshcore-dev/MeshCore/pull/2340)\n- R1 Neo, shutdown fix [#2371](https://github.com/meshcore-dev/MeshCore/pull/2371)\n- Heltec V4, set adc.multiplier support [#2335](https://github.com/meshcore-dev/MeshCore/pull/2335)\n\n## Limiting Unscoped Traffic\n\nThe new `flood.max.unscoped` CLI config variable is specifically for limiting unscoped flood traffic. Like `flood.max`, it drops unscoped flood packets which have already had a given number of hops. By default it is 64, which is essentially _off_.\n\n## Limiting Advert Traffic\n\nThe new `flood.max.advert` CLI config variable is specifically for limiting adverts. Like `flood.max`, it drops advert packets which have already had a given number of hops. By default it is **8**.\n\n## New Preamble\n\nWhen using the lower Spreading Factors, the radio has less time to _lock onto_ an incoming packet, so this change gives the faster SF’s a longer preamble, and thus decreasing the chance of the preamble being missed. For SF <= 8, the preamble is now 32 symbols.\n\n## Improved Region Discovery in Mobile App\n\nThe new companion firmware, and latest app, will be able to do ad-hoc requests to near by repeaters _without_ having to add them to contacts first. This will streamline both repeater discovery, and region discovery.\n\n## New `region def` Command\n\nDefining regions via the CLI is currently quite verbose, and the latest CLI handling introduces a new `region def...` command which has a short-hand notation for defining regions, especially ones which have deep nesting.\n\nSee the [CLI Command Reference](https://docs.meshcore.io/cli_commands/) for more details.\n\n## Extended ACK Support\n\nThe latest firmwares introduce support for ‘extended ACKs’, which are 6 bytes instead of 4. The extra bytes contain an extended attempt number, and additional random byte. This is in preparation for a later app feature which will enable much more than 4 attempts for direct messages. For now, repeaters will have to be updated first.\n\n## Companion Raw Packets\n\nThe latest companion firmwares now enable apps to compose the _full_ packet, ie. headers, path and payload. This can correspond with the existing RxLog ability, so app can do its own raw send and receive of packets.", "notesUrl": "https://blog.meshcore.io/2026/06/06/release-1-16-0", "notesHtml": "

Download

\n

Latest firmwares are in the flasher.meshcore.io

\n

Change Log

\n

New Features

\n\n

Enhancements

\n\n

New device support

\n\n

Bug fixes and Other

\n\n

Limiting Unscoped Traffic

\n

The new flood.max.unscoped CLI config variable is specifically for limiting unscoped flood traffic. Like flood.max, it drops unscoped flood packets which have already had a given number of hops. By default it is 64, which is essentially off.

\n

Limiting Advert Traffic

\n

The new flood.max.advert CLI config variable is specifically for limiting adverts. Like flood.max, it drops advert packets which have already had a given number of hops. By default it is 8.

\n

New Preamble

\n

When using the lower Spreading Factors, the radio has less time to lock onto an incoming packet, so this change gives the faster SF’s a longer preamble, and thus decreasing the chance of the preamble being missed. For SF <= 8, the preamble is now 32 symbols.

\n

Improved Region Discovery in Mobile App

\n

The new companion firmware, and latest app, will be able to do ad-hoc requests to near by repeaters without having to add them to contacts first. This will streamline both repeater discovery, and region discovery.

\n

New region def Command

\n

Defining regions via the CLI is currently quite verbose, and the latest CLI handling introduces a new region def... command which has a short-hand notation for defining regions, especially ones which have deep nesting.

\n

See the CLI Command Reference for more details.

\n

Extended ACK Support

\n

The latest firmwares introduce support for ‘extended ACKs’, which are 6 bytes instead of 4. The extra bytes contain an extended attempt number, and additional random byte. This is in preparation for a later app feature which will enable much more than 4 attempts for direct messages. For now, repeaters will have to be updated first.

\n

Companion Raw Packets

\n

The latest companion firmwares now enable apps to compose the full packet, ie. headers, path and payload. This can correspond with the existing RxLog ability, so app can do its own raw send and receive of packets.

\n" }, { "version": "companion-v1.16.0", "name": "Companion Firmware v1.16.0", "datetime": "2026-06-06T15:55:20Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/companion-v1.16.0", "prerelease": false, "notes": "## Download\n\nLatest firmwares are in the [flasher.meshcore.io](https://flasher.meshcore.io/)\n\n## Change Log\n\n### New Features\n\n- New CLI config var ‘flood.max.unscoped’ [#2661](https://github.com/meshcore-dev/MeshCore/pull/2661)\n- New CLI config var ‘flood.max.advert’ [#2702](https://github.com/meshcore-dev/MeshCore/pull/2702)\n- longer preamble now for lower SF. (32 for SF<=8, 16 for SF>8) [#1954](https://github.com/meshcore-dev/MeshCore/pull/1954)\n- app/companion can now do anon\\_req/response with non-contact nodes [#2672](https://github.com/meshcore-dev/MeshCore/pull/2672)\n- companion auto-shutdown, disabled when on external power, new UI warning on display [#2663](https://github.com/meshcore-dev/MeshCore/pull/2663)\n- new ‘region def …’ CLI command [#2540](https://github.com/meshcore-dev/MeshCore/pull/2540)\n- extended ACK support [#2594](https://github.com/meshcore-dev/MeshCore/pull/2594)\n- app/companion can now compose and send raw packets [#2543](https://github.com/meshcore-dev/MeshCore/pull/2543)\n- companion can now override default scope to explicit unscoped [#2492](https://github.com/meshcore-dev/MeshCore/pull/2492)\n\n### Enhancements\n\n- All ESP repeaters, power saving improvements [#1687](https://github.com/meshcore-dev/MeshCore/pull/1687)\n- nRF companions, power saving [#2286](https://github.com/meshcore-dev/MeshCore/pull/2286)\n\n### New device support\n\n- NEW: LilyGo T-Echo Card support [#2517](https://github.com/meshcore-dev/MeshCore/pull/2517)\n- NEW: LilyGo T-Impulse Plus support [#2522](https://github.com/meshcore-dev/MeshCore/pull/2522)\n- NEW: Station G3 support [#2515](https://github.com/meshcore-dev/MeshCore/pull/2515)\n- NEW: Heltec Mesh Node T1 support [#2520](https://github.com/meshcore-dev/MeshCore/pull/2520)\n- new Xiao S3 variants (repeater, companion, etc) [#2383](https://github.com/meshcore-dev/MeshCore/pull/2383)\n\n### Bug fixes and Other\n\n- RP2040 target build fixes. [#2684](https://github.com/meshcore-dev/MeshCore/pull/2684)\n- companion protocol max frame size increase (now 176) [#2022](https://github.com/meshcore-dev/MeshCore/pull/2022)\n- RAK Wismesh Tag fixes [#2664](https://github.com/meshcore-dev/MeshCore/pull/2664)\n- Bug fix: repeater neighbor discovery fail when path.hash.mode != 0\n- RAK4631, now using Bosch driver for BME680 sensor [#2634](https://github.com/meshcore-dev/MeshCore/pull/2634)\n- enable radio.rxgain CLI command for LR1110 (T1000e) [#2235](https://github.com/meshcore-dev/MeshCore/pull/2235)\n- default flood advert interval now 47 hours (was 12) [#2608](https://github.com/meshcore-dev/MeshCore/pull/2608)\n- Client repeat (off-grid) EU freq change (from 869.0 to 869.495) [#2604](https://github.com/meshcore-dev/MeshCore/pull/2604)\n- CLI validation on rxdelay, txdelay and direct.txdelay [#2443](https://github.com/meshcore-dev/MeshCore/pull/2443)\n- Heltec T096, sensor node support [#2576](https://github.com/meshcore-dev/MeshCore/pull/2576)\n- Heltec E290 USB companion fix [#2562](https://github.com/meshcore-dev/MeshCore/pull/2562)\n- WiFi companion, reconnect logic redesigned for non-blocking [#2493](https://github.com/meshcore-dev/MeshCore/pull/2493)\n- RAM usage reduced for older boards [#2497](https://github.com/meshcore-dev/MeshCore/pull/2497)\n- nRF variants, CustomLFS lib upgrade to v2.2 [#2519](https://github.com/meshcore-dev/MeshCore/pull/2519)\n- T-Echo Lite, fixes to RXEN, TXEN and TCXO [#2511](https://github.com/meshcore-dev/MeshCore/pull/2511)\n- KISS modem frame timeout fixes [#2490](https://github.com/meshcore-dev/MeshCore/pull/2490)\n- sensor manager redesign [#2327](https://github.com/meshcore-dev/MeshCore/pull/2327)\n- startup tune suppressed if sound pref off [#2460](https://github.com/meshcore-dev/MeshCore/pull/2460)\n- added KISS Modem variants for most boards [#2620](https://github.com/meshcore-dev/MeshCore/pull/2620) [#2432](https://github.com/meshcore-dev/MeshCore/pull/2432)\n- Adafruit nRF BLE fork, to prevent lockup during rapid connect/disconnect [#2430](https://github.com/meshcore-dev/MeshCore/pull/2430)\n- RAK3401 companion, analog button support [#2436](https://github.com/meshcore-dev/MeshCore/pull/2436)\n- Heltec boards, LNA disabled by default [#2439](https://github.com/meshcore-dev/MeshCore/pull/2439)\n- new splash screens [#2424](https://github.com/meshcore-dev/MeshCore/pull/2424)\n- Sensecap Solar Tx LED fix [#2157](https://github.com/meshcore-dev/MeshCore/pull/2157)\n- new repeater variant: Heltec V4 expansion kit [#2326](https://github.com/meshcore-dev/MeshCore/pull/2326)\n- new T-Echo Lite non-shell companion variants [#2503](https://github.com/meshcore-dev/MeshCore/pull/2503) [#2353](https://github.com/meshcore-dev/MeshCore/pull/2353)\n- T-Echo Lite, battery measure fix [#2287](https://github.com/meshcore-dev/MeshCore/pull/2287)\n- RAK4631, sx1262 reset pin fix [#2008](https://github.com/meshcore-dev/MeshCore/pull/2008)\n- Heltec T096, Wireless Tracker: FEM/LNA enable by default [#2340](https://github.com/meshcore-dev/MeshCore/pull/2340)\n- R1 Neo, shutdown fix [#2371](https://github.com/meshcore-dev/MeshCore/pull/2371)\n- Heltec V4, set adc.multiplier support [#2335](https://github.com/meshcore-dev/MeshCore/pull/2335)\n\n## Limiting Unscoped Traffic\n\nThe new `flood.max.unscoped` CLI config variable is specifically for limiting unscoped flood traffic. Like `flood.max`, it drops unscoped flood packets which have already had a given number of hops. By default it is 64, which is essentially _off_.\n\n## Limiting Advert Traffic\n\nThe new `flood.max.advert` CLI config variable is specifically for limiting adverts. Like `flood.max`, it drops advert packets which have already had a given number of hops. By default it is **8**.\n\n## New Preamble\n\nWhen using the lower Spreading Factors, the radio has less time to _lock onto_ an incoming packet, so this change gives the faster SF’s a longer preamble, and thus decreasing the chance of the preamble being missed. For SF <= 8, the preamble is now 32 symbols.\n\n## Improved Region Discovery in Mobile App\n\nThe new companion firmware, and latest app, will be able to do ad-hoc requests to near by repeaters _without_ having to add them to contacts first. This will streamline both repeater discovery, and region discovery.\n\n## New `region def` Command\n\nDefining regions via the CLI is currently quite verbose, and the latest CLI handling introduces a new `region def...` command which has a short-hand notation for defining regions, especially ones which have deep nesting.\n\nSee the [CLI Command Reference](https://docs.meshcore.io/cli_commands/) for more details.\n\n## Extended ACK Support\n\nThe latest firmwares introduce support for ‘extended ACKs’, which are 6 bytes instead of 4. The extra bytes contain an extended attempt number, and additional random byte. This is in preparation for a later app feature which will enable much more than 4 attempts for direct messages. For now, repeaters will have to be updated first.\n\n## Companion Raw Packets\n\nThe latest companion firmwares now enable apps to compose the _full_ packet, ie. headers, path and payload. This can correspond with the existing RxLog ability, so app can do its own raw send and receive of packets.", "notesUrl": "https://blog.meshcore.io/2026/06/06/release-1-16-0", "notesHtml": "

Download

\n

Latest firmwares are in the flasher.meshcore.io

\n

Change Log

\n

New Features

\n\n

Enhancements

\n\n

New device support

\n\n

Bug fixes and Other

\n\n

Limiting Unscoped Traffic

\n

The new flood.max.unscoped CLI config variable is specifically for limiting unscoped flood traffic. Like flood.max, it drops unscoped flood packets which have already had a given number of hops. By default it is 64, which is essentially off.

\n

Limiting Advert Traffic

\n

The new flood.max.advert CLI config variable is specifically for limiting adverts. Like flood.max, it drops advert packets which have already had a given number of hops. By default it is 8.

\n

New Preamble

\n

When using the lower Spreading Factors, the radio has less time to lock onto an incoming packet, so this change gives the faster SF’s a longer preamble, and thus decreasing the chance of the preamble being missed. For SF <= 8, the preamble is now 32 symbols.

\n

Improved Region Discovery in Mobile App

\n

The new companion firmware, and latest app, will be able to do ad-hoc requests to near by repeaters without having to add them to contacts first. This will streamline both repeater discovery, and region discovery.

\n

New region def Command

\n

Defining regions via the CLI is currently quite verbose, and the latest CLI handling introduces a new region def... command which has a short-hand notation for defining regions, especially ones which have deep nesting.

\n

See the CLI Command Reference for more details.

\n

Extended ACK Support

\n

The latest firmwares introduce support for ‘extended ACKs’, which are 6 bytes instead of 4. The extra bytes contain an extended attempt number, and additional random byte. This is in preparation for a later app feature which will enable much more than 4 attempts for direct messages. For now, repeaters will have to be updated first.

\n

Companion Raw Packets

\n

The latest companion firmwares now enable apps to compose the full packet, ie. headers, path and payload. This can correspond with the existing RxLog ability, so app can do its own raw send and receive of packets.

\n" }, { "version": "room-server-v1.15.0", "name": "Room Server Firmware v1.15.0", "datetime": "2026-04-19T03:07:54Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/room-server-v1.15.0", "prerelease": false, "notes": "**Download**\n\nLatest firmwares are in the [flasher.meshcore.io](https://flasher.meshcore.io/)\n\n**Change Log**\n\n- Default Scope support\n- Support for New GROUP\\_DATA (binary) packets [#1928](https://github.com/meshcore-dev/MeshCore/pull/1928) [#2130](https://github.com/meshcore-dev/MeshCore/pull/2130)\n- Heltec V4.3 support [#1867](https://github.com/meshcore-dev/MeshCore/pull/1867)\n- Heltec nRF Tracker (T096) support [#2097](https://github.com/meshcore-dev/MeshCore/pull/2097)\n- GAT562 Mesh EVB Pro repeater and room server support [#2042](https://github.com/meshcore-dev/MeshCore/pull/2042)\n- Radio rxgain now ON by default [#2124](https://github.com/meshcore-dev/MeshCore/pull/2124)\n- Radio freq range now supported down to 150Mhz [#2126](https://github.com/meshcore-dev/MeshCore/pull/2126)\n- GPS pref peristence fix [#2018](https://github.com/meshcore-dev/MeshCore/pull/2018)\n- New `get|set dutycycle` CLI command [#1961](https://github.com/meshcore-dev/MeshCore/pull/1961)\n- Muzi Works R1 Neo support [#2007](https://github.com/meshcore-dev/MeshCore/pull/2007)\n- GAT562 Watch support [#2138](https://github.com/meshcore-dev/MeshCore/pull/2138) [#2228](https://github.com/meshcore-dev/MeshCore/pull/2228)\n- BME680 sensor init fix [#2227](https://github.com/meshcore-dev/MeshCore/pull/2227)\n- Heltec Wireless Paper battery read fix [#2164](https://github.com/meshcore-dev/MeshCore/pull/2164)\n- WiFi companion fixes for Heltec V4,TBeam 1W [#1833](https://github.com/meshcore-dev/MeshCore/pull/1833)\n- Waveshare RP2040: RXEN fix [#2298](https://github.com/meshcore-dev/MeshCore/pull/2298)\n- nRF companion, support for OTA updates [#2323](https://github.com/meshcore-dev/MeshCore/pull/2323)\n- Added companion for Heltec Wireless Paper [#2315](https://github.com/meshcore-dev/MeshCore/pull/2315)\n- Misc [#2134](https://github.com/meshcore-dev/MeshCore/pull/2134) [#2190](https://github.com/meshcore-dev/MeshCore/pull/2190) [#1425](https://github.com/meshcore-dev/MeshCore/pull/1425) [#2075](https://github.com/meshcore-dev/MeshCore/pull/2075) [#2302](https://github.com/meshcore-dev/MeshCore/pull/2302) [#2306](https://github.com/meshcore-dev/MeshCore/pull/2306)\n- Xiao C3 bootloop fix [#2328](https://github.com/meshcore-dev/MeshCore/pull/2328)\n\n**Documentation Links**\n\nFor info on the new Default Scope feature, please see [this article](https://blog.meshcore.io/2026/04/17/default-scope).\n\nFor low level format of the GROUP\\_DATA packets, please see [this docs link](https://docs.meshcore.io/payloads/?h=group+datagram#group-datagram).", "notesUrl": "https://blog.meshcore.io/2026/04/19/release-1-15-0", "notesHtml": "

Download

\n

Latest firmwares are in the flasher.meshcore.io

\n

Change Log

\n\n

Documentation Links

\n

For info on the new Default Scope feature, please see this article.

\n

For low level format of the GROUP_DATA packets, please see this docs link.

\n" }, { "version": "repeater-v1.15.0", "name": "Repeater Firmware v1.15.0", "datetime": "2026-04-19T03:08:26Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/repeater-v1.15.0", "prerelease": false, "notes": "**Download**\n\nLatest firmwares are in the [flasher.meshcore.io](https://flasher.meshcore.io/)\n\n**Change Log**\n\n- Default Scope support\n- Support for New GROUP\\_DATA (binary) packets [#1928](https://github.com/meshcore-dev/MeshCore/pull/1928) [#2130](https://github.com/meshcore-dev/MeshCore/pull/2130)\n- Heltec V4.3 support [#1867](https://github.com/meshcore-dev/MeshCore/pull/1867)\n- Heltec nRF Tracker (T096) support [#2097](https://github.com/meshcore-dev/MeshCore/pull/2097)\n- GAT562 Mesh EVB Pro repeater and room server support [#2042](https://github.com/meshcore-dev/MeshCore/pull/2042)\n- Radio rxgain now ON by default [#2124](https://github.com/meshcore-dev/MeshCore/pull/2124)\n- Radio freq range now supported down to 150Mhz [#2126](https://github.com/meshcore-dev/MeshCore/pull/2126)\n- GPS pref peristence fix [#2018](https://github.com/meshcore-dev/MeshCore/pull/2018)\n- New `get|set dutycycle` CLI command [#1961](https://github.com/meshcore-dev/MeshCore/pull/1961)\n- Muzi Works R1 Neo support [#2007](https://github.com/meshcore-dev/MeshCore/pull/2007)\n- GAT562 Watch support [#2138](https://github.com/meshcore-dev/MeshCore/pull/2138) [#2228](https://github.com/meshcore-dev/MeshCore/pull/2228)\n- BME680 sensor init fix [#2227](https://github.com/meshcore-dev/MeshCore/pull/2227)\n- Heltec Wireless Paper battery read fix [#2164](https://github.com/meshcore-dev/MeshCore/pull/2164)\n- WiFi companion fixes for Heltec V4,TBeam 1W [#1833](https://github.com/meshcore-dev/MeshCore/pull/1833)\n- Waveshare RP2040: RXEN fix [#2298](https://github.com/meshcore-dev/MeshCore/pull/2298)\n- nRF companion, support for OTA updates [#2323](https://github.com/meshcore-dev/MeshCore/pull/2323)\n- Added companion for Heltec Wireless Paper [#2315](https://github.com/meshcore-dev/MeshCore/pull/2315)\n- Misc [#2134](https://github.com/meshcore-dev/MeshCore/pull/2134) [#2190](https://github.com/meshcore-dev/MeshCore/pull/2190) [#1425](https://github.com/meshcore-dev/MeshCore/pull/1425) [#2075](https://github.com/meshcore-dev/MeshCore/pull/2075) [#2302](https://github.com/meshcore-dev/MeshCore/pull/2302) [#2306](https://github.com/meshcore-dev/MeshCore/pull/2306)\n- Xiao C3 bootloop fix [#2328](https://github.com/meshcore-dev/MeshCore/pull/2328)\n\n**Documentation Links**\n\nFor info on the new Default Scope feature, please see [this article](https://blog.meshcore.io/2026/04/17/default-scope).\n\nFor low level format of the GROUP\\_DATA packets, please see [this docs link](https://docs.meshcore.io/payloads/?h=group+datagram#group-datagram).", "notesUrl": "https://blog.meshcore.io/2026/04/19/release-1-15-0", "notesHtml": "

Download

\n

Latest firmwares are in the flasher.meshcore.io

\n

Change Log

\n\n

Documentation Links

\n

For info on the new Default Scope feature, please see this article.

\n

For low level format of the GROUP_DATA packets, please see this docs link.

\n" }, { "version": "companion-v1.15.0", "name": "Companion Firmware v1.15.0", "datetime": "2026-04-19T06:48:14Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/companion-v1.15.0", "prerelease": false, "notes": "**Download**\n\nLatest firmwares are in the [flasher.meshcore.io](https://flasher.meshcore.io/)\n\n**Change Log**\n\n- Default Scope support\n- Support for New GROUP\\_DATA (binary) packets [#1928](https://github.com/meshcore-dev/MeshCore/pull/1928) [#2130](https://github.com/meshcore-dev/MeshCore/pull/2130)\n- Heltec V4.3 support [#1867](https://github.com/meshcore-dev/MeshCore/pull/1867)\n- Heltec nRF Tracker (T096) support [#2097](https://github.com/meshcore-dev/MeshCore/pull/2097)\n- GAT562 Mesh EVB Pro repeater and room server support [#2042](https://github.com/meshcore-dev/MeshCore/pull/2042)\n- Radio rxgain now ON by default [#2124](https://github.com/meshcore-dev/MeshCore/pull/2124)\n- Radio freq range now supported down to 150Mhz [#2126](https://github.com/meshcore-dev/MeshCore/pull/2126)\n- GPS pref peristence fix [#2018](https://github.com/meshcore-dev/MeshCore/pull/2018)\n- New `get|set dutycycle` CLI command [#1961](https://github.com/meshcore-dev/MeshCore/pull/1961)\n- Muzi Works R1 Neo support [#2007](https://github.com/meshcore-dev/MeshCore/pull/2007)\n- GAT562 Watch support [#2138](https://github.com/meshcore-dev/MeshCore/pull/2138) [#2228](https://github.com/meshcore-dev/MeshCore/pull/2228)\n- BME680 sensor init fix [#2227](https://github.com/meshcore-dev/MeshCore/pull/2227)\n- Heltec Wireless Paper battery read fix [#2164](https://github.com/meshcore-dev/MeshCore/pull/2164)\n- WiFi companion fixes for Heltec V4,TBeam 1W [#1833](https://github.com/meshcore-dev/MeshCore/pull/1833)\n- Waveshare RP2040: RXEN fix [#2298](https://github.com/meshcore-dev/MeshCore/pull/2298)\n- nRF companion, support for OTA updates [#2323](https://github.com/meshcore-dev/MeshCore/pull/2323)\n- Added companion for Heltec Wireless Paper [#2315](https://github.com/meshcore-dev/MeshCore/pull/2315)\n- Misc [#2134](https://github.com/meshcore-dev/MeshCore/pull/2134) [#2190](https://github.com/meshcore-dev/MeshCore/pull/2190) [#1425](https://github.com/meshcore-dev/MeshCore/pull/1425) [#2075](https://github.com/meshcore-dev/MeshCore/pull/2075) [#2302](https://github.com/meshcore-dev/MeshCore/pull/2302) [#2306](https://github.com/meshcore-dev/MeshCore/pull/2306)\n- Xiao C3 bootloop fix [#2328](https://github.com/meshcore-dev/MeshCore/pull/2328)\n\n**Documentation Links**\n\nFor info on the new Default Scope feature, please see [this article](https://blog.meshcore.io/2026/04/17/default-scope).\n\nFor low level format of the GROUP\\_DATA packets, please see [this docs link](https://docs.meshcore.io/payloads/?h=group+datagram#group-datagram).", "notesUrl": "https://blog.meshcore.io/2026/04/19/release-1-15-0", "notesHtml": "

Download

\n

Latest firmwares are in the flasher.meshcore.io

\n

Change Log

\n\n

Documentation Links

\n

For info on the new Default Scope feature, please see this article.

\n

For low level format of the GROUP_DATA packets, please see this docs link.

\n" }, { "version": "room-server-v1.14.1", "name": "Room Server Firmware v1.14.1", "datetime": "2026-03-20T02:54:49Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/room-server-v1.14.1", "prerelease": false, "notes": "change log:\r\nAdded GPS support for SenseCAP Solar P1 in #1589\r\nPower off switch long press support for SenseCAP Solar P1 #1871\r\nAdded nRF52 power management for RAK3401 in #1984\r\nAdded token bucket based duty cycle enforcement in #1297\r\nAdded support for new GAT562 30S Mesh Kit device in #2009\r\nAdded support for new GAT562 Mesh Tracker Pro device in #1980\r\nAdded LNA toggle CLI commands radio.rxgain on and radio.rxgain off in #1653\r\nAdded MCU temperature to telemetry responses from room servers in #2052\r\nMigrated Heltec Tracker v2 to KCT8103L in #1936\r\nNodes with GPS enabled will now auto sync time every 30 minutes in #1350\r\nFixed bug where some queued packets would not get transmit in #1877\r\nFixed bug where automatic adverts were not using the configured multibyte path setting in fcfdc5f", "notesHtml": "

change log:\nAdded GPS support for SenseCAP Solar P1 in #1589\nPower off switch long press support for SenseCAP Solar P1 #1871\nAdded nRF52 power management for RAK3401 in #1984\nAdded token bucket based duty cycle enforcement in #1297\nAdded support for new GAT562 30S Mesh Kit device in #2009\nAdded support for new GAT562 Mesh Tracker Pro device in #1980\nAdded LNA toggle CLI commands radio.rxgain on and radio.rxgain off in #1653\nAdded MCU temperature to telemetry responses from room servers in #2052\nMigrated Heltec Tracker v2 to KCT8103L in #1936\nNodes with GPS enabled will now auto sync time every 30 minutes in #1350\nFixed bug where some queued packets would not get transmit in #1877\nFixed bug where automatic adverts were not using the configured multibyte path setting in fcfdc5f

\n" }, { "version": "repeater-v1.14.1", "name": "Repeater Firmware v1.14.1", "datetime": "2026-03-20T02:55:43Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/repeater-v1.14.1", "prerelease": false, "notes": "change log:\r\nAdded GPS support for SenseCAP Solar P1 in #1589\r\nPower off switch long press support for SenseCAP Solar P1 #1871\r\nAdded nRF52 power management for RAK3401 in #1984\r\nAdded token bucket based duty cycle enforcement in #1297\r\nAdded support for new GAT562 30S Mesh Kit device in #2009\r\nAdded support for new GAT562 Mesh Tracker Pro device in #1980\r\nAdded LNA toggle CLI commands radio.rxgain on and radio.rxgain off in #1653\r\nAdded MCU temperature to telemetry responses from room servers in #2052\r\nMigrated Heltec Tracker v2 to KCT8103L in #1936\r\nNodes with GPS enabled will now auto sync time every 30 minutes in #1350\r\nFixed bug where some queued packets would not get transmit in #1877\r\nFixed bug where automatic adverts were not using the configured multibyte path setting in https://github.com/meshcore-dev/MeshCore/commit/fcfdc5fc5b1e0cf81b4ca2dfbc51d714f3eb1ead", "notesHtml": "

change log:\nAdded GPS support for SenseCAP Solar P1 in #1589\nPower off switch long press support for SenseCAP Solar P1 #1871\nAdded nRF52 power management for RAK3401 in #1984\nAdded token bucket based duty cycle enforcement in #1297\nAdded support for new GAT562 30S Mesh Kit device in #2009\nAdded support for new GAT562 Mesh Tracker Pro device in #1980\nAdded LNA toggle CLI commands radio.rxgain on and radio.rxgain off in #1653\nAdded MCU temperature to telemetry responses from room servers in #2052\nMigrated Heltec Tracker v2 to KCT8103L in #1936\nNodes with GPS enabled will now auto sync time every 30 minutes in #1350\nFixed bug where some queued packets would not get transmit in #1877\nFixed bug where automatic adverts were not using the configured multibyte path setting in https://github.com/meshcore-dev/MeshCore/commit/fcfdc5fc5b1e0cf81b4ca2dfbc51d714f3eb1ead

\n" }, { "version": "companion-v1.14.1", "name": "Companion Firmware v1.14.1", "datetime": "2026-03-20T03:53:00Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/companion-v1.14.1", "prerelease": false, "notes": "change log:\r\nAdded GPS support for SenseCAP Solar P1 in #1589\r\nAdded nRF52 power management for RAK3401 in #1984\r\nAdded token bucket based duty cycle enforcement in #1297\r\nAdded support for new GAT562 30S Mesh Kit device in #2009\r\nAdded support for new GAT562 Mesh Tracker Pro device in #1980\r\nAdded LNA toggle CLI commands radio.rxgain on and radio.rxgain off in #1653\r\nAdded MCU temperature to telemetry responses from room servers in #2052\r\nMigrated Heltec Tracker v2 to KCT8103L in #1936\r\nFixed bug where some queued packets would not get transmit in #1877\r\nFixed bug where BLE would stay on if turned off from companion screen when already connected in #1991", "notesHtml": "

change log:\nAdded GPS support for SenseCAP Solar P1 in #1589\nAdded nRF52 power management for RAK3401 in #1984\nAdded token bucket based duty cycle enforcement in #1297\nAdded support for new GAT562 30S Mesh Kit device in #2009\nAdded support for new GAT562 Mesh Tracker Pro device in #1980\nAdded LNA toggle CLI commands radio.rxgain on and radio.rxgain off in #1653\nAdded MCU temperature to telemetry responses from room servers in #2052\nMigrated Heltec Tracker v2 to KCT8103L in #1936\nFixed bug where some queued packets would not get transmit in #1877\nFixed bug where BLE would stay on if turned off from companion screen when already connected in #1991

\n" }, { "version": "room-server-v1.14.0", "name": "Room Server Firmware v1.14.0", "datetime": "2026-03-06T02:37:59Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/room-server-v1.14.0", "prerelease": false, "notes": "Change log:\r\n* multibyte path hash support\r\n* new radio AGC reset implementation\r\n* HeltecV4 power fixes\r\n* RAK3401 power optimisations\r\n* Heltec Tracker V2 power fixes", "notesHtml": "

Change log:

\n\n" }, { "version": "repeater-v1.14.0", "name": "Repeater Firmware v1.14.0", "datetime": "2026-03-06T02:37:28Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/repeater-v1.14.0", "prerelease": false, "notes": "Change log:\r\n* multibyte path hash support\r\n* new CLI command: “get/set loop.detect …”\r\n* new CLI command: “get/set path.hash.mode …”\r\n* new CLI command: “get bootloader.ver”\r\n* new CLI command: “discover.neighbors”\r\n* new radio AGC reset implementation\r\n* HeltecV4 power fixes\r\n* RAK3401 power optimisations\r\n* Heltec Tracker V2 power fixes", "notesHtml": "

Change log:

\n\n" }, { "version": "companion-v1.14.0", "name": "Companion Firmware v1.14.0", "datetime": "2026-03-06T03:52:31Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/companion-v1.14.0", "prerelease": false, "notes": "Change log:\r\n* multibyte path hash support\r\n* new ‘auto add max hops’ preference\r\n* new radio AGC reset implementation\r\n* HeltecV4 power fixes\r\n* RAK3401 power optimisations\r\n* Heltec Tracker V2 power fixes", "notesHtml": "

Change log:

\n\n" }, { "version": "room-server-v1.13.0", "name": "Room Server Firmware v1.13.0", "datetime": "2026-02-15T07:48:23Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/room-server-v1.13.0", "prerelease": false, "notes": "Change log:\r\n* Thinknode M3 fixes\r\n* new boards: T-Beam 1W, M5 Stack C6\r\n* nRF board sleep optimisations\r\n* Heltec V4: improved RX sensitivity, low power fixes\r\n* WIO Tracker L1 Grove sensor support", "notesHtml": "

Change log:

\n\n" }, { "version": "repeater-v1.13.0", "name": "Repeater Firmware v1.13.0", "datetime": "2026-02-15T07:47:04Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/repeater-v1.13.0", "prerelease": false, "notes": "Change log:\r\n* Thinknode M3 fixes\r\n* new boards: T-Beam 1W, M5 Stack C6\r\n* new stats field: receive errors\r\n* nRF board sleep optimisations\r\n* Heltec V4: improved RX sensitivity, low power fixes\r\n* WIO Tracker L1 Grove sensor support", "notesHtml": "

Change log:

\n\n" }, { "version": "companion-v1.13.0", "name": "Companion Firmware v1.13.0", "datetime": "2026-02-15T08:49:34Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/companion-v1.13.0", "prerelease": false, "notes": "Change log:\r\n* off-grid (client repeat) mode support\r\n* buzzer sound logic reverted\r\n* new boards: T-Beam 1W, M5 Stack C6\r\n* some UI fixes, mute icon\r\n* blob file cleanup added\r\n* Heltec V4: improved RX sensitivity, low power fixes\r\n* WIO Tracker L1 Grove sensor support", "notesHtml": "

Change log:

\n\n" }, { "version": "room-server-v1.12.0", "name": "Room Server Firmware v1.12.0", "datetime": "2026-01-29T11:18:49Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/room-server-v1.12.0", "prerelease": false, "notes": "Change log:\r\n* new boards: Thinknode M6, M3, RAK3401, RAK11310, Meshtiny\r\n* nRF low power recovery manager\r\n* sensor fixes: BMP280, LPS22HB, SHTC3\r\n* new “clkreboot” CLI\r\n* on-boot adverts now zero-hop\r\n* remote “set prv.key” CLI \r\n* new “get/set owner.info” CLI\r\n* flood.advert.interval range now 3..168 hours\r\n* MCU temperature now in telemetry responses", "notesHtml": "

Change log:

\n\n" }, { "version": "repeater-v1.12.0", "name": "Repeater Firmware v1.12.0", "datetime": "2026-01-29T11:26:04Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/repeater-v1.12.0", "prerelease": false, "notes": "Change log:\r\n* new boards: Thinknode M6, M3, RAK3401, RAK11310, Meshtiny\r\n* nRF low power recovery manager (CLI ‘pwrmgt’)\r\n* Stats: new recv errors counter\r\n* region names now without ‘#’, new ‘region list’ CLI\r\n* ESP32: new “powersaving on/off” CLI\r\n* new “clkreboot” CLI\r\n* on-boot adverts now zero-hop\r\n* new “get/set owner.info” CLI\r\n* flood.advert.interval range now 3..168 hours\r\n* remote “set prv.key” CLI \r\n* new zero-hop anonReq types (Region discovery, owner info, clock sync)\r\n* MCU temperature now in telemetry responses", "notesHtml": "

Change log:

\n\n" }, { "version": "companion-v1.12.0", "name": "Companion Firmware v1.12.0", "datetime": "2026-01-29T12:10:45Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/companion-v1.12.0", "prerelease": false, "notes": "Change log:\r\n* new boards: Thinknode M6, M3, RAK3401, RAK11310, Meshtiny\r\n* nRF low power recovery manager\r\n* BLE code rewritten\r\n* WiFi serial fixes\r\n* contacts db can now overwrite old entries\r\n* new prefs: buzzer quiet, gps enabled, gps interval", "notesHtml": "

Change log:

\n\n" }, { "version": "room-server-v1.11.0", "name": "Room Server Firmware v1.11.0", "datetime": "2025-11-30T08:34:45Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/room-server-v1.11.0", "prerelease": false, "notes": "Change log:\r\n* remote login bug fix (no responses after login)\r\n* Extended Trace support\r\n* get/set adc,multiplier support\r\n* New boards: Ikoka handheld, Keepteen LT1", "notesHtml": "

Change log:

\n\n" }, { "version": "repeater-v1.11.0", "name": "Repeater Firmware v1.11.0", "datetime": "2025-11-30T08:33:44Z", "url": "https://github.com/meshcore-dev/MeshCore/releases/tag/repeater-v1.11.0", "prerelease": false, "notes": "Change log:\r\n* remote login bug fix (no responses after login)\r\n* Extended Trace support\r\n* get/set adc,multiplier support\r\n* RAK4631: Uart bridge support\r\n* New boards: Ikoka handheld, Keepteen LT1", "notesHtml": "

Change log:

\n\n" } ], "changelogSource": "script", "changelogUpdatedAt": "2026-06-21T09:55:37.699Z" }, { "id": "cubecell-meshcore", "name": "CubeCell MeshCore", "type": "fork", "maintainer": "atomozero", "description": "A minimal MeshCore-compatible repeater firmware for Heltec CubeCell boards (HTCC-AB01, AB02, AC01). Extends mesh coverage with flood routing, supports authenticated remote management via companion app, and includes automatic daily health reports. Optimized for solar-powered deployments.\n", "repository": "https://github.com/atomozero/CubeCellMeshCore", "license": "MIT", "status": "active", "lifecycle": "active", "maturity": "beta", "distribution": "community", "lineage": { "kind": "fork", "upstreamFirmwareId": "meshcore-official", "upstreamRepository": "https://github.com/meshcore-dev/MeshCore" }, "runtime": { "framework": "arduino", "language": "cpp" }, "roles": [ "repeater" ], "features": [ "Flood routing repeater", "Authenticated remote management via companion app", "Automatic daily health reports", "Solar-powered optimization", "CubeCell board support (HTCC-AB01, AB02, AC01)" ], "capabilities": { "protocol": { "meshcoreCompatible": true }, "transports": { "ble": false, "usbSerial": true, "nativeTcp": false, "wifiAp": false }, "operations": { "ota": false, "webFlasher": false }, "networking": { "repeater": true, "roomServer": false, "observer": false, "kissModem": false }, "hardware": { "gps": false, "display": false, "sensors": false, "lowPowerRx": true } }, "devices": [ { "id": "cubecell-htcc-ab01", "status": "supported" } ], "popularity": { "githubStars": 13, "githubForks": 1, "githubWatchers": 3, "githubOpenIssues": 5, "githubContributors": 2, "releaseDownloads": 79, "latestReleaseDownloads": 49, "lastChecked": "2026-06-21" }, "verification": { "sourceAvailable": true, "releasesAvailable": true, "ciBuilds": false, "lastChecked": "2026-06-21" }, "latest_version": "0.5.0", "released": "2026-02-14", "releases": [ { "version": "v0.5.0", "name": "v0.5.0 San Valentino Release", "datetime": "2026-02-14T16:53:46Z", "url": "https://github.com/atomozero/CubeCellMeshCore/releases/tag/v0.5.0", "prerelease": false, "notes": "Quiet Hours + Circuit Breaker + Adaptive TX Power\r\n\r\n Three new features leveraging the existing SNR/RSSI infrastructure to improve reliability, power savings, and mesh network resilience.\r\n\r\n- Quiet Hours — Configurable night-time rate limiting (e.g. 22:00-06:00) reduces forwarding from 100 to 30 packets/min. Saves battery during low-traffic periods. Requires TimeSync.\r\n\r\n- Circuit Breaker — Automatically blocks DIRECT forwarding to neighbours with degraded links (SNR < -10dB). Transitions to half-open after 5 minutes for a test packet. Good SNR closes the breaker. FLOOD traffic is never blocked.\r\n\r\n- Adaptive TX Power — Dynamically adjusts transmit power (5-14 dBm EU) based on average neighbour SNR. Reduces power when signal is strong, increases when weak.", "notesHtml": "

Quiet Hours + Circuit Breaker + Adaptive TX Power

\n

Three new features leveraging the existing SNR/RSSI infrastructure to improve reliability, power savings, and mesh network resilience.

\n\n" }, { "version": "v0.4.0", "name": "v0.4.0 - Battery Fix, Remote CLI & Flash Optimization", "datetime": "2026-02-09T22:23:34Z", "url": "https://github.com/atomozero/CubeCellMeshCore/releases/tag/v0.4.0", "prerelease": false, "notes": "## What's New in v0.4.0\r\n\r\n ### Bug Fixes\r\n - **Battery ADC fixed** - Resolved 0V battery reading caused by\r\n CubeCell framework 1.6.0 bug (ch3 SAR calibration not initialized).\r\n New workaround uses `analogRead()` + ch0 calibration + `VBAT_ADC_CTL`\r\n circuit control\r\n - **Airtime tracking** - RX/TX airtime now properly calculated\r\n per-packet using LoRa formula\r\n - **Noise floor estimation** - EMA-smoothed noise floor from\r\n RSSI-SNR, no longer stuck at 0dB\r\n - **Remote CLI commands** - Fixed \"Err:Unknown\" for commands only\r\n available on local serial\r\n\r\n ### New Features\r\n - **`radiostats` command** - Noise floor, last RSSI/SNR, airtime\r\n TX/RX (serial + remote)\r\n - **`packetstats` command** - Packet breakdown: flood/direct RX/TX\r\n (serial + remote)\r\n - **`lifetime` command** - Now available via remote CLI (was\r\n serial-only)\r\n - **`tempradio` command** - Temporary radio parameter changes without\r\n saving to EEPROM\r\n\r\n ### Optimizations\r\n - **Flash savings: 2,904 bytes** - String abbreviation in LOG/LOG_RAW\r\n macros (98.3% → 96.0%)\r\n - Startup banner simplified (removed unicode box-drawing characters)\r\n\r\n ### Documentation\r\n - Complete command reference tables in README\r\n - Corrected radio parameters (frequency, TX power, sync word)\r\n\r\n ### Build Info\r\n - Flash: 96.5% (126,492 / 131,072 bytes)\r\n - RAM: 51.3% (8,408 / 16,384 bytes)\r\n - Board: Heltec CubeCell HTCC-AB01\r\n - Region: EU868", "notesHtml": "

What's New in v0.4.0

\n

Bug Fixes

\n\n

New Features

\n\n

Optimizations

\n\n

Documentation

\n\n

Build Info

\n\n" }, { "version": "v0.3.3", "name": "CubeCellMeshCore v0.3.3", "datetime": "2026-01-23T21:37:34Z", "url": "https://github.com/atomozero/CubeCellMeshCore/releases/tag/v0.3.3", "prerelease": false, "notes": "## Features\r\n\r\n - **MeshCore Protocol Compatible** - Works with MeshCore Android/iOS apps\r\n - **Ed25519 Authentication** - Secure login with encrypted sessions\r\n - **Rate Limiting** - Protection against brute-force and flood attacks\r\n - **Persistent Statistics** - Lifetime stats survive reboots (EEPROM)\r\n - **Neighbour Tracking** - Direct repeater discovery via 0-hop ADVERTs\r\n - **Remote CLI** - Encrypted command access via mesh network\r\n - **Deep Sleep** - Low power mode support\r\n\r\n ## What's New in v0.3.3\r\n\r\n - Added persistent statistics stored in EEPROM\r\n - Tracks lifetime: RX/TX/FWD packets, unique nodes, logins, uptime\r\n - Auto-save every 5 minutes with CRC16 integrity\r\n - New commands: `lifetime`, `savestats`\r\n - Boot counter for reliability monitoring\r\n\r\n ## Installation\r\n\r\n Download `CubeCellMeshCore-v0.3.3.zip` and flash using CubeCellTool or PlatformIO.\r\n\r\n See `INSTALL.md` for detailed instructions.\r\n\r\n ## Hardware\r\n\r\n - Heltec CubeCell HTCC-AB01\r\n - Flash: 95.8% used\r\n - RAM: 51.1% used", "notesHtml": "

Features

\n\n

What's New in v0.3.3

\n\n

Installation

\n

Download CubeCellMeshCore-v0.3.3.zip and flash using CubeCellTool or PlatformIO.

\n

See INSTALL.md for detailed instructions.

\n

Hardware

\n\n" } ], "changelogSource": "github", "changelogUpdatedAt": "2026-06-21T09:55:27.762Z" }, { "id": "eastmesh", "name": "EastMesh", "type": "fork", "maintainer": "xJARiD", "description": "EastMesh firmware builds for MeshCore, with MQTT repeaters, WiFi companions, and simple release downloads for supported boards. Features an optional local HTTPS config panel on supported ESP32 targets, JWT auth using device identity, and battery reporting.\n", "repository": "https://github.com/xJARiD/MeshCore-EastMesh", "license": "MIT", "status": "active", "lifecycle": "active", "maturity": "beta", "distribution": "community", "lineage": { "kind": "fork", "upstreamFirmwareId": "meshcore-official", "upstreamRepository": "https://github.com/meshcore-dev/MeshCore" }, "runtime": { "framework": "arduino", "language": "cpp" }, "roles": [ "companion", "repeater", "observer" ], "features": [ "MQTT repeater builds", "WiFi companion builds", "Optional local HTTPS config panel (ESP32)", "JWT auth using device identity", "Battery reporting on supported targets", "Observer role support" ], "capabilities": { "protocol": { "meshcoreCompatible": true }, "transports": { "ble": true, "usbSerial": true, "nativeTcp": true, "wifiAp": true }, "operations": { "ota": true, "webFlasher": false }, "networking": { "repeater": true, "roomServer": false, "observer": true, "mqtt": true, "kissModem": false }, "hardware": { "gps": true, "display": true, "sensors": false, "lowPowerRx": false } }, "devices": [ { "id": "heltec-v4", "status": "supported" } ], "popularity": { "githubStars": 18, "githubForks": 6, "githubWatchers": 2, "githubOpenIssues": 0, "githubContributors": 172, "releaseDownloads": 3317, "latestReleaseDownloads": 108, "lastChecked": "2026-06-21" }, "verification": { "sourceAvailable": true, "releasesAvailable": true, "ciBuilds": true, "lastChecked": "2026-06-21" }, "latest_version": "2026.6.3", "released": "2026-06-09", "releases": [ { "version": "observer-eastmesh-v2026.6.3", "name": "Observer EastMesh Firmware v1.16.0-eastmesh-v2026.6.3", "datetime": "2026-06-09T10:19:45Z", "url": "https://github.com/xJARiD/MeshCore-EastMesh/releases/tag/observer-eastmesh-v2026.6.3", "prerelease": false, "notes": "## MeshCore EastMesh Observer\r\n\r\nEastMesh `observer-eastmesh` firmware for MeshCore boards with secure MQTT uplink and optional local web management, based on MeshCore firmware `v1.16.0`.\r\n\r\nThis release adds secure WebSocket transport support for custom MQTT brokers from the Observer web panel and CLI.\r\n\r\n### What's Changed\r\n\r\n- Added TCP/WSS transport selection for custom MQTT brokers.\r\n- Added web-panel Custom MQTT transport control for switching between TCP and WSS.\r\n- Added CLI support for viewing and setting the custom MQTT transport.\r\n- Kept custom MQTT authentication to username and password only; no JWT/web auth is used for custom brokers.\r\n- Verified custom MQTT WSS connections with the ESP-IDF x509 root CA bundle.\r\n- Fixed custom MQTT WSS to use the `/mqtt` WebSocket path.\r\n- Configured custom MQTT WSS using a full `wss://host:port/mqtt` URI so ESP-MQTT handles the WebSocket connection consistently.\r\n- Updated `get mqtt.status` to show the custom MQTT transport and state, for example `custom:wss:up`.\r\n\r\n### Breaking Changes\r\n\r\nNone.\r\n\r\n### Notes\r\n\r\n- `eastmesh-au` remains the recommended MQTT endpoint once `mqtt.iata` is configured.\r\n- Custom MQTT is available for private broker deployments.\r\n- For TCP custom MQTT, use the broker host and port as before.\r\n- For WSS custom MQTT, set the host and port, select WSS transport, and the firmware will connect using `wss://host:port/mqtt`.\r\n- WSS uses TLS encryption and validates against the ESP-IDF x509 root CA bundle.\r\n- For maximum heap headroom on busy observers, use the web panel for setup and troubleshooting, then disable it with `set web off`.\r\n- Browsers may still require accepting the self-signed certificate warning on first HTTPS access.\r\n- `flood.max.unscoped` defaults to `64`; lower it only if you want to limit how far unscoped flood traffic repeats.\r\n- `flood.max.advert` controls the hop limit for flooded advert packets.\r\n\r\n### Documentation\r\n\r\n[xjarid.github.io/MeshCore-EastMesh](https://xjarid.github.io/MeshCore-EastMesh/)\r\n\r\n### Flashing\r\n\r\n- [flasher.eastmesh.au](https://flasher.eastmesh.au/)\r\n- [flasher.meshcore.io](https://flasher.meshcore.io/)\r\n\r\n### Assets\r\n\r\n- `.bin` - standard update image\r\n- `-merged.bin` - full ESP32 image for flashing after erase", "notesHtml": "

MeshCore EastMesh Observer

\n

EastMesh observer-eastmesh firmware for MeshCore boards with secure MQTT uplink and optional local web management, based on MeshCore firmware v1.16.0.

\n

This release adds secure WebSocket transport support for custom MQTT brokers from the Observer web panel and CLI.

\n

What's Changed

\n\n

Breaking Changes

\n

None.

\n

Notes

\n\n

Documentation

\n

xjarid.github.io/MeshCore-EastMesh

\n

Flashing

\n\n

Assets

\n\n" }, { "version": "observer-eastmesh-bridge-espnow-v2026.6.3", "name": "Observer EastMesh Firmware with ESP-NOW Bridge v1.16.0-eastmesh-v2026.6.3", "datetime": "2026-06-09T10:18:22Z", "url": "https://github.com/xJARiD/MeshCore-EastMesh/releases/tag/observer-eastmesh-bridge-espnow-v2026.6.3", "prerelease": false, "notes": "## MeshCore EastMesh Observer with ESP-NOW Bridge\r\n\r\nEastMesh `observer-eastmesh-bridge-espnow` firmware for MeshCore boards that combine secure MQTT uplink with ESP-NOW bridge support, based on MeshCore firmware `v1.16.0`.\r\n\r\nThis release includes the same Observer updates as `observer-eastmesh-v2026.6.3`, with ESP-NOW bridge support included.\r\n\r\n### What's Changed\r\n\r\n- Same changes as `observer-eastmesh-v2026.6.3`.\r\n- Includes ESP-NOW bridge firmware targets using the `*_repeater_observer_espnow` PlatformIO environment suffix.\r\n\r\n### Breaking Changes\r\n\r\nNone.\r\n\r\n### Notes\r\n\r\n- This track is separate from `observer-eastmesh`.\r\n- Use `get wifi.status` to confirm the active 2.4 GHz Wi-Fi channel before setting `bridge.channel`.\r\n- `bridge.channel` should match the connected Wi-Fi channel for reliable ESP-NOW bridge operation.\r\n- For maximum heap headroom after setup, disable the web panel with `set web off`.\r\n- `flood.max.advert` controls the hop limit for flooded advert packets.\r\n\r\n### Documentation\r\n\r\n[xjarid.github.io/MeshCore-EastMesh](https://xjarid.github.io/MeshCore-EastMesh/)\r\n\r\n### Flashing\r\n\r\n- [flasher.eastmesh.au](https://flasher.eastmesh.au/)\r\n- [flasher.meshcore.io](https://flasher.meshcore.io/)\r\n\r\n### Assets\r\n\r\n- `.bin` - standard update image\r\n- `-merged.bin` - full ESP32 image for flashing after erase", "notesHtml": "

MeshCore EastMesh Observer with ESP-NOW Bridge

\n

EastMesh observer-eastmesh-bridge-espnow firmware for MeshCore boards that combine secure MQTT uplink with ESP-NOW bridge support, based on MeshCore firmware v1.16.0.

\n

This release includes the same Observer updates as observer-eastmesh-v2026.6.3, with ESP-NOW bridge support included.

\n

What's Changed

\n\n

Breaking Changes

\n

None.

\n

Notes

\n\n

Documentation

\n

xjarid.github.io/MeshCore-EastMesh

\n

Flashing

\n\n

Assets

\n\n" }, { "version": "observer-eastmesh-v2026.6.2", "name": "Observer EastMesh Firmware v1.16.0-eastmesh-v2026.6.2", "datetime": "2026-06-07T05:03:35Z", "url": "https://github.com/xJARiD/MeshCore-EastMesh/releases/tag/observer-eastmesh-v2026.6.2", "prerelease": false, "notes": "## MeshCore EastMesh Observer\r\n\r\nEastMesh `observer-eastmesh` firmware for MeshCore boards with secure MQTT uplink and optional local web management, based on MeshCore firmware `v1.16.0`.\r\n\r\nThis release improves Observer boot reliability, T-Beam S3 Supreme telemetry, Wi-Fi/OTA persistence, and web-panel archive maintenance.\r\n\r\n### What's Changed\r\n\r\n- Fixed LilyGo T-Beam S3 Supreme BME280 detection and live telemetry.\r\n- Added board-specific I2C recovery for T-Beam S3 Supreme BME280 reads.\r\n- Changed live `/stats` sensor values to use the main-loop sensor snapshot.\r\n- Improved boot-time Wi-Fi startup on T-Beam S3 Supreme.\r\n- Added last-connected Wi-Fi channel learning with fallback to full scan.\r\n- Added NVS-backed Wi-Fi preference recovery so SSID and password survive OTA updates even if filesystem prefs are lost.\r\n- Hardened Wi-Fi retry handling so scan-mode connects are not interrupted early.\r\n- Fixed `set wifi.powersaving none` when power saving was already disabled.\r\n- Bounded archive neighbour restore and history reads to avoid slow boots from large SD-card archive files.\r\n- Added web-panel and CLI SD purge actions for supported SD-card targets.\r\n- Hardened OTA startup by binding before reporting success and falling back to alternate ports if port 80 is still busy.\r\n\r\n### Breaking Changes\r\n\r\nNone.\r\n\r\n### Notes\r\n\r\n- `eastmesh-au` remains the recommended MQTT endpoint once `mqtt.iata` is configured.\r\n- Custom MQTT is available for private broker deployments.\r\n- For maximum heap headroom on busy observers, use the web panel for setup and troubleshooting, then disable it with `set web off`.\r\n- Browsers may still require accepting the self-signed certificate warning on first HTTPS access.\r\n- `flood.max.unscoped` defaults to `64`; lower it only if you want to limit how far unscoped flood traffic repeats.\r\n- `flood.max.advert` controls the hop limit for flooded advert packets.\r\n- Wi-Fi credentials are now mirrored into ESP32 NVS for OTA-safe recovery.\r\n\r\n### Documentation\r\n\r\n[xjarid.github.io/MeshCore-EastMesh](https://xjarid.github.io/MeshCore-EastMesh/)\r\n\r\n### Flashing\r\n\r\n- [flasher.eastmesh.au](https://flasher.eastmesh.au/)\r\n- [flasher.meshcore.io](https://flasher.meshcore.io/)\r\n\r\n### Assets\r\n\r\n- `.bin` - standard update image\r\n- `-merged.bin` - full ESP32 image for flashing after erase", "notesHtml": "

MeshCore EastMesh Observer

\n

EastMesh observer-eastmesh firmware for MeshCore boards with secure MQTT uplink and optional local web management, based on MeshCore firmware v1.16.0.

\n

This release improves Observer boot reliability, T-Beam S3 Supreme telemetry, Wi-Fi/OTA persistence, and web-panel archive maintenance.

\n

What's Changed

\n\n

Breaking Changes

\n

None.

\n

Notes

\n\n

Documentation

\n

xjarid.github.io/MeshCore-EastMesh

\n

Flashing

\n\n

Assets

\n\n" }, { "version": "observer-eastmesh-bridge-espnow-v2026.6.2", "name": "Observer EastMesh Firmware with ESP-NOW Bridge v1.16.0-eastmesh-v2026.6.2", "datetime": "2026-06-07T05:03:22Z", "url": "https://github.com/xJARiD/MeshCore-EastMesh/releases/tag/observer-eastmesh-bridge-espnow-v2026.6.2", "prerelease": false, "notes": "## MeshCore EastMesh Observer with ESP-NOW Bridge\r\n\r\nEastMesh `observer-eastmesh-bridge-espnow` firmware for MeshCore boards that combine secure MQTT uplink with ESP-NOW bridge support, based on MeshCore firmware `v1.16.0`.\r\n\r\nThis release includes the same Observer updates as `observer-eastmesh-v2026.6.2`, with ESP-NOW bridge support included.\r\n\r\n### What's Changed\r\n\r\n- Same changes as `observer-eastmesh-v2026.6.2`.\r\n- Includes ESP-NOW bridge firmware targets using the `*_repeater_observer_espnow` PlatformIO environment suffix.\r\n\r\n### Breaking Changes\r\n\r\nNone.\r\n\r\n### Notes\r\n\r\n- This track is separate from `observer-eastmesh`.\r\n- Use `get wifi.status` to confirm the active 2.4 GHz Wi-Fi channel before setting `bridge.channel`.\r\n- `bridge.channel` should match the connected Wi-Fi channel for reliable ESP-NOW bridge operation.\r\n- For maximum heap headroom after setup, disable the web panel with `set web off`.\r\n- `flood.max.advert` controls the hop limit for flooded advert packets.\r\n\r\n### Documentation\r\n\r\n[xjarid.github.io/MeshCore-EastMesh](https://xjarid.github.io/MeshCore-EastMesh/)\r\n\r\n### Flashing\r\n\r\n- [flasher.eastmesh.au](https://flasher.eastmesh.au/)\r\n- [flasher.meshcore.io](https://flasher.meshcore.io/)\r\n\r\n### Assets\r\n\r\n- `.bin` - standard update image\r\n- `-merged.bin` - full ESP32 image for flashing after erase", "notesHtml": "

MeshCore EastMesh Observer with ESP-NOW Bridge

\n

EastMesh observer-eastmesh-bridge-espnow firmware for MeshCore boards that combine secure MQTT uplink with ESP-NOW bridge support, based on MeshCore firmware v1.16.0.

\n

This release includes the same Observer updates as observer-eastmesh-v2026.6.2, with ESP-NOW bridge support included.

\n

What's Changed

\n\n

Breaking Changes

\n

None.

\n

Notes

\n\n

Documentation

\n

xjarid.github.io/MeshCore-EastMesh

\n

Flashing

\n\n

Assets

\n\n" }, { "version": "repeater-bridge-espnow-v1.16.0", "name": "Repeater ESP-NOW Bridge Firmware v1.16.0", "datetime": "2026-06-06T23:20:49Z", "url": "https://github.com/xJARiD/MeshCore-EastMesh/releases/tag/repeater-bridge-espnow-v1.16.0", "prerelease": false, "notes": "## MeshCore Repeater ESP-NOW Bridge\r\n\r\nRepeater ESP-NOW bridge firmware built from the upstream `meshcore-dev/MeshCore` firmware base.\r\n\r\nThis release packages the existing upstream bridge functionality as EastMesh release assets.\r\n\r\n### What's Changed\r\n\r\n- Added release builds for `repeater-bridge-espnow-v*` firmware artifacts.\r\n- Kept the version aligned with upstream MeshCore `v1.16.0`.\r\n\r\n### Breaking Changes\r\n\r\nNone.\r\n\r\n### Flashing\r\n\r\n- [flasher.meshcore.io](https://flasher.meshcore.io/)\r\n- [flasher.eastmesh.au](https://flasher.eastmesh.au/)\r\n\r\n### Assets\r\n\r\n- `.bin` - standard update image\r\n- `-merged.bin` - full ESP32 image for flashing after erase", "notesHtml": "

MeshCore Repeater ESP-NOW Bridge

\n

Repeater ESP-NOW bridge firmware built from the upstream meshcore-dev/MeshCore firmware base.

\n

This release packages the existing upstream bridge functionality as EastMesh release assets.

\n

What's Changed

\n\n

Breaking Changes

\n

None.

\n

Flashing

\n\n

Assets

\n\n" }, { "version": "observer-eastmesh-v2026.6.1", "name": "Observer EastMesh Firmware v1.16.0-eastmesh-v2026.6.1", "datetime": "2026-06-06T23:40:32Z", "url": "https://github.com/xJARiD/MeshCore-EastMesh/releases/tag/observer-eastmesh-v2026.6.1", "prerelease": false, "notes": "## MeshCore EastMesh Observer\r\n\r\nEastMesh `observer-eastmesh` firmware for MeshCore boards with secure MQTT uplink and optional local web management, based on MeshCore firmware `v1.16.0`.\r\n\r\nThis release updates Observer firmware to upstream MeshCore `v1.16.0` with flood-advert controls, web panel refinements, and board/platform fixes.\r\n\r\n### What's Changed\r\n\r\n- Added `flood.max.advert` so flooded advert packets can use their own hop limit.\r\n- Added web panel controls for scoped and unscoped flood max values.\r\n- Improved web panel login recovery and favicon handling.\r\n- Hardened OTA startup from the local web panel by waiting for the OTA HTTP listener before redirecting.\r\n- Merged upstream MeshCore `v1.16.0` dev updates, including companion UI, board, radio, power-saving, documentation, and platform fixes.\r\n\r\n### Breaking Changes\r\n\r\nNone.\r\n\r\n### Notes\r\n\r\n- `eastmesh-au` remains the recommended MQTT endpoint once `mqtt.iata` is configured.\r\n- Custom MQTT is available for private broker deployments.\r\n- For maximum heap headroom on busy observers, use the web panel for setup and troubleshooting, then disable it with `set web off`.\r\n- Browsers may still require accepting the self-signed certificate warning on first HTTPS access.\r\n- `flood.max.unscoped` defaults to `64`; lower it only if you want to limit how far unscoped flood traffic repeats.\r\n- `flood.max.advert` controls the hop limit for flooded advert packets.\r\n\r\n### Documentation\r\n\r\n[xjarid.github.io/MeshCore-EastMesh](https://xjarid.github.io/MeshCore-EastMesh/)\r\n\r\n### Flashing\r\n\r\n- [flasher.eastmesh.au](https://flasher.eastmesh.au/)\r\n- [flasher.meshcore.io](https://flasher.meshcore.io/)\r\n\r\n### Assets\r\n\r\n- `.bin` - standard update image\r\n- `-merged.bin` - full ESP32 image for flashing after erase", "notesHtml": "

MeshCore EastMesh Observer

\n

EastMesh observer-eastmesh firmware for MeshCore boards with secure MQTT uplink and optional local web management, based on MeshCore firmware v1.16.0.

\n

This release updates Observer firmware to upstream MeshCore v1.16.0 with flood-advert controls, web panel refinements, and board/platform fixes.

\n

What's Changed

\n\n

Breaking Changes

\n

None.

\n

Notes

\n\n

Documentation

\n

xjarid.github.io/MeshCore-EastMesh

\n

Flashing

\n\n

Assets

\n\n" }, { "version": "observer-eastmesh-bridge-espnow-v2026.6.1", "name": "Observer EastMesh Firmware with ESP-NOW Bridge v1.16.0-eastmesh-v2026.6.1", "datetime": "2026-06-06T23:40:20Z", "url": "https://github.com/xJARiD/MeshCore-EastMesh/releases/tag/observer-eastmesh-bridge-espnow-v2026.6.1", "prerelease": false, "notes": "## MeshCore EastMesh Observer with ESP-NOW Bridge\r\n\r\nEastMesh `observer-eastmesh-bridge-espnow` firmware for MeshCore boards that combine secure MQTT uplink with ESP-NOW bridge support, based on MeshCore firmware `v1.16.0`.\r\n\r\nThis release includes the same Observer updates as `observer-eastmesh-v2026.6.1`, with ESP-NOW bridge support included.\r\n\r\n### What's Changed\r\n\r\n- Same changes as `observer-eastmesh-v2026.6.1`.\r\n- Includes ESP-NOW bridge firmware targets using the `*_repeater_observer_espnow` PlatformIO environment suffix.\r\n\r\n### Breaking Changes\r\n\r\nNone.\r\n\r\n### Notes\r\n\r\n- This track is separate from `observer-eastmesh`.\r\n- Use `get wifi.status` to confirm the active 2.4 GHz Wi-Fi channel before setting `bridge.channel`.\r\n- `bridge.channel` should match the connected Wi-Fi channel for reliable ESP-NOW bridge operation.\r\n- For maximum heap headroom after setup, disable the web panel with `set web off`.\r\n- `flood.max.advert` controls the hop limit for flooded advert packets.\r\n\r\n### Documentation\r\n\r\n[xjarid.github.io/MeshCore-EastMesh](https://xjarid.github.io/MeshCore-EastMesh/)\r\n\r\n### Flashing\r\n\r\n- [flasher.eastmesh.au](https://flasher.eastmesh.au/)\r\n- [flasher.meshcore.io](https://flasher.meshcore.io/)\r\n\r\n### Assets\r\n\r\n- `.bin` - standard update image\r\n- `-merged.bin` - full ESP32 image for flashing after erase", "notesHtml": "

MeshCore EastMesh Observer with ESP-NOW Bridge

\n

EastMesh observer-eastmesh-bridge-espnow firmware for MeshCore boards that combine secure MQTT uplink with ESP-NOW bridge support, based on MeshCore firmware v1.16.0.

\n

This release includes the same Observer updates as observer-eastmesh-v2026.6.1, with ESP-NOW bridge support included.

\n

What's Changed

\n\n

Breaking Changes

\n

None.

\n

Notes

\n\n

Documentation

\n

xjarid.github.io/MeshCore-EastMesh

\n

Flashing

\n\n

Assets

\n\n" }, { "version": "companion-wifi-v1.16.0", "name": "Companion WiFi Firmware v1.16.0", "datetime": "2026-06-06T23:20:08Z", "url": "https://github.com/xJARiD/MeshCore-EastMesh/releases/tag/companion-wifi-v1.16.0", "prerelease": false, "notes": "## MeshCore EastMesh Companion WiFi\r\n\r\nThis is standard MeshCore companion WiFi firmware based on MeshCore `v1.16.0`, with a few extra Wi-Fi setup commands added for EastMesh.\r\n\r\n### What’s Different\r\n\r\nThe only EastMesh-specific addition is a small set of Wi-Fi CLI commands that let you view and save Wi-Fi settings:\r\n\r\n- `get wifi.status`\r\n- `get wifi.ssid`\r\n- `get wifi.powersaving`\r\n- `set wifi.ssid `\r\n- `set wifi.pwd `\r\n- `set wifi.powersaving none|min|max`\r\n\r\n### Notes\r\n\r\n- Everything else behaves like the normal MeshCore companion WiFi firmware\r\n- Use the file that matches your board exactly\r\n- Companion WiFi releases use the upstream MeshCore version number\r\n\r\n### Documentation\r\n\r\nhttps://xjarid.github.io/MeshCore-EastMesh/\r\n\r\n### Flashing\r\n\r\n- https://flasher.eastmesh.au/\r\n- https://flasher.meshcore.io/\r\n\r\n### Assets\r\n\r\n- `.bin` – standard update\r\n- `-merged.bin` – full image (after erase, ESP32)", "notesHtml": "

MeshCore EastMesh Companion WiFi

\n

This is standard MeshCore companion WiFi firmware based on MeshCore v1.16.0, with a few extra Wi-Fi setup commands added for EastMesh.

\n

What’s Different

\n

The only EastMesh-specific addition is a small set of Wi-Fi CLI commands that let you view and save Wi-Fi settings:

\n\n

Notes

\n\n

Documentation

\n

https://xjarid.github.io/MeshCore-EastMesh/

\n

Flashing

\n\n

Assets

\n\n" }, { "version": "observer-eastmesh-v2026.6.0", "name": "Observer EastMesh Firmware v1.15.0-eastmesh-v2026.6.0", "datetime": "2026-06-03T02:49:43Z", "url": "https://github.com/xJARiD/MeshCore-EastMesh/releases/tag/observer-eastmesh-v2026.6.0", "prerelease": false, "notes": "## MeshCore EastMesh Observer\r\n\r\nEastMesh `observer-eastmesh` firmware for MeshCore boards with secure MQTT uplink and optional local web management, based on MeshCore firmware `v1.15.0`.\r\n\r\nThis release updates Observer firmware with the latest upstream MeshCore dev changes plus EastMesh web panel, MQTT, radio, and board support fixes.\r\n\r\n### What's Changed\r\n\r\n- Added configurable custom MQTT broker support alongside the curated EastMesh and LetsMesh endpoints.\r\n- Added Station G3 ESP32 Observer firmware targets.\r\n- Added `flood.max.unscoped` so unscoped flood packets can use a separate hop limit from scoped flood traffic.\r\n- Preserved web panel sessions across Wi-Fi reconnects.\r\n- Hardened OTA startup from the local web panel and existing Wi-Fi connections.\r\n- Hardened LilyGo T-Beam 1W radio setup.\r\n- Restored the missing SX126x register patch.\r\n- Merged upstream MeshCore dev updates, including sensor handling, RAK4631 BME680/BSEC support, documentation refreshes, and board/platform fixes.\r\n\r\n### Breaking Changes\r\n\r\nNone.\r\n\r\n### Notes\r\n\r\n- `eastmesh-au` remains the recommended MQTT endpoint once `mqtt.iata` is configured.\r\n- Custom MQTT is available for private broker deployments.\r\n- For maximum heap headroom on busy observers, use the web panel for setup and troubleshooting, then disable it with `set web off`.\r\n- Browsers may still require accepting the self-signed certificate warning on first HTTPS access.\r\n- `flood.max.unscoped` defaults to `64`; lower it only if you want to limit how far unscoped flood traffic repeats.\r\n- If using LilyGo T-Beam 1W fan controls after upgrading, re-save your preferred fan settings if needed.\r\n\r\n### Documentation\r\n\r\n[xjarid.github.io/MeshCore-EastMesh](https://xjarid.github.io/MeshCore-EastMesh/)\r\n\r\n### Flashing\r\n\r\n- [flasher.eastmesh.au](https://flasher.eastmesh.au/)\r\n- [flasher.meshcore.io](https://flasher.meshcore.io/)\r\n\r\n### Assets\r\n\r\n- `.bin` - standard update image\r\n- `-merged.bin` - full ESP32 image for flashing after erase", "notesHtml": "

MeshCore EastMesh Observer

\n

EastMesh observer-eastmesh firmware for MeshCore boards with secure MQTT uplink and optional local web management, based on MeshCore firmware v1.15.0.

\n

This release updates Observer firmware with the latest upstream MeshCore dev changes plus EastMesh web panel, MQTT, radio, and board support fixes.

\n

What's Changed

\n\n

Breaking Changes

\n

None.

\n

Notes

\n\n

Documentation

\n

xjarid.github.io/MeshCore-EastMesh

\n

Flashing

\n\n

Assets

\n\n" }, { "version": "observer-eastmesh-bridge-espnow-v2026.6.0", "name": "Observer EastMesh Firmware with ESP-NOW Bridge v1.15.0-eastmesh-v2026.6.0", "datetime": "2026-06-03T02:49:29Z", "url": "https://github.com/xJARiD/MeshCore-EastMesh/releases/tag/observer-eastmesh-bridge-espnow-v2026.6.0", "prerelease": false, "notes": "## MeshCore EastMesh Observer with ESP-NOW Bridge\r\n\r\nEastMesh `observer-eastmesh-bridge-espnow` firmware for MeshCore boards that combine secure MQTT uplink with ESP-NOW bridge support, based on MeshCore firmware `v1.15.0`.\r\n\r\nThis release includes the same Observer updates as `observer-eastmesh-v2026.6.0`, with ESP-NOW bridge support included.\r\n\r\n### What's Changed\r\n\r\n- Same changes as `observer-eastmesh-v2026.6.0`.\r\n- Includes ESP-NOW bridge firmware targets using the `*_repeater_observer_espnow` PlatformIO environment suffix.\r\n\r\n### Breaking Changes\r\n\r\nNone.\r\n\r\n### Notes\r\n\r\n- This track is separate from `observer-eastmesh`.\r\n- Use `get wifi.status` to confirm the active 2.4 GHz Wi-Fi channel before setting `bridge.channel`.\r\n- `bridge.channel` should match the connected Wi-Fi channel for reliable ESP-NOW bridge operation.\r\n- For maximum heap headroom after setup, disable the web panel with `set web off`.\r\n\r\n### Documentation\r\n\r\n[xjarid.github.io/MeshCore-EastMesh](https://xjarid.github.io/MeshCore-EastMesh/)\r\n\r\n### Flashing\r\n\r\n- [flasher.eastmesh.au](https://flasher.eastmesh.au/)\r\n- [flasher.meshcore.io](https://flasher.meshcore.io/)\r\n\r\n### Assets\r\n\r\n- `.bin` - standard update image\r\n- `-merged.bin` - full ESP32 image for flashing after erase", "notesHtml": "

MeshCore EastMesh Observer with ESP-NOW Bridge

\n

EastMesh observer-eastmesh-bridge-espnow firmware for MeshCore boards that combine secure MQTT uplink with ESP-NOW bridge support, based on MeshCore firmware v1.15.0.

\n

This release includes the same Observer updates as observer-eastmesh-v2026.6.0, with ESP-NOW bridge support included.

\n

What's Changed

\n\n

Breaking Changes

\n

None.

\n

Notes

\n\n

Documentation

\n

xjarid.github.io/MeshCore-EastMesh

\n

Flashing

\n\n

Assets

\n\n" }, { "version": "observer-eastmesh-v2026.5.1", "name": "Observer EastMesh Firmware v1.15.0-eastmesh-v2026.5.1", "datetime": "2026-05-23T11:39:54Z", "url": "https://github.com/xJARiD/MeshCore-EastMesh/releases/tag/observer-eastmesh-v2026.5.1", "prerelease": false, "notes": "## MeshCore EastMesh Observer\r\n\r\nEastMesh `observer-eastmesh` firmware for MeshCore boards with secure MQTT uplink and optional local web management, based on MeshCore firmware `v1.15.0`.\r\n\r\nThis release renames the EastMesh MQTT observer firmware and release track, aligning release tags and PlatformIO target names with the new Observer naming.\r\n\r\n### What's Changed\r\n\r\n- Renamed the EastMesh MQTT release tag format from `repeater-mqtt-eastmesh-v*` to `observer-eastmesh-v*`.\r\n- Renamed `*_repeater_mqtt` PlatformIO environments and release artifact prefixes to `*_repeater_observer`.\r\n- Updated EastMesh release, local build, board, web panel, API, and CLI documentation to use Observer naming.\r\n\r\n### Breaking Changes\r\n\r\n- The EastMesh MQTT release tag format and PlatformIO target suffix changed to Observer naming.\r\n\r\n### Notes\r\n\r\n- `eastmesh-au` remains the recommended MQTT endpoint once `mqtt.iata` is configured.\r\n- For maximum heap headroom on busy observers, use the web panel for setup and troubleshooting, then disable it with `set web off`.\r\n- Browsers may still require accepting the self-signed certificate warning on first HTTPS access.\r\n- If upgrading from a build older than `observer-eastmesh-v1.3.11`, use the web `Start OTA` button if `start ota` sends you through an odd redirect.\r\n\r\n### Documentation\r\n\r\n[xjarid.github.io/MeshCore-EastMesh](https://xjarid.github.io/MeshCore-EastMesh/)\r\n\r\n### Flashing\r\n\r\n- [flasher.eastmesh.au](https://flasher.eastmesh.au/)\r\n- [flasher.meshcore.io](https://flasher.meshcore.io/)\r\n\r\n### Assets\r\n\r\n- `.bin` - standard update image\r\n- `-merged.bin` - full ESP32 image for flashing after erase", "notesHtml": "

MeshCore EastMesh Observer

\n

EastMesh observer-eastmesh firmware for MeshCore boards with secure MQTT uplink and optional local web management, based on MeshCore firmware v1.15.0.

\n

This release renames the EastMesh MQTT observer firmware and release track, aligning release tags and PlatformIO target names with the new Observer naming.

\n

What's Changed

\n\n

Breaking Changes

\n\n

Notes

\n\n

Documentation

\n

xjarid.github.io/MeshCore-EastMesh

\n

Flashing

\n\n

Assets

\n\n" }, { "version": "observer-eastmesh-bridge-espnow-v2026.5.1", "name": "Observer EastMesh Firmware with ESP-NOW Bridge v1.15.0-eastmesh-v2026.5.1", "datetime": "2026-05-23T11:39:36Z", "url": "https://github.com/xJARiD/MeshCore-EastMesh/releases/tag/observer-eastmesh-bridge-espnow-v2026.5.1", "prerelease": false, "notes": "## MeshCore EastMesh Observer with ESP-NOW Bridge\r\n\r\nEastMesh `observer-eastmesh-bridge-espnow` firmware for MeshCore boards that combine secure MQTT uplink with ESP-NOW bridge support, based on MeshCore firmware `v1.15.0`.\r\n\r\nThis release renames the EastMesh MQTT bridge observer firmware and release track, aligning release tags and PlatformIO target names with the new Observer naming.\r\n\r\n### What's Changed\r\n\r\n- Renamed the EastMesh MQTT bridge release tag format from `repeater-mqtt-bridge-eastmesh-v*` to `observer-eastmesh-bridge-espnow-v*`.\r\n- Renamed `*_repeater_mqtt_bridge` PlatformIO environments and release artifact prefixes to `*_repeater_observer_espnow`.\r\n- Updated EastMesh release, local build, board, and CLI documentation to use Observer ESP-NOW naming.\r\n\r\n### Breaking Changes\r\n\r\n- The EastMesh MQTT bridge release tag format and PlatformIO target suffix changed to Observer ESP-NOW naming.\r\n\r\n### Notes\r\n\r\n- This track is separate from `observer-eastmesh`.\r\n- Use `get wifi.status` to confirm the active 2.4 GHz Wi-Fi channel before setting `bridge.channel`.\r\n- `bridge.channel` should match the connected Wi-Fi channel for reliable ESP-NOW bridge operation.\r\n- For maximum heap headroom after setup, disable the web panel with `set web off`.\r\n\r\n### Documentation\r\n\r\n[xjarid.github.io/MeshCore-EastMesh](https://xjarid.github.io/MeshCore-EastMesh/)\r\n\r\n### Flashing\r\n\r\n- [flasher.eastmesh.au](https://flasher.eastmesh.au/)\r\n- [flasher.meshcore.io](https://flasher.meshcore.io/)\r\n\r\n### Assets\r\n\r\n- `.bin` - standard update image\r\n- `-merged.bin` - full ESP32 image for flashing after erase", "notesHtml": "

MeshCore EastMesh Observer with ESP-NOW Bridge

\n

EastMesh observer-eastmesh-bridge-espnow firmware for MeshCore boards that combine secure MQTT uplink with ESP-NOW bridge support, based on MeshCore firmware v1.15.0.

\n

This release renames the EastMesh MQTT bridge observer firmware and release track, aligning release tags and PlatformIO target names with the new Observer naming.

\n

What's Changed

\n\n

Breaking Changes

\n\n

Notes

\n\n

Documentation

\n

xjarid.github.io/MeshCore-EastMesh

\n

Flashing

\n\n

Assets

\n\n" }, { "version": "repeater-bridge-espnow-v1.15.0", "name": "Repeater ESP-NOW Bridge Firmware v1.15.0", "datetime": "2026-05-05T23:41:38Z", "url": "https://github.com/xJARiD/MeshCore-EastMesh/releases/tag/repeater-bridge-espnow-v1.15.0", "prerelease": false, "notes": "## MeshCore Repeater ESP-NOW Bridge\r\n\r\nRepeater ESP-NOW bridge firmware built from the upstream `meshcore-dev/MeshCore` firmware base.\r\n\r\nThis release packages the existing upstream bridge functionality as EastMesh release assets.\r\n\r\n### What's Changed\r\n\r\n- Added release builds for `repeater-bridge-espnow-v*` firmware artifacts.\r\n- Kept the version aligned with upstream MeshCore `v1.15.0`.\r\n\r\n### Breaking Changes\r\n\r\nNone.\r\n\r\n### Flashing\r\n\r\n- [flasher.meshcore.io](https://flasher.meshcore.io/)\r\n- [flasher.eastmesh.au](https://flasher.eastmesh.au/)\r\n\r\n### Assets\r\n\r\n- `.bin` - standard update image\r\n- `-merged.bin` - full ESP32 image for flashing after erase", "notesHtml": "

MeshCore Repeater ESP-NOW Bridge

\n

Repeater ESP-NOW bridge firmware built from the upstream meshcore-dev/MeshCore firmware base.

\n

This release packages the existing upstream bridge functionality as EastMesh release assets.

\n

What's Changed

\n\n

Breaking Changes

\n

None.

\n

Flashing

\n\n

Assets

\n\n" }, { "version": "companion-wifi-v1.15.0", "name": "Companion WiFi Firmware v1.15.0", "datetime": "2026-04-19T02:53:50Z", "url": "https://github.com/xJARiD/MeshCore-EastMesh/releases/tag/companion-wifi-v1.15.0", "prerelease": false, "notes": "## MeshCore EastMesh Companion WiFi\r\n\r\nThis is standard MeshCore companion WiFi firmware based on MeshCore `v1.15.0`, with a few extra Wi-Fi setup commands added for EastMesh.\r\n\r\n### What’s Different\r\n\r\nThe only EastMesh-specific addition is a small set of Wi-Fi CLI commands that let you view and save Wi-Fi settings:\r\n\r\n- `get wifi.status`\r\n- `get wifi.ssid`\r\n- `get wifi.powersaving`\r\n- `set wifi.ssid `\r\n- `set wifi.pwd `\r\n- `set wifi.powersaving none|min|max`\r\n\r\n### Notes\r\n\r\n- Everything else behaves like the normal MeshCore companion WiFi firmware\r\n- Use the file that matches your board exactly\r\n- Companion WiFi releases use the upstream MeshCore version number\r\n\r\n### Documentation\r\n\r\nhttps://xjarid.github.io/MeshCore-EastMesh/\r\n\r\n### Flashing\r\n\r\n- https://flasher.eastmesh.au/\r\n- https://flasher.meshcore.io/\r\n\r\n### Assets\r\n\r\n- `.bin` – standard update\r\n- `-merged.bin` – full image (after erase, ESP32)", "notesHtml": "

MeshCore EastMesh Companion WiFi

\n

This is standard MeshCore companion WiFi firmware based on MeshCore v1.15.0, with a few extra Wi-Fi setup commands added for EastMesh.

\n

What’s Different

\n

The only EastMesh-specific addition is a small set of Wi-Fi CLI commands that let you view and save Wi-Fi settings:

\n
    \n
  • get wifi.status
    • \n
  • get wifi.ssid
    • \n
  • get wifi.powersaving
    • \n
  • set wifi.ssid <ssid>
    • \n
  • set wifi.pwd <password>
    • \n
  • set wifi.powersaving none|min|max
    • \n
\n

Notes

\n
    \n
  • Everything else behaves like the normal MeshCore companion WiFi firmware
    • \n
  • Use the file that matches your board exactly
    • \n
  • Companion WiFi releases use the upstream MeshCore version number
    • \n
\n

Documentation

\n

https://xjarid.github.io/MeshCore-EastMesh/

\n

Flashing

\n\n

Assets

\n
    \n
  • .bin – standard update
    • \n
  • -merged.bin – full image (after erase, ESP32)
    • \n
\n" }, { "version": "companion-wifi-v1.14.1", "name": "Companion WiFi Firmware v1.14.1", "datetime": "2026-04-09T07:16:35Z", "url": "https://github.com/xJARiD/MeshCore-EastMesh/releases/tag/companion-wifi-v1.14.1", "prerelease": false, "notes": "## MeshCore EastMesh Companion WiFi\r\n\r\nThis release publishes the EastMesh `companion_radio_wifi` builds for supported boards.\r\n\r\n### Highlights\r\n\r\n- WiFi-enabled companion firmware builds for EastMesh-supported MeshCore boards\r\n- Local build and release flow now standardized through `uv`\r\n- Persisted companion WiFi rescue commands added:\r\n - `get wifi.status`\r\n - `get wifi.ssid`\r\n - `get wifi.powersaving`\r\n - `set wifi.ssid `\r\n - `set wifi.pwd `\r\n - `set wifi.powersaving none|min|max`\r\n- EastMesh release automation and docs flow now in place\r\n\r\n### Notes\r\n\r\n- This release uses the upstream MeshCore firmware version for `FIRMWARE_VERSION`\r\n- Use the asset that matches your board exactly\r\n- For flashing custom firmware, use:\r\n - https://flasher.meshcore.io/\r\n\r\n### Documentation\r\n\r\nTemporary docs home:\r\n- https://xjarid.github.io/MeshCore-EastMesh/\r\n\r\n### Assets\r\n\r\n- `.bin` = normal update / incremental flash\r\n- `-merged.bin` = clean flash after erase on supported ESP32 targets", "notesHtml": "

MeshCore EastMesh Companion WiFi

\n

This release publishes the EastMesh companion_radio_wifi builds for supported boards.

\n

Highlights

\n
    \n
  • WiFi-enabled companion firmware builds for EastMesh-supported MeshCore boards
    • \n
  • Local build and release flow now standardized through uv
    • \n
  • Persisted companion WiFi rescue commands added:
      \n
    • get wifi.status
      • \n
    • get wifi.ssid
      • \n
    • get wifi.powersaving
      • \n
    • set wifi.ssid <ssid>
      • \n
    • set wifi.pwd <password>
      • \n
    • set wifi.powersaving none|min|max
      • \n
    \n
    • \n
  • EastMesh release automation and docs flow now in place
    • \n
\n

Notes

\n
    \n
  • This release uses the upstream MeshCore firmware version for FIRMWARE_VERSION
    • \n
  • Use the asset that matches your board exactly
    • \n
  • For flashing custom firmware, use:\n
    • \n
\n

Documentation

\n

Temporary docs home:

\n\n

Assets

\n
    \n
  • .bin = normal update / incremental flash
    • \n
  • -merged.bin = clean flash after erase on supported ESP32 targets
    • \n
\n" } ], "changelogSource": "github", "changelogUpdatedAt": "2026-06-21T09:55:28.646Z" }, { "id": "easyskymesh", "name": "EasySkyMesh", "type": "fork", "maintainer": "IoTThinks", "description": "A power-saving oriented MeshCore firmware with experimental, advanced features and bug fixes aimed at ultra-low-power repeater and sensor deployments. Targets extended battery life (e.g. ~16µA power-off) with the intent of upstreaming improvements into MeshCore.\n", "repository": "https://github.com/IoTThinks/EasySkyMesh", "website": "https://iotthinks.com", "license": "MIT", "status": "active", "lifecycle": "active", "maturity": "beta", "distribution": "community", "lineage": { "kind": "fork", "upstreamFirmwareId": "meshcore-official", "upstreamRepository": "https://github.com/meshcore-dev/MeshCore" }, "runtime": { "framework": "arduino", "language": "cpp" }, "roles": [ "repeater", "sensor" ], "features": [ "Ultra-low-power operation (~16µA power-off)", "Sensor integration", "Auto-reboot / watchdog", "Long-range mesh messaging" ], "capabilities": { "protocol": { "meshcoreCompatible": true }, "transports": { "ble": true, "usbSerial": true, "nativeTcp": false, "wifiAp": true }, "operations": { "ota": true, "webFlasher": false }, "networking": { "repeater": true, "roomServer": false, "observer": false, "kissModem": false }, "hardware": { "gps": true, "display": true, "sensors": true, "lowPowerRx": true } }, "devices": [ { "id": "heltec-v3", "status": "supported" }, { "id": "heltec-wsl3", "status": "supported" }, { "id": "heltec-v4", "status": "supported" }, { "id": "heltec-v4-exp", "status": "supported" }, { "id": "heltec-t096", "status": "supported" }, { "id": "heltec-t114", "status": "supported" }, { "id": "rak-4631", "status": "supported" }, { "id": "uart-solar-node-station", "status": "supported" }, { "id": "xiao-esp32s3", "status": "partial", "notes": "Power-saving figures vary by board revision." }, { "id": "xiao-esp32c3", "status": "supported" }, { "id": "xiao-nrf52", "status": "supported" } ], "popularity": { "githubStars": 162, "githubForks": 6, "githubWatchers": 9, "githubOpenIssues": 2, "githubContributors": 1, "releaseDownloads": 8018, "latestReleaseDownloads": 1073, "lastChecked": "2026-06-21" }, "verification": { "sourceAvailable": true, "releasesAvailable": true, "ciBuilds": false, "lastChecked": "2026-06-21" }, "latest_version": "PowerSaving16", "released": "2026-06-08", "releases": [ { "version": "PowerSaving16", "name": "Power Saving 16: Poweroff at 16uA, T096 at 8.7mA and auto reboot", "datetime": "2026-06-08T14:58:49Z", "url": "https://github.com/IoTThinks/EasySkyMesh/releases/tag/PowerSaving16", "prerelease": false, "notes": "## Keep making 1-2W solar repeaters and 5-day BLE companions possible:\r\n- Developed by IoTThinks and tested by our supportive MeshCore friends.\r\n- Contribution to MeshCore: [By IoTThinks](https://github.com/meshcore-dev/MeshCore/issues?q=(state%3Aopen%20OR%20state%3Amerged)%20is%3Apr%20author%3A%40IoTThinks).\r\n- Source code: https://github.com/IoTThinks/MeshCore/tree/PowerSaving-v16\r\n\r\nThe power consumption of common boards is measured at battery cable. Ping us if your boards are not low power as expected.\r\n| Board | Repeaters / Room Servers | BLE Companions | Power Off for BLE Companions |\r\n| ------------- | ------------- | ------------- | ------------- |\r\n| Heltec v3 | 9mA | 19.6mA | ~16uA |\r\n| Heltec v4.2 and v4.3 (FEM ON) | 16mA | 28.6mA | ~16uA |\r\n| Heltec v4.3 (FEM Off) | 13mA | 24.9 mA | ~16uA |\r\n| Xiao S3, C3 | 7mA | 15 mA | ~16uA |\r\n| Xiao C6 | 7mA | C6 is not supported yet | ~16uA |\r\n| RAK 4631, Heltec T114, Xiao NRF52 | 5.8mA | 5.8mA | ~16uA |\r\n| Heltec T096 (FEM Off) | 8.7mA | 8.6 mA | ~16uA |\r\n| Heltec T096 (FEM On) | 16mA | 16 mA | ~16uA |\r\n\r\n## Support Us\r\n* Enjoying our work? \r\n* Support us via [![Sponsor](https://img.shields.io/badge/Paypal-IoTThinks-0070ba?style=flat&logo=paypal&logoColor=white&labelColor=0070ba&color=555555)](https://www.paypal.com/ncp/payment/6FGWJJVC572VL) or [![Sponsor](https://img.shields.io/badge/GitHub%20Sponsors-IoTThinks-ea4aaa?style=flat&logo=github-sponsors&logoColor=white&labelColor=ea4aaa&color=555555)](https://github.com/sponsors/IoTThinks).\r\n\r\n### Known issues and Patches:\r\n- For repeaters / room servers, after upgrade to PowerSaving 16, you need to check and set the default values again `set flood.max 64` (default value) , `set flood.max.unscoped 64` (default value) and `set radio.fem.rxgain on/off` (Heltec v4.3 and T096 only, if you set \"off\" before) https://github.com/meshcore-dev/MeshCore/pull/2140#issuecomment-4677295983\r\n- [Fixed in v16.0.1] Wio Tracker L1 BLE companion has high power consumption is at 35mA in PowerSaving 16 instead of 7.5mA as in PowerSaving 15. This issue might affect a few NRF52 boards with GPS modules attached.\r\n\r\n### Instruction:\r\n- Scroll down to bottom to download uf2 / upgrade.bin to upgrade or freshInstall-merged.bin for new devices. \r\n- Heltec v4 bin files is for both Heltec v4.2 and v4.3. Heltec v4.3 bin files is for Heltec v4.3 only\r\n- Heltec v4.3 and T096 have two options FEM RXgain on and FEM Rxgain off.\r\n- Flash Custom Firmware as in [INSTRUCTION](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Instruction-to-flash-firmware.md).\r\n- If your board is not at the bottom section, please request us at [GITHUB](https://github.com/IoTThinks/EasySkyMesh/discussions/categories/ideas)\r\n- Fast support: [Discord](https://discord.com/channels/1472633259799220224/1472634841077121144)\r\n\r\n## Features: \r\nBased on [MeshCore 1.16](https://blog.meshcore.io/2026/06/06/release-1-16-0), plus PowerSaving features and more:\r\n- Repeaters and room servers for both ESP32 and NRF52: CLI `powersaving on`, `powersaving off `and `powersaving`\r\n- BLE companions for both ESP32 and NRF52: Enabled by default\r\n- [NEW] Hibernate mode for ESP32 BLE Companions now work properly and at 16uA\r\n- [NEW] Optimize Heltec T096 from 12mA down to 8.7mA\r\n- [NEW] Repeaters for both ESP32 and NRF52: CLI `set reboot.interval ` and `get reboot.interval`. hours is 0-255. 0 is default and disabled. This helps to recover repeaters due to unknown hang.\r\n- [NEW] Set return path for repeaters: https://github.com/meshcore-dev/MeshCore/pull/2586\r\n- [NEW] Add time keeping for NRF52 across resets: https://github.com/meshcore-dev/MeshCore/pull/2704\r\n- FEM LNA for Heltec v4.3, Heltec T096, Heltec TrackerV2: CLI `set radio.fem.rxgain on/off` and `get radio.fem.rxgain`. https://github.com/meshcore-dev/MeshCore/pull/2140\r\n- Automatically select I2C address (0x76 or 0x77) for BME280, BME680 and BMP680.\r\n- Fixed boot loop for Xiao C6: https://github.com/meshcore-dev/MeshCore/pull/2570\r\n- Ch\n…", "notesHtml": "

Keep making 1-2W solar repeaters and 5-day BLE companions possible:

\n\n

The power consumption of common boards is measured at battery cable. Ping us if your boards are not low power as expected.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
BoardRepeaters / Room ServersBLE CompanionsPower Off for BLE Companions
Heltec v39mA19.6mA~16uA
Heltec v4.2 and v4.3 (FEM ON)16mA28.6mA~16uA
Heltec v4.3 (FEM Off)13mA24.9 mA~16uA
Xiao S3, C37mA15 mA~16uA
Xiao C67mAC6 is not supported yet~16uA
RAK 4631, Heltec T114, Xiao NRF525.8mA5.8mA~16uA
Heltec T096 (FEM Off)8.7mA8.6 mA~16uA
Heltec T096 (FEM On)16mA16 mA~16uA
\n

Support Us

\n
    \n
  • Enjoying our work?
    • \n
  • Support us via \"Sponsor\" or \"Sponsor\".
    • \n
\n

Known issues and Patches:

\n
    \n
  • For repeaters / room servers, after upgrade to PowerSaving 16, you need to check and set the default values again set flood.max 64 (default value) , set flood.max.unscoped 64 (default value) and set radio.fem.rxgain on/off (Heltec v4.3 and T096 only, if you set \"off\" before) https://github.com/meshcore-dev/MeshCore/pull/2140#issuecomment-4677295983
    • \n
  • [Fixed in v16.0.1] Wio Tracker L1 BLE companion has high power consumption is at 35mA in PowerSaving 16 instead of 7.5mA as in PowerSaving 15. This issue might affect a few NRF52 boards with GPS modules attached.
    • \n
\n

Instruction:

\n
    \n
  • Scroll down to bottom to download uf2 / upgrade.bin to upgrade or freshInstall-merged.bin for new devices.
    • \n
  • Heltec v4 bin files is for both Heltec v4.2 and v4.3. Heltec v4.3 bin files is for Heltec v4.3 only
    • \n
  • Heltec v4.3 and T096 have two options FEM RXgain on and FEM Rxgain off.
    • \n
  • Flash Custom Firmware as in INSTRUCTION.
    • \n
  • If your board is not at the bottom section, please request us at GITHUB
    • \n
  • Fast support: Discord
    • \n
\n

Features:

\n

Based on MeshCore 1.16, plus PowerSaving features and more:

\n
    \n
  • Repeaters and room servers for both ESP32 and NRF52: CLI powersaving on, powersaving off and powersaving
    • \n
  • BLE companions for both ESP32 and NRF52: Enabled by default
    • \n
  • [NEW] Hibernate mode for ESP32 BLE Companions now work properly and at 16uA
    • \n
  • [NEW] Optimize Heltec T096 from 12mA down to 8.7mA
    • \n
  • [NEW] Repeaters for both ESP32 and NRF52: CLI set reboot.interval <hours> and get reboot.interval. hours is 0-255. 0 is default and disabled. This helps to recover repeaters due to unknown hang.
    • \n
  • [NEW] Set return path for repeaters: https://github.com/meshcore-dev/MeshCore/pull/2586
    • \n
  • [NEW] Add time keeping for NRF52 across resets: https://github.com/meshcore-dev/MeshCore/pull/2704
    • \n
  • FEM LNA for Heltec v4.3, Heltec T096, Heltec TrackerV2: CLI set radio.fem.rxgain on/off and get radio.fem.rxgain. https://github.com/meshcore-dev/MeshCore/pull/2140
    • \n
  • Automatically select I2C address (0x76 or 0x77) for BME280, BME680 and BMP680.
    • \n
  • Fixed boot loop for Xiao C6: https://github.com/meshcore-dev/MeshCore/pull/2570
    • \n
  • Ch\n…
    • \n
\n" }, { "version": "PowerSaving15", "name": "Power Saving 15: 15mA for ESP32 BLE Companions and no time-drift for repeaters", "datetime": "2026-04-24T23:58:53Z", "url": "https://github.com/IoTThinks/EasySkyMesh/releases/tag/PowerSaving15", "prerelease": false, "notes": "## Based on MeshCore v1.15 plus the below features:\r\n* Developed by IoTThinks and tested by our supportive friends and MeshCore community.\r\n* Current Contribution to Meshcore: [By IoTThinks](https://github.com/meshcore-dev/MeshCore/issues?q=(state%3Aopen%20OR%20state%3Amerged)%20is%3Apr%20author%3A%40IoTThinks). You may feedback there to get them merged faster to MeshCore main stream.\r\n* If you want us to compile for your boards or have question, please comment in [GITHUB](https://github.com/IoTThinks/EasySkyMesh/discussions/categories/ideas) or [DISCORD](https://discord.com/channels/1472633259799220224/1472634841077121144)\r\n\r\nUpdates:\r\n* 15 May 2026: PS v15.0.2: Fixed boot loop due to flash mode for Xiao C6\r\n* 10 May 2026: PS v15.0.2: Fixed FEM Off version for T096 BLE companions. The external LNA was fixed to off properly to reach -115 dbm noise floor.\r\n* 04 May 2026: [BLE Companions for ESP32] PS v15.0.1: Skipped sleep when BLE read is busy and reduced sleep period from 50ms to 10ms.\r\n* 27 April 2026: [Heltec v4 repeaters and room servers] PS v15.0.1: Applied latest changes in https://github.com/meshcore-dev/MeshCore/pull/2140. Fixed missing `get radio.fem.rxgrain` and not persisted `radio.fem.rxgrain` accross reboots.\r\n\r\n## Support Us\r\n* Enjoying our work? \r\n* Support us via [![Sponsor](https://img.shields.io/badge/Paypal-IoTThinks-0070ba?style=flat&logo=paypal&logoColor=white&labelColor=0070ba&color=555555)](https://www.paypal.com/ncp/payment/6FGWJJVC572VL) or [![Sponsor](https://img.shields.io/badge/GitHub%20Sponsors-IoTThinks-ea4aaa?style=flat&logo=github-sponsors&logoColor=white&labelColor=ea4aaa&color=555555)](https://github.com/sponsors/IoTThinks).\r\n\r\n### STAR Features:\r\n- **ESP32 BLE Companions**: Officially support PowerSaving for **ALL ESP32/S3/C3** BLE Companions. Fast loading of channels and contacts. Fixed hibernation mode for Heltec v3 and v4. ESP32C6 (including Xiao C6) is not supported yet.\r\n\r\n| Board | Power Consumption |\r\n| ------------- | ------------- |\r\n| Heltec v3 | 100 mA => 19.6 mA |\r\n| Heltec v4.2 and v4.3 (FEM ON) | 120mA => 24.9mA |\r\n| Heltec v4.3 (FEM Off) | 120mA => 18mA |\r\n| Xiao S3 | 7x mA => 16.3 mA |\r\n| Xiao C3 | 7xmA => 15.1mA |\r\n\r\n- [BETA] Repeater and room servers: **No time drift** by applying a time adjustment offset during \"`powersaving on`\"\r\n\r\n### Power Saving:\r\n* Latest Power Saving to Repeater, Room Server and BLE Companion.\r\n* One 3000mAh battery can last an ESP32 repeaters, room servers and BLE companions for a week.\r\n\r\n| Role | NRF52 | ESP32 | CLI Commands |\r\n| ------------- | ------------- | ------------- | ------------- |\r\n| Repeater / Room Server | 8mA => 5.8mA | 50+mA => 10-13mA | powersaving on, powersaving off, powersaving |\r\n| BLE Companion | 12mA => 5.8mA | 120mA => 15-20mA | Enabled by default |\r\n\r\n### Extra Features:\r\n* Merged to add CLI control to LoRa's FEM LNA: https://github.com/meshcore-dev/MeshCore/pull/2140. CLI: `set radio.fem.rxgrain on/off` and `get radio.fem.rxgrain`\r\n* Added CLI \"**powerlog**\" to list the last reset reason, last shutdown reason (NRF52 only) and last boot voltage (NRF52 only). This is to help debugging why the boards were reset due to software fault or low voltage (brownout).\r\n* Included sensor CLI to list I2C and UART GPIOs: sensor\r\n* Merged to keep date after crash/watchdog/brownout reset on ESP32: https://github.com/meshcore-dev/MeshCore/pull/1896\r\n* Automatically selected I2C address 0x76 and 0x77 for BME280/BME680/BMP280\r\n* Added i2c probe for sensors to start only in-use sensors.\r\n* Added variant Xiao S3 (non-Wio) and Wio SX1262 (Initial support): SDA=D6, SCL=D7 https://github.com/meshcore-dev/MeshCore/pull/2383\r\n\r\n## Instruction:\r\nPlease upgrade your **easy to access devices** first.\r\n* Download: Download **upgrade.bin** to upgrade existing devices or **freshInstall-merged.bin** for new devices.\r\n* Instruction to [Flash Custom Firmware](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Instruction-to-flash-firmware.md)\n…", "notesHtml": "

Based on MeshCore v1.15 plus the below features:

\n
    \n
  • Developed by IoTThinks and tested by our supportive friends and MeshCore community.
    • \n
  • Current Contribution to Meshcore: By IoTThinks. You may feedback there to get them merged faster to MeshCore main stream.
    • \n
  • If you want us to compile for your boards or have question, please comment in GITHUB or DISCORD
    • \n
\n

Updates:

\n
    \n
  • 15 May 2026: PS v15.0.2: Fixed boot loop due to flash mode for Xiao C6
    • \n
  • 10 May 2026: PS v15.0.2: Fixed FEM Off version for T096 BLE companions. The external LNA was fixed to off properly to reach -115 dbm noise floor.
    • \n
  • 04 May 2026: [BLE Companions for ESP32] PS v15.0.1: Skipped sleep when BLE read is busy and reduced sleep period from 50ms to 10ms.
    • \n
  • 27 April 2026: [Heltec v4 repeaters and room servers] PS v15.0.1: Applied latest changes in https://github.com/meshcore-dev/MeshCore/pull/2140. Fixed missing get radio.fem.rxgrain and not persisted radio.fem.rxgrain accross reboots.
    • \n
\n

Support Us

\n
    \n
  • Enjoying our work?
    • \n
  • Support us via \"Sponsor\" or \"Sponsor\".
    • \n
\n

STAR Features:

\n
    \n
  • ESP32 BLE Companions: Officially support PowerSaving for ALL ESP32/S3/C3 BLE Companions. Fast loading of channels and contacts. Fixed hibernation mode for Heltec v3 and v4. ESP32C6 (including Xiao C6) is not supported yet.
    • \n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
BoardPower Consumption
Heltec v3100 mA => 19.6 mA
Heltec v4.2 and v4.3 (FEM ON)120mA => 24.9mA
Heltec v4.3 (FEM Off)120mA => 18mA
Xiao S37x mA => 16.3 mA
Xiao C37xmA => 15.1mA
\n
    \n
  • [BETA] Repeater and room servers: No time drift by applying a time adjustment offset during \"powersaving on\"
    • \n
\n

Power Saving:

\n
    \n
  • Latest Power Saving to Repeater, Room Server and BLE Companion.
    • \n
  • One 3000mAh battery can last an ESP32 repeaters, room servers and BLE companions for a week.
    • \n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
RoleNRF52ESP32CLI Commands
Repeater / Room Server8mA => 5.8mA50+mA => 10-13mApowersaving on, powersaving off, powersaving
BLE Companion12mA => 5.8mA120mA => 15-20mAEnabled by default
\n

Extra Features:

\n
    \n
  • Merged to add CLI control to LoRa's FEM LNA: https://github.com/meshcore-dev/MeshCore/pull/2140. CLI: set radio.fem.rxgrain on/off and get radio.fem.rxgrain
    • \n
  • Added CLI \"powerlog\" to list the last reset reason, last shutdown reason (NRF52 only) and last boot voltage (NRF52 only). This is to help debugging why the boards were reset due to software fault or low voltage (brownout).
    • \n
  • Included sensor CLI to list I2C and UART GPIOs: sensor
    • \n
  • Merged to keep date after crash/watchdog/brownout reset on ESP32: https://github.com/meshcore-dev/MeshCore/pull/1896
    • \n
  • Automatically selected I2C address 0x76 and 0x77 for BME280/BME680/BMP280
    • \n
  • Added i2c probe for sensors to start only in-use sensors.
    • \n
  • Added variant Xiao S3 (non-Wio) and Wio SX1262 (Initial support): SDA=D6, SCL=D7 https://github.com/meshcore-dev/MeshCore/pull/2383
    • \n
\n

Instruction:

\n

Please upgrade your easy to access devices first.

\n
    \n
  • Download: Download upgrade.bin to upgrade existing devices or freshInstall-merged.bin for new devices.
    • \n
  • Instruction to Flash Custom Firmware\n…
    • \n
\n" }, { "version": "PowerSaving14.1", "name": "Power Saving 14.1: Heltec v4.3 at 5.5mA, FEM LNA control and powerlog", "datetime": "2026-03-27T12:38:20Z", "url": "https://github.com/IoTThinks/EasySkyMesh/releases/tag/PowerSaving14.1", "prerelease": false, "notes": "### Based on MeshCore v1.14.1 plus the below features:\r\n* 16 April 2026 -v14.1.1: Disabled NRF52_POWER_MANAGEMENT for RAK4631, RAK3401, Heltec T114, Xiao NRF52, Senscap Solar and Ga562_30s meshkit and Ga562_30s mesh tracker pro.\r\n* 10 Arpril 2026 - v14.1.1: **[BETA]** Added Power saving for Heltec v3, v4.2 and v4.3 companion BLE. Reduced from 120mA down to 32mA for Heltec v3 and 39mA for Heltec v4. LNA and FEM LNA use default settings (E.g On).\r\n* 09 April 2026 - v14.1.1: Fixed reset issue in high traffic locations for ESP32-based repeaters and room servers.\r\n\r\n#### NEW FEATURES:\r\n* Added Heltec v4.3 support: https://github.com/meshcore-dev/MeshCore/pull/1867. The PR will automatically detect Heltec v4.2 and v4.3.\r\n* Added CLI control to LoRa's FEM LNA: https://github.com/meshcore-dev/MeshCore/pull/2140. Heltec T090 is not included. The details are below.\r\n* Added CLI \"**powerlog**\" to list the last reset reason, last shutdown reason (NRF52 only) and last boot voltage (NRF52 only). This is to help debugging why the boards were reset due to software fault or low voltage (brownout).\r\n\r\nFEM LNA vs. Chip LNA:\r\n* FEM LNA is external LNA from the 1W boards (such as Heltec v4.3). You can on / off this FEM LNA: **set/get radio.fem.rxgain on/off.** This will impact the RX gain and power consumption (up to 7.8mA). When this is off, Heltec v4.3 can reach 5.8mA. For Heltec v4.2, this CLI will return \"Not supported\" as it does not support FEM control.\r\n* Chip LNA inside SX1262: This is available to all boards including 1W boards. You can on/off this LNA : **set/get radio.rxgain on/off**. This will impact the RX gain and power consumption (up to 0.5mA)\r\n \r\n#### Repeaters and Room Servers:\r\n* Included latest PowerSaving and PowerSaving CLI (powersaving, **powersaving on** and powersaving off): **5.0mA** for NRF52, 10mA for Heltec v3, 13mA for Heltec v4.2 and **5.5 mA for Heltec v4.3** (with FEM off). https://github.com/meshcore-dev/MeshCore/pull/1687\r\n\r\n #### Companions:\r\n* [NRF52] PowerSaving by default. Reduced from 9mA down to **5.8mA**. https://github.com/meshcore-dev/MeshCore/pull/2286\r\n* **[BETA]** [ESP32] PowerSaving by default for Heltec v3 and v4. Reduced from 120mA down to 32mA for Heltec v3 and 39mA for Heltec v4.2 and 4.3.\r\n\r\n#### Common features\r\n* Included sensor CLI to list I2C and UART GPIOs: sensor\r\n* Kept date after crash/watchdog/brownout reset on ESP32: https://github.com/meshcore-dev/MeshCore/pull/1896\r\n* Automatically selected I2C address 0x76 and 0x77 for BME280/BME680/BMP280\r\n* Added i2c probe for sensors to start only in-use sensors: https://github.com/meshcore-dev/MeshCore/pull/1282\r\n* Added variant Xiao S3 (non-Wio) and Wio SX1262 (Initial support): SDA=D6, SCL=D7\r\n\r\n## Instruction:\r\nPlease upgrade your **easy to access devices** first.\r\n* Download: Download **upgrade.bin** to upgrade existing devices or **freshInstall-merged.bin** for new devices.\r\n* Instruction to [Flash Custom Firmware](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Instruction-to-flash-firmware.md).\r\n* Please read the instruction in [Add sensors to repeaters](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Add-sensors-to-repeaters.md)\r\n* Source code for [PowerSaving 14](https://github.com/IoTThinks/MeshCore/tree/PowerSaving-v14.1)\r\n\r\n## Demo\r\n#### Power Saving\r\n* Enter powersaving mode (CLI > powersaving on),\r\n* 5.5mA for Heltec v4.3 with FEM and rxgain off, 5.8mA if FEM off and rxgain on. Thanks **Wireless Rocks** for your testing, .\r\n* 13mA for Heltec v4.2 or Heltec V4.3 with FEM and rxgain on.\r\n* 5.0mA for RAK4631\r\n\r\n\"image\"\r\n\"image\"\r\n\"image\"\r\n\r\n* Default PowerSaving for Heltec v3, v4.2 and\n…", "notesHtml": "

Based on MeshCore v1.14.1 plus the below features:

\n
    \n
  • 16 April 2026 -v14.1.1: Disabled NRF52_POWER_MANAGEMENT for RAK4631, RAK3401, Heltec T114, Xiao NRF52, Senscap Solar and Ga562_30s meshkit and Ga562_30s mesh tracker pro.
    • \n
  • 10 Arpril 2026 - v14.1.1: [BETA] Added Power saving for Heltec v3, v4.2 and v4.3 companion BLE. Reduced from 120mA down to 32mA for Heltec v3 and 39mA for Heltec v4. LNA and FEM LNA use default settings (E.g On).
    • \n
  • 09 April 2026 - v14.1.1: Fixed reset issue in high traffic locations for ESP32-based repeaters and room servers.
    • \n
\n

NEW FEATURES:

\n
    \n
  • Added Heltec v4.3 support: https://github.com/meshcore-dev/MeshCore/pull/1867. The PR will automatically detect Heltec v4.2 and v4.3.
    • \n
  • Added CLI control to LoRa's FEM LNA: https://github.com/meshcore-dev/MeshCore/pull/2140. Heltec T090 is not included. The details are below.
    • \n
  • Added CLI \"powerlog\" to list the last reset reason, last shutdown reason (NRF52 only) and last boot voltage (NRF52 only). This is to help debugging why the boards were reset due to software fault or low voltage (brownout).
    • \n
\n

FEM LNA vs. Chip LNA:

\n
    \n
  • FEM LNA is external LNA from the 1W boards (such as Heltec v4.3). You can on / off this FEM LNA: set/get radio.fem.rxgain on/off. This will impact the RX gain and power consumption (up to 7.8mA). When this is off, Heltec v4.3 can reach 5.8mA. For Heltec v4.2, this CLI will return \"Not supported\" as it does not support FEM control.
    • \n
  • Chip LNA inside SX1262: This is available to all boards including 1W boards. You can on/off this LNA : set/get radio.rxgain on/off. This will impact the RX gain and power consumption (up to 0.5mA)
    • \n
\n

Repeaters and Room Servers:

\n
    \n
  • Included latest PowerSaving and PowerSaving CLI (powersaving, powersaving on and powersaving off): 5.0mA for NRF52, 10mA for Heltec v3, 13mA for Heltec v4.2 and 5.5 mA for Heltec v4.3 (with FEM off). https://github.com/meshcore-dev/MeshCore/pull/1687
    • \n
\n

Companions:

\n
    \n
  • [NRF52] PowerSaving by default. Reduced from 9mA down to 5.8mA. https://github.com/meshcore-dev/MeshCore/pull/2286
    • \n
  • [BETA] [ESP32] PowerSaving by default for Heltec v3 and v4. Reduced from 120mA down to 32mA for Heltec v3 and 39mA for Heltec v4.2 and 4.3.
    • \n
\n

Common features

\n\n

Instruction:

\n

Please upgrade your easy to access devices first.

\n\n

Demo

\n

Power Saving

\n
    \n
  • Enter powersaving mode (CLI > powersaving on),
    • \n
  • 5.5mA for Heltec v4.3 with FEM and rxgain off, 5.8mA if FEM off and rxgain on. Thanks Wireless Rocks for your testing, .
    • \n
  • 13mA for Heltec v4.2 or Heltec V4.3 with FEM and rxgain on.
    • \n
  • 5.0mA for RAK4631
    • \n
\n\"image\"\n\"image\"\n\"image\"
    \n
  • Default PowerSaving for Heltec v3, v4.2 and\n…
    • \n
\n" }, { "version": "PowerSaving14", "name": "Power Saving 14: Bringing PowerSaving to Room Servers and Companions", "datetime": "2026-03-13T09:01:28Z", "url": "https://github.com/IoTThinks/EasySkyMesh/releases/tag/PowerSaving14", "prerelease": false, "notes": "## Based on MeshCore v1.14 plus the below features and bug fixes:\r\n\r\n## Repeater:\r\n+ Included latest PowerSaving and PowerSaving CLI (powersaving, powersaving on and powersaving off): 5.8mA for NRF52, 10mA for Heltec v3 and 13mA for Heltec v4. https://github.com/meshcore-dev/MeshCore/pull/1687\r\n+ [COMING SOON] Modbus RS485 support is coming soon...\r\n\r\n## Room server:\r\n+ Added latest PowerSaving and PowerSaving CLI (powersaving, powersaving on and powersaving off): 5.8mA for NRF52, 10mA for Heltec v3 and 13mA for Heltec v4.\r\n+ Added MCU temperature\r\n\r\n## Companion:\r\n+ [NRF52] Added PowerSaving. Reduced from 9mA down to 5.8mA.\r\n+ [ESP32] PowerSaving is coming soon...\r\n\r\n## Common:\r\n+ Included sensor CLI to list I2C and UART GPIOs: sensor\r\n+ Kept date after crash/watchdog/brownout reset on ESP32: https://github.com/meshcore-dev/MeshCore/pull/1896\r\n+ Fixed hasPendingWork for TX queue: https://github.com/meshcore-dev/MeshCore/pull/1877\r\n+ Automatically selected I2C address 0x76 and 0x77 for BME280/BME680/BMP280\r\n+ Added i2c probe for sensors to start only in-use sensors: https://github.com/meshcore-dev/MeshCore/pull/1282\r\n+ Added variant Xiao S3 (non-Wio) and Wio SX1262 (Initial support): SDA=D6, SCL=D7\r\n\r\n## Instruction:\r\nPlease upgrade your **easy to access repeaters / room servers** first.\r\n* Instruction to [Flash Custom Firmware](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Instruction-to-flash-firmware.md)\r\n* Please read the instruction in [Add sensors to repeaters](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Add-sensors-to-repeaters.md)\r\n* Source code for [PowerSaving 14](https://github.com/IoTThinks/MeshCore/tree/PowerSaving-v14)\r\n\r\n## Support and Discussion\r\n* If you want us to compile for your boards or have question, please comment in [GITHUB](https://github.com/IoTThinks/EasySkyMesh/discussions/categories/ideas) or [DISCORD](https://discord.com/channels/1472633259799220224/1472634841077121144)\r\n\r\n## Love the build?\r\n* You may buy us a cofee ☕ for good work via Paypal [![Buy me a coffee](https://img.shields.io/badge/Buy%20me%20a%20coffee-iotthinks-0070ba?style=flat&logo=paypal&logoColor=white&labelColor=0070ba&color=555555)](https://www.paypal.com/paypalme/iotthinks/9usd) or Github [![Sponsor](https://img.shields.io/badge/Sponsor-iotthinks-ea4aaa?style=flat&logo=github-sponsors&logoColor=white&labelColor=ea4aaa&color=555555)](https://github.com/sponsors/IoTThinks).\r\nWe can buy more test boards and test sensors for development.\r\n\r\n## Demo\r\n* Enter powersaving mode (CLI > powersaving on), 5.8mA for RAK4631 / Xiao NRF52, 6mA for Xiao S6/C3/C6, 10mA for Heltec v3, 13mA for Heltec v4...\r\n\"image\"\r\n\"image\"\r\n\"image\"\r\n\r\n* Enter CLI \"powersaving\", \"powersaving on\" and \"powersaving off\" with detailed responses\r\n* Enter CLI \"sensor\" to check I2C and GPS Serial pins\r\n\"image\" \r\n\"image\"", "notesHtml": "

Based on MeshCore v1.14 plus the below features and bug fixes:

\n

Repeater:

\n
    \n
  • Included latest PowerSaving and PowerSaving CLI (powersaving, powersaving on and powersaving off): 5.8mA for NRF52, 10mA for Heltec v3 and 13mA for Heltec v4. https://github.com/meshcore-dev/MeshCore/pull/1687
    • \n
  • [COMING SOON] Modbus RS485 support is coming soon...
    • \n
\n

Room server:

\n
    \n
  • Added latest PowerSaving and PowerSaving CLI (powersaving, powersaving on and powersaving off): 5.8mA for NRF52, 10mA for Heltec v3 and 13mA for Heltec v4.
    • \n
  • Added MCU temperature
    • \n
\n

Companion:

\n
    \n
  • [NRF52] Added PowerSaving. Reduced from 9mA down to 5.8mA.
    • \n
  • [ESP32] PowerSaving is coming soon...
    • \n
\n

Common:

\n\n

Instruction:

\n

Please upgrade your easy to access repeaters / room servers first.

\n\n

Support and Discussion

\n
    \n
  • If you want us to compile for your boards or have question, please comment in GITHUB or DISCORD
    • \n
\n

Love the build?

\n
    \n
  • You may buy us a cofee ☕ for good work via Paypal \"Buy or Github \"Sponsor\".\nWe can buy more test boards and test sensors for development.
    • \n
\n

Demo

\n
    \n
  • Enter powersaving mode (CLI > powersaving on), 5.8mA for RAK4631 / Xiao NRF52, 6mA for Xiao S6/C3/C6, 10mA for Heltec v3, 13mA for Heltec v4...
    • \n
\n\"image\"\n\"image\"\n\"image\"
    \n
  • Enter CLI \"powersaving\", \"powersaving on\" and \"powersaving off\" with detailed responses
    • \n
  • Enter CLI \"sensor\" to check I2C and GPS Serial pins
    • \n
\n\"image\" \n\"image\"" }, { "version": "PowerSaving13.1", "name": "[BETA] Power Saving 13.1: More experiemental features", "datetime": "2026-02-28T04:17:35Z", "url": "https://github.com/IoTThinks/EasySkyMesh/releases/tag/PowerSaving13.1", "prerelease": true, "notes": "## Power Saving 13 plus the below features:\r\nBased on stable main MeshCore v1.13:\r\n* 28 Feb 2026 - Added \"fix agc reset on SX126x, SX1276 & LR11x0 chips\": [PR 1743](https://github.com/meshcore-dev/MeshCore/pull/1743) by [weebl2000](https://github.com/weebl2000). This is to fix stuck noise floor at -120 dBm.\r\n* 04 Mar 2026 - Added \"Fix 1970 date after crash/watchdog/brownout reset on ESP32\": [PR 1896](https://github.com/meshcore-dev/MeshCore/pull/1896) by [weebl2000](https://github.com/weebl2000). This is to keep the time after crash/watchdog/brownout reset on ESP32-based repeaters.\r\n\r\nSource code:\r\n* https://github.com/IoTThinks/MeshCore/tree/PowerSaving-v13.1", "notesHtml": "

Power Saving 13 plus the below features:

\n

Based on stable main MeshCore v1.13:

\n
    \n
  • 28 Feb 2026 - Added \"fix agc reset on SX126x, SX1276 & LR11x0 chips\": PR 1743 by weebl2000. This is to fix stuck noise floor at -120 dBm.
    • \n
  • 04 Mar 2026 - Added \"Fix 1970 date after crash/watchdog/brownout reset on ESP32\": PR 1896 by weebl2000. This is to keep the time after crash/watchdog/brownout reset on ESP32-based repeaters.
    • \n
\n

Source code:

\n\n" }, { "version": "PowerSaving13", "name": "Power Saving 13 - More power saving support, sensor support, hot fixes and variant support", "datetime": "2026-02-21T05:39:09Z", "url": "https://github.com/IoTThinks/EasySkyMesh/releases/tag/PowerSaving13", "prerelease": false, "notes": "## MeshCore v1.13 plus latest PowerSaving and more features:\r\n#### 1. More Power Saving support [Repeater] :\r\n* CLI: powersaving, powersaving on and powersaving off with detailed messages: https://github.com/meshcore-dev/MeshCore/pull/1687\r\n* PowerSaving for ALL ESP32-based (ESP32S3/C3/C6 and SX1276/sx1262) repeaters: Sleep after 2 minutes from boot. Wakeup on LoRa messages and sleep IMMEDIATELY. Reduced time drift (5 minutes/day to 1 minute/day) for ALL ESP32 repeaters. \r\n* Power Saving for NRF52 at 5.5mA in MeshCore v1.13 is from another contributor: Wakeup on LoRa messages and sleep immediately.\r\n\r\n#### 2. More sensor support [Repeater]:\r\n* [Heltec v4] Fixed broken I2C sensors (BME, INA sensors...) for Heltec v4: https://github.com/meshcore-dev/MeshCore/pull/1569\r\n* Automatically selected I2C addresses 0x76 or 0x77 for BME280, BMP280 and BME680. Just plug the sensors to the VCC, GND, SDA and SCL.\r\n* Added i2c probe for sensors to start only in-use sensors: https://github.com/meshcore-dev/MeshCore/pull/1282\r\n\r\n#### 3. Hot fixes [Repeater/Companion]:\r\n* [RAK4631 / Heltec T114 / Xiao NRF52] Reduced voltage boot lock from 3.3v to 1.8v in NRF52 power management. This is useful for devices with non-Lipo batteries: https://github.com/meshcore-dev/MeshCore/issues/1629\r\n* Automatically restart after flash for Heltec v4 (CDC support): https://github.com/meshcore-dev/MeshCore/pull/1335\r\n\r\n#### 4. More variant support [Repeater/Companion]\r\n* Xiao S3 (non-Wio) and Wio SX1262 (Initial support): SDA=D6, SCL=D7\r\n* Xiao C3 (Latest support): SDA=D6, SCL=D7\r\n* Xiao C6 (Latest support): SDA=D6, SCL=D7\r\n\r\n## Instruction:\r\nPlease upgrade your easy to access repeaters first.\r\n* Instruction to [Flash Custom Firmware](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Instruction-to-flash-firmware.md)\r\n* Please read the instruction in [Add sensors to repeaters](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Add-sensors-to-repeaters.md)\r\n* Source code for [PowerSaving 13](https://github.com/IoTThinks/MeshCore/tree/PowerSaving-v13)\r\n\r\n## Support\r\n* You may buy us a cofee ☕ for good work via Paypal [![Buy me a coffee](https://img.shields.io/badge/Buy%20me%20a%20coffee-iotthinks-0070ba?style=flat&logo=paypal&logoColor=white&labelColor=0070ba&color=555555)](https://www.paypal.com/paypalme/iotthinks/9usd) or Github [![Sponsor](https://img.shields.io/badge/Sponsor-iotthinks-ea4aaa?style=flat&logo=github-sponsors&logoColor=white&labelColor=ea4aaa&color=555555)](https://github.com/sponsors/IoTThinks)\r\n* If you want us to compile for your boards or have question, please comment in [IDEAS](https://github.com/IoTThinks/EasySkyMesh/discussions/categories/ideas)\r\n\r\n## Demo\r\n* Enter powersaving mode (CLI > powersaving on), 5.8mA for RAK4631 / Xiao NRF52, 6mA for Xiao S6/C3/C6, 10mA for Heltec v3, 13mA for Heltec v4...\r\n\"image\"\r\n\"image\"\r\n\"image\"\r\n\r\n* Enter CLI \"powersaving\", \"powersaving on\" and \"powersaving off\" with detailed responses\r\n* Enter CLI \"sensor\" to check I2C and GPS Serial pins\r\n\"image\" \r\n\"image\"\r\n\r\n* Telemetry works properly for Heltec v4 when OLED is off\r\n\"image\"\r\n\r\n* RAK4631 / Heltec T114 / Xiao NRF52 works at lower voltage lock. Boot lock is reduced from 3.3v to 1.8v,\r\n\"image\"MeshCore v1.13 plus latest PowerSaving and more features:\n

1. More Power Saving support [Repeater] :

\n
    \n
  • CLI: powersaving, powersaving on and powersaving off with detailed messages: https://github.com/meshcore-dev/MeshCore/pull/1687
    • \n
  • PowerSaving for ALL ESP32-based (ESP32S3/C3/C6 and SX1276/sx1262) repeaters: Sleep after 2 minutes from boot. Wakeup on LoRa messages and sleep IMMEDIATELY. Reduced time drift (5 minutes/day to 1 minute/day) for ALL ESP32 repeaters.
    • \n
  • Power Saving for NRF52 at 5.5mA in MeshCore v1.13 is from another contributor: Wakeup on LoRa messages and sleep immediately.
    • \n
\n

2. More sensor support [Repeater]:

\n\n

3. Hot fixes [Repeater/Companion]:

\n\n

4. More variant support [Repeater/Companion]

\n
    \n
  • Xiao S3 (non-Wio) and Wio SX1262 (Initial support): SDA=D6, SCL=D7
    • \n
  • Xiao C3 (Latest support): SDA=D6, SCL=D7
    • \n
  • Xiao C6 (Latest support): SDA=D6, SCL=D7
    • \n
\n

Instruction:

\n

Please upgrade your easy to access repeaters first.

\n\n

Support

\n
    \n
  • You may buy us a cofee ☕ for good work via Paypal \"Buy or Github \"Sponsor\"
    • \n
  • If you want us to compile for your boards or have question, please comment in IDEAS
    • \n
\n

Demo

\n
    \n
  • Enter powersaving mode (CLI > powersaving on), 5.8mA for RAK4631 / Xiao NRF52, 6mA for Xiao S6/C3/C6, 10mA for Heltec v3, 13mA for Heltec v4...
    • \n
\n\"image\"\n\"image\"\n\"image\"
    \n
  • Enter CLI \"powersaving\", \"powersaving on\" and \"powersaving off\" with detailed responses
    • \n
  • Enter CLI \"sensor\" to check I2C and GPS Serial pins
    • \n
\n\"image\" \n\"image\"
    \n
  • Telemetry works properly for Heltec v4 when OLED is off
    • \n
\n\"image\"\n" }, { "version": "PowerSaving11", "name": "Power Saving 11 - 6mA power consumption for ALL NRF52-based repeaters and 10mA power consumption for ALL ESP32-based repeaters", "datetime": "2026-01-07T15:49:04Z", "url": "https://github.com/IoTThinks/EasySkyMesh/releases/tag/PowerSaving11", "prerelease": false, "notes": "This is for all NRF52-based repeaters and ESP32-based repeaters: **6mA** power consumption for ALL NRF52-based repeaters and **10mA** power consumption for ALL ESP32-based repeaters\r\n- [Production] For ESP32-based repeaters, the firmware is very stable and in production. We will improve the timedrift for ESP32-based repeaters in the next version.\r\n- [**Beta**] For NRF52-based repeaters, the firmware is newly released. Please test it a while with easy to access repeaters.\r\n- We will push this PowerSaving version to MeshCore github within 7 days. Usually, we will listen for your feedback before we push to MeshCore github.\r\n\r\nNRF52-based repeater at **6mA** and ESP32-based repeater at **10mA**\r\n\"image\" \"image\"\r\n\r\n**IMPORTANT:** \r\n- On CLI, you need to type \"**powersaving on**\" ONCE to achieve 10mA power consumption. The setting will persist even after reboot.\r\n- Powersaving (if enabled) will start 2 minutes since boot.\r\n- If you enable OTA via `start ota` in CLI, then powersaving will have no effect.\r\n\r\n**New features:**\r\n- Improved PowerSaving for ALL NRF52-based repeaters from 8.5mA down to 6mA. Initially, NRF52 consumes 12mA down to 8.5mA (PowerSaving 9+) and now 6mA (PowerSaving 11).\r\n\r\n**Instruction:** \r\n- Instruction to [Flash Custom Firmware](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Instruction-to-flash-firmware.md)\r\n- Please read the instruction in [Add sensors to repeaters](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Add-sensors-to-repeaters.md)\r\n\r\n**Videos:**\r\nThis is a RAK4631 repeater with PowerSaving in action: Sleep at 6mA, wakeup when a LoRa packet comes, process it, wake up for 5s and go to sleep again.\r\n\r\nhttps://github.com/user-attachments/assets/fbb698ce-f551-4900-bf2b-1c9945d6f3a4\r\n\r\nPing us if you want us to compile for your boards [HERE](https://github.com/IoTThinks/EasySkyMesh/discussions/categories/ideas)\r\nYou may want to buy us [a coffee](https://github.com/sponsors/IoTThinks) ☕ for good work.\r\nEnjoy.", "notesHtml": "

This is for all NRF52-based repeaters and ESP32-based repeaters: 6mA power consumption for ALL NRF52-based repeaters and 10mA power consumption for ALL ESP32-based repeaters

\n
    \n
  • [Production] For ESP32-based repeaters, the firmware is very stable and in production. We will improve the timedrift for ESP32-based repeaters in the next version.
    • \n
  • [Beta] For NRF52-based repeaters, the firmware is newly released. Please test it a while with easy to access repeaters.
    • \n
  • We will push this PowerSaving version to MeshCore github within 7 days. Usually, we will listen for your feedback before we push to MeshCore github.
    • \n
\n

NRF52-based repeater at 6mA and ESP32-based repeater at 10mA\n\"image\" \"image\"

\n

IMPORTANT:

\n
    \n
  • On CLI, you need to type \"powersaving on\" ONCE to achieve 10mA power consumption. The setting will persist even after reboot.
    • \n
  • Powersaving (if enabled) will start 2 minutes since boot.
    • \n
  • If you enable OTA via start ota in CLI, then powersaving will have no effect.
    • \n
\n

New features:

\n
    \n
  • Improved PowerSaving for ALL NRF52-based repeaters from 8.5mA down to 6mA. Initially, NRF52 consumes 12mA down to 8.5mA (PowerSaving 9+) and now 6mA (PowerSaving 11).
    • \n
\n

Instruction:

\n\n

Videos:\nThis is a RAK4631 repeater with PowerSaving in action: Sleep at 6mA, wakeup when a LoRa packet comes, process it, wake up for 5s and go to sleep again.

\n

https://github.com/user-attachments/assets/fbb698ce-f551-4900-bf2b-1c9945d6f3a4

\n

Ping us if you want us to compile for your boards HERE\nYou may want to buy us a coffee ☕ for good work.\nEnjoy.

\n" }, { "version": "PowerSaving10", "name": "Power Saving 10 - 10mA power consumption for ALL ESP32-based repeaters", "datetime": "2026-01-02T15:40:28Z", "url": "https://github.com/IoTThinks/EasySkyMesh/releases/tag/PowerSaving10", "prerelease": false, "notes": "If your ESP32 boards have not had power saving yet, you could use this PowerSaving 10 to achieve 10mA.\r\nElse you may stay with PowerSaving 09.\r\n\r\nHOT_FIXES - 06 JAN 2026: v10.1\r\n- Hot-fixes for old boards with SX1276: To wake up on DIO0 (instead of DIO1) for Heltec v2, LilyGo_T3S3_sx1276, LilyGo_TLora_V2_1_1_6 and Tbeam_SX1276. Known issue: Deepsleep is only working for SX1262, however it is not in scope of the powersaving.\r\n- Hot-fixes for TBeam boards: To fix TBeam boards to separate boards with SX1262 and SX1276.\r\n\r\nIMPORTANT: \r\n- On CLI, you need to type \"**powersaving on**\" ONCE to achieve 10mA power consumption. The setting will persist even after reboot.\r\n- Powersaving (if enabled) will start 2 minutes since boot.\r\n\r\nNew features:\r\n- Supports PowerSaving for ALL ESP32-based repeaters\r\n\r\nExisting features:\r\n- PowerSaving for RTC-DIO1 boards: 9mA for Heltec v2, v3, v4, WSL3, TBeam... since PowerSaving 07\r\n- PowerSaving for NRF52 boards: 8.5mA for RAK4631, Heltec T114, Xiao-NRF52 and T-Echo/T-Echo Lite... since PowerSaving 07\r\n- PowerSaving CLI: \"powersaving\" to check status, \"powersaving on\" and \"powersaving off\". \r\n- Built-in temperature in telemetry for ESP32S3 and NRF52 repeaters.\r\n- Fixed BME280 and BME680 for all boards.\r\n- Added force clock sync in CLI \"clock fsync\"\r\n- Fixed measurement of battery voltage for T-Echo lite\r\n\r\nInstruction: \r\n- Instruction to [Flash Custom Firmware](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Instruction-to-flash-firmware.md)\r\n- Please read the instruction in [Add sensors to repeaters](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Add-sensors-to-repeaters.md)\r\n\r\nHeltec v3, RAK4631 and simulated Xiao Wio S3 (by Heltec v3)\r\n\r\n\"image\"\r\n\"image\" \r\n\"image\"\r\n\r\nPing us if you want us to compile for your boards [HERE](https://github.com/IoTThinks/EasySkyMesh/discussions/categories/ideas)\r\nYou may want to buy us [a coffee](https://github.com/sponsors/IoTThinks) ☕ for good work.\r\nEnjoy.", "notesHtml": "

If your ESP32 boards have not had power saving yet, you could use this PowerSaving 10 to achieve 10mA.\nElse you may stay with PowerSaving 09.

\n

HOT_FIXES - 06 JAN 2026: v10.1

\n
    \n
  • Hot-fixes for old boards with SX1276: To wake up on DIO0 (instead of DIO1) for Heltec v2, LilyGo_T3S3_sx1276, LilyGo_TLora_V2_1_1_6 and Tbeam_SX1276. Known issue: Deepsleep is only working for SX1262, however it is not in scope of the powersaving.
    • \n
  • Hot-fixes for TBeam boards: To fix TBeam boards to separate boards with SX1262 and SX1276.
    • \n
\n

IMPORTANT:

\n
    \n
  • On CLI, you need to type \"powersaving on\" ONCE to achieve 10mA power consumption. The setting will persist even after reboot.
    • \n
  • Powersaving (if enabled) will start 2 minutes since boot.
    • \n
\n

New features:

\n
    \n
  • Supports PowerSaving for ALL ESP32-based repeaters
    • \n
\n

Existing features:

\n
    \n
  • PowerSaving for RTC-DIO1 boards: 9mA for Heltec v2, v3, v4, WSL3, TBeam... since PowerSaving 07
    • \n
  • PowerSaving for NRF52 boards: 8.5mA for RAK4631, Heltec T114, Xiao-NRF52 and T-Echo/T-Echo Lite... since PowerSaving 07
    • \n
  • PowerSaving CLI: \"powersaving\" to check status, \"powersaving on\" and \"powersaving off\".
    • \n
  • Built-in temperature in telemetry for ESP32S3 and NRF52 repeaters.
    • \n
  • Fixed BME280 and BME680 for all boards.
    • \n
  • Added force clock sync in CLI \"clock fsync\"
    • \n
  • Fixed measurement of battery voltage for T-Echo lite
    • \n
\n

Instruction:

\n\n

Heltec v3, RAK4631 and simulated Xiao Wio S3 (by Heltec v3)

\n\"image\"\n\"image\" \n\"image\"

Ping us if you want us to compile for your boards HERE\nYou may want to buy us a coffee ☕ for good work.\nEnjoy.

\n" }, { "version": "PowerSaving09", "name": "Power Saving 09 - Added PowerSaving CLI and fixed sensor support", "datetime": "2025-12-28T05:20:14Z", "url": "https://github.com/IoTThinks/EasySkyMesh/releases/tag/PowerSaving09", "prerelease": false, "notes": "Power Saving 09: Power saving CLI and more sensor support\r\n- Added PowerSaving CLI: To type in CLI \"powersaving\" to check status, \"powersaving on\" and \"powersaving off\". You need to type \"**powersaving on**\" ONCE. The setting will persist even after reboot.\r\n- Used the default I2C pins as same as MeshCore\r\n- Improved performance for repeaters' boot: To check availability of I2C addresses of sensors before triggering begin() for sensors.\r\n- Added sensor support for T114. Please help to test it.\r\n- Fixed to use temperature of BME280/680 (if available) instead of MCU Temperature\r\n- Fixed the accuracy of MCU temperature for ESP32 boards: To get the MCU temperature 4 times and average them to have better accuracy in low temperature (~0*C)\r\n- Updated the instruction to [Add sensors to repeaters](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Add-sensors-to-repeaters.md)\r\n\r\nNotes:\r\n- Please read the instruction in [Add sensors to repeaters](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Add-sensors-to-repeaters.md)\r\n- Instruction to [Flash Custom Firmware](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Instruction-to-flash-firmware.md)\r\n- PING us if you want us to compile for your boards [HERE](https://github.com/IoTThinks/EasySkyMesh/discussions/categories/ideas)\r\n\r\nPlease type \"powersaving on\" to enjoy the power consumption as low as 9.5mA for ESP32-based boards (Except Xiao S3) and 8.5mA for NRF52 boards.\r\n\"image\"\r\n\r\nThe temperature of BME280/680 will override the default temperature of MCU.\r\n\"image\"\r\n\r\nYou may want to buy us [a coffee](https://github.com/sponsors/IoTThinks) for good work.\r\nEnjoy.", "notesHtml": "

Power Saving 09: Power saving CLI and more sensor support

\n
    \n
  • Added PowerSaving CLI: To type in CLI \"powersaving\" to check status, \"powersaving on\" and \"powersaving off\". You need to type \"powersaving on\" ONCE. The setting will persist even after reboot.
    • \n
  • Used the default I2C pins as same as MeshCore
    • \n
  • Improved performance for repeaters' boot: To check availability of I2C addresses of sensors before triggering begin() for sensors.
    • \n
  • Added sensor support for T114. Please help to test it.
    • \n
  • Fixed to use temperature of BME280/680 (if available) instead of MCU Temperature
    • \n
  • Fixed the accuracy of MCU temperature for ESP32 boards: To get the MCU temperature 4 times and average them to have better accuracy in low temperature (~0*C)
    • \n
  • Updated the instruction to Add sensors to repeaters
    • \n
\n

Notes:

\n\n

Please type \"powersaving on\" to enjoy the power consumption as low as 9.5mA for ESP32-based boards (Except Xiao S3) and 8.5mA for NRF52 boards.\n\"image\"

\n

The temperature of BME280/680 will override the default temperature of MCU.\n\"image\"

\n

You may want to buy us a coffee for good work.\nEnjoy.

\n" }, { "version": "PowerSaving08", "name": "Power Saving 08 - Fixed BME280 and BME680 for all boards", "datetime": "2025-12-21T13:58:52Z", "url": "https://github.com/IoTThinks/EasySkyMesh/releases/tag/PowerSaving08", "prerelease": false, "notes": "Power Saving 08 fixed BME280/BME680 for repeaters\r\n- Fixed BME280 and BME680 for all boards.\r\n- Added force clock sync in CLI \"clock fsync\"\r\n- Fixed measurement of battery voltage for T-Echo lite\r\n\r\nNotes:\r\n- Please read the instruction in [Add sensors to repeaters](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Add-sensors-to-repeaters.md)\r\n- Instruction to [Flash Custom Firmware](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Instruction-to-flash-firmware.md)\r\n- PING us if you want us to compile for your boards [HERE](https://github.com/IoTThinks/EasySkyMesh/discussions/categories/ideas)\r\n\r\n\"image\" \"image\"\r\n\r\nYou may want to buy us [a coffee](https://github.com/sponsors/IoTThinks) for good work.\r\nEnjoy.", "notesHtml": "

Power Saving 08 fixed BME280/BME680 for repeaters

\n
    \n
  • Fixed BME280 and BME680 for all boards.
    • \n
  • Added force clock sync in CLI \"clock fsync\"
    • \n
  • Fixed measurement of battery voltage for T-Echo lite
    • \n
\n

Notes:

\n\n

\"image\" \"image\"

\n

You may want to buy us a coffee for good work.\nEnjoy.

\n" }, { "version": "PowerSaving07", "name": "Power Saving 07 - Improved power saving and added built-in temperature", "datetime": "2025-12-11T04:28:59Z", "url": "https://github.com/IoTThinks/EasySkyMesh/releases/tag/PowerSaving07", "prerelease": false, "notes": "Improved power saving and added built-in temperature for ESP32S3 and NRF52 repeaters\r\n- Based on MeshCore repeater v1.11.0\r\n- ESP32S3 boards: Heltec v3 and Heltec v4\r\n- NRF52 boards: RAK4631, Heltec T114, Xiao-NRF52 and T-Echo/T-Echo Lite\r\n- Powersaving: **9mA for ESP32 boards and 8.5mA for NRF52 boards**. You need to measure at the battery cable (NOT from USB cable).\r\n- Built-in temperature in telemetry for ESP32S3 and NRF52 repeaters.\r\n\r\nNotes:\r\n\r\n- Instruction to [Flash Custom Firmware](https://github.com/IoTThinks/EasySkyMesh/blob/main/firmware/Instruction-to-flash-firmware.md)\r\n- PING us if you want us to compile for your boards [HERE](https://github.com/IoTThinks/EasySkyMesh/discussions/categories/ideas)\r\n\r\nHeltec v3 from 50mA down to 9mA. RAK4631 from 12.5mA down to 8.5mA\r\n\"image\" \"image\"\r\n\r\nBuilt-in temperature (BME280/680/688 is NOT required.)\r\n\"image\" \"image\"\r\n\r\nYou may want to buy us [a coffee](https://github.com/sponsors/IoTThinks) for good work.\r\nEnjoy.", "notesHtml": "

Improved power saving and added built-in temperature for ESP32S3 and NRF52 repeaters

\n
    \n
  • Based on MeshCore repeater v1.11.0
    • \n
  • ESP32S3 boards: Heltec v3 and Heltec v4
    • \n
  • NRF52 boards: RAK4631, Heltec T114, Xiao-NRF52 and T-Echo/T-Echo Lite
    • \n
  • Powersaving: 9mA for ESP32 boards and 8.5mA for NRF52 boards. You need to measure at the battery cable (NOT from USB cable).
    • \n
  • Built-in temperature in telemetry for ESP32S3 and NRF52 repeaters.
    • \n
\n

Notes:

\n\n

Heltec v3 from 50mA down to 9mA. RAK4631 from 12.5mA down to 8.5mA\n\"image\" \"image\"

\n

Built-in temperature (BME280/680/688 is NOT required.)\n\"image\" \"image\"

\n

You may want to buy us a coffee for good work.\nEnjoy.

\n" } ], "changelogSource": "github", "changelogUpdatedAt": "2026-06-21T09:55:29.384Z" }, { "id": "fennek", "name": "Fennek", "type": "fork", "maintainer": "danst0", "description": "An alternative open-source firmware for the LilyGO T-Deck Pro — music, audiobooks, eBooks and LoRa mesh chat via MeshCore. Features a homescreen launcher, touch and physical keyboard support, EPUB reader, audiobook player, and PCM5102A DAC audio output.\n", "repository": "https://github.com/danst0/fennek", "license": "GPL-3.0", "status": "active", "lifecycle": "active", "maturity": "beta", "distribution": "community", "lineage": { "kind": "fork", "upstreamFirmwareId": "meshcore-official", "upstreamRepository": "https://github.com/meshcore-dev/MeshCore" }, "runtime": { "framework": "arduino", "language": "cpp" }, "roles": [ "companion", "standalone-ui" ], "features": [ "Homescreen launcher", "Music playback (PCM5102A DAC)", "Audiobook player", "EPUB and TXT reader with page-index cache", "LoRa mesh chat via MeshCore", "Touch + physical keyboard support", "Per-book reading position" ], "capabilities": { "protocol": { "meshcoreCompatible": true }, "transports": { "ble": true, "usbSerial": true, "nativeTcp": true, "wifiAp": true }, "operations": { "ota": false, "webFlasher": false }, "networking": { "repeater": false, "roomServer": false, "observer": false, "kissModem": false }, "hardware": { "gps": true, "display": true, "sensors": false, "lowPowerRx": false } }, "devices": [ { "id": "lilygo-tdeck-pro", "status": "supported" } ], "popularity": { "githubStars": 2, "githubForks": 0, "githubWatchers": 0, "githubOpenIssues": 0, "githubContributors": 101, "releaseDownloads": 0, "latestReleaseDownloads": 0, "lastChecked": "2026-06-21" }, "verification": { "sourceAvailable": true, "releasesAvailable": true, "ciBuilds": false, "lastChecked": "2026-06-21" }, "latest_version": "2.4.8", "released": "2026-06-20", "releases": [ { "version": "v2.4.8", "name": "Fennek v2.4.8", "datetime": "2026-06-20T19:59:52Z", "url": "https://github.com/danst0/fennek/releases/tag/v2.4.8", "prerelease": false, "notes": "## Änderungen\n\n- **OTA:** Semver-Vergleich für Update-Erkennung (`tag_name != FENNEK_VERSION` → korrekte Versionslogik)\n- **Akku:** Batterieanzeige-Fix in der Statuszeile\n\n## Flashen\n\n```\npio run -e fennek -t upload\n```\n\noder OTA via `fennek.local` → Firmware-Update.", "notesHtml": "

Änderungen

\n
    \n
  • OTA: Semver-Vergleich für Update-Erkennung (tag_name != FENNEK_VERSION → korrekte Versionslogik)
    • \n
  • Akku: Batterieanzeige-Fix in der Statuszeile
    • \n
\n

Flashen

\n
pio run -e fennek -t upload\n
\n

oder OTA via fennek.local → Firmware-Update.

\n" }, { "version": "v2.3.1", "name": "Fennek v2.3.1", "datetime": "2026-06-19T14:27:33Z", "url": "https://github.com/danst0/fennek/releases/tag/v2.3.1", "prerelease": false, "notes": "## Notizen / Audio\n- **Sprachnotiz-Liste** zeigt jetzt **Datum + HH:MM** (statt HH:MM:SS bzw. generisch „Sprachnotiz\").\n- **Aufnahme-Gain ×6** mit Sättigung: das PDM-Mikro war ~−20 dBFS leise → Wiedergabe kaum hörbar. Neue Aufnahmen sitzen bei ~−7 dBFS (kein Clipping).\n- **Sauberer I2S0-Handover** nach der Aufnahme: kein doppeltes `i2s_driver_uninstall` mehr (`endMic`/`MicResume` macht uninstall+install in einem Schritt).\n\n## Karten / GPS\n- **No-Fix-Fallback** zentriert jetzt auf **Düsseldorf** (51.2277/6.7735); `DEFAULT_ZOOM` 15 → 13 (NRW-weit bekachelt).\n- **GPS-Zeit-Diagnose**: Einmal-Log `[MAPS] GPS-Zeit empfangen …` pro Karten-Session.\n\nEnthält außerdem v2.3.0 (GPS-/WAV-Diagnose-Logs, Karten-Fallback, Notizen-Zeitlabel).", "notesHtml": "

Notizen / Audio

\n
    \n
  • Sprachnotiz-Liste zeigt jetzt Datum + HH:MM (statt HH:MM:SS bzw. generisch „Sprachnotiz\").
    • \n
  • Aufnahme-Gain ×6 mit Sättigung: das PDM-Mikro war ~−20 dBFS leise → Wiedergabe kaum hörbar. Neue Aufnahmen sitzen bei ~−7 dBFS (kein Clipping).
    • \n
  • Sauberer I2S0-Handover nach der Aufnahme: kein doppeltes i2s_driver_uninstall mehr (endMic/MicResume macht uninstall+install in einem Schritt).
    • \n
\n

Karten / GPS

\n
    \n
  • No-Fix-Fallback zentriert jetzt auf Düsseldorf (51.2277/6.7735); DEFAULT_ZOOM 15 → 13 (NRW-weit bekachelt).
    • \n
  • GPS-Zeit-Diagnose: Einmal-Log [MAPS] GPS-Zeit empfangen … pro Karten-Session.
    • \n
\n

Enthält außerdem v2.3.0 (GPS-/WAV-Diagnose-Logs, Karten-Fallback, Notizen-Zeitlabel).

\n" }, { "version": "v2.0.4", "name": "v2.0.4", "datetime": "2026-06-17T17:30:26Z", "url": "https://github.com/danst0/fennek/releases/tag/v2.0.4", "prerelease": false, "notes": "## Changes\n\n- **Regenerated README/website screenshots.** The home-screen mirror in the host renderer (`tools/screenshot.cpp`) was stuck on an old layout (6 tiles, 2×3); it now matches the real `launcher.cpp` — a 2×5 grid with all 10 slots (Music/Listen/Read/Mesh/Settings/Games/Files/Notes/Alarm). The Settings screenshot now shows the current version.\n- Images updated in `docs/screenshots/{de,en,sv}/` and on [fennek.dumke.me](https://fennek.dumke.me).\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)", "notesHtml": "

Changes

\n
    \n
  • Regenerated README/website screenshots. The home-screen mirror in the host renderer (tools/screenshot.cpp) was stuck on an old layout (6 tiles, 2×3); it now matches the real launcher.cpp — a 2×5 grid with all 10 slots (Music/Listen/Read/Mesh/Settings/Games/Files/Notes/Alarm). The Settings screenshot now shows the current version.
    • \n
  • Images updated in docs/screenshots/{de,en,sv}/ and on fennek.dumke.me.
    • \n
\n

🤖 Generated with Claude Code

\n" }, { "version": "v1.9.4", "name": "v1.9.4", "datetime": "2026-06-17T06:53:30Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.9.4", "prerelease": false, "notes": "## Änderungen\n\n- **Web-Dateimanager**: Löschen ohne Rückfrage. Nur Ordner mit Unterordnern fragen kurz nach und werden dann rekursiv gelöscht (`rmRecursive`); Dateien und flache Ordner verschwinden sofort.\n- **Notizen-App + Konsole**: weitere Verbesserungen.\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)", "notesHtml": "

Änderungen

\n
    \n
  • Web-Dateimanager: Löschen ohne Rückfrage. Nur Ordner mit Unterordnern fragen kurz nach und werden dann rekursiv gelöscht (rmRecursive); Dateien und flache Ordner verschwinden sofort.
    • \n
  • Notizen-App + Konsole: weitere Verbesserungen.
    • \n
\n

🤖 Generated with Claude Code

\n" }, { "version": "v1.9.2", "name": "Fennek v1.9.2", "datetime": "2026-06-15T15:51:06Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.9.2", "prerelease": false, "notes": "### Added\n- **`BATTLOG` — opt-in battery & activity logger** (`services/battlog`). When the `BATTLOG` build flag is set, the firmware writes one record per event (app switch, audio track, mesh radio on, Wi-Fi on/off, standby/wake) **and** a battery probe every 60 s to `/.fennek/battery.log` (timestamp + %/mV/charging? + Wi-Fi/mesh status). It's a throttled PSRAM ring flushed to SD before standby, and downloadable via the Web file manager — useful for diagnosing real-world battery drain. Deliberately zero-cost when the flag is off (all `BATTLOG_*` calls compile to nothing).\n\n🌐 Project page & screenshots: **https://fennek.dumke.me**\n\n**Full changelog:** [`CHANGELOG.md`](https://github.com/danst0/fennek/blob/main/CHANGELOG.md)", "notesHtml": "

Added

\n
    \n
  • BATTLOG — opt-in battery & activity logger (services/battlog). When the BATTLOG build flag is set, the firmware writes one record per event (app switch, audio track, mesh radio on, Wi-Fi on/off, standby/wake) and a battery probe every 60 s to /.fennek/battery.log (timestamp + %/mV/charging? + Wi-Fi/mesh status). It's a throttled PSRAM ring flushed to SD before standby, and downloadable via the Web file manager — useful for diagnosing real-world battery drain. Deliberately zero-cost when the flag is off (all BATTLOG_* calls compile to nothing).
    • \n
\n

🌐 Project page & screenshots: https://fennek.dumke.me

\n

Full changelog: CHANGELOG.md

\n" }, { "version": "v1.9.1", "name": "Fennek v1.9.1", "datetime": "2026-06-15T15:51:06Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.9.1", "prerelease": false, "notes": "### Fixed\n- **Notes never silently lost on a failed SD write.** The save path now clears its dirty flag only on a *complete* success; if an SD write or remove fails, the note stays dirty and is retried on the next autosave instead of being overwritten on the next editor open.\n- **Just-played track now reaches the scrobble queue before standby.** `power::poll()` stops audio (and lets the audio task drain the stop command) *before* the pre-standby Navidrome flush, so the current track is enqueued via `noteTrackEnded()` rather than landing in the PSRAM ring that deep sleep would otherwise discard.\n\n**Full changelog:** [`CHANGELOG.md`](https://github.com/danst0/fennek/blob/main/CHANGELOG.md)", "notesHtml": "

Fixed

\n
    \n
  • Notes never silently lost on a failed SD write. The save path now clears its dirty flag only on a complete success; if an SD write or remove fails, the note stays dirty and is retried on the next autosave instead of being overwritten on the next editor open.
    • \n
  • Just-played track now reaches the scrobble queue before standby. power::poll() stops audio (and lets the audio task drain the stop command) before the pre-standby Navidrome flush, so the current track is enqueued via noteTrackEnded() rather than landing in the PSRAM ring that deep sleep would otherwise discard.
    • \n
\n

Full changelog: CHANGELOG.md

\n" }, { "version": "v1.9.0", "name": "Fennek v1.9.0", "datetime": "2026-06-15T15:51:05Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.9.0", "prerelease": false, "notes": "### Added\n- **Mesh: `contacts reset` console command** + `mesh_client::resetContacts()`. Clears all contacts and their persistent mirrors (SPIFFS `/contacts`, SD `/meshcore/contacts.bin`); the contact table then rebuilds itself from incoming adverts. Handy when the 64-slot table fills up with stale nodes or you want a clean slate.\n\n**Full changelog:** [`CHANGELOG.md`](https://github.com/danst0/fennek/blob/main/CHANGELOG.md)", "notesHtml": "

Added

\n
    \n
  • Mesh: contacts reset console command + mesh_client::resetContacts(). Clears all contacts and their persistent mirrors (SPIFFS /contacts, SD /meshcore/contacts.bin); the contact table then rebuilds itself from incoming adverts. Handy when the 64-slot table fills up with stale nodes or you want a clean slate.
    • \n
\n

Full changelog: CHANGELOG.md

\n" }, { "version": "v1.8.1", "name": "Fennek v1.8.1", "datetime": "2026-06-15T15:51:04Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.8.1", "prerelease": false, "notes": "### Changed\n- **Unified back/home navigation across all apps.** Home is now a visible affordance: the status bar shows a house glyph (⌂) outside the launcher and the whole bar taps to Home. Lower corner buttons are consistently labelled **\"Back\"** (exactly one level) — audiobook/reader/notes lists and Settings now say \"Back\" instead of \"Home\", and the Settings back button steps edit → category → root → launcher. Mesh sub-screens dropped their redundant second \"Home\" button, the Files app gained a visible \"Back\" button, and the reader footer tap-zone is labelled \"◄ List\". Games keep no on-screen back button (exit via the ⌂ glyph; keyboard `Backspace`/`Q` still works). Keyboard conventions (`Q` = Home, `Backspace` = one level back) unchanged.\n\n**Full changelog:** [`CHANGELOG.md`](https://github.com/danst0/fennek/blob/main/CHANGELOG.md)", "notesHtml": "

Changed

\n
    \n
  • Unified back/home navigation across all apps. Home is now a visible affordance: the status bar shows a house glyph (⌂) outside the launcher and the whole bar taps to Home. Lower corner buttons are consistently labelled \"Back\" (exactly one level) — audiobook/reader/notes lists and Settings now say \"Back\" instead of \"Home\", and the Settings back button steps edit → category → root → launcher. Mesh sub-screens dropped their redundant second \"Home\" button, the Files app gained a visible \"Back\" button, and the reader footer tap-zone is labelled \"◄ List\". Games keep no on-screen back button (exit via the ⌂ glyph; keyboard Backspace/Q still works). Keyboard conventions (Q = Home, Backspace = one level back) unchanged.
    • \n
\n

Full changelog: CHANGELOG.md

\n" }, { "version": "v1.8.0", "name": "Fennek v1.8.0", "datetime": "2026-06-13T19:18:10Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.8.0", "prerelease": false, "notes": "## Added\n- **Notes app** (launcher tile 7): a daily-notes model — exactly one note per day, named after the local date (`/notes/YYYY-MM-DD.md`). **\"+ Today\"** opens or appends to today's note; the list shows every day newest-first with a first-line preview, and notes can be deleted with a confirmation. The editor is append-style (type / Backspace / Enter) with its own word wrap and a compact header.\n\n Persistence is chunked under `spiLock` (never inside `draw()`), with a 30 s autosave and a save on leave; empty notes are removed. Without an SD card it shows \"No SD card\" + \"Search again\" like the other apps. The date comes from the local system clock (`timesync`). New console command `notes` runs an SD round-trip / scan self-check (in the style of `books`).\n\nLocalized in DE/IT/SV/EN/ES. Verified on device (clean boot, SD round-trip with UTF-8 preserved, scan/sort).\n\n**Full changelog:** [CHANGELOG.md](https://github.com/danst0/fennek/blob/main/CHANGELOG.md)", "notesHtml": "

Added

\n
    \n

  • Notes app (launcher tile 7): a daily-notes model — exactly one note per day, named after the local date (/notes/YYYY-MM-DD.md). \"+ Today\" opens or appends to today's note; the list shows every day newest-first with a first-line preview, and notes can be deleted with a confirmation. The editor is append-style (type / Backspace / Enter) with its own word wrap and a compact header.

    \n

    Persistence is chunked under spiLock (never inside draw()), with a 30 s autosave and a save on leave; empty notes are removed. Without an SD card it shows \"No SD card\" + \"Search again\" like the other apps. The date comes from the local system clock (timesync). New console command notes runs an SD round-trip / scan self-check (in the style of books).

    \n
    • \n
\n

Localized in DE/IT/SV/EN/ES. Verified on device (clean boot, SD round-trip with UTF-8 preserved, scan/sort).

\n

Full changelog: CHANGELOG.md

\n" }, { "version": "v1.7.1", "name": "Fennek v1.7.1", "datetime": "2026-06-13T04:08:05Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.7.1", "prerelease": false, "notes": "## ✨ Added\n- **Settings backup as INI** (`services/settingsfile`): export/import all NVS settings to/from an SD file. SPI-free serialization on a RAM buffer, SD I/O isolated under `spiLock`. Per-book bookmarks/reading positions are excluded (CRC32-hashed keys). New console command + `main`/`power` wiring.\n\n## 📝 Docs\n- Added `CHANGELOG.md` and GitHub releases for v1.3.0–v1.7.0.\n- README now ships in **English (default)**, German (`README.de.md`) and Swedish (`README.sv.md`) with a language switcher and release/changelog badges.\n\n📋 Full history: [CHANGELOG.md](https://github.com/danst0/fennek/blob/main/CHANGELOG.md)", "notesHtml": "

✨ Added

\n
    \n
  • Settings backup as INI (services/settingsfile): export/import all NVS settings to/from an SD file. SPI-free serialization on a RAM buffer, SD I/O isolated under spiLock. Per-book bookmarks/reading positions are excluded (CRC32-hashed keys). New console command + main/power wiring.
    • \n
\n

📝 Docs

\n
    \n
  • Added CHANGELOG.md and GitHub releases for v1.3.0–v1.7.0.
    • \n
  • README now ships in English (default), German (README.de.md) and Swedish (README.sv.md) with a language switcher and release/changelog badges.
    • \n
\n

📋 Full history: CHANGELOG.md

\n" }, { "version": "v1.7.0", "name": "Fennek v1.7.0", "datetime": "2026-06-13T04:03:33Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.7.0", "prerelease": false, "notes": "## ✨ Added\n- **\"+ New Channel\" UI** for joining hashtag channels — a \"► New Channel\" row at the top of the chat list opens a join screen (keyboard types the `#name`, PSK derived from it, persisted to `channels.txt` on SD; jumps straight into the new channel after joining).\n\n## 🔄 Changed\n- **Robust time synchronization without a hardware RTC.** Canonical clock is now ESP32 system time (`SystemRTCClock`), which survives deep sleep. New `services/timesync` coordinator: opportunistic NTP (when Wi-Fi is up) + a top-up before auto-standby, with Mesh adverts as a passive source. Quality model (`estErr = learned drift × time since sync`) with exponential back-off, `s_clockConfident` bootstrap for the first advert after boot, POSIX time zone (default `Europe/Berlin` incl. DST), settings rows \"Time zone\"/\"Time\", and console `time` / `time set` / `time sync` / `tz`.\n\n📋 Full history: [CHANGELOG.md](https://github.com/danst0/fennek/blob/main/CHANGELOG.md)", "notesHtml": "

✨ Added

\n
    \n
  • \"+ New Channel\" UI for joining hashtag channels — a \"► New Channel\" row at the top of the chat list opens a join screen (keyboard types the #name, PSK derived from it, persisted to channels.txt on SD; jumps straight into the new channel after joining).
    • \n
\n

🔄 Changed

\n
    \n
  • Robust time synchronization without a hardware RTC. Canonical clock is now ESP32 system time (SystemRTCClock), which survives deep sleep. New services/timesync coordinator: opportunistic NTP (when Wi-Fi is up) + a top-up before auto-standby, with Mesh adverts as a passive source. Quality model (estErr = learned drift × time since sync) with exponential back-off, s_clockConfident bootstrap for the first advert after boot, POSIX time zone (default Europe/Berlin incl. DST), settings rows \"Time zone\"/\"Time\", and console time / time set / time sync / tz.
    • \n
\n

📋 Full history: CHANGELOG.md

\n" }, { "version": "v1.6.3", "name": "v1.6.3", "datetime": "2026-06-13T04:03:32Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.6.3", "prerelease": false, "notes": "## 📡 Mesh SD persistence & clock hardening\n- Contact mirror (`/meshcore/contacts.bin`, SD takes load priority over SPIFFS, deferred write from `loop()`) and joined hashtag channels (`/meshcore/channels.txt`, re-joined on boot).\n- RTC sync guard against future-clock outliers (bootstrap + forward jumps < 1 h, backward only on a 3× advert consensus).\n- Contact overflow fix: overwrite the oldest non-favorite when the table (64) is full instead of dropping new adverts.\n- Console hashtag commands `join` / `chan`, plus a new `i2cscan` command. Verified on device: the T-Deck Pro V1.1 has **no hardware RTC** (0x51 empty).", "notesHtml": "

📡 Mesh SD persistence & clock hardening

\n
    \n
  • Contact mirror (/meshcore/contacts.bin, SD takes load priority over SPIFFS, deferred write from loop()) and joined hashtag channels (/meshcore/channels.txt, re-joined on boot).
    • \n
  • RTC sync guard against future-clock outliers (bootstrap + forward jumps < 1 h, backward only on a 3× advert consensus).
    • \n
  • Contact overflow fix: overwrite the oldest non-favorite when the table (64) is full instead of dropping new adverts.
    • \n
  • Console hashtag commands join / chan, plus a new i2cscan command. Verified on device: the T-Deck Pro V1.1 has no hardware RTC (0x51 empty).
    • \n
\n" }, { "version": "v1.6.2", "name": "v1.6.2", "datetime": "2026-06-13T04:03:31Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.6.2", "prerelease": false, "notes": "## 📄 Licensing\n- SPDX `GPL-3.0-or-later` / © Dr. Daniel Dumke headers added to all Fennek-owned `src` files (the vendored Hynitron touch driver in `src/core/hyn/` is left untouched).\n- Options screen now shows an author/copyright footer.", "notesHtml": "

📄 Licensing

\n
    \n
  • SPDX GPL-3.0-or-later / © Dr. Daniel Dumke headers added to all Fennek-owned src files (the vendored Hynitron touch driver in src/core/hyn/ is left untouched).
    • \n
  • Options screen now shows an author/copyright footer.
    • \n
\n" }, { "version": "v1.6.1", "name": "v1.6.1", "datetime": "2026-06-13T04:03:30Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.6.1", "prerelease": false, "notes": "## 📡 Mesh app overhaul (MVP)\n- Contacts split from the chat list (chats show only channels + contacts with history; a new contacts screen lists all adverts).\n- HH:MM timestamps + touch scrollback in conversations.\n- Status line (noise floor / RX / TX / contacts / clock), contact detail view (hops + last seen).\n- Touch scroll strip for lists, error-retry button, DM resend on timeout, and multi-ACK tracking for parallel DMs.", "notesHtml": "

📡 Mesh app overhaul (MVP)

\n
    \n
  • Contacts split from the chat list (chats show only channels + contacts with history; a new contacts screen lists all adverts).
    • \n
  • HH:MM timestamps + touch scrollback in conversations.
    • \n
  • Status line (noise floor / RX / TX / contacts / clock), contact detail view (hops + last seen).
    • \n
  • Touch scroll strip for lists, error-retry button, DM resend on timeout, and multi-ACK tracking for parallel DMs.
    • \n
\n" }, { "version": "v1.6.0", "name": "v1.6.0", "datetime": "2026-06-13T04:03:29Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.6.0", "prerelease": false, "notes": "## ✨ Added\n- **Unlimited music library:** on-demand growing PSRAM blocks (instead of `MAX_TRACKS=512`), track cache `/.fennek/tracks.bin` (boot in seconds), background scan in `readdir` chunks. Scans pause during playback (anti-stutter). Track paths up to 256 chars (Calibre).\n- **Web file manager** (Files app + `webfm`): Wi-Fi station with an embedded HTML page + JSON API to browse/upload/download/delete SD files over `http://fennek.local`.\n- Console: `sleep` command + boot/reset diagnostics in `status`.", "notesHtml": "

✨ Added

\n
    \n
  • Unlimited music library: on-demand growing PSRAM blocks (instead of MAX_TRACKS=512), track cache /.fennek/tracks.bin (boot in seconds), background scan in readdir chunks. Scans pause during playback (anti-stutter). Track paths up to 256 chars (Calibre).
    • \n
  • Web file manager (Files app + webfm): Wi-Fi station with an embedded HTML page + JSON API to browse/upload/download/delete SD files over http://fennek.local.
    • \n
  • Console: sleep command + boot/reset diagnostics in status.
    • \n
\n" }, { "version": "v1.5.0", "name": "v1.5.0", "datetime": "2026-06-13T04:03:29Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.5.0", "prerelease": false, "notes": "## 🌍 Localization\n- Extended with **English and Spanish** (`FENNEK_STRS` now 5 columns, EN/ES appended — NVS-compatible).\n- Documented the CP437 limitation for missing uppercase accented characters.\n- Reader rescan rework, chess brace fixes, MeshSeeLog entry.", "notesHtml": "

🌍 Localization

\n
    \n
  • Extended with English and Spanish (FENNEK_STRS now 5 columns, EN/ES appended — NVS-compatible).
    • \n
  • Documented the CP437 limitation for missing uppercase accented characters.
    • \n
  • Reader rescan rework, chess brace fixes, MeshSeeLog entry.
    • \n
\n" }, { "version": "v1.4.0", "name": "v1.4.0", "datetime": "2026-06-13T04:03:28Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.4.0", "prerelease": false, "notes": "## 🌍 Internationalization framework\n- New `core/i18n`: central string table, language selectable in settings, applied across all apps (launcher, music, book, reader, mesh, games, settings).\n- README screenshots + host-side renderer (`tools/screenshot.cpp`) for generating UI screenshots without the device.", "notesHtml": "

🌍 Internationalization framework

\n
    \n
  • New core/i18n: central string table, language selectable in settings, applied across all apps (launcher, music, book, reader, mesh, games, settings).
    • \n
  • README screenshots + host-side renderer (tools/screenshot.cpp) for generating UI screenshots without the device.
    • \n
\n" }, { "version": "v1.3.1", "name": "v1.3.1", "datetime": "2026-06-13T04:03:27Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.3.1", "prerelease": false, "notes": "## 🎨 Standby & project\n- **Standby screen:** AI-generated sleeping fennec as a 1-bit bitmap (Floyd–Steinberg, 240×320) with a bottom banner.\n- GPL-3.0+ license, README reworked as an alternative firmware.\n- Repo slimmed down and detached from the Meck fork; build env renamed `mp3player` → `fennek`.", "notesHtml": "

🎨 Standby & project

\n
    \n
  • Standby screen: AI-generated sleeping fennec as a 1-bit bitmap (Floyd–Steinberg, 240×320) with a bottom banner.
    • \n
  • GPL-3.0+ license, README reworked as an alternative firmware.
    • \n
  • Repo slimmed down and detached from the Meck fork; build env renamed mp3player → fennek.
    • \n
\n" }, { "version": "v1.3.0", "name": "v1.3.0", "datetime": "2026-06-13T04:03:26Z", "url": "https://github.com/danst0/fennek/releases/tag/v1.3.0", "prerelease": false, "notes": "## 🎮 Games app\n- New Games app: **2048, Minesweeper, Chess (Negamax AI), Tic-Tac-Toe**. Game logic lives in Arduino-free, host-tested cores.", "notesHtml": "

🎮 Games app

\n
    \n
  • New Games app: 2048, Minesweeper, Chess (Negamax AI), Tic-Tac-Toe. Game logic lives in Arduino-free, host-tested cores.
    • \n
\n" } ], "changelogSource": "github", "changelogUpdatedAt": "2026-06-21T09:55:29.691Z" }, { "id": "fieldmesh", "name": "FieldMesh", "type": "fork", "maintainer": "TogeriX-hub (Tobias Guertler)", "maintainers": [ { "name": "TogeriX-hub", "url": "https://github.com/TogeriX-hub" } ], "repository": "https://github.com/TogeriX-hub/FieldMesh", "website": "https://www.tobiasguertler.de/blog/en/fieldmesh", "license": "MIT", "description": "A MeshCore firmware fork optimized for outdoor use — festivals, hiking, off-grid events. Adds automatic GPS advertising, dedicated tracking page with distance calculation, Off-Grid mode with legal frequency defaults and one-press toggle, SOS system with buzzer alarms, message history with RAM ring buffer, and text input/send on joystick-equipped devices. Designed to be field-ready: put it in your backpack and trust it's doing its job.\n", "status": "active", "lifecycle": "active", "maturity": "stable", "distribution": "community", "lineage": { "kind": "fork", "upstreamFirmwareId": "meshcore-official", "upstreamRepository": "https://github.com/meshcore-dev/MeshCore" }, "runtime": { "framework": "arduino", "language": "cpp" }, "roles": [ "companion", "repeater", "standalone-ui" ], "features": [ "Automatic GPS advertising (zero-hop, every 5 minutes)", "Dedicated tracking page with Haversine distance calculation", "Off-Grid mode with Client Repeat on separate legal frequencies", "One-press Off-Grid toggle (menu or 5x button press on headless devices)", "SOS system with two-step confirmation and buzzer alarm", "Message history (RAM ring buffer, up to 32 entries)", "Text input and send via joystick (Wio Tracker L1)", "Online node counter on home screen", "Mode indicators (GPS-SHARE, OFF-GRID)", "Headless device support (T1000-E, RAK WiseMesh TAG)", "Forced buzzer feedback for all actions on headless devices", "Splash screen with version info and FieldMesh branding", "Backlight fixes for various displays" ], "capabilities": { "protocol": { "meshcoreCompatible": true, "rawPacketSend": true, "rawPacketObserve": true }, "transports": { "ble": true, "usbSerial": true, "nativeTcp": false, "wifiAp": false }, "operations": { "webFlasher": false, "ota": false, "bleDfu": false, "configurationBackup": true }, "networking": { "repeater": true, "roomServer": false, "observer": false, "mqtt": false, "kissModem": false }, "hardware": { "gps": true, "display": true, "sensors": false, "lowPowerRx": false } }, "changelog": { "source": "github", "repo": "TogeriX-hub/FieldMesh" }, "devices": [ { "id": "thinknode-m1", "status": "supported", "target": "thinknode_m1", "platformio_board": "thinknode_m1", "notes": "E-Ink display, single button; primary development target" }, { "id": "wio-tracker-l1", "status": "supported", "target": "wio-tracker-l1", "platformio_board": "seeed-wio-tracker-l1", "notes": "OLED display (SSD1306/SH1106 128x64), joystick; text input and send supported" }, { "id": "wio-tracker-l1-eink", "status": "supported", "target": "wio-tracker-l1-eink", "platformio_board": "seeed-wio-tracker-l1", "notes": "E-ink variant (GxEPD2 250x122)" }, { "id": "sensecap-t1000e", "status": "supported", "target": "t1000-e", "platformio_board": "tracker-t1000-e", "notes": "Headless device (no display, single button); primary headless reference" }, { "id": "rak-wismesh-tag", "status": "supported", "target": "rak_wismesh_tag", "platformio_board": "rak4631", "notes": "Headless device; contributions welcome" } ], "popularity": { "githubStars": 25, "githubForks": 0, "githubWatchers": 1, "githubOpenIssues": 3, "githubContributors": 151, "releaseDownloads": 0, "latestReleaseDownloads": 0, "lastChecked": "2026-06-21" }, "verification": { "sourceAvailable": true, "releasesAvailable": true, "ciBuilds": true, "lastChecked": "2026-06-21" }, "latest_version": "5.3", "released": "2026-04-28", "releases": [ { "version": "v5.3", "name": "FieldMesh v5.3", "datetime": "2026-04-28T07:00:54Z", "url": "https://github.com/TogeriX-hub/FieldMesh/releases/tag/v5.3", "prerelease": false, "notes": "## [5.3] — MeshCore Upstream Sync\r\n\r\n\r\n### Changes\r\n- **MeshCore upstream alignment** — codebase updated to track MeshCore v1.15.0; no FieldMesh-specific feature changes in this release\r\n\r\n\r\n# Download latest build\r\n## EU Offgrid frequency\r\n[ThinkNode_M1_companion_radio_ble_FieldMeshv5.3.zip](https://github.com/user-attachments/files/27154033/ThinkNode_M1_companion_radio_ble_FieldMeshv5.3.zip)\r\n[WioTrackerL1_companion_radio_ble_FieldMeshv5.3.zip](https://github.com/user-attachments/files/27154037/WioTrackerL1_companion_radio_ble_FieldMeshv5.3.zip)\r\n[t1000e_companion_radio_ble_FieldMeshv5.3.zip](https://github.com/user-attachments/files/27154044/t1000e_companion_radio_ble_FieldMeshv5.3.zip)\r\n\r\n\r\n## US Offgrid frequency\r\n[ThinkNode_M1_companion_radio_ble_USFieldMeshv5.3.zip](https://github.com/user-attachments/files/27154065/ThinkNode_M1_companion_radio_ble_USFieldMeshv5.3.zip)\r\n[WioTrackerL1_companion_radio_ble_USFieldMeshv5.3.zip](https://github.com/user-attachments/files/27154067/WioTrackerL1_companion_radio_ble_USFieldMeshv5.3.zip)\r\n[t1000e_companion_radio_ble_USFieldMeshv5.3.zip](https://github.com/user-attachments/files/27154071/t1000e_companion_radio_ble_USFieldMeshv5.3.zip)", "notesHtml": "

[5.3] — MeshCore Upstream Sync

\n

Changes

\n
    \n
  • MeshCore upstream alignment — codebase updated to track MeshCore v1.15.0; no FieldMesh-specific feature changes in this release
    • \n
\n

Download latest build

\n

EU Offgrid frequency

\n

ThinkNode_M1_companion_radio_ble_FieldMeshv5.3.zip\nWioTrackerL1_companion_radio_ble_FieldMeshv5.3.zip\nt1000e_companion_radio_ble_FieldMeshv5.3.zip

\n

US Offgrid frequency

\n

ThinkNode_M1_companion_radio_ble_USFieldMeshv5.3.zip\nWioTrackerL1_companion_radio_ble_USFieldMeshv5.3.zip\nt1000e_companion_radio_ble_USFieldMeshv5.3.zip

\n" }, { "version": "v5.2", "name": "FieldMesh v5.2", "datetime": "2026-04-09T14:29:21Z", "url": "https://github.com/TogeriX-hub/FieldMesh/releases/tag/v5.2", "prerelease": false, "notes": "## [5.2] — HomeScreen Redesign & Online Node Counter\r\n\r\n### New features\r\n- **Online node counter** — HomeScreen now shows how many nodes have been\r\n heard in the last 30 minutes, combining advert senders and message senders\r\n in a single deduplicated count (16-entry LRU cache)\r\n- **Node counter icon** — the online count is displayed with a filled circle\r\n icon (●) instead of plain [X] text\r\n- **Real channel name in title bar** — message history and favorite preview\r\n now show the actual channel name (e.g. \"Public\") instead of the hardcoded\r\n \"[CH]\" tag\r\n- **Mode indicator** — GPS-SHARE and OFF-GRID modes are now shown on the\r\n HomeScreen FIRST page\r\n\r\n### Changes\r\n- **M1 HomeScreen layout** — node counter fixed at y=22 regardless of\r\n connection state; MSG:X replaces `< Connected >` when disconnected;\r\n nodes_icon y-offset corrected (+3px) to align with text baseline\r\n- **Channel message title bar** — sender name omitted from title bar for\r\n channel messages (already visible inside the message text)\r\n- **Favorite indicator** — clears correctly after all messages are deleted\r\n (deleteEntry / clearAll); no longer persists stale data after app sync\r\n- **MSG:X counter** — hidden on HomeScreen while phone app is connected\r\n- **RECENT/TRACKING pages** — row limits now display-height-adaptive via\r\n max_y variable instead of hardcoded values\r\n\r\n### Bug fixes\r\n- **BLE init: send_queue flood** — between `onSecured()` and `CMD_APP_START`\r\n async pushes could fill all 12 send_queue slots, causing the app to time\r\n out. Fixed via `_app_initialized` flag and `isWriteBusy()` guard\r\n- **Double-counting in node counter** — nodes heard via both advert and\r\n message were counted twice. Fixed via `countOnlineNodesExcluding()`\r\n- **adv_fresh buffer** — was reusing the 4-entry RECENT display array,\r\n capping the advert-based node count at 4. Now uses a dedicated\r\n ADVERT_PATH_TABLE_SIZE (16) buffer\r\n- **formatRelTime undefined behavior** — replaced signed int cast with\r\n safe uint32_t arithmetic\r\n\r\n### Technical notes\r\n- Changes confined to `UITask.cpp`, `UITask.h`, `MyMesh.cpp`, `MyMesh.h`,\r\n `icons.h`\r\n- `DataStore`, `AbstractUITask`, `platformio.ini` unaffected\r\n\r\n# Download latest build\r\n## EU Offgrid frequency\r\n[ThinkNode_M1_companion_radio_ble_FieldMeshv5.2.zip](https://github.com/user-attachments/files/26605877/ThinkNode_M1_companion_radio_ble_FieldMeshv5.2.zip)\r\n[WioTrackerL1_companion_radio_ble_FieldMeshv5.2.zip](https://github.com/user-attachments/files/26605890/WioTrackerL1_companion_radio_ble_FieldMeshv5.2.zip)\r\n[t1000e_companion_radio_ble_FieldMeshv5.2.zip](https://github.com/user-attachments/files/26605896/t1000e_companion_radio_ble_FieldMeshv5.2.zip)\r\n\r\n## US Offgrid frequency\r\n[ThinkNode_M1_companion_radio_ble_USFieldMeshv5.2.zip](https://github.com/user-attachments/files/26605905/ThinkNode_M1_companion_radio_ble_USFieldMeshv5.2.zip)\r\n[WioTrackerL1_companion_radio_ble_USFieldMeshv5.2.zip](https://github.com/user-attachments/files/26605916/WioTrackerL1_companion_radio_ble_USFieldMeshv5.2.zip)\r\n[t1000e_companion_radio_ble_USFieldMeshv5.2.zip](https://github.com/user-attachments/files/26605923/t1000e_companion_radio_ble_USFieldMeshv5.2.zip)", "notesHtml": "

[5.2] — HomeScreen Redesign & Online Node Counter

\n

New features

\n
    \n
  • Online node counter — HomeScreen now shows how many nodes have been\nheard in the last 30 minutes, combining advert senders and message senders\nin a single deduplicated count (16-entry LRU cache)
    • \n
  • Node counter icon — the online count is displayed with a filled circle\nicon (●) instead of plain [X] text
    • \n
  • Real channel name in title bar — message history and favorite preview\nnow show the actual channel name (e.g. \"Public\") instead of the hardcoded\n\"[CH]\" tag
    • \n
  • Mode indicator — GPS-SHARE and OFF-GRID modes are now shown on the\nHomeScreen FIRST page
    • \n
\n

Changes

\n
    \n
  • M1 HomeScreen layout — node counter fixed at y=22 regardless of\nconnection state; MSG:X replaces < Connected > when disconnected;\nnodes_icon y-offset corrected (+3px) to align with text baseline
    • \n
  • Channel message title bar — sender name omitted from title bar for\nchannel messages (already visible inside the message text)
    • \n
  • Favorite indicator — clears correctly after all messages are deleted\n(deleteEntry / clearAll); no longer persists stale data after app sync
    • \n
  • MSG:X counter — hidden on HomeScreen while phone app is connected
    • \n
  • RECENT/TRACKING pages — row limits now display-height-adaptive via\nmax_y variable instead of hardcoded values
    • \n
\n

Bug fixes

\n
    \n
  • BLE init: send_queue flood — between onSecured() and CMD_APP_START\nasync pushes could fill all 12 send_queue slots, causing the app to time\nout. Fixed via _app_initialized flag and isWriteBusy() guard
    • \n
  • Double-counting in node counter — nodes heard via both advert and\nmessage were counted twice. Fixed via countOnlineNodesExcluding()
    • \n
  • adv_fresh buffer — was reusing the 4-entry RECENT display array,\ncapping the advert-based node count at 4. Now uses a dedicated\nADVERT_PATH_TABLE_SIZE (16) buffer
    • \n
  • formatRelTime undefined behavior — replaced signed int cast with\nsafe uint32_t arithmetic
    • \n
\n

Technical notes

\n
    \n
  • Changes confined to UITask.cpp, UITask.h, MyMesh.cpp, MyMesh.h,\nicons.h
    • \n
  • DataStore, AbstractUITask, platformio.ini unaffected
    • \n
\n

Download latest build

\n

EU Offgrid frequency

\n

ThinkNode_M1_companion_radio_ble_FieldMeshv5.2.zip\nWioTrackerL1_companion_radio_ble_FieldMeshv5.2.zip\nt1000e_companion_radio_ble_FieldMeshv5.2.zip

\n

US Offgrid frequency

\n

ThinkNode_M1_companion_radio_ble_USFieldMeshv5.2.zip\nWioTrackerL1_companion_radio_ble_USFieldMeshv5.2.zip\nt1000e_companion_radio_ble_USFieldMeshv5.2.zip

\n" }, { "version": "v5.1", "name": "FieldMesh v5.1", "datetime": "2026-04-04T08:18:12Z", "url": "https://github.com/TogeriX-hub/FieldMesh/releases/tag/v5.1", "prerelease": false, "notes": "## [5.1] — Headless Device Support (T1000-E, RAK WiseMesh TAG)\r\n\r\n### New features\r\n- **Headless device support** — `ui-orig` now fully integrated into FieldMesh; devices with no display and a single button (Seeed T1000-E, RAK WiseMesh TAG) are supported as first-class citizens\r\n- **Off-Grid toggle via 5× click** — 5 presses on the single button toggles Off-Grid mode on/off; buzzer feedback is forced regardless of mute state (ascending tone = on, descending = off)\r\n- **SOS alarm via buzzer** — incoming `!SOS` messages trigger a continuous buzzer siren that overrides quiet mode and loops until acknowledged with a short press\r\n\r\n### Changes\r\n- All button actions (advert, GPS toggle, buzzer toggle, Off-Grid toggle) now produce forced buzzer feedback regardless of quiet mode — essential for display-less operation\r\n- Ascending tone (`c,e`) = feature enabled; descending tone (`e,c`) = feature disabled — consistent across all actions\r\n- `newMsg()` signature updated to include `is_favorite` parameter — compatible with V5 `AbstractUITask` interface\r\n- `refreshDisplay()` and `isOnRecentOrTrackingPage()` added as explicit no-op overrides — required for `MyMesh` compatibility\r\n\r\n### Button mapping (headless devices — single button)\r\n| Press | Action |\r\n|---|---|\r\n| 1× | Wake display / acknowledge SOS alarm |\r\n| 2× | Send advert |\r\n| 3× | Buzzer mute on/off |\r\n| 4× | GPS on/off |\r\n| 5× | Off-Grid mode on/off |\r\n| Long press (first 8 s) | CLI Rescue Mode |\r\n| Long press | Shutdown |\r\n\r\n### Technical notes\r\n- Changes confined to `ui-orig/Button.h`, `ui-orig/Button.cpp`, `ui-orig/UITask.h`, `ui-orig/UITask.cpp`\r\n- `ui-new` (ThinkNode M1, Wio Tracker L1) is completely unaffected\r\n- `_buzzer_restore_quiet` flag ensures non-blocking buzzer playback before quiet state is restored\r\n\r\n# Download latest build\r\n\r\n## EU Offgrid frequency\r\n[ThinkNode_M1_companion_radio_ble_FieldMeshv5.1.zip](https://github.com/user-attachments/files/26479266/ThinkNode_M1_companion_radio_ble_FieldMeshv5.1.zip)\r\n[WioTrackerL1_companion_radio_ble_FieldMeshv5.1.zip](https://github.com/user-attachments/files/26479268/WioTrackerL1_companion_radio_ble_FieldMeshv5.1.zip)\r\n[t1000e_companion_radio_ble_FieldMeshv5.1.zip](https://github.com/user-attachments/files/26479270/t1000e_companion_radio_ble_FieldMeshv5.1.zip)\r\n\r\n## US Offgrid frequency\r\n[ThinkNode_M1_companion_radio_ble_USFieldMeshv5.1.zip](https://github.com/user-attachments/files/26479519/ThinkNode_M1_companion_radio_ble_USFieldMeshv5.1.zip)\r\n[WioTrackerL1_companion_radio_ble_USFieldMeshv5.1.zip](https://github.com/user-attachments/files/26479520/WioTrackerL1_companion_radio_ble_USFieldMeshv5.1.zip)\r\n[t1000e_companion_radio_ble_USFieldMeshv5.1.zip](https://github.com/user-attachments/files/26479521/t1000e_companion_radio_ble_USFieldMeshv5.1.zip)", "notesHtml": "

[5.1] — Headless Device Support (T1000-E, RAK WiseMesh TAG)

\n

New features

\n
    \n
  • Headless device support — ui-orig now fully integrated into FieldMesh; devices with no display and a single button (Seeed T1000-E, RAK WiseMesh TAG) are supported as first-class citizens
    • \n
  • Off-Grid toggle via 5× click — 5 presses on the single button toggles Off-Grid mode on/off; buzzer feedback is forced regardless of mute state (ascending tone = on, descending = off)
    • \n
  • SOS alarm via buzzer — incoming !SOS messages trigger a continuous buzzer siren that overrides quiet mode and loops until acknowledged with a short press
    • \n
\n

Changes

\n
    \n
  • All button actions (advert, GPS toggle, buzzer toggle, Off-Grid toggle) now produce forced buzzer feedback regardless of quiet mode — essential for display-less operation
    • \n
  • Ascending tone (c,e) = feature enabled; descending tone (e,c) = feature disabled — consistent across all actions
    • \n
  • newMsg() signature updated to include is_favorite parameter — compatible with V5 AbstractUITask interface
    • \n
  • refreshDisplay() and isOnRecentOrTrackingPage() added as explicit no-op overrides — required for MyMesh compatibility
    • \n
\n

Button mapping (headless devices — single button)

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PressAction
1×Wake display / acknowledge SOS alarm
2×Send advert
3×Buzzer mute on/off
4×GPS on/off
5×Off-Grid mode on/off
Long press (first 8 s)CLI Rescue Mode
Long pressShutdown
\n

Technical notes

\n
    \n
  • Changes confined to ui-orig/Button.h, ui-orig/Button.cpp, ui-orig/UITask.h, ui-orig/UITask.cpp
    • \n
  • ui-new (ThinkNode M1, Wio Tracker L1) is completely unaffected
    • \n
  • _buzzer_restore_quiet flag ensures non-blocking buzzer playback before quiet state is restored
    • \n
\n

Download latest build

\n

EU Offgrid frequency

\n

ThinkNode_M1_companion_radio_ble_FieldMeshv5.1.zip\nWioTrackerL1_companion_radio_ble_FieldMeshv5.1.zip\nt1000e_companion_radio_ble_FieldMeshv5.1.zip

\n

US Offgrid frequency

\n

ThinkNode_M1_companion_radio_ble_USFieldMeshv5.1.zip\nWioTrackerL1_companion_radio_ble_USFieldMeshv5.1.zip\nt1000e_companion_radio_ble_USFieldMeshv5.1.zip

\n" }, { "version": "v5.09", "name": "Release v5.09 — Message History & Text Input", "datetime": "2026-04-03T12:35:15Z", "url": "https://github.com/TogeriX-hub/FieldMesh/releases/tag/v5.09", "prerelease": false, "notes": "FieldMesh V5 — the first release that makes the node fully standalone for messaging. No phone required.\r\n\r\n## What's new\r\n\r\n### Message History (ThinkNode M1 + Wio Tracker L1)\r\n- Received messages are stored on the device and browsable without the companion app\r\n- Home screen redesigned: shows unread counter and the name + timestamp of the most recent message from a favourite contact\r\n- Long press on home screen opens the message menu (filter: All / Favourites)\r\n- One message per view, newest first — short press = next, long press = clear all\r\n- Channel tag (`[CH1]`, `[DM]`) and timestamp shown per message\r\n- New message while history is open: `+1 new` alert, no automatic screen switch\r\n\r\n### Text Input & Send (Wio Tracker L1 only)\r\n- Compose and send channel messages directly from the device via joystick\r\n- Channel select → character compose → \"Sent!\" confirmation\r\n- Character selection via joystick left/right, confirm with short press, send with long press\r\n- 80 character limit\r\n\r\n## Important notes\r\n- Message history is RAM-only — messages are lost on reboot. This is intentional: smartphone sync via the companion app is never affected by what the device shows or clears.\r\n- Text send is available on Wio Tracker L1 only. Single-button input on ThinkNode M1 does not support text composition.\r\n- No DM sending — channel messages only.\r\n\r\n## Files changed\r\n`UITask.h`, `UITask.cpp`, `MyMesh.h`, `MyMesh.cpp`, `AbstractUITask.h`\r\n\r\n## Full changelog\r\nSee [RELEASE.md](RELEASE.md) for the complete version history.\r\n\r\n[ThinkNode_M1_companion_radio_ble_FieldMeshv5.09.zip](https://github.com/user-attachments/files/26460200/ThinkNode_M1_companion_radio_ble_FieldMeshv5.09.zip)\r\n\r\n[WioTrackerL1_companion_radio_ble_FieldMeshv5.09.zip](https://github.com/user-attachments/files/26460205/WioTrackerL1_companion_radio_ble_FieldMeshv5.09.zip)", "notesHtml": "

FieldMesh V5 — the first release that makes the node fully standalone for messaging. No phone required.

\n

What's new

\n

Message History (ThinkNode M1 + Wio Tracker L1)

\n
    \n
  • Received messages are stored on the device and browsable without the companion app
    • \n
  • Home screen redesigned: shows unread counter and the name + timestamp of the most recent message from a favourite contact
    • \n
  • Long press on home screen opens the message menu (filter: All / Favourites)
    • \n
  • One message per view, newest first — short press = next, long press = clear all
    • \n
  • Channel tag ([CH1], [DM]) and timestamp shown per message
    • \n
  • New message while history is open: +1 new alert, no automatic screen switch
    • \n
\n

Text Input & Send (Wio Tracker L1 only)

\n
    \n
  • Compose and send channel messages directly from the device via joystick
    • \n
  • Channel select → character compose → \"Sent!\" confirmation
    • \n
  • Character selection via joystick left/right, confirm with short press, send with long press
    • \n
  • 80 character limit
    • \n
\n

Important notes

\n
    \n
  • Message history is RAM-only — messages are lost on reboot. This is intentional: smartphone sync via the companion app is never affected by what the device shows or clears.
    • \n
  • Text send is available on Wio Tracker L1 only. Single-button input on ThinkNode M1 does not support text composition.
    • \n
  • No DM sending — channel messages only.
    • \n
\n

Files changed

\n

UITask.h, UITask.cpp, MyMesh.h, MyMesh.cpp, AbstractUITask.h

\n

Full changelog

\n

See RELEASE.md for the complete version history.

\n

ThinkNode_M1_companion_radio_ble_FieldMeshv5.09.zip

\n

WioTrackerL1_companion_radio_ble_FieldMeshv5.09.zip

\n" }, { "version": "v4.04", "name": "FieldMesh v4.04", "datetime": "2026-03-30T20:55:22Z", "url": "https://github.com/TogeriX-hub/FieldMesh/releases/tag/v4.04", "prerelease": false, "notes": "## V4.04 — Wio Tracker L1 Joystick UI Fixes\r\n\r\n\r\n### target.cpp / target.h\r\n- Added `joystick_up` (`JOYSTICK_UP`) and `joystick_down` (`JOYSTICK_DOWN`) as `MomentaryButton`\r\n\r\n### UITask.cpp — loop()\r\n- Joystick Up → `KEY_PREV`, Joystick Down → `KEY_NEXT`\r\n- Joystick press short → `KEY_ENTER` (confirm in menus)\r\n- Joystick press long → `handleLongPress()` (context action)\r\n\r\n### UITask.cpp — HomeScreen\r\n- Removed dead code: `KEY_ENTER` on Tracking page directly toggled GPS-Share — unused since V2.02 (Outdoor Menu), but accidentally active on Wio Tracker\r\n- Tracking hint text: `\"Settings: press Enter\"` (joystick) instead of `\"Settings: long press\"`\r\n\r\n### UITask.cpp — OutdoorMenuScreen\r\n- Removed footer `\"short=next long=select\"` on joystick devices (self-explanatory)\r\n- Menu navigation: Up/Down instead of Left/Right\r\n\r\n### UITask.cpp — SOSSendScreen\r\n- `handleLongPress()` now sends `KEY_SELECT` instead of `KEY_ENTER` to `SOSSendScreen` to distinguish short and long press\r\n- Short press = always go back (both states)\r\n- Long press = confirm / send (both states)\r\n- Hint text both states: `\"long press: SEND`\r\n\r\n[ThinkNode_M1_companion_radio_ble_FieldMeshv4.04.zip](https://github.com/user-attachments/files/26416861/ThinkNode_M1_companion_radio_ble_FieldMeshv4.04.zip)\r\n\r\n\r\n[WioTrackerL1_companion_radio_ble_FieldMeshv4.04.zip](https://github.com/user-attachments/files/26416618/WioTrackerL1_companion_radio_ble_FieldMeshv4.04.zip)", "notesHtml": "

V4.04 — Wio Tracker L1 Joystick UI Fixes

\n

target.cpp / target.h

\n
    \n
  • Added joystick_up (JOYSTICK_UP) and joystick_down (JOYSTICK_DOWN) as MomentaryButton
    • \n
\n

UITask.cpp — loop()

\n
    \n
  • Joystick Up → KEY_PREV, Joystick Down → KEY_NEXT
    • \n
  • Joystick press short → KEY_ENTER (confirm in menus)
    • \n
  • Joystick press long → handleLongPress() (context action)
    • \n
\n

UITask.cpp — HomeScreen

\n
    \n
  • Removed dead code: KEY_ENTER on Tracking page directly toggled GPS-Share — unused since V2.02 (Outdoor Menu), but accidentally active on Wio Tracker
    • \n
  • Tracking hint text: \"Settings: press Enter\" (joystick) instead of \"Settings: long press\"
    • \n
\n

UITask.cpp — OutdoorMenuScreen

\n
    \n
  • Removed footer \"short=next long=select\" on joystick devices (self-explanatory)
    • \n
  • Menu navigation: Up/Down instead of Left/Right
    • \n
\n

UITask.cpp — SOSSendScreen

\n
    \n
  • handleLongPress() now sends KEY_SELECT instead of KEY_ENTER to SOSSendScreen to distinguish short and long press
    • \n
  • Short press = always go back (both states)
    • \n
  • Long press = confirm / send (both states)
    • \n
  • Hint text both states: \"long press: SEND
    • \n
\n

ThinkNode_M1_companion_radio_ble_FieldMeshv4.04.zip

\n

WioTrackerL1_companion_radio_ble_FieldMeshv4.04.zip

\n" }, { "version": "v4.03", "name": "FieldMesh V4.03", "datetime": "2026-03-30T14:46:33Z", "url": "https://github.com/TogeriX-hub/FieldMesh/releases/tag/v4.03", "prerelease": false, "notes": "## V4.03 – Backlight & Display Logic Overhaul\r\n\r\n### Fixed\r\n- `AUTO_OFF_MILLIS=0` removed from `platformio.ini` – display now correctly sleeps after 15 seconds of inactivity\r\n- 5-minute backlight auto-off timer removed – no longer needed with display sleep active\r\n- Backlight now correctly follows `_backlight_on` state on every `turnOn()` call, overriding GxEPD driver behavior\r\n\r\n### Improved\r\n- Backlight state is fully decoupled from display wake events – incoming messages and adverts wake the display without changing the backlight state\r\n- Added `refreshDisplay()` – wakes display briefly on incoming adverts when on Recent or Tracking page, without affecting backlight\r\n- Advert-triggered display refresh works even when a phone is connected via BLE\r\n\r\n### Technical\r\n- Added `refreshDisplay()` and `isOnRecentOrTrackingPage()` to `AbstractUITask` as virtual methods\r\n- `_backlight_off_at` member removed from `UITask`", "notesHtml": "

V4.03 – Backlight & Display Logic Overhaul

\n

Fixed

\n
    \n
  • AUTO_OFF_MILLIS=0 removed from platformio.ini – display now correctly sleeps after 15 seconds of inactivity
    • \n
  • 5-minute backlight auto-off timer removed – no longer needed with display sleep active
    • \n
  • Backlight now correctly follows _backlight_on state on every turnOn() call, overriding GxEPD driver behavior
    • \n
\n

Improved

\n
    \n
  • Backlight state is fully decoupled from display wake events – incoming messages and adverts wake the display without changing the backlight state
    • \n
  • Added refreshDisplay() – wakes display briefly on incoming adverts when on Recent or Tracking page, without affecting backlight
    • \n
  • Advert-triggered display refresh works even when a phone is connected via BLE
    • \n
\n

Technical

\n
    \n
  • Added refreshDisplay() and isOnRecentOrTrackingPage() to AbstractUITask as virtual methods
    • \n
  • _backlight_off_at member removed from UITask
    • \n
\n" } ], "changelogSource": "github", "changelogUpdatedAt": "2026-06-21T09:55:30.022Z" }, { "id": "mclite", "name": "MCLite", "type": "fork", "maintainer": "laserir", "description": "A lightweight off-grid communicator firmware for the LilyGo T-Deck Plus and T-Watch Ultra. Purpose-built for emergency and outdoor communication — no internet, no cell towers needed. SD card configuration, web flasher, and room server support. Compatible with MeshCore apps.\n", "repository": "https://github.com/laserir/MCLite", "license": "MIT", "status": "active", "lifecycle": "active", "maturity": "beta", "distribution": "community", "lineage": { "kind": "fork", "upstreamFirmwareId": "meshcore-official", "upstreamRepository": "https://github.com/meshcore-dev/MeshCore" }, "runtime": { "framework": "arduino", "language": "cpp" }, "roles": [ "companion" ], "features": [ "Web flasher (Chrome/Edge)", "SD card configuration (one person sets up, copies to everyone)", "Room server support (up to 8)", "On-screen keyboard", "GPS support", "No accounts, no pairing, no per-device setup" ], "capabilities": { "protocol": { "meshcoreCompatible": true }, "transports": { "ble": true, "usbSerial": true, "nativeTcp": false, "wifiAp": false }, "operations": { "ota": false, "webFlasher": true }, "networking": { "repeater": false, "roomServer": false, "observer": false, "kissModem": false }, "hardware": { "gps": true, "display": true, "sensors": false, "lowPowerRx": false } }, "devices": [ { "id": "lilygo-t-deck", "status": "supported", "notes": "T-Deck Plus — primary target with QWERTY keyboard, trackball, GPS." }, { "id": "lilygo-twatch-s3", "status": "supported", "notes": "T-Watch Ultra — wrist-worn with AMOLED touchscreen." } ], "popularity": { "githubStars": 17, "githubForks": 2, "githubWatchers": 3, "githubOpenIssues": 2, "githubContributors": 3, "releaseDownloads": 179, "latestReleaseDownloads": 6, "lastChecked": "2026-06-21" }, "verification": { "sourceAvailable": true, "releasesAvailable": true, "ciBuilds": true, "lastChecked": "2026-06-21" }, "latest_version": "0.3.9", "released": "2026-06-21", "releases": [ { "version": "v0.3.9", "name": "0.3.9", "datetime": "2026-06-21T08:09:35Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.3.9", "prerelease": false, "notes": "### Added\n- **Step-wise admin permissions.** Beyond the existing `security.admin_enabled` (global on/off for the Admin\n screen), a new `permissions` config block scopes what's reachable *inside* Admin: `permissions.settings`\n (`full` / `restricted` / `none`) — **restricted** keeps only the basics editable (brightness, auto-dim, dim\n brightness, keyboard brightness, theme) and shows everything else read-only (no chevron); **none** makes all\n settings read-only. `permissions.companion` (default on) hides the Companion group (WiFi/USB/Bluetooth) when\n off — configured services still run. `permissions.conversation_management` (default off) is reserved for a\n future release (on-device add/edit/remove of contacts/channels/rooms; they stay read-only views for now). All\n three are provisionable from the config tool. Defaults are fully permissive, so existing configs are unchanged.\n- **Settings reorganised into per-section screens + Admin is now a pure hub.** The on-device Admin screen no\n longer mixes settings, diagnostics and shortcuts — it's three labelled groups of links: **Companion** (WiFi /\n USB / Bluetooth), **Conversations** (Contacts / Channels / Rooms, read-only views), and **Settings** (Device,\n Radio, Display, Messaging, Sound, GPS, Battery, Security). Each section is its own screen mirroring the config\n tool, with all of its editable settings *and* its read-only diagnostics in one place (no more duplicated rows\n across Admin and Device Settings). Newly editable on-device: **Radio** (region preset picker — EU/UK/CH vs\n US/Canada — plus a TX-power slider and an advert-interval picker; frequency/SF/BW/CR/scope/path-hash stay read-only),\n **Messaging** (history, max-per-chat, location format, retries, telemetry request/badges/auto-refresh, canned\n messages, allow-mute), and **GPS** (enable, location-advert precision, timezone, clock offset, last-known max\n age). Offgrid mode and the live Heard-Adverts count now live at the top of the Radio screen. Each hub link\n carries an icon (gear for settings; `@`/`#`/`R` for contacts/channels/rooms; Wi-Fi/USB/Bluetooth for\n companion), and the 3rd-party licenses moved to an *About* block at the bottom of the hub. Radio/GPS changes\n reboot once on exit (same batched-save model as theme/language). The old single \"Device Settings\" screen is\n superseded by this layout.\n- **Selectable UI themes.** Choose a color palette — **Dark** (default), **Light**, **Amber** (a \"military\"\n night mode that preserves night vision), or **High contrast** — on-device (Admin → Theme, reboots to apply)\n or via `display.theme` in config. Custom palettes can be defined under `display.themes` (start from a built-in\n `base`, override any color with `#RRGGBB`). Default appearance is unchanged. On/off switches now use the\n theme accent colour too. Thanks [@jason-s13r](https://github.com/jason-s13r) (#24).\n- **Per-row Info + Map buttons on the Heard Adverts screen.** Each heard node now has an explicit info (eye)\n button that opens its detail dialog, and — when the advert carries a location — a map button that opens the\n map centered on that node. Back now returns to the Admin screen. Thanks [@jason-s13r](https://github.com/jason-s13r) (#15).\n- **Map screen pan buttons + windowed chrome.** The map gains an on-screen D-pad (up/left/centre/right/down)\n alongside the existing drag-to-pan. On the T-Deck the map now keeps the **status bar visible** and uses the\n standard `lv_win` header with a back button (the T-Watch stays full-screen). Thanks [@jason-s13r](https://github.com/jason-s13r) (#22, supersedes #20/#21).\n- **Uptime + last-charged in the Admin Battery section.** Shows when the device booted (wall-clock + relative)\n and when charging last stopped (with the level at the time). Thanks [@jason-s13r](https://github.com/jason-s13r) (#23).\n- **On-device Device Settings.** A new editable settings screen (Admin → Device Settings, behind the existing\n `admin.enabled` gate) for changing device n\n…", "notesHtml": "

Added

\n
    \n
  • Step-wise admin permissions. Beyond the existing security.admin_enabled (global on/off for the Admin\nscreen), a new permissions config block scopes what's reachable inside Admin: permissions.settings\n(full / restricted / none) — restricted keeps only the basics editable (brightness, auto-dim, dim\nbrightness, keyboard brightness, theme) and shows everything else read-only (no chevron); none makes all\nsettings read-only. permissions.companion (default on) hides the Companion group (WiFi/USB/Bluetooth) when\noff — configured services still run. permissions.conversation_management (default off) is reserved for a\nfuture release (on-device add/edit/remove of contacts/channels/rooms; they stay read-only views for now). All\nthree are provisionable from the config tool. Defaults are fully permissive, so existing configs are unchanged.
    • \n
  • Settings reorganised into per-section screens + Admin is now a pure hub. The on-device Admin screen no\nlonger mixes settings, diagnostics and shortcuts — it's three labelled groups of links: Companion (WiFi /\nUSB / Bluetooth), Conversations (Contacts / Channels / Rooms, read-only views), and Settings (Device,\nRadio, Display, Messaging, Sound, GPS, Battery, Security). Each section is its own screen mirroring the config\ntool, with all of its editable settings and its read-only diagnostics in one place (no more duplicated rows\nacross Admin and Device Settings). Newly editable on-device: Radio (region preset picker — EU/UK/CH vs\nUS/Canada — plus a TX-power slider and an advert-interval picker; frequency/SF/BW/CR/scope/path-hash stay read-only),\nMessaging (history, max-per-chat, location format, retries, telemetry request/badges/auto-refresh, canned\nmessages, allow-mute), and GPS (enable, location-advert precision, timezone, clock offset, last-known max\nage). Offgrid mode and the live Heard-Adverts count now live at the top of the Radio screen. Each hub link\ncarries an icon (gear for settings; @/#/R for contacts/channels/rooms; Wi-Fi/USB/Bluetooth for\ncompanion), and the 3rd-party licenses moved to an About block at the bottom of the hub. Radio/GPS changes\nreboot once on exit (same batched-save model as theme/language). The old single \"Device Settings\" screen is\nsuperseded by this layout.
    • \n
  • Selectable UI themes. Choose a color palette — Dark (default), Light, Amber (a \"military\"\nnight mode that preserves night vision), or High contrast — on-device (Admin → Theme, reboots to apply)\nor via display.theme in config. Custom palettes can be defined under display.themes (start from a built-in\nbase, override any color with #RRGGBB). Default appearance is unchanged. On/off switches now use the\ntheme accent colour too. Thanks @jason-s13r (#24).
    • \n
  • Per-row Info + Map buttons on the Heard Adverts screen. Each heard node now has an explicit info (eye)\nbutton that opens its detail dialog, and — when the advert carries a location — a map button that opens the\nmap centered on that node. Back now returns to the Admin screen. Thanks @jason-s13r (#15).
    • \n
  • Map screen pan buttons + windowed chrome. The map gains an on-screen D-pad (up/left/centre/right/down)\nalongside the existing drag-to-pan. On the T-Deck the map now keeps the status bar visible and uses the\nstandard lv_win header with a back button (the T-Watch stays full-screen). Thanks @jason-s13r (#22, supersedes #20/#21).
    • \n
  • Uptime + last-charged in the Admin Battery section. Shows when the device booted (wall-clock + relative)\nand when charging last stopped (with the level at the time). Thanks @jason-s13r (#23).
    • \n
  • On-device Device Settings. A new editable settings screen (Admin → Device Settings, behind the existing\nadmin.enabled gate) for changing device n\n…
    • \n
\n" }, { "version": "v0.3.8", "name": "MCLite 0.3.8", "datetime": "2026-06-16T09:19:15Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.3.8", "prerelease": false, "notes": "## Highlights\n\n**Less advert spam, more location privacy.**\n\n### Added\n- **Location-advert privacy precision.** The location-advert setting (now `gps.location_precision`) can coarsen the position you broadcast: **Off · Exact · ~100 m · ~750 m · ~3 km · ~12 km · ~50 km** (Meshtastic-style grid snapping, centred in the cell). Only the broadcast advert is coarsened — **telemetry replies to authorized contacts and the in-chat GPS insert always use your exact position**. Default off; old `location_advert: true/false` configs are read automatically. Scheme adopted from @jason-s13r.\n- **Zero-hop \"Local\" advert button** on the Heard Adverts screen — announce yourself to immediate neighbours without flooding the whole mesh.\n\n### Changed\n- **No more periodic flood adverts by default** (#13). MCLite previously flooded a mesh-wide advert every ~9 min; on a 110-repeater mesh one device generated ~half of all adverts. Now it sends a single flood advert **on boot** and otherwise advertises **on demand** — matching stock MeshCore clients. Thanks @stucamp and @jason-s13r.\n- **Opt-in periodic advert** — new `radio.advert_interval_min` field (config tool → Radio) re-enables periodic adverts for ad-hoc / SAR / private meshes. Default 0 = off; if set, enforced to ≥60 min (720 / 12 h recommended).\n- **GPS button inserts your location into the message** instead of a \"Send Location?\" confirm — append `@ ` to the input, add context, send normally (byte-guarded against the 160-byte limit).\n\n---\nFlash from the web flasher or grab the merged `.bin` below. T-Deck Plus: `mclite-v0.3.8.bin` · T-Watch Ultra: `mclite-watch-v0.3.8.bin`.", "notesHtml": "

Highlights

\n

Less advert spam, more location privacy.

\n

Added

\n
    \n
  • Location-advert privacy precision. The location-advert setting (now gps.location_precision) can coarsen the position you broadcast: Off · Exact · ~100 m · ~750 m · ~3 km · ~12 km · ~50 km (Meshtastic-style grid snapping, centred in the cell). Only the broadcast advert is coarsened — telemetry replies to authorized contacts and the in-chat GPS insert always use your exact position. Default off; old location_advert: true/false configs are read automatically. Scheme adopted from @jason-s13r.
    • \n
  • Zero-hop \"Local\" advert button on the Heard Adverts screen — announce yourself to immediate neighbours without flooding the whole mesh.
    • \n
\n

Changed

\n
    \n
  • No more periodic flood adverts by default (#13). MCLite previously flooded a mesh-wide advert every ~9 min; on a 110-repeater mesh one device generated ~half of all adverts. Now it sends a single flood advert on boot and otherwise advertises on demand — matching stock MeshCore clients. Thanks @stucamp and @jason-s13r.
    • \n
  • Opt-in periodic advert — new radio.advert_interval_min field (config tool → Radio) re-enables periodic adverts for ad-hoc / SAR / private meshes. Default 0 = off; if set, enforced to ≥60 min (720 / 12 h recommended).
    • \n
  • GPS button inserts your location into the message instead of a \"Send Location?\" confirm — append @ <coords> to the input, add context, send normally (byte-guarded against the 160-byte limit).
    • \n
\n
\n

Flash from the web flasher or grab the merged .bin below. T-Deck Plus: mclite-v0.3.8.bin · T-Watch Ultra: mclite-watch-v0.3.8.bin.

\n" }, { "version": "v0.3.7", "name": "MCLite 0.3.7", "datetime": "2026-06-15T09:34:57Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.3.7", "prerelease": false, "notes": "MCLite 0.3.7 — tappable map coordinates, lv_win screen chrome, and on-device screenshots.\n\n## Added\n- **Tap a shared location to open it on the map.** A received/sent message containing a GPS position — decimal `lat, lon` or MGRS/UTMREF — shows an underlined \"Open in map\" link under the bubble; tapping it opens the map centered there. Touch-only, shown only when map tiles are present on SD. Adds a reverse MGRS→lat/lon parser, unit-tested.\n- **Screenshot to SD** (debug aid, off by default). Enable `debug.screenshots` (config tool → Display) and capture the current screen to `/screenshots/*.bmp` (24-bit BMP, opens on any PC) — T-Deck: **Shift+$**; T-Watch: **double-press the side (PEK) button**. (Top-layer overlays like toasts/PIN/SOS aren't captured.)\n\n## Changed\n- **Heard Adverts** screen now uses the standard `lv_win` chrome (back arrow + title + action buttons) — the first step of rolling consistent screen headers across the app (community PR #8, @jason-s13r).\n\n## Removed\n- The non-functional Alt+L \"insert location\" keyboard shortcut (the chat GPS button already does this).\n\n## Notes\n- Config tool: \"Save screenshots\" toggle (Display); Security section relayout (Lock + Auto Lock on one line, Admin Screen separate).\n- Both boards (T-Deck Plus, T-Watch Ultra) build; 246 native tests pass.", "notesHtml": "

MCLite 0.3.7 — tappable map coordinates, lv_win screen chrome, and on-device screenshots.

\n

Added

\n
    \n
  • Tap a shared location to open it on the map. A received/sent message containing a GPS position — decimal lat, lon or MGRS/UTMREF — shows an underlined \"Open in map\" link under the bubble; tapping it opens the map centered there. Touch-only, shown only when map tiles are present on SD. Adds a reverse MGRS→lat/lon parser, unit-tested.
    • \n
  • Screenshot to SD (debug aid, off by default). Enable debug.screenshots (config tool → Display) and capture the current screen to /screenshots/*.bmp (24-bit BMP, opens on any PC) — T-Deck: Shift+$; T-Watch: double-press the side (PEK) button. (Top-layer overlays like toasts/PIN/SOS aren't captured.)
    • \n
\n

Changed

\n
    \n
  • Heard Adverts screen now uses the standard lv_win chrome (back arrow + title + action buttons) — the first step of rolling consistent screen headers across the app (community PR #8, @jason-s13r).
    • \n
\n

Removed

\n
    \n
  • The non-functional Alt+L \"insert location\" keyboard shortcut (the chat GPS button already does this).
    • \n
\n

Notes

\n
    \n
  • Config tool: \"Save screenshots\" toggle (Display); Security section relayout (Lock + Auto Lock on one line, Admin Screen separate).
    • \n
  • Both boards (T-Deck Plus, T-Watch Ultra) build; 246 native tests pass.
    • \n
\n" }, { "version": "v0.3.6", "name": "MCLite 0.3.6", "datetime": "2026-06-12T09:45:06Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.3.6", "prerelease": false, "notes": "MCLite 0.3.6 — emoji, three-step volume, and reliability polish.\n\n## Added\n- **Emoji in chat** — received emoji render inline (monochrome OpenMoji font with a Montserrat fallback, so plain text is unchanged and unknown glyphs degrade gracefully). An on-device emoji picker (`display.emoji`, default on, can be disabled) adds a smiley button to compose from a curated set, capped to the 160-byte message budget. Incoming/outgoing text is sanitized (strips emoji variation selectors, normalizes smart quotes to ASCII). Adopted from the @jason-s13r fork; OpenMoji is CC-BY-SA 4.0.\n- **Three-step volume** — the status-bar bell now cycles max → mute → mid → max; the built-in chime and custom WAV notifications scale to the level. Default is max (loudness unchanged); SOS stays fixed and loud (@jason-s13r, #11).\n\n## Changed\n- **`sound.enabled` is now a true master switch.** `false` means fully silent — no notifications, no chime, and no SOS sound — and the status-bar bell is hidden. Set `true` (the default) for the 3-step volume bell.\n\n## Fixed\n- A last-known position restored after reboot no longer reports \"~0s ago\" before the clock has synced — it shows \"Last known position\" until GPS/NTP re-locks, then the real age.\n- A failed send now shows a \"Send failed - try again\" toast instead of a silently FAILED bubble (still tap-to-retry).\n- Map tile loader hardening: oversized/corrupt PNGs and out-of-range tile coordinates are rejected and grey-filled cleanly.\n\nBoth boards (T-Deck Plus, T-Watch Ultra) build; 219 native tests pass.", "notesHtml": "

MCLite 0.3.6 — emoji, three-step volume, and reliability polish.

\n

Added

\n
    \n
  • Emoji in chat — received emoji render inline (monochrome OpenMoji font with a Montserrat fallback, so plain text is unchanged and unknown glyphs degrade gracefully). An on-device emoji picker (display.emoji, default on, can be disabled) adds a smiley button to compose from a curated set, capped to the 160-byte message budget. Incoming/outgoing text is sanitized (strips emoji variation selectors, normalizes smart quotes to ASCII). Adopted from the @jason-s13r fork; OpenMoji is CC-BY-SA 4.0.
    • \n
  • Three-step volume — the status-bar bell now cycles max → mute → mid → max; the built-in chime and custom WAV notifications scale to the level. Default is max (loudness unchanged); SOS stays fixed and loud (@jason-s13r, #11).
    • \n
\n

Changed

\n
    \n
  • sound.enabled is now a true master switch. false means fully silent — no notifications, no chime, and no SOS sound — and the status-bar bell is hidden. Set true (the default) for the 3-step volume bell.
    • \n
\n

Fixed

\n
    \n
  • A last-known position restored after reboot no longer reports \"~0s ago\" before the clock has synced — it shows \"Last known position\" until GPS/NTP re-locks, then the real age.
    • \n
  • A failed send now shows a \"Send failed - try again\" toast instead of a silently FAILED bubble (still tap-to-retry).
    • \n
  • Map tile loader hardening: oversized/corrupt PNGs and out-of-range tile coordinates are rejected and grey-filled cleanly.
    • \n
\n

Both boards (T-Deck Plus, T-Watch Ultra) build; 219 native tests pass.

\n" }, { "version": "v0.3.5", "name": "v0.3.5 — i18n cap + config-tool WiFi-wipe fixes", "datetime": "2026-06-11T10:32:26Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.3.5", "prerelease": false, "notes": "### Fixed\n- **Translations past ~128 keys reverted to English.** The i18n loader capped SD-loaded strings at 128, but the\n language files now hold ~197 keys — so on German/French/Italian every key past the cap silently fell back to\n English (e.g. `canned_5`–`8`, plus the offgrid / firmware-update / WiFi / USB / BLE / map / heard-adverts /\n toast screens). Raised the cap to 256 and added a boot-time warning if a language file ever exceeds it.\n- **Config tool wiped stored WiFi on edit.** The tool's file-import never loaded the `wifi` section, so\n importing a device's `config.json`, editing it, and re-exporting produced an empty `wifi` block — clearing\n the device's stored SSID/password on the next copy to SD. WiFi (and the persisted BLE pairing PIN) now\n round-trip correctly, including through the share-link and start-fresh paths.", "notesHtml": "

Fixed

\n
    \n
  • Translations past ~128 keys reverted to English. The i18n loader capped SD-loaded strings at 128, but the\nlanguage files now hold ~197 keys — so on German/French/Italian every key past the cap silently fell back to\nEnglish (e.g. canned_5–8, plus the offgrid / firmware-update / WiFi / USB / BLE / map / heard-adverts /\ntoast screens). Raised the cap to 256 and added a boot-time warning if a language file ever exceeds it.
    • \n
  • Config tool wiped stored WiFi on edit. The tool's file-import never loaded the wifi section, so\nimporting a device's config.json, editing it, and re-exporting produced an empty wifi block — clearing\nthe device's stored SSID/password on the next copy to SD. WiFi (and the persisted BLE pairing PIN) now\nround-trip correctly, including through the share-link and start-fresh paths.
    • \n
\n" }, { "version": "v0.3.4", "name": "v0.3.4 — Quick replies, auto-GPS refresh, companion advert + fixes", "datetime": "2026-06-11T10:03:31Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.3.4", "prerelease": false, "notes": "### Added\n- **Auto-refresh contact GPS** — keeps the map markers / convo-list badges of contacts who *don't* broadcast\n their own location fresh, by quietly re-requesting telemetry GPS before the cached fix goes stale. Throttled\n (one request per scan, respects the EU duty cycle, yields to manual requests) and self-limiting (stops asking\n a contact that doesn't answer). New setting `messaging.auto_telemetry`, **default on**, can be disabled.\n- **Per-conversation quick replies** — any contact, channel, or room can carry its own `canned` list (max 8)\n that overrides the global quick-reply list *for that chat only*; leave it empty to fall back to the global\n list. Editable per card in the config tool. Turns a conversation into a command menu — e.g. a Home Assistant\n / automation bridge (\"Open gate\", \"Lights on\", \"Status?\").\n- **Last-known location persists across reboots** — the most recent GPS fix is saved to SD\n (`/mclite/last_location.json`, throttled) and restored on boot, so the map opens to your last position\n without waiting for a fresh fix ([@jason-s13r](https://github.com/jason-s13r), #10).\n- **Advertise from the companion app** — the MeshCore phone/desktop app's **Advertise** button now works while\n connected (BLE/WiFi/USB); previously it was rejected as an unsupported command. Honours the app's flood vs\n local (zero-hop) option. The on-device advert button and the automatic periodic advert are unchanged.\n\n### Changed\n- The device-info / admin screen is now fully localized — every row label routes through the translation\n table (de/fr/it) ([@jason-s13r](https://github.com/jason-s13r), #9).\n- Conversation history now loads only the most recent `max_history_per_chat` messages per chat at boot\n (previously the whole file was loaded into RAM). Bounds memory if a history file is larger than the cap —\n e.g. after lowering the setting. No visible change; the runtime cap was already in place.\n\n### Fixed\n- Telemetry retry is no longer cancelled by the contact-info pop-up's own timeout when the mesh's outbound\n queue is busy (the two timers now stay in lockstep) — the retry fires under congestion as intended.\n- Closing the contact-info pop-up now cancels its in-flight telemetry retry, so no stray flood request goes\n out for a pop-up you already closed.\n- Muting a chat is now absolute: it silences notifications even for a contact flagged `always_sound`\n (`always_sound` still overrides *global* mute, unchanged).\n- Messages that exceed the 160-**byte** limit (e.g. emoji or accented/non-Latin text — which can be ≤160\n *characters* but more bytes) are now refused with a \"Message too long\" toast that keeps your text, instead\n of silently failing to send while still drawing a (failed) bubble.\n- A timed-out telemetry request now releases the radio's single telemetry slot when the exchange ends\n (previously the slot stayed held after a no-response request). Without this, **auto-refresh contact GPS**\n would stall for the rest of the session after the first contact that didn't answer, and slow/multi-hop\n contacts could be backed off too eagerly; both are resolved.\n- Auto-refresh no longer lets a single un-sendable contact block the rest of the round-robin, and\n `max_history_per_chat: 0` now consistently means \"unlimited\" on both load and prune (previously prune at 0\n would wipe the conversation).", "notesHtml": "

Added

\n
    \n
  • Auto-refresh contact GPS — keeps the map markers / convo-list badges of contacts who don't broadcast\ntheir own location fresh, by quietly re-requesting telemetry GPS before the cached fix goes stale. Throttled\n(one request per scan, respects the EU duty cycle, yields to manual requests) and self-limiting (stops asking\na contact that doesn't answer). New setting messaging.auto_telemetry, default on, can be disabled.
    • \n
  • Per-conversation quick replies — any contact, channel, or room can carry its own canned list (max 8)\nthat overrides the global quick-reply list for that chat only; leave it empty to fall back to the global\nlist. Editable per card in the config tool. Turns a conversation into a command menu — e.g. a Home Assistant\n/ automation bridge (\"Open gate\", \"Lights on\", \"Status?\").
    • \n
  • Last-known location persists across reboots — the most recent GPS fix is saved to SD\n(/mclite/last_location.json, throttled) and restored on boot, so the map opens to your last position\nwithout waiting for a fresh fix (@jason-s13r, #10).
    • \n
  • Advertise from the companion app — the MeshCore phone/desktop app's Advertise button now works while\nconnected (BLE/WiFi/USB); previously it was rejected as an unsupported command. Honours the app's flood vs\nlocal (zero-hop) option. The on-device advert button and the automatic periodic advert are unchanged.
    • \n
\n

Changed

\n
    \n
  • The device-info / admin screen is now fully localized — every row label routes through the translation\ntable (de/fr/it) (@jason-s13r, #9).
    • \n
  • Conversation history now loads only the most recent max_history_per_chat messages per chat at boot\n(previously the whole file was loaded into RAM). Bounds memory if a history file is larger than the cap —\ne.g. after lowering the setting. No visible change; the runtime cap was already in place.
    • \n
\n

Fixed

\n
    \n
  • Telemetry retry is no longer cancelled by the contact-info pop-up's own timeout when the mesh's outbound\nqueue is busy (the two timers now stay in lockstep) — the retry fires under congestion as intended.
    • \n
  • Closing the contact-info pop-up now cancels its in-flight telemetry retry, so no stray flood request goes\nout for a pop-up you already closed.
    • \n
  • Muting a chat is now absolute: it silences notifications even for a contact flagged always_sound\n(always_sound still overrides global mute, unchanged).
    • \n
  • Messages that exceed the 160-byte limit (e.g. emoji or accented/non-Latin text — which can be ≤160\ncharacters but more bytes) are now refused with a \"Message too long\" toast that keeps your text, instead\nof silently failing to send while still drawing a (failed) bubble.
    • \n
  • A timed-out telemetry request now releases the radio's single telemetry slot when the exchange ends\n(previously the slot stayed held after a no-response request). Without this, auto-refresh contact GPS\nwould stall for the rest of the session after the first contact that didn't answer, and slow/multi-hop\ncontacts could be backed off too eagerly; both are resolved.
    • \n
  • Auto-refresh no longer lets a single un-sendable contact block the rest of the round-robin, and\nmax_history_per_chat: 0 now consistently means \"unlimited\" on both load and prune (previously prune at 0\nwould wipe the conversation).
    • \n
\n" }, { "version": "v0.3.3", "name": "v0.3.3 — Unified contact location + reliability batch", "datetime": "2026-06-10T16:51:48Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.3.3", "prerelease": false, "notes": "Contact-location and delivery-reliability improvements, plus a batch of community contributions from [@jason-s13r](https://github.com/jason-s13r).\n\n## Added\n- **Unified contact location** — one source of truth for where a contact is: fresh telemetry (accurate) → their advert GPS → a heard advert. The conversation-list **GPS badge** now shows for *any* known position (not just telemetry); the **contact info pop-up** shows that position even without a telemetry reply (advert-sourced coordinates are marked approximate with `~`), offers the **Map** button whenever any position is known, and on a request timeout shows the known position instead of a bare \"No response\". Telemetry stays primary; the 30-minute freshness window is unchanged.\n- **Flood-routing retries** for better delivery when a direct path degrades — on **DM** retries and on **telemetry-request** retries (with a \"Retrying…\" state).\n- **Per-chat mute** — opt-in (`messaging.allow_mute`, default off). Long-press a conversation to mute; muted chats don't beep or wake the screen (SOS always does), with an indicator in the list and chat header.\n- **Vendor row** on the device-info screen showing the firmware's source repo (`owner/repo`) — handy with fork flashing.\n\n## Fixed\n- Chat scroll-to-bottom is more robust on an empty chat area / on open.\n\n## Thanks\n- @jason-s13r for PRs #3–#7.\n\nInstall/update via the [web flasher](https://laserir.github.io/MCLite/tools/web-flasher/), or on-device (SD card / WiFi). Binaries: `mclite-v0.3.3.bin` (T-Deck Plus), `mclite-watch-v0.3.3.bin` (T-Watch Ultra).\n\n**Full Changelog**: https://github.com/laserir/MCLite/compare/v0.3.2...v0.3.3", "notesHtml": "

Contact-location and delivery-reliability improvements, plus a batch of community contributions from @jason-s13r.

\n

Added

\n
    \n
  • Unified contact location — one source of truth for where a contact is: fresh telemetry (accurate) → their advert GPS → a heard advert. The conversation-list GPS badge now shows for any known position (not just telemetry); the contact info pop-up shows that position even without a telemetry reply (advert-sourced coordinates are marked approximate with ~), offers the Map button whenever any position is known, and on a request timeout shows the known position instead of a bare \"No response\". Telemetry stays primary; the 30-minute freshness window is unchanged.
    • \n
  • Flood-routing retries for better delivery when a direct path degrades — on DM retries and on telemetry-request retries (with a \"Retrying…\" state).
    • \n
  • Per-chat mute — opt-in (messaging.allow_mute, default off). Long-press a conversation to mute; muted chats don't beep or wake the screen (SOS always does), with an indicator in the list and chat header.
    • \n
  • Vendor row on the device-info screen showing the firmware's source repo (owner/repo) — handy with fork flashing.
    • \n
\n

Fixed

\n
    \n
  • Chat scroll-to-bottom is more robust on an empty chat area / on open.
    • \n
\n

Thanks

\n
    \n
  • @jason-s13r for PRs #3–#7.
    • \n
\n

Install/update via the web flasher, or on-device (SD card / WiFi). Binaries: mclite-v0.3.3.bin (T-Deck Plus), mclite-watch-v0.3.3.bin (T-Watch Ultra).

\n

Full Changelog: https://github.com/laserir/MCLite/compare/v0.3.2...v0.3.3

\n" }, { "version": "v0.3.2", "name": "v0.3.2 — Unified map + review fixes", "datetime": "2026-06-09T11:03:17Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.3.2", "prerelease": false, "notes": "Map unification plus fixes from a careful review of 0.3.0/0.3.1.\n\n## Changed\n- The contact **Map** button and the status-bar **GPS icon** now open the *same* map (one screen, one set of controls). Opening from a contact just centers on that contact and pre-selects it — drawn slightly larger with a highlight ring and its name in the bottom bar — while still showing every other contact / telemetry / heard-node location and your own position (a distinct green/amber dot).\n- **Reload** rebuilds all markers and re-checks your own position; **Center** always jumps to your own location once a fix is available (even when opened from a contact), falling back to the location the map opened on when there's no fix.\n\n## Fixed\n- Center now uses your own location on a contact-opened map (previously it only ever recentered on the contact).\n- The status-bar GPS icon stays visible (dimmed) and tappable when GPS is disabled, so the map remains reachable.\n- @mention no longer truncates a near-full message draft.\n- Companion: the contacts `since` field is read safely (removed an unaligned read).\n\nInstall/update via the [web flasher](https://laserir.github.io/MCLite/tools/web-flasher/), or on-device (SD card / WiFi). Binaries: `mclite-v0.3.2.bin` (T-Deck Plus), `mclite-watch-v0.3.2.bin` (T-Watch Ultra).\n\n**Full Changelog**: https://github.com/laserir/MCLite/compare/v0.3.1...v0.3.2", "notesHtml": "

Map unification plus fixes from a careful review of 0.3.0/0.3.1.

\n

Changed

\n
    \n
  • The contact Map button and the status-bar GPS icon now open the same map (one screen, one set of controls). Opening from a contact just centers on that contact and pre-selects it — drawn slightly larger with a highlight ring and its name in the bottom bar — while still showing every other contact / telemetry / heard-node location and your own position (a distinct green/amber dot).
    • \n
  • Reload rebuilds all markers and re-checks your own position; Center always jumps to your own location once a fix is available (even when opened from a contact), falling back to the location the map opened on when there's no fix.
    • \n
\n

Fixed

\n
    \n
  • Center now uses your own location on a contact-opened map (previously it only ever recentered on the contact).
    • \n
  • The status-bar GPS icon stays visible (dimmed) and tappable when GPS is disabled, so the map remains reachable.
    • \n
  • @mention no longer truncates a near-full message draft.
    • \n
  • Companion: the contacts since field is read safely (removed an unaligned read).
    • \n
\n

Install/update via the web flasher, or on-device (SD card / WiFi). Binaries: mclite-v0.3.2.bin (T-Deck Plus), mclite-watch-v0.3.2.bin (T-Watch Ultra).

\n

Full Changelog: https://github.com/laserir/MCLite/compare/v0.3.1...v0.3.2

\n" }, { "version": "v0.3.1", "name": "v0.3.1 — GPS in adverts + map", "datetime": "2026-06-09T09:01:00Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.3.1", "prerelease": false, "notes": "Fork-adoption batch (features adopted from the jason-s13r/MCLite fork) plus map polish.\n\n## Added\n- **GPS location in adverts** (opt-in, `gps.location_advert`, default off) — broadcast your position so contacts see you on their map. Uses MeshCore's native advert location; sends a live fix or a still-valid last-known one. Unencrypted broadcast — hence opt-in. Read-only status on the admin GPS screen; toggled via the config tool / SD.\n- **General map** — tap the status-bar GPS icon for a map of your own location plus every heard node / contact that carries GPS (same chat / repeater / room / sensor symbols as the heard-adverts list). Tap a marker for its name; **Reload** button re-scans heard nodes.\n- **NTP time sync** — set the clock from an NTP server over WiFi when GPS hasn't locked (GPS still overrides once it does).\n- **@mention** — tap a sender's name in a channel/room to insert `@name `.\n- **Fork-aware OTA** — build-time overridable update repo so forks can self-update.\n- **Web flasher repo/fork picker** — choose which repo's published releases to flash.\n\n## Changed\n- Map markers render as filled colored dots (type color + contrasting symbol) so they read against any tile; selection ring sits just outside the dot.\n\n## Fixed\n- Map markers are reliably tappable (tap-slop dead-zone; wider hit tolerance).\n- Map markers no longer blink out near the viewport edge across zoom levels.\n\nInstall/update via the [web flasher](https://laserir.github.io/MCLite/tools/web-flasher/), or on-device (SD card / WiFi). Binaries: `mclite-v0.3.1.bin` (T-Deck Plus), `mclite-watch-v0.3.1.bin` (T-Watch Ultra).\n\n**Full Changelog**: https://github.com/laserir/MCLite/compare/v0.3.0...v0.3.1", "notesHtml": "

Fork-adoption batch (features adopted from the jason-s13r/MCLite fork) plus map polish.

\n

Added

\n
    \n
  • GPS location in adverts (opt-in, gps.location_advert, default off) — broadcast your position so contacts see you on their map. Uses MeshCore's native advert location; sends a live fix or a still-valid last-known one. Unencrypted broadcast — hence opt-in. Read-only status on the admin GPS screen; toggled via the config tool / SD.
    • \n
  • General map — tap the status-bar GPS icon for a map of your own location plus every heard node / contact that carries GPS (same chat / repeater / room / sensor symbols as the heard-adverts list). Tap a marker for its name; Reload button re-scans heard nodes.
    • \n
  • NTP time sync — set the clock from an NTP server over WiFi when GPS hasn't locked (GPS still overrides once it does).
    • \n
  • @mention — tap a sender's name in a channel/room to insert @name .
    • \n
  • Fork-aware OTA — build-time overridable update repo so forks can self-update.
    • \n
  • Web flasher repo/fork picker — choose which repo's published releases to flash.
    • \n
\n

Changed

\n
    \n
  • Map markers render as filled colored dots (type color + contrasting symbol) so they read against any tile; selection ring sits just outside the dot.
    • \n
\n

Fixed

\n
    \n
  • Map markers are reliably tappable (tap-slop dead-zone; wider hit tolerance).
    • \n
  • Map markers no longer blink out near the viewport edge across zoom levels.
    • \n
\n

Install/update via the web flasher, or on-device (SD card / WiFi). Binaries: mclite-v0.3.1.bin (T-Deck Plus), mclite-watch-v0.3.1.bin (T-Watch Ultra).

\n

Full Changelog: https://github.com/laserir/MCLite/compare/v0.3.0...v0.3.1

\n" }, { "version": "v0.3.0", "name": "v0.3.0 — Companion mode (WiFi / USB / BLE)", "datetime": "2026-06-08T12:18:56Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.3.0", "prerelease": false, "notes": "## Highlights\n\n**Companion mode** — bridge the radio to a phone, desktop, or CLI using the standard MeshCore companion protocol, in parallel with normal on-device use (messages appear in both):\n- **Bluetooth** — pairs with the official MeshCore iOS/Android apps (6-digit passkey + bonding).\n- **WiFi** — reach it from `meshcore-cli`/`meshcore.js`/`meshcore_py` on your LAN.\n- **USB** — wired serial companion.\n\nOne transport at a time; messaging is read-only for config. WiFi and Bluetooth can't run together (shared radio/RAM) — the device handles the switch and offers a reboot when needed.\n\nAlso includes the on-device firmware-update fixes and a refreshed README (Quick Start + balanced companion docs).\n\nInstall/update via the [web flasher](https://laserir.github.io/MCLite/tools/web-flasher/), or on-device (SD card / WiFi). Binaries: `mclite-v0.3.0.bin` (T-Deck Plus), `mclite-watch-v0.3.0.bin` (T-Watch Ultra).\n\n**Full Changelog**: https://github.com/laserir/MCLite/compare/v0.2.2...v0.3.0", "notesHtml": "

Highlights

\n

Companion mode — bridge the radio to a phone, desktop, or CLI using the standard MeshCore companion protocol, in parallel with normal on-device use (messages appear in both):

\n
    \n
  • Bluetooth — pairs with the official MeshCore iOS/Android apps (6-digit passkey + bonding).
    • \n
  • WiFi — reach it from meshcore-cli/meshcore.js/meshcore_py on your LAN.
    • \n
  • USB — wired serial companion.
    • \n
\n

One transport at a time; messaging is read-only for config. WiFi and Bluetooth can't run together (shared radio/RAM) — the device handles the switch and offers a reboot when needed.

\n

Also includes the on-device firmware-update fixes and a refreshed README (Quick Start + balanced companion docs).

\n

Install/update via the web flasher, or on-device (SD card / WiFi). Binaries: mclite-v0.3.0.bin (T-Deck Plus), mclite-watch-v0.3.0.bin (T-Watch Ultra).

\n

Full Changelog: https://github.com/laserir/MCLite/compare/v0.2.2...v0.3.0

\n" }, { "version": "v0.2.2", "name": "v0.2.2 — Fix WiFi OTA crash", "datetime": "2026-06-07T15:20:45Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.2.2", "prerelease": false, "notes": "Fixes a stack overflow that crashed the device when installing a firmware update over WiFi (the TLS handshake + on-stack buffer exceeded the loop-task stack). WiFi over-the-air updates now work end-to-end. SD-card install and USB flashing were unaffected.\n\nNote: devices on 0.2.1 should update via SD card or USB (the 0.2.1 WiFi installer has the crash); 0.2.2 onward updates over WiFi cleanly.", "notesHtml": "

Fixes a stack overflow that crashed the device when installing a firmware update over WiFi (the TLS handshake + on-stack buffer exceeded the loop-task stack). WiFi over-the-air updates now work end-to-end. SD-card install and USB flashing were unaffected.

\n

Note: devices on 0.2.1 should update via SD card or USB (the 0.2.1 WiFi installer has the crash); 0.2.2 onward updates over WiFi cleanly.

\n" }, { "version": "v0.2.0", "name": "v0.2.0 — T-Watch Ultra support", "datetime": "2026-06-01T14:43:59Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.2.0", "prerelease": false, "notes": "**Full Changelog**: https://github.com/laserir/MCLite/compare/v0.1.8...v0.2.0", "notesHtml": "

Full Changelog: https://github.com/laserir/MCLite/compare/v0.1.8...v0.2.0

\n" }, { "version": "v0.1.8", "name": "v0.1.8 — Heard Adverts", "datetime": "2026-05-05T12:01:26Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.1.8", "prerelease": false, "notes": "## Highlights\n\n**Heard Adverts** — every advert MeshCore decodes goes into a 64-entry LRU buffer (RAM, evaporates on reboot). New screen reachable from the admin menu lists them with type icons, last-heard age, alias-when-known, and a queued badge for entries you've saved this session. Detail modal shows fingerprint-style pubkey + per-hop path direction.\n\n- **Live updates** while the screen is visible: 1 Hz rate-limited rebuild, focus preserved by pubkey, skipped while a modal is open.\n- **Save discovered chat contacts** — Save button on the detail modal appends a `from_discovery: true` entry to `config.json` with conservative defaults (all permissions off, no SOS in/out). Activates on next boot via the existing ContactStore + MCLiteMesh registration path. CHAT-only — repeaters/rooms/sensors stay infrastructure. After save: `[Reboot now, OK]` confirmation.\n- **Manual advert** button in the header — sends a local advert immediately and re-anchors the periodic 9-min schedule. Toast confirms.\n- **Clear button** wipes the in-memory buffer.\n\n## Config persistence hardening\n\n- `ConfigManager::save()` now uses **atomic writes**: stage to `.tmp`, retain previous file as `.bak` during the rename, drop `.bak` on successful completion. Steady state is just `config.json`.\n- **Boot fallback** to `config.json.bak` if the live file is missing or corrupt (mid-save power loss). Successful recovery promotes the loaded content back to main and removes `.bak`.\n- Required because `config.json` holds the device identity keys — a torn truncate-write would brick the unit.\n\n## Other changes\n\n- **Boot screen** — MCLite mark glyph above the title, drawn programmatically (no raster asset).\n- **Default `dim_brightness` 20 → 0** — auto-dim now goes fully dark, prevents long-term burn-in on the always-on status bar.\n- **Long-standing log fix**: `[MCLiteMesh] Discovered contact` was printing the raw packed `path_len` byte (low 6 bits = hops, upper 2 = hash size). Values like `70` actually meant 6 hops with 2-byte hashes. Now masked correctly.\n- **Config tool**: amber 'Added via device — review me' badge on `from_discovery` contacts, with an inline ✕ to mark reviewed. Round-trip preserves the flag on both load paths and the export builder.\n- **i18n**: 19 new keys covering type names, field labels, hops format, save/reboot/queue/error states, advert-sent toast — across en/de/fr/it and the embedded LANG_FILES.\n\n## Tests\n\n- 185 native test cases (was 172). New coverage in `test_heard_advert_cache` (14) and `test_config` (atomic writes, `.bak` fallback, recovery cleanup, `from_discovery` round-trip, append-discovered-contact success/duplicate/cap).\n\n## Compatibility\n\n- Backward-compatible config: missing `from_discovery` parses as `false`. Old firmware ignores the field.\n- ConfigManager now writes through the atomic path even for the existing offgrid-toggle save — no caller change needed.\n- To force first-boot regen, delete **both** `config.json` and `config.json.bak`.\n\n## Install\n\n- **Web flasher:** [laserir.github.io/MCLite/tools/web-flasher](https://laserir.github.io/MCLite/tools/web-flasher/) — pick v0.1.8\n- **Manual:** \\`esptool.py write_flash 0x0 mclite-v0.1.8.bin\\`\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)", "notesHtml": "

Highlights

\n

Heard Adverts — every advert MeshCore decodes goes into a 64-entry LRU buffer (RAM, evaporates on reboot). New screen reachable from the admin menu lists them with type icons, last-heard age, alias-when-known, and a queued badge for entries you've saved this session. Detail modal shows fingerprint-style pubkey + per-hop path direction.

\n
    \n
  • Live updates while the screen is visible: 1 Hz rate-limited rebuild, focus preserved by pubkey, skipped while a modal is open.
    • \n
  • Save discovered chat contacts — Save button on the detail modal appends a from_discovery: true entry to config.json with conservative defaults (all permissions off, no SOS in/out). Activates on next boot via the existing ContactStore + MCLiteMesh registration path. CHAT-only — repeaters/rooms/sensors stay infrastructure. After save: [Reboot now, OK] confirmation.
    • \n
  • Manual advert button in the header — sends a local advert immediately and re-anchors the periodic 9-min schedule. Toast confirms.
    • \n
  • Clear button wipes the in-memory buffer.
    • \n
\n

Config persistence hardening

\n
    \n
  • ConfigManager::save() now uses atomic writes: stage to .tmp, retain previous file as .bak during the rename, drop .bak on successful completion. Steady state is just config.json.
    • \n
  • Boot fallback to config.json.bak if the live file is missing or corrupt (mid-save power loss). Successful recovery promotes the loaded content back to main and removes .bak.
    • \n
  • Required because config.json holds the device identity keys — a torn truncate-write would brick the unit.
    • \n
\n

Other changes

\n
    \n
  • Boot screen — MCLite mark glyph above the title, drawn programmatically (no raster asset).
    • \n
  • Default dim_brightness 20 → 0 — auto-dim now goes fully dark, prevents long-term burn-in on the always-on status bar.
    • \n
  • Long-standing log fix: [MCLiteMesh] Discovered contact was printing the raw packed path_len byte (low 6 bits = hops, upper 2 = hash size). Values like 70 actually meant 6 hops with 2-byte hashes. Now masked correctly.
    • \n
  • Config tool: amber 'Added via device — review me' badge on from_discovery contacts, with an inline ✕ to mark reviewed. Round-trip preserves the flag on both load paths and the export builder.
    • \n
  • i18n: 19 new keys covering type names, field labels, hops format, save/reboot/queue/error states, advert-sent toast — across en/de/fr/it and the embedded LANG_FILES.
    • \n
\n

Tests

\n
    \n
  • 185 native test cases (was 172). New coverage in test_heard_advert_cache (14) and test_config (atomic writes, .bak fallback, recovery cleanup, from_discovery round-trip, append-discovered-contact success/duplicate/cap).
    • \n
\n

Compatibility

\n
    \n
  • Backward-compatible config: missing from_discovery parses as false. Old firmware ignores the field.
    • \n
  • ConfigManager now writes through the atomic path even for the existing offgrid-toggle save — no caller change needed.
    • \n
  • To force first-boot regen, delete both config.json and config.json.bak.
    • \n
\n

Install

\n\n

🤖 Generated with Claude Code

\n" }, { "version": "v0.1.7", "name": "v0.1.7 — Room Server Client", "datetime": "2026-04-29T10:39:57Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.1.7", "prerelease": false, "notes": "## Highlights\n\n**Room server client** — join community message boards run by MeshCore room servers. Posts appear in the conversation list with an `R` icon (purple), ordered alongside DMs and channels by last activity. Up to 8 rooms.\n\n- **Auto-login on boot** with exponential backoff (1 → 2 → 4 → cap 30 min).\n- **Disconnect recovery** — re-login on chat-open (rate-limited 30s) and after 10 minutes of silence while a room chat is foreground. Both wake the server's 3-strike push-freeze that trips after ~36s of radio dropout, so passive readers don't miss posts after brief out-of-range moments.\n- **Per-room flags** mirroring channels: `read_only`, `allow_sos` (default true), `send_sos` (default false), `scope` override.\n- **Sender resolution** — 4-byte `sender_prefix` looked up against ContactStore: alias if known, else 8-hex-char fallback.\n- **`sync_since` persisted** per-room across reboots; only newer posts replay on next login.\n- **AdminScreen Rooms section** under Channels: name, online/offline indicator, last-sync timestamp.\n- **Config tool** Rooms card with all four toggles and the new `info-icon` collapsible-hint pattern.\n\n## Other changes\n\n- `MAX_CONTACTS=32 → 40` (32 chat + 8 room) with cap warnings on overflow.\n- `MAX_CONVERSATIONS=48 → 56`.\n- Translations: `sec_rooms` added in de/fr/it.\n- `data[5]` keep-alive byte runtime watch — warns if a future MeshCore server re-enables the legacy interval.\n\n## Compatibility\n\n- Backward-compatible config: missing `room_servers` block parses as empty list. Old firmware ignores the field.\n- DM and channel history files stay byte-identical (no `syncSince` written when zero).\n- Telemetry, SOS, key/PIN lock, offgrid mode all unaffected.\n\n## Install\n\n- **Web flasher:** [laserir.github.io/MCLite/tools/web-flasher](https://laserir.github.io/MCLite/tools/web-flasher/) — pick v0.1.7\n- **Manual:** `esptool.py write_flash 0x0 mclite-v0.1.7.bin`\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)", "notesHtml": "

Highlights

\n

Room server client — join community message boards run by MeshCore room servers. Posts appear in the conversation list with an R icon (purple), ordered alongside DMs and channels by last activity. Up to 8 rooms.

\n
    \n
  • Auto-login on boot with exponential backoff (1 → 2 → 4 → cap 30 min).
    • \n
  • Disconnect recovery — re-login on chat-open (rate-limited 30s) and after 10 minutes of silence while a room chat is foreground. Both wake the server's 3-strike push-freeze that trips after ~36s of radio dropout, so passive readers don't miss posts after brief out-of-range moments.
    • \n
  • Per-room flags mirroring channels: read_only, allow_sos (default true), send_sos (default false), scope override.
    • \n
  • Sender resolution — 4-byte sender_prefix looked up against ContactStore: alias if known, else 8-hex-char fallback.
    • \n
  • sync_since persisted per-room across reboots; only newer posts replay on next login.
    • \n
  • AdminScreen Rooms section under Channels: name, online/offline indicator, last-sync timestamp.
    • \n
  • Config tool Rooms card with all four toggles and the new info-icon collapsible-hint pattern.
    • \n
\n

Other changes

\n
    \n
  • MAX_CONTACTS=32 → 40 (32 chat + 8 room) with cap warnings on overflow.
    • \n
  • MAX_CONVERSATIONS=48 → 56.
    • \n
  • Translations: sec_rooms added in de/fr/it.
    • \n
  • data[5] keep-alive byte runtime watch — warns if a future MeshCore server re-enables the legacy interval.
    • \n
\n

Compatibility

\n
    \n
  • Backward-compatible config: missing room_servers block parses as empty list. Old firmware ignores the field.
    • \n
  • DM and channel history files stay byte-identical (no syncSince written when zero).
    • \n
  • Telemetry, SOS, key/PIN lock, offgrid mode all unaffected.
    • \n
\n

Install

\n\n

🤖 Generated with Claude Code

\n" }, { "version": "v0.1.5", "name": "v0.1.5", "datetime": "2026-04-21T09:31:28Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.1.5", "prerelease": false, "notes": "## Highlights\n\n- **MeshCore upgraded to v1.15.0** (`companion-v1.15.0`) — catches up with upstream bug fixes, new token-bucket duty-cycle dispatcher, and default-scope aligned wire format. Binary-compatible with all MCLite v0.1.x peers.\n- **SOS burst hardened** — 50ms inter-send pacing and dispatcher yield between each recipient so the packet pool can drain. Fixes intermittent cases where SOS delivered to only some contacts/channels in meshes with many targets.\n- **SOS received → key lock auto-disengages** — when an incoming SOS alert appears, the device automatically unlocks its keys so the user can respond immediately. **PIN lock stays engaged** — no security compromise.\n- **Configurable path hash mode** — new `radio.path_hash_mode` setting (0/1/2 → 1/2/3 bytes per repeater fingerprint in the packet path). Larger sizes reduce path collisions in dense meshes at the cost of a few extra bytes per hop. Defaults to 0 for wire-identical compatibility with pre-v1.15 peers.\n- **Admin screen shows active path hash size** plus per-channel scope overrides rendered as `[scope:#name]`, distinct from the `[SOS]` / `[read-only]` capability flags.\n\n## Changes since v0.1.4\n\n- `08ca1f7` Bump MeshCore to v1.15.0, harden SOS burst delivery\n- `a90ad6e` Add configurable path hash mode and admin screen scope display\n- `0f53de1` Bump version to 0.1.5\n- `aba8ceb` Publish firmware v0.1.5 to web flasher\n- `debad94` Document scope and path_hash_mode in example config\n\n## Install\n\nFlash `mclite-v0.1.5.bin` via the [web flasher](https://laserir.github.io/MCLite/tools/web-flasher/) or manually with esptool. Use `mclite_config_tool.html` (offline, single file) to edit `config.json`.", "notesHtml": "

Highlights

\n
    \n
  • MeshCore upgraded to v1.15.0 (companion-v1.15.0) — catches up with upstream bug fixes, new token-bucket duty-cycle dispatcher, and default-scope aligned wire format. Binary-compatible with all MCLite v0.1.x peers.
    • \n
  • SOS burst hardened — 50ms inter-send pacing and dispatcher yield between each recipient so the packet pool can drain. Fixes intermittent cases where SOS delivered to only some contacts/channels in meshes with many targets.
    • \n
  • SOS received → key lock auto-disengages — when an incoming SOS alert appears, the device automatically unlocks its keys so the user can respond immediately. PIN lock stays engaged — no security compromise.
    • \n
  • Configurable path hash mode — new radio.path_hash_mode setting (0/1/2 → 1/2/3 bytes per repeater fingerprint in the packet path). Larger sizes reduce path collisions in dense meshes at the cost of a few extra bytes per hop. Defaults to 0 for wire-identical compatibility with pre-v1.15 peers.
    • \n
  • Admin screen shows active path hash size plus per-channel scope overrides rendered as [scope:#name], distinct from the [SOS] / [read-only] capability flags.
    • \n
\n

Changes since v0.1.4

\n
    \n
  • 08ca1f7 Bump MeshCore to v1.15.0, harden SOS burst delivery
    • \n
  • a90ad6e Add configurable path hash mode and admin screen scope display
    • \n
  • 0f53de1 Bump version to 0.1.5
    • \n
  • aba8ceb Publish firmware v0.1.5 to web flasher
    • \n
  • debad94 Document scope and path_hash_mode in example config
    • \n
\n

Install

\n

Flash mclite-v0.1.5.bin via the web flasher or manually with esptool. Use mclite_config_tool.html (offline, single file) to edit config.json.

\n" }, { "version": "v0.1.4", "name": "v0.1.4", "datetime": "2026-04-20T18:19:03Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.1.4", "prerelease": false, "notes": "## Highlights\n\n- **Map view on telemetry modal** — tap a contact's name in the chat header → telemetry modal → **Map** button (visible when the contact has fresh GPS and SD tiles are available). Full-screen slippy-tile map centred on the contact, own-device marker, `+`/`-` zoom, scale bar. Tile pack layout `/tiles/{z}/{x}/{y}.png` is compatible with upstream MeshCore T-Deck firmware — existing tile packs work unchanged. See the updated README for how to prepare a `/tiles` folder with [map-tiles-downloader](https://github.com/tekk/map-tiles-downloader).\n- **Screen lock & auto-lock unified** — single `lock` / `auto_lock` config with deferred click; backwards-compatible with older configs missing `auto_key_lock`.\n- **Region scope transport codes** — optional per-radio / per-channel scope for repeater filtering.\n- **MeshCore dependency pinned** to commit `792f2999` for reproducible builds.\n\n## Changes since v0.1.3\n\n- `444065d` Add map view on telemetry modal\n- `89c3825` Add Map view to features list, drop OSM attribution note\n- `b4598bb` Correct map-tiles-downloader description (TUI, not browser) and document GeoNames region codes\n- `6f378e0` Pin MeshCore dep to commit 792f2999 for reproducible builds\n\n## Install\n\nFlash `mclite-v0.1.4.bin` via the [web flasher](https://laserir.github.io/MCLite/tools/web-flasher/) or manually with esptool. Use `mclite_config_tool.html` (offline, single file) to edit `config.json`.", "notesHtml": "

Highlights

\n
    \n
  • Map view on telemetry modal — tap a contact's name in the chat header → telemetry modal → Map button (visible when the contact has fresh GPS and SD tiles are available). Full-screen slippy-tile map centred on the contact, own-device marker, +/- zoom, scale bar. Tile pack layout /tiles/{z}/{x}/{y}.png is compatible with upstream MeshCore T-Deck firmware — existing tile packs work unchanged. See the updated README for how to prepare a /tiles folder with map-tiles-downloader.
    • \n
  • Screen lock & auto-lock unified — single lock / auto_lock config with deferred click; backwards-compatible with older configs missing auto_key_lock.
    • \n
  • Region scope transport codes — optional per-radio / per-channel scope for repeater filtering.
    • \n
  • MeshCore dependency pinned to commit 792f2999 for reproducible builds.
    • \n
\n

Changes since v0.1.3

\n
    \n
  • 444065d Add map view on telemetry modal
    • \n
  • 89c3825 Add Map view to features list, drop OSM attribution note
    • \n
  • b4598bb Correct map-tiles-downloader description (TUI, not browser) and document GeoNames region codes
    • \n
  • 6f378e0 Pin MeshCore dep to commit 792f2999 for reproducible builds
    • \n
\n

Install

\n

Flash mclite-v0.1.4.bin via the web flasher or manually with esptool. Use mclite_config_tool.html (offline, single file) to edit config.json.

\n" }, { "version": "v0.1.3", "name": "v0.1.3", "datetime": "2026-04-13T08:44:54Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.1.3", "prerelease": false, "notes": "## What's New\n\n- **Region scope** — tag outgoing packets with MeshCore transport codes so repeaters can filter by region. Set a global scope or override per channel. Compatible with 1-byte and 2-byte repeaters\n- **Automatic DST** — POSIX timezone strings for automatic daylight saving time transitions\n- **SOS fix** — SOS acknowledgement no longer triggers an SOS alert on the sender's device\n- **Telemetry fix** — CayenneLPP parsing off-by-one corrected\n- **Config tool** — region scope settings for radio and per-channel override\n\n## Install\n\nFlash via the [Web Flasher](https://laserir.github.io/MCLite/tools/web-flasher/) or download the binary below and flash with esptool:\n```\nesptool.py write_flash 0x0 mclite-v0.1.3.bin\n```", "notesHtml": "

What's New

\n
    \n
  • Region scope — tag outgoing packets with MeshCore transport codes so repeaters can filter by region. Set a global scope or override per channel. Compatible with 1-byte and 2-byte repeaters
    • \n
  • Automatic DST — POSIX timezone strings for automatic daylight saving time transitions
    • \n
  • SOS fix — SOS acknowledgement no longer triggers an SOS alert on the sender's device
    • \n
  • Telemetry fix — CayenneLPP parsing off-by-one corrected
    • \n
  • Config tool — region scope settings for radio and per-channel override
    • \n
\n

Install

\n

Flash via the Web Flasher or download the binary below and flash with esptool:

\n
esptool.py write_flash 0x0 mclite-v0.1.3.bin\n
\n" }, { "version": "v0.1.2", "name": "v0.1.2", "datetime": "2026-03-30T12:01:18Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.1.2", "prerelease": false, "notes": "## What's New\n\n- **Quick replies** — optional canned message picker in chat (OK, Copy, Where are you?, Need help, etc.). Disabled by default, enable via config tool or `\"canned_messages\": true` in config.json. Supports custom messages via JSON array.\n- **Translations** — quick reply messages translated for German, French, and Italian\n- **Config tool** — Quick Replies toggle in Messaging section; auto-detects base64 identity keys from firmware-generated configs\n\n## Install\n\nFlash via the [Web Flasher](https://laserir.github.io/MCLite/tools/web-flasher/) or download the binary below and flash with esptool:\n```\nesptool.py write_flash 0x0 mclite-v0.1.2.bin\n```", "notesHtml": "

What's New

\n
    \n
  • Quick replies — optional canned message picker in chat (OK, Copy, Where are you?, Need help, etc.). Disabled by default, enable via config tool or \"canned_messages\": true in config.json. Supports custom messages via JSON array.
    • \n
  • Translations — quick reply messages translated for German, French, and Italian
    • \n
  • Config tool — Quick Replies toggle in Messaging section; auto-detects base64 identity keys from firmware-generated configs
    • \n
\n

Install

\n

Flash via the Web Flasher or download the binary below and flash with esptool:

\n
esptool.py write_flash 0x0 mclite-v0.1.2.bin\n
\n" }, { "version": "v0.1.1", "name": "v0.1.1", "datetime": "2026-03-28T18:32:12Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.1.1", "prerelease": false, "notes": "## What's New\n\n- **Keyboard backlight support** — turns on at boot, off on auto-dim, restores on wake. Configurable via `kbd_backlight` (on/off) and `kbd_brightness` (1–255, default 127).\n- **Configurable dim brightness** — new `dim_brightness` setting (0–255, default 20). Set to 0 to turn the screen off completely when inactive.\n- **Config tool: Basic/Advanced mode** — new toggle to show only Device, Identity, Contacts, and Channels by default. Switch to Advanced for Radio, Display, Messaging, Sound, GPS, Battery, and Security settings.\n- Updated config tool, example config, admin screen, and README.\n\n## Flashing\n\nUse the [web flasher](https://laserir.github.io/MCLite/tools/web-flasher/) or download `mclite-v0.1.1.bin` below and flash with esptool:\n```\nesptool.py write_flash 0x0 mclite-v0.1.1.bin\n```", "notesHtml": "

What's New

\n
    \n
  • Keyboard backlight support — turns on at boot, off on auto-dim, restores on wake. Configurable via kbd_backlight (on/off) and kbd_brightness (1–255, default 127).
    • \n
  • Configurable dim brightness — new dim_brightness setting (0–255, default 20). Set to 0 to turn the screen off completely when inactive.
    • \n
  • Config tool: Basic/Advanced mode — new toggle to show only Device, Identity, Contacts, and Channels by default. Switch to Advanced for Radio, Display, Messaging, Sound, GPS, Battery, and Security settings.
    • \n
  • Updated config tool, example config, admin screen, and README.
    • \n
\n

Flashing

\n

Use the web flasher or download mclite-v0.1.1.bin below and flash with esptool:

\n
esptool.py write_flash 0x0 mclite-v0.1.1.bin\n
\n" }, { "version": "v0.1.0", "name": "MCLite v0.1.0", "datetime": "2026-03-27T06:34:31Z", "url": "https://github.com/laserir/MCLite/releases/tag/v0.1.0", "prerelease": false, "notes": "## MCLite v0.1.0\n\nPurpose-built MeshCore companion firmware for LilyGo T-Deck Plus.\n\n### Highlights\n- MeshCore mesh messaging (DM + channels)\n- SOS alert system with long-press trigger\n- GPS location sharing (decimal, MGRS, or both)\n- On-demand telemetry (battery, location, environment)\n- Multi-language support (EN/DE/FR/IT)\n- SD card message history with ACK persistence\n- Offline config tool (HTML)\n\n### Install\nFlash `mclite-v0.1.0.bin` via the [web flasher](https://laserir.github.io/MCLite/tools/web-flasher/) or esptool.", "notesHtml": "

MCLite v0.1.0

\n

Purpose-built MeshCore companion firmware for LilyGo T-Deck Plus.

\n

Highlights

\n
    \n
  • MeshCore mesh messaging (DM + channels)
    • \n
  • SOS alert system with long-press trigger
    • \n
  • GPS location sharing (decimal, MGRS, or both)
    • \n
  • On-demand telemetry (battery, location, environment)
    • \n
  • Multi-language support (EN/DE/FR/IT)
    • \n
  • SD card message history with ACK persistence
    • \n
  • Offline config tool (HTML)
    • \n
\n

Install

\n

Flash mclite-v0.1.0.bin via the web flasher or esptool.

\n" } ], "changelogSource": "github", "changelogUpdatedAt": "2026-06-21T09:55:30.520Z" }, { "id": "meck", "name": "Meck", "type": "fork", "maintainer": "pelgraine", "description": "A MeshCore companion firmware fork focused on enabling BLE and WiFi connectivity for the LilyGo T-Deck Pro, T-Deck Max, and T5 E-Paper S3 Pro. Features a full touch UI with on-device keyboard, games, voice notes over LoRa, web browser, SMS, and a configuration launcher with OTA updates.\n", "repository": "https://github.com/pelgraine/Meck", "license": "MIT", "status": "active", "lifecycle": "active", "maturity": "beta", "distribution": "community", "lineage": { "kind": "fork", "upstreamFirmwareId": "meshcore-official", "upstreamRepository": "https://github.com/meshcore-dev/MeshCore" }, "runtime": { "framework": "arduino", "language": "cpp" }, "roles": [ "companion", "repeater", "room-server" ], "features": [ "BLE and WiFi companion connectivity", "Touch UI with on-device keyboard", "Games (Sokoban, Pong, Snake)", "Voice notes over LoRa", "Web browser and IRC client", "SMS and phone app (4G models only)", "Per-channel notification preferences and custom tones", "Config export/import", "OTA firmware update", "Lock screen and shutdown" ], "capabilities": { "protocol": { "meshcoreCompatible": true }, "transports": { "ble": true, "usbSerial": true, "nativeTcp": true, "wifiAp": true }, "operations": { "ota": true, "webFlasher": false }, "networking": { "repeater": true, "roomServer": true, "observer": false, "kissModem": false }, "hardware": { "gps": true, "display": true, "sensors": false, "lowPowerRx": false } }, "devices": [ { "id": "lilygo-tdeck-pro", "status": "supported", "notes": "T-Deck Pro variant with ESP32-S3 and e-paper display." }, { "id": "lilygo-t5-pro", "status": "supported", "notes": "T5 E-Paper S3 Pro (H752-XX) variant." }, { "id": "heltec-v3", "status": "supported", "notes": "Remote repeater only." }, { "id": "heltec-wsl3", "status": "supported", "notes": "Remote repeater only." }, { "id": "heltec-v4", "status": "supported", "notes": "Remote repeater only." }, { "id": "heltec-v4-exp", "status": "supported", "notes": "Remote repeater only." } ], "popularity": { "githubStars": 25, "githubForks": 2, "githubWatchers": 0, "githubOpenIssues": 4, "githubContributors": 99, "releaseDownloads": 381, "latestReleaseDownloads": 32, "lastChecked": "2026-06-21" }, "verification": { "sourceAvailable": true, "releasesAvailable": true, "ciBuilds": true, "lastChecked": "2026-06-21" }, "latest_version": "1.12.2", "released": "2026-06-16", "releases": [ { "version": "v1.12.2", "name": "Meck v1.12.2 (patch): Notes & WiFi password 'q' input fix", "datetime": "2026-06-16T21:13:31Z", "url": "https://github.com/pelgraine/Meck/releases/tag/v1.12.2", "prerelease": false, "notes": "v1.12.2 is a small patch release on top of [v1.12.1](https://github.com/pelgraine/Meck/releases/tag/v1.12.1). It fixes a regression on the **T-Deck Pro** and **T-Deck Max** where pressing \"q\" (or \"Q\") during text entry was caught as a back/exit shortcut instead of being typed. This affected two screens -- the Notes editor and the WiFi password prompt -- so any note or WiFi password containing the letter \"q\" could not be entered. Both screens now accept \"q\"/\"Q\" as normal characters, with Shift+Backspace used to leave instead.\r\n\r\n## What's Changed in v1.12.2\r\n\r\n### Notes editor -- \"q\" now types instead of exiting\r\n\r\nPreviously, pressing \"q\" while editing a note could exit the editor (when the buffer was empty or unchanged) rather than inserting the letter. \"q\"/\"Q\" are now entered like any other character. Shift+Backspace continues to save and exit.\r\n\r\n### WiFi password entry -- \"q\" now types instead of jumping back\r\n\r\nIn the WiFi password screen, \"q\"/\"Q\" were intercepted and sent you back to the network list, so passwords containing those letters could not be entered. They are now accepted as password characters. Shift+Backspace returns to the network list, and the on-screen footer now reads `Enter:Connect Sh+Del:Exit`.\r\n\r\nAll other devices and features are unchanged from [v1.12.1](https://github.com/pelgraine/Meck/releases/tag/v1.12.1).\r\n\r\n## First-Time Flashing\r\n\r\nEach build comes in two forms:\r\n\r\n- **`-merged.bin`** -- bootloader, partition table, and firmware in a single image. Flash at address `0x0`. Use this for a first-time flash, when coming from other firmware, **or if a device will not boot after an update**.\r\n\r\n- **`.bin`** -- application firmware only. Use this to update an existing Meck install, including OTA updates from your phone (**Settings -> OTA Tools**).\r\n\r\nThe partition layout supports dual OTA slots, so the previous firmware remains on the inactive partition as an automatic rollback target if a new image fails to boot.\r\n\r\n## MeshCore Companion Apps\r\n\r\n**BLE variants** connect to the standard MeshCore companion apps:\r\n\r\n- Web: \r\n- Android: \r\n- iOS: \r\n\r\n**WiFi variants** connect via TCP on port 5000:\r\n\r\n- Web: \r\n- meshcore.js: \r\n- Python CLI: ", "notesHtml": "

v1.12.2 is a small patch release on top of v1.12.1. It fixes a regression on the T-Deck Pro and T-Deck Max where pressing \"q\" (or \"Q\") during text entry was caught as a back/exit shortcut instead of being typed. This affected two screens -- the Notes editor and the WiFi password prompt -- so any note or WiFi password containing the letter \"q\" could not be entered. Both screens now accept \"q\"/\"Q\" as normal characters, with Shift+Backspace used to leave instead.

\n

What's Changed in v1.12.2

\n

Notes editor -- \"q\" now types instead of exiting

\n

Previously, pressing \"q\" while editing a note could exit the editor (when the buffer was empty or unchanged) rather than inserting the letter. \"q\"/\"Q\" are now entered like any other character. Shift+Backspace continues to save and exit.

\n

WiFi password entry -- \"q\" now types instead of jumping back

\n

In the WiFi password screen, \"q\"/\"Q\" were intercepted and sent you back to the network list, so passwords containing those letters could not be entered. They are now accepted as password characters. Shift+Backspace returns to the network list, and the on-screen footer now reads Enter:Connect Sh+Del:Exit.

\n

All other devices and features are unchanged from v1.12.1.

\n

First-Time Flashing

\n

Each build comes in two forms:

\n
    \n

  • <name>-merged.bin -- bootloader, partition table, and firmware in a single image. Flash at address 0x0. Use this for a first-time flash, when coming from other firmware, or if a device will not boot after an update.

    \n
    • \n

  • <name>.bin -- application firmware only. Use this to update an existing Meck install, including OTA updates from your phone (Settings -> OTA Tools).

    \n
    • \n
\n

The partition layout supports dual OTA slots, so the previous firmware remains on the inactive partition as an automatic rollback target if a new image fails to boot.

\n

MeshCore Companion Apps

\n

BLE variants connect to the standard MeshCore companion apps:

\n\n

WiFi variants connect via TCP on port 5000:

\n\n" }, { "version": "v1.12.1", "name": "Meck v1.12.1: T-Deck Max battery capacity correction", "datetime": "2026-06-10T23:01:12Z", "url": "https://github.com/pelgraine/Meck/releases/tag/v1.12.1", "prerelease": false, "notes": "v1.12.1 is a small patch release on top of [v1.12.](https://github.com/pelgraine/Meck/releases/tag/v1.12) It corrects the configured battery capacity for the **T-Deck Max** from 1500 mAh to 1400 mAh, matching the cell actually shipped in the device. This improves the accuracy of battery percentage and runtime estimates on the Max.\r\n\r\n## What's Changed in v1.12.1\r\n\r\n### T-Deck Max battery capacity -- 1500 -> 1400 mAh\r\n\r\nThe Max's battery capacity was set to 1500 mAh; it is now 1400 mAh to reflect the real cell. No other behaviour changes.\r\n\r\nAll other devices and features are unchanged from [v1.12.](https://github.com/pelgraine/Meck/releases/tag/v1.12).\r\n\r\nDespite the LilyGO T-Deck Max readme reflecting 1500mAh, I've removed the battery from my Max (to put in a 2500mAh battery with a custom case) and can confirm my T-Deck Max battery was actually the same 1400mAh used in the T-Deck Pro.\r\n\r\n\"Screenshot\r\n\r\n\"IMG_3378\"\r\n\r\n## First-Time Flashing\r\n\r\nEach build comes in two forms:\r\n\r\n- **`-merged.bin`** -- bootloader, partition table, and firmware in a single image. Flash at address `0x0`. Use this for a first-time flash, when coming from other firmware, **or if a device will not boot after an update**.\r\n\r\n- **`.bin`** -- application firmware only. Use this to update an existing Meck install, including OTA updates from your phone (**Settings -> OTA Tools**).\r\n\r\nThe partition layout supports dual OTA slots, so the previous firmware remains on the inactive partition as an automatic rollback target if a new image fails to boot.\r\n\r\n## MeshCore Companion Apps\r\n\r\n**BLE variants** connect to the standard MeshCore companion apps:\r\n\r\n- Web: \r\n- Android: \r\n- iOS: \r\n\r\n\r\n**WiFi variants** connect via TCP on port 5000:\r\n\r\n- Web: \r\n- meshcore.js: \r\n- Python CLI: ", "notesHtml": "

v1.12.1 is a small patch release on top of v1.12. It corrects the configured battery capacity for the T-Deck Max from 1500 mAh to 1400 mAh, matching the cell actually shipped in the device. This improves the accuracy of battery percentage and runtime estimates on the Max.

\n

What's Changed in v1.12.1

\n

T-Deck Max battery capacity -- 1500 -> 1400 mAh

\n

The Max's battery capacity was set to 1500 mAh; it is now 1400 mAh to reflect the real cell. No other behaviour changes.

\n

All other devices and features are unchanged from v1.12..

\n

Despite the LilyGO T-Deck Max readme reflecting 1500mAh, I've removed the battery from my Max (to put in a 2500mAh battery with a custom case) and can confirm my T-Deck Max battery was actually the same 1400mAh used in the T-Deck Pro.

\n\"Screenshot\"IMG_3378\"

First-Time Flashing

\n

Each build comes in two forms:

\n
    \n

  • <name>-merged.bin -- bootloader, partition table, and firmware in a single image. Flash at address 0x0. Use this for a first-time flash, when coming from other firmware, or if a device will not boot after an update.

    \n
    • \n

  • <name>.bin -- application firmware only. Use this to update an existing Meck install, including OTA updates from your phone (Settings -> OTA Tools).

    \n
    • \n
\n

The partition layout supports dual OTA slots, so the previous firmware remains on the inactive partition as an automatic rollback target if a new image fails to boot.

\n

MeshCore Companion Apps

\n

BLE variants connect to the standard MeshCore companion apps:

\n\n

WiFi variants connect via TCP on port 5000:

\n\n" }, { "version": "v1.12", "name": "Meck v1.12: RX log, RX packet counter, plus T-Deck Max power fixes", "datetime": "2026-06-06T21:30:49Z", "url": "https://github.com/pelgraine/Meck/releases/tag/v1.12", "prerelease": false, "notes": "v1.12 is a polish-and-power release across all three companion devices. The headline addition is an on-device **Rx Log** packet sniffer -- a live view of every packet your radio hears -- available on every build. Alongside it: an unread badge for the SMS inbox, a batch of **T-Deck Max** power, wake, and GPS fixes, and a set of channel and repeater refinements. \r\n\r\n## What's New in v1.12\r\n\r\n### Rx Log packet sniffer -- all devices\r\n\r\nA new on-device packet sniffer, mirroring the Rx Log in the MeshCore companion app. Open it from **Settings -> Rx Log >>**. It captures every packet the radio receives -- including relays destined for other nodes, since capture happens before filtering -- into a buffer of the most recent 100 packets, newest first. Each entry shows the route type (flood/direct) and payload type, the receive time and wire size, the packet hash, the hop path, and the channel hash/name (group messages) or the From/To node hashes (addressed packets). For channel messages your device can decrypt, the decoded \"sender: message\" line is attached too. The log is RAM-only and clears on reboot.\r\n\r\nA running **RX packets** count also appears on the radio details page on the home screen, just beneath the noise-floor reading. It counts flood and direct packets received since boot and resets on reboot or when you change radio parameters.\r\n\r\n### SMS Inbox unread badge -- 4G and Max\r\n\r\nThe SMS app's inbox entry now shows a count of unread received messages in brackets (e.g. **SMS Inbox [3]**), and the badge disappears once everything is read. Read state is stored per message on the SD card, so the count survives reboots and modem power-cycles. Opening a conversation marks it read.\r\n\r\n### T-Deck Max power, wake, and GPS fixes\r\n\r\n- **USB-C wake after shutdown** -- after a full power-off, plugging in USB-C now reliably powers the Max back on. The Max uses the SY6970 charger (0x6A); its BATFET shutdown is now handled to match, so charger plug-in re-wakes the board.\r\n- **GPS power** -- GPS power on the Max is routed through the XL9555 I/O expander rather than a dedicated pin; powering it on and off now works correctly.\r\n- **CPU frequency scaling** -- idle / boost / low-power CPU management to trim current draw, with the low-power floor held at 80 MHz (40 MHz breaks I2C on the Max).\r\n- **Idle BLE power** -- the BLE controller now stays powered down until you first turn Bluetooth on, reclaiming its idle current in the standalone-first default. This applies to all ESP32 BLE builds, not just the Max.\r\n- **Minesweeper** -- grid alignment fixes and a larger 15x20 / 50-mine board sized to the Max e-ink panel.\r\n\r\n### Channel and repeater refinements -- all devices\r\n\r\n- **Region on incoming messages** -- the message path-detail view now shows the resolved region for scoped channel messages it recognises.\r\n- **Path detail** -- the route line now reports hop count and bytes-per-hop (e.g. \"2 hops (2-byte)\"), and the last-message age line shows hop/byte info.\r\n- **Repeater admin** -- two new configuration commands: Set Flood Max Unscoped (`flood.max.unscoped`) and Set Flood Adv Max (`flood.max.advert`).\r\n\r\n### Documentation\r\n\r\nThe README and the hyperlinked **Meck_README_v1.12.pdf** are updated for this release.\r\n\r\n## First-Time Flashing\r\n\r\nEach build comes in two forms:\r\n\r\n- **`-merged.bin`** -- bootloader, partition table, and firmware in a single image. Flash at address `0x0`. Use this for a first-time flash, when coming from other firmware, **or if a device will not boot after an update**. \r\n\r\n- **`.bin`** -- application firmware only. Use this to update an existing Meck install, including OTA updates from your phone (**Settings -> OTA Tools**).\r\n\r\nThe partition layout supports dual OTA slots, so the previous firmware remains on the inactive partition as an automatic rollback target if a new image fails to boot.\r\n\r\n## Build Files\r\n\r\nGrouped by device. Each variant ships as a merged (`-merged.bin`, first flash) and non-merged (`.bin`, \n…", "notesHtml": "

v1.12 is a polish-and-power release across all three companion devices. The headline addition is an on-device Rx Log packet sniffer -- a live view of every packet your radio hears -- available on every build. Alongside it: an unread badge for the SMS inbox, a batch of T-Deck Max power, wake, and GPS fixes, and a set of channel and repeater refinements.

\n

What's New in v1.12

\n

Rx Log packet sniffer -- all devices

\n

A new on-device packet sniffer, mirroring the Rx Log in the MeshCore companion app. Open it from Settings -> Rx Log >>. It captures every packet the radio receives -- including relays destined for other nodes, since capture happens before filtering -- into a buffer of the most recent 100 packets, newest first. Each entry shows the route type (flood/direct) and payload type, the receive time and wire size, the packet hash, the hop path, and the channel hash/name (group messages) or the From/To node hashes (addressed packets). For channel messages your device can decrypt, the decoded \"sender: message\" line is attached too. The log is RAM-only and clears on reboot.

\n

A running RX packets count also appears on the radio details page on the home screen, just beneath the noise-floor reading. It counts flood and direct packets received since boot and resets on reboot or when you change radio parameters.

\n

SMS Inbox unread badge -- 4G and Max

\n

The SMS app's inbox entry now shows a count of unread received messages in brackets (e.g. SMS Inbox [3]), and the badge disappears once everything is read. Read state is stored per message on the SD card, so the count survives reboots and modem power-cycles. Opening a conversation marks it read.

\n

T-Deck Max power, wake, and GPS fixes

\n
    \n
  • USB-C wake after shutdown -- after a full power-off, plugging in USB-C now reliably powers the Max back on. The Max uses the SY6970 charger (0x6A); its BATFET shutdown is now handled to match, so charger plug-in re-wakes the board.
    • \n
  • GPS power -- GPS power on the Max is routed through the XL9555 I/O expander rather than a dedicated pin; powering it on and off now works correctly.
    • \n
  • CPU frequency scaling -- idle / boost / low-power CPU management to trim current draw, with the low-power floor held at 80 MHz (40 MHz breaks I2C on the Max).
    • \n
  • Idle BLE power -- the BLE controller now stays powered down until you first turn Bluetooth on, reclaiming its idle current in the standalone-first default. This applies to all ESP32 BLE builds, not just the Max.
    • \n
  • Minesweeper -- grid alignment fixes and a larger 15x20 / 50-mine board sized to the Max e-ink panel.
    • \n
\n

Channel and repeater refinements -- all devices

\n
    \n
  • Region on incoming messages -- the message path-detail view now shows the resolved region for scoped channel messages it recognises.
    • \n
  • Path detail -- the route line now reports hop count and bytes-per-hop (e.g. \"2 hops (2-byte)\"), and the last-message age line shows hop/byte info.
    • \n
  • Repeater admin -- two new configuration commands: Set Flood Max Unscoped (flood.max.unscoped) and Set Flood Adv Max (flood.max.advert).
    • \n
\n

Documentation

\n

The README and the hyperlinked Meck_README_v1.12.pdf are updated for this release.

\n

First-Time Flashing

\n

Each build comes in two forms:

\n
    \n

  • <name>-merged.bin -- bootloader, partition table, and firmware in a single image. Flash at address 0x0. Use this for a first-time flash, when coming from other firmware, or if a device will not boot after an update.

    \n
    • \n

  • <name>.bin -- application firmware only. Use this to update an existing Meck install, including OTA updates from your phone (Settings -> OTA Tools).

    \n
    • \n
\n

The partition layout supports dual OTA slots, so the previous firmware remains on the inactive partition as an automatic rollback target if a new image fails to boot.

\n

Build Files

\n

Grouped by device. Each variant ships as a merged (-merged.bin, first flash) and non-merged (.bin, \n…

\n" }, { "version": "maxv1.11", "name": "Meck v1.11 -- T-Deck Max Support", "datetime": "2026-06-04T18:56:49Z", "url": "https://github.com/pelgraine/Meck/releases/tag/maxv1.11", "prerelease": false, "notes": ">⚠️ Files from 2+hrs ago have now been patched with the correct bootloader. Please re-download fresh copies if you've been having trouble booting for the first time⚠️ \r\n\r\nThis release adds the **LilyGo T-Deck Max** as a supported device. It runs the full Meck [v1.11](https://github.com/pelgraine/Meck/releases/tag/v1.11) feature set with the same on-device UI, keyboard controls, and screens as the T-Deck Pro -- all of those apply unchanged. The firmware version stays at v1.11 because the core feature set is the same, but the Max has hardware the other boards don't, so this build exposes several capabilities the standard T-Deck Pro builds can't.\r\n\r\nIf you are on a standard T-Deck Pro, T-Deck Pro 4G, T-Deck Pro Audio, or T5S3, use the [v1.11 release](https://github.com/pelgraine/Meck/releases/tag/v1.11) builds instead.\r\n\r\n---\r\n\r\n## What the T-Deck Max Adds\r\n\r\nThe headline difference is hardware: the Max carries an **A7682E 4G modem and an ES8311 audio codec at the same time**, wired through an XL9555 I/O expander. On the T-Deck Pro the modem and the audio DAC share one hardware slot and are mutually exclusive; on the Max you get the SMS & Phone app, the audiobook player, the alarm clock, **and** cellular data on a single device. The Max also adds a CST328 capacitive touchscreen, three capacitive front buttons, a DRV2605 haptic motor for vibrate alerts, an e-ink frontlight, and a 1500 mAh battery with a BQ27220 fuel gauge.\r\n\r\n### 4G and Audio at the Same Time\r\n\r\nEvery Max build includes both the 4G modem and the audio codec -- there is no \"audio vs 4G\" split like the T-Deck Pro. The home screen carries the full app set: Audiobooks (**P**), Alarm (**K**), Phone & SMS (**T**), Browser & IRC (**B**), Discover (**F**), and Voice Messages (**Mic**). Audio output runs through a shared speaker mux that switches between the modem (calls, ringtones, modem tones) and the ES8311 codec (audiobooks, alarms, notification MP3s) automatically.\r\n\r\n> The Max records and plays voice notes through its ES8311 codec (the same output path that drives audiobooks and alarms). Sending a recorded note over the mesh is not yet verified -- see Known Limitations below.\r\n\r\n### Antenna (Internal / External)\r\n\r\nThe Max has both an on-board internal antenna and an external MMCX antenna connector, with a switch in **Settings** to select between them. **Internal is the default** -- if you want to use an external MMCX antenna, change the switch in Settings first.\r\n\r\n### E-Ink Frontlight with Adjustable Brightness\r\n\r\nThe Max has an e-ink frontlight -- a first for the T-Deck line. The on-level is set in **Settings → Backlight Brightness**, adjustable from **5% to 100% in 5% steps** (default 100%); this setting only appears on the Max. You can switch the frontlight on with the new **Heart capacitive button** (turns on at the configured brightness) or with **Alt + B** (turns on at minimum brightness).\r\n\r\n### Capacitive Touch Buttons\r\n\r\nThe Max adds a CST328 capacitive touchscreen plus **three capacitive buttons** along the front bezel, none of which the T-Deck Pro has:\r\n\r\n- **Heart** -- toggle the e-ink frontlight (see above)\r\n- **Speech bubble** -- jump straight to the channel picker (same as pressing **M**)\r\n- **Paper plane** -- jump straight to the DM inbox\r\n\r\n### Buzzer (Vibrate) Notifications\r\n\r\nThe Max's DRV2605 haptic motor can be used for silent alerts. In **Settings → Channels**, highlight a channel, press **T** to open the notification tone picker, and choose the new **Buzzer (vibrate)** entry (just below \"Default (silent)\"). Incoming messages on that channel pulse the motor instead of sounding a tone -- useful for silent alerts. The Max also supports custom MP3 tones from the `/alarms/` folder, like the T-Deck Pro audio variant.\r\n\r\n### Multi-Constellation GPS\r\n\r\nThe Max's GPS is configured for multi-constellation positioning -- **GPS, Galileo, and BeiDou** (via the `$PCAS04,7` command) -- for faster fixes and better coverage than single-constellation GPS.\r\n\r\n#\n…", "notesHtml": "
\n

⚠️ Files from 2+hrs ago have now been patched with the correct bootloader. Please re-download fresh copies if you've been having trouble booting for the first time⚠️

\n
\n

This release adds the LilyGo T-Deck Max as a supported device. It runs the full Meck v1.11 feature set with the same on-device UI, keyboard controls, and screens as the T-Deck Pro -- all of those apply unchanged. The firmware version stays at v1.11 because the core feature set is the same, but the Max has hardware the other boards don't, so this build exposes several capabilities the standard T-Deck Pro builds can't.

\n

If you are on a standard T-Deck Pro, T-Deck Pro 4G, T-Deck Pro Audio, or T5S3, use the v1.11 release builds instead.

\n
\n

What the T-Deck Max Adds

\n

The headline difference is hardware: the Max carries an A7682E 4G modem and an ES8311 audio codec at the same time, wired through an XL9555 I/O expander. On the T-Deck Pro the modem and the audio DAC share one hardware slot and are mutually exclusive; on the Max you get the SMS & Phone app, the audiobook player, the alarm clock, and cellular data on a single device. The Max also adds a CST328 capacitive touchscreen, three capacitive front buttons, a DRV2605 haptic motor for vibrate alerts, an e-ink frontlight, and a 1500 mAh battery with a BQ27220 fuel gauge.

\n

4G and Audio at the Same Time

\n

Every Max build includes both the 4G modem and the audio codec -- there is no \"audio vs 4G\" split like the T-Deck Pro. The home screen carries the full app set: Audiobooks (P), Alarm (K), Phone & SMS (T), Browser & IRC (B), Discover (F), and Voice Messages (Mic). Audio output runs through a shared speaker mux that switches between the modem (calls, ringtones, modem tones) and the ES8311 codec (audiobooks, alarms, notification MP3s) automatically.

\n
\n

The Max records and plays voice notes through its ES8311 codec (the same output path that drives audiobooks and alarms). Sending a recorded note over the mesh is not yet verified -- see Known Limitations below.

\n
\n

Antenna (Internal / External)

\n

The Max has both an on-board internal antenna and an external MMCX antenna connector, with a switch in Settings to select between them. Internal is the default -- if you want to use an external MMCX antenna, change the switch in Settings first.

\n

E-Ink Frontlight with Adjustable Brightness

\n

The Max has an e-ink frontlight -- a first for the T-Deck line. The on-level is set in Settings → Backlight Brightness, adjustable from 5% to 100% in 5% steps (default 100%); this setting only appears on the Max. You can switch the frontlight on with the new Heart capacitive button (turns on at the configured brightness) or with Alt + B (turns on at minimum brightness).

\n

Capacitive Touch Buttons

\n

The Max adds a CST328 capacitive touchscreen plus three capacitive buttons along the front bezel, none of which the T-Deck Pro has:

\n
    \n
  • Heart -- toggle the e-ink frontlight (see above)
    • \n
  • Speech bubble -- jump straight to the channel picker (same as pressing M)
    • \n
  • Paper plane -- jump straight to the DM inbox
    • \n
\n

Buzzer (Vibrate) Notifications

\n

The Max's DRV2605 haptic motor can be used for silent alerts. In Settings → Channels, highlight a channel, press T to open the notification tone picker, and choose the new Buzzer (vibrate) entry (just below \"Default (silent)\"). Incoming messages on that channel pulse the motor instead of sounding a tone -- useful for silent alerts. The Max also supports custom MP3 tones from the /alarms/ folder, like the T-Deck Pro audio variant.

\n

Multi-Constellation GPS

\n

The Max's GPS is configured for multi-constellation positioning -- GPS, Galileo, and BeiDou (via the $PCAS04,7 command) -- for faster fixes and better coverage than single-constellation GPS.

\n

\n

…

\n" }, { "version": "v1.11", "name": "Meck v1.11 -- Private Channels, Channel Sharing, Config Export/Import", "datetime": "2026-05-22T22:10:58Z", "url": "https://github.com/pelgraine/Meck/releases/tag/v1.11", "prerelease": false, "notes": "This release adds private channel support, the ability to share channels with other Meck users via encrypted DM, and a full config export/import system for backing up and migrating device configurations. Also includes two new emoji, an expanded Minesweeper grid on the T5S3, and a fix for contacts with stuck clocks sinking in the recency-sorted contacts list.\r\n\r\n---\r\n\r\n## First-Time Flashing -- Read This First\r\n\r\nEach firmware is provided in two formats:\r\n\r\n- **`filename.bin`** -- the application firmware only. Use this for **updating** an existing Meck install (including OTA updates from your phone).\r\n- **`filename-merged.bin`** -- includes the bootloader, partition table, and application firmware in a single image. **Use this if you are flashing Meck for the first time**, coming from a different firmware, or if your device is not booting correctly after an update.\r\n\r\n**If in doubt, use the `-merged.bin` file.** It will always work regardless of what was previously on the device.\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to **https://flasher.meshcore.io/**\r\n2. Select **Custom Firmware**\r\n3. Load the `.bin` or `-merged.bin` file and click **Flash**\r\n4. Select your device in the popup and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\n```\r\nesptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\r\n```\r\n\r\n---\r\n\r\n## What's New Since v1.10\r\n\r\n### Private Channels\r\n\r\nMeck now supports private channels alongside the existing public hashtag channels. The difference is in how the channel secret is generated:\r\n\r\n- **Public (hashtag) channels** — type a name starting with `#` (e.g. `#camping`). The 16-byte secret is derived deterministically from the name via SHA-256, so anyone on any MeshCore device who creates the same hashtag name gets the same key and can communicate on that channel.\r\n- **Private channels** — type a name **without** the `#` prefix (e.g. `team-alpha`). A cryptographically random 16-byte secret is generated, meaning only devices that have been explicitly given the key can participate.\r\n\r\n**How to create a private channel:**\r\n\r\n1. From the home screen, press **S** to open settings\r\n2. Scroll down to the **Channels >>** section and press Enter to open it\r\n3. Navigate to **+ Add Channel (# = public)** and press Enter\r\n4. Type the channel name **without** a `#` prefix, then press Enter\r\n\r\nThe channel is created with a random secret. To let other Meck users join, use channel sharing (see below).\r\n\r\n### Channel Sharing via DM\r\n\r\nYou can now share any channel — public or private — with another Meck user by sending them the channel name and secret as an encrypted direct message. This is particularly useful for private channels, where sharing the secret manually would mean typing 32 hex characters.\r\n\r\n**How to share a channel:**\r\n\r\n1. From the home screen, press **S** to open settings\r\n2. Scroll down to the **Channels >>** section and press Enter to open it\r\n3. Navigate to the channel you want to share\r\n4. Press **C** to open the contact picker\r\n5. Select a contact and press Enter to send\r\n\r\nThe recipient's device automatically adds the channel to their channel list (if it doesn't already exist and there's an empty slot). An alert confirms the channel was added. In the DM conversation, both sender and recipient see a sanitised message (\"Shared channel: name\") rather than the raw protocol data.\r\n\r\nOn the T5S3, channel sharing works the same way via the CardKB keyboard.\r\n\r\n### Config Export/Import\r\n\r\nA new **Export/Import >>** sub-screen in Settings lets you back up and restore your device configuration via JSON files on the SD card. This is useful for migrating settings to a new board, keeping a backup before reflashing, or cloning a configuration across multiple devices.\r\n\r\n**Exporting:**\r\n\r\n1. From the home screen, press **S** to open settings\r\n2. Scroll down to **Export/Import >>** and press Enter\r\n3. Select **Export to SD >>** and press Enter\r\n4. Toggle which sections t\n…", "notesHtml": "

This release adds private channel support, the ability to share channels with other Meck users via encrypted DM, and a full config export/import system for backing up and migrating device configurations. Also includes two new emoji, an expanded Minesweeper grid on the T5S3, and a fix for contacts with stuck clocks sinking in the recency-sorted contacts list.

\n
\n

First-Time Flashing -- Read This First

\n

Each firmware is provided in two formats:

\n
    \n
  • filename.bin -- the application firmware only. Use this for updating an existing Meck install (including OTA updates from your phone).
    • \n
  • filename-merged.bin -- includes the bootloader, partition table, and application firmware in a single image. Use this if you are flashing Meck for the first time, coming from a different firmware, or if your device is not booting correctly after an update.
    • \n
\n

If in doubt, use the -merged.bin file. It will always work regardless of what was previously on the device.

\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.io/
    2. \n
  2. Select Custom Firmware
    3. \n
  3. Load the .bin or -merged.bin file and click Flash
    4. \n
  4. Select your device in the popup and click Connect
    5. \n
\n

Flashing with esptool.py

\n
esptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\n
\n
\n

What's New Since v1.10

\n

Private Channels

\n

Meck now supports private channels alongside the existing public hashtag channels. The difference is in how the channel secret is generated:

\n
    \n
  • Public (hashtag) channels — type a name starting with # (e.g. #camping). The 16-byte secret is derived deterministically from the name via SHA-256, so anyone on any MeshCore device who creates the same hashtag name gets the same key and can communicate on that channel.
    • \n
  • Private channels — type a name without the # prefix (e.g. team-alpha). A cryptographically random 16-byte secret is generated, meaning only devices that have been explicitly given the key can participate.
    • \n
\n

How to create a private channel:

\n
    \n
  1. From the home screen, press S to open settings
    2. \n
  2. Scroll down to the Channels >> section and press Enter to open it
    3. \n
  3. Navigate to + Add Channel (# = public) and press Enter
    4. \n
  4. Type the channel name without a # prefix, then press Enter
    5. \n
\n

The channel is created with a random secret. To let other Meck users join, use channel sharing (see below).

\n

Channel Sharing via DM

\n

You can now share any channel — public or private — with another Meck user by sending them the channel name and secret as an encrypted direct message. This is particularly useful for private channels, where sharing the secret manually would mean typing 32 hex characters.

\n

How to share a channel:

\n
    \n
  1. From the home screen, press S to open settings
    2. \n
  2. Scroll down to the Channels >> section and press Enter to open it
    3. \n
  3. Navigate to the channel you want to share
    4. \n
  4. Press C to open the contact picker
    5. \n
  5. Select a contact and press Enter to send
    6. \n
\n

The recipient's device automatically adds the channel to their channel list (if it doesn't already exist and there's an empty slot). An alert confirms the channel was added. In the DM conversation, both sender and recipient see a sanitised message (\"Shared channel: name\") rather than the raw protocol data.

\n

On the T5S3, channel sharing works the same way via the CardKB keyboard.

\n

Config Export/Import

\n

A new Export/Import >> sub-screen in Settings lets you back up and restore your device configuration via JSON files on the SD card. This is useful for migrating settings to a new board, keeping a backup before reflashing, or cloning a configuration across multiple devices.

\n

Exporting:

\n
    \n
  1. From the home screen, press S to open settings
    2. \n
  2. Scroll down to Export/Import >> and press Enter
    3. \n
  3. Select Export to SD >> and press Enter
    4. \n
  4. Toggle which sections t\n…
    5. \n
\n" }, { "version": "v1.10", "name": "Meck v1.10 -- Custom Channel Notification Tones, Per-Channel Notifications, Message History Deletion, Games", "datetime": "2026-05-14T23:37:31Z", "url": "https://github.com/pelgraine/Meck/releases/tag/v1.10", "prerelease": true, "notes": "A feature-packed update for the **T-Deck Pro**. This release adds custom notification tones for both the Audio and 4G variants, per-channel notification preferences with @mention support, the ability to delete message history per channel, a games menu with Snake and Minesweeper, and expands the maximum group channel count to 40 across all builds.\r\n\r\n---\r\n\r\n## First-Time Flashing -- Read This First\r\n\r\nEach firmware is provided in two formats:\r\n\r\n- **`filename.bin`** -- the application firmware only. Use this for **updating** an existing Meck install (including OTA updates from your phone).\r\n- **`filename-merged.bin`** -- includes the bootloader, partition table, and application firmware in a single image. **Use this if you are flashing Meck for the first time**, coming from a different firmware, or if your device is not booting correctly after an update.\r\n\r\n**If in doubt, use the `-merged.bin` file.** It will always work regardless of what was previously on the device.\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to **https://flasher.meshcore.io/**\r\n2. Select **Custom Firmware**\r\n3. Load the `.bin` or `-merged.bin` file and click **Flash**\r\n4. Select your device in the popup and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\n```\r\nesptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\r\n```\r\n\r\n---\r\n\r\n## What's New Since v1.9\r\n\r\n### Custom Notification Tones (Audio + 4G Variants)\r\n\r\nEach channel can now have its own notification tone instead of the default buzzer. When a message arrives on a channel with a custom tone assigned, that tone plays through the speaker and the buzzer is suppressed.\r\n\r\n**How to set a custom tone:**\r\n\r\n1. From the home screen, press **S** to open settings\r\n2. Scroll down to the **Channels >>** section and press Enter to open it\r\n3. Navigate to the channel you want to customise\r\n4. Press **T** to open the tone picker\r\n5. Use **W/S** to browse the available tones, then press **Enter** to select\r\n6. To remove a custom tone, select **Default (silent)** from the top of the list\r\n\r\n**Audio variant (PCM5102A DAC):** A selection of bundled tones are copied to the `/alarms/` folder on the SD card on first boot. You can also drop your own MP3 files into that folder -- they'll appear in the tone picker alongside the bundled options. This gives you complete flexibility to use any short MP3 as a notification sound.\r\n\r\n**4G variant (A7682E modem):** Seven bundled notification tones are embedded in the firmware as 8kHz mono WAV files. On first boot (with the 4G modem enabled in settings and the red LED on and blinking to indicate the modem is ready), the tones are transferred to the modem's internal filesystem. Playback goes through the modem's own speaker amplifier. Custom user-supplied tones are not supported on the 4G variant -- only the bundled set is available. The 4G modem must be switched on in settings for the notification tones to work, as all audio output on the 4G variant goes through the modem hardware.\r\n\r\n**Available bundled tones:** Bell, Ding, High Trill, Low Soft Ding (x2), Mid Trill, and Soft Notif. All are short, 1-2 second alert sounds.\r\n\r\n### Per-Channel Notification Preferences\r\n\r\nEach channel and the DM inbox can now be individually set to one of three notification levels:\r\n\r\n- **All** -- notify on every message (default)\r\n- **@ (Mentions)** -- only notify when someone tags you with `@YourNodeName` or `@[YourNodeName]` in their message\r\n- **Off** -- completely muted (no buzzer, no custom tone, no keyboard backlight flash, no screen wake, no toast popup)\r\n\r\nMessages are always stored in history regardless of the notification setting -- only the alerts and unread badges are suppressed. You won't miss anything; you just won't be interrupted.\r\n\r\n**How to set notification preferences:**\r\n\r\n1. From the home screen, press **S** to open settings\r\n2. Scroll down to the **Channels >>** section and press Enter to open it\r\n3. Navigate to the channel you w\n…", "notesHtml": "

A feature-packed update for the T-Deck Pro. This release adds custom notification tones for both the Audio and 4G variants, per-channel notification preferences with @mention support, the ability to delete message history per channel, a games menu with Snake and Minesweeper, and expands the maximum group channel count to 40 across all builds.

\n
\n

First-Time Flashing -- Read This First

\n

Each firmware is provided in two formats:

\n
    \n
  • filename.bin -- the application firmware only. Use this for updating an existing Meck install (including OTA updates from your phone).
    • \n
  • filename-merged.bin -- includes the bootloader, partition table, and application firmware in a single image. Use this if you are flashing Meck for the first time, coming from a different firmware, or if your device is not booting correctly after an update.
    • \n
\n

If in doubt, use the -merged.bin file. It will always work regardless of what was previously on the device.

\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.io/
    2. \n
  2. Select Custom Firmware
    3. \n
  3. Load the .bin or -merged.bin file and click Flash
    4. \n
  4. Select your device in the popup and click Connect
    5. \n
\n

Flashing with esptool.py

\n
esptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\n
\n
\n

What's New Since v1.9

\n

Custom Notification Tones (Audio + 4G Variants)

\n

Each channel can now have its own notification tone instead of the default buzzer. When a message arrives on a channel with a custom tone assigned, that tone plays through the speaker and the buzzer is suppressed.

\n

How to set a custom tone:

\n
    \n
  1. From the home screen, press S to open settings
    2. \n
  2. Scroll down to the Channels >> section and press Enter to open it
    3. \n
  3. Navigate to the channel you want to customise
    4. \n
  4. Press T to open the tone picker
    5. \n
  5. Use W/S to browse the available tones, then press Enter to select
    6. \n
  6. To remove a custom tone, select Default (silent) from the top of the list
    7. \n
\n

Audio variant (PCM5102A DAC): A selection of bundled tones are copied to the /alarms/ folder on the SD card on first boot. You can also drop your own MP3 files into that folder -- they'll appear in the tone picker alongside the bundled options. This gives you complete flexibility to use any short MP3 as a notification sound.

\n

4G variant (A7682E modem): Seven bundled notification tones are embedded in the firmware as 8kHz mono WAV files. On first boot (with the 4G modem enabled in settings and the red LED on and blinking to indicate the modem is ready), the tones are transferred to the modem's internal filesystem. Playback goes through the modem's own speaker amplifier. Custom user-supplied tones are not supported on the 4G variant -- only the bundled set is available. The 4G modem must be switched on in settings for the notification tones to work, as all audio output on the 4G variant goes through the modem hardware.

\n

Available bundled tones: Bell, Ding, High Trill, Low Soft Ding (x2), Mid Trill, and Soft Notif. All are short, 1-2 second alert sounds.

\n

Per-Channel Notification Preferences

\n

Each channel and the DM inbox can now be individually set to one of three notification levels:

\n
    \n
  • All -- notify on every message (default)
    • \n
  • @ (Mentions) -- only notify when someone tags you with @YourNodeName or @[YourNodeName] in their message
    • \n
  • Off -- completely muted (no buzzer, no custom tone, no keyboard backlight flash, no screen wake, no toast popup)
    • \n
\n

Messages are always stored in history regardless of the notification setting -- only the alerts and unread badges are suppressed. You won't miss anything; you just won't be interrupted.

\n

How to set notification preferences:

\n
    \n
  1. From the home screen, press S to open settings
    2. \n
  2. Scroll down to the Channels >> section and press Enter to open it
    3. \n
  3. Navigate to the channel you w\n…
    4. \n
\n" }, { "version": "v1.9", "name": "Meck v1.9 — Trace Route Screen, DM Persistence, Minor fixes", "datetime": "2026-05-07T10:35:12Z", "url": "https://github.com/pelgraine/Meck/releases/tag/v1.9", "prerelease": true, "notes": "A small but meaningful update for the T-Deck Pro and T5S3 E-Paper Pro. This release adds an on-device trace route screen, fixes DM message history loss across reboots, and patches a handful of settings that weren't being persisted properly.\r\n\r\n---\r\n\r\n## First-Time Flashing — Read This First\r\n\r\nEach firmware is provided in two formats:\r\n\r\n- **`filename.bin`** — the application firmware only. Use this for **updating** an existing Meck install (including OTA updates from your phone).\r\n- **`filename-merged.bin`** — includes the bootloader, partition table, and application firmware in a single image. **Use this if you are flashing Meck for the first time**, coming from a different firmware, or if your device is not booting correctly after an update.\r\n\r\n**If in doubt, use the `-merged.bin` file.** It will always work regardless of what was previously on the device.\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to ****\r\n2. Select **Custom Firmware**\r\n3. Load the `.bin` or `-merged.bin` file and click **Flash**\r\n4. Select your device in the popup and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\n esptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\r\n\r\n---\r\n\r\n## What's New Since v1.8\r\n\r\n### 🔍 Trace Route Screen (T-Deck Pro)\r\n\r\nMeck now has an on-device equivalent to the trace path feature in the MeshCore companion app. Press **R** from the home screen to open the trace screen, build a repeater chain, and run a trace — no BLE/WiFi pairing or phone needed.\r\n\r\nThe path can be built two ways:\r\n\r\n- **+ Add repeater** — opens a picker showing all known Repeater contacts. Press Enter on a repeater to append it to the path. Repeat to build multi-hop chains.\r\n- **Type Path** — opens an inline text editor for comma-separated decimal hash values (e.g. `3601,2198,1244,2198,3601`), matching the format the companion app uses. Useful when the repeater isn't in your contacts but you know its hash.\r\n\r\nOnce the path is built, select **Run Trace** and Meck sends a `PAYLOAD_TYPE_TRACE` packet direct-routed through the chain. Each repeater that recognises its hash appends its receive SNR before forwarding. When the packet completes the round-trip, the screen shows per-hop SNR results and the round-trip time.\r\n\r\nA few things worth knowing:\r\n\r\n- **The path must be symmetric for a round-trip.** To trace through repeaters A → B → C and back, type `A,B,C,B,A`. You also need to be able to hear the last repeater in the chain (the one that responds) directly.\r\n- **1-byte vs 2-byte hash mode** is selectable on the screen and follows your device's `path.hash.mode` setting by default. The companion app uses 2-byte mode in most regions.\r\n- **Up to 16 hops**, with a 30-second timeout per trace.\r\n\r\n| Key | Action |\r\n|-----|--------|\r\n| W / S | Navigate menu items |\r\n| Enter | Select / confirm / open editor |\r\n| A / D | Toggle hash mode (1-byte / 2-byte) on the mode row |\r\n| 0–9 , | Enter path values when the inline editor is open |\r\n| Q | Cancel edit / back to home screen |\r\n\r\nT5S3 users with a CardKB attached can also access the trace screen via the **R** key.\r\n\r\n### 📩 DM Message Persistence\r\n\r\nDM message history now survives reboots correctly. Previously, the in-memory `ChannelMessage` struct tracked which peer each DM belonged to, but the on-disk `MsgFileRecord` did not — so although the messages themselves were saved to SD, every DM lost its peer association on reload and ended up in a single muddled bucket.\r\n\r\nThe fix adds a `dm_peer_hash` field to the on-disk record and bumps `MSG_FILE_VERSION` from 3 to 4. New DMs received under v1.9 will persist correctly with their peer association intact.\r\n\r\n> ⚠️ **Existing v1.8 message history on the SD card will be discarded on first boot of v1.9** due to the version bump. Channel messages and DMs received under v1.8 will not migrate forward — only messages received from v1.9 onward will appear in your history. This is a one-time eve\n…", "notesHtml": "

A small but meaningful update for the T-Deck Pro and T5S3 E-Paper Pro. This release adds an on-device trace route screen, fixes DM message history loss across reboots, and patches a handful of settings that weren't being persisted properly.

\n
\n

First-Time Flashing — Read This First

\n

Each firmware is provided in two formats:

\n
    \n
  • filename.bin — the application firmware only. Use this for updating an existing Meck install (including OTA updates from your phone).
    • \n
  • filename-merged.bin — includes the bootloader, partition table, and application firmware in a single image. Use this if you are flashing Meck for the first time, coming from a different firmware, or if your device is not booting correctly after an update.
    • \n
\n

If in doubt, use the -merged.bin file. It will always work regardless of what was previously on the device.

\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.io/
    2. \n
  2. Select Custom Firmware
    3. \n
  3. Load the .bin or -merged.bin file and click Flash
    4. \n
  4. Select your device in the popup and click Connect
    5. \n
\n

Flashing with esptool.py

\n
esptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\n
\n
\n

What's New Since v1.8

\n

🔍 Trace Route Screen (T-Deck Pro)

\n

Meck now has an on-device equivalent to the trace path feature in the MeshCore companion app. Press R from the home screen to open the trace screen, build a repeater chain, and run a trace — no BLE/WiFi pairing or phone needed.

\n

The path can be built two ways:

\n
    \n
  • + Add repeater — opens a picker showing all known Repeater contacts. Press Enter on a repeater to append it to the path. Repeat to build multi-hop chains.
    • \n
  • Type Path — opens an inline text editor for comma-separated decimal hash values (e.g. 3601,2198,1244,2198,3601), matching the format the companion app uses. Useful when the repeater isn't in your contacts but you know its hash.
    • \n
\n

Once the path is built, select Run Trace and Meck sends a PAYLOAD_TYPE_TRACE packet direct-routed through the chain. Each repeater that recognises its hash appends its receive SNR before forwarding. When the packet completes the round-trip, the screen shows per-hop SNR results and the round-trip time.

\n

A few things worth knowing:

\n
    \n
  • The path must be symmetric for a round-trip. To trace through repeaters A → B → C and back, type A,B,C,B,A. You also need to be able to hear the last repeater in the chain (the one that responds) directly.
    • \n
  • 1-byte vs 2-byte hash mode is selectable on the screen and follows your device's path.hash.mode setting by default. The companion app uses 2-byte mode in most regions.
    • \n
  • Up to 16 hops, with a 30-second timeout per trace.
    • \n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
KeyAction
W / SNavigate menu items
EnterSelect / confirm / open editor
A / DToggle hash mode (1-byte / 2-byte) on the mode row
0–9 ,Enter path values when the inline editor is open
QCancel edit / back to home screen
\n

T5S3 users with a CardKB attached can also access the trace screen via the R key.

\n

📩 DM Message Persistence

\n

DM message history now survives reboots correctly. Previously, the in-memory ChannelMessage struct tracked which peer each DM belonged to, but the on-disk MsgFileRecord did not — so although the messages themselves were saved to SD, every DM lost its peer association on reload and ended up in a single muddled bucket.

\n

The fix adds a dm_peer_hash field to the on-disk record and bumps MSG_FILE_VERSION from 3 to 4. New DMs received under v1.9 will persist correctly with their peer association intact.

\n
\n

⚠️ Existing v1.8 message history on the SD card will be discarded on first boot of v1.9 due to the version bump. Channel messages and DMs received under v1.8 will not migrate forward — only messages received from v1.9 onward will appear in your history. This is a one-time eve\n…

\n
\n" }, { "version": "v1.8", "name": "Meck v1.8 — Diacritics, Faster Page Scroll, True Power Off, BLE Boost", "datetime": "2026-05-03T11:29:22Z", "url": "https://github.com/pelgraine/Meck/releases/tag/v1.8", "prerelease": true, "notes": "An update for the T-Deck Pro and T5S3 E-Paper Pro. This release adds accented character support for international users, page scroll on all list screens, true deep sleep power-off, BLE performance improvements, and numerous fixes. Ten firmware variants across both platforms.\r\n\r\n---\r\n\r\n## First-Time Flashing — Read This First\r\n\r\nEach firmware is provided in two formats:\r\n\r\n* **`filename.bin`** — the application firmware only. Use this for **updating** an existing Meck install (including OTA updates from your phone).\r\n* **`filename-merged.bin`** — includes the bootloader, partition table, and application firmware in a single image. **Use this if you are flashing Meck for the first time**, coming from a different firmware, or if your device is not booting correctly after an update.\r\n\r\n**If in doubt, use the `-merged.bin` file.** It will always work regardless of what was previously on the device.\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to **https://flasher.meshcore.io/**\r\n2. Select **Custom Firmware**\r\n3. Load the `.bin` or `-merged.bin` file and click **Flash**\r\n4. Select your device in the popup and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\n```\r\nesptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\r\n```\r\n\r\n---\r\n\r\n## What's New Since v1.7\r\n\r\n### 🇨🇿 Accented Character Support\r\n\r\nMeck now properly handles accented and diacritical characters throughout the UI — channel messages, contact names, and the e-book reader. Czech (ěščřžýáíé), Polish (ąćęłńóśźż), French (àâçéèêëïôùûü), German (äöüß), and all other Latin Extended characters are now supported.\r\n\r\nPreviously, non-ASCII characters in received messages would either disappear entirely or render as emoji sprite artifacts. All three font styles now display these characters correctly — no more missing letters where diacritics used to be.\r\n\r\n**Noto Sans at Larger text size** renders accented characters with their full diacritical marks (carons, accents, cedillas, etc.) thanks to regenerated font files with Latin Extended-A glyph coverage. All other font and size combinations fold accented characters to their ASCII base letter (ě→e, ž→z, ñ→n, etc.) — you won't see the diacritic marks, but the letter itself is always visible.\r\n\"586669026-a3d22972-4b66-4b2c-b736-528f814b9ca4\"\r\n\"586668415-a3c38456-b98c-47f6-8c41-6cbacb2901c4\"\r\n\r\n### Faster Page Scroll (T-Deck Pro)\r\n\r\n**Shift+W** and **Shift+S** now jump a full page at a time on all scrollable list screens: Contacts, Discovery, Last Heard, Notes (file list), Text Reader (file list), and Settings. The page size is calculated from the screen height and current font metrics, so it adapts automatically to your font and text size choices.\r\n\r\nSingle-press W/S still scrolls one item at a time.\r\n\r\n### True Power Off (T-Deck Pro)\r\n\r\nThe home screen now includes a **Shutdown** page. Selecting it enters ESP32-S3 deep sleep with no software wake sources — the CPU halts, peripheral power is cut (keyboard, fuel gauge, sensors), and the LoRa module is powered down with NSS held high to prevent parasitic current draw.\r\n\r\n**Only a hardware reset (reset button) or USB power-on will wake the device.** This replaces the previous hibernate behaviour which maintained wake-on-packet capability. The old hibernate (with wake-on-LoRa) remains available on the auto-lock timeout.\r\n\r\n### New Emoji\r\n\r\nBeer mug (🍺) added as emoji #77. The emoji picker now has 77 total sprites.\r\n\r\n\"586668547-bd80ae7c-5d09-4016-b1ea-7d219a0d681c\"\r\n\"586668673-89009912-e1af-45ee-8923-8023b5bed023\"An update for the T-Deck Pro and T5S3 E-Paper Pro. This release adds accented character support for international users, page scroll on all list screens, true deep sleep power-off, BLE performance improvements, and numerous fixes. Ten firmware variants across both platforms.

\n
\n

First-Time Flashing — Read This First

\n

Each firmware is provided in two formats:

\n
    \n
  • filename.bin — the application firmware only. Use this for updating an existing Meck install (including OTA updates from your phone).
    • \n
  • filename-merged.bin — includes the bootloader, partition table, and application firmware in a single image. Use this if you are flashing Meck for the first time, coming from a different firmware, or if your device is not booting correctly after an update.
    • \n
\n

If in doubt, use the -merged.bin file. It will always work regardless of what was previously on the device.

\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.io/
    2. \n
  2. Select Custom Firmware
    3. \n
  3. Load the .bin or -merged.bin file and click Flash
    4. \n
  4. Select your device in the popup and click Connect
    5. \n
\n

Flashing with esptool.py

\n
esptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\n
\n
\n

What's New Since v1.7

\n

🇨🇿 Accented Character Support

\n

Meck now properly handles accented and diacritical characters throughout the UI — channel messages, contact names, and the e-book reader. Czech (ěščřžýáíé), Polish (ąćęłńóśźż), French (àâçéèêëïôùûü), German (äöüß), and all other Latin Extended characters are now supported.

\n

Previously, non-ASCII characters in received messages would either disappear entirely or render as emoji sprite artifacts. All three font styles now display these characters correctly — no more missing letters where diacritics used to be.

\n

Noto Sans at Larger text size renders accented characters with their full diacritical marks (carons, accents, cedillas, etc.) thanks to regenerated font files with Latin Extended-A glyph coverage. All other font and size combinations fold accented characters to their ASCII base letter (ě→e, ž→z, ñ→n, etc.) — you won't see the diacritic marks, but the letter itself is always visible.\n\"586669026-a3d22972-4b66-4b2c-b736-528f814b9ca4\"\n\"586668415-a3c38456-b98c-47f6-8c41-6cbacb2901c4\"

\n

Faster Page Scroll (T-Deck Pro)

\n

Shift+W and Shift+S now jump a full page at a time on all scrollable list screens: Contacts, Discovery, Last Heard, Notes (file list), Text Reader (file list), and Settings. The page size is calculated from the screen height and current font metrics, so it adapts automatically to your font and text size choices.

\n

Single-press W/S still scrolls one item at a time.

\n

True Power Off (T-Deck Pro)

\n

The home screen now includes a Shutdown page. Selecting it enters ESP32-S3 deep sleep with no software wake sources — the CPU halts, peripheral power is cut (keyboard, fuel gauge, sensors), and the LoRa module is powered down with NSS held high to prevent parasitic current draw.

\n

Only a hardware reset (reset button) or USB power-on will wake the device. This replaces the previous hibernate behaviour which maintained wake-on-packet capability. The old hibernate (with wake-on-LoRa) remains available on the auto-lock timeout.

\n

New Emoji

\n

Beer mug (🍺) added as emoji #77. The emoji picker now has 77 total sprites.

\n\"586668547-bd80ae7c-5d09-4016-b1ea-7d219a0d681c\"\n" }, { "version": "v1.7", "name": "Meck v1.7 — Channel Picker, Region Scope, Custom Fonts", "datetime": "2026-04-19T11:28:41Z", "url": "https://github.com/pelgraine/Meck/releases/tag/v1.7", "prerelease": true, "notes": "An update for the T-Deck Pro and T5S3 E-Paper Pro. This release adds a channel picker screen for quick channel switching, MeshCore region scope support for controlling flood message propagation, selectable font styles (Classic, Noto Sans, Montserrat), an expanded emoji picker, and numerous bug fixes. Ten firmware variants across both platforms.\r\n\r\n> **📄 Meck_README_v1.7.pdf** is included in this release — it covers all keyboard controls, touch gestures, screen navigation, settings, and feature documentation for all platforms, provided in PDF form for convenience.\r\n\r\n---\r\n\r\n## ⚠️ First-Time Flashing — Read This First\r\n\r\nEach firmware is provided in two formats:\r\n\r\n* **`filename.bin`** — the application firmware only. Use this for **updating** an existing Meck install (including OTA updates from your phone).\r\n* **`filename-merged.bin`** — includes the bootloader, partition table, and application firmware in a single image. **Use this if you are flashing Meck for the first time**, coming from a different firmware, or if your device is not booting correctly after an update.\r\n\r\n**If in doubt, use the `-merged.bin` file.** It will always work regardless of what was previously on the device.\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to **https://flasher.meshcore.io/**\r\n2. Select **Custom Firmware**\r\n3. Load the `.bin` or `-merged.bin` file and click **Flash**\r\n4. Select your device in the popup and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\n```\r\nesptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\r\n```\r\n\r\n---\r\n\r\n## What's New Since v1.6\r\n\r\n### 📋 Channel Picker Screen (T-Deck Pro & T5S3)\r\n\r\nThe A and D keys (T-Deck Pro) and swipe left/right (T5S3 channel screen) now open a **channel picker** instead of cycling through channels one at a time. The picker shows all your channels and the DM inbox in a single view with unread message badges, so you can jump directly to any channel.\r\n\r\nOn the T5S3, the picker displays a **vertical bubble list** matching the Meck P4 aesthetic — full-width outlined bubbles with the channel name left-aligned and unread badge right-aligned. On the T-Deck Pro, it uses a compact **vertical list**. Select a channel and press Enter (or tap) to switch to it. Press Q or Boot to go back.\r\n\r\nThe previous A/D cycling behaviour on the channel messages screen has been replaced — A and D now both open the picker. The footer hints have been updated accordingly (`A/D:List` instead of `A/D:Ch`).\r\n\r\n### 🌏 Region Scope (MeshCore v1.15+ Compatibility)\r\n\r\nMeck now supports **region scoping** for flood messages, bringing it in line with MeshCore v1.15. Regions limit how far your flood messages propagate through the mesh — when you set a region, outgoing messages are tagged with a transport code that repeaters use to decide whether to forward them. Messages sent without a region reach all repeaters via the default wildcard, same as always.\r\n\r\n**Device-wide default region:** Set a default region in **Settings → Default Region** (e.g. `au-nsw`). This applies to all channels and DMs unless a channel has its own override.\r\n\r\n**Per-channel region:** Each channel can have its own region scope. In Settings → Channels, select a channel and press Enter to edit its region. Setting a per-channel region overrides the device default for that channel only.\r\n\r\n**Serial commands:** `set region au-nsw`, `get region`, `set channel.scope 2 au-syd`, `get channel.scope 2`, `get channels` (now shows region scope tags). See the [Serial Settings Guide](Serial_Settings_Guide.md) for full documentation.\r\n\r\n**Settings nudge:** When exiting settings, if no region is configured anywhere (no device default and no per-channel scopes), a prompt reminds you to consider setting one. You can dismiss it to stay unscoped.\r\n\r\nRegion names are determined by your local mesh community — check with your local group for the names in use. Common patterns follow ISO 3166 country/subdivision codes (e.g. `au` f\n…", "notesHtml": "

An update for the T-Deck Pro and T5S3 E-Paper Pro. This release adds a channel picker screen for quick channel switching, MeshCore region scope support for controlling flood message propagation, selectable font styles (Classic, Noto Sans, Montserrat), an expanded emoji picker, and numerous bug fixes. Ten firmware variants across both platforms.

\n
\n

📄 Meck_README_v1.7.pdf is included in this release — it covers all keyboard controls, touch gestures, screen navigation, settings, and feature documentation for all platforms, provided in PDF form for convenience.

\n
\n
\n

⚠️ First-Time Flashing — Read This First

\n

Each firmware is provided in two formats:

\n
    \n
  • filename.bin — the application firmware only. Use this for updating an existing Meck install (including OTA updates from your phone).
    • \n
  • filename-merged.bin — includes the bootloader, partition table, and application firmware in a single image. Use this if you are flashing Meck for the first time, coming from a different firmware, or if your device is not booting correctly after an update.
    • \n
\n

If in doubt, use the -merged.bin file. It will always work regardless of what was previously on the device.

\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.io/
    2. \n
  2. Select Custom Firmware
    3. \n
  3. Load the .bin or -merged.bin file and click Flash
    4. \n
  4. Select your device in the popup and click Connect
    5. \n
\n

Flashing with esptool.py

\n
esptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\n
\n
\n

What's New Since v1.6

\n

📋 Channel Picker Screen (T-Deck Pro & T5S3)

\n

The A and D keys (T-Deck Pro) and swipe left/right (T5S3 channel screen) now open a channel picker instead of cycling through channels one at a time. The picker shows all your channels and the DM inbox in a single view with unread message badges, so you can jump directly to any channel.

\n

On the T5S3, the picker displays a vertical bubble list matching the Meck P4 aesthetic — full-width outlined bubbles with the channel name left-aligned and unread badge right-aligned. On the T-Deck Pro, it uses a compact vertical list. Select a channel and press Enter (or tap) to switch to it. Press Q or Boot to go back.

\n

The previous A/D cycling behaviour on the channel messages screen has been replaced — A and D now both open the picker. The footer hints have been updated accordingly (A/D:List instead of A/D:Ch).

\n

🌏 Region Scope (MeshCore v1.15+ Compatibility)

\n

Meck now supports region scoping for flood messages, bringing it in line with MeshCore v1.15. Regions limit how far your flood messages propagate through the mesh — when you set a region, outgoing messages are tagged with a transport code that repeaters use to decide whether to forward them. Messages sent without a region reach all repeaters via the default wildcard, same as always.

\n

Device-wide default region: Set a default region in Settings → Default Region (e.g. au-nsw). This applies to all channels and DMs unless a channel has its own override.

\n

Per-channel region: Each channel can have its own region scope. In Settings → Channels, select a channel and press Enter to edit its region. Setting a per-channel region overrides the device default for that channel only.

\n

Serial commands: set region au-nsw, get region, set channel.scope 2 au-syd, get channel.scope 2, get channels (now shows region scope tags). See the Serial Settings Guide for full documentation.

\n

Settings nudge: When exiting settings, if no region is configured anywhere (no device default and no per-channel scopes), a prompt reminds you to consider setting one. You can dismiss it to stay unscoped.

\n

Region names are determined by your local mesh community — check with your local group for the names in use. Common patterns follow ISO 3166 country/subdivision codes (e.g. au f\n…

\n" }, { "version": "v1.6", "name": "Meck v1.6 — Voice Notes Over LoRa, Remote Repeater, Contact Management", "datetime": "2026-03-30T17:08:03Z", "url": "https://github.com/pelgraine/Meck/releases/tag/v1.6", "prerelease": true, "notes": "An update for the T-Deck Pro and T5S3 E-Paper Pro. This release adds voice note recording and playback over LoRa between Meck audio devices (or to any mesh device via the Meck-Mycelium web app), a new remote repeater firmware for managing a MeshCore repeater from anywhere in the world over cellular MQTT, and refined contact export with per-contact selection. Ten firmware variants across both platforms.\r\n\r\n> **📄 Meck_README_v1.6.pdf** is included in this release — it covers all keyboard controls, touch gestures, screen navigation, settings, and feature documentation for both platforms, provided in PDF form for convenience.\r\n\r\n---\r\n\r\n## ⚠️ First-Time Flashing — Read This First\r\n\r\nEach firmware is provided in two formats:\r\n\r\n* **`filename.bin`** — the application firmware only. Use this for **updating** an existing Meck install (including OTA updates from your phone).\r\n* **`filename-merged.bin`** — includes the bootloader, partition table, and application firmware in a single image. **Use this if you are flashing Meck for the first time**, coming from a different firmware, or if your device is not booting correctly after an update.\r\n\r\n**If in doubt, use the `-merged.bin` file.** It will always work regardless of what was previously on the device.\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to **https://flasher.meshcore.co.uk/**\r\n2. Select **Custom Firmware**\r\n3. Load the `.bin` or `-merged.bin` file and click **Flash**\r\n4. Select your device in the popup and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\n```\r\nesptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\r\n```\r\n\r\n---\r\n\r\n## What's New Since v1.5\r\n\r\n### 🎙️ Voice Notes Over LoRa (T-Deck Pro Audio Variant)\r\n\r\nRecord and send voice messages of up to 12 seconds over LoRa — no internet, no cellular, just the mesh. Audio is encoded on-device using Codec2 at 1200 bps, which compresses each second of speech into a single 150-byte LoRa packet. This means voice notes use very little airtime relative to what they deliver — a 5-second message is just 5 packets, and a full 12-second recording is 12 packets.\r\n\r\nVoice notes can be sent to:\r\n\r\n* **Another T-Deck Pro Audio device** — the message is decoded and plays automatically through the headphone jack on receipt. Headphones are recommended as the built-in speaker is very quiet.\r\n* **Any MeshCore companion device** — connect via BLE to the [Meck-Mycelium web app](https://pelgraine.github.io/Meck-Mycelium) in a Chrome browser on your phone. Voice messages appear as tappable playback bubbles in the DM view and play through your phone's speaker.\r\n\r\nVoice notes are sent as direct messages using a pre-set path (direct or multi-hop). The packets are sent with staggered 3-second delays between each one to avoid congesting the channel, so delivery time depends on recording length and your radio preset. For example, on a 62.5 kHz / SF7 preset (e.g. Australia Narrow), a 5-second voice note takes roughly 20 seconds to arrive, and a 12-second recording takes about 42 seconds.\r\n\r\n**How to send a voice note:**\r\n\r\n1. **Set a path for your contact first.** Go to **Contacts** (press **C** from the home screen), scroll to your contact, and press **P** to open the Path Editor. Press **Enter** to select 1-byte or 2-byte path encoding, then use **S** to scroll down and either add repeater hops or set the contact as direct (zero hops). Scroll to **Save & Exit** and press **Enter**.\r\n\r\n2. **Record your message.** Press the **Microphone key** (the zero key on the T-Deck Pro keyboard) to open the Voice Messages screen. Press and **hold** the Microphone key to start recording. **Release** the key to stop. You can record up to 12 seconds.\r\n\r\n3. **Choose a recipient and send.** Press **S** to open the contact picker. Contacts with a direct (zero-hop) path appear at the top of the list for convenience. Tap or scroll to highlight your contact, then press **Enter** to send. A \"Voice sent!\" confirmation will a\n…", "notesHtml": "

An update for the T-Deck Pro and T5S3 E-Paper Pro. This release adds voice note recording and playback over LoRa between Meck audio devices (or to any mesh device via the Meck-Mycelium web app), a new remote repeater firmware for managing a MeshCore repeater from anywhere in the world over cellular MQTT, and refined contact export with per-contact selection. Ten firmware variants across both platforms.

\n
\n

📄 Meck_README_v1.6.pdf is included in this release — it covers all keyboard controls, touch gestures, screen navigation, settings, and feature documentation for both platforms, provided in PDF form for convenience.

\n
\n
\n

⚠️ First-Time Flashing — Read This First

\n

Each firmware is provided in two formats:

\n
    \n
  • filename.bin — the application firmware only. Use this for updating an existing Meck install (including OTA updates from your phone).
    • \n
  • filename-merged.bin — includes the bootloader, partition table, and application firmware in a single image. Use this if you are flashing Meck for the first time, coming from a different firmware, or if your device is not booting correctly after an update.
    • \n
\n

If in doubt, use the -merged.bin file. It will always work regardless of what was previously on the device.

\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.co.uk/
    2. \n
  2. Select Custom Firmware
    3. \n
  3. Load the .bin or -merged.bin file and click Flash
    4. \n
  4. Select your device in the popup and click Connect
    5. \n
\n

Flashing with esptool.py

\n
esptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\n
\n
\n

What's New Since v1.5

\n

🎙️ Voice Notes Over LoRa (T-Deck Pro Audio Variant)

\n

Record and send voice messages of up to 12 seconds over LoRa — no internet, no cellular, just the mesh. Audio is encoded on-device using Codec2 at 1200 bps, which compresses each second of speech into a single 150-byte LoRa packet. This means voice notes use very little airtime relative to what they deliver — a 5-second message is just 5 packets, and a full 12-second recording is 12 packets.

\n

Voice notes can be sent to:

\n
    \n
  • Another T-Deck Pro Audio device — the message is decoded and plays automatically through the headphone jack on receipt. Headphones are recommended as the built-in speaker is very quiet.
    • \n
  • Any MeshCore companion device — connect via BLE to the Meck-Mycelium web app in a Chrome browser on your phone. Voice messages appear as tappable playback bubbles in the DM view and play through your phone's speaker.
    • \n
\n

Voice notes are sent as direct messages using a pre-set path (direct or multi-hop). The packets are sent with staggered 3-second delays between each one to avoid congesting the channel, so delivery time depends on recording length and your radio preset. For example, on a 62.5 kHz / SF7 preset (e.g. Australia Narrow), a 5-second voice note takes roughly 20 seconds to arrive, and a 12-second recording takes about 42 seconds.

\n

How to send a voice note:

\n
    \n

  1. Set a path for your contact first. Go to Contacts (press C from the home screen), scroll to your contact, and press P to open the Path Editor. Press Enter to select 1-byte or 2-byte path encoding, then use S to scroll down and either add repeater hops or set the contact as direct (zero hops). Scroll to Save & Exit and press Enter.

    \n
    2. \n

  2. Record your message. Press the Microphone key (the zero key on the T-Deck Pro keyboard) to open the Voice Messages screen. Press and hold the Microphone key to start recording. Release the key to stop. You can record up to 12 seconds.

    \n
    3. \n

  3. Choose a recipient and send. Press S to open the contact picker. Contacts with a direct (zero-hop) path appear at the top of the list for convenience. Tap or scroll to highlight your contact, then press Enter to send. A \"Voice sent!\" confirmation will a\n…

    \n
    4. \n
\n" }, { "version": "v1.5", "name": "Meck v1.5 — Alarm Clock, Larger Fonts, BLE Speed Boost, OTA Tools & OTA SD File Manager", "datetime": "2026-03-27T14:52:16Z", "url": "https://github.com/pelgraine/Meck/releases/tag/v1.5", "prerelease": true, "notes": "An update for both the T-Deck Pro and T5S3 E-Paper Pro. This release adds an alarm clock app for the audio variant, a user-selectable larger font mode, significantly faster BLE companion contact sync, an OTA SD-based firmware file manager, upstream MeshCore routing fixes, and several bug fixes. Nine firmware variants across both platforms.\r\n\r\n> **📄 Meck\\_README\\_v1.5\\_28\\_March\\_2026.pdf** is included in this release — it covers all keyboard controls, touch gestures, screen navigation, settings, and feature documentation for both platforms.\r\n\r\n---\r\n\r\n## ⚠️ First-Time Flashing — Read This First\r\n\r\nEach firmware is provided in two formats:\r\n\r\n* **`filename.bin`** — the application firmware only. Use this for **updating** an existing Meck install (including OTA updates from your phone).\r\n* **`filename-merged.bin`** — includes the bootloader, partition table, and application firmware in a single image. **Use this if you are flashing Meck for the first time**, coming from a different firmware, or if your device is not booting correctly after an update.\r\n\r\n**If in doubt, use the `-merged.bin` file.** It will always work regardless of what was previously on the device.\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to ****\r\n2. Select **Custom Firmware**\r\n3. Load the `.bin` or `-merged.bin` file and click **Flash**\r\n4. Select your device in the popup and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\n```\r\nesptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\r\n```\r\n\r\n---\r\n\r\n## What's New Since v1.3\r\n\r\n### ⏰ Alarm Clock (T-Deck Pro Audio Variant)\r\n\r\nSet up to five daily alarms that play custom MP3 sounds through the PCM5102A DAC. Alarms trigger even when the device is on other screens or playing an audiobook. A bell icon displays in the home screen UI header bar when the alarm has been set to ON.\r\n\r\n**Setup:**\r\n\r\n1. Place MP3 files (44100 Hz sample rate) in `/alarms/` on the SD card\r\n2. Open the alarm clock from the home screen (press **K**)\r\n3. Select an alarm slot (1–5), set the time, and choose an MP3 file from the list\r\n\r\n**When an alarm fires:**\r\n\r\n* The selected MP3 plays through the headphone jack\r\n* Press **Z** to snooze for 5 minutes\r\n* Press **any other key** to dismiss\r\n\r\nAlarm configuration is stored in `/alarms/.alarmcfg` on the SD card. Alarms persist across reboots — if the RTC has valid time (via GPS or companion app sync), alarms will fire at the correct time after a restart.\r\n\r\n> **Note:** MP3 files should be encoded at **44100 Hz** sample rate. Lower sample rates may cause distortion due to ESP32-S3 I2S hardware limitations (same requirement as the audiobook player).\r\n\r\n\"alarm_clock\"\r\n\r\n### 🔤 Larger Font Mode (T-Deck Pro & T5S3)\r\n\r\nA new display option that increases the text size across channel messages, contacts, the DM inbox, and repeater admin screens. Useful for improved readability, especially on the T-Deck Pro's compact 240×320 display.\r\n\r\nEnable it in **Settings → Larger Font** (toggle on/off). The setting persists across reboots.\r\n\r\n\"IMG_1852\"\r\n\r\n### ⚡ Faster BLE Companion Sync (T-Deck Pro & T5S3)\r\n\r\nBLE contact sync with the companion app is now approximately **twice as fast**. Loading 460 contacts previously took around 30 seconds — it now completes in roughly 15 seconds. The improvement applies to both the T-Deck Pro BLE and T5S3 BLE firmware variants.\r\n\r\n### 📂 OTA Tools: SD File Manager (T-Deck Pro & T5S3)\r\n\r\nThe Settings screen now has an **OTA Tools** submenu containing two utilities: the existing **Firmware Update** and a new **SD File Manager**. The file manager creates a WiFi access point (same as the firmware updater) and serves a browser-based interface where you can \n…", "notesHtml": "

An update for both the T-Deck Pro and T5S3 E-Paper Pro. This release adds an alarm clock app for the audio variant, a user-selectable larger font mode, significantly faster BLE companion contact sync, an OTA SD-based firmware file manager, upstream MeshCore routing fixes, and several bug fixes. Nine firmware variants across both platforms.

\n
\n

📄 Meck_README_v1.5_28_March_2026.pdf is included in this release — it covers all keyboard controls, touch gestures, screen navigation, settings, and feature documentation for both platforms.

\n
\n
\n

⚠️ First-Time Flashing — Read This First

\n

Each firmware is provided in two formats:

\n
    \n
  • filename.bin — the application firmware only. Use this for updating an existing Meck install (including OTA updates from your phone).
    • \n
  • filename-merged.bin — includes the bootloader, partition table, and application firmware in a single image. Use this if you are flashing Meck for the first time, coming from a different firmware, or if your device is not booting correctly after an update.
    • \n
\n

If in doubt, use the -merged.bin file. It will always work regardless of what was previously on the device.

\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.co.uk/
    2. \n
  2. Select Custom Firmware
    3. \n
  3. Load the .bin or -merged.bin file and click Flash
    4. \n
  4. Select your device in the popup and click Connect
    5. \n
\n

Flashing with esptool.py

\n
esptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\n
\n
\n

What's New Since v1.3

\n

⏰ Alarm Clock (T-Deck Pro Audio Variant)

\n

Set up to five daily alarms that play custom MP3 sounds through the PCM5102A DAC. Alarms trigger even when the device is on other screens or playing an audiobook. A bell icon displays in the home screen UI header bar when the alarm has been set to ON.

\n

Setup:

\n
    \n
  1. Place MP3 files (44100 Hz sample rate) in /alarms/ on the SD card
    2. \n
  2. Open the alarm clock from the home screen (press K)
    3. \n
  3. Select an alarm slot (1–5), set the time, and choose an MP3 file from the list
    4. \n
\n

When an alarm fires:

\n
    \n
  • The selected MP3 plays through the headphone jack
    • \n
  • Press Z to snooze for 5 minutes
    • \n
  • Press any other key to dismiss
    • \n
\n

Alarm configuration is stored in /alarms/.alarmcfg on the SD card. Alarms persist across reboots — if the RTC has valid time (via GPS or companion app sync), alarms will fire at the correct time after a restart.

\n
\n

Note: MP3 files should be encoded at 44100 Hz sample rate. Lower sample rates may cause distortion due to ESP32-S3 I2S hardware limitations (same requirement as the audiobook player).

\n
\n\"alarm_clock\"

🔤 Larger Font Mode (T-Deck Pro & T5S3)

\n

A new display option that increases the text size across channel messages, contacts, the DM inbox, and repeater admin screens. Useful for improved readability, especially on the T-Deck Pro's compact 240×320 display.

\n

Enable it in Settings → Larger Font (toggle on/off). The setting persists across reboots.

\n\"IMG_1852\"

⚡ Faster BLE Companion Sync (T-Deck Pro & T5S3)

\n

BLE contact sync with the companion app is now approximately twice as fast. Loading 460 contacts previously took around 30 seconds — it now completes in roughly 15 seconds. The improvement applies to both the T-Deck Pro BLE and T5S3 BLE firmware variants.

\n

📂 OTA Tools: SD File Manager (T-Deck Pro & T5S3)

\n

The Settings screen now has an OTA Tools submenu containing two utilities: the existing Firmware Update and a new SD File Manager. The file manager creates a WiFi access point (same as the firmware updater) and serves a browser-based interface where you can \n…

\n" }, { "version": "ota-1.3", "name": "Meck v1.3 — T-Deck Pro & T5S3 OTA Updates, DM Inbox & Roomserver Fixes", "datetime": "2026-03-23T04:21:31Z", "url": "https://github.com/pelgraine/Meck/releases/tag/ota-1.3", "prerelease": true, "notes": "An update for both the T-Deck Pro and T5S3 E-Paper Pro. This release adds over-the-air firmware update capabilities from your phone or other device, a DM inbox for reading received direct messages, roomserver message handling, and per-contact unread indicators. Nine firmware variants across both platforms.\r\n\r\n> **📄 Meck\\_README\\_v1.3\\_23\\_March\\_2026.pdf** is included in this release — it covers all keyboard controls, touch gestures, screen navigation, settings, and feature documentation for both platforms.\r\n\r\n---\r\n\r\n## ⚠️ First-Time Flashing — Read This First\r\n\r\nEach firmware is provided in two formats:\r\n\r\n* **`filename.bin`** — the application firmware only. Use this for **updating** an existing Meck install (including OTA updates from your phone).\r\n* **`filename-merged.bin`** — includes the bootloader, partition table, and application firmware in a single image. **Use this if you are flashing Meck for the first time**, coming from a different firmware, or if your device is not booting correctly after an update.\r\n\r\n**If in doubt, use the `-merged.bin` file.** It will always work regardless of what was previously on the device.\r\n\r\n> **⚠️ Important:** The merged filename uses a **hyphen** (`-merged.bin`) not an underscore. The MeshCore web flasher uses this suffix to detect merged firmware and flash at the correct address (0x0). Files without `-merged.bin` in the name are written at 0x10000, which will fail on a clean device.\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to ****\r\n2. Select **Custom Firmware**\r\n3. Load the `.bin` or `-merged.bin` file and click **Flash**\r\n4. Select your device in the popup and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\n```\r\nesptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\r\n```\r\n---\r\n\r\n## What's New Since v1.2\r\n\r\n### 📲 OTA Firmware Update (T-Deck Pro & T5S3)\r\n\r\nUpdate your firmware directly from your phone — no computer or serial cable required. The device creates a temporary WiFi access point, and you upload the new firmware via your phone's browser.\r\n\r\n**How it works:**\r\n\r\n1. Download the new `.bin` file to your phone (from GitHub Releases, Discord, etc.)\r\n2. On the device: **Settings → Firmware Update → Enter** (T-Deck Pro) or **tap** (T5S3)\r\n3. The device starts a WiFi network called `Meck-Update-XXXX` and displays the connection details\r\n4. On your phone: connect to the `Meck-Update` WiFi network, open a browser, and go to `192.168.4.1`\r\n5. Tap **Choose File**, select the `.bin`, and tap **Upload**\r\n6. The device receives the file, saves it to SD, verifies the image, flashes it to the inactive partition, and reboots\r\n\r\nTotal time is under 2 minutes. The device's existing partition layout already supports dual OTA partitions — no initial USB reflash is needed. If the new firmware fails to boot, the ESP32 bootloader automatically rolls back to the previous working firmware.\r\n\r\n> **Note:** Use the **non-merged** `.bin` file for OTA updates, not the merged binary. The merged binary includes the bootloader and partition table, which are only needed for first-time USB flashing.\r\n\r\n### 💬 DM Inbox (T-Deck Pro & T5S3)\r\n\r\nReceived direct messages can now be viewed on-device. Previously, DMs were only visible as a brief toast notification and then disappeared — there was no way to go back and read them.\r\n\r\n* **T-Deck Pro:** Press **D** past the last channel on the Channel Messages screen to reach the DM inbox. Press **A** to return to group channels.\r\n* **T5S3:** Swipe left past the last channel on the Channel Messages screen to reach the DM inbox. Swipe right to return to group channels.\r\n\r\nThe DM inbox shows all received direct messages with sender name and timestamp, sorted by arrival order. Entering the DM inbox automatically marks all DM messages as read.\r\n\r\n### ✉️ Per-Contact DM Unread Indicator (T-Deck Pro & T5S3)\r\n\r\nContacts with unread direct messages now show a `*` marker next to their name i\n…", "notesHtml": "

An update for both the T-Deck Pro and T5S3 E-Paper Pro. This release adds over-the-air firmware update capabilities from your phone or other device, a DM inbox for reading received direct messages, roomserver message handling, and per-contact unread indicators. Nine firmware variants across both platforms.

\n
\n

📄 Meck_README_v1.3_23_March_2026.pdf is included in this release — it covers all keyboard controls, touch gestures, screen navigation, settings, and feature documentation for both platforms.

\n
\n
\n

⚠️ First-Time Flashing — Read This First

\n

Each firmware is provided in two formats:

\n
    \n
  • filename.bin — the application firmware only. Use this for updating an existing Meck install (including OTA updates from your phone).
    • \n
  • filename-merged.bin — includes the bootloader, partition table, and application firmware in a single image. Use this if you are flashing Meck for the first time, coming from a different firmware, or if your device is not booting correctly after an update.
    • \n
\n

If in doubt, use the -merged.bin file. It will always work regardless of what was previously on the device.

\n
\n

⚠️ Important: The merged filename uses a hyphen (-merged.bin) not an underscore. The MeshCore web flasher uses this suffix to detect merged firmware and flash at the correct address (0x0). Files without -merged.bin in the name are written at 0x10000, which will fail on a clean device.

\n
\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.co.uk/
    2. \n
  2. Select Custom Firmware
    3. \n
  3. Load the .bin or -merged.bin file and click Flash
    4. \n
  4. Select your device in the popup and click Connect
    5. \n
\n

Flashing with esptool.py

\n
esptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\n
\n
\n

What's New Since v1.2

\n

📲 OTA Firmware Update (T-Deck Pro & T5S3)

\n

Update your firmware directly from your phone — no computer or serial cable required. The device creates a temporary WiFi access point, and you upload the new firmware via your phone's browser.

\n

How it works:

\n
    \n
  1. Download the new .bin file to your phone (from GitHub Releases, Discord, etc.)
    2. \n
  2. On the device: Settings → Firmware Update → Enter (T-Deck Pro) or tap (T5S3)
    3. \n
  3. The device starts a WiFi network called Meck-Update-XXXX and displays the connection details
    4. \n
  4. On your phone: connect to the Meck-Update WiFi network, open a browser, and go to 192.168.4.1
    5. \n
  5. Tap Choose File, select the .bin, and tap Upload
    6. \n
  6. The device receives the file, saves it to SD, verifies the image, flashes it to the inactive partition, and reboots
    7. \n
\n

Total time is under 2 minutes. The device's existing partition layout already supports dual OTA partitions — no initial USB reflash is needed. If the new firmware fails to boot, the ESP32 bootloader automatically rolls back to the previous working firmware.

\n
\n

Note: Use the non-merged .bin file for OTA updates, not the merged binary. The merged binary includes the bootloader and partition table, which are only needed for first-time USB flashing.

\n
\n

💬 DM Inbox (T-Deck Pro & T5S3)

\n

Received direct messages can now be viewed on-device. Previously, DMs were only visible as a brief toast notification and then disappeared — there was no way to go back and read them.

\n
    \n
  • T-Deck Pro: Press D past the last channel on the Channel Messages screen to reach the DM inbox. Press A to return to group channels.
    • \n
  • T5S3: Swipe left past the last channel on the Channel Messages screen to reach the DM inbox. Swipe right to return to group channels.
    • \n
\n

The DM inbox shows all received direct messages with sender name and timestamp, sorted by arrival order. Entering the DM inbox automatically marks all DM messages as read.

\n

✉️ Per-Contact DM Unread Indicator (T-Deck Pro & T5S3)

\n

Contacts with unread direct messages now show a * marker next to their name i\n…

\n" }, { "version": "v1.2", "name": "Meck v1.2 — T-Deck Pro & T5S3 Update & Bugfixes", "datetime": "2026-03-20T10:41:27Z", "url": "https://github.com/pelgraine/Meck/releases/tag/v1.2", "prerelease": true, "notes": "An update for both the T-Deck Pro and T5S3 E-Paper Pro. New features include a lock screen, last heard advert list, touch tap-to-select across all list screens, non-blocking contact saves, and CardKB external keyboard support for the T5S3. Nine firmware variants across both platforms.\r\n\r\n> **📄 Meck_README_v1.2_March_2026.pdf** is included in this release — it covers all keyboard controls, touch gestures, screen navigation, settings, and feature documentation for both platforms.\r\n\r\n---\r\n\r\n## ⚠️ First-Time Flashing — Read This First\r\n\r\nEach firmware is provided in two formats:\r\n\r\n* **`filename.bin`** — the application firmware only. Use this for **updating** an existing Meck install.\r\n* **`filename-merged.bin`** — includes the bootloader, partition table, and application firmware in a single image. **Use this if you are flashing Meck for the first time**, coming from a different firmware, or if your device is not booting correctly after an update.\r\n\r\n**If in doubt, use the `-merged.bin` file.** It will always work regardless of what was previously on the device.\r\n\r\n> **⚠️ Important:** The merged filename now uses a **hyphen** (`-merged.bin`) instead of an underscore. The MeshCore web flasher uses this suffix to detect merged firmware and flash at the correct address (0x0). Files without `-merged.bin` in the name are written at 0x10000, which will fail on a clean device.\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to **https://flasher.meshcore.co.uk**\r\n2. Select **Custom Firmware**\r\n3. Load the `.bin` or `-merged.bin` file and click **Flash**\r\n4. Select your device in the popup and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\n```\r\nesptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\r\n```\r\n\r\n> **Note:** On first boot after a fresh flash (or after erasing flash), you may see a SPIFFS mount error in serial output — this is normal. The filesystem auto-formats on first boot and everything proceeds as expected.\r\n\r\n---\r\n\r\n## What's New Since v1.1\r\n\r\n### 🔒 Lock Screen (T-Deck Pro & T5S3)\r\n\r\nBoth platforms now have a lock screen that shows the current time, battery percentage, and unread message count.\r\n\r\n* **T-Deck Pro:** Double-click the Boot button to lock/unlock\r\n* **T5S3:** Long press the Boot button to lock/unlock\r\n\r\nAn auto-lock timer is available in **Settings → Auto Lock** with options for None, 2, 5, 10, 15, or 30 minutes of idle time. The CPU drops to 40 MHz while locked to reduce power consumption. The clock refreshes every 15 minutes while locked.\r\n\r\n### 📡 Last Heard Screen (T-Deck Pro & T5S3)\r\n\r\nA new passive advert list showing all recently heard nodes sorted by recency. Unlike Discovery (which does an active zero-hop scan), Last Heard is purely passive — it shows nodes whose adverts have been received over time.\r\n\r\n* Press **H** from the home screen (T-Deck Pro) or swipe to the Recent Adverts home page and tap \"Tap here for full Last Heard list\" (T5S3)\r\n* Shows node type, name, time since last heard, hop count\r\n* Nodes already in contacts are marked with `[+]`, favourites with `[★]`\r\n* Add or remove contacts directly from the list\r\n\r\n### 👆 Tap-to-Select (T-Deck Pro & T5S3)\r\n\r\nTap on any row in Contacts, Discovery, Last Heard, Settings, Text Reader file list, and Notes to select it. Tap the same row again (or press Enter) to activate. This brings touch interaction to the T-Deck Pro for the first time on list screens.\r\n\r\n### 💾 Non-Blocking Contact Save\r\n\r\nLarge contact lists previously blocked the main loop for 500ms+ during save. Contact saves now happen in chunks across multiple loop iterations (20 contacts per chunk, ~30ms each). A write-then-verify-then-rename pattern prevents corruption if the save is interrupted.\r\n\r\n### ⌨️ CardKB Support (T5S3)\r\n\r\nThe T5S3 now supports the M5Stack CardKB (or compatible I2C keyboard) connected via the QWIIC port. When detected at boot, the CardKB can be used for all text input — composing messages, entering URLs, editing \n…", "notesHtml": "

An update for both the T-Deck Pro and T5S3 E-Paper Pro. New features include a lock screen, last heard advert list, touch tap-to-select across all list screens, non-blocking contact saves, and CardKB external keyboard support for the T5S3. Nine firmware variants across both platforms.

\n
\n

📄 Meck_README_v1.2_March_2026.pdf is included in this release — it covers all keyboard controls, touch gestures, screen navigation, settings, and feature documentation for both platforms.

\n
\n
\n

⚠️ First-Time Flashing — Read This First

\n

Each firmware is provided in two formats:

\n
    \n
  • filename.bin — the application firmware only. Use this for updating an existing Meck install.
    • \n
  • filename-merged.bin — includes the bootloader, partition table, and application firmware in a single image. Use this if you are flashing Meck for the first time, coming from a different firmware, or if your device is not booting correctly after an update.
    • \n
\n

If in doubt, use the -merged.bin file. It will always work regardless of what was previously on the device.

\n
\n

⚠️ Important: The merged filename now uses a hyphen (-merged.bin) instead of an underscore. The MeshCore web flasher uses this suffix to detect merged firmware and flash at the correct address (0x0). Files without -merged.bin in the name are written at 0x10000, which will fail on a clean device.

\n
\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.co.uk
    2. \n
  2. Select Custom Firmware
    3. \n
  3. Load the .bin or -merged.bin file and click Flash
    4. \n
  4. Select your device in the popup and click Connect
    5. \n
\n

Flashing with esptool.py

\n
esptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware-merged.bin\n
\n
\n

Note: On first boot after a fresh flash (or after erasing flash), you may see a SPIFFS mount error in serial output — this is normal. The filesystem auto-formats on first boot and everything proceeds as expected.

\n
\n
\n

What's New Since v1.1

\n

🔒 Lock Screen (T-Deck Pro & T5S3)

\n

Both platforms now have a lock screen that shows the current time, battery percentage, and unread message count.

\n
    \n
  • T-Deck Pro: Double-click the Boot button to lock/unlock
    • \n
  • T5S3: Long press the Boot button to lock/unlock
    • \n
\n

An auto-lock timer is available in Settings → Auto Lock with options for None, 2, 5, 10, 15, or 30 minutes of idle time. The CPU drops to 40 MHz while locked to reduce power consumption. The clock refreshes every 15 minutes while locked.

\n

📡 Last Heard Screen (T-Deck Pro & T5S3)

\n

A new passive advert list showing all recently heard nodes sorted by recency. Unlike Discovery (which does an active zero-hop scan), Last Heard is purely passive — it shows nodes whose adverts have been received over time.

\n
    \n
  • Press H from the home screen (T-Deck Pro) or swipe to the Recent Adverts home page and tap \"Tap here for full Last Heard list\" (T5S3)
    • \n
  • Shows node type, name, time since last heard, hop count
    • \n
  • Nodes already in contacts are marked with [+], favourites with [★]
    • \n
  • Add or remove contacts directly from the list
    • \n
\n

👆 Tap-to-Select (T-Deck Pro & T5S3)

\n

Tap on any row in Contacts, Discovery, Last Heard, Settings, Text Reader file list, and Notes to select it. Tap the same row again (or press Enter) to activate. This brings touch interaction to the T-Deck Pro for the first time on list screens.

\n

💾 Non-Blocking Contact Save

\n

Large contact lists previously blocked the main loop for 500ms+ during save. Contact saves now happen in chunks across multiple loop iterations (20 contacts per chunk, ~30ms each). A write-then-verify-then-rename pattern prevents corruption if the save is interrupted.

\n

⌨️ CardKB Support (T5S3)

\n

The T5S3 now supports the M5Stack CardKB (or compatible I2C keyboard) connected via the QWIIC port. When detected at boot, the CardKB can be used for all text input — composing messages, entering URLs, editing \n…

\n" }, { "version": "tdpro-v1.1", "name": "Meck v1.1 — T-Deck Pro Update", "datetime": "2026-03-15T04:46:27Z", "url": "https://github.com/pelgraine/Meck/releases/tag/tdpro-v1.1", "prerelease": true, "notes": "A T-Deck Pro–only update with settings screen improvements, GPS fixes, and a new 2000mAh 4G standalone variant. Eight firmware variants for the T-Deck Pro — the T5S3 E-Paper Pro remains on [v1.0](https://github.com/pelgraine/Meck/releases/tag/v1.0) for now.\r\n\r\n> **📄 Meck_Firmware_Guide — 15 March 2026.pdf** is included in this release for easy reference — it covers all keyboard controls, screen navigation, settings, and feature documentation for both platforms.\r\n\r\n> **📦 Convenience ZIP:** `v1.1-Meck-T-Deck-Pro-firmware.zip` bundles all T-Deck Pro variants into a single download.\r\n\r\n---\r\n\r\n## ⚠️ First-Time Flashing — Read This First\r\n\r\nEach firmware is provided in two formats:\r\n\r\n* **`filename.bin`** — the application firmware only. Use this for **updating** an existing Meck install.\r\n* **`filename_merged.bin`** — includes the bootloader, partition table, and application firmware in a single image. **Use this if you are flashing Meck for the first time**, coming from a different firmware, or if your device is not booting correctly after an update.\r\n\r\n**If in doubt, use the `_merged.bin` file.** It will always work regardless of what was previously on the device.\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to **https://flasher.meshcore.co.uk**\r\n2. Select **Custom Firmware**\r\n3. Load the `.bin` or `_merged.bin` file and click **Flash**\r\n4. Select your device in the popup and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\nIf you prefer the command line, `esptool.py` can be used to flash firmware directly. First-time users should use the `_merged.bin` which includes everything the device needs to boot:\r\n\r\n```\r\nesptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware_merged.bin\r\n```\r\n\r\n> **Note:** On first boot after a fresh flash (or after erasing flash), you may see a SPIFFS mount error in serial output — this is normal. The filesystem auto-formats on first boot and everything proceeds as expected.\r\n\r\n---\r\n\r\n## What's New Since v1.0\r\n\r\n### ⚙️ Settings Screen Reorganisation\r\n\r\nThe settings screen has been restructured for clarity. Contacts and Channels are now in their own sub-screens instead of being listed inline:\r\n\r\n* **Contacts >>** — opens a dedicated sub-screen for the contact auto-add mode picker (Auto All / Custom / Manual) and per-type toggles\r\n* **Channels >>** — opens a dedicated sub-screen for viewing, adding, and deleting channels\r\n\r\nPress **Enter** to open a sub-screen and **Q** to return to the top-level settings list. Your cursor position is remembered when navigating back.\r\n\r\n### 📡 GPS Baud Rate in Settings\r\n\r\nThe GPS baud rate can now be changed on-screen in Settings (previously serial-only). Cycle through options with **A / D** — available rates are Default (38400), 4800, 9600, 19200, 38400, 57600, and 115200. Requires a reboot to take effect.\r\n\r\n### 🔢 Frequency Text Entry\r\n\r\nThe frequency setting now uses direct text entry instead of increment/decrement. Type the exact value (e.g. `916.575`) and press **Enter** to confirm — much faster for precise tuning.\r\n\r\n### 🛰️ GPS Initialisation Fix\r\n\r\nFixed a bug where `Serial1` (used by the sensor library's GPS init) was not properly released before reinitialising `Serial2` for the GPS stream. This could cause GPS to silently fail to receive data on some boots. The fix ensures `Serial1.end()` is called before `Serial2.begin()`, cleanly handing the UART pins back to the GPS parser.\r\n\r\n### 🔧 Preferences Validation on Upgrade\r\n\r\nWhen upgrading from older firmware versions, stored preferences may contain garbage values in fields that didn't exist before. v1.1 now clamps invalid values on boot — `path_hash_mode`, `dark_mode`, `portrait_mode`, `autoadd_max_hops`, and `interference_threshold` are all validated and reset to safe defaults if out of range. This prevents unexpected behaviour after a firmware upgrade without erasing flash.\r\n\r\n---\r\n\r\n## T-Deck Pro Firmware Variants\r\n\r\nSix firmware variants for the LilyGo T-Deck Pro. Pi\n…", "notesHtml": "

A T-Deck Pro–only update with settings screen improvements, GPS fixes, and a new 2000mAh 4G standalone variant. Eight firmware variants for the T-Deck Pro — the T5S3 E-Paper Pro remains on v1.0 for now.

\n
\n

📄 Meck_Firmware_Guide — 15 March 2026.pdf is included in this release for easy reference — it covers all keyboard controls, screen navigation, settings, and feature documentation for both platforms.

\n
\n
\n

📦 Convenience ZIP: v1.1-Meck-T-Deck-Pro-firmware.zip bundles all T-Deck Pro variants into a single download.

\n
\n
\n

⚠️ First-Time Flashing — Read This First

\n

Each firmware is provided in two formats:

\n
    \n
  • filename.bin — the application firmware only. Use this for updating an existing Meck install.
    • \n
  • filename_merged.bin — includes the bootloader, partition table, and application firmware in a single image. Use this if you are flashing Meck for the first time, coming from a different firmware, or if your device is not booting correctly after an update.
    • \n
\n

If in doubt, use the _merged.bin file. It will always work regardless of what was previously on the device.

\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.co.uk
    2. \n
  2. Select Custom Firmware
    3. \n
  3. Load the .bin or _merged.bin file and click Flash
    4. \n
  4. Select your device in the popup and click Connect
    5. \n
\n

Flashing with esptool.py

\n

If you prefer the command line, esptool.py can be used to flash firmware directly. First-time users should use the _merged.bin which includes everything the device needs to boot:

\n
esptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware_merged.bin\n
\n
\n

Note: On first boot after a fresh flash (or after erasing flash), you may see a SPIFFS mount error in serial output — this is normal. The filesystem auto-formats on first boot and everything proceeds as expected.

\n
\n
\n

What's New Since v1.0

\n

⚙️ Settings Screen Reorganisation

\n

The settings screen has been restructured for clarity. Contacts and Channels are now in their own sub-screens instead of being listed inline:

\n
    \n
  • Contacts >> — opens a dedicated sub-screen for the contact auto-add mode picker (Auto All / Custom / Manual) and per-type toggles
    • \n
  • Channels >> — opens a dedicated sub-screen for viewing, adding, and deleting channels
    • \n
\n

Press Enter to open a sub-screen and Q to return to the top-level settings list. Your cursor position is remembered when navigating back.

\n

📡 GPS Baud Rate in Settings

\n

The GPS baud rate can now be changed on-screen in Settings (previously serial-only). Cycle through options with A / D — available rates are Default (38400), 4800, 9600, 19200, 38400, 57600, and 115200. Requires a reboot to take effect.

\n

🔢 Frequency Text Entry

\n

The frequency setting now uses direct text entry instead of increment/decrement. Type the exact value (e.g. 916.575) and press Enter to confirm — much faster for precise tuning.

\n

🛰️ GPS Initialisation Fix

\n

Fixed a bug where Serial1 (used by the sensor library's GPS init) was not properly released before reinitialising Serial2 for the GPS stream. This could cause GPS to silently fail to receive data on some boots. The fix ensures Serial1.end() is called before Serial2.begin(), cleanly handing the UART pins back to the GPS parser.

\n

🔧 Preferences Validation on Upgrade

\n

When upgrading from older firmware versions, stored preferences may contain garbage values in fields that didn't exist before. v1.1 now clamps invalid values on boot — path_hash_mode, dark_mode, portrait_mode, autoadd_max_hops, and interference_threshold are all validated and reset to safe defaults if out of range. This prevents unexpected behaviour after a firmware upgrade without erasing flash.

\n
\n

T-Deck Pro Firmware Variants

\n

Six firmware variants for the LilyGo T-Deck Pro. Pi\n…

\n" }, { "version": "v1.0", "name": "Meck v1.0 — Unified Release for T-Deck Pro & T5S3 E-Paper Pro", "datetime": "2026-03-13T12:47:04Z", "url": "https://github.com/pelgraine/Meck/releases/tag/v1.0", "prerelease": true, "notes": "The first combined release covering both supported hardware platforms. Ten firmware variants across two devices, one codebase.\r\n\r\n> **📄 Meck v1.0 Readme Guide - March 2026.pdf** is included in this release for easy reference — it covers all keyboard controls, screen navigation, settings, and feature documentation for both platforms.\r\n\r\n> **📦 Convenience ZIPs:** `v1.0-Meck-T-Deck-Pro-firmware.zip` and `v1.0-Meck-T5S3-firmware.zip` bundle all variants for each platform into a single download.\r\n\r\n---\r\n\r\n## ⚠️ First-Time Flashing — Read This First\r\n\r\nEach firmware is provided in two formats:\r\n\r\n- **`filename.bin`** — the application firmware only. Use this for **updating** an existing Meck install.\r\n- **`filename_merged.bin`** — includes the bootloader, partition table, and application firmware in a single image. **Use this if you are flashing Meck for the first time**, coming from a different firmware, or if your device is not booting correctly after an update.\r\n\r\n**If in doubt, use the `_merged.bin` file.** It will always work regardless of what was previously on the device.\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to **https://flasher.meshcore.co.uk**\r\n2. Select **Custom Firmware**\r\n3. Load the `.bin` or `_merged.bin` file and click **Flash**\r\n4. Select your device in the popup and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\nIf you prefer the command line, `esptool.py` can be used to flash firmware directly. First-time users should use the `_merged.bin` which includes everything the device needs to boot:\r\n\r\n```\r\nesptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware_merged.bin\r\n```\r\n\r\n> **Note:** On first boot after a fresh flash (or after erasing flash), you may see a SPIFFS mount error in serial output — this is normal. The filesystem auto-formats on first boot and everything proceeds as expected.\r\n\r\n---\r\n\r\n## What's New Since v0.9.8 (T-Deck Pro)\r\n\r\n### 🔗 Multibyte Path Hash Support\r\n\r\nMeck now supports MeshCore v1.14's multibyte path hash mode, which significantly reduces hash collisions in larger networks. You can choose the path hash size in the Settings screen (press **S** from the home screen) or set it via USB serial with `set path.hash.mode {0,1,2}`.\r\n\r\n| Mode | Bytes/hop | Max hops | Notes |\r\n|------|-----------|----------|-------|\r\n| 0 | 1 | 64 | Legacy — prone to hash collisions in larger networks |\r\n| 1 | 2 | 32 | Recommended — effectively eliminates collisions |\r\n| 2 | 3 | 21 | Maximum precision, rarely needed |\r\n\r\nNodes with different modes coexist on the same network — the mode only affects packets your node originates. Read more about what this means in practice: https://buymeacoffee.com/ripplebiz/path-diagnostics-improvements\r\n\r\n### 🌑 Dark Mode (T-Deck Pro & T5S3)\r\n\r\nDark mode is now available on the T-Deck Pro as well as the T5S3. Toggle it in Settings to invert the display — white text on a black background. The setting persists across reboots.\r\n\r\n\"IMG_1649\"\r\n\r\n### 📡 Mesh Tuning via Serial CLI\r\n\r\nNew serial commands for advanced mesh tuning — all configurable over USB without needing to recompile:\r\n\r\n* **`rxdelay`** — SNR-based flood delay (0–20, 0=disabled). Stronger signals processed first; weaker copies delayed and typically discarded as duplicates. Values below 1.0 have no practical effect. See the [MeshSydney wiki](https://meshsydney.com/wiki) for tuning profiles.\r\n* **`af`** — Airtime factor (0–9, default 1.0). Adjusts internal timing windows. Keep consistent across nodes in your mesh.\r\n* **`multi.acks`** — Redundant ACKs for direct messages (0 or 1, **default changed to 1**). Sends two ACKs instead of one for improved delivery confirmation.\r\n* **`int.thresh`** — Interference threshold in dB (0=disabled, 14+=enabled). Scans channel activity before transmitting. Adds ~4s receive delay per packet — only recommended for high RF in\n…", "notesHtml": "

The first combined release covering both supported hardware platforms. Ten firmware variants across two devices, one codebase.

\n
\n

📄 Meck v1.0 Readme Guide - March 2026.pdf is included in this release for easy reference — it covers all keyboard controls, screen navigation, settings, and feature documentation for both platforms.

\n
\n
\n

📦 Convenience ZIPs: v1.0-Meck-T-Deck-Pro-firmware.zip and v1.0-Meck-T5S3-firmware.zip bundle all variants for each platform into a single download.

\n
\n
\n

⚠️ First-Time Flashing — Read This First

\n

Each firmware is provided in two formats:

\n
    \n
  • filename.bin — the application firmware only. Use this for updating an existing Meck install.
    • \n
  • filename_merged.bin — includes the bootloader, partition table, and application firmware in a single image. Use this if you are flashing Meck for the first time, coming from a different firmware, or if your device is not booting correctly after an update.
    • \n
\n

If in doubt, use the _merged.bin file. It will always work regardless of what was previously on the device.

\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.co.uk
    2. \n
  2. Select Custom Firmware
    3. \n
  3. Load the .bin or _merged.bin file and click Flash
    4. \n
  4. Select your device in the popup and click Connect
    5. \n
\n

Flashing with esptool.py

\n

If you prefer the command line, esptool.py can be used to flash firmware directly. First-time users should use the _merged.bin which includes everything the device needs to boot:

\n
esptool.py --port /dev/ttyACM0 --baud 921600 write_flash 0x0 firmware_merged.bin\n
\n
\n

Note: On first boot after a fresh flash (or after erasing flash), you may see a SPIFFS mount error in serial output — this is normal. The filesystem auto-formats on first boot and everything proceeds as expected.

\n
\n
\n

What's New Since v0.9.8 (T-Deck Pro)

\n

🔗 Multibyte Path Hash Support

\n

Meck now supports MeshCore v1.14's multibyte path hash mode, which significantly reduces hash collisions in larger networks. You can choose the path hash size in the Settings screen (press S from the home screen) or set it via USB serial with set path.hash.mode {0,1,2}.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
ModeBytes/hopMax hopsNotes
0164Legacy — prone to hash collisions in larger networks
1232Recommended — effectively eliminates collisions
2321Maximum precision, rarely needed
\n

Nodes with different modes coexist on the same network — the mode only affects packets your node originates. Read more about what this means in practice: https://buymeacoffee.com/ripplebiz/path-diagnostics-improvements

\n

🌑 Dark Mode (T-Deck Pro & T5S3)

\n

Dark mode is now available on the T-Deck Pro as well as the T5S3. Toggle it in Settings to invert the display — white text on a black background. The setting persists across reboots.

\n\"IMG_1649\"

📡 Mesh Tuning via Serial CLI

\n

New serial commands for advanced mesh tuning — all configurable over USB without needing to recompile:

\n
    \n
  • rxdelay — SNR-based flood delay (0–20, 0=disabled). Stronger signals processed first; weaker copies delayed and typically discarded as duplicates. Values below 1.0 have no practical effect. See the MeshSydney wiki for tuning profiles.
    • \n
  • af — Airtime factor (0–9, default 1.0). Adjusts internal timing windows. Keep consistent across nodes in your mesh.
    • \n
  • multi.acks — Redundant ACKs for direct messages (0 or 1, default changed to 1). Sends two ACKs instead of one for improved delivery confirmation.
    • \n
  • int.thresh — Interference threshold in dB (0=disabled, 14+=enabled). Scans channel activity before transmitting. Adds ~4s receive delay per packet — only recommended for high RF in\n…
    • \n
\n" }, { "version": "t5s3-1", "name": "Meck v1.0 - Community Firmware Builds for the LilyGo T5S3 E-Paper Pro H752-01B (NO GPS)", "datetime": "2026-03-12T12:59:32Z", "url": "https://github.com/pelgraine/Meck/releases/tag/t5s3-1", "prerelease": true, "notes": "### _*THIS FIRMWARE WILL NOT WORK IF YOUR LILYGO T5 E-PAPER S3 PRO HAS GPS*_\r\n\r\nMore details to follow on how to use it, but it's pretty self-explanatory once you flash the firmware. Takes a little bit to get used to the swipe-drag motion for scrolling through menu options.\r\n\r\nUsual Meck Wifi and BLE companion modes, now with Dark Mode and Portrait Mode for the T5S3. \r\n\r\n- Double click the Boot button to turn the backlight on or off. \r\n- Triple click the Boot button to turn on low-brightness backlight for night reading. \r\n- Hold down the boot button for a long press (3+ seconds) to activate the lock screen. \r\n\r\nNo maps in this one as there's no GPS. Time is set when you link to the Meshcore app on your phone or computer, either via wifi or BLE. The RTC will keep the time after that first pairing.", "notesHtml": "

THIS FIRMWARE WILL NOT WORK IF YOUR LILYGO T5 E-PAPER S3 PRO HAS GPS

\n

More details to follow on how to use it, but it's pretty self-explanatory once you flash the firmware. Takes a little bit to get used to the swipe-drag motion for scrolling through menu options.

\n

Usual Meck Wifi and BLE companion modes, now with Dark Mode and Portrait Mode for the T5S3.

\n
    \n
  • Double click the Boot button to turn the backlight on or off.
    • \n
  • Triple click the Boot button to turn on low-brightness backlight for night reading.
    • \n
  • Hold down the boot button for a long press (3+ seconds) to activate the lock screen.
    • \n
\n

No maps in this one as there's no GPS. Time is set when you link to the Meshcore app on your phone or computer, either via wifi or BLE. The RTC will keep the time after that first pairing.

\n" }, { "version": "multi-byte-1", "name": "Meck v0.9.9 - multibyte path hash support!", "datetime": "2026-03-06T18:26:10Z", "url": "https://github.com/pelgraine/Meck/releases/tag/multi-byte-1", "prerelease": true, "notes": "---\r\n\r\n## What's New Since v0.9.8\r\n\r\nMultibyte path hash support to bring Meck in line with recent updates in Meshcore firmware v1.14. You can now choose the path hash size in the T-Deck Pro device settings (via the S key from the home screen) or set it via serial over USB to your T-Deck Pro with `set path.hash.mode {0,1,2}`\r\n\r\nRead a run-down on what multibyte path hash implementation means: [https://buymeacoffee.com/ripplebiz/path-diagnostics-improvements](https://buymeacoffee.com/ripplebiz/path-diagnostics-improvements)\r\n\r\n---\r\n\r\nSix firmware variants, one codebase. Pick the right `.bin` for your hardware:\r\n\r\n---\r\n\r\n## Firmware Variants\r\n\r\n**`v0.9.9-Meck-4G-BLE.bin`**\r\nFor T-Deck Pro 4G boards. Full-featured build — messaging, contacts, direct messages, repeater admin, e-book reader, notes, emoji, GPS, map viewer, BLE companion app support, SMS & Phone app, IRC client, and web browser. Up to 500 contacts and 20 channels.\r\n\r\n> Note: BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.\r\n\r\n**`v0.9.9W-Meck-4G-WiFi.bin`**\r\nFor T-Deck Pro 4G boards. Same as the 4G-BLE build but with WiFi replacing BLE as the companion transport — connect via the MeshCore web app, iOS/Android app, meshcore.js, or Python CLI over your local network (TCP port 5000). WiFi is on by default at boot but can be toggled off in Settings to save power. No BLE companion app support. Up to **1,500 contacts** and 20 channels.\r\n\r\nAlso available for those with a custom 2000mah battery build.\r\n\r\n**`v0.9.9-4G.SA-Meck-standalone.bin`**\r\nFor T-Deck Pro 4G boards. No BLE or WiFi companion — maximum battery life. The web browser, IRC client, and map viewer are all still available (they use WiFi independently, not as a companion transport). Up to 1,500 contacts and 20 channels.\r\n\r\n**`v0.9.9A-Meck-Audio-BLE.bin`**\r\nEverything in the 4G-BLE build plus the audiobook player, sleep timer, and auto-queuing — minus the 4G modem features. BLE companion support included. Up to 500 contacts and 20 channels.\r\n\r\n> ⚠️ PCM5102A audio hardware only. The I2S audio pins (GPIO 7, 8, 9) conflict with the A7682E modem control lines — do not flash on 4G boards.\r\n\r\n> Note: BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.\r\n\r\n**`v0.9.9AW-Meck-Audio-WiFi.bin`**\r\nSame as the Audio-BLE build but with WiFi replacing BLE as the companion transport. WiFi is on by default at boot but can be toggled off in Settings to save power. No BLE companion app support. Up to **1,500 contacts** and 20 channels.\r\n\r\n> ⚠️ PCM5102A audio hardware only — same GPIO conflict applies. Do not flash on 4G boards.\r\n\r\n**`v0.9.9A-SA-Meck-standalone.bin`**\r\nSame as the Audio-BLE build but with Bluetooth and WiFi completely removed at compile time. The radio hardware is never initialised, giving a significant battery life improvement. The web browser, IRC client, and map viewer are not available on this variant. Up to 1,500 contacts and 20 channels.\r\n\r\n> Battery life: Disabling Bluetooth extends estimated runtime from ~10.5 hours to ~20.5 hours on the 1400mAh cell.\r\n\r\n> ⚠️ PCM5102A audio hardware only — do not flash on 4G boards.\r\n\r\n---\r\n\r\nSee all the features and updates that are available in Meck from v0.9.8 onwards here: [https://github.com/pelgraine/Meck/releases/tag/wifi-1](https://github.com/pelgraine/Meck/releases/tag/wifi-1)", "notesHtml": "
\n

What's New Since v0.9.8

\n

Multibyte path hash support to bring Meck in line with recent updates in Meshcore firmware v1.14. You can now choose the path hash size in the T-Deck Pro device settings (via the S key from the home screen) or set it via serial over USB to your T-Deck Pro with set path.hash.mode {0,1,2}

\n

Read a run-down on what multibyte path hash implementation means: https://buymeacoffee.com/ripplebiz/path-diagnostics-improvements

\n
\n

Six firmware variants, one codebase. Pick the right .bin for your hardware:

\n
\n

Firmware Variants

\n

v0.9.9-Meck-4G-BLE.bin\nFor T-Deck Pro 4G boards. Full-featured build — messaging, contacts, direct messages, repeater admin, e-book reader, notes, emoji, GPS, map viewer, BLE companion app support, SMS & Phone app, IRC client, and web browser. Up to 500 contacts and 20 channels.

\n
\n

Note: BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.

\n
\n

v0.9.9W-Meck-4G-WiFi.bin\nFor T-Deck Pro 4G boards. Same as the 4G-BLE build but with WiFi replacing BLE as the companion transport — connect via the MeshCore web app, iOS/Android app, meshcore.js, or Python CLI over your local network (TCP port 5000). WiFi is on by default at boot but can be toggled off in Settings to save power. No BLE companion app support. Up to 1,500 contacts and 20 channels.

\n

Also available for those with a custom 2000mah battery build.

\n

v0.9.9-4G.SA-Meck-standalone.bin\nFor T-Deck Pro 4G boards. No BLE or WiFi companion — maximum battery life. The web browser, IRC client, and map viewer are all still available (they use WiFi independently, not as a companion transport). Up to 1,500 contacts and 20 channels.

\n

v0.9.9A-Meck-Audio-BLE.bin\nEverything in the 4G-BLE build plus the audiobook player, sleep timer, and auto-queuing — minus the 4G modem features. BLE companion support included. Up to 500 contacts and 20 channels.

\n
\n

⚠️ PCM5102A audio hardware only. The I2S audio pins (GPIO 7, 8, 9) conflict with the A7682E modem control lines — do not flash on 4G boards.

\n
\n
\n

Note: BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.

\n
\n

v0.9.9AW-Meck-Audio-WiFi.bin\nSame as the Audio-BLE build but with WiFi replacing BLE as the companion transport. WiFi is on by default at boot but can be toggled off in Settings to save power. No BLE companion app support. Up to 1,500 contacts and 20 channels.

\n
\n

⚠️ PCM5102A audio hardware only — same GPIO conflict applies. Do not flash on 4G boards.

\n
\n

v0.9.9A-SA-Meck-standalone.bin\nSame as the Audio-BLE build but with Bluetooth and WiFi completely removed at compile time. The radio hardware is never initialised, giving a significant battery life improvement. The web browser, IRC client, and map viewer are not available on this variant. Up to 1,500 contacts and 20 channels.

\n
\n

Battery life: Disabling Bluetooth extends estimated runtime from ~10.5 hours to ~20.5 hours on the 1400mAh cell.

\n
\n
\n

⚠️ PCM5102A audio hardware only — do not flash on 4G boards.

\n
\n
\n

See all the features and updates that are available in Meck from v0.9.8 onwards here: https://github.com/pelgraine/Meck/releases/tag/wifi-1

\n" }, { "version": "v0.9.8.1", "name": "Meck v0.9.8.1 - bugfixes for v0.9.8", "datetime": "2026-03-05T07:50:08Z", "url": "https://github.com/pelgraine/Meck/releases/tag/v0.9.8.1", "prerelease": false, "notes": "
\r\n

What's New Since v0.9.8

\r\n

Bugfixes: Discover nodes is back to working how it should, and repeater admin login fixes have been applied along with improvements on how login timeout responses behave depending on how many hops away the repeater is. Also have now fixed webreaderscreen missing code regression that popped up.

\r\n
\r\n

Six firmware variants, one codebase. Pick the right .bin for your hardware:

\r\n
\r\n

Firmware Variants

\r\n

v0.9.8.1-Meck-4G-BLE.bin\r\nFor T-Deck Pro 4G boards. Full-featured build — messaging, contacts, direct messages, repeater admin, e-book reader, notes, emoji, GPS, map viewer, BLE companion app support, SMS & Phone app, IRC client, and web browser. Up to 500 contacts and 20 channels.

\r\n
\r\n

Note: BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.

\r\n
\r\n

v0.9.8.1W-Meck-4G-WiFi.bin\r\nFor T-Deck Pro 4G boards. Same as the 4G-BLE build but with WiFi replacing BLE as the companion transport — connect via the MeshCore web app, iOS/Android app, meshcore.js, or Python CLI over your local network (TCP port 5000). WiFi is on by default at boot but can be toggled off in Settings to save power. No BLE companion app support. Up to 1,500 contacts and 20 channels.

\r\n

Also available for those with a custom 2000mah battery build.

\r\n

v0.9.8.14G.SA-Meck-standalone.bin\r\nFor T-Deck Pro 4G boards. No BLE or WiFi companion — maximum battery life. The web browser, IRC client, and map viewer are all still available (they use WiFi independently, not as a companion transport). Up to 1,500 contacts and 20 channels.

\r\n

v0.9.8.1A-Meck-Audio-BLE.bin\r\nEverything in the 4G-BLE build plus the audiobook player, sleep timer, and auto-queuing — minus the 4G modem features. BLE companion support included. Up to 500 contacts and 20 channels.

\r\n
\r\n

⚠️ PCM5102A audio hardware only. The I2S audio pins (GPIO 7, 8, 9) conflict with the A7682E modem control lines — do not flash on 4G boards.

\r\n
\r\n
\r\n

Note: BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.

\r\n
\r\n

v0.9.8.1AW-Meck-Audio-WiFi.bin\r\nSame as the Audio-BLE build but with WiFi replacing BLE as the companion transport. WiFi is on by default at boot but can be toggled off in Settings to save power. No BLE companion app support. Up to 1,500 contacts and 20 channels.

\r\n
\r\n

⚠️ PCM5102A audio hardware only — same GPIO conflict applies. Do not flash on 4G boards.

\r\n
\r\n

v0.9.8.1A-SA-Meck-standalone.bin\r\nSame as the Audio-BLE build but with Bluetooth and WiFi completely removed at compile time. The radio hardware is never initialised, giving a significant battery life improvement. The web browser, IRC client, and map viewer are not available on this variant. Up to 1,500 contacts and 20 channels.

\r\n
\r\n

Battery life: Disabling Bluetooth extends estimated runtime from ~10.5 hours to ~20.5 hours on the 1400mAh cell.

\r\n
\r\n
\r\n

⚠️ PCM5102A audio hardware only — do not flash on 4G boards.

\r\n
\r\n
\r\nSee all the features and updates available in Meck v0.9.8 here: https://github.com/pelgraine/Meck/releases/tag/wifi-1", "notesHtml": "
\n

What's New Since v0.9.8

\n

Bugfixes: Discover nodes is back to working how it should, and repeater admin login fixes have been applied along with improvements on how login timeout responses behave depending on how many hops away the repeater is. Also have now fixed webreaderscreen missing code regression that popped up.

\n
\n

Six firmware variants, one codebase. Pick the right .bin for your hardware:

\n
\n

Firmware Variants

\n

v0.9.8.1-Meck-4G-BLE.bin\nFor T-Deck Pro 4G boards. Full-featured build — messaging, contacts, direct messages, repeater admin, e-book reader, notes, emoji, GPS, map viewer, BLE companion app support, SMS & Phone app, IRC client, and web browser. Up to 500 contacts and 20 channels.

\n
\n

Note: BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.

\n
\n

v0.9.8.1W-Meck-4G-WiFi.bin\nFor T-Deck Pro 4G boards. Same as the 4G-BLE build but with WiFi replacing BLE as the companion transport — connect via the MeshCore web app, iOS/Android app, meshcore.js, or Python CLI over your local network (TCP port 5000). WiFi is on by default at boot but can be toggled off in Settings to save power. No BLE companion app support. Up to 1,500 contacts and 20 channels.

\n

Also available for those with a custom 2000mah battery build.

\n

v0.9.8.14G.SA-Meck-standalone.bin\nFor T-Deck Pro 4G boards. No BLE or WiFi companion — maximum battery life. The web browser, IRC client, and map viewer are all still available (they use WiFi independently, not as a companion transport). Up to 1,500 contacts and 20 channels.

\n

v0.9.8.1A-Meck-Audio-BLE.bin\nEverything in the 4G-BLE build plus the audiobook player, sleep timer, and auto-queuing — minus the 4G modem features. BLE companion support included. Up to 500 contacts and 20 channels.

\n
\n

⚠️ PCM5102A audio hardware only. The I2S audio pins (GPIO 7, 8, 9) conflict with the A7682E modem control lines — do not flash on 4G boards.

\n
\n
\n

Note: BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.

\n
\n

v0.9.8.1AW-Meck-Audio-WiFi.bin\nSame as the Audio-BLE build but with WiFi replacing BLE as the companion transport. WiFi is on by default at boot but can be toggled off in Settings to save power. No BLE companion app support. Up to 1,500 contacts and 20 channels.

\n
\n

⚠️ PCM5102A audio hardware only — same GPIO conflict applies. Do not flash on 4G boards.

\n
\n

v0.9.8.1A-SA-Meck-standalone.bin\nSame as the Audio-BLE build but with Bluetooth and WiFi completely removed at compile time. The radio hardware is never initialised, giving a significant battery life improvement. The web browser, IRC client, and map viewer are not available on this variant. Up to 1,500 contacts and 20 channels.

\n
\n

Battery life: Disabling Bluetooth extends estimated runtime from ~10.5 hours to ~20.5 hours on the 1400mAh cell.

\n
\n
\n

⚠️ PCM5102A audio hardware only — do not flash on 4G boards.

\n
\n
\nSee all the features and updates available in Meck v0.9.8 here: https://github.com/pelgraine/Meck/releases/tag/wifi-1" }, { "version": "wifi-1", "name": "Meck v0.9.8 — Maps, WiFi Companion, Serial Config & More", "datetime": "2026-03-04T09:20:45Z", "url": "https://github.com/pelgraine/Meck/releases/tag/wifi-1", "prerelease": false, "notes": "

Six firmware variants, one codebase. Pick the right .bin for your hardware:

\r\n
\r\n

Firmware Variants

\r\n

v0.9.8-Meck-4G-BLE.bin\r\nFor T-Deck Pro 4G boards. Full-featured build — messaging, contacts, direct messages, repeater admin, e-book reader, notes, emoji, GPS, map viewer, BLE companion app support, SMS & Phone app, IRC client, and web browser. Up to 500 contacts and 20 channels.

\r\n
\r\n

Note: BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.

\r\n
\r\n

v0.9.8W-Meck-4G-WiFi.bin\r\nFor T-Deck Pro 4G boards. Same as the 4G-BLE build but with WiFi replacing BLE as the companion transport — connect via the MeshCore web app, iOS/Android app, meshcore.js, or Python CLI over your local network (TCP port 5000). WiFi is on by default at boot but can be toggled off in Settings to save power. No BLE companion app support. Up to 1,500 contacts and 20 channels.

\r\n

v0.9.8.4G.SA-Meck-standalone.bin\r\nFor T-Deck Pro 4G boards. No BLE or WiFi companion — maximum battery life. The web browser, IRC client, and map viewer are all still available (they use WiFi independently, not as a companion transport). Up to 1,500 contacts and 20 channels.

\r\n

v0.9.8A-Meck-Audio-BLE.bin\r\nEverything in the 4G-BLE build plus the audiobook player, sleep timer, and auto-queuing — minus the 4G modem features. BLE companion support included. Up to 500 contacts and 20 channels.

\r\n
\r\n

⚠️ PCM5102A audio hardware only. The I2S audio pins (GPIO 7, 8, 9) conflict with the A7682E modem control lines — do not flash on 4G boards.

\r\n
\r\n
\r\n

Note: BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.

\r\n
\r\n

v0.9.8AW-Meck-Audio-WiFi.bin\r\nSame as the Audio-BLE build but with WiFi replacing BLE as the companion transport. WiFi is on by default at boot but can be toggled off in Settings to save power. No BLE companion app support. Up to 1,500 contacts and 20 channels.

\r\n
\r\n

⚠️ PCM5102A audio hardware only — same GPIO conflict applies. Do not flash on 4G boards.

\r\n
\r\n

v0.9.8A-SA-Meck-standalone.bin\r\nSame as the Audio-BLE build but with Bluetooth and WiFi completely removed at compile time. The radio hardware is never initialised, giving a significant battery life improvement. The web browser, IRC client, and map viewer are not available on this variant. Up to 1,500 contacts and 20 channels.

\r\n
\r\n

Battery life: Disabling Bluetooth extends estimated runtime from ~10.5 hours to ~20.5 hours on the 1400mAh cell.

\r\n
\r\n
\r\n

⚠️ PCM5102A audio hardware only — do not flash on 4G boards.

\r\n
\r\n
\r\n

What's New Since v0.9.5

\r\n

🗺️ GPS Map Viewer (All variants except Audio Standalone)

\r\n

Press G from the home screen to open the map. Renders standard OSM \"slippy map\" tiles from your SD card at native 240×320 resolution, with a GPS position marker and overlays for all mesh contacts that have GPS coordinates.

\r\n\r\nKey | Action\r\n-- | --\r\nW / A / S / D | Pan the map\r\n+ / - | Zoom in / out\r\nG | Re-centre on your GPS position\r\nQ | Back to home screen\r\n\r\n\r\n
\r\n

🔁 Repeater Admin Improvements

\r\n

The repeater admin screen has been significantly expanded. Commands are now organised into a category menu, grouping related functions into logical sections rather than a single flat list — making it easier to navigate the full command set without scrolling past irrelevant options.

\r\n

Telemetry is now fetched automatically on login — no \n…", "notesHtml": "

Six firmware variants, one codebase. Pick the right .bin for your hardware:

\n
\n

Firmware Variants

\n

v0.9.8-Meck-4G-BLE.bin\nFor T-Deck Pro 4G boards. Full-featured build — messaging, contacts, direct messages, repeater admin, e-book reader, notes, emoji, GPS, map viewer, BLE companion app support, SMS & Phone app, IRC client, and web browser. Up to 500 contacts and 20 channels.

\n
\n

Note: BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.

\n
\n

v0.9.8W-Meck-4G-WiFi.bin\nFor T-Deck Pro 4G boards. Same as the 4G-BLE build but with WiFi replacing BLE as the companion transport — connect via the MeshCore web app, iOS/Android app, meshcore.js, or Python CLI over your local network (TCP port 5000). WiFi is on by default at boot but can be toggled off in Settings to save power. No BLE companion app support. Up to 1,500 contacts and 20 channels.

\n

v0.9.8.4G.SA-Meck-standalone.bin\nFor T-Deck Pro 4G boards. No BLE or WiFi companion — maximum battery life. The web browser, IRC client, and map viewer are all still available (they use WiFi independently, not as a companion transport). Up to 1,500 contacts and 20 channels.

\n

v0.9.8A-Meck-Audio-BLE.bin\nEverything in the 4G-BLE build plus the audiobook player, sleep timer, and auto-queuing — minus the 4G modem features. BLE companion support included. Up to 500 contacts and 20 channels.

\n
\n

⚠️ PCM5102A audio hardware only. The I2S audio pins (GPIO 7, 8, 9) conflict with the A7682E modem control lines — do not flash on 4G boards.

\n
\n
\n

Note: BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.

\n
\n

v0.9.8AW-Meck-Audio-WiFi.bin\nSame as the Audio-BLE build but with WiFi replacing BLE as the companion transport. WiFi is on by default at boot but can be toggled off in Settings to save power. No BLE companion app support. Up to 1,500 contacts and 20 channels.

\n
\n

⚠️ PCM5102A audio hardware only — same GPIO conflict applies. Do not flash on 4G boards.

\n
\n

v0.9.8A-SA-Meck-standalone.bin\nSame as the Audio-BLE build but with Bluetooth and WiFi completely removed at compile time. The radio hardware is never initialised, giving a significant battery life improvement. The web browser, IRC client, and map viewer are not available on this variant. Up to 1,500 contacts and 20 channels.

\n
\n

Battery life: Disabling Bluetooth extends estimated runtime from ~10.5 hours to ~20.5 hours on the 1400mAh cell.

\n
\n
\n

⚠️ PCM5102A audio hardware only — do not flash on 4G boards.

\n
\n
\n

What's New Since v0.9.5

\n

🗺️ GPS Map Viewer (All variants except Audio Standalone)

\n

Press G from the home screen to open the map. Renders standard OSM \"slippy map\" tiles from your SD card at native 240×320 resolution, with a GPS position marker and overlays for all mesh contacts that have GPS coordinates.

\n\n\n\n\n\n\n\n\n\n\n
KeyAction
W / A / S / DPan the map
\n
    \n
  • / - | Zoom in / out\nG | Re-centre on your GPS position\nQ | Back to home screen
    • \n
\n
\n

🔁 Repeater Admin Improvements

\n

The repeater admin screen has been significantly expanded. Commands are now organised into a category menu, grouping related functions into logical sections rather than a single flat list — making it easier to navigate the full command set without scrolling past irrelevant options.

\n

Telemetry is now fetched automatically on login — no \n…

" }, { "version": "v0.9.5", "name": "Meck v0.9.5 — Phone App Overhaul, IRC, Web Browser & More", "datetime": "2026-02-27T09:09:11Z", "url": "https://github.com/pelgraine/Meck/releases/tag/v0.9.5", "prerelease": false, "notes": "Four firmware variants, one codebase. Pick the right `.bin` for your hardware:\r\n\r\n## Firmware Variants\r\n\r\n### v0.9.5-Meck-4G-BLE.bin\r\n\r\n**For T-Deck Pro 4G boards.** The full-featured build — messaging, contacts, direct messages, repeater admin, e-book reader, notes, emoji, basic GPS, BLE companion app support, SMS & Phone app, and the **new IRC client, web browser, and DuckDuckGo search**. Limited to max 500 contacts and 20 channels.\r\n\r\n> **Note:** BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.\r\n\r\n### v0.9.5-4GSA-Meck-4G (1400mAh stock battery).bin\r\n\r\n**For T-Deck Pro 4G boards with the stock 1400mAh battery.** Same features as the 4G-BLE build but with Bluetooth removed at compile time — no BLE companion app support, but WiFi and the web browser/IRC remain available. Battery gauge calibrated for the stock 1400mAh cell. Limited to max 1500 contacts and 20 channels.\r\n\r\n### v0.9.5-4GSA-Meck-4G (2000mAh battery).bin\r\n\r\n**For T-Deck Pro 4G boards with an upgraded 2000mAh battery and custom case.** Identical to the 4G standalone variant above, but with the battery gauge calibrated for a 2000mAh cell. Limited to max 1500 contacts and 20 channels.\r\n\r\n### v0.9.5A-Meck-Audio-BLE (PCM5102A Audio only).bin\r\n\r\nEverything in the standard build plus the audiobook player, sleep timer, and auto-queuing — minus the 4G modem features. Includes the new web browser, DuckDuckGo search, and IRC client over WiFi. Limited to max 500 contacts and 20 channels.\r\n\r\n> **⚠️ Do not flash this on the 4G variant** — the I2S audio pins (GPIO 7, 8, 9) conflict with the modem control lines. This firmware is only for T-Deck Pro boards with the PCM5102A DAC.\r\n\r\n> **Note:** BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.\r\n\r\n### v0.9.5A-SA-Meck-standalone-firmware (PCM5102A Audio only).bin\r\n\r\nSame as the Audio+BLE build but with Bluetooth and WiFi completely removed at compile time. The BLE/WiFi radio hardware is never initialised, giving a significant battery life improvement. The web browser and IRC client are not available on this variant. Limited to max 1500 contacts and 20 channels.\r\n\r\n> **Battery life:** Disabling Bluetooth extends estimated runtime from ~10.5 hours to ~20.5 hours on the 1400mAh cell.\r\n\r\n> **⚠️ PCM5102A audio hardware only** — same GPIO conflict applies as the Audio+BLE variant. Do not flash on 4G boards.\r\n\r\n---\r\n\r\n## What's New Since v0.9.3\r\n\r\n### 📱 Phone App Overhaul (4G variant only)\r\n\r\nThe Phone app has been redesigned with a new dedicated screen giving you the choice of making phone calls to non-contacts or jumping straight into the SMS inbox where you can also call saved contacts.\r\n\r\n* **New phone dialpad** with three text entry methods:\r\n - **Direct key press** — press the keyboard letter mapped to each number (W for 1, E for 2, etc.)\r\n - **Touchscreen tap** — tap the on-screen number buttons directly (note: requires fairly precise taps on the numbers themselves)\r\n - **Sym+key** — the classic method from previous versions\r\n* **IMEI, carrier, and APN details** now displayed at the bottom of the Settings menu alongside your node ID and firmware version\r\n* **Favourites filter** added to the mesh Contacts screen\r\n* **Fixed regression** with dropped in-call screen\r\n* **Fixed 0 key recognition** on the dialpad\r\n\r\n### 🌐 Web Browser & Search (BLE and 4G variants)\r\n\r\nA brand-new set of connectivity features available on the 4G-BLE, 4G standalone, and Audio-BLE variants (not the standalone audio variant, which excludes WiFi to preserve lowest-battery-usage design):\r\n\r\n* **DuckDuckGo Lite search** — very basic web search directly from the device\r\n* **HTML web reader browser** — a text-centric web browser, still very much in development but already useful for reading text-heavy websites\r\n* **EPUB download support** — follow a link to an `.epub` file\n…", "notesHtml": "

Four firmware variants, one codebase. Pick the right .bin for your hardware:

\n

Firmware Variants

\n

v0.9.5-Meck-4G-BLE.bin

\n

For T-Deck Pro 4G boards. The full-featured build — messaging, contacts, direct messages, repeater admin, e-book reader, notes, emoji, basic GPS, BLE companion app support, SMS & Phone app, and the new IRC client, web browser, and DuckDuckGo search. Limited to max 500 contacts and 20 channels.

\n
\n

Note: BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.

\n
\n

v0.9.5-4GSA-Meck-4G (1400mAh stock battery).bin

\n

For T-Deck Pro 4G boards with the stock 1400mAh battery. Same features as the 4G-BLE build but with Bluetooth removed at compile time — no BLE companion app support, but WiFi and the web browser/IRC remain available. Battery gauge calibrated for the stock 1400mAh cell. Limited to max 1500 contacts and 20 channels.

\n

v0.9.5-4GSA-Meck-4G (2000mAh battery).bin

\n

For T-Deck Pro 4G boards with an upgraded 2000mAh battery and custom case. Identical to the 4G standalone variant above, but with the battery gauge calibrated for a 2000mAh cell. Limited to max 1500 contacts and 20 channels.

\n

v0.9.5A-Meck-Audio-BLE (PCM5102A Audio only).bin

\n

Everything in the standard build plus the audiobook player, sleep timer, and auto-queuing — minus the 4G modem features. Includes the new web browser, DuckDuckGo search, and IRC client over WiFi. Limited to max 500 contacts and 20 channels.

\n
\n

⚠️ Do not flash this on the 4G variant — the I2S audio pins (GPIO 7, 8, 9) conflict with the modem control lines. This firmware is only for T-Deck Pro boards with the PCM5102A DAC.

\n
\n
\n

Note: BLE is toggled off at boot to save battery. Navigate to the Bluetooth home page and press Enter to enable it when you want to connect to the app.

\n
\n

v0.9.5A-SA-Meck-standalone-firmware (PCM5102A Audio only).bin

\n

Same as the Audio+BLE build but with Bluetooth and WiFi completely removed at compile time. The BLE/WiFi radio hardware is never initialised, giving a significant battery life improvement. The web browser and IRC client are not available on this variant. Limited to max 1500 contacts and 20 channels.

\n
\n

Battery life: Disabling Bluetooth extends estimated runtime from ~10.5 hours to ~20.5 hours on the 1400mAh cell.

\n
\n
\n

⚠️ PCM5102A audio hardware only — same GPIO conflict applies as the Audio+BLE variant. Do not flash on 4G boards.

\n
\n
\n

What's New Since v0.9.3

\n

📱 Phone App Overhaul (4G variant only)

\n

The Phone app has been redesigned with a new dedicated screen giving you the choice of making phone calls to non-contacts or jumping straight into the SMS inbox where you can also call saved contacts.

\n
    \n
  • New phone dialpad with three text entry methods:
      \n
    • Direct key press — press the keyboard letter mapped to each number (W for 1, E for 2, etc.)
      • \n
    • Touchscreen tap — tap the on-screen number buttons directly (note: requires fairly precise taps on the numbers themselves)
      • \n
    • Sym+key — the classic method from previous versions
      • \n
    \n
    • \n
  • IMEI, carrier, and APN details now displayed at the bottom of the Settings menu alongside your node ID and firmware version
    • \n
  • Favourites filter added to the mesh Contacts screen
    • \n
  • Fixed regression with dropped in-call screen
    • \n
  • Fixed 0 key recognition on the dialpad
    • \n
\n

🌐 Web Browser & Search (BLE and 4G variants)

\n

A brand-new set of connectivity features available on the 4G-BLE, 4G standalone, and Audio-BLE variants (not the standalone audio variant, which excludes WiFi to preserve lowest-battery-usage design):

\n
    \n
  • DuckDuckGo Lite search — very basic web search directly from the device
    • \n
  • HTML web reader browser — a text-centric web browser, still very much in development but already useful for reading text-heavy websites
    • \n
  • EPUB download support — follow a link to an .epub file\n…
    • \n
\n" } ], "changelogSource": "github", "changelogUpdatedAt": "2026-06-21T09:55:31.295Z" }, { "id": "meck-p4", "name": "Meck-P4", "type": "fork", "maintainer": "pelgraine", "description": "A port of Meck (a MeshCore fork) to the LilyGo T-Display P4, targeting the ESP32-P4 main MCU. The onboard ESP32-C6 provides WiFi companion connectivity to the MeshCore app; BLE is not yet enabled. Features a full touch UI with virtual keyboard, channel messaging, repeater admin, trace route, position adverts, and private channels.\n", "repository": "https://github.com/pelgraine/Meck-P4", "license": "GPL-3.0", "status": "active", "lifecycle": "active", "maturity": "alpha", "distribution": "community", "lineage": { "kind": "fork", "upstreamFirmwareId": "meshcore-official", "upstreamRepository": "https://github.com/meshcore-dev/MeshCore" }, "runtime": { "framework": "arduino", "language": "cpp" }, "roles": [ "companion", "repeater", "room-server" ], "features": [ "ESP32-P4 main MCU with ESP32-C6 WiFi companion", "Touch UI with virtual keyboard", "Screen-off power saving", "Channel messaging and direct messages", "Repeater admin and room server", "Trace route and path view", "Position adverts and share position", "Private channels", "Per-contact path editor", "Region scope" ], "capabilities": { "protocol": { "meshcoreCompatible": true }, "transports": { "ble": false, "usbSerial": true, "nativeTcp": true, "wifiAp": true }, "operations": { "ota": false, "webFlasher": false }, "networking": { "repeater": true, "roomServer": true, "observer": false, "kissModem": false }, "hardware": { "gps": true, "display": true, "sensors": false, "lowPowerRx": false } }, "devices": [ { "id": "lilygo-tdisplay-p4", "status": "supported" } ], "popularity": { "githubStars": 9, "githubForks": 1, "githubWatchers": 1, "githubOpenIssues": 0, "githubContributors": 2, "releaseDownloads": 111, "latestReleaseDownloads": 17, "lastChecked": "2026-06-21" }, "verification": { "sourceAvailable": true, "releasesAvailable": true, "ciBuilds": false, "lastChecked": "2026-06-21" }, "latest_version": "0.6.2-patch", "released": "2026-06-14", "releases": [ { "version": "v0.6.2-patch", "name": "Meck P4 v0.6.2 Pre-release (Patch): Trace and notification fixes", "datetime": "2026-06-14T19:48:10Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.6.2-patch", "prerelease": true, "notes": "# Meck P4 v0.6.2 Pre-release (Patch): Trace and notification fixes\r\n\r\nPoint release on top of [[v0.6.1](https://github.com/pelgraine/Meck-P4/releases/tag/v0.6.1-patch)](https://github.com/pelgraine/Meck-P4/releases/tag/v0.6.1-patch). Two bug fixes, no new features. Firmware identity is now 0.6.2.\r\n\r\n## Bug Fixes\r\n\r\n### Multi-byte trace path parsed as single-byte\r\n\r\nRunning a path trace in **2-byte mode** returned a wrong result. The response was parsed as if it were 1-byte, so it reported twice as many hops as actually existed, each one resolved to the wrong repeater. As an example, a two-hop 2-byte trace of `3601,2198` came back as four hops (`36`, `01`, `21`, `98`) matched against unrelated repeaters.\r\n\r\nThe cause was in the trace-response handler: the hop count and hash size were taken from the wrong source. The byte length handed up from the base layer was being read with the packet-header path encoding, which collapses to 1-byte mode for any short path. The real hash size is carried separately in the trace flags.\r\n\r\nThe handler now reads the hash size from the trace flags and computes the hop count as the path byte length divided by bytes-per-hop. 1-byte traces were already correct and are unchanged. 2-byte traces now report the right hop count and resolve to the correct repeaters.\r\n\r\n### Custom notification sounds not playing\r\n\r\nCustom per-channel notification tones stopped playing as of v0.6 (they worked in v0.5). A tone could be selected and would show as set, but nothing played when a message arrived on that channel.\r\n\r\nThe cause was the v0.6 audio rework, which split file preparation from playback start. The notification trigger prepared the tone file but never issued the start, so it sat ready and silent.\r\n\r\nThe notification path now starts playback after preparing. The same missing start also affected the tone-picker preview and voice-message playback, both fixed by the same change.\r\n\r\n## Files Changed\r\n\r\n3 files changed (`MeckMesh.h`, `MeckUI.cpp`, `meck.h`).\r\n\r\n## First-Time Flashing: Read This First\r\n\r\nMeck-P4 ships as a single **merged binary** (bootloader + partition table + application combined). One file, flash at offset `0x0`.\r\n> **An SD card is recommended.** With a FAT32-formatted card inserted, every saved setting, channel message, DM, room post, and note is mirrored or stored on the card, notification tones have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot, and the Reader, Notes, and notification sounds have no storage.\r\n\r\nEnsure you use the **right-side USB-C port** (the data port), not the high-speed charger port, to flash.\r\n\"correct\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to \r\n2. Scroll to the bottom and select **Custom Firmware**\r\n3. Select the `meck-p4-0.6.2.bin` file you downloaded\r\n4. Click OK on the merged-binary warning\r\n5. Click **Flash**, pick your device in the popup, and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\n```\r\npip install esptool\r\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.6.2.bin\r\n```\r\n\r\n(Replace `PORT` with `/dev/cu.usbmodemXXXX` on macOS, `/dev/ttyACM0` on Linux, or `COM3` on Windows.)\r\n\r\nUpgrading from v0.6.1 or v0.6 does not require `erase_flash`. This patch changes program logic only and adds no new settings, so existing prefs carry over unchanged.\r\n\r\n---\r\n\r\nFor the full feature list see the [[README](https://github.com/pelgraine/Meck-P4/blob/main/README.md)](https://github.com/pelgraine/Meck-P4/blob/main/README.md).\r\n\r\n## Reporting Issues\r\n\r\nThe Meck-P4 channel on the MeshCore Discord is the fastest path. GitHub Issues on the Meck-P4 repo also work for anything reproducible. Include the serial log if you can: Settings > Debug Logs > Start capt\n…", "notesHtml": "

Meck P4 v0.6.2 Pre-release (Patch): Trace and notification fixes

\n

Point release on top of v0.6.1. Two bug fixes, no new features. Firmware identity is now 0.6.2.

\n

Bug Fixes

\n

Multi-byte trace path parsed as single-byte

\n

Running a path trace in 2-byte mode returned a wrong result. The response was parsed as if it were 1-byte, so it reported twice as many hops as actually existed, each one resolved to the wrong repeater. As an example, a two-hop 2-byte trace of 3601,2198 came back as four hops (36, 01, 21, 98) matched against unrelated repeaters.

\n

The cause was in the trace-response handler: the hop count and hash size were taken from the wrong source. The byte length handed up from the base layer was being read with the packet-header path encoding, which collapses to 1-byte mode for any short path. The real hash size is carried separately in the trace flags.

\n

The handler now reads the hash size from the trace flags and computes the hop count as the path byte length divided by bytes-per-hop. 1-byte traces were already correct and are unchanged. 2-byte traces now report the right hop count and resolve to the correct repeaters.

\n

Custom notification sounds not playing

\n

Custom per-channel notification tones stopped playing as of v0.6 (they worked in v0.5). A tone could be selected and would show as set, but nothing played when a message arrived on that channel.

\n

The cause was the v0.6 audio rework, which split file preparation from playback start. The notification trigger prepared the tone file but never issued the start, so it sat ready and silent.

\n

The notification path now starts playback after preparing. The same missing start also affected the tone-picker preview and voice-message playback, both fixed by the same change.

\n

Files Changed

\n

3 files changed (MeckMesh.h, MeckUI.cpp, meck.h).

\n

First-Time Flashing: Read This First

\n

Meck-P4 ships as a single merged binary (bootloader + partition table + application combined). One file, flash at offset 0x0.

\n
\n

An SD card is recommended. With a FAT32-formatted card inserted, every saved setting, channel message, DM, room post, and note is mirrored or stored on the card, notification tones have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot, and the Reader, Notes, and notification sounds have no storage.

\n
\n

Ensure you use the right-side USB-C port (the data port), not the high-speed charger port, to flash.\n\"correct

\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.io/
    2. \n
  2. Scroll to the bottom and select Custom Firmware
    3. \n
  3. Select the meck-p4-0.6.2.bin file you downloaded
    4. \n
  4. Click OK on the merged-binary warning
    5. \n
  5. Click Flash, pick your device in the popup, and click Connect
    6. \n
\n

Flashing with esptool.py

\n
pip install esptool\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.6.2.bin\n
\n

(Replace PORT with /dev/cu.usbmodemXXXX on macOS, /dev/ttyACM0 on Linux, or COM3 on Windows.)

\n

Upgrading from v0.6.1 or v0.6 does not require erase_flash. This patch changes program logic only and adds no new settings, so existing prefs carry over unchanged.

\n
\n

For the full feature list see the README.

\n

Reporting Issues

\n

The Meck-P4 channel on the MeshCore Discord is the fastest path. GitHub Issues on the Meck-P4 repo also work for anything reproducible. Include the serial log if you can: Settings > Debug Logs > Start capt\n…

\n" }, { "version": "v0.6.1-patch", "name": "Meck P4 v0.6.1 Pre-release (Patch): Antenna switch", "datetime": "2026-06-10T03:42:22Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.6.1-patch", "prerelease": true, "notes": "Point release on top of [v0.6](https://github.com/pelgraine/Meck-P4/releases/tag/v0.6), adding a software LoRa antenna selector in Settings. No other functional changes. Firmware identity is now 0.6.1.\r\n\r\n## Antenna Switch\r\n\r\nA new **Antenna (tap to toggle)** row at the top of **Settings**, switching the SX1262 between the two ports on the SKY13453 RF switch (XL9535 IO1 / VCTL).\r\n\r\n- **Internal (RF1)** is the default and corresponds to VCTL HIGH; **External (RF2)** is VCTL LOW. The internal antenna is the one in use when no external antenna is attached, so the device works out of the box without changing this.\r\n- The choice persists via prefs (NVS, mirrored to SD) and is re-applied at boot, so the selected port survives a reboot.\r\n- Tap applies live: the pin is driven immediately and the row label updates to show the active port.\r\n\r\n## Bug Fixes\r\n\r\nNone.\r\n\r\n## Files Changed\r\n\r\n5 files changed.\r\n\r\n## First-Time Flashing: Read This First\r\n\r\nMeck-P4 ships as a single **merged binary** (bootloader + partition table + application combined). One file, flash at offset `0x0`.\r\n> **An SD card is recommended.** With a FAT32-formatted card inserted, every saved setting, channel message, DM, room post, and note is mirrored or stored on the card, notification tones have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot, and the Reader, Notes, and notification sounds have no storage.\r\n\r\nEnsure you use the **right-side USB-C port** (the data port), not the high-speed charger port, to flash.\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to \r\n2. Scroll to the bottom and select **Custom Firmware**\r\n3. Select the `meck-p4-0.6.1.bin` file you downloaded\r\n4. Click OK on the merged-binary warning\r\n5. Click **Flash**, pick your device in the popup, and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\n```\r\npip install esptool\r\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.6.1.bin\r\n```\r\n\r\n(Replace `PORT` with `/dev/cu.usbmodemXXXX` on macOS, `/dev/ttyACM0` on Linux, or `COM3` on Windows.)\r\n\r\nUpgrading from v0.6 does not require `erase_flash`. The prefs loader tolerates the older layout, and the new antenna field comes up at its default (Internal).\r\n\r\n---\r\n\r\nFor the full feature list see the [[README](https://github.com/pelgraine/Meck-P4/blob/main/README.md)](https://github.com/pelgraine/Meck-P4/blob/main/README.md).\r\n\r\n## Reporting Issues\r\n\r\nThe Meck-P4 channel on the MeshCore Discord is the fastest path. GitHub Issues on the Meck-P4 repo also work for anything reproducible. Include the serial log if you can: Settings > Debug Logs > Start captures it to SD if a serial monitor isn't practical.\r\n\r\n## License\r\n\r\nMIT for Meck-specific code. The combined firmware binary links libraries with mixed licensing including GPL-3.0 and LGPL-2.1 (Codec2) and is effectively GPL-3.0 when distributed.", "notesHtml": "

Point release on top of v0.6, adding a software LoRa antenna selector in Settings. No other functional changes. Firmware identity is now 0.6.1.

\n

Antenna Switch

\n

A new Antenna (tap to toggle) row at the top of Settings, switching the SX1262 between the two ports on the SKY13453 RF switch (XL9535 IO1 / VCTL).

\n
    \n
  • Internal (RF1) is the default and corresponds to VCTL HIGH; External (RF2) is VCTL LOW. The internal antenna is the one in use when no external antenna is attached, so the device works out of the box without changing this.
    • \n
  • The choice persists via prefs (NVS, mirrored to SD) and is re-applied at boot, so the selected port survives a reboot.
    • \n
  • Tap applies live: the pin is driven immediately and the row label updates to show the active port.
    • \n
\n

Bug Fixes

\n

None.

\n

Files Changed

\n

5 files changed.

\n

First-Time Flashing: Read This First

\n

Meck-P4 ships as a single merged binary (bootloader + partition table + application combined). One file, flash at offset 0x0.

\n
\n

An SD card is recommended. With a FAT32-formatted card inserted, every saved setting, channel message, DM, room post, and note is mirrored or stored on the card, notification tones have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot, and the Reader, Notes, and notification sounds have no storage.

\n
\n

Ensure you use the right-side USB-C port (the data port), not the high-speed charger port, to flash.

\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.io/
    2. \n
  2. Scroll to the bottom and select Custom Firmware
    3. \n
  3. Select the meck-p4-0.6.1.bin file you downloaded
    4. \n
  4. Click OK on the merged-binary warning
    5. \n
  5. Click Flash, pick your device in the popup, and click Connect
    6. \n
\n

Flashing with esptool.py

\n
pip install esptool\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.6.1.bin\n
\n

(Replace PORT with /dev/cu.usbmodemXXXX on macOS, /dev/ttyACM0 on Linux, or COM3 on Windows.)

\n

Upgrading from v0.6 does not require erase_flash. The prefs loader tolerates the older layout, and the new antenna field comes up at its default (Internal).

\n
\n

For the full feature list see the README.

\n

Reporting Issues

\n

The Meck-P4 channel on the MeshCore Discord is the fastest path. GitHub Issues on the Meck-P4 repo also work for anything reproducible. Include the serial log if you can: Settings > Debug Logs > Start captures it to SD if a serial monitor isn't practical.

\n

License

\n

MIT for Meck-specific code. The combined firmware binary links libraries with mixed licensing including GPL-3.0 and LGPL-2.1 (Codec2) and is effectively GPL-3.0 when distributed.

\n" }, { "version": "v0.6", "name": "Meck P4 v0.6 Pre-release: Web reader, Notes, and EPUB books", "datetime": "2026-06-09T22:14:40Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.6", "prerelease": true, "notes": "Feature release building on v0.5, adding a reader-mode web browser over the ESP32-C6, a Notes app, EPUB book support in the reader, a Cyrillic keyboard layout, optional M5Stack CardKB hardware-keyboard support, and a portrait/landscape orientation toggle, alongside several bug fixes. Firmware identity is now 0.6.\r\n\r\n## Web Reader\r\n\r\nA lightweight reader-mode web browser on the new **Web** home tile, running over the onboard ESP32-C6. It drives the C6 directly over ESP-AT, building its HTTP and TLS requests by hand, so it shares the WiFi companion's C6 link but uses its own request path. The C6 must be connected to WiFi for it to fetch anything.\r\n\r\n- Landing menu with **Enter URL**, a **DuckDuckGo Lite** search, **Bookmarks**, and **History**.\r\n- Reader view: pages are parsed to readable text with a status line. Headings render in dark red; link markers show as a muted grey `[N]` and are followed from the **Links** panel.\r\n- HTTPS support, confirmed against DuckDuckGo Lite.\r\n- GET form fill: an orange **Forms (N)** button opens a picker (duplicate forms collapsed), then a fill modal with a labelled field per text or password input. Submitting builds the `action?name=value&...` query and loads it through the normal page path, so history and status stay correct.\r\n- Bookmarks (added from the reader view with a confirmation toast) and History.\r\n- This is a **work in progress**: an amber notice appears for a few seconds each time the Web tile is opened. See Known Limitations below and the README for the full list.\r\n\r\n## EPUB Reading\r\n\r\nThe reader now opens **EPUB (`.epub`)** files in addition to plain text. The file list shows folders, `.txt`, and `.epub` items.\r\n\r\n- Tapping an EPUB converts it to plain text the first time it is opened. A *Converting ... to txt* screen is shown while the book is decoded.\r\n- The result is cached as a `.txt` in a hidden `.epub_cache` subfolder, so re-opening the same EPUB later loads straight from the cache and the conversion only runs once.\r\n- You only ever see and tap the `.epub` itself; the cached text stays hidden from the browser.\r\n\r\n## Notes\r\n\r\nA Notes app on the **Notes** home tile. Notes are plain UTF-8 `.txt` files stored under `/sdcard/notes`, so they live on the removable card, survive a reflash, and can be read or edited on a computer. The folder is created automatically on first run.\r\n\r\n- Browser modelled on the reader's: folder navigation, an up-one-level button, and a breadcrumb, rooted at `/sdcard/notes`. A green **+ New Note** row sits at the top of every folder.\r\n- Create and edit with the on-screen keyboard (which honours the KB Theme and KB Layout settings). New notes are named by date and time when the clock is synced (`note_YYYYMMDD_HHMM.txt`), or sequentially (`note_NNN.txt`) otherwise.\r\n- Read view reuses the reader's paging: left third of the screen turns back, right two-thirds turns forward, with a progress percentage and a saved-position bookmark.\r\n- Long-press a note for an action menu with **Rename**, **Delete** (with confirmation), and **Cancel**.\r\n\r\n## Cyrillic Keyboard\r\n\r\nA fourth on-screen keyboard layout, **ЙЦУКЕН** (Cyrillic), added to the **Settings > KB Layout** cycle alongside QWERTY, AZERTY, and QWERTZ.\r\n\r\n- Standard Russian arrangement, also commonly used by Bulgarian users. The top three rows carry twelve letters each, with ё on the third row.\r\n- The control keys keep their Latin labels (ABC / abc / 1#) so case and number switching still work.\r\n- Ukrainian and Serbian letter sets are not included. The Settings row shows \"ЙЦУКЕН\" when this layout is active.\r\n\r\n## Physical Keyboard (M5Stack CardKB)\r\n\r\nOptional support for the **M5Stack CardKB**, a small I2C QWERTY keyboard, as an alternative to the on-screen keyboard for typing messages. Gated behind the `MECK_CARDKB` build flag (a build-from-source option).\r\n\r\n- Connects to the board's **P1 connector** (the 1x4 header) as a software-I2C bus on SDA = GPIO 48 and SCL = GPIO 47, at 10 kHz, address 0x5F. Probed for \n…", "notesHtml": "

Feature release building on v0.5, adding a reader-mode web browser over the ESP32-C6, a Notes app, EPUB book support in the reader, a Cyrillic keyboard layout, optional M5Stack CardKB hardware-keyboard support, and a portrait/landscape orientation toggle, alongside several bug fixes. Firmware identity is now 0.6.

\n

Web Reader

\n

A lightweight reader-mode web browser on the new Web home tile, running over the onboard ESP32-C6. It drives the C6 directly over ESP-AT, building its HTTP and TLS requests by hand, so it shares the WiFi companion's C6 link but uses its own request path. The C6 must be connected to WiFi for it to fetch anything.

\n
    \n
  • Landing menu with Enter URL, a DuckDuckGo Lite search, Bookmarks, and History.
    • \n
  • Reader view: pages are parsed to readable text with a status line. Headings render in dark red; link markers show as a muted grey [N] and are followed from the Links panel.
    • \n
  • HTTPS support, confirmed against DuckDuckGo Lite.
    • \n
  • GET form fill: an orange Forms (N) button opens a picker (duplicate forms collapsed), then a fill modal with a labelled field per text or password input. Submitting builds the action?name=value&... query and loads it through the normal page path, so history and status stay correct.
    • \n
  • Bookmarks (added from the reader view with a confirmation toast) and History.
    • \n
  • This is a work in progress: an amber notice appears for a few seconds each time the Web tile is opened. See Known Limitations below and the README for the full list.
    • \n
\n

EPUB Reading

\n

The reader now opens EPUB (.epub) files in addition to plain text. The file list shows folders, .txt, and .epub items.

\n
    \n
  • Tapping an EPUB converts it to plain text the first time it is opened. A Converting ... to txt screen is shown while the book is decoded.
    • \n
  • The result is cached as a .txt in a hidden .epub_cache subfolder, so re-opening the same EPUB later loads straight from the cache and the conversion only runs once.
    • \n
  • You only ever see and tap the .epub itself; the cached text stays hidden from the browser.
    • \n
\n

Notes

\n

A Notes app on the Notes home tile. Notes are plain UTF-8 .txt files stored under /sdcard/notes, so they live on the removable card, survive a reflash, and can be read or edited on a computer. The folder is created automatically on first run.

\n
    \n
  • Browser modelled on the reader's: folder navigation, an up-one-level button, and a breadcrumb, rooted at /sdcard/notes. A green + New Note row sits at the top of every folder.
    • \n
  • Create and edit with the on-screen keyboard (which honours the KB Theme and KB Layout settings). New notes are named by date and time when the clock is synced (note_YYYYMMDD_HHMM.txt), or sequentially (note_NNN.txt) otherwise.
    • \n
  • Read view reuses the reader's paging: left third of the screen turns back, right two-thirds turns forward, with a progress percentage and a saved-position bookmark.
    • \n
  • Long-press a note for an action menu with Rename, Delete (with confirmation), and Cancel.
    • \n
\n

Cyrillic Keyboard

\n

A fourth on-screen keyboard layout, ЙЦУКЕН (Cyrillic), added to the Settings > KB Layout cycle alongside QWERTY, AZERTY, and QWERTZ.

\n
    \n
  • Standard Russian arrangement, also commonly used by Bulgarian users. The top three rows carry twelve letters each, with ё on the third row.
    • \n
  • The control keys keep their Latin labels (ABC / abc / 1#) so case and number switching still work.
    • \n
  • Ukrainian and Serbian letter sets are not included. The Settings row shows \"ЙЦУКЕН\" when this layout is active.
    • \n
\n

Physical Keyboard (M5Stack CardKB)

\n

Optional support for the M5Stack CardKB, a small I2C QWERTY keyboard, as an alternative to the on-screen keyboard for typing messages. Gated behind the MECK_CARDKB build flag (a build-from-source option).

\n
    \n
  • Connects to the board's P1 connector (the 1x4 header) as a software-I2C bus on SDA = GPIO 48 and SCL = GPIO 47, at 10 kHz, address 0x5F. Probed for \n…
    • \n
\n" }, { "version": "v0.5", "name": "Meck P4 v0.5 Pre-release: Text reader, inline emoji, and repeater admin", "datetime": "2026-05-29T09:24:01Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.5", "prerelease": true, "notes": "Feature release building on v0.4, adding a plain-text reader, inline colour emoji with a picker, over-the-mesh repeater administration from the companion app, audio player fixes, and draft message saving. Firmware identity is now 0.5.\r\n\r\n## Text Reader\r\n\r\n- New plain-text (.txt) reader, opened from the home grid's Reader tile. Folder browser rooted at `/sdcard/books` with subfolder navigation, a breadcrumb, and an up-one-level button.\r\n- Windowed, page-at-a-time rendering: the reader never loads the whole book, so memory and layout cost stay fixed to one screen regardless of file size. LVGL's own layout finds each page boundary at a clean line break.\r\n- Per-book resume across reboots via a `.pos` sidecar, plus page-back through the pages visited in the current session.\r\n- Percentage progress through the file.\r\n- Reading-view taps: the left third turns back a page, the right two-thirds turns forward. Back returns to the browser; the browser's Back goes up a folder, or home at the `/sdcard/books` root.\r\n- Honours the Settings font-size preference.\r\n\r\n## Inline Emoji\r\n\r\n\r\n\"IMG_3256\"\r\n\"IMG_3255\"\r\n\r\n- Inline colour emoji across the UI. A per-size LVGL image-font (`lv_imgfont`) is attached as the fallback of each `meck_montserrat_*` font, so emoji codepoints the text font can't draw are rendered from baked-in Twemoji images instead of a missing-glyph box. Requires `CONFIG_LV_USE_IMGFONT=y`.\r\n- Emoji picker: a modal scrollable grid opened from the emoji key on the message-composer keyboards, inserting the chosen emoji as UTF-8. Dark-theme aware.\r\n- Expanded emoji set.\r\n- The emoji key moved to the right side of the space bar on the composer keyboards.\r\n- VS-16 presentation selector and the AU-flag regional indicators are handled so trailing combiners don't render as boxes.\r\n\r\n## Repeater Admin (Companion App)\r\n\r\nOver-the-mesh repeater administration from the MeshCore app. The app's session state is kept separate from the on-device Repeater Admin screen, so the two can't capture each other's responses.\r\n\r\n- **CMD_SEND_LOGIN (26)**: log in to a repeater from the app (force-flood for the login itself, `out_path` restored afterwards, `sync_since` reset for room contacts).\r\n- **CMD_SEND_STATUS_REQ (27)**: request a repeater's status block; matched back to the app by tag.\r\n- **CMD_HAS_CONNECTION (28)**: query whether a keep-alive session is active for a contact.\r\n- **CMD_LOGOUT (29)**: end the keep-alive session for a contact.\r\n- **CMD_SEND_BINARY_REQ (50)**: generic binary request (GET_NEIGHBOURS, ACL queries, owner info, and so on), forwarded verbatim and matched by tag. This is the path behind the app's neighbours command.\r\n- **Push notifications**: login success (0x85), login fail (0x86), status response (0x87), and binary response (0x8C). CLI text replies are queued to the app through the existing offline-message path (`TXT_TYPE_CLI_DATA`). Frame layouts mirror upstream byte-for-byte, so the app parses them with no protocol-version negotiation.\r\n- Pushes are delivered to both the BLE and WiFi companions.\r\n\r\n## Audio Player\r\n\r\n- **Track-skip fix**: fixed a cascade where an entire album would skip through in under a second. The end-of-track flag was being set on every player IDLE event, including the internal stop that fires when advancing to the next track, so each advance immediately triggered another. The flag is now set only on a genuine track completion.\r\n- **Bookmarks scoped to audiobooks**: resume bookmarks are kept only for files under `/sdcard/audio/audiobooks`. Music and other audio always start from the beginning, so finishing a short track no longer leaves a near-end position that made it skip on reopen, and no stray bookmark files are written for music.\r\n- **Tappable now-playing ind\n…", "notesHtml": "

Feature release building on v0.4, adding a plain-text reader, inline colour emoji with a picker, over-the-mesh repeater administration from the companion app, audio player fixes, and draft message saving. Firmware identity is now 0.5.

\n

Text Reader

\n
    \n
  • New plain-text (.txt) reader, opened from the home grid's Reader tile. Folder browser rooted at /sdcard/books with subfolder navigation, a breadcrumb, and an up-one-level button.
    • \n
  • Windowed, page-at-a-time rendering: the reader never loads the whole book, so memory and layout cost stay fixed to one screen regardless of file size. LVGL's own layout finds each page boundary at a clean line break.
    • \n
  • Per-book resume across reboots via a .pos sidecar, plus page-back through the pages visited in the current session.
    • \n
  • Percentage progress through the file.
    • \n
  • Reading-view taps: the left third turns back a page, the right two-thirds turns forward. Back returns to the browser; the browser's Back goes up a folder, or home at the /sdcard/books root.
    • \n
  • Honours the Settings font-size preference.
    • \n
\n

Inline Emoji

\n\"IMG_3256\"\n\"IMG_3255\"
    \n
  • Inline colour emoji across the UI. A per-size LVGL image-font (lv_imgfont) is attached as the fallback of each meck_montserrat_* font, so emoji codepoints the text font can't draw are rendered from baked-in Twemoji images instead of a missing-glyph box. Requires CONFIG_LV_USE_IMGFONT=y.
    • \n
  • Emoji picker: a modal scrollable grid opened from the emoji key on the message-composer keyboards, inserting the chosen emoji as UTF-8. Dark-theme aware.
    • \n
  • Expanded emoji set.
    • \n
  • The emoji key moved to the right side of the space bar on the composer keyboards.
    • \n
  • VS-16 presentation selector and the AU-flag regional indicators are handled so trailing combiners don't render as boxes.
    • \n
\n

Repeater Admin (Companion App)

\n

Over-the-mesh repeater administration from the MeshCore app. The app's session state is kept separate from the on-device Repeater Admin screen, so the two can't capture each other's responses.

\n
    \n
  • CMD_SEND_LOGIN (26): log in to a repeater from the app (force-flood for the login itself, out_path restored afterwards, sync_since reset for room contacts).
    • \n
  • CMD_SEND_STATUS_REQ (27): request a repeater's status block; matched back to the app by tag.
    • \n
  • CMD_HAS_CONNECTION (28): query whether a keep-alive session is active for a contact.
    • \n
  • CMD_LOGOUT (29): end the keep-alive session for a contact.
    • \n
  • CMD_SEND_BINARY_REQ (50): generic binary request (GET_NEIGHBOURS, ACL queries, owner info, and so on), forwarded verbatim and matched by tag. This is the path behind the app's neighbours command.
    • \n
  • Push notifications: login success (0x85), login fail (0x86), status response (0x87), and binary response (0x8C). CLI text replies are queued to the app through the existing offline-message path (TXT_TYPE_CLI_DATA). Frame layouts mirror upstream byte-for-byte, so the app parses them with no protocol-version negotiation.
    • \n
  • Pushes are delivered to both the BLE and WiFi companions.
    • \n
\n

Audio Player

\n
    \n
  • Track-skip fix: fixed a cascade where an entire album would skip through in under a second. The end-of-track flag was being set on every player IDLE event, including the internal stop that fires when advancing to the next track, so each advance immediately triggered another. The flag is now set only on a genuine track completion.
    • \n
  • Bookmarks scoped to audiobooks: resume bookmarks are kept only for files under /sdcard/audio/audiobooks. Music and other audio always start from the beginning, so finishing a short track no longer leaves a near-end position that made it skip on reopen, and no stray bookmark files are written for music.
    • \n
  • **Tappable now-playing ind\n…
    • \n
\n" }, { "version": "v0.4", "name": "Meck P4 v0.4 Pre-release: WiFi companion app support", "datetime": "2026-05-28T08:09:22Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.4", "prerelease": true, "notes": "Feature release building on v0.3.8, adding WiFi companion app support, companion protocol compatibility, power optimisation, and stability improvements.\r\n\r\n## WiFi Companion Support\r\n\r\n- Full WiFi companion transport via ESP32-C6 AT commands over SDIO. Connect the MeshCore app to your T-Display P4 over your local WiFi network (TCP port 5000).\r\n- WiFi SSID and password configuration from the device Settings screen.\r\n- WiFi IP address displayed on the home screen and settings page with live refresh.\r\n- WiFi-aware sleep: when WiFi is active, the display dims to zero brightness instead of entering light sleep (which would kill the SDIO bus and TCP connection). Touch or boot button wakes the screen.\r\n\r\n## Companion Protocol\r\n\r\nExtensive companion protocol implementation for MeshCore app compatibility:\r\n\r\n- **CMD_DEVICE_QUERY (22)**: Full device info response including firmware version, build date, model, path hash mode.\r\n- **CMD_APP_START (1)**: Identity, radio params, and position shared with the app on connection.\r\n- **CMD_GET_CONTACTS (4)**: Full contact iteration with streaming and incremental sync (since timestamp).\r\n- **CMD_SEND_CHANNEL_TXT_MSG (3)**: Send channel messages from the app, with own-echo detection so the app shows \"Heard X Repeats\".\r\n- **CMD_SET_ADVERT_NAME (8)**: Set node name from the app.\r\n- **CMD_SET_RADIO_PARAMS (11)**: Set frequency, bandwidth, spreading factor, coding rate (reboot to apply).\r\n- **CMD_SET_RADIO_TX_POWER (12)**: Set TX power.\r\n- **CMD_SET_ADVERT_LATLON (14)**: Set position for adverts.\r\n- **CMD_REMOVE_CONTACT (15)**: Delete contacts from the app.\r\n- **CMD_EXPORT_PRIVATE_KEY (23)**: Export identity for config backup.\r\n- **CMD_IMPORT_PRIVATE_KEY (24)**: Import identity for config restore.\r\n- **CMD_GET_CONTACT_BY_KEY (30)**: Look up contact by public key (required for app-side delete).\r\n- **CMD_SET_CHANNEL (32)**: Import/update channel name and secret from the app.\r\n- **CMD_SET_OTHER_PARAMS (38)**: Set manual add, advert location policy, multi-acks.\r\n- **CMD_GET_CUSTOM_VARS (40)**: Returns GPS state, interval, latitude, longitude for the app's Position Settings page.\r\n- **CMD_SET_CUSTOM_VAR (41)**: Toggle GPS on/off, set latitude/longitude from the app.\r\n- **CMD_GET_ADVERT_PATH (42)**: Returns cached advert path hashes so the app can display route details with repeater names.\r\n- **CMD_SET_FLOOD_SCOPE_KEY (54)**: Acknowledged (stub).\r\n- **CMD_SET_PATH_HASH_MODE (61)**: Set path hash size (1-byte, 2-byte, or 3-byte) from the app's Experimental Settings.\r\n- **CMD_SET_DEFAULT_FLOOD_SCOPE (63)**: Set/clear default region scope from the app.\r\n- **CMD_GET_DEFAULT_FLOOD_SCOPE (64)**: Returns current scope name and key.\r\n- **Push notifications**: Channel messages, DM messages, send confirmations (acks), new adverts, and path updates are all pushed to the app in real time.\r\n\r\n## Channel Expansion\r\n\r\n- Channel support expanded from 12 to 40 (`MAX_GROUP_CHANNELS`).\r\n- Channel notification preferences array expanded to match (41 slots: 40 channels + 1 DM).\r\n- Channel picker UI updated to support all 40 channels.\r\n- Stack-local channel record arrays moved to heap allocation to prevent stack overflow.\r\n\r\n## Power Optimisation\r\n\r\n- **ICM20948 IMU**: Put to sleep after init (~3mA saved).\r\n- **ES8311 audio codec**: DAC, ADC, and PGA powered down after init. I2S channels disabled to release APB_FREQ_MAX PM locks. Woken on demand before playback, slept after stop (~5-10mA saved).\r\n- **I2S PM lock management**: Added `disable_channels()` / `enable_channels()` to Hardware_Iis class so I2S driver PM locks are only held during active audio playback.\r\n- **DFS investigation**: PM stats task added (enable via sdkconfig). Confirmed DSI display driver holds CPU_FREQ_MAX lock 97% of the time while screen is on, making CPU frequency reduction ineffective. ~172mA baseline is the hardware floor with display active.\r\n\r\n## UI Improvements\r\n\r\n- **Path display**: Incoming message routes and outgoing heard-by lists reformatted as n\n…", "notesHtml": "

Feature release building on v0.3.8, adding WiFi companion app support, companion protocol compatibility, power optimisation, and stability improvements.

\n

WiFi Companion Support

\n
    \n
  • Full WiFi companion transport via ESP32-C6 AT commands over SDIO. Connect the MeshCore app to your T-Display P4 over your local WiFi network (TCP port 5000).
    • \n
  • WiFi SSID and password configuration from the device Settings screen.
    • \n
  • WiFi IP address displayed on the home screen and settings page with live refresh.
    • \n
  • WiFi-aware sleep: when WiFi is active, the display dims to zero brightness instead of entering light sleep (which would kill the SDIO bus and TCP connection). Touch or boot button wakes the screen.
    • \n
\n

Companion Protocol

\n

Extensive companion protocol implementation for MeshCore app compatibility:

\n
    \n
  • CMD_DEVICE_QUERY (22): Full device info response including firmware version, build date, model, path hash mode.
    • \n
  • CMD_APP_START (1): Identity, radio params, and position shared with the app on connection.
    • \n
  • CMD_GET_CONTACTS (4): Full contact iteration with streaming and incremental sync (since timestamp).
    • \n
  • CMD_SEND_CHANNEL_TXT_MSG (3): Send channel messages from the app, with own-echo detection so the app shows \"Heard X Repeats\".
    • \n
  • CMD_SET_ADVERT_NAME (8): Set node name from the app.
    • \n
  • CMD_SET_RADIO_PARAMS (11): Set frequency, bandwidth, spreading factor, coding rate (reboot to apply).
    • \n
  • CMD_SET_RADIO_TX_POWER (12): Set TX power.
    • \n
  • CMD_SET_ADVERT_LATLON (14): Set position for adverts.
    • \n
  • CMD_REMOVE_CONTACT (15): Delete contacts from the app.
    • \n
  • CMD_EXPORT_PRIVATE_KEY (23): Export identity for config backup.
    • \n
  • CMD_IMPORT_PRIVATE_KEY (24): Import identity for config restore.
    • \n
  • CMD_GET_CONTACT_BY_KEY (30): Look up contact by public key (required for app-side delete).
    • \n
  • CMD_SET_CHANNEL (32): Import/update channel name and secret from the app.
    • \n
  • CMD_SET_OTHER_PARAMS (38): Set manual add, advert location policy, multi-acks.
    • \n
  • CMD_GET_CUSTOM_VARS (40): Returns GPS state, interval, latitude, longitude for the app's Position Settings page.
    • \n
  • CMD_SET_CUSTOM_VAR (41): Toggle GPS on/off, set latitude/longitude from the app.
    • \n
  • CMD_GET_ADVERT_PATH (42): Returns cached advert path hashes so the app can display route details with repeater names.
    • \n
  • CMD_SET_FLOOD_SCOPE_KEY (54): Acknowledged (stub).
    • \n
  • CMD_SET_PATH_HASH_MODE (61): Set path hash size (1-byte, 2-byte, or 3-byte) from the app's Experimental Settings.
    • \n
  • CMD_SET_DEFAULT_FLOOD_SCOPE (63): Set/clear default region scope from the app.
    • \n
  • CMD_GET_DEFAULT_FLOOD_SCOPE (64): Returns current scope name and key.
    • \n
  • Push notifications: Channel messages, DM messages, send confirmations (acks), new adverts, and path updates are all pushed to the app in real time.
    • \n
\n

Channel Expansion

\n
    \n
  • Channel support expanded from 12 to 40 (MAX_GROUP_CHANNELS).
    • \n
  • Channel notification preferences array expanded to match (41 slots: 40 channels + 1 DM).
    • \n
  • Channel picker UI updated to support all 40 channels.
    • \n
  • Stack-local channel record arrays moved to heap allocation to prevent stack overflow.
    • \n
\n

Power Optimisation

\n
    \n
  • ICM20948 IMU: Put to sleep after init (~3mA saved).
    • \n
  • ES8311 audio codec: DAC, ADC, and PGA powered down after init. I2S channels disabled to release APB_FREQ_MAX PM locks. Woken on demand before playback, slept after stop (~5-10mA saved).
    • \n
  • I2S PM lock management: Added disable_channels() / enable_channels() to Hardware_Iis class so I2S driver PM locks are only held during active audio playback.
    • \n
  • DFS investigation: PM stats task added (enable via sdkconfig). Confirmed DSI display driver holds CPU_FREQ_MAX lock 97% of the time while screen is on, making CPU frequency reduction ineffective. ~172mA baseline is the hardware floor with display active.
    • \n
\n

UI Improvements

\n
    \n
  • Path display: Incoming message routes and outgoing heard-by lists reformatted as n\n…
    • \n
\n" }, { "version": "v0.3.8", "name": "v0.3.8", "datetime": "2026-05-27T02:36:17Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.3.8", "prerelease": true, "notes": "Pre-release.\r\n\r\nFeature release building on v0.3.6, adding position adverts, share position, path view, private channels, and voice/picture over LoRa infrastructure (disabled pending final integration).\r\n\r\n---\r\n\r\n## What's New\r\n\r\n### Position Adverts\r\n\r\nYour GPS position can now be encoded into outgoing adverts, allowing other nodes on the mesh to see your location on their Maps screen. Position is configured via a new **Settings > Position** sub-screen with three fields:\r\n\r\n- **Latitude / Longitude** (tap to edit) for manual entry in decimal degrees\r\n- **Share Position** (tap to cycle): Off / Manual / Auto-GPS\r\n\r\nIn Auto-GPS mode, the L76K GPS snapshot is polled every 15 minutes and the stored position is updated automatically whenever the fix changes. A **Copy Position** button is also available on the sub-screen.\r\n\r\n### Share Position\r\n\r\nThe **+** button on the channel messages and DM compose screens now includes a **Share Position** option. Tapping it sends your current lat/lon as a message to the active channel or conversation.\r\n\r\n### Path View and Message Actions\r\n\r\nLong-pressing an incoming message now opens **Path View**, which displays the routing path that message took through the mesh, showing each hop in the route.\r\n\r\nLong-pressing an outgoing message gives you the option to **Retry Send** if the message failed, or to see which repeaters acknowledged the message.\r\n\r\n### Private Channels\r\n\r\nChannels can now be public or private:\r\n\r\n- **Public channels** start with `#` (e.g. `#test`). The secret is derived via SHA-256 from the name, matching the standard MeshCore convention.\r\n- **Private channels** have no `#` prefix. A random 16-byte secret is generated at creation, so only invited users can join.\r\n\r\n**Sharing:** open **Settings > Channels**, tap the channel, then tap **Share Channel**. This opens a contact picker and sends the channel name and secret as a DM invitation. Recipients see a pending invite they can accept (tap) or dismiss (long-press).\r\n\r\n---\r\n\r\n### Voice over LoRa Infrastructure (Not Yet Enabled)\r\n\r\nThe full infrastructure for Codec2 1200bps voice messaging has been added to the firmware:\r\n\r\n- Codec2 ESP-IDF component (`components/codec2/`) wrapping drowe67/codec2 with only the core 1200bps mode compiled in\r\n- ES8311 microphone capture at native 44100 Hz I2S rate\r\n- VE3 protocol for chunked voice packet transfer\r\n- Recording buffer in PSRAM, staggered send timing\r\n- Voice UI: inbox with metadata persistence, record screen with Play/Discard/Send, previous recordings list, contact picker (favourites first), send status tracking\r\n- Playback at 85% volume via meck_audio_play_file\r\n\r\nVoice and Picture tiles are present on the home screen as placeholders but the features are disabled in this release pending final integration and testing.\r\n\r\n### Picture over LoRa Infrastructure (Not Yet Enabled)\r\n\r\nChunked image transfer protocol infrastructure has been added but is disabled in this release.\r\n\r\n### UI Changes\r\n\r\n- **Splash screen** updated with new design and progress bar\r\n- **Maps and Trace tile colours** swapped so there are no longer two adjacent red tiles on the home screen\r\n- **Home screen** expanded from seven tiles to nine (Voice and Camera placeholders added)\r\n- **MAX_GROUP_CHANNELS** bumped from 8 to 12\r\n\r\n---\r\n\r\n## First-Time Flashing: Read This First\r\n\r\nMeck-P4 ships as a single **merged binary** (bootloader + partition table + application combined). One file, flash at offset `0x0`.\r\n> **An SD card is recommended.** With a FAT32-formatted card inserted, every saved setting, channel message, DM, and room post is mirrored automatically, notification tones have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot and notification sounds won't be available.\r\n\r\nEnsure you use the **right-side USB-C port** (the data port), not the high-speed charger port, to flash.\r\n\"correctPre-release.

\n

Feature release building on v0.3.6, adding position adverts, share position, path view, private channels, and voice/picture over LoRa infrastructure (disabled pending final integration).

\n
\n

What's New

\n

Position Adverts

\n

Your GPS position can now be encoded into outgoing adverts, allowing other nodes on the mesh to see your location on their Maps screen. Position is configured via a new Settings > Position sub-screen with three fields:

\n
    \n
  • Latitude / Longitude (tap to edit) for manual entry in decimal degrees
    • \n
  • Share Position (tap to cycle): Off / Manual / Auto-GPS
    • \n
\n

In Auto-GPS mode, the L76K GPS snapshot is polled every 15 minutes and the stored position is updated automatically whenever the fix changes. A Copy Position button is also available on the sub-screen.

\n

Share Position

\n

The + button on the channel messages and DM compose screens now includes a Share Position option. Tapping it sends your current lat/lon as a message to the active channel or conversation.

\n

Path View and Message Actions

\n

Long-pressing an incoming message now opens Path View, which displays the routing path that message took through the mesh, showing each hop in the route.

\n

Long-pressing an outgoing message gives you the option to Retry Send if the message failed, or to see which repeaters acknowledged the message.

\n

Private Channels

\n

Channels can now be public or private:

\n
    \n
  • Public channels start with # (e.g. #test). The secret is derived via SHA-256 from the name, matching the standard MeshCore convention.
    • \n
  • Private channels have no # prefix. A random 16-byte secret is generated at creation, so only invited users can join.
    • \n
\n

Sharing: open Settings > Channels, tap the channel, then tap Share Channel. This opens a contact picker and sends the channel name and secret as a DM invitation. Recipients see a pending invite they can accept (tap) or dismiss (long-press).

\n
\n

Voice over LoRa Infrastructure (Not Yet Enabled)

\n

The full infrastructure for Codec2 1200bps voice messaging has been added to the firmware:

\n
    \n
  • Codec2 ESP-IDF component (components/codec2/) wrapping drowe67/codec2 with only the core 1200bps mode compiled in
    • \n
  • ES8311 microphone capture at native 44100 Hz I2S rate
    • \n
  • VE3 protocol for chunked voice packet transfer
    • \n
  • Recording buffer in PSRAM, staggered send timing
    • \n
  • Voice UI: inbox with metadata persistence, record screen with Play/Discard/Send, previous recordings list, contact picker (favourites first), send status tracking
    • \n
  • Playback at 85% volume via meck_audio_play_file
    • \n
\n

Voice and Picture tiles are present on the home screen as placeholders but the features are disabled in this release pending final integration and testing.

\n

Picture over LoRa Infrastructure (Not Yet Enabled)

\n

Chunked image transfer protocol infrastructure has been added but is disabled in this release.

\n

UI Changes

\n
    \n
  • Splash screen updated with new design and progress bar
    • \n
  • Maps and Trace tile colours swapped so there are no longer two adjacent red tiles on the home screen
    • \n
  • Home screen expanded from seven tiles to nine (Voice and Camera placeholders added)
    • \n
  • MAX_GROUP_CHANNELS bumped from 8 to 12
    • \n
\n
\n

First-Time Flashing: Read This First

\n

Meck-P4 ships as a single merged binary (bootloader + partition table + application combined). One file, flash at offset 0x0.

\n
\n

An SD card is recommended. With a FAT32-formatted card inserted, every saved setting, channel message, DM, and room post is mirrored automatically, notification tones have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot and notification sounds won't be available.

\n
\n

Ensure you use the right-side USB-C port (the data port), not the high-speed charger port, to flash.\n<img width=\"377\" height=\"284\" alt=\"correct \n…

\n" }, { "version": "v0.3.6", "name": "Meck-P4 v0.3.6: Custom Radio, Region Scope, Channels, Notification Sounds", "datetime": "2026-05-24T23:38:02Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.3.6", "prerelease": true, "notes": "Pre-release.\r\n\r\nFeature release building on v0.3.5.1, adding custom radio parameters, region scope support, a Channels settings sub-screen, and per-channel notification sounds.\r\n\r\n---\r\n\r\n## What's New\r\n\r\n### Custom Radio Parameters\r\n\r\nFrequency, Bandwidth, and Spreading Factor are now individually editable via text entry in Settings (tap the row, type the value, tap Confirm). Coding Rate cycles on tap (4/5 through 4/8). The Radio Preset row remains available and shows \"Custom\" whenever the current values don't match any of the 17 built-in presets. Selecting a preset populates all four fields; you can then tweak individual values without losing the rest.\r\n\r\nThis is primarily useful for users in regions where the community presets don't cover the exact parameters in use, such as parts of Europe running SR 5/6 with 32.5 kHz bandwidth, or anyone wanting to customise the coding rate independently.\r\n\r\n### Region Scope (MeshCore v1.15+ Compatibility)\r\n\r\nRegions limit how far your flood messages propagate through the mesh. When you set a region, outgoing messages are tagged with a transport code that repeaters use to decide whether to forward them. Messages sent without a region reach all repeaters via the default wildcard, same as always.\r\n\r\n**Setting your device region:**\r\n- Open **Settings**, tap **Default Region**, enter your region name (e.g. `au-nsw`), tap **Confirm**\r\n- Leave empty for unscoped (legacy behaviour, reaches all repeaters)\r\n\r\n**Per-channel region:** Open **Settings > Channels**, tap a channel, then tap **Region Scope** to set an override for that specific channel. Empty uses the device default.\r\n\r\n**Finding your region name:** Region names are determined by your local mesh community. Check with your local group, or browse the community region registry at [regions.meshcore.nz](https://regions.meshcore.nz/) for names already in use. Common patterns follow ISO 3166 codes (e.g. `au` for Australia, `au-nsw`, `gb-eng`, `us-ca`), but communities may also use custom names. Names must be lowercase alphanumeric characters and hyphens, max 30 characters. You can also create your own custom regions on repeaters you manage (see Repeater Admin below).\r\n\r\n**Note:** Region scoping requires repeaters in your area to be running MeshCore v1.10+ with the appropriate regions configured. If no repeaters have region filtering enabled, scoped and unscoped messages behave identically.\r\n\r\n### Repeater Admin: Region Management via CLI\r\n\r\nRepeaters running MeshCore v1.10+ support full region management through the Cmd Line screen in Repeater Admin. Log in to a repeater, tap **Cmd Line**, and use the following commands:\r\n\r\n| Command | Description |\r\n| --- | --- |\r\n| `region put [parent]` | Create a new region (optional parent for nesting) |\r\n| `region remove ` | Remove a region (remove children first) |\r\n| `region allowf ` | Allow flooding for a region |\r\n| `region denyf ` | Block flooding for a region |\r\n| `region get ` | Show info for a region |\r\n| `region home` / `region home ` | View or set the repeater's home region |\r\n| `region default` / `region default ` | View or set the repeater's default scope |\r\n| `region save` | Persist region changes to the repeater's flash |\r\n| `region list allowed` / `region list denied` | View regions (repeater firmware 1.12+) |\r\n| `region load [F]` | Single-line region load (append `F` to allow flooding) |\r\n\r\n**Not supported:** The interactive multi-line `region load` (without parameters) requires a serial terminal and is not available on the P4, which does not currently support serial CLI commands. Use individual `region put` and `region allowf` commands instead.\r\n\r\n**Quick start example** (setting up a repeater for the `au-nsw` region):\r\n```\r\nregion put au-nsw\r\nregion allowf au-nsw\r\nregion home au-nsw\r\nregion save\r\n```\r\n\r\nFor full documentation and nested region examples, see the [MeshCore CLI docs](https://docs.meshcore.io/cli_commands/#region-management-v1\n…", "notesHtml": "

Pre-release.

\n

Feature release building on v0.3.5.1, adding custom radio parameters, region scope support, a Channels settings sub-screen, and per-channel notification sounds.

\n
\n

What's New

\n

Custom Radio Parameters

\n

Frequency, Bandwidth, and Spreading Factor are now individually editable via text entry in Settings (tap the row, type the value, tap Confirm). Coding Rate cycles on tap (4/5 through 4/8). The Radio Preset row remains available and shows \"Custom\" whenever the current values don't match any of the 17 built-in presets. Selecting a preset populates all four fields; you can then tweak individual values without losing the rest.

\n

This is primarily useful for users in regions where the community presets don't cover the exact parameters in use, such as parts of Europe running SR 5/6 with 32.5 kHz bandwidth, or anyone wanting to customise the coding rate independently.

\n

Region Scope (MeshCore v1.15+ Compatibility)

\n

Regions limit how far your flood messages propagate through the mesh. When you set a region, outgoing messages are tagged with a transport code that repeaters use to decide whether to forward them. Messages sent without a region reach all repeaters via the default wildcard, same as always.

\n

Setting your device region:

\n
    \n
  • Open Settings, tap Default Region, enter your region name (e.g. au-nsw), tap Confirm
    • \n
  • Leave empty for unscoped (legacy behaviour, reaches all repeaters)
    • \n
\n

Per-channel region: Open Settings > Channels, tap a channel, then tap Region Scope to set an override for that specific channel. Empty uses the device default.

\n

Finding your region name: Region names are determined by your local mesh community. Check with your local group, or browse the community region registry at regions.meshcore.nz for names already in use. Common patterns follow ISO 3166 codes (e.g. au for Australia, au-nsw, gb-eng, us-ca), but communities may also use custom names. Names must be lowercase alphanumeric characters and hyphens, max 30 characters. You can also create your own custom regions on repeaters you manage (see Repeater Admin below).

\n

Note: Region scoping requires repeaters in your area to be running MeshCore v1.10+ with the appropriate regions configured. If no repeaters have region filtering enabled, scoped and unscoped messages behave identically.

\n

Repeater Admin: Region Management via CLI

\n

Repeaters running MeshCore v1.10+ support full region management through the Cmd Line screen in Repeater Admin. Log in to a repeater, tap Cmd Line, and use the following commands:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
CommandDescription
region put <name> [parent]Create a new region (optional parent for nesting)
region remove <name>Remove a region (remove children first)
region allowf <name>Allow flooding for a region
region denyf <name>Block flooding for a region
region get <name>Show info for a region
region home / region home <name>View or set the repeater's home region
region default / region default <name>View or set the repeater's default scope
region savePersist region changes to the repeater's flash
region list allowed / region list deniedView regions (repeater firmware 1.12+)
region load <name> [F]Single-line region load (append F to allow flooding)
\n

Not supported: The interactive multi-line region load (without parameters) requires a serial terminal and is not available on the P4, which does not currently support serial CLI commands. Use individual region put and region allowf commands instead.

\n

Quick start example (setting up a repeater for the au-nsw region):

\n
region put au-nsw\nregion allowf au-nsw\nregion home au-nsw\nregion save\n
\n

For full documentation and nested region examples, see the [MeshCore CLI docs](https://docs.meshcore.io/cli_commands/#region-management-v1\n…

\n" }, { "version": "v0.3.5.1", "name": "Meck-P4 v0.3.5.1: Contacts list fixes", "datetime": "2026-05-22T19:34:27Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.3.5.1", "prerelease": true, "notes": "Pre-release.\r\n\r\nPatch release on top of v0.3.5, fixing three bugs in the Contacts screen:\r\n\r\n- **200-row cap removed.** The contacts list previously stopped rendering after 200 matched rows. With 200+ contacts this hid recently-added repeaters from the list entirely (including, in one reproducible case, a freshly-added Repeater that Discover claimed to have added but which was nowhere to be seen). The list now displays every matching contact.\r\n- **Sorted by recency.** Contacts now appear newest-first instead of in creation order. The sort key is local activity time (advert receipt, message send, or message receive), so the most recently active contacts sit at the top of the list regardless of which filter is active.\r\n- **Sort key corrected.** Initial attempt used `last_advert_timestamp`, which is the *sender's claimed clock* embedded in the advert payload rather than our reception time. That gave nonsense ordering: nodes with forward-dated clocks (stale build epoch, mis-set NTP, etc.) sat permanently at the top, and nodes whose clocks were stuck or behind had their adverts silently dropped by the upstream replay-attack guard and sank to the bottom. The fix sorts by `lastmod` (our local RTC time at last contact activity) with an override in `onAdvertRecv` so `lastmod` is updated on every advert receipt regardless of whether the upstream replay guard early-returned.\r\n\r\nNo other behavioural changes from v0.3.5.\r\n\r\n## First-Time Flashing: Read This First\r\n\r\n(Same as v0.3.5 — skip this section if you've already flashed v0.3.5; the contacts fixes carry over via the usual upgrade path.)\r\n\r\nMeck-P4 ships as a single **merged binary** (bootloader + partition table + application combined). One file, flash at offset `0x0`.\r\n\r\n> **An SD card is recommended.** With a FAT32-formatted card inserted, every saved setting, channel message, DM, and room post is mirrored automatically, audio files have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot.\r\n\r\nEnsure you use the **right-side USB-C port** (the data port), not the high-speed charger port, to flash.\r\n\"correct\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to \r\n2. Scroll to the bottom and select **Custom Firmware**\r\n3. Select the `meck-p4-0.3.5.1-version-merged.bin` file you downloaded\r\n4. Click OK on the merged-binary warning\r\n5. Click **Flash**, pick your device in the popup, and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\n```\r\npip install esptool\r\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.3.5.1-version-merged.bin\r\n```\r\n\r\n(Replace `PORT` with `/dev/cu.usbmodemXXXX` on macOS, `/dev/ttyACM0` on Linux, or `COM3` on Windows.)\r\n\r\nUpgrading from v0.3.5 or v0.3.3 does not require `erase_flash`. The prefs loader continues to tolerate older shorter-blob layouts, so any new fields come up at default rather than wiping existing settings.\r\n\r\n> ⚠️ **AMOLED variant remains untested by the maintainer.** The `-amoled.bin` is built from the same source tree with the AMOLED display option selected in menuconfig, but the project maintainer doesn't have the AMOLED hardware on hand. The TFT variant is the tested and known-working build.\r\n\r\n## Known Limitations\r\n\r\nCarried over unchanged from v0.3.5:\r\n\r\n- **Background audio playback has known issues — not recommended for general use yet.** A blue `>>` glyph was added to the top bar to indicate when the audio player is actively playing, mirrored across every home tile and full screen. However, the broader background-playback experience has a number of unresolved bugs: tapping the Audio tile while a track is playing doesn't jump back to the Now Playing screen (so pausing requires navigating back to the file manually), and starting a second \n…", "notesHtml": "

Pre-release.

\n

Patch release on top of v0.3.5, fixing three bugs in the Contacts screen:

\n
    \n
  • 200-row cap removed. The contacts list previously stopped rendering after 200 matched rows. With 200+ contacts this hid recently-added repeaters from the list entirely (including, in one reproducible case, a freshly-added Repeater that Discover claimed to have added but which was nowhere to be seen). The list now displays every matching contact.
    • \n
  • Sorted by recency. Contacts now appear newest-first instead of in creation order. The sort key is local activity time (advert receipt, message send, or message receive), so the most recently active contacts sit at the top of the list regardless of which filter is active.
    • \n
  • Sort key corrected. Initial attempt used last_advert_timestamp, which is the sender's claimed clock embedded in the advert payload rather than our reception time. That gave nonsense ordering: nodes with forward-dated clocks (stale build epoch, mis-set NTP, etc.) sat permanently at the top, and nodes whose clocks were stuck or behind had their adverts silently dropped by the upstream replay-attack guard and sank to the bottom. The fix sorts by lastmod (our local RTC time at last contact activity) with an override in onAdvertRecv so lastmod is updated on every advert receipt regardless of whether the upstream replay guard early-returned.
    • \n
\n

No other behavioural changes from v0.3.5.

\n

First-Time Flashing: Read This First

\n

(Same as v0.3.5 — skip this section if you've already flashed v0.3.5; the contacts fixes carry over via the usual upgrade path.)

\n

Meck-P4 ships as a single merged binary (bootloader + partition table + application combined). One file, flash at offset 0x0.

\n
\n

An SD card is recommended. With a FAT32-formatted card inserted, every saved setting, channel message, DM, and room post is mirrored automatically, audio files have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot.

\n
\n

Ensure you use the right-side USB-C port (the data port), not the high-speed charger port, to flash.\n\"correct

\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.io/
    2. \n
  2. Scroll to the bottom and select Custom Firmware
    3. \n
  3. Select the meck-p4-0.3.5.1-version-merged.bin file you downloaded
    4. \n
  4. Click OK on the merged-binary warning
    5. \n
  5. Click Flash, pick your device in the popup, and click Connect
    6. \n
\n

Flashing with esptool.py

\n
pip install esptool\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.3.5.1-version-merged.bin\n
\n

(Replace PORT with /dev/cu.usbmodemXXXX on macOS, /dev/ttyACM0 on Linux, or COM3 on Windows.)

\n

Upgrading from v0.3.5 or v0.3.3 does not require erase_flash. The prefs loader continues to tolerate older shorter-blob layouts, so any new fields come up at default rather than wiping existing settings.

\n
\n

⚠️ AMOLED variant remains untested by the maintainer. The -amoled.bin is built from the same source tree with the AMOLED display option selected in menuconfig, but the project maintainer doesn't have the AMOLED hardware on hand. The TFT variant is the tested and known-working build.

\n
\n

Known Limitations

\n

Carried over unchanged from v0.3.5:

\n
    \n
  • Background audio playback has known issues — not recommended for general use yet. A blue >> glyph was added to the top bar to indicate when the audio player is actively playing, mirrored across every home tile and full screen. However, the broader background-playback experience has a number of unresolved bugs: tapping the Audio tile while a track is playing doesn't jump back to the Now Playing screen (so pausing requires navigating back to the file manually), and starting a second \n…
    • \n
\n" }, { "version": "v0.3.5", "name": "Meck-P4 v0.3.5: Direct Messaging, Repeater Admin, Room servers & Maps", "datetime": "2026-05-21T09:56:27Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.3.5", "prerelease": true, "notes": "Direct messaging arrives in v0.3.5 — compose, send, receive, and persist DMs from any companion contact, with unread badges viewable in the channel list. Room server support and repeater admin land alongside, giving you logged-in access to room post history and the full status/CLI/settings interface for remote repeater management. A new map screen renders OSM slippy tiles from the SD card with a GPS dot, contact markers, and pan/zoom. Plus a per-contact path editor, a standalone trace route screen, a keyboard layout overhaul, a GPS time-sync fix, debug logs to SD, and config export to a MeshCore-app-compatible JSON file.\r\n\r\n> ⚠️ **Still a pre-release.** ⚠️ Web browser, IRC, and the BLE/WiFi companion path are still not in this build. See What's Not Yet Implemented for the full pending list.\r\n\r\n## First-Time Flashing: Read This First\r\n\r\nMeck-P4 ships as a single **merged binary** (bootloader + partition table + application combined). One file, flash at offset `0x0`.\r\n\r\n> **An SD card is recommended.** With a FAT32-formatted card inserted, every saved setting, channel message, DM, and room post is mirrored automatically, audio files have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot.\r\n\r\nEnsure you use the **right-side USB-C port** (the data port), not the high-speed charger port, to flash.\r\n\"correct\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to \r\n2. Scroll to the bottom and select **Custom Firmware**\r\n3. Select the `meck-p4-0.3.5-version-merged.bin` file you downloaded\r\n4. Click OK on the merged-binary warning\r\n5. Click **Flash**, pick your device in the popup, and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\n```\r\npip install esptool\r\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.3.5-version-merged.bin\r\n```\r\n\r\n(Replace `PORT` with `/dev/cu.usbmodemXXXX` on macOS, `/dev/ttyACM0` on Linux, or `COM3` on Windows.)\r\n\r\nUpgrading from v0.3.3 does not require `erase_flash`. The prefs loader continues to tolerate older shorter-blob layouts, so any new fields come up at default rather than wiping existing settings.\r\n\r\n> ⚠️ **AMOLED variant remains untested by the maintainer.** The `-amoled.bin` is built from the same source tree with the AMOLED display option selected in menuconfig, but the project maintainer doesn't have the AMOLED hardware on hand. The TFT variant is the tested and known-working build.\r\n\r\n## What's New Since v0.3.3\r\n\r\n### Direct Messaging\r\n\r\nOpen a companion contact's detail screen (from the Contacts menu tile on the home screen) and tap the cyan **Send DM** button (stacked above the red Delete button) to compose. The DM conversation view uses the standard chat layout — keyboard on the bottom half, message bubbles scrolling above.\r\n\r\n- Per-contact 20-message ring buffers in PSRAM, lazy-allocated so unused contacts cost nothing\r\n- Per-contact DM history persisted to SD and reloaded on boot\r\n- DM Inbox row in the channel picker shows a per-contact unread badge, refreshed every tick\r\n- Send-side ACK tracking — outgoing bubbles update from \"Sending...\" through to \"Delivered\" or \"Failed\" as the ACK round-trip completes\r\n\r\n### Room Server Support\r\n\r\nTap a Room-type contact to open the same admin login flow as repeaters. On successful login, the room's post timeline appears as a scrollable bubble list, left-aligned, with the author name above each bubble and a timestamp and hop count footer below.\r\n\r\n- Post history persisted per-room to SD and loaded on boot, so you don't need to re-login to see what's already been received\r\n- Live re-render: posts arriving while you're sitting on the room view land in the bubble list without leaving the screen\r\n- Author resolution walks your contacts looking for a matc\n…", "notesHtml": "

Direct messaging arrives in v0.3.5 — compose, send, receive, and persist DMs from any companion contact, with unread badges viewable in the channel list. Room server support and repeater admin land alongside, giving you logged-in access to room post history and the full status/CLI/settings interface for remote repeater management. A new map screen renders OSM slippy tiles from the SD card with a GPS dot, contact markers, and pan/zoom. Plus a per-contact path editor, a standalone trace route screen, a keyboard layout overhaul, a GPS time-sync fix, debug logs to SD, and config export to a MeshCore-app-compatible JSON file.

\n
\n

⚠️ Still a pre-release. ⚠️ Web browser, IRC, and the BLE/WiFi companion path are still not in this build. See What's Not Yet Implemented for the full pending list.

\n
\n

First-Time Flashing: Read This First

\n

Meck-P4 ships as a single merged binary (bootloader + partition table + application combined). One file, flash at offset 0x0.

\n
\n

An SD card is recommended. With a FAT32-formatted card inserted, every saved setting, channel message, DM, and room post is mirrored automatically, audio files have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot.

\n
\n

Ensure you use the right-side USB-C port (the data port), not the high-speed charger port, to flash.\n\"correct

\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.io/
    2. \n
  2. Scroll to the bottom and select Custom Firmware
    3. \n
  3. Select the meck-p4-0.3.5-version-merged.bin file you downloaded
    4. \n
  4. Click OK on the merged-binary warning
    5. \n
  5. Click Flash, pick your device in the popup, and click Connect
    6. \n
\n

Flashing with esptool.py

\n
pip install esptool\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.3.5-version-merged.bin\n
\n

(Replace PORT with /dev/cu.usbmodemXXXX on macOS, /dev/ttyACM0 on Linux, or COM3 on Windows.)

\n

Upgrading from v0.3.3 does not require erase_flash. The prefs loader continues to tolerate older shorter-blob layouts, so any new fields come up at default rather than wiping existing settings.

\n
\n

⚠️ AMOLED variant remains untested by the maintainer. The -amoled.bin is built from the same source tree with the AMOLED display option selected in menuconfig, but the project maintainer doesn't have the AMOLED hardware on hand. The TFT variant is the tested and known-working build.

\n
\n

What's New Since v0.3.3

\n

Direct Messaging

\n

Open a companion contact's detail screen (from the Contacts menu tile on the home screen) and tap the cyan Send DM button (stacked above the red Delete button) to compose. The DM conversation view uses the standard chat layout — keyboard on the bottom half, message bubbles scrolling above.

\n
    \n
  • Per-contact 20-message ring buffers in PSRAM, lazy-allocated so unused contacts cost nothing
    • \n
  • Per-contact DM history persisted to SD and reloaded on boot
    • \n
  • DM Inbox row in the channel picker shows a per-contact unread badge, refreshed every tick
    • \n
  • Send-side ACK tracking — outgoing bubbles update from \"Sending...\" through to \"Delivered\" or \"Failed\" as the ACK round-trip completes
    • \n
\n

Room Server Support

\n

Tap a Room-type contact to open the same admin login flow as repeaters. On successful login, the room's post timeline appears as a scrollable bubble list, left-aligned, with the author name above each bubble and a timestamp and hop count footer below.

\n
    \n
  • Post history persisted per-room to SD and loaded on boot, so you don't need to re-login to see what's already been received
    • \n
  • Live re-render: posts arriving while you're sitting on the room view land in the bubble list without leaving the screen
    • \n
  • Author resolution walks your contacts looking for a matc\n…
    • \n
\n" }, { "version": "v0.3.3", "name": "Meck-P4 v0.3.3: MeshCore Config Import, BQ27220 Calibration, UI Polish", "datetime": "2026-05-18T02:47:07Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.3.3", "prerelease": true, "notes": "One-step config import from the MeshCore mobile app so existing users can move to a P4 without re-entering everything, a firmware-side fix for the BQ27220 fuel gauge calibration so the battery percentage matches reality, and substantial UI work on the home screen, Settings, and tile layouts. Plus a small power-savings pass that trims about 38 mA off idle draw.\r\n\r\n> ⚠️ **Still a pre-release.** ⚠️ Direct messaging, roomserver access, repeater admin, trace route, web browser, IRC, and the BLE companion path are still not in this build. See What's Not Yet Implemented for the full pending list.\r\n\r\n## First-Time Flashing: Read This First\r\n\r\nMeck-P4 ships as a single **merged binary** (bootloader + partition table + application combined). One file, flash at offset `0x0`.\r\n\r\n> **An SD card is recommended.** With a FAT32-formatted card inserted, every saved setting and channel message is mirrored automatically, audio files have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot.\r\n\r\nEnsure you use the **right-side USB-C port** (the data port), not the high-speed charger port, to flash.\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to https://flasher.meshcore.io/\r\n2. Scroll to the bottom and select **Custom Firmware**\r\n3. Select the `meck-p4-0.3.3-version-merged.bin` file you downloaded\r\n4. Click OK on the merged-binary warning\r\n5. Click **Flash**, pick your device in the popup, and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\n```\r\npip install esptool\r\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.3.3-version-merged.bin\r\n```\r\n\r\n(Replace `PORT` with `/dev/cu.usbmodemXXXX` on macOS, `/dev/ttyACM0` on Linux, or `COM3` on Windows.)\r\n\r\nUpgrading from v0.3 does not require `erase_flash`. The prefs loader has been made tolerant of older shorter-blob layouts, so any new fields added in v0.3.3 (such as Font Size) come up at default rather than wiping existing settings.\r\n\r\n> ⚠️ **AMOLED variant remains untested by the maintainer.** The `-amoled.bin` is built from the same source tree with the AMOLED display option selected in menuconfig, but the project maintainer doesn't have the AMOLED hardware on hand. The TFT variant is the tested and known-working build.\r\n\r\n## What's New Since v0.3\r\n\r\n### MeshCore App Config Import\r\n\r\nDrop your MeshCore mobile or desktop app config export onto the SD card, reboot, and your identity, channels, contacts, node name, and radio settings come across in one step. No more re-entering contacts or generating a fresh keypair when moving to the P4.\r\n\r\nHow to use:\r\n\r\n1. In the MeshCore mobile or desktop app, export your config as JSON\r\n2. Rename to `import.json` and copy to `/sdcard/meshcore/import.json` on the P4's SD card\r\n3. Reboot the device\r\n\r\nOn boot, Meck reads the file and applies it:\r\n\r\n| Field | Behaviour |\r\n|---|---|\r\n| Identity (private + public key) | Replaces `_main.id` atomically (tmp + rename). Existing identity is overwritten. |\r\n| Channels | Merged by 16-byte secret. Existing channels kept; new ones appended to free slots; duplicates skipped. |\r\n| Contacts | Merged by public key. Existing kept; new ones appended. Lat/lon converted from string-decimal to int32 e7. `custom_name` preferred over `name`. |\r\n| Node name | Replaces `prefs.node_name`. |\r\n| Radio settings | Replaces freq, BW, SF, CR, TX power on `P4NodePrefs`. Freq converted kHz to MHz, BW Hz to kHz. |\r\n\r\nOn success the file is moved to `/sdcard/meshcore/import.history/import-.json` so it doesn't re-apply on subsequent boots and leaves an audit trail. On parse failure (bad JSON, missing identity keys, wrong-length hex) a warning is logged and the file is left in place for inspection.\r\n\r\nImported names (node, channels, contacts) are stripped to printable ASCII before being stored. Meck-P4's Montserrat fonts cover Latin-1 only, so emoji codepoints would otherwise render as tofu boxes. Leading an\n…", "notesHtml": "

One-step config import from the MeshCore mobile app so existing users can move to a P4 without re-entering everything, a firmware-side fix for the BQ27220 fuel gauge calibration so the battery percentage matches reality, and substantial UI work on the home screen, Settings, and tile layouts. Plus a small power-savings pass that trims about 38 mA off idle draw.

\n
\n

⚠️ Still a pre-release. ⚠️ Direct messaging, roomserver access, repeater admin, trace route, web browser, IRC, and the BLE companion path are still not in this build. See What's Not Yet Implemented for the full pending list.

\n
\n

First-Time Flashing: Read This First

\n

Meck-P4 ships as a single merged binary (bootloader + partition table + application combined). One file, flash at offset 0x0.

\n
\n

An SD card is recommended. With a FAT32-formatted card inserted, every saved setting and channel message is mirrored automatically, audio files have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot.

\n
\n

Ensure you use the right-side USB-C port (the data port), not the high-speed charger port, to flash.

\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.io/
    2. \n
  2. Scroll to the bottom and select Custom Firmware
    3. \n
  3. Select the meck-p4-0.3.3-version-merged.bin file you downloaded
    4. \n
  4. Click OK on the merged-binary warning
    5. \n
  5. Click Flash, pick your device in the popup, and click Connect
    6. \n
\n

Flashing with esptool.py

\n
pip install esptool\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.3.3-version-merged.bin\n
\n

(Replace PORT with /dev/cu.usbmodemXXXX on macOS, /dev/ttyACM0 on Linux, or COM3 on Windows.)

\n

Upgrading from v0.3 does not require erase_flash. The prefs loader has been made tolerant of older shorter-blob layouts, so any new fields added in v0.3.3 (such as Font Size) come up at default rather than wiping existing settings.

\n
\n

⚠️ AMOLED variant remains untested by the maintainer. The -amoled.bin is built from the same source tree with the AMOLED display option selected in menuconfig, but the project maintainer doesn't have the AMOLED hardware on hand. The TFT variant is the tested and known-working build.

\n
\n

What's New Since v0.3

\n

MeshCore App Config Import

\n

Drop your MeshCore mobile or desktop app config export onto the SD card, reboot, and your identity, channels, contacts, node name, and radio settings come across in one step. No more re-entering contacts or generating a fresh keypair when moving to the P4.

\n

How to use:

\n
    \n
  1. In the MeshCore mobile or desktop app, export your config as JSON
    2. \n
  2. Rename to import.json and copy to /sdcard/meshcore/import.json on the P4's SD card
    3. \n
  3. Reboot the device
    4. \n
\n

On boot, Meck reads the file and applies it:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
FieldBehaviour
Identity (private + public key)Replaces _main.id atomically (tmp + rename). Existing identity is overwritten.
ChannelsMerged by 16-byte secret. Existing channels kept; new ones appended to free slots; duplicates skipped.
ContactsMerged by public key. Existing kept; new ones appended. Lat/lon converted from string-decimal to int32 e7. custom_name preferred over name.
Node nameReplaces prefs.node_name.
Radio settingsReplaces freq, BW, SF, CR, TX power on P4NodePrefs. Freq converted kHz to MHz, BW Hz to kHz.
\n

On success the file is moved to /sdcard/meshcore/import.history/import-<unix_epoch>.json so it doesn't re-apply on subsequent boots and leaves an audit trail. On parse failure (bad JSON, missing identity keys, wrong-length hex) a warning is logged and the file is left in place for inspection.

\n

Imported names (node, channels, contacts) are stripped to printable ASCII before being stored. Meck-P4's Montserrat fonts cover Latin-1 only, so emoji codepoints would otherwise render as tofu boxes. Leading an\n…

\n" }, { "version": "v0.3", "name": "Meck-P4 v0.3 -- Audio Player, Active Discovery, Internationalised Keyboard", "datetime": "2026-05-16T03:53:52Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.3", "prerelease": true, "notes": "The third Meck-P4 pre-release. Audio playback from SD, active zero-hop neighbour discovery with one-tap contact add, and a substantially upgraded virtual keyboard with light/dark theme, three physical layouts, and long-press accent input for French and Czech. Plus per-message hop and ACK metadata, and a fix for the battery cell capacity (which had been wrong since v0.1).\r\n\r\n> **⚠️ Still a pre-release.⚠️ ** Direct messaging, roomserver access, repeater admin, trace route, web browser, IRC, and the BLE companion path are still not in this build. See [What's Not Yet Implemented](#whats-not-yet-implemented) for the full pending list.\r\n\r\n---\r\n\r\n## First-Time Flashing -- Read This First\r\n\r\nMeck-P4 ships as a single **merged binary** (bootloader + partition table + application combined). One file, flash at offset `0x0`.\r\n\r\n> **An SD card is recommended.** With a FAT32-formatted card inserted, every saved setting and channel message is mirrored automatically, audio files have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot.\r\n\"correct\r\n\r\nEnsure you use the right-side USB-C port (the data port), not the high-speed charger port, to flash.\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go to \r\n2. Scroll to the bottom and select **Custom Firmware**\r\n3. Select the `meck-p4-0.3-version-merged.bin` file you downloaded\r\n4. Click OK on the merged-binary warning\r\n5. Click **Flash**, pick your device in the popup, and click **Connect**\r\n\r\n### Flashing with esptool.py\r\n\r\n```\r\npip install esptool\r\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.3-version-merged.bin\r\n```\r\n\r\n(Replace `PORT` with `/dev/cu.usbmodemXXXX` on macOS, `/dev/ttyACM0` on Linux, or `COM3` on Windows.)\r\n\r\nIf you're upgrading from v0.1 and want to start with clean defaults, run `esptool.py --chip esp32p4 -p PORT erase_flash` before the write. Your contacts and prefs will be restored from the SD card mirror on first boot.\r\n\r\n> ⚠️ AMOLED variant is untested. The -amoled.bin is built from the same source tree with the AMOLED display option selected in menuconfig, but the project maintainer doesn't have the AMOLED hardware on hand and hasn't been able to flash or run it. Community members are currently testing it. If you have an AMOLED board, please report back via the [MeshCore Discord](https://discord.com/channels/1495203904898728149/1500323702859104457) or a GitHub issue with whether it boots, the display works, and touch works. The TFT variant is the tested and known-working build.\r\n\r\n---\r\n\r\n## What's New Since v0.1\r\n\r\n### Audio Player\r\n\r\nMP3 playback directly from the SD card. Two top-level subtrees give the player different defaults so music and audiobooks behave appropriately:\r\n\r\n| Subtree | Defaults |\r\n| --- | --- |\r\n| `/sdcard/audio/music/` | Standard playback. Resume bookmark off. |\r\n| `/sdcard/audio/audiobooks/` | Audiobook mode. Resume bookmark on, sleep timer available, position tracked through the playlist. |\r\n\r\n**How to use the audio player:**\r\n\r\n1. Drop your `music/` and `audiobooks/` folders into `/sdcard/audio/` on the SD card (the firmware creates the subtree automatically on first boot if it doesn't exist)\r\n2. Insert the card and power on\r\n3. Tap the **Audio** tile on the home grid to open the browser\r\n4. Navigate to a track and tap to play\r\n5. Use the transport row on the Now Playing screen for skip / play-pause / volume\r\n\r\n> **Read the [audio player guide](https://github.com/pelgraine/Meck-P4/blob/main/information/Meck%20Docs/audioplayerguide.md) before copying files to your SD card.** MP3s with large embedded album art can starve the IDLE task on first decode and trigger a watchdog reboot. The guide walks through the `tools/mp3_clean.py` script that strip\n…", "notesHtml": "

The third Meck-P4 pre-release. Audio playback from SD, active zero-hop neighbour discovery with one-tap contact add, and a substantially upgraded virtual keyboard with light/dark theme, three physical layouts, and long-press accent input for French and Czech. Plus per-message hop and ACK metadata, and a fix for the battery cell capacity (which had been wrong since v0.1).

\n
\n

**⚠️ Still a pre-release.⚠️ ** Direct messaging, roomserver access, repeater admin, trace route, web browser, IRC, and the BLE companion path are still not in this build. See What's Not Yet Implemented for the full pending list.

\n
\n
\n

First-Time Flashing -- Read This First

\n

Meck-P4 ships as a single merged binary (bootloader + partition table + application combined). One file, flash at offset 0x0.

\n
\n

An SD card is recommended. With a FAT32-formatted card inserted, every saved setting and channel message is mirrored automatically, audio files have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot.

\n\"correct
\n

Ensure you use the right-side USB-C port (the data port), not the high-speed charger port, to flash.

\n

Flashing with the MeshCore Web Flasher (recommended)

\n
    \n
  1. Go to https://flasher.meshcore.io/
    2. \n
  2. Scroll to the bottom and select Custom Firmware
    3. \n
  3. Select the meck-p4-0.3-version-merged.bin file you downloaded
    4. \n
  4. Click OK on the merged-binary warning
    5. \n
  5. Click Flash, pick your device in the popup, and click Connect
    6. \n
\n

Flashing with esptool.py

\n
pip install esptool\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.3-version-merged.bin\n
\n

(Replace PORT with /dev/cu.usbmodemXXXX on macOS, /dev/ttyACM0 on Linux, or COM3 on Windows.)

\n

If you're upgrading from v0.1 and want to start with clean defaults, run esptool.py --chip esp32p4 -p PORT erase_flash before the write. Your contacts and prefs will be restored from the SD card mirror on first boot.

\n
\n

⚠️ AMOLED variant is untested. The -amoled.bin is built from the same source tree with the AMOLED display option selected in menuconfig, but the project maintainer doesn't have the AMOLED hardware on hand and hasn't been able to flash or run it. Community members are currently testing it. If you have an AMOLED board, please report back via the MeshCore Discord or a GitHub issue with whether it boots, the display works, and touch works. The TFT variant is the tested and known-working build.

\n
\n
\n

What's New Since v0.1

\n

Audio Player

\n

MP3 playback directly from the SD card. Two top-level subtrees give the player different defaults so music and audiobooks behave appropriately:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
SubtreeDefaults
/sdcard/audio/music/Standard playback. Resume bookmark off.
/sdcard/audio/audiobooks/Audiobook mode. Resume bookmark on, sleep timer available, position tracked through the playlist.
\n

How to use the audio player:

\n
    \n
  1. Drop your music/ and audiobooks/ folders into /sdcard/audio/ on the SD card (the firmware creates the subtree automatically on first boot if it doesn't exist)
    2. \n
  2. Insert the card and power on
    3. \n
  3. Tap the Audio tile on the home grid to open the browser
    4. \n
  4. Navigate to a track and tap to play
    5. \n
  5. Use the transport row on the Now Playing screen for skip / play-pause / volume
    6. \n
\n
\n

Read the audio player guide before copying files to your SD card. MP3s with large embedded album art can starve the IDLE task on first decode and trigger a watchdog reboot. The guide walks through the tools/mp3_clean.py script that strip\n…

\n
\n" }, { "version": "v0.1", "name": "Meck-P4 v0.1 — First Pre-Release for the LilyGo T-Display P4", "datetime": "2026-05-09T08:14:03Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.1", "prerelease": true, "notes": "The first publicly flashable Meck firmware for the LilyGo T-Display P4. One\r\nfile, one offset, you're on the mesh.\r\n\r\n> **⚠️ This is a pre-release, not a finished product.** Many of the features people associate with Meck on the T-Deck Pro and T5S3 — direct messaging, roomserver access, repeater admin, trace route, web browser, IRC, audio player — are **not yet implemented** on the P4. What's here is the foundation: a fully functional MeshCore node with channel messaging, contacts, persistent storage, GPS, and battery monitoring. See the [full feature list and roadmap](https://github.com/pelgraine/Meck-P4#road-map--to-do).\r\n\r\n---\r\n\r\n## Hardware\r\n\r\n⚠️ LilyGo T-Display P4 (TFT version)⚠️ **The AMOLED variant has not been tested** but should be close — adjust the display init in\r\n`main/examples/lvgl_9_ui/main.cpp` if you want to try it.\r\n\r\n## Flashing\r\n\"IMG_2838\"\r\n\r\n\r\nEnsure you use the right-usb C port, ie **not** the high-speed charger port to flash.\r\n\r\nThe release file `meck-p4-0.1-merged.bin` is a **merged binary** containing the bootloader, partition table, and application combined into a single image — flash it at address `0x0`.\r\n\r\n**Using the MeshCore Flasher (web-based):**\r\n\r\n1. Go to \r\n2. Scroll to the bottom and select **Custom Firmware**\r\n3. Select the `meck-p4-0.1.bin` file you downloaded\r\n4. Click OK for the warning about erase files because it's a merged binary.\r\n5. Click **Flash**, choose your device in the popup, and click **Connect**\r\n\r\n**Using esptool.py:**\r\n\r\n```\r\npip install esptool\r\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.1.bin\r\n```\r\n\r\n(Replace `PORT` with `/dev/cu.usbmodemXXXX` on macOS, `/dev/ttyACM0` on Linux, or `COM3` on Windows.)\r\n\r\nIf you've previously had something else on the device, run `esptool.py --chip esp32p4 -p PORT erase_flash` first to clear NVS so Meck starts with clean defaults.\r\n\r\n> **An SD card is recommended.** With a FAT32-formatted card inserted, every saved setting and channel message is mirrored automatically. The device works without one but loses message history on reboot.\r\n\r\n---\r\n\r\n## What's Working\r\n\r\n### 📡 Mesh networking\r\n\r\n- Channel messaging — send and receive on Public, #test, #sydney\r\n- 17-preset radio picker (AU, US, EU, CN regions). Boots on Australia Narrow by default (916.575 MHz / SF7 / BW 62.5 kHz / CR 4/8)\r\n- Adverts go out automatically; received adverts populate Recent Heard and (subject to your auto-add policy) the contact list\r\n- **Self-healing public-channel migration** — earlier dev builds derived the Public channel secret from a hash, which didn't match the rest of the network. v0.1 detects this on every boot and repairs it automatically, without disturbing your custom channels\r\n\r\n### 📱 UI\r\n\r\nA horizontal seven-tile home layout. Swipe left/right to switch tiles.\r\n\r\n| Tile | What it shows |\r\n| --- | --- |\r\n| 0 Home | Node name, freq/SF/RSSI/RX counters, six-button nav grid |\r\n| 1 Recent Heard | Live list of nodes whose adverts you've received |\r\n| 2 Radio Details | Current freq / BW / SF / CR / TX / sync word |\r\n| 3 Advert | Long-press to send a manual advert |\r\n| 4 GPS | Fix status, satellites, position, altitude, sentence rate |\r\n| 5 Battery | Voltage, charge%, current, chip temp, remaining mAh |\r\n| 6 Shutdown | Long-press to power down |\r\n\r\n### 👥 Contacts\r\n\r\n- Filter chip bar at the top: All / Chat / Rptr / Room / Sens / Fav. Swipe left/right to cycle, or tap a chip directly\r\n- Per-row colour-coded type pill (C / R / RS / S) and 4-byte pubkey prefix for disambiguation\r\n- **Long-press a contact** to toggle favourite (a star appears, the contact rises to the top)\r\n- Tap a contact to open the detail screen, with a red **Hold** button that long-press-deletes (single tap is unbound to prevent accidents)\r\n- Auto-add policies in Settings → Contacts: Auto All / Custom (per-type toggles) / Manu\n…", "notesHtml": "

The first publicly flashable Meck firmware for the LilyGo T-Display P4. One\nfile, one offset, you're on the mesh.

\n
\n

⚠️ This is a pre-release, not a finished product. Many of the features people associate with Meck on the T-Deck Pro and T5S3 — direct messaging, roomserver access, repeater admin, trace route, web browser, IRC, audio player — are not yet implemented on the P4. What's here is the foundation: a fully functional MeshCore node with channel messaging, contacts, persistent storage, GPS, and battery monitoring. See the full feature list and roadmap.

\n
\n
\n

Hardware

\n

⚠️ LilyGo T-Display P4 (TFT version)⚠️ The AMOLED variant has not been tested but should be close — adjust the display init in\nmain/examples/lvgl_9_ui/main.cpp if you want to try it.

\n

Flashing

\n\"IMG_2838\"

Ensure you use the right-usb C port, ie not the high-speed charger port to flash.

\n

The release file meck-p4-0.1-merged.bin is a merged binary containing the bootloader, partition table, and application combined into a single image — flash it at address 0x0.

\n

Using the MeshCore Flasher (web-based):

\n
    \n
  1. Go to https://flasher.meshcore.io
    2. \n
  2. Scroll to the bottom and select Custom Firmware
    3. \n
  3. Select the meck-p4-0.1.bin file you downloaded
    4. \n
  4. Click OK for the warning about erase files because it's a merged binary.
    5. \n
  5. Click Flash, choose your device in the popup, and click Connect
    6. \n
\n

Using esptool.py:

\n
pip install esptool\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.1.bin\n
\n

(Replace PORT with /dev/cu.usbmodemXXXX on macOS, /dev/ttyACM0 on Linux, or COM3 on Windows.)

\n

If you've previously had something else on the device, run esptool.py --chip esp32p4 -p PORT erase_flash first to clear NVS so Meck starts with clean defaults.

\n
\n

An SD card is recommended. With a FAT32-formatted card inserted, every saved setting and channel message is mirrored automatically. The device works without one but loses message history on reboot.

\n
\n
\n

What's Working

\n

📡 Mesh networking

\n
    \n
  • Channel messaging — send and receive on Public, #test, #sydney
    • \n
  • 17-preset radio picker (AU, US, EU, CN regions). Boots on Australia Narrow by default (916.575 MHz / SF7 / BW 62.5 kHz / CR 4/8)
    • \n
  • Adverts go out automatically; received adverts populate Recent Heard and (subject to your auto-add policy) the contact list
    • \n
  • Self-healing public-channel migration — earlier dev builds derived the Public channel secret from a hash, which didn't match the rest of the network. v0.1 detects this on every boot and repairs it automatically, without disturbing your custom channels
    • \n
\n

📱 UI

\n

A horizontal seven-tile home layout. Swipe left/right to switch tiles.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TileWhat it shows
0 HomeNode name, freq/SF/RSSI/RX counters, six-button nav grid
1 Recent HeardLive list of nodes whose adverts you've received
2 Radio DetailsCurrent freq / BW / SF / CR / TX / sync word
3 AdvertLong-press to send a manual advert
4 GPSFix status, satellites, position, altitude, sentence rate
5 BatteryVoltage, charge%, current, chip temp, remaining mAh
6 ShutdownLong-press to power down
\n

👥 Contacts

\n
    \n
  • Filter chip bar at the top: All / Chat / Rptr / Room / Sens / Fav. Swipe left/right to cycle, or tap a chip directly
    • \n
  • Per-row colour-coded type pill (C / R / RS / S) and 4-byte pubkey prefix for disambiguation
    • \n
  • Long-press a contact to toggle favourite (a star appears, the contact rises to the top)
    • \n
  • Tap a contact to open the detail screen, with a red Hold button that long-press-deletes (single tap is unbound to prevent accidents)
    • \n
  • Auto-add policies in Settings → Contacts: Auto All / Custom (per-type toggles) / Manu\n…
    • \n
\n" } ], "changelogSource": "github", "changelogUpdatedAt": "2026-06-21T09:55:31.755Z" }, { "id": "meshcomod", "name": "Meshcomod", "type": "fork", "maintainer": "ALLFATHER-BV", "description": "A multi-transport companion firmware built on MeshCore that exposes USB, Bluetooth and TCP connectivity simultaneously, so phones, web clients and Home Assistant can all talk to one radio at once. Adds runtime Wi-Fi config and an on-device UI.\n", "repository": "https://github.com/ALLFATHER-BV/meshcomod", "website": "https://meshcomod.com", "license": "MIT", "status": "active", "lifecycle": "active", "maturity": "stable", "distribution": "community", "lineage": { "kind": "fork", "upstreamFirmwareId": "meshcore-official", "upstreamRepository": "https://github.com/meshcore-dev/MeshCore" }, "runtime": { "framework": "arduino", "language": "cpp" }, "roles": [ "companion", "repeater", "room-server" ], "features": [ "Simultaneous USB + BLE + TCP connections", "Real-time push to all connected clients", "Home Assistant sidebar integration", "Runtime Wi-Fi configuration (no CLI recovery)", "On-device UI tabs (BLE pairing, TCP status)" ], "capabilities": { "protocol": { "meshcoreCompatible": true }, "transports": { "ble": true, "usbSerial": true, "nativeTcp": true, "wifiAp": true }, "operations": { "ota": true, "webFlasher": false }, "networking": { "repeater": true, "roomServer": true, "observer": false, "kissModem": false }, "hardware": { "gps": true, "display": true, "sensors": false, "lowPowerRx": false } }, "devices": [ { "id": "heltec-v4", "status": "supported" }, { "id": "heltec-v4-exp", "status": "supported" }, { "id": "heltec-v3", "status": "supported" }, { "id": "heltec-wsl3", "status": "supported" }, { "id": "heltec-paper", "status": "supported" }, { "id": "xiao-esp32s3", "status": "supported" } ], "popularity": { "githubStars": 62, "githubForks": 6, "githubWatchers": 5, "githubOpenIssues": 4, "githubContributors": 151, "releaseDownloads": 144, "latestReleaseDownloads": 38, "lastChecked": "2026-06-21" }, "verification": { "sourceAvailable": true, "releasesAvailable": true, "ciBuilds": true, "lastChecked": "2026-06-21" }, "latest_version": "1.16.0.4", "released": "2026-06-16", "releases": [ { "version": "companion-v1.16.0.4", "name": "Companion Firmware v1.16.0.4", "datetime": "2026-06-16T19:39:49Z", "url": "https://github.com/ALLFATHER-BV/meshcomod/releases/tag/companion-v1.16.0.4", "prerelease": false, "notes": "**Full Changelog**: https://github.com/ALLFATHER-BV/meshcomod/compare/companion-v1.16.0.3...companion-v1.16.0.4", "notesHtml": "

Full Changelog: https://github.com/ALLFATHER-BV/meshcomod/compare/companion-v1.16.0.3...companion-v1.16.0.4

\n" }, { "version": "companion-v1.16.0.3", "name": "Companion Firmware v1.16.0.3", "datetime": "2026-06-15T10:44:19Z", "url": "https://github.com/ALLFATHER-BV/meshcomod/releases/tag/companion-v1.16.0.3", "prerelease": false, "notes": "**Full Changelog**: https://github.com/ALLFATHER-BV/meshcomod/compare/companion-v1.16.0.2...companion-v1.16.0.3", "notesHtml": "

Full Changelog: https://github.com/ALLFATHER-BV/meshcomod/compare/companion-v1.16.0.2...companion-v1.16.0.3

\n" }, { "version": "companion-v1.16.0.2", "name": "Companion Firmware v1.16.0.2", "datetime": "2026-06-14T06:32:51Z", "url": "https://github.com/ALLFATHER-BV/meshcomod/releases/tag/companion-v1.16.0.2", "prerelease": false, "notes": "**Full Changelog**: https://github.com/ALLFATHER-BV/meshcomod/compare/companion-v1.16.0.1...companion-v1.16.0.2", "notesHtml": "

Full Changelog: https://github.com/ALLFATHER-BV/meshcomod/compare/companion-v1.16.0.1...companion-v1.16.0.2

\n" }, { "version": "companion-v1.16.0.1", "name": "Companion Firmware v1.16.0.1", "datetime": "2026-06-13T21:10:09Z", "url": "https://github.com/ALLFATHER-BV/meshcomod/releases/tag/companion-v1.16.0.1", "prerelease": false, "notes": "**meshcomod companion v1.16.0.1** (on MeshCore 1.16).\n\nBoards: Heltec V4 (OLED), Heltec V3, Heltec Wireless Paper (E213), Seeed Xiao S3 WIO — multi-transport USB + BLE + TCP.\n\n**Fixes**\n- **BLE no longer fails to start when Wi-Fi credentials are set** (issue #32). On the V4/OLED companions, BLE and Wi-Fi now co-init correctly at boot instead of BLE being deferred and unable to come up later.\n\nFlash the `-merged.bin` at 0x0 for a first-time/recovery flash, or the app-only `.bin` at 0x10000 over a matching partition table.", "notesHtml": "

meshcomod companion v1.16.0.1 (on MeshCore 1.16).

\n

Boards: Heltec V4 (OLED), Heltec V3, Heltec Wireless Paper (E213), Seeed Xiao S3 WIO — multi-transport USB + BLE + TCP.

\n

Fixes

\n
    \n
  • BLE no longer fails to start when Wi-Fi credentials are set (issue #32). On the V4/OLED companions, BLE and Wi-Fi now co-init correctly at boot instead of BLE being deferred and unable to come up later.
    • \n
\n

Flash the -merged.bin at 0x0 for a first-time/recovery flash, or the app-only .bin at 0x10000 over a matching partition table.

\n" } ], "changelogSource": "github", "changelogUpdatedAt": "2026-06-21T09:55:32.127Z" }, { "id": "meshcore-lowpower", "name": "MeshCore Low-Power", "type": "fork", "maintainer": "dt267", "description": "A power-optimised MeshCore firmware with deep sleep, a full companion display UI with multi-transport connectivity (BLE + USB + WiFi in a single build), advanced radio and network controls, a browser-based configuration portal, and battery-life profiling — built for multi-day off-grid operation.\n", "repository": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4", "license": "MIT", "status": "active", "lifecycle": "active", "maturity": "beta", "distribution": "community", "lineage": { "kind": "fork", "upstreamFirmwareId": "meshcore-official", "upstreamRepository": "https://github.com/meshcore-dev/MeshCore" }, "runtime": { "framework": "arduino", "language": "cpp" }, "roles": [ "companion", "repeater", "room-server" ], "features": [ "Deep power optimisation with idle current profiling", "Unified BLE + USB + WiFi companion build (single binary)", "Browser-based configuration portal (backup, restore, flash, reboot)", "Companion backup/restore (preferences, WiFi credentials, presets)", "Adaptive Rx boosted gain on Heltec V4.2", "GPS constellation selection and runtime GPS update interval", "Low-battery protection and voltage reading", "Native multilingual display on Heltec T096 colour TFT", "KCT8103L FEM auto-detection on Heltec V4.3" ], "capabilities": { "protocol": { "meshcoreCompatible": true }, "transports": { "ble": true, "usbSerial": true, "nativeTcp": true, "wifiAp": true }, "operations": { "ota": true, "webFlasher": false }, "networking": { "repeater": true, "roomServer": true, "observer": false, "kissModem": false }, "hardware": { "gps": true, "display": true, "sensors": true, "lowPowerRx": true } }, "devices": [ { "id": "heltec-v3", "status": "supported" }, { "id": "heltec-wsl3", "status": "supported" }, { "id": "heltec-v4", "status": "supported" }, { "id": "heltec-v4-exp", "status": "supported" }, { "id": "heltec-e213", "status": "supported" }, { "id": "heltec-e290", "status": "supported" }, { "id": "heltec-paper", "status": "supported" }, { "id": "heltec-t096", "status": "supported" }, { "id": "xiao-esp32s3", "status": "supported" }, { "id": "rak-4631", "status": "supported", "notes": "Uses RAK19003 base board for power profiling." }, { "id": "uart-solar-node-station", "status": "supported", "notes": "Uses RAK4631 target; same as rak-4631." } ], "latest_version": "1.16.dev_0621", "released": "2026-06-21", "releases": [ { "version": "MeshCore-low-power-v1.16.dev_0621", "name": "MeshCore low power - v1.16.dev_0621", "datetime": "2026-06-21T07:24:05Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/MeshCore-low-power-v1.16.dev_0621", "prerelease": false, "notes": "### v1.16_0621\r\n\r\n- **Configuration portal for Companion, Repeater, and Room Server — configure, back up, restore, and update firmware without the CLI.** *(ESP32 devices only)*\r\n\r\n Open it the same way as before — `start ota` in the CLI, or **Start OTA** from the companion Settings menu. Previously this landed on a firmware-only upload page; it now opens the full configuration portal where you can configure, back up, restore, flash firmware, and reboot — all from one page in the browser.\r\n\r\n The companion backup covers custom preferences (Quick Send presets, saved locations, channel hop limits, display settings, WiFi credentials,...) that upstream MeshCore doesn't have — handy when moving to a new device. For the Repeater and Room Server, this is the first time backup and restore are available at all — no more re-entering everything from scratch after a node failure or hardware swap.\r\n\r\n The portal is password-protected. Companion: set one with `set portal.password` in the CLI. Repeater / Room Server: the existing admin password is used automatically.\r\n\r\n The backup format is compatible with the official MeshCore app — upstream preferences in the backup can be restored by the app. Passwords are never written to backup files.\r\n\r\n- **Config portal AP: open network, login page, 1-client limit, 10-minute idle auto-shutdown.**\r\n\r\n The WiFi AP is open (no AP password); access is gated by a browser login page using the portal password described above. Only one device can associate with the AP at a time. If no device connects within 10 minutes of the AP opening, it shuts down automatically.\r\n\r\n \"config-portal\"\r\n\r\n\r\n- **Fix: full-flash (`_merged.bin`) images for Vision Master E213 and E290 were built with the wrong flash size.**\r\n\r\n Both boards have 16 MB of flash, but their merged full-flash images were generated with an 8 MB flash-size header. The pre-merged images are now built with the correct 16 MB size. If you previously flashed an E213 or E290 using a `_merged.bin`, re-flash with the corrected image. OTA (`.bin`) updates were not affected.", "notesHtml": "

v1.16_0621

\n
    \n

  • Configuration portal for Companion, Repeater, and Room Server — configure, back up, restore, and update firmware without the CLI. (ESP32 devices only)

    \n

    Open it the same way as before — start ota in the CLI, or Start OTA from the companion Settings menu. Previously this landed on a firmware-only upload page; it now opens the full configuration portal where you can configure, back up, restore, flash firmware, and reboot — all from one page in the browser.

    \n

    The companion backup covers custom preferences (Quick Send presets, saved locations, channel hop limits, display settings, WiFi credentials,...) that upstream MeshCore doesn't have — handy when moving to a new device. For the Repeater and Room Server, this is the first time backup and restore are available at all — no more re-entering everything from scratch after a node failure or hardware swap.

    \n

    The portal is password-protected. Companion: set one with set portal.password in the CLI. Repeater / Room Server: the existing admin password is used automatically.

    \n

    The backup format is compatible with the official MeshCore app — upstream preferences in the backup can be restored by the app. Passwords are never written to backup files.

    \n
    • \n

  • Config portal AP: open network, login page, 1-client limit, 10-minute idle auto-shutdown.

    \n

    The WiFi AP is open (no AP password); access is gated by a browser login page using the portal password described above. Only one device can associate with the AP at a time. If no device connects within 10 minutes of the AP opening, it shuts down automatically.

    \n\"config-portal\"
    • \n

  • Fix: full-flash (_merged.bin) images for Vision Master E213 and E290 were built with the wrong flash size.

    \n

    Both boards have 16 MB of flash, but their merged full-flash images were generated with an 8 MB flash-size header. The pre-merged images are now built with the correct 16 MB size. If you previously flashed an E213 or E290 using a _merged.bin, re-flash with the corrected image. OTA (.bin) updates were not affected.

    \n
    • \n
\n" }, { "version": "MeshCore-low-power-v1.16.dev_0614", "name": "MeshCore low power - v1.16.dev_0614", "datetime": "2026-06-14T04:15:08Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/MeshCore-low-power-v1.16.dev_0614", "prerelease": false, "notes": "### v1.16_0614\r\n\r\n- **New devices: Heltec Vision Master E213, Wireless Paper, and Vision Master E290 — full e-ink companion support (Companion, Repeater, Room Server).**\r\n\r\n Three e-ink boards are now fully supported with the complete companion UI — Quick Send, Contacts, Settings, Saved Locations, GPS Trace, and message preview. Repeater and Room Server firmware are provided for all three.\r\n\r\n - **Heltec Vision Master E213** *(author-tested, v1.1.1)* — ESP32-S3 with a 2.13\" e-ink display (250×122 px), SX1262 LoRa, and a QuickLink I2C port. Has a second user button (GPIO21): press to scroll up in any list, or to go back — faster than double clicking the main button.\r\n - **Heltec Wireless Paper** — ESP32-S3 with the same 2.13\" e-ink panel as the E213 in a more compact form factor. Shares the same companion UI and firmware variants as the E213. Single button only.\r\n - **Heltec Vision Master E290** — ESP32-S3R8 with a larger 2.9\" e-ink display (296×128 px), SX1262 LoRa, and a QuickLink I2C port. Also has a second button (GPIO21) like the E213. The companion UI adapts automatically to the wider panel — more message lines and a larger clock on the Home screen.\r\n\r\n **Common characteristics across all three e-ink boards:**\r\n - **Always-on display** — e-ink retains content indefinitely without power; no screen timeout.\r\n - **Native multilingual text** — Latin, Cyrillic, and Greek scripts render natively.\r\n - **Font Weight setting** — choose between **Thin** and **Bold** via **Settings → Font Weight**. Preference is saved to flash.\r\n - **I2C sensor support** — environment sensors can be connected via the QuickLink I2C port.\r\n\r\n- **Companion: unified BLE / USB / WiFi connection mode for all ESP32-S3 boards.**\r\n\r\n All ESP32-S3 companion builds (Heltec V3, V4, E213, Wireless Paper, E290, XIAO S3) now ship as a single unified firmware image that supports all three connection transports: **BLE**, **USB serial**, and **WiFi TCP**. The active mode is saved to flash and selected at boot — no per-mode build is needed.\r\n\r\n Switching is done via **Settings → Connection Mode**, which opens a direct selection screen listing all three modes with the current one marked `*`. Navigate to the desired mode and confirm — the device reboots into the new mode.\r\n\r\n Alternatively, switch via [TerminalCLI](Companion_TerminalCLI_Commands.md): `set conn.mode wifi|ble|usb`. WiFi credentials are configured with `set wifi.ssid` / `set wifi.password`, or from the **OTA update page** which now includes a WiFi credentials form alongside the firmware upload button.\r\n\r\n In WiFi mode, the node connects as a STA to your router and the Home screen shows the IP address and port. All three modes meet the low-power criteria of this repo. \r\n\r\n- **Companion UI: Home screen always shows a large clock; message count shown in the header.**\r\n\r\n The center of the Home screen now always shows the current time (`HH:MM`) in a large font — `MSG: N` is gone. If there are messages stored in memory, their count and a small envelope icon appear in the header (where the small clock used to be); the header is left empty when count is zero. The header clock is visible again on all other pages as before.\r\n\r\n On e-ink displays (E213, Wireless Paper, E290), the clock is rendered in a large font; pairing pin or connection status appears at the bottom-left, and the date at the bottom-right. On OLED and T096, the layout is: large clock → date → connection status, stacked top to bottom.\r\n\r\n Before the clock is synchronized with the app or GPS, the display shows uptime counting up from `00:00` since boot, consistent with the small header clock.\r\n\r\n- **Repeater/Room Server: flood hop limits now correctly ignore leading-zero path padding.**\r\n\r\n Some senders limit how far a packet propagates by pre-filling the path with zero entries — a TTL trick used by custom firmware, and by companions in this firmware via `ch.hops`. Previously, repeaters counted these zeros as real relay hops, causi\n…", "notesHtml": "

v1.16_0614

\n
    \n

  • New devices: Heltec Vision Master E213, Wireless Paper, and Vision Master E290 — full e-ink companion support (Companion, Repeater, Room Server).

    \n

    Three e-ink boards are now fully supported with the complete companion UI — Quick Send, Contacts, Settings, Saved Locations, GPS Trace, and message preview. Repeater and Room Server firmware are provided for all three.

    \n
      \n
    • Heltec Vision Master E213 (author-tested, v1.1.1) — ESP32-S3 with a 2.13\" e-ink display (250×122 px), SX1262 LoRa, and a QuickLink I2C port. Has a second user button (GPIO21): press to scroll up in any list, or to go back — faster than double clicking the main button.
      • \n
    • Heltec Wireless Paper — ESP32-S3 with the same 2.13\" e-ink panel as the E213 in a more compact form factor. Shares the same companion UI and firmware variants as the E213. Single button only.
      • \n
    • Heltec Vision Master E290 — ESP32-S3R8 with a larger 2.9\" e-ink display (296×128 px), SX1262 LoRa, and a QuickLink I2C port. Also has a second button (GPIO21) like the E213. The companion UI adapts automatically to the wider panel — more message lines and a larger clock on the Home screen.
      • \n
    \n

    Common characteristics across all three e-ink boards:

    \n
      \n
    • Always-on display — e-ink retains content indefinitely without power; no screen timeout.
      • \n
    • Native multilingual text — Latin, Cyrillic, and Greek scripts render natively.
      • \n
    • Font Weight setting — choose between Thin and Bold via Settings → Font Weight. Preference is saved to flash.
      • \n
    • I2C sensor support — environment sensors can be connected via the QuickLink I2C port.
      • \n
    \n
    • \n

  • Companion: unified BLE / USB / WiFi connection mode for all ESP32-S3 boards.

    \n

    All ESP32-S3 companion builds (Heltec V3, V4, E213, Wireless Paper, E290, XIAO S3) now ship as a single unified firmware image that supports all three connection transports: BLE, USB serial, and WiFi TCP. The active mode is saved to flash and selected at boot — no per-mode build is needed.

    \n

    Switching is done via Settings → Connection Mode, which opens a direct selection screen listing all three modes with the current one marked *. Navigate to the desired mode and confirm — the device reboots into the new mode.

    \n

    Alternatively, switch via TerminalCLI: set conn.mode wifi|ble|usb. WiFi credentials are configured with set wifi.ssid / set wifi.password, or from the OTA update page which now includes a WiFi credentials form alongside the firmware upload button.

    \n

    In WiFi mode, the node connects as a STA to your router and the Home screen shows the IP address and port. All three modes meet the low-power criteria of this repo.

    \n
    • \n

  • Companion UI: Home screen always shows a large clock; message count shown in the header.

    \n

    The center of the Home screen now always shows the current time (HH:MM) in a large font — MSG: N is gone. If there are messages stored in memory, their count and a small envelope icon appear in the header (where the small clock used to be); the header is left empty when count is zero. The header clock is visible again on all other pages as before.

    \n

    On e-ink displays (E213, Wireless Paper, E290), the clock is rendered in a large font; pairing pin or connection status appears at the bottom-left, and the date at the bottom-right. On OLED and T096, the layout is: large clock → date → connection status, stacked top to bottom.

    \n

    Before the clock is synchronized with the app or GPS, the display shows uptime counting up from 00:00 since boot, consistent with the small header clock.

    \n
    • \n

  • Repeater/Room Server: flood hop limits now correctly ignore leading-zero path padding.

    \n

    Some senders limit how far a packet propagates by pre-filling the path with zero entries — a TTL trick used by custom firmware, and by companions in this firmware via ch.hops. Previously, repeaters counted these zeros as real relay hops, causi\n…

    \n
    • \n
\n" }, { "version": "MeshCore-low-power-v1.16.dev_0607", "name": "MeshCore low power - v1.16.dev_0607", "datetime": "2026-06-07T05:01:31Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/MeshCore-low-power-v1.16.dev_0607", "prerelease": false, "notes": "### v1.16_0607\r\n\r\n- **Companion UI: Native multilingual display on Heltec T096 (ST7735S)**\r\n\r\n Node names and messages now render natively on the T096 color TFT — characters are displayed as-is instead of being converted to ASCII equivalents. Supported languages include all 31 from v1.14 plus additional scripts:\r\n\r\n **Latin-based:** Catalan, Croatian, Czech, Danish, Dutch, Estonian, Finnish, French, German, Hungarian, Icelandic, Italian, Latvian, Lithuanian, Maltese, Norwegian, Polish, Portuguese, Romanian, Slovak, Slovenian, Spanish, Swedish, Turkish, Vietnamese, Welsh\r\n\r\n **Cyrillic:** Belarusian, Bulgarian, Macedonian, Russian, Serbian, Ukrainian\r\n\r\n **Greek:** Greek\r\n\r\n- **Companion UI: Contacts screen now includes room servers; request telemetry from any contact.**\r\n\r\n Room servers appear in the contact list tagged `[R]`. Selecting any contact — chat node or room server — and long pressing opens an action menu: **Send message** or **Request telemetry**. Requesting telemetry displays the node's battery voltage and GPS coordinates (if present); long press to open the GPS Trace screen for that location.\r\n\r\n GPS coordinates follow the **Pos. Format** selected in Settings (DD, UTM, or MGRS).\r\n\r\n The message inbox group list now tags group/channel entries with `[G]` and room server entries with `[R]` for consistent visual distinction. Each room message shows the original author's name. When viewing a room message, long press to open the popup and select **Reply** to post back to the room (visible to all subscribers).\r\n\r\n > **Private room servers:** messaging requires a prior login. Public rooms (no password) work without any login. For private rooms, log in once via the MeshCore app — if your account has admin rights on that room server, the session persists across reboots. Regular user sessions are not saved to flash and will require re-login after the room server reboots.\r\n\r\n- **Companion: switch the app connection between BLE and USB serial without reflashing.**\r\n\r\n In USB mode the node behaves like a standard `usb` build — the PC app connects over the USB serial port directly. Toggle via **Settings → Connection Mode** on the display, or via TerminalCLI: `set conn.mode usb` / `set conn.mode ble`. The setting persists across reboots. BLE toggle is hidden in the Settings menu while USB mode is active.\r\n\r\n- **Repeater, Room Sever: hold user button 5 seconds to power off.**\r\n\r\n Hold the user button for 5 seconds to power off the node — faster than reaching for the CLI when you're standing next to it. The LED blinks 5 times as a warning before shutdown.\r\n\r\n- **Repeater, Room Server: `advert.hops.max` default changed to 8; room server support added; `flood.max.advert` alias.**\r\n\r\n `advert.hops.max` now defaults to `8` instead of `flood.max` — advert relay limiting is active out of the box without any configuration. Room servers now also enforce this limit (previously repeater-only). The command `flood.max.advert` is accepted as an alias for compatibility with upstream firmware.", "notesHtml": "

v1.16_0607

\n
    \n

  • Companion UI: Native multilingual display on Heltec T096 (ST7735S)

    \n

    Node names and messages now render natively on the T096 color TFT — characters are displayed as-is instead of being converted to ASCII equivalents. Supported languages include all 31 from v1.14 plus additional scripts:

    \n

    Latin-based: Catalan, Croatian, Czech, Danish, Dutch, Estonian, Finnish, French, German, Hungarian, Icelandic, Italian, Latvian, Lithuanian, Maltese, Norwegian, Polish, Portuguese, Romanian, Slovak, Slovenian, Spanish, Swedish, Turkish, Vietnamese, Welsh

    \n

    Cyrillic: Belarusian, Bulgarian, Macedonian, Russian, Serbian, Ukrainian

    \n

    Greek: Greek

    \n
    • \n

  • Companion UI: Contacts screen now includes room servers; request telemetry from any contact.

    \n

    Room servers appear in the contact list tagged [R]. Selecting any contact — chat node or room server — and long pressing opens an action menu: Send message or Request telemetry. Requesting telemetry displays the node's battery voltage and GPS coordinates (if present); long press to open the GPS Trace screen for that location.

    \n

    GPS coordinates follow the Pos. Format selected in Settings (DD, UTM, or MGRS).

    \n

    The message inbox group list now tags group/channel entries with [G] and room server entries with [R] for consistent visual distinction. Each room message shows the original author's name. When viewing a room message, long press to open the popup and select Reply to post back to the room (visible to all subscribers).

    \n
    \n

    Private room servers: messaging requires a prior login. Public rooms (no password) work without any login. For private rooms, log in once via the MeshCore app — if your account has admin rights on that room server, the session persists across reboots. Regular user sessions are not saved to flash and will require re-login after the room server reboots.

    \n
    \n
    • \n

  • Companion: switch the app connection between BLE and USB serial without reflashing.

    \n

    In USB mode the node behaves like a standard usb build — the PC app connects over the USB serial port directly. Toggle via Settings → Connection Mode on the display, or via TerminalCLI: set conn.mode usb / set conn.mode ble. The setting persists across reboots. BLE toggle is hidden in the Settings menu while USB mode is active.

    \n
    • \n

  • Repeater, Room Sever: hold user button 5 seconds to power off.

    \n

    Hold the user button for 5 seconds to power off the node — faster than reaching for the CLI when you're standing next to it. The LED blinks 5 times as a warning before shutdown.

    \n
    • \n

  • Repeater, Room Server: advert.hops.max default changed to 8; room server support added; flood.max.advert alias.

    \n

    advert.hops.max now defaults to 8 instead of flood.max — advert relay limiting is active out of the box without any configuration. Room servers now also enforce this limit (previously repeater-only). The command flood.max.advert is accepted as an alias for compatibility with upstream firmware.

    \n
    • \n
\n" }, { "version": "pre-release-Heltec-E213-Wireless-Paper-E290", "name": "pre-release Heltec E213, Wireless Paper, E290", "datetime": "2026-06-11T11:45:39Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/pre-release-Heltec-E213-Wireless-Paper-E290", "prerelease": true, "notes": "### v1.16_0611 pre-release for Heltec E213, Wireless Paper and E290\r\n\r\n- **New device: Heltec Vision Master E213 — full support (Companion, Repeater, Room Server).**\r\n\r\n The Heltec Vision Master E213 is now fully supported. It is an ESP32-S3 based board with a 2.13\" e-ink display, SX1262 LoRa radio, and a USB-C port. The complete companion UI runs on the e-ink display — Quick Send, Contacts, Settings, Saved Locations, GPS Trace, and message preview. Repeater and Room Server firmware are also provided.\r\n\r\n **Notable characteristics:**\r\n - **Always-on e-ink display** — no screen timeout; the display retains its content indefinitely without power.\r\n - **Native multilingual text** — Latin, Cyrillic, and Greek scripts render natively.\r\n - **I2C sensor support** — environment sensors (temperature, humidity, pressure...) can be connected via the QuickLink I2C port.\r\n - **Two user buttons** — the second button (GPIO21) makes navigation faster: press it to scroll up in any list, or to go back/exit any menu.\r\n\r\n- **New devices: Heltec Wireless Paper and Heltec Vision Master E290 — full support (Companion, Repeater, Room Server).**\r\n\r\n Two new e-ink boards are now supported:\r\n\r\n - **Heltec Wireless Paper** — ESP32-S3 with a 2.13\" e-ink display (same resolution as E213), SX1262 LoRa radio, and a compact form factor. Shares the same companion UI and firmware variants as E213.\r\n\r\n - **Heltec Vision Master E290** — ESP32-S3R8 with a larger 2.9\" e-ink display (296×128), SX1262 LoRa radio, and a QuickLink I2C port for external sensors. The companion UI adapts automatically to the wider, taller display — showing more message lines and better-spaced layouts compared to the 2.13\" boards.", "notesHtml": "

v1.16_0611 pre-release for Heltec E213, Wireless Paper and E290

\n
    \n

  • New device: Heltec Vision Master E213 — full support (Companion, Repeater, Room Server).

    \n

    The Heltec Vision Master E213 is now fully supported. It is an ESP32-S3 based board with a 2.13\" e-ink display, SX1262 LoRa radio, and a USB-C port. The complete companion UI runs on the e-ink display — Quick Send, Contacts, Settings, Saved Locations, GPS Trace, and message preview. Repeater and Room Server firmware are also provided.

    \n

    Notable characteristics:

    \n
      \n
    • Always-on e-ink display — no screen timeout; the display retains its content indefinitely without power.
      • \n
    • Native multilingual text — Latin, Cyrillic, and Greek scripts render natively.
      • \n
    • I2C sensor support — environment sensors (temperature, humidity, pressure...) can be connected via the QuickLink I2C port.
      • \n
    • Two user buttons — the second button (GPIO21) makes navigation faster: press it to scroll up in any list, or to go back/exit any menu.
      • \n
    \n
    • \n

  • New devices: Heltec Wireless Paper and Heltec Vision Master E290 — full support (Companion, Repeater, Room Server).

    \n

    Two new e-ink boards are now supported:

    \n
      \n

    • Heltec Wireless Paper — ESP32-S3 with a 2.13\" e-ink display (same resolution as E213), SX1262 LoRa radio, and a compact form factor. Shares the same companion UI and firmware variants as E213.

      \n
      • \n

    • Heltec Vision Master E290 — ESP32-S3R8 with a larger 2.9\" e-ink display (296×128), SX1262 LoRa radio, and a QuickLink I2C port for external sensors. The companion UI adapts automatically to the wider, taller display — showing more message lines and better-spaced layouts compared to the 2.13\" boards.

      \n
      • \n
    \n
    • \n
\n" }, { "version": "MeshCore-low-power-v1.15.dev_0531", "name": "MeshCore low power - v1.15.dev_0531", "datetime": "2026-05-31T02:29:03Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/MeshCore-low-power-v1.15.dev_0531", "prerelease": false, "notes": "### v1.15_0531\r\n\r\n- **Full support for Heltec T096 — companion, repeater, and room server**\r\n\r\n The Heltec T096 is now fully supported across all node types. The hardware is an nRF52840-based board with an SX1262 radio, KCT8103L FEM, UC6580 GPS, and a 0.96\" 160×80 color TFT display (ST7735S).\r\n\r\n The complete companion UI — Quick Send, Contacts, Settings, GPS, Saved Locations, GPS Trace, and message preview — runs on the color TFT.\r\n\r\n **Differences from other supported boards:**\r\n\r\n - **Color TFT display.** All companion pages render in color on the 160×80 ST7735S — unlike other supported boards which use a monochrome OLED.\r\n\r\n - **Brightness control.** A **Brightness** item in the Settings page adjusts the TFT backlight intensity: `25` → `50` → `75` → `100`. Setting is saved to flash.\r\n\r\n - **KCT8103L FEM — same as Heltec V4.3.** `set radio.rxgain on` / `off` works identically.\r\n\r\n - **UC6580 GPS.** `gps.interval` works the same as on Heltec V4. Constellation selection (`gps.mode`) uses a different set of options:\r\n\r\n | Value | Constellations |\r\n |---|---|\r\n | `1` | GPS L1 only |\r\n | `2` | All-system L1 (GPS+BDS+GLO+GAL) |\r\n | `3` | All-system + QZSS dual-band *(default)* |\r\n\r\n- **AGC auto-reset improvements (all node types).**\r\n\r\n Coordination between AGC auto-reset and channel busy detection has been improved. While the noise floor baseline is being re-established after a reset, channel sensing falls back to hardware CAD only.\r\n\r\n- **Fix: excessive flash writes on nRF52 Companion (T096, RAK4631).**\r\n\r\n Each received advertisement previously triggered an immediate flash write — both to the advert blob store and to the contact list. In areas with high advert traffic this caused unnecessary flash wear, and a malicious node spamming adverts could wear out ExtraFS in hours. Advert blobs are now buffered in RAM and flushed to flash at most once every 10 minutes. Auto-discovered contacts use the same 10-minute pattern instead of a short debounce timer.", "notesHtml": "

v1.15_0531

\n
    \n

  • Full support for Heltec T096 — companion, repeater, and room server

    \n

    The Heltec T096 is now fully supported across all node types. The hardware is an nRF52840-based board with an SX1262 radio, KCT8103L FEM, UC6580 GPS, and a 0.96\" 160×80 color TFT display (ST7735S).

    \n

    The complete companion UI — Quick Send, Contacts, Settings, GPS, Saved Locations, GPS Trace, and message preview — runs on the color TFT.

    \n

    Differences from other supported boards:

    \n
      \n

    • Color TFT display. All companion pages render in color on the 160×80 ST7735S — unlike other supported boards which use a monochrome OLED.

      \n
      • \n

    • Brightness control. A Brightness item in the Settings page adjusts the TFT backlight intensity: 25 → 50 → 75 → 100. Setting is saved to flash.

      \n
      • \n

    • KCT8103L FEM — same as Heltec V4.3. set radio.rxgain on / off works identically.

      \n
      • \n

    • UC6580 GPS. gps.interval works the same as on Heltec V4. Constellation selection (gps.mode) uses a different set of options:

      \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
      ValueConstellations
      1GPS L1 only
      2All-system L1 (GPS+BDS+GLO+GAL)
      3All-system + QZSS dual-band (default)
      \n
      • \n
    \n
    • \n

  • AGC auto-reset improvements (all node types).

    \n

    Coordination between AGC auto-reset and channel busy detection has been improved. While the noise floor baseline is being re-established after a reset, channel sensing falls back to hardware CAD only.

    \n
    • \n

  • Fix: excessive flash writes on nRF52 Companion (T096, RAK4631).

    \n

    Each received advertisement previously triggered an immediate flash write — both to the advert blob store and to the contact list. In areas with high advert traffic this caused unnecessary flash wear, and a malicious node spamming adverts could wear out ExtraFS in hours. Advert blobs are now buffered in RAM and flushed to flash at most once every 10 minutes. Auto-discovered contacts use the same 10-minute pattern instead of a short debounce timer.

    \n
    • \n
\n" }, { "version": "MeshCore-low-power-v1.15.dev_0524", "name": "MeshCore low power - v1.15.dev_0524", "datetime": "2026-05-24T01:53:36Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/MeshCore-low-power-v1.15.dev_0524", "prerelease": false, "notes": "### v1.15_0524\r\n\r\n- **Fix: radio deafness recovery in noisy environments (all node types).**\r\n\r\n When strong in-band interference causes the SX1262 AGC to become overwhelmed, the radio can go deaf — severely degraded in receive sensitivity. The firmware now detects this condition automatically and triggers an immediate hardware recalibration, restoring sensitivity without waiting for the scheduled `agc.reset.interval`. The `agc.reset.interval` setting remains available but is now unnecessary.\r\n\r\n Two new commands let you monitor and reset the AGC reset counter:\r\n\r\n | Command | Effect |\r\n |---------|--------|\r\n | `get agc.resets` | Show how many times the AGC has been auto-reset since boot or last `clear` |\r\n | `clear agc.resets` | Reset the counter to zero |\r\n\r\n **Real-world validation:** A repeater installed near a periodic in-band interference source (confirmed via RTL-SDR) accumulated 918 auto-resets over 8.5 hours (~1.8/min), matching the observed interference sweep cycle. A second repeater at a clean location recorded 0 resets over the same period, confirming no false positives. Without this feature, the first repeater was unreachable remotely due to persistent deafness.\r\n\r\n- **GPS update interval configurable at runtime on Heltec V4 (all node types).**\r\n\r\n A new `gps.interval` setting controls the sleep time between GPS position updates. After each fix, GPS powers down for the configured interval, then wakes and acquires a new fix. Set it to `0` to keep GPS always on. Default is 10 seconds.\r\n\r\n Available on **Companion** via [TerminalCLI](Companion_TerminalCLI_Commands.md) and on **Repeater / Room Server** via the Command Line:\r\n\r\n | Command | Effect |\r\n |---|---|\r\n | `get gps.interval` | Show current interval (`always on` if 0) |\r\n | `set gps.interval 0` | GPS always on — maximum accuracy, highest power draw |\r\n | `set gps.interval 30` | GPS sleeps 30s after each fix, then re-acquires |\r\n | `set gps.interval 300` | GPS sleeps 5 minutes after each fix |\r\n\r\n Setting is saved to flash and takes effect immediately — no reboot needed.\r\n\r\n- **GPS constellation selection for L78K on Heltec V4 (`gps.mode`) (all node types).**\r\n\r\n Choose which satellite constellations the L78K module tracks. Average current draw is essentially the same across all configurations in duty cycle mode with `gps.interval` greater than 10 (~23 mA mean current measured on Heltec V4.3 Companion with `gps.mode = 4` and `gps.interval = 10`). Leave at the default `4` for the most robust fix; adjust only if you have a specific coverage reason.\r\n\r\n | Value | Constellations |\r\n |---|---|\r\n | `1` | GPS only |\r\n | `2` | GPS + BeiDou |\r\n | `3` | GPS + GLONASS |\r\n | `4` | GPS + BeiDou + GLONASS *(default)* |\r\n\r\n Available on **Companion** via [TerminalCLI](Companion_TerminalCLI_Commands.md) and on **Repeater / Room Server** via the Command Line:\r\n\r\n | Command | Effect |\r\n |---|---|\r\n | `get gps.mode` | Show current constellation selection |\r\n | `set gps.mode 4` | GPS + BeiDou + GLONASS (default) |\r\n | `set gps.mode 1` | GPS only |\r\n\r\n Setting is saved to flash. Change takes effect on next GPS on.\r\n\r\n- **Companion: GPS screen shows interval and constellation when GPS is off.**\r\n\r\n When GPS is off, the GPS page now shows the configured update interval (`intv`) and constellation selection (`mode`, Heltec V4 only), so you can verify settings before enabling GPS.", "notesHtml": "

v1.15_0524

\n
    \n

  • Fix: radio deafness recovery in noisy environments (all node types).

    \n

    When strong in-band interference causes the SX1262 AGC to become overwhelmed, the radio can go deaf — severely degraded in receive sensitivity. The firmware now detects this condition automatically and triggers an immediate hardware recalibration, restoring sensitivity without waiting for the scheduled agc.reset.interval. The agc.reset.interval setting remains available but is now unnecessary.

    \n

    Two new commands let you monitor and reset the AGC reset counter:

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    CommandEffect
    get agc.resetsShow how many times the AGC has been auto-reset since boot or last clear
    clear agc.resetsReset the counter to zero
    \n

    Real-world validation: A repeater installed near a periodic in-band interference source (confirmed via RTL-SDR) accumulated 918 auto-resets over 8.5 hours (~1.8/min), matching the observed interference sweep cycle. A second repeater at a clean location recorded 0 resets over the same period, confirming no false positives. Without this feature, the first repeater was unreachable remotely due to persistent deafness.

    \n
    • \n

  • GPS update interval configurable at runtime on Heltec V4 (all node types).

    \n

    A new gps.interval setting controls the sleep time between GPS position updates. After each fix, GPS powers down for the configured interval, then wakes and acquires a new fix. Set it to 0 to keep GPS always on. Default is 10 seconds.

    \n

    Available on Companion via TerminalCLI and on Repeater / Room Server via the Command Line:

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    CommandEffect
    get gps.intervalShow current interval (always on if 0)
    set gps.interval 0GPS always on — maximum accuracy, highest power draw
    set gps.interval 30GPS sleeps 30s after each fix, then re-acquires
    set gps.interval 300GPS sleeps 5 minutes after each fix
    \n

    Setting is saved to flash and takes effect immediately — no reboot needed.

    \n
    • \n

  • GPS constellation selection for L78K on Heltec V4 (gps.mode) (all node types).

    \n

    Choose which satellite constellations the L78K module tracks. Average current draw is essentially the same across all configurations in duty cycle mode with gps.interval greater than 10 (~23 mA mean current measured on Heltec V4.3 Companion with gps.mode = 4 and gps.interval = 10). Leave at the default 4 for the most robust fix; adjust only if you have a specific coverage reason.

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    ValueConstellations
    1GPS only
    2GPS + BeiDou
    3GPS + GLONASS
    4GPS + BeiDou + GLONASS (default)
    \n

    Available on Companion via TerminalCLI and on Repeater / Room Server via the Command Line:

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    CommandEffect
    get gps.modeShow current constellation selection
    set gps.mode 4GPS + BeiDou + GLONASS (default)
    set gps.mode 1GPS only
    \n

    Setting is saved to flash. Change takes effect on next GPS on.

    \n
    • \n

  • Companion: GPS screen shows interval and constellation when GPS is off.

    \n

    When GPS is off, the GPS page now shows the configured update interval (intv) and constellation selection (mode, Heltec V4 only), so you can verify settings before enabling GPS.

    \n
    • \n
\n" }, { "version": "MeshCore-low-power-v1.15.dev_0517", "name": "MeshCore low power - v1.15.dev_0517", "datetime": "2026-05-17T03:19:48Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/MeshCore-low-power-v1.15.dev_0517", "prerelease": false, "notes": "### v1.15_0517\r\n\r\n- **Companion: per-channel outgoing hop limit (`ch.hops`).**\r\n\r\n Limit how far your outgoing messages travel on a specific channel, without affecting any other channel or any other node in the network. Useful for keeping a private or local-area channel confined to a small radius — for example, a home-to-nearby-relay link — without touching the rest of the city mesh.\r\n\r\n Configure via **TerminalCLI**:\r\n\r\n | Command | Effect |\r\n |---|---|\r\n | `set ch.hops ` | Limit outgoing messages on `` to at most N hops |\r\n | `set ch.hops off` | Remove the limit |\r\n | `get ch.hops ` | Show current limit |\r\n | `ch.hops status` | List all channels with an active limit |\r\n | `ch.hops clear` | Remove all limits |\r\n\r\n ```\r\n set ch.hops Public 2 # Public channel messages travel at most 2 hops\r\n set ch.hops My Local Net 3 # My Local Net channel travel at most 3 hops\r\n set ch.hops Public off # remove the limit\r\n ch.hops status\r\n ```\r\n\r\n\r\n The limit applies to **your outgoing messages only** — other nodes sending on the same channel are unaffected. No repeater configuration or network coordination required.\r\n\r\n The repeater's `group.hops.max` algorithm has been updated to correctly account for sender-side pre-fill, so `ch.hops` and `group.hops.max` work together without conflict — update repeater firmware to get full compatibility.\r\n\r\n Settings are stored in flash and persist after reboot.\r\n\r\n- **Companion: toggle RxGain directly from the Radio screen.**\r\n\r\n Long press on the **Radio** page cycles through RxGain modes (OFF → ON → Auto) and shows a popup confirming the new mode. The current mode is now also displayed on the Radio page itself (`RxG: OFF` / `RxG: ON` / `RxG: Auto`), so you can check it at a glance without going into Settings. *(`Auto` is available on Heltec V4.2 only.)*\r\n\r\n- **Fix: noise floor stuck at -120 in noisy environments (all node types)**\r\n\r\n In environments with strong in-band interference, the noise floor could remain at -120 dBm for a long time instead of updating to reflect actual conditions. Fixed.", "notesHtml": "

v1.15_0517

\n
    \n

  • Companion: per-channel outgoing hop limit (ch.hops).

    \n

    Limit how far your outgoing messages travel on a specific channel, without affecting any other channel or any other node in the network. Useful for keeping a private or local-area channel confined to a small radius — for example, a home-to-nearby-relay link — without touching the rest of the city mesh.

    \n

    Configure via TerminalCLI:

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    CommandEffect
    set ch.hops <channel> <N>Limit outgoing messages on <channel> to at most N hops
    set ch.hops <channel> offRemove the limit
    get ch.hops <channel>Show current limit
    ch.hops statusList all channels with an active limit
    ch.hops clearRemove all limits
    \n
    set ch.hops Public 2         # Public channel messages travel at most 2 hops\nset ch.hops My Local Net 3   # My Local Net channel travel at most 3 hops\nset ch.hops Public off       # remove the limit\nch.hops status\n
    \n

    The limit applies to your outgoing messages only — other nodes sending on the same channel are unaffected. No repeater configuration or network coordination required.

    \n

    The repeater's group.hops.max algorithm has been updated to correctly account for sender-side pre-fill, so ch.hops and group.hops.max work together without conflict — update repeater firmware to get full compatibility.

    \n

    Settings are stored in flash and persist after reboot.

    \n
    • \n

  • Companion: toggle RxGain directly from the Radio screen.

    \n

    Long press on the Radio page cycles through RxGain modes (OFF → ON → Auto) and shows a popup confirming the new mode. The current mode is now also displayed on the Radio page itself (RxG: OFF / RxG: ON / RxG: Auto), so you can check it at a glance without going into Settings. (Auto is available on Heltec V4.2 only.)

    \n
    • \n

  • Fix: noise floor stuck at -120 in noisy environments (all node types)

    \n

    In environments with strong in-band interference, the noise floor could remain at -120 dBm for a long time instead of updating to reflect actual conditions. Fixed.

    \n
    • \n
\n" }, { "version": "MeshCore-low-power-v1.15.dev_0510", "name": "MeshCore low power - v1.15.dev_0510", "datetime": "2026-05-10T02:47:22Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/MeshCore-low-power-v1.15.dev_0510", "prerelease": false, "notes": "### v1.15_0510\r\n\r\n- **Repeater: per-type relay hop cap (`advert.hops.max` / `group.hops.max`).**\r\n\r\n Two new settings let you independently limit how far **advertisement packets** and **group messages** are relayed across the mesh, without affecting direct messages, ACKs, or path discovery.\r\n\r\n | Setting | Controls | Default |\r\n |---|---|---|\r\n | `advert.hops.max` | Max hops to relay node advertisement (ADVERT) packets | = `flood.max` |\r\n | `group.hops.max` | Max hops to relay group messages (GRP_TXT / GRP_DATA) | = `flood.max` |\r\n\r\n These are **repeater-only** settings. Configure via the **Command Line** in the MeshCore App:\r\n ```\r\n set advert.hops.max 3 # relay adverts at most 3 hops from sender\r\n set group.hops.max 5 # relay group messages at most 5 hops\r\n get advert.hops.max\r\n get group.hops.max\r\n ```\r\n\r\n Setting either value to `0` completely suppresses that packet type — no relay at all, while everything else (DM, ACK, path) continues to work normally.\r\n\r\n **Why this matters — advert storm reduction:**\r\n\r\n Each repeater periodically broadcasts an advertisement that every other repeater in range relays, up to `flood.max` times (default 64). In a network of 35 repeaters and 35 companions, advert traffic alone consumes roughly 4% of airtime. Limiting to 3 hops brings that down to under 0.5% — a 7× reduction — with no loss of communication capability. \r\n\r\n **No coordination required.** Each repeater applies its own cap independently. You do not need all repeaters to agree on the same value — even a partial deployment reduces airtime. No region configuration, no App UI changes needed.\r\n\r\n **Recommended profiles:**\r\n\r\n | Profile | `advert.hops.max` | `group.hops.max` | Airtime (35R / 35C) | Use case |\r\n |---|---|---|---|---|\r\n | Default | = `flood.max` | = `flood.max` | ~4% | No change |\r\n | Optimized | 3 | 5 | ~0.5% | Most deployments |\r\n | DM-focused | 0 | 3 | ~0.2% | Prioritise direct messages |\r\n | EU compliance | 0 | 3 | ~0.2% | Large EU networks (legal requirement) |\r\n\r\n > **Relationship with `flood.max` and path hash size:** `flood.max` is the master hop cap for **all** flood payloads. Its default of 64 is calibrated for 1-byte path hash mode. With larger hashes the packet fills up sooner — 2-byte hash caps at 32 hops, 3-byte hash caps at 21 hops — so `flood.max` is typically set to match. `advert.hops.max` and `group.hops.max` are automatically clamped to `flood.max` and work correctly with all hash sizes. If you want to suppress adverts entirely while keeping everything else unrestricted, set `advert.hops.max 0` — leave `flood.max` untouched.\r\n\r\n- **Repeater: combining hop caps with region scope for full community isolation.**\r\n\r\n `advert.hops.max` and `group.hops.max` work standalone — no coordination needed. For operators who also want to restrict which community's group messages get relayed, combine them with region rules and the companion's scope settings:\r\n\r\n 1. Each companion sets a region scope — either per-channel via the burger menu, or globally via **Settings → Experimental → Default Region Scope**. All outgoing flood packets (including DM path discovery) are tagged with the community name.\r\n 2. Each repeater: `denyf *` + `allowf ` — only relay community-tagged traffic.\r\n 3. Add `set advert.hops.max 0` to also suppress advert relay.\r\n\r\n With a global Default Region Scope, DM path discovery is tagged and passes through `denyf *` repeaters — direct messaging works normally inside the community.\r\n\r\n > **Default Region Scope** is in the App's Experimental Settings and is opt-in. Per-channel scope (burger menu) only tags group messages for that channel, not advertisements or DM path discovery.\r\n\r\n- **Companion: GPS coordinate display formats — DD / UTM / MGRS.**\r\n\r\n A new **Pos. Format** item in the Settings page lets you choose how GPS coordinates are shown on the GPS page, GPS Trace screen, and Quick Send status bar.\r\n\r\n | Format | Example |\r\n |---|---|\r\n | D\n…", "notesHtml": "

v1.15_0510

\n
    \n

  • Repeater: per-type relay hop cap (advert.hops.max / group.hops.max).

    \n

    Two new settings let you independently limit how far advertisement packets and group messages are relayed across the mesh, without affecting direct messages, ACKs, or path discovery.

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    SettingControlsDefault
    advert.hops.maxMax hops to relay node advertisement (ADVERT) packets= flood.max
    group.hops.maxMax hops to relay group messages (GRP_TXT / GRP_DATA)= flood.max
    \n

    These are repeater-only settings. Configure via the Command Line in the MeshCore App:

    \n
    set advert.hops.max 3    # relay adverts at most 3 hops from sender\nset group.hops.max 5     # relay group messages at most 5 hops\nget advert.hops.max\nget group.hops.max\n
    \n

    Setting either value to 0 completely suppresses that packet type — no relay at all, while everything else (DM, ACK, path) continues to work normally.

    \n

    Why this matters — advert storm reduction:

    \n

    Each repeater periodically broadcasts an advertisement that every other repeater in range relays, up to flood.max times (default 64). In a network of 35 repeaters and 35 companions, advert traffic alone consumes roughly 4% of airtime. Limiting to 3 hops brings that down to under 0.5% — a 7× reduction — with no loss of communication capability.

    \n

    No coordination required. Each repeater applies its own cap independently. You do not need all repeaters to agree on the same value — even a partial deployment reduces airtime. No region configuration, no App UI changes needed.

    \n

    Recommended profiles:

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    Profileadvert.hops.maxgroup.hops.maxAirtime (35R / 35C)Use case
    Default= flood.max= flood.max~4%No change
    Optimized35~0.5%Most deployments
    DM-focused03~0.2%Prioritise direct messages
    EU compliance03~0.2%Large EU networks (legal requirement)
    \n
    \n

    Relationship with flood.max and path hash size: flood.max is the master hop cap for all flood payloads. Its default of 64 is calibrated for 1-byte path hash mode. With larger hashes the packet fills up sooner — 2-byte hash caps at 32 hops, 3-byte hash caps at 21 hops — so flood.max is typically set to match. advert.hops.max and group.hops.max are automatically clamped to flood.max and work correctly with all hash sizes. If you want to suppress adverts entirely while keeping everything else unrestricted, set advert.hops.max 0 — leave flood.max untouched.

    \n
    \n
    • \n

  • Repeater: combining hop caps with region scope for full community isolation.

    \n

    advert.hops.max and group.hops.max work standalone — no coordination needed. For operators who also want to restrict which community's group messages get relayed, combine them with region rules and the companion's scope settings:

    \n
      \n
    1. Each companion sets a region scope — either per-channel via the burger menu, or globally via Settings → Experimental → Default Region Scope. All outgoing flood packets (including DM path discovery) are tagged with the community name.
      2. \n
    2. Each repeater: denyf * + allowf <community> — only relay community-tagged traffic.
      3. \n
    3. Add set advert.hops.max 0 to also suppress advert relay.
      4. \n
    \n

    With a global Default Region Scope, DM path discovery is tagged and passes through denyf * repeaters — direct messaging works normally inside the community.

    \n
    \n

    Default Region Scope is in the App's Experimental Settings and is opt-in. Per-channel scope (burger menu) only tags group messages for that channel, not advertisements or DM path discovery.

    \n
    \n
    • \n

  • Companion: GPS coordinate display formats — DD / UTM / MGRS.

    \n

    A new Pos. Format item in the Settings page lets you choose how GPS coordinates are shown on the GPS page, GPS Trace screen, and Quick Send status bar.

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    FormatExample
    D
    …
    \n
    • \n
\n" }, { "version": "MeshCore-low-power-v1.15.dev_0426", "name": "MeshCore low power - v1.15.dev_0426", "datetime": "2026-04-26T04:49:25Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/MeshCore-low-power-v1.15.dev_0426", "prerelease": false, "notes": "### v1.15_0426\r\n\r\n- **Companion: redesigned message preview.**\r\n\r\n Messages are now grouped by sender or channel so you can read a conversation in one place instead of hunting through a mixed list.\r\n\r\n From the **group list** you can scroll back through older messages from any sender or channel, including ones you've already read. Long press a group to open it.\r\n\r\n When new messages arrive, you go straight to a **new messages view** that shows only the unread ones — from all senders and channels — one by one. Once you've read them all, a single click takes you home.\r\n\r\n Long messages scroll one full page at a time with no overlap. Small arrows (`▲` / `▼`) appear at the corner of the screen to let you know there is more content above or below.\r\n\r\n- **Companion: reply directly from message preview.**\r\n\r\n While reading any message, long press to open the menu. A new **Reply** option lets you send a preset message back without leaving the screen:\r\n\r\n - If the message came from a contact, the reply goes to that contact as a private direct message.\r\n - If the message came from a channel (Public, #SOS, or any other), the reply goes back to that same channel.\r\n\r\n > **Note:** The **Quick Send** page always sends to the Public channel. Use Reply from the message preview when you want to respond to a specific contact or a non-Public channel.\r\n\r\n- **Companion: Contacts page and direct messaging.**\r\n\r\n A new **Contacts** page sits between Quick Send and Saved Locations. Long press it to open the contact list, only chat-capable nodes are listed (repeaters, room servers and sensors are excluded — they cannot receive direct messages). Select a contact and long press to send them a direct message using your Quick Send presets.\r\n\r\n- **Companion: configurable Screen Off timeout in Settings.**\r\n\r\n A new **Screen Off** item in the Settings page lets you choose how long the display stays on after the last button press: `15s` → `3min` → `Never`. Setting is saved to flash and persists after reboot.\r\n\r\n- **Companion: Flip Screen setting in Settings.**\r\n\r\n A new **Flip Screen** toggle in the Settings page rotates the display 180°. Setting is saved to flash and persists after reboot.\r\n- **fix bugs**", "notesHtml": "

v1.15_0426

\n
    \n

  • Companion: redesigned message preview.

    \n

    Messages are now grouped by sender or channel so you can read a conversation in one place instead of hunting through a mixed list.

    \n

    From the group list you can scroll back through older messages from any sender or channel, including ones you've already read. Long press a group to open it.

    \n

    When new messages arrive, you go straight to a new messages view that shows only the unread ones — from all senders and channels — one by one. Once you've read them all, a single click takes you home.

    \n

    Long messages scroll one full page at a time with no overlap. Small arrows (▲ / ▼) appear at the corner of the screen to let you know there is more content above or below.

    \n
    • \n

  • Companion: reply directly from message preview.

    \n

    While reading any message, long press to open the menu. A new Reply option lets you send a preset message back without leaving the screen:

    \n
      \n
    • If the message came from a contact, the reply goes to that contact as a private direct message.
      • \n
    • If the message came from a channel (Public, #SOS, or any other), the reply goes back to that same channel.
      • \n
    \n
    \n

    Note: The Quick Send page always sends to the Public channel. Use Reply from the message preview when you want to respond to a specific contact or a non-Public channel.

    \n
    \n
    • \n

  • Companion: Contacts page and direct messaging.

    \n

    A new Contacts page sits between Quick Send and Saved Locations. Long press it to open the contact list, only chat-capable nodes are listed (repeaters, room servers and sensors are excluded — they cannot receive direct messages). Select a contact and long press to send them a direct message using your Quick Send presets.

    \n
    • \n

  • Companion: configurable Screen Off timeout in Settings.

    \n

    A new Screen Off item in the Settings page lets you choose how long the display stays on after the last button press: 15s → 3min → Never. Setting is saved to flash and persists after reboot.

    \n
    • \n

  • Companion: Flip Screen setting in Settings.

    \n

    A new Flip Screen toggle in the Settings page rotates the display 180°. Setting is saved to flash and persists after reboot.

    \n
    • \n

  • fix bugs

    \n
    • \n
\n" }, { "version": "MeshCore-low-power-v1.15.dev_0427", "name": "Repeater feature: per-type relay hop cap (advert.hops.max, group.hops.max) - v1.15.dev_0427", "datetime": "2026-04-27T09:32:36Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/MeshCore-low-power-v1.15.dev_0427", "prerelease": true, "notes": "### v1.15_0427\r\n\r\n- **Repeater: per-type relay hop cap (`advert.hops.max` / `group.hops.max`).**\r\n\r\n Two new settings let you independently limit how far **advertisement packets** and **group messages** are relayed across the mesh, without affecting direct messages, ACKs, or path discovery.\r\n\r\n | Setting | Controls | Default |\r\n |---|---|---|\r\n | `advert.hops.max` | Max hops to relay node advertisement (ADVERT) packets | 64 (unchanged) |\r\n | `group.hops.max` | Max hops to relay group messages (GRP_TXT / GRP_DATA) | 64 (unchanged) |\r\n\r\n These are **repeater-only** settings. Configure via the **Command Line** in the MeshCore App:\r\n ```\r\n set advert.hops.max 3 # relay adverts at most 3 hops from sender\r\n set group.hops.max 5 # relay group messages at most 5 hops\r\n get advert.hops.max\r\n get group.hops.max\r\n ```\r\n\r\n Setting either value to `0` completely suppresses that packet type — no relay at all, while everything else (DM, ACK, path) continues to work normally.\r\n\r\n **Why this matters — advert storm reduction:**\r\n\r\n Each repeater periodically broadcasts an advertisement that every other repeater in range relays, up to `flood.max` times (default 64). In a network of 35 repeaters and 35 companions, advert traffic alone consumes roughly 4% of airtime. Limiting to 3 hops brings that down to under 0.5% — a 7× reduction — with no loss of communication capability. \r\n\r\n **No coordination required.** Each repeater applies its own cap independently. You do not need all repeaters to agree on the same value — even a partial deployment reduces airtime. No region configuration, no App UI changes needed.\r\n\r\n **Recommended profiles:**\r\n\r\n | Profile | `advert.hops.max` | `group.hops.max` | Airtime (35R / 35C) | Use case |\r\n |---|---|---|---|---|\r\n | Default | 64 | 64 | ~4% | No change |\r\n | Optimized | 3 | 5 | ~0.5% | Most deployments |\r\n | DM-focused | 0 | 3 | ~0.2% | Prioritise direct messages |\r\n | EU compliance | 0 | 3 | ~0.2% | Large EU networks (legal requirement) |\r\n\r\n > **Relationship with `flood.max`:** `flood.max` (long-standing setting, default 64) is the master hop cap for **all** flood payloads — DMs on first send, path discovery, group messages, adverts. It applies regardless of payload type. `advert.hops.max` and `group.hops.max` add finer per-type control on top: they can only be equal to or stricter than `flood.max`, never looser. Setting `flood.max` lower automatically clamps both values to match. If you want to suppress adverts entirely while keeping DMs unrestricted, lower `advert.hops.max` to `0` — leave `flood.max` untouched.", "notesHtml": "

v1.15_0427

\n
    \n

  • Repeater: per-type relay hop cap (advert.hops.max / group.hops.max).

    \n

    Two new settings let you independently limit how far advertisement packets and group messages are relayed across the mesh, without affecting direct messages, ACKs, or path discovery.

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    SettingControlsDefault
    advert.hops.maxMax hops to relay node advertisement (ADVERT) packets64 (unchanged)
    group.hops.maxMax hops to relay group messages (GRP_TXT / GRP_DATA)64 (unchanged)
    \n

    These are repeater-only settings. Configure via the Command Line in the MeshCore App:

    \n
    set advert.hops.max 3    # relay adverts at most 3 hops from sender\nset group.hops.max 5     # relay group messages at most 5 hops\nget advert.hops.max\nget group.hops.max\n
    \n

    Setting either value to 0 completely suppresses that packet type — no relay at all, while everything else (DM, ACK, path) continues to work normally.

    \n

    Why this matters — advert storm reduction:

    \n

    Each repeater periodically broadcasts an advertisement that every other repeater in range relays, up to flood.max times (default 64). In a network of 35 repeaters and 35 companions, advert traffic alone consumes roughly 4% of airtime. Limiting to 3 hops brings that down to under 0.5% — a 7× reduction — with no loss of communication capability.

    \n

    No coordination required. Each repeater applies its own cap independently. You do not need all repeaters to agree on the same value — even a partial deployment reduces airtime. No region configuration, no App UI changes needed.

    \n

    Recommended profiles:

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    Profileadvert.hops.maxgroup.hops.maxAirtime (35R / 35C)Use case
    Default6464~4%No change
    Optimized35~0.5%Most deployments
    DM-focused03~0.2%Prioritise direct messages
    EU compliance03~0.2%Large EU networks (legal requirement)
    \n
    \n

    Relationship with flood.max: flood.max (long-standing setting, default 64) is the master hop cap for all flood payloads — DMs on first send, path discovery, group messages, adverts. It applies regardless of payload type. advert.hops.max and group.hops.max add finer per-type control on top: they can only be equal to or stricter than flood.max, never looser. Setting flood.max lower automatically clamps both values to match. If you want to suppress adverts entirely while keeping DMs unrestricted, lower advert.hops.max to 0 — leave flood.max untouched.

    \n
    \n
    • \n
\n" }, { "version": "MeshCore-low-power-v1.15.dev_0419", "name": "MeshCore low power - v1.15.dev_0419", "datetime": "2026-04-19T04:50:53Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/MeshCore-low-power-v1.15.dev_0419", "prerelease": false, "notes": "bump to 1.15.dev", "notesHtml": "

bump to 1.15.dev

\n" }, { "version": "XIAO-S3-Wio-low-power-v1.14_0417", "name": "XIAO S3 Wio low power - v1.14_0417", "datetime": "2026-04-17T13:57:17Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/XIAO-S3-Wio-low-power-v1.14_0417", "prerelease": false, "notes": "### v1.14_0417\r\n\r\n- **Hybrid RSSI + hardware CAD channel sensing (all node types).**\r\n\r\n `isChannelActive()` now performs a two-stage check before transmitting:\r\n 1. RSSI check (fast, single SPI register read) — defers if signal is above `noise_floor + int.thresh`.\r\n 2. Hardware CAD (`scanChannel()`) — if RSSI misses, performs LoRa chirp correlation to detect signals below the noise floor (~16ms blocking scan on SX126x).\r\n\r\n RSSI also detects any in-band signal (interference, jamming), while CAD only correlates LoRa chirp patterns and ignores non-LoRa noise entirely. With hybrid, RSSI acts as the first guard — CAD only runs when the channel appears clear to RSSI.\r\n\r\n `int.thresh=0` disables both RSSI and CAD. `int.thresh=1` enables full hybrid at maximum sensitivity.\r\n\r\n **On repeaters** (single source sending): results depend on topology. Field tests with 4 repeaters (SF8/BW62.5kHz, **`txdelay=2`**, 100 messages):\r\n\r\n - **Repeaters close together / strong inter-repeater signal:** RSSI handles detection well, CAD rarely fires. Example: int.thresh=1 → **9% collision rate**.\r\n - **Spread-out repeaters, some pairs below noise floor:** RSSI misses sub-NF pairs; CAD fills the gap. Example: hybrid/CAD **8%** vs RSSI-only **17%**.\r\n - **Many hidden node pairs:** neither RSSI nor CAD helps. **Only `txdelay` reduces the floor.** Example: ~20–24% regardless of sensing method.\r\n\r\n **On companions** (multiple sources sending concurrently): channel sensing still helps, but with diminishing returns. Tested with 2 concurrent companions plus a third node sending long messages every 5s (SF8/BW62.5kHz):\r\n\r\n - `int.thresh=3`: **53–64%** of messages successfully relayed by all 4 repeaters (confirmed by hearing each relay back)\r\n - `int.thresh=0` (no sensing): **0–1%** relayed by all 4; most messages are relayed by 0–1 repeaters only — collisions occur at two levels: concurrent companion transmissions corrupt each other at the repeater, and the resulting relay transmissions from multiple repeaters collide on the way back\r\n\r\n Channel sensing — even imperfect — is far better than none. The remaining loss at int.thresh=3 is a fundamental ALOHA-style limitation: uncoordinated LoRa nodes cannot eliminate simultaneous transmission without a shared scheduling mechanism that does not exist in this protocol.\r\n\r\n- **Companion: `get/set txdelay`, `get/set direct.txdelay`, `get/set int.thresh` via [TerminalCLI](Companion_TerminalCLI_Commands.md).**\r\n\r\n Relay timing and interference threshold are now configurable without reflashing.\r\n\r\n- **Companion: \"Heard N Repeats\" alert after Quick Send.**\r\n\r\n After sending from the Quick Send screen, the display shows how many repeaters have relayed the message (e.g. \"Heard 3 Repeats\"). The counter updates in real time as each relay is heard.\r\n\r\n- **Companion: local time and date on the display.**\r\n\r\n All pages now show the current time (`HH:MM`) in the header, between the page title and the battery icon. The Home page also shows the full date at the bottom (e.g. `14 Apr 2026`).\r\n\r\n Time is sourced from the device RTC, which is synchronized upon app connection or GPS fix. Configure your local timezone offset once via [TerminalCLI](Companion_TerminalCLI_Commands.md):\r\n ```\r\n set tz.offset 7 # UTC+7\r\n set tz.offset -5 # UTC-5\r\n get tz.offset\r\n ```\r\n Offset is saved to flash. All internal timestamps remain UTC — the offset is applied only for display.\r\n\r\n- **Companion: Metric / Imperial units.**\r\n\r\n A new **Units** item in the Settings page toggles between Metric and Imperial. Setting is saved to flash and persists after reboot.\r\n\r\n | Display | Metric | Imperial |\r\n |---|---|---|\r\n | GPS Trace distance | `150m` / `1.2km` | `492ft` / `0.7mi` |\r\n | GPS page altitude | `245m` | `804ft` |\r\n | Home page date | `14 Apr 2026` | `Apr 14 2026` |\r\n\r\n- **Companion: GPS Privacy mode.**\r\n\r\n A new **GPS Privacy** item in the Settings page lets you stop GPS coordinates from being attached to Quick Send me\n…", "notesHtml": "

v1.14_0417

\n
    \n

  • Hybrid RSSI + hardware CAD channel sensing (all node types).

    \n

    isChannelActive() now performs a two-stage check before transmitting:

    \n
      \n
    1. RSSI check (fast, single SPI register read) — defers if signal is above noise_floor + int.thresh.
      2. \n
    2. Hardware CAD (scanChannel()) — if RSSI misses, performs LoRa chirp correlation to detect signals below the noise floor (~16ms blocking scan on SX126x).
      3. \n
    \n

    RSSI also detects any in-band signal (interference, jamming), while CAD only correlates LoRa chirp patterns and ignores non-LoRa noise entirely. With hybrid, RSSI acts as the first guard — CAD only runs when the channel appears clear to RSSI.

    \n

    int.thresh=0 disables both RSSI and CAD. int.thresh=1 enables full hybrid at maximum sensitivity.

    \n

    On repeaters (single source sending): results depend on topology. Field tests with 4 repeaters (SF8/BW62.5kHz, txdelay=2, 100 messages):

    \n
      \n
    • Repeaters close together / strong inter-repeater signal: RSSI handles detection well, CAD rarely fires. Example: int.thresh=1 → 9% collision rate.
      • \n
    • Spread-out repeaters, some pairs below noise floor: RSSI misses sub-NF pairs; CAD fills the gap. Example: hybrid/CAD 8% vs RSSI-only 17%.
      • \n
    • Many hidden node pairs: neither RSSI nor CAD helps. Only txdelay reduces the floor. Example: ~20–24% regardless of sensing method.
      • \n
    \n

    On companions (multiple sources sending concurrently): channel sensing still helps, but with diminishing returns. Tested with 2 concurrent companions plus a third node sending long messages every 5s (SF8/BW62.5kHz):

    \n
      \n
    • int.thresh=3: 53–64% of messages successfully relayed by all 4 repeaters (confirmed by hearing each relay back)
      • \n
    • int.thresh=0 (no sensing): 0–1% relayed by all 4; most messages are relayed by 0–1 repeaters only — collisions occur at two levels: concurrent companion transmissions corrupt each other at the repeater, and the resulting relay transmissions from multiple repeaters collide on the way back
      • \n
    \n

    Channel sensing — even imperfect — is far better than none. The remaining loss at int.thresh=3 is a fundamental ALOHA-style limitation: uncoordinated LoRa nodes cannot eliminate simultaneous transmission without a shared scheduling mechanism that does not exist in this protocol.

    \n
    • \n

  • Companion: get/set txdelay, get/set direct.txdelay, get/set int.thresh via TerminalCLI.

    \n

    Relay timing and interference threshold are now configurable without reflashing.

    \n
    • \n

  • Companion: \"Heard N Repeats\" alert after Quick Send.

    \n

    After sending from the Quick Send screen, the display shows how many repeaters have relayed the message (e.g. \"Heard 3 Repeats\"). The counter updates in real time as each relay is heard.

    \n
    • \n

  • Companion: local time and date on the display.

    \n

    All pages now show the current time (HH:MM) in the header, between the page title and the battery icon. The Home page also shows the full date at the bottom (e.g. 14 Apr 2026).

    \n

    Time is sourced from the device RTC, which is synchronized upon app connection or GPS fix. Configure your local timezone offset once via TerminalCLI:

    \n
    set tz.offset 7    # UTC+7\nset tz.offset -5   # UTC-5\nget tz.offset\n
    \n

    Offset is saved to flash. All internal timestamps remain UTC — the offset is applied only for display.

    \n
    • \n

  • Companion: Metric / Imperial units.

    \n

    A new Units item in the Settings page toggles between Metric and Imperial. Setting is saved to flash and persists after reboot.

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    DisplayMetricImperial
    GPS Trace distance150m / 1.2km492ft / 0.7mi
    GPS page altitude245m804ft
    Home page date14 Apr 2026Apr 14 2026
    \n
    • \n

  • Companion: GPS Privacy mode.

    \n

    A new GPS Privacy item in the Settings page lets you stop GPS coordinates from being attached to Quick Send me\n…

    \n
    • \n
\n" }, { "version": "RAK4631-low-power-v1.14_0417", "name": "RAK4631 low power - v1.14_0417", "datetime": "2026-04-17T13:53:55Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/RAK4631-low-power-v1.14_0417", "prerelease": false, "notes": "### v1.14_0417\r\n\r\n- **Hybrid RSSI + hardware CAD channel sensing (all node types).**\r\n\r\n `isChannelActive()` now performs a two-stage check before transmitting:\r\n 1. RSSI check (fast, single SPI register read) — defers if signal is above `noise_floor + int.thresh`.\r\n 2. Hardware CAD (`scanChannel()`) — if RSSI misses, performs LoRa chirp correlation to detect signals below the noise floor (~16ms blocking scan on SX126x).\r\n\r\n RSSI also detects any in-band signal (interference, jamming), while CAD only correlates LoRa chirp patterns and ignores non-LoRa noise entirely. With hybrid, RSSI acts as the first guard — CAD only runs when the channel appears clear to RSSI.\r\n\r\n `int.thresh=0` disables both RSSI and CAD. `int.thresh=1` enables full hybrid at maximum sensitivity.\r\n\r\n **On repeaters** (single source sending): results depend on topology. Field tests with 4 repeaters (SF8/BW62.5kHz, **`txdelay=2`**, 100 messages):\r\n\r\n - **Repeaters close together / strong inter-repeater signal:** RSSI handles detection well, CAD rarely fires. Example: int.thresh=1 → **9% collision rate**.\r\n - **Spread-out repeaters, some pairs below noise floor:** RSSI misses sub-NF pairs; CAD fills the gap. Example: hybrid/CAD **8%** vs RSSI-only **17%**.\r\n - **Many hidden node pairs:** neither RSSI nor CAD helps. **Only `txdelay` reduces the floor.** Example: ~20–24% regardless of sensing method.\r\n\r\n **On companions** (multiple sources sending concurrently): channel sensing still helps, but with diminishing returns. Tested with 2 concurrent companions plus a third node sending long messages every 5s (SF8/BW62.5kHz):\r\n\r\n - `int.thresh=3`: **53–64%** of messages successfully relayed by all 4 repeaters (confirmed by hearing each relay back)\r\n - `int.thresh=0` (no sensing): **0–1%** relayed by all 4; most messages are relayed by 0–1 repeaters only — collisions occur at two levels: concurrent companion transmissions corrupt each other at the repeater, and the resulting relay transmissions from multiple repeaters collide on the way back\r\n\r\n Channel sensing — even imperfect — is far better than none. The remaining loss at int.thresh=3 is a fundamental ALOHA-style limitation: uncoordinated LoRa nodes cannot eliminate simultaneous transmission without a shared scheduling mechanism that does not exist in this protocol.\r\n\r\n- **Companion: `get/set txdelay`, `get/set direct.txdelay`, `get/set int.thresh` via [TerminalCLI](Companion_TerminalCLI_Commands.md).**\r\n\r\n Relay timing and interference threshold are now configurable without reflashing.\r\n\r\n- **Companion: \"Heard N Repeats\" alert after Quick Send.**\r\n\r\n After sending from the Quick Send screen, the display shows how many repeaters have relayed the message (e.g. \"Heard 3 Repeats\"). The counter updates in real time as each relay is heard.\r\n\r\n- **Companion: local time and date on the display.**\r\n\r\n All pages now show the current time (`HH:MM`) in the header, between the page title and the battery icon. The Home page also shows the full date at the bottom (e.g. `14 Apr 2026`).\r\n\r\n Time is sourced from the device RTC, which is synchronized upon app connection or GPS fix. Configure your local timezone offset once via [TerminalCLI](Companion_TerminalCLI_Commands.md):\r\n ```\r\n set tz.offset 7 # UTC+7\r\n set tz.offset -5 # UTC-5\r\n get tz.offset\r\n ```\r\n Offset is saved to flash. All internal timestamps remain UTC — the offset is applied only for display.\r\n\r\n- **Companion: Metric / Imperial units.**\r\n\r\n A new **Units** item in the Settings page toggles between Metric and Imperial. Setting is saved to flash and persists after reboot.\r\n\r\n | Display | Metric | Imperial |\r\n |---|---|---|\r\n | GPS Trace distance | `150m` / `1.2km` | `492ft` / `0.7mi` |\r\n | GPS page altitude | `245m` | `804ft` |\r\n | Home page date | `14 Apr 2026` | `Apr 14 2026` |\r\n\r\n- **Companion: GPS Privacy mode.**\r\n\r\n A new **GPS Privacy** item in the Settings page lets you stop GPS coordinates from being attached to Quick Send me\n…", "notesHtml": "

v1.14_0417

\n
    \n

  • Hybrid RSSI + hardware CAD channel sensing (all node types).

    \n

    isChannelActive() now performs a two-stage check before transmitting:

    \n
      \n
    1. RSSI check (fast, single SPI register read) — defers if signal is above noise_floor + int.thresh.
      2. \n
    2. Hardware CAD (scanChannel()) — if RSSI misses, performs LoRa chirp correlation to detect signals below the noise floor (~16ms blocking scan on SX126x).
      3. \n
    \n

    RSSI also detects any in-band signal (interference, jamming), while CAD only correlates LoRa chirp patterns and ignores non-LoRa noise entirely. With hybrid, RSSI acts as the first guard — CAD only runs when the channel appears clear to RSSI.

    \n

    int.thresh=0 disables both RSSI and CAD. int.thresh=1 enables full hybrid at maximum sensitivity.

    \n

    On repeaters (single source sending): results depend on topology. Field tests with 4 repeaters (SF8/BW62.5kHz, txdelay=2, 100 messages):

    \n
      \n
    • Repeaters close together / strong inter-repeater signal: RSSI handles detection well, CAD rarely fires. Example: int.thresh=1 → 9% collision rate.
      • \n
    • Spread-out repeaters, some pairs below noise floor: RSSI misses sub-NF pairs; CAD fills the gap. Example: hybrid/CAD 8% vs RSSI-only 17%.
      • \n
    • Many hidden node pairs: neither RSSI nor CAD helps. Only txdelay reduces the floor. Example: ~20–24% regardless of sensing method.
      • \n
    \n

    On companions (multiple sources sending concurrently): channel sensing still helps, but with diminishing returns. Tested with 2 concurrent companions plus a third node sending long messages every 5s (SF8/BW62.5kHz):

    \n
      \n
    • int.thresh=3: 53–64% of messages successfully relayed by all 4 repeaters (confirmed by hearing each relay back)
      • \n
    • int.thresh=0 (no sensing): 0–1% relayed by all 4; most messages are relayed by 0–1 repeaters only — collisions occur at two levels: concurrent companion transmissions corrupt each other at the repeater, and the resulting relay transmissions from multiple repeaters collide on the way back
      • \n
    \n

    Channel sensing — even imperfect — is far better than none. The remaining loss at int.thresh=3 is a fundamental ALOHA-style limitation: uncoordinated LoRa nodes cannot eliminate simultaneous transmission without a shared scheduling mechanism that does not exist in this protocol.

    \n
    • \n

  • Companion: get/set txdelay, get/set direct.txdelay, get/set int.thresh via TerminalCLI.

    \n

    Relay timing and interference threshold are now configurable without reflashing.

    \n
    • \n

  • Companion: \"Heard N Repeats\" alert after Quick Send.

    \n

    After sending from the Quick Send screen, the display shows how many repeaters have relayed the message (e.g. \"Heard 3 Repeats\"). The counter updates in real time as each relay is heard.

    \n
    • \n

  • Companion: local time and date on the display.

    \n

    All pages now show the current time (HH:MM) in the header, between the page title and the battery icon. The Home page also shows the full date at the bottom (e.g. 14 Apr 2026).

    \n

    Time is sourced from the device RTC, which is synchronized upon app connection or GPS fix. Configure your local timezone offset once via TerminalCLI:

    \n
    set tz.offset 7    # UTC+7\nset tz.offset -5   # UTC-5\nget tz.offset\n
    \n

    Offset is saved to flash. All internal timestamps remain UTC — the offset is applied only for display.

    \n
    • \n

  • Companion: Metric / Imperial units.

    \n

    A new Units item in the Settings page toggles between Metric and Imperial. Setting is saved to flash and persists after reboot.

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    DisplayMetricImperial
    GPS Trace distance150m / 1.2km492ft / 0.7mi
    GPS page altitude245m804ft
    Home page date14 Apr 2026Apr 14 2026
    \n
    • \n

  • Companion: GPS Privacy mode.

    \n

    A new GPS Privacy item in the Settings page lets you stop GPS coordinates from being attached to Quick Send me\n…

    \n
    • \n
\n" }, { "version": "Heltec-V4-OLED-low-power-v1.14_0417", "name": "Heltec V4 OLED low power - v1.14_0417", "datetime": "2026-04-17T14:04:26Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/Heltec-V4-OLED-low-power-v1.14_0417", "prerelease": false, "notes": "### v1.14_0417\r\n\r\n- **Hybrid RSSI + hardware CAD channel sensing (all node types).**\r\n\r\n `isChannelActive()` now performs a two-stage check before transmitting:\r\n 1. RSSI check (fast, single SPI register read) — defers if signal is above `noise_floor + int.thresh`.\r\n 2. Hardware CAD (`scanChannel()`) — if RSSI misses, performs LoRa chirp correlation to detect signals below the noise floor (~16ms blocking scan on SX126x).\r\n\r\n RSSI also detects any in-band signal (interference, jamming), while CAD only correlates LoRa chirp patterns and ignores non-LoRa noise entirely. With hybrid, RSSI acts as the first guard — CAD only runs when the channel appears clear to RSSI.\r\n\r\n `int.thresh=0` disables both RSSI and CAD. `int.thresh=1` enables full hybrid at maximum sensitivity.\r\n\r\n **On repeaters** (single source sending): results depend on topology. Field tests with 4 repeaters (SF8/BW62.5kHz, **`txdelay=2`**, 100 messages):\r\n\r\n - **Repeaters close together / strong inter-repeater signal:** RSSI handles detection well, CAD rarely fires. Example: int.thresh=1 → **9% collision rate**.\r\n - **Spread-out repeaters, some pairs below noise floor:** RSSI misses sub-NF pairs; CAD fills the gap. Example: hybrid/CAD **8%** vs RSSI-only **17%**.\r\n - **Many hidden node pairs:** neither RSSI nor CAD helps. **Only `txdelay` reduces the floor.** Example: ~20–24% regardless of sensing method.\r\n\r\n **On companions** (multiple sources sending concurrently): channel sensing still helps, but with diminishing returns. Tested with 2 concurrent companions plus a third node sending long messages every 5s (SF8/BW62.5kHz):\r\n\r\n - `int.thresh=3`: **53–64%** of messages successfully relayed by all 4 repeaters (confirmed by hearing each relay back)\r\n - `int.thresh=0` (no sensing): **0–1%** relayed by all 4; most messages are relayed by 0–1 repeaters only — collisions occur at two levels: concurrent companion transmissions corrupt each other at the repeater, and the resulting relay transmissions from multiple repeaters collide on the way back\r\n\r\n Channel sensing — even imperfect — is far better than none. The remaining loss at int.thresh=3 is a fundamental ALOHA-style limitation: uncoordinated LoRa nodes cannot eliminate simultaneous transmission without a shared scheduling mechanism that does not exist in this protocol.\r\n\r\n- **Companion: `get/set txdelay`, `get/set direct.txdelay`, `get/set int.thresh` via [TerminalCLI](Companion_TerminalCLI_Commands.md).**\r\n\r\n Relay timing and interference threshold are now configurable without reflashing.\r\n\r\n- **Companion: \"Heard N Repeats\" alert after Quick Send.**\r\n\r\n After sending from the Quick Send screen, the display shows how many repeaters have relayed the message (e.g. \"Heard 3 Repeats\"). The counter updates in real time as each relay is heard.\r\n\r\n- **Companion: local time and date on the display.**\r\n\r\n All pages now show the current time (`HH:MM`) in the header, between the page title and the battery icon. The Home page also shows the full date at the bottom (e.g. `14 Apr 2026`).\r\n\r\n Time is sourced from the device RTC, which is synchronized upon app connection or GPS fix. Configure your local timezone offset once via [TerminalCLI](Companion_TerminalCLI_Commands.md):\r\n ```\r\n set tz.offset 7 # UTC+7\r\n set tz.offset -5 # UTC-5\r\n get tz.offset\r\n ```\r\n Offset is saved to flash. All internal timestamps remain UTC — the offset is applied only for display.\r\n\r\n- **Companion: Metric / Imperial units.**\r\n\r\n A new **Units** item in the Settings page toggles between Metric and Imperial. Setting is saved to flash and persists after reboot.\r\n\r\n | Display | Metric | Imperial |\r\n |---|---|---|\r\n | GPS Trace distance | `150m` / `1.2km` | `492ft` / `0.7mi` |\r\n | GPS page altitude | `245m` | `804ft` |\r\n | Home page date | `14 Apr 2026` | `Apr 14 2026` |\r\n\r\n- **Companion: GPS Privacy mode.**\r\n\r\n A new **GPS Privacy** item in the Settings page lets you stop GPS coordinates from being attached to Quick Send me\n…", "notesHtml": "

v1.14_0417

\n
    \n

  • Hybrid RSSI + hardware CAD channel sensing (all node types).

    \n

    isChannelActive() now performs a two-stage check before transmitting:

    \n
      \n
    1. RSSI check (fast, single SPI register read) — defers if signal is above noise_floor + int.thresh.
      2. \n
    2. Hardware CAD (scanChannel()) — if RSSI misses, performs LoRa chirp correlation to detect signals below the noise floor (~16ms blocking scan on SX126x).
      3. \n
    \n

    RSSI also detects any in-band signal (interference, jamming), while CAD only correlates LoRa chirp patterns and ignores non-LoRa noise entirely. With hybrid, RSSI acts as the first guard — CAD only runs when the channel appears clear to RSSI.

    \n

    int.thresh=0 disables both RSSI and CAD. int.thresh=1 enables full hybrid at maximum sensitivity.

    \n

    On repeaters (single source sending): results depend on topology. Field tests with 4 repeaters (SF8/BW62.5kHz, txdelay=2, 100 messages):

    \n
      \n
    • Repeaters close together / strong inter-repeater signal: RSSI handles detection well, CAD rarely fires. Example: int.thresh=1 → 9% collision rate.
      • \n
    • Spread-out repeaters, some pairs below noise floor: RSSI misses sub-NF pairs; CAD fills the gap. Example: hybrid/CAD 8% vs RSSI-only 17%.
      • \n
    • Many hidden node pairs: neither RSSI nor CAD helps. Only txdelay reduces the floor. Example: ~20–24% regardless of sensing method.
      • \n
    \n

    On companions (multiple sources sending concurrently): channel sensing still helps, but with diminishing returns. Tested with 2 concurrent companions plus a third node sending long messages every 5s (SF8/BW62.5kHz):

    \n
      \n
    • int.thresh=3: 53–64% of messages successfully relayed by all 4 repeaters (confirmed by hearing each relay back)
      • \n
    • int.thresh=0 (no sensing): 0–1% relayed by all 4; most messages are relayed by 0–1 repeaters only — collisions occur at two levels: concurrent companion transmissions corrupt each other at the repeater, and the resulting relay transmissions from multiple repeaters collide on the way back
      • \n
    \n

    Channel sensing — even imperfect — is far better than none. The remaining loss at int.thresh=3 is a fundamental ALOHA-style limitation: uncoordinated LoRa nodes cannot eliminate simultaneous transmission without a shared scheduling mechanism that does not exist in this protocol.

    \n
    • \n

  • Companion: get/set txdelay, get/set direct.txdelay, get/set int.thresh via TerminalCLI.

    \n

    Relay timing and interference threshold are now configurable without reflashing.

    \n
    • \n

  • Companion: \"Heard N Repeats\" alert after Quick Send.

    \n

    After sending from the Quick Send screen, the display shows how many repeaters have relayed the message (e.g. \"Heard 3 Repeats\"). The counter updates in real time as each relay is heard.

    \n
    • \n

  • Companion: local time and date on the display.

    \n

    All pages now show the current time (HH:MM) in the header, between the page title and the battery icon. The Home page also shows the full date at the bottom (e.g. 14 Apr 2026).

    \n

    Time is sourced from the device RTC, which is synchronized upon app connection or GPS fix. Configure your local timezone offset once via TerminalCLI:

    \n
    set tz.offset 7    # UTC+7\nset tz.offset -5   # UTC-5\nget tz.offset\n
    \n

    Offset is saved to flash. All internal timestamps remain UTC — the offset is applied only for display.

    \n
    • \n

  • Companion: Metric / Imperial units.

    \n

    A new Units item in the Settings page toggles between Metric and Imperial. Setting is saved to flash and persists after reboot.

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    DisplayMetricImperial
    GPS Trace distance150m / 1.2km492ft / 0.7mi
    GPS page altitude245m804ft
    Home page date14 Apr 2026Apr 14 2026
    \n
    • \n

  • Companion: GPS Privacy mode.

    \n

    A new GPS Privacy item in the Settings page lets you stop GPS coordinates from being attached to Quick Send me\n…

    \n
    • \n
\n" }, { "version": "Heltec-V3-WSL3-low-power-v1.14_0417", "name": "Heltec V3 & WSL3 low power - v1.14_0417", "datetime": "2026-04-17T14:00:08Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/Heltec-V3-WSL3-low-power-v1.14_0417", "prerelease": false, "notes": "### v1.14_0417\r\n\r\n- **Hybrid RSSI + hardware CAD channel sensing (all node types).**\r\n\r\n `isChannelActive()` now performs a two-stage check before transmitting:\r\n 1. RSSI check (fast, single SPI register read) — defers if signal is above `noise_floor + int.thresh`.\r\n 2. Hardware CAD (`scanChannel()`) — if RSSI misses, performs LoRa chirp correlation to detect signals below the noise floor (~16ms blocking scan on SX126x).\r\n\r\n RSSI also detects any in-band signal (interference, jamming), while CAD only correlates LoRa chirp patterns and ignores non-LoRa noise entirely. With hybrid, RSSI acts as the first guard — CAD only runs when the channel appears clear to RSSI.\r\n\r\n `int.thresh=0` disables both RSSI and CAD. `int.thresh=1` enables full hybrid at maximum sensitivity.\r\n\r\n **On repeaters** (single source sending): results depend on topology. Field tests with 4 repeaters (SF8/BW62.5kHz, **`txdelay=2`**, 100 messages):\r\n\r\n - **Repeaters close together / strong inter-repeater signal:** RSSI handles detection well, CAD rarely fires. Example: int.thresh=1 → **9% collision rate**.\r\n - **Spread-out repeaters, some pairs below noise floor:** RSSI misses sub-NF pairs; CAD fills the gap. Example: hybrid/CAD **8%** vs RSSI-only **17%**.\r\n - **Many hidden node pairs:** neither RSSI nor CAD helps. **Only `txdelay` reduces the floor.** Example: ~20–24% regardless of sensing method.\r\n\r\n **On companions** (multiple sources sending concurrently): channel sensing still helps, but with diminishing returns. Tested with 2 concurrent companions plus a third node sending long messages every 5s (SF8/BW62.5kHz):\r\n\r\n - `int.thresh=3`: **53–64%** of messages successfully relayed by all 4 repeaters (confirmed by hearing each relay back)\r\n - `int.thresh=0` (no sensing): **0–1%** relayed by all 4; most messages are relayed by 0–1 repeaters only — collisions occur at two levels: concurrent companion transmissions corrupt each other at the repeater, and the resulting relay transmissions from multiple repeaters collide on the way back\r\n\r\n Channel sensing — even imperfect — is far better than none. The remaining loss at int.thresh=3 is a fundamental ALOHA-style limitation: uncoordinated LoRa nodes cannot eliminate simultaneous transmission without a shared scheduling mechanism that does not exist in this protocol.\r\n\r\n- **Companion: `get/set txdelay`, `get/set direct.txdelay`, `get/set int.thresh` via [TerminalCLI](Companion_TerminalCLI_Commands.md).**\r\n\r\n Relay timing and interference threshold are now configurable without reflashing.\r\n\r\n- **Companion: \"Heard N Repeats\" alert after Quick Send.**\r\n\r\n After sending from the Quick Send screen, the display shows how many repeaters have relayed the message (e.g. \"Heard 3 Repeats\"). The counter updates in real time as each relay is heard.\r\n\r\n- **Companion: local time and date on the display.**\r\n\r\n All pages now show the current time (`HH:MM`) in the header, between the page title and the battery icon. The Home page also shows the full date at the bottom (e.g. `14 Apr 2026`).\r\n\r\n Time is sourced from the device RTC, which is synchronized upon app connection or GPS fix. Configure your local timezone offset once via [TerminalCLI](Companion_TerminalCLI_Commands.md):\r\n ```\r\n set tz.offset 7 # UTC+7\r\n set tz.offset -5 # UTC-5\r\n get tz.offset\r\n ```\r\n Offset is saved to flash. All internal timestamps remain UTC — the offset is applied only for display.\r\n\r\n- **Companion: Metric / Imperial units.**\r\n\r\n A new **Units** item in the Settings page toggles between Metric and Imperial. Setting is saved to flash and persists after reboot.\r\n\r\n | Display | Metric | Imperial |\r\n |---|---|---|\r\n | GPS Trace distance | `150m` / `1.2km` | `492ft` / `0.7mi` |\r\n | GPS page altitude | `245m` | `804ft` |\r\n | Home page date | `14 Apr 2026` | `Apr 14 2026` |\r\n\r\n- **Companion: GPS Privacy mode.**\r\n\r\n A new **GPS Privacy** item in the Settings page lets you stop GPS coordinates from being attached to Quick Send me\n…", "notesHtml": "

v1.14_0417

\n
    \n

  • Hybrid RSSI + hardware CAD channel sensing (all node types).

    \n

    isChannelActive() now performs a two-stage check before transmitting:

    \n
      \n
    1. RSSI check (fast, single SPI register read) — defers if signal is above noise_floor + int.thresh.
      2. \n
    2. Hardware CAD (scanChannel()) — if RSSI misses, performs LoRa chirp correlation to detect signals below the noise floor (~16ms blocking scan on SX126x).
      3. \n
    \n

    RSSI also detects any in-band signal (interference, jamming), while CAD only correlates LoRa chirp patterns and ignores non-LoRa noise entirely. With hybrid, RSSI acts as the first guard — CAD only runs when the channel appears clear to RSSI.

    \n

    int.thresh=0 disables both RSSI and CAD. int.thresh=1 enables full hybrid at maximum sensitivity.

    \n

    On repeaters (single source sending): results depend on topology. Field tests with 4 repeaters (SF8/BW62.5kHz, txdelay=2, 100 messages):

    \n
      \n
    • Repeaters close together / strong inter-repeater signal: RSSI handles detection well, CAD rarely fires. Example: int.thresh=1 → 9% collision rate.
      • \n
    • Spread-out repeaters, some pairs below noise floor: RSSI misses sub-NF pairs; CAD fills the gap. Example: hybrid/CAD 8% vs RSSI-only 17%.
      • \n
    • Many hidden node pairs: neither RSSI nor CAD helps. Only txdelay reduces the floor. Example: ~20–24% regardless of sensing method.
      • \n
    \n

    On companions (multiple sources sending concurrently): channel sensing still helps, but with diminishing returns. Tested with 2 concurrent companions plus a third node sending long messages every 5s (SF8/BW62.5kHz):

    \n
      \n
    • int.thresh=3: 53–64% of messages successfully relayed by all 4 repeaters (confirmed by hearing each relay back)
      • \n
    • int.thresh=0 (no sensing): 0–1% relayed by all 4; most messages are relayed by 0–1 repeaters only — collisions occur at two levels: concurrent companion transmissions corrupt each other at the repeater, and the resulting relay transmissions from multiple repeaters collide on the way back
      • \n
    \n

    Channel sensing — even imperfect — is far better than none. The remaining loss at int.thresh=3 is a fundamental ALOHA-style limitation: uncoordinated LoRa nodes cannot eliminate simultaneous transmission without a shared scheduling mechanism that does not exist in this protocol.

    \n
    • \n

  • Companion: get/set txdelay, get/set direct.txdelay, get/set int.thresh via TerminalCLI.

    \n

    Relay timing and interference threshold are now configurable without reflashing.

    \n
    • \n

  • Companion: \"Heard N Repeats\" alert after Quick Send.

    \n

    After sending from the Quick Send screen, the display shows how many repeaters have relayed the message (e.g. \"Heard 3 Repeats\"). The counter updates in real time as each relay is heard.

    \n
    • \n

  • Companion: local time and date on the display.

    \n

    All pages now show the current time (HH:MM) in the header, between the page title and the battery icon. The Home page also shows the full date at the bottom (e.g. 14 Apr 2026).

    \n

    Time is sourced from the device RTC, which is synchronized upon app connection or GPS fix. Configure your local timezone offset once via TerminalCLI:

    \n
    set tz.offset 7    # UTC+7\nset tz.offset -5   # UTC-5\nget tz.offset\n
    \n

    Offset is saved to flash. All internal timestamps remain UTC — the offset is applied only for display.

    \n
    • \n

  • Companion: Metric / Imperial units.

    \n

    A new Units item in the Settings page toggles between Metric and Imperial. Setting is saved to flash and persists after reboot.

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    DisplayMetricImperial
    GPS Trace distance150m / 1.2km492ft / 0.7mi
    GPS page altitude245m804ft
    Home page date14 Apr 2026Apr 14 2026
    \n
    • \n

  • Companion: GPS Privacy mode.

    \n

    A new GPS Privacy item in the Settings page lets you stop GPS coordinates from being attached to Quick Send me\n…

    \n
    • \n
\n" }, { "version": "Heltec-V4-OLED-low-power-v1.14_0410", "name": "Heltec V4 OLED low power - v1.14_0410", "datetime": "2026-04-10T04:40:07Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/Heltec-V4-OLED-low-power-v1.14_0410", "prerelease": false, "notes": "### v1.14_0410\r\n\r\n- **Message preview: scroll long messages & see all 256 buffered messages.**\r\n\r\n The message preview screen is rebuilt from the ground up. All 256 buffered messages are now navigable — previously capped at 32. Long messages that overflow the screen can be scrolled line by line.\r\n\r\n #### Button controls in message preview\r\n\r\n | Action | Effect |\r\n |---|---|\r\n | **Single click** | Scroll text down (3 lines); advances to next older message at end of text |\r\n | **Double click** | Scroll text up (3 lines); goes to next newer message at top; at newest → home |\r\n | **Long press** | Open menu: **Save location** *(if message has GPS coords)* / **Home** |\r\n\r\n #### Counter and unread tracking\r\n\r\n ```\r\n ┌──────────────────────────────┐\r\n │ 5/19 42s │\r\n │──────────────────────────────│\r\n │ (2) Alien: │\r\n │ Hello everyone, just wanted │\r\n │ to check in. We made it to │\r\n │ base camp safe and sound. │\r\n │ ▼ │\r\n └──────────────────────────────┘\r\n ```\r\n\r\n `5/19` = viewing message 5 (newest = 19, oldest = 1). `▼` = more text below. `42s` = time since received. The counter tracks unread messages — when you close preview and return, only new messages since last session are counted.\r\n\r\n- **Saved Locations: save GPS coordinates from messages to flash.**\r\n\r\n When viewing a message with GPS coordinates, long press opens a menu. Choose **Save location**, then pick one of 10 slots to save into. Saved locations persist in flash memory — they survive reboot.\r\n\r\n Navigate to the **SAVED LOCS** page on the home screen to browse your saved locations and open the GPS Trace screen for any of them.\r\n\r\n ```\r\n ┌──────────────────────────────┐\r\n │ SAVED 2/10 │\r\n │──────────────────────────────│\r\n │ > Alien: I need help │\r\n │ Big Boy: Heading home │\r\n │ │\r\n │ │\r\n └──────────────────────────────┘\r\n ```\r\n\r\n Each entry shows **sender + message snippet** so you can identify entries even when multiple locations from the same person are saved.\r\n\r\n | Press | Effect |\r\n |---|---|\r\n | Single click | Move highlight to next entry |\r\n | Long press | Open GPS Trace screen for that location |\r\n | Double click | Return to home |\r\n\r\n- **GPS Trace screen: live distance & bearing to a saved location.**\r\n\r\n ```\r\n ┌──────────────────────────────┐\r\n │ Alien: I need help 5m │\r\n │──────────────────────────────│\r\n │ 10.7769 106.7009 │\r\n │ │\r\n │ 1.2km │\r\n │ │\r\n │ 247° WSW │\r\n └──────────────────────────────┘\r\n ```\r\n\r\n The timer in the top-right corner shows how long you have been on this Trace screen. Requires own GPS fix for distance/bearing. Raw coordinates are always shown. Any button returns to the Saved Locations list.\r\n\r\n- **Saved locations CLI commands (TerminalCLI).**\r\n\r\n Manage saved locations from the terminal without touching the display:\r\n\r\n | Command | Effect |\r\n |---|---|\r\n | `get loc` | List all occupied slots (`N:lat,lon:name`, N is 0-based) |\r\n | `set loc. ` | Save to slot N (0-based; display shows 1–10) |\r\n | `del loc.` | Clear slot N (0-based) |\r\n | `del loc.all` | Clear all slots |", "notesHtml": "

v1.14_0410

\n
    \n

  • Message preview: scroll long messages & see all 256 buffered messages.

    \n

    The message preview screen is rebuilt from the ground up. All 256 buffered messages are now navigable — previously capped at 32. Long messages that overflow the screen can be scrolled line by line.

    \n

    Button controls in message preview

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    ActionEffect
    Single clickScroll text down (3 lines); advances to next older message at end of text
    Double clickScroll text up (3 lines); goes to next newer message at top; at newest → home
    Long pressOpen menu: Save location (if message has GPS coords) / Home
    \n

    Counter and unread tracking

    \n
    ┌──────────────────────────────┐\n│ 5/19                    42s  │\n│──────────────────────────────│\n│ (2) Alien:                   │\n│ Hello everyone, just wanted  │\n│ to check in. We made it to   │\n│ base camp safe and sound.    │\n│                           ▼  │\n└──────────────────────────────┘\n
    \n

    5/19 = viewing message 5 (newest = 19, oldest = 1). ▼ = more text below. 42s = time since received. The counter tracks unread messages — when you close preview and return, only new messages since last session are counted.

    \n
    • \n

  • Saved Locations: save GPS coordinates from messages to flash.

    \n

    When viewing a message with GPS coordinates, long press opens a menu. Choose Save location, then pick one of 10 slots to save into. Saved locations persist in flash memory — they survive reboot.

    \n

    Navigate to the SAVED LOCS page on the home screen to browse your saved locations and open the GPS Trace screen for any of them.

    \n
    ┌──────────────────────────────┐\n│ SAVED  2/10                  │\n│──────────────────────────────│\n│ > Alien: I need help         │\n│   Big Boy: Heading home      │\n│                              │\n│                              │\n└──────────────────────────────┘\n
    \n

    Each entry shows sender + message snippet so you can identify entries even when multiple locations from the same person are saved.

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    PressEffect
    Single clickMove highlight to next entry
    Long pressOpen GPS Trace screen for that location
    Double clickReturn to home
    \n
    • \n

  • GPS Trace screen: live distance & bearing to a saved location.

    \n
    ┌──────────────────────────────┐\n│ Alien: I need help       5m  │\n│──────────────────────────────│\n│      10.7769  106.7009       │\n│                              │\n│           1.2km              │\n│                              │\n│          247°  WSW           │\n└──────────────────────────────┘\n
    \n

    The timer in the top-right corner shows how long you have been on this Trace screen. Requires own GPS fix for distance/bearing. Raw coordinates are always shown. Any button returns to the Saved Locations list.

    \n
    • \n

  • Saved locations CLI commands (TerminalCLI).

    \n

    Manage saved locations from the terminal without touching the display:

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    CommandEffect
    get locList all occupied slots (N:lat,lon:name, N is 0-based)
    set loc.<N> <name> <lat> <lon>Save to slot N (0-based; display shows 1–10)
    del loc.<N>Clear slot N (0-based)
    del loc.allClear all slots
    \n
    • \n
\n" }, { "version": "Heltec-V3-WSL3-low-power-v1.14_0410", "name": "Heltec V3 & WSL3 low power - v1.14_0410", "datetime": "2026-04-10T04:32:34Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/Heltec-V3-WSL3-low-power-v1.14_0410", "prerelease": false, "notes": "### v1.14_0410\r\n\r\n- **Message preview: scroll long messages & see all 256 buffered messages.**\r\n\r\n The message preview screen is rebuilt from the ground up. All 256 buffered messages are now navigable — previously capped at 32. Long messages that overflow the screen can be scrolled line by line.\r\n\r\n #### Button controls in message preview\r\n\r\n | Action | Effect |\r\n |---|---|\r\n | **Single click** | Scroll text down (3 lines); advances to next older message at end of text |\r\n | **Double click** | Scroll text up (3 lines); goes to next newer message at top; at newest → home |\r\n | **Long press** | Open menu: **Save location** *(if message has GPS coords)* / **Home** |\r\n\r\n #### Counter and unread tracking\r\n\r\n ```\r\n ┌──────────────────────────────┐\r\n │ 5/19 42s │\r\n │──────────────────────────────│\r\n │ (2) Alien: │\r\n │ Hello everyone, just wanted │\r\n │ to check in. We made it to │\r\n │ base camp safe and sound. │\r\n │ ▼ │\r\n └──────────────────────────────┘\r\n ```\r\n\r\n `5/19` = viewing message 5 (newest = 19, oldest = 1). `▼` = more text below. `42s` = time since received. The counter tracks unread messages — when you close preview and return, only new messages since last session are counted.\r\n\r\n- **Saved Locations: save GPS coordinates from messages to flash.**\r\n\r\n When viewing a message with GPS coordinates, long press opens a menu. Choose **Save location**, then pick one of 10 slots to save into. Saved locations persist in flash memory — they survive reboot.\r\n\r\n Navigate to the **SAVED LOCS** page on the home screen to browse your saved locations and open the GPS Trace screen for any of them.\r\n\r\n ```\r\n ┌──────────────────────────────┐\r\n │ SAVED 2/10 │\r\n │──────────────────────────────│\r\n │ > Alien: I need help │\r\n │ Big Boy: Heading home │\r\n │ │\r\n │ │\r\n └──────────────────────────────┘\r\n ```\r\n\r\n Each entry shows **sender + message snippet** so you can identify entries even when multiple locations from the same person are saved.\r\n\r\n | Press | Effect |\r\n |---|---|\r\n | Single click | Move highlight to next entry |\r\n | Long press | Open GPS Trace screen for that location |\r\n | Double click | Return to home |\r\n\r\n- **GPS Trace screen: live distance & bearing to a saved location.**\r\n\r\n ```\r\n ┌──────────────────────────────┐\r\n │ Alien: I need help 5m │\r\n │──────────────────────────────│\r\n │ 10.7769 106.7009 │\r\n │ │\r\n │ 1.2km │\r\n │ │\r\n │ 247° WSW │\r\n └──────────────────────────────┘\r\n ```\r\n\r\n The timer in the top-right corner shows how long you have been on this Trace screen. Requires own GPS fix for distance/bearing. Raw coordinates are always shown. Any button returns to the Saved Locations list.\r\n\r\n- **Saved locations CLI commands (TerminalCLI).**\r\n\r\n Manage saved locations from the terminal without touching the display:\r\n\r\n | Command | Effect |\r\n |---|---|\r\n | `get loc` | List all occupied slots (`N:lat,lon:name`, N is 0-based) |\r\n | `set loc. ` | Save to slot N (0-based; display shows 1–10) |\r\n | `del loc.` | Clear slot N (0-based) |\r\n | `del loc.all` | Clear all slots |", "notesHtml": "

v1.14_0410

\n
    \n

  • Message preview: scroll long messages & see all 256 buffered messages.

    \n

    The message preview screen is rebuilt from the ground up. All 256 buffered messages are now navigable — previously capped at 32. Long messages that overflow the screen can be scrolled line by line.

    \n

    Button controls in message preview

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    ActionEffect
    Single clickScroll text down (3 lines); advances to next older message at end of text
    Double clickScroll text up (3 lines); goes to next newer message at top; at newest → home
    Long pressOpen menu: Save location (if message has GPS coords) / Home
    \n

    Counter and unread tracking

    \n
    ┌──────────────────────────────┐\n│ 5/19                    42s  │\n│──────────────────────────────│\n│ (2) Alien:                   │\n│ Hello everyone, just wanted  │\n│ to check in. We made it to   │\n│ base camp safe and sound.    │\n│                           ▼  │\n└──────────────────────────────┘\n
    \n

    5/19 = viewing message 5 (newest = 19, oldest = 1). ▼ = more text below. 42s = time since received. The counter tracks unread messages — when you close preview and return, only new messages since last session are counted.

    \n
    • \n

  • Saved Locations: save GPS coordinates from messages to flash.

    \n

    When viewing a message with GPS coordinates, long press opens a menu. Choose Save location, then pick one of 10 slots to save into. Saved locations persist in flash memory — they survive reboot.

    \n

    Navigate to the SAVED LOCS page on the home screen to browse your saved locations and open the GPS Trace screen for any of them.

    \n
    ┌──────────────────────────────┐\n│ SAVED  2/10                  │\n│──────────────────────────────│\n│ > Alien: I need help         │\n│   Big Boy: Heading home      │\n│                              │\n│                              │\n└──────────────────────────────┘\n
    \n

    Each entry shows sender + message snippet so you can identify entries even when multiple locations from the same person are saved.

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    PressEffect
    Single clickMove highlight to next entry
    Long pressOpen GPS Trace screen for that location
    Double clickReturn to home
    \n
    • \n

  • GPS Trace screen: live distance & bearing to a saved location.

    \n
    ┌──────────────────────────────┐\n│ Alien: I need help       5m  │\n│──────────────────────────────│\n│      10.7769  106.7009       │\n│                              │\n│           1.2km              │\n│                              │\n│          247°  WSW           │\n└──────────────────────────────┘\n
    \n

    The timer in the top-right corner shows how long you have been on this Trace screen. Requires own GPS fix for distance/bearing. Raw coordinates are always shown. Any button returns to the Saved Locations list.

    \n
    • \n

  • Saved locations CLI commands (TerminalCLI).

    \n

    Manage saved locations from the terminal without touching the display:

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    CommandEffect
    get locList all occupied slots (N:lat,lon:name, N is 0-based)
    set loc.<N> <name> <lat> <lon>Save to slot N (0-based; display shows 1–10)
    del loc.<N>Clear slot N (0-based)
    del loc.allClear all slots
    \n
    • \n
\n" }, { "version": "RAK4631-low-power-v1.14_0404", "name": "RAK4631 low power - v1.14_0404", "datetime": "2026-04-04T10:34:37Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/RAK4631-low-power-v1.14_0404", "prerelease": false, "notes": "Ported the BLE random disconnection fix from ESP32 to nRF52.", "notesHtml": "

Ported the BLE random disconnection fix from ESP32 to nRF52.

\n" }, { "version": "Heltec-V4-OLED-low-power-v1.14_0404", "name": "Heltec V4 OLED low power - v1.14_0404", "datetime": "2026-04-04T10:51:14Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/Heltec-V4-OLED-low-power-v1.14_0404", "prerelease": false, "notes": "### v1.14_0404\r\n\r\n- **Quick Send and Settings — control your Companion without a phone.**\r\n\r\n Two new pages are added to the Companion's display, accessible without a phone or app.\r\n\r\n #### Button controls\r\n\r\n - **Single click / Double click** — navigate between pages (next / previous)\r\n - **Long press on FIRST page** — reopen unread message preview (up to 32 messages buffered)\r\n - **Long press** on Quick Send or Settings — enter the page; active item highlights\r\n - Single click = next item · Double click = exit · Long press = confirm\r\n\r\n #### Quick Send\r\n\r\n Send a short status message directly over LoRa to the public channel — no typing, no phone needed. Useful when your phone is dead or unavailable.\r\n\r\n GPS coordinates are automatically appended if available (e.g. `I'm OK @10.7769,106.7009`). If GPS has no current fix, last known coordinates are used with a `?` prefix so you know before sending.\r\n\r\n **10 built-in presets:**\r\n - I'm OK\r\n - On my way\r\n - I need help\r\n - Everyone OK here\r\n - Wait for me\r\n - Heading home\r\n - Running late\r\n - Lost contact, call me\r\n - Battery low, signing off\r\n - All clear\r\n\r\n **Customize via TerminalCLI** — changes are saved to flash and persist after reboot:\r\n ```\r\n get quick list all current presets\r\n set quick.0 Arrived at camp set preset at index 0\r\n set quick.reset restore all 10 built-in defaults\r\n ```\r\n\r\n #### Settings\r\n\r\n A scrollable list of device settings, controlled directly from the button:\r\n\r\n | Item | Action |\r\n |---|---|\r\n | BLE | Toggle Bluetooth on/off (shows connection state) |\r\n | Repeat | Toggle repeat mode on/off |\r\n | RxGain | Cycle RxGain mode: OFF → ON → AUTO *(AUTO: V4.2 only)* |\r\n | Buzzer | Toggle buzzer on/muted *(boards with buzzer only)* |\r\n | Send Advert | Broadcast your presence to nearby nodes |\r\n | Start OTA | Start OTA update mode — connect to `MeshCore-OTA` WiFi and go to `192.168.4.1/update` |\r\n | Shutdown | Power off the device |\r\n\r\n- **Heltec V4.3 support (KCT8103L FEM).**\r\n Firmware automatically detects V4.2 / V4.3 at boot — no configuration required. V4.3 replaces the GC1109 FEM with KCT8103L, which supports explicit LNA/bypass RX mode selection via `radio.rxgain`.\r\n\r\n | Mode | Description |\r\n |---|---|\r\n | `on` *(default)* | FEM LNA active — best sensitivity |\r\n | `off` | FEM bypass — SX1262 boosted gain compensates, better in high-interference environments near strong transmitters |\r\n\r\n > V4.3 does **not** support `auto` mode — use `on` or `off`.\r\n\r\n **TerminalCLI** (Companion app), **Command Line** (Repeater / Room Server):\r\n ```\r\n set radio.rxgain on\r\n set radio.rxgain off\r\n get radio.rxgain\r\n ```\r\n \r\n Setting is saved and restored after reboot.\r\n\r\n- **Unified firmware for \"No Display\" hardware variants.**\r\n\r\n A single firmware binary now runs on both OLED and no-display hardware — no separate build required. The display is detected automatically at boot via I2C probe.\r\n\r\n | Hardware | Detected as |\r\n |---|---|\r\n | Heltec V4.2 with OLED | Heltec V4.2 OLED |\r\n | Heltec V4.2 without OLED | Heltec V4.2 No Display |\r\n | Heltec V4.3 with OLED | Heltec V4.3 OLED |\r\n | Heltec V4.3 without OLED | Heltec V4.3 No Display |\r\n\r\n The device name shown in the MeshCore app reflects the actual hardware detected. On no-display hardware, the user button has no effect (previously it could trigger unintended I2C writes).", "notesHtml": "

v1.14_0404

\n
    \n

  • Quick Send and Settings — control your Companion without a phone.

    \n

    Two new pages are added to the Companion's display, accessible without a phone or app.

    \n

    Button controls

    \n
      \n
    • Single click / Double click — navigate between pages (next / previous)
      • \n
    • Long press on FIRST page — reopen unread message preview (up to 32 messages buffered)
      • \n
    • Long press on Quick Send or Settings — enter the page; active item highlights
        \n
      • Single click = next item · Double click = exit · Long press = confirm
        • \n
      \n
      • \n
    \n

    Quick Send

    \n

    Send a short status message directly over LoRa to the public channel — no typing, no phone needed. Useful when your phone is dead or unavailable.

    \n

    GPS coordinates are automatically appended if available (e.g. I'm OK @10.7769,106.7009). If GPS has no current fix, last known coordinates are used with a ? prefix so you know before sending.

    \n

    10 built-in presets:

    \n
      \n
    • I'm OK
      • \n
    • On my way
      • \n
    • I need help
      • \n
    • Everyone OK here
      • \n
    • Wait for me
      • \n
    • Heading home
      • \n
    • Running late
      • \n
    • Lost contact, call me
      • \n
    • Battery low, signing off
      • \n
    • All clear
      • \n
    \n

    Customize via TerminalCLI — changes are saved to flash and persist after reboot:

    \n
    get quick                        list all current presets\nset quick.0 Arrived at camp      set preset at index 0\nset quick.reset                  restore all 10 built-in defaults\n
    \n

    Settings

    \n

    A scrollable list of device settings, controlled directly from the button:

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    ItemAction
    BLEToggle Bluetooth on/off (shows connection state)
    RepeatToggle repeat mode on/off
    RxGainCycle RxGain mode: OFF → ON → AUTO (AUTO: V4.2 only)
    BuzzerToggle buzzer on/muted (boards with buzzer only)
    Send AdvertBroadcast your presence to nearby nodes
    Start OTAStart OTA update mode — connect to MeshCore-OTA WiFi and go to 192.168.4.1/update
    ShutdownPower off the device
    \n
    • \n

  • Heltec V4.3 support (KCT8103L FEM).\nFirmware automatically detects V4.2 / V4.3 at boot — no configuration required. V4.3 replaces the GC1109 FEM with KCT8103L, which supports explicit LNA/bypass RX mode selection via radio.rxgain.

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    ModeDescription
    on (default)FEM LNA active — best sensitivity
    offFEM bypass — SX1262 boosted gain compensates, better in high-interference environments near strong transmitters
    \n
    \n

    V4.3 does not support auto mode — use on or off.

    \n
    \n

    TerminalCLI (Companion app), Command Line (Repeater / Room Server):

    \n
    set radio.rxgain on\nset radio.rxgain off\nget radio.rxgain\n
    \n

    Setting is saved and restored after reboot.

    \n
    • \n

  • Unified firmware for \"No Display\" hardware variants.

    \n

    A single firmware binary now runs on both OLED and no-display hardware — no separate build required. The display is detected automatically at boot via I2C probe.

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    HardwareDetected as
    Heltec V4.2 with OLEDHeltec V4.2 OLED
    Heltec V4.2 without OLEDHeltec V4.2 No Display
    Heltec V4.3 with OLEDHeltec V4.3 OLED
    Heltec V4.3 without OLEDHeltec V4.3 No Display
    \n

    The device name shown in the MeshCore app reflects the actual hardware detected. On no-display hardware, the user button has no effect (previously it could trigger unintended I2C writes).

    \n
    • \n
\n" }, { "version": "Heltec-V3-WSL3-low-power-v1.14_0404", "name": "Heltec V3 & WSL3 low power - v1.14_0404", "datetime": "2026-04-04T10:47:33Z", "url": "https://github.com/dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4/releases/tag/Heltec-V3-WSL3-low-power-v1.14_0404", "prerelease": false, "notes": "### v1.14_0404\r\n\r\n- **Quick Send and Settings — control your Companion without a phone.**\r\n\r\n Two new pages are added to the Companion's display, accessible without a phone or app.\r\n\r\n #### Button controls\r\n\r\n - **Single click / Double click** — navigate between pages (next / previous)\r\n - **Long press on FIRST page** — reopen unread message preview (up to 32 messages buffered)\r\n - **Long press** on Quick Send or Settings — enter the page; active item highlights\r\n - Single click = next item · Double click = exit · Long press = confirm\r\n\r\n #### Quick Send\r\n\r\n Send a short status message directly over LoRa to the public channel — no typing, no phone needed. Useful when your phone is dead or unavailable.\r\n\r\n GPS coordinates are automatically appended if available (e.g. `I'm OK @10.7769,106.7009`). If GPS has no current fix, last known coordinates are used with a `?` prefix so you know before sending.\r\n\r\n **10 built-in presets:**\r\n - I'm OK\r\n - On my way\r\n - I need help\r\n - Everyone OK here\r\n - Wait for me\r\n - Heading home\r\n - Running late\r\n - Lost contact, call me\r\n - Battery low, signing off\r\n - All clear\r\n\r\n **Customize via TerminalCLI** — changes are saved to flash and persist after reboot:\r\n ```\r\n get quick list all current presets\r\n set quick.0 Arrived at camp set preset at index 0\r\n set quick.reset restore all 10 built-in defaults\r\n ```\r\n\r\n #### Settings\r\n\r\n A scrollable list of device settings, controlled directly from the button:\r\n\r\n | Item | Action |\r\n |---|---|\r\n | BLE | Toggle Bluetooth on/off (shows connection state) |\r\n | Repeat | Toggle repeat mode on/off |\r\n | RxGain | Cycle RxGain mode: OFF → ON → AUTO *(AUTO: V4.2 only)* |\r\n | Buzzer | Toggle buzzer on/muted *(boards with buzzer only)* |\r\n | Send Advert | Broadcast your presence to nearby nodes |\r\n | Start OTA | Start OTA update mode — connect to `MeshCore-OTA` WiFi and go to `192.168.4.1/update` |\r\n | Shutdown | Power off the device |\r\n\r\n- **Unified firmware for \"No Display\" hardware variants.**\r\n\r\n A single firmware binary now runs on both OLED and no-display hardware — no separate build required. The display is detected automatically at boot via I2C probe.\r\n\r\n | Hardware | Detected as |\r\n |---|---|\r\n | Heltec V3 with OLED | Heltec V3 |\r\n | Heltec WSL3 (no OLED) | Heltec WSL3 |\r\n\r\n The device name shown in the MeshCore app reflects the actual hardware detected. On no-display hardware, the user button has no effect (previously it could trigger unintended I2C writes).", "notesHtml": "

v1.14_0404

\n
    \n

  • Quick Send and Settings — control your Companion without a phone.

    \n

    Two new pages are added to the Companion's display, accessible without a phone or app.

    \n

    Button controls

    \n
      \n
    • Single click / Double click — navigate between pages (next / previous)
      • \n
    • Long press on FIRST page — reopen unread message preview (up to 32 messages buffered)
      • \n
    • Long press on Quick Send or Settings — enter the page; active item highlights
        \n
      • Single click = next item · Double click = exit · Long press = confirm
        • \n
      \n
      • \n
    \n

    Quick Send

    \n

    Send a short status message directly over LoRa to the public channel — no typing, no phone needed. Useful when your phone is dead or unavailable.

    \n

    GPS coordinates are automatically appended if available (e.g. I'm OK @10.7769,106.7009). If GPS has no current fix, last known coordinates are used with a ? prefix so you know before sending.

    \n

    10 built-in presets:

    \n
      \n
    • I'm OK
      • \n
    • On my way
      • \n
    • I need help
      • \n
    • Everyone OK here
      • \n
    • Wait for me
      • \n
    • Heading home
      • \n
    • Running late
      • \n
    • Lost contact, call me
      • \n
    • Battery low, signing off
      • \n
    • All clear
      • \n
    \n

    Customize via TerminalCLI — changes are saved to flash and persist after reboot:

    \n
    get quick                        list all current presets\nset quick.0 Arrived at camp      set preset at index 0\nset quick.reset                  restore all 10 built-in defaults\n
    \n

    Settings

    \n

    A scrollable list of device settings, controlled directly from the button:

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    ItemAction
    BLEToggle Bluetooth on/off (shows connection state)
    RepeatToggle repeat mode on/off
    RxGainCycle RxGain mode: OFF → ON → AUTO (AUTO: V4.2 only)
    BuzzerToggle buzzer on/muted (boards with buzzer only)
    Send AdvertBroadcast your presence to nearby nodes
    Start OTAStart OTA update mode — connect to MeshCore-OTA WiFi and go to 192.168.4.1/update
    ShutdownPower off the device
    \n
    • \n

  • Unified firmware for \"No Display\" hardware variants.

    \n

    A single firmware binary now runs on both OLED and no-display hardware — no separate build required. The display is detected automatically at boot via I2C probe.

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    HardwareDetected as
    Heltec V3 with OLEDHeltec V3
    Heltec WSL3 (no OLED)Heltec WSL3
    \n

    The device name shown in the MeshCore app reflects the actual hardware detected. On no-display hardware, the user button has no effect (previously it could trigger unintended I2C writes).

    \n
    • \n
\n" } ], "changelogSource": "github", "changelogUpdatedAt": "2026-06-21T09:55:33.826Z" }, { "id": "meshcore-solo", "name": "MeshCore Solo", "type": "fork", "maintainer": "MarekZegare4", "maintainers": [ { "name": "MarekZegare4", "url": "https://github.com/MarekZegare4" } ], "maintainerUrl": "https://github.com/MarekZegare4", "repository": "https://github.com/MarekZegare4/MeshCore-Solo", "website": "https://marekzegare4.github.io/Solo-tools/", "license": "MIT", "description": "A fork of the official MeshCore companion radio firmware with extended features and UI enhancements. Adds GPS navigation (waypoints, compass, trail recording with GPX export), battery power-saving (hardware RX duty-cycle + adaptive power control), favourite contacts dial, extended language support with native Unicode rendering, message delivery status, screen lock, auto-reply bot, repeater mode with diagnostics, and more — all optimized for joystick-only navigation on small displays.\n", "status": "active", "lifecycle": "active", "maturity": "stable", "distribution": "community", "lineage": { "kind": "fork", "upstreamFirmwareId": "meshcore-official", "upstreamRepository": "https://github.com/meshcore-dev/MeshCore" }, "runtime": { "framework": "arduino", "language": "cpp" }, "roles": [ "companion", "repeater", "standalone-ui" ], "features": [ "Extended Unicode support with Lemon font and native input", "GPS navigation suite (waypoints, compass, backtrack, trail recording)", "GPX export via USB serial", "Screenshot capture over USB", "Favourites dial for pinned contacts", "Message delivery status indicators", "DM auto-resend and incoming deduplication", "Screen lock with time and sensor display", "Auto-reply bot with command responses", "Auto-advert for location sharing", "Battery power saving (RX duty-cycle + APC)", "Companion repeater mode with diagnostics", "Ping functionality in Nearby Nodes", "SOS broadcast with configurable target", "Quiet hours for sound suppression", "Mark-all-read at type level", "Lock-screen unread count", "Channel scanner home page", "Contact distance sorting", "Signal stats screen", "Display test pattern", "Power profile presets", "Solo Tools web app for screenshot capture and GPX export (https://marekzegare4.github.io/Solo-tools/)" ], "capabilities": { "protocol": { "meshcoreCompatible": true, "rawPacketSend": true, "rawPacketObserve": true }, "transports": { "ble": true, "usbSerial": true, "nativeTcp": false, "wifiAp": false }, "operations": { "webFlasher": false, "ota": false, "bleDfu": false, "configurationBackup": true }, "networking": { "repeater": true, "roomServer": false, "observer": false, "mqtt": false, "kissModem": false }, "hardware": { "gps": true, "display": true, "sensors": true, "lowPowerRx": true } }, "changelog": { "source": "github", "repo": "MarekZegare4/MeshCore-Solo" }, "devices": [ { "id": "wio-tracker-l1", "status": "supported", "target": "wio-tracker-l1", "platformio_board": "seeed-wio-tracker-l1", "notes": "OLED variant (SSD1306/SH1106 128x64)" }, { "id": "wio-tracker-l1-pro", "status": "supported", "target": "wio-tracker-l1", "platformio_board": "seeed-wio-tracker-l1", "notes": "OLED variant — same firmware target as wio-tracker-l1" }, { "id": "wio-tracker-l1-eink", "status": "supported", "target": "wio-tracker-l1-eink", "platformio_board": "seeed-wio-tracker-l1", "notes": "E-ink variant (GxEPD2 250x122)" }, { "id": "gatiot-gat562-30s", "status": "supported", "target": "gat562_30s_mesh_kit", "platformio_board": "rak4631", "notes": "GAT562 30S Mesh Kit" } ], "latest_version": "1.19", "released": "2026-06-16", "releases": [ { "version": "v1.19", "name": "Solo v1.19", "datetime": "2026-06-16T08:11:43Z", "url": "https://github.com/MarekZegare4/MeshCore-Solo/releases/tag/v1.19", "prerelease": false, "notes": "## MeshCore Solo Companion Firmware v1.19\r\n\r\n### What's new\r\n\r\n- **Message delivery status** — outgoing messages now show an end-to-end delivery marker, auto-scaled to the font (legible on landscape e-ink), in both the history list and the fullscreen view:\r\n - **Direct messages** (and room servers): pending → delivered (✓) → failed (✗), driven by the real end-to-end ACK. While pending, a row of dots shows one per send so auto-resend progress is visible.\r\n - **Auto-resend** — a pending DM whose ACK times out is re-sent automatically (reusing the original timestamp) until resends run out. Configurable count under Settings › Messages › Resend (0–5, default 2). Runs in the background, independent of which screen is open; incoming duplicates from retries are dropped.\r\n - **Channels** — ✓ appears only once a repeater echo confirms the message was relayed into the mesh. No echo is normal (flood has no recipient ACK), so no pending/fail is shown.\r\n- **Auto-reply bot overhaul** — the trigger/reply bot grows into a small auto-responder:\r\n - **Query commands** — a DM or monitored-channel message is scanned for `!` tokens (`!ping !batt !loc !time !temp !hops !status !help`) and answered in one combined reply.\r\n - **Away / reply-to-all** — a lone `*` trigger replies to every message.\r\n - **Separate DM and channel triggers**, each with its own reply text.\r\n - **Quiet hours** — silence push replies during a chosen window (wraps midnight).\r\n - **Throttling & anti-loop** — per-contact DM throttle so one sender can't starve others; channel echo guard so the bot never answers itself; reply counter shown in the bot screen header.\r\n- **Keyboard overhaul** — one shared keyboard across all screens (reclaims duplicate RAM), icon keys (⇧ caps, ⎵ space, ⌫ delete, ✓ OK), and a second **symbols page** toggled with `#@`/`abc`.\r\n- **UI refresh**\r\n - Proportional **scrollbar** with up/down triangle caps replaces the old `^`/`v` arrows, scaling with the font (1× OLED, 2× landscape e-ink); used by every scrollable list and the fullscreen message view. The redundant `>` selection marker is gone and rows shifted left to reclaim space.\r\n - Status-bar single-letter indicators (M/B/A/G) replaced with scalable **mini-icons** (mute, bluetooth, advert, trail).\r\n- **Nearby Nodes reorganized** — one list over two sources (stored contacts + live discover scan) with a unified detail/action menu. Type filter and sort are independent axes and persist across re-entry; the active filter is shown in the title and in empty-list messages.\r\n- **Tools › Trail reorganized** — a short two-level action menu (Hold Enter) replaces the flat ~12-item list; view-aware settings; a fitted **square map grid**; and the waypoint manager split out into its own component. No change to trail recording itself.\r\n- **OTA updates** — each solo release now ships a DFU `.zip` (`solo---ota.zip`) for over-the-air / BLE-DFU updates, alongside the `.uf2` for USB flashing.\r\n\r\n### Fixes\r\n\r\n- **GPS battery drain on shutdown** — GPS is powered off before `SYSTEMOFF`, and uses the correct active-level (`!PIN_GPS_EN_ACTIVE`) instead of a hardcoded level.\r\n- **Buzzer octave 8** — the RTTTL parser now fully accepts octave 8 instead of clamping it away (which could leak a digit into the next note's duration).\r\n- **Trail file robustness** — `Waypoint`/trail readers check every header read, so a truncated file is rejected instead of using a garbage count.\r\n\r\n### Under the hood\r\n\r\n- OTA DFU zip is named and attached to releases by the `_solo_dual` build workflow; the per-build Actions artifact already carried it.\r\n- Large UI consolidation: shared `drawList` / header / key-decode helpers, deduplicated status-bar indicators, reusable scalable mini-icon facility (`icons.h`), and an audit-pass cleanup premoving dead code and redundant scroll-clamp logic.", "notesHtml": "

MeshCore Solo Companion Firmware v1.19

\n

What's new

\n
    \n
  • Message delivery status — outgoing messages now show an end-to-end delivery marker, auto-scaled to the font (legible on landscape e-ink), in both the history list and the fullscreen view:
      \n
    • Direct messages (and room servers): pending → delivered (✓) → failed (✗), driven by the real end-to-end ACK. While pending, a row of dots shows one per send so auto-resend progress is visible.
      • \n
    • Auto-resend — a pending DM whose ACK times out is re-sent automatically (reusing the original timestamp) until resends run out. Configurable count under Settings › Messages › Resend (0–5, default 2). Runs in the background, independent of which screen is open; incoming duplicates from retries are dropped.
      • \n
    • Channels — ✓ appears only once a repeater echo confirms the message was relayed into the mesh. No echo is normal (flood has no recipient ACK), so no pending/fail is shown.
      • \n
    \n
    • \n
  • Auto-reply bot overhaul — the trigger/reply bot grows into a small auto-responder:
      \n
    • Query commands — a DM or monitored-channel message is scanned for ! tokens (!ping !batt !loc !time !temp !hops !status !help) and answered in one combined reply.
      • \n
    • Away / reply-to-all — a lone * trigger replies to every message.
      • \n
    • Separate DM and channel triggers, each with its own reply text.
      • \n
    • Quiet hours — silence push replies during a chosen window (wraps midnight).
      • \n
    • Throttling & anti-loop — per-contact DM throttle so one sender can't starve others; channel echo guard so the bot never answers itself; reply counter shown in the bot screen header.
      • \n
    \n
    • \n
  • Keyboard overhaul — one shared keyboard across all screens (reclaims duplicate RAM), icon keys (⇧ caps, ⎵ space, ⌫ delete, ✓ OK), and a second symbols page toggled with #@/abc.
    • \n
  • UI refresh
      \n
    • Proportional scrollbar with up/down triangle caps replaces the old ^/v arrows, scaling with the font (1× OLED, 2× landscape e-ink); used by every scrollable list and the fullscreen message view. The redundant > selection marker is gone and rows shifted left to reclaim space.
      • \n
    • Status-bar single-letter indicators (M/B/A/G) replaced with scalable mini-icons (mute, bluetooth, advert, trail).
      • \n
    \n
    • \n
  • Nearby Nodes reorganized — one list over two sources (stored contacts + live discover scan) with a unified detail/action menu. Type filter and sort are independent axes and persist across re-entry; the active filter is shown in the title and in empty-list messages.
    • \n
  • Tools › Trail reorganized — a short two-level action menu (Hold Enter) replaces the flat ~12-item list; view-aware settings; a fitted square map grid; and the waypoint manager split out into its own component. No change to trail recording itself.
    • \n
  • OTA updates — each solo release now ships a DFU .zip (solo-<ver>-<device>-ota.zip) for over-the-air / BLE-DFU updates, alongside the .uf2 for USB flashing.
    • \n
\n

Fixes

\n
    \n
  • GPS battery drain on shutdown — GPS is powered off before SYSTEMOFF, and uses the correct active-level (!PIN_GPS_EN_ACTIVE) instead of a hardcoded level.
    • \n
  • Buzzer octave 8 — the RTTTL parser now fully accepts octave 8 instead of clamping it away (which could leak a digit into the next note's duration).
    • \n
  • Trail file robustness — Waypoint/trail readers check every header read, so a truncated file is rejected instead of using a garbage count.
    • \n
\n

Under the hood

\n
    \n
  • OTA DFU zip is named and attached to releases by the _solo_dual build workflow; the per-build Actions artifact already carried it.
    • \n
  • Large UI consolidation: shared drawList / header / key-decode helpers, deduplicated status-bar indicators, reusable scalable mini-icon facility (icons.h), and an audit-pass cleanup premoving dead code and redundant scroll-clamp logic.
    • \n
\n" }, { "version": "v1.18", "name": "Solo v1.18", "datetime": "2026-06-14T08:22:51Z", "url": "https://github.com/MarekZegare4/MeshCore-Solo/releases/tag/v1.18", "prerelease": false, "notes": "## MeshCore Solo Companion Firmware v1.18\r\n\r\n### New device support\r\n\r\n- **GAT562 30S Mesh Kit** — the firmware now supports the GAT562 30S alongside the Wio Tracker L1 family. Pre-built `.uf2` files for all supported devices are published with each release — see the [Supported Devices](https://github.com/MarekZegare4/MeshCore-Solo#supported-devices) table.\r\n\r\n### What's new\r\n\r\n- **GAT562 30S Mesh Kit support** — see above.\r\n- **Battery saving (radio)** — two new independent toggles under Settings › Radio:\r\n - **Pwr save** — hardware duty-cycle receive (SX126x `SetRxDutyCycle`): the radio cycles RX↔sleep autonomously and wakes on a preamble, cutting average RX current with only a small increase in receive latency\r\n - **Auto pwr** — Adaptive Power Control: trims TX power on strong links (based on ACK SNR) and ramps back up on weak or lost links; the home screen shows the live transmit power\r\n- **BLE disconnect icon fix** — the BLE status icon now updates immediately when the connection drops (e.g. out of range, supervision timeout). Previously it could stay active until the next UI polling cycle.\r\n- **Bot trigger preserves case** — the auto-reply trigger phrase is now stored exactly as typed. Matching remains case-insensitive, so `Ping`, `ping` and `PING` all trigger the bot, but the trigger no longer gets silently lowercased when saved.\r\n- **Screenshot support in all solo builds** — `ENABLE_SCREENSHOT` is now enabled in every solo firmware build. No need to use a separate `_dev` environment. Use the [Solo Tools](https://marekzegare4.github.io/Solo-tools/) web app to capture screenshots directly from the browser.\r\n\r\n\r\n### Under the hood\r\n\r\n- CI matrix for solo firmware builds is now fully dynamic — new devices are picked up automatically from `platformio.ini` based on the `_solo_dual` env suffix, no workflow changes required.\r\n- `AbstractUITask::onBLEDisconnected()` virtual hook added — called by `setHasConnection()` on transition to disconnected; `UITask` overrides it to set `_next_refresh = 0`.\r\n- `build.sh` gains `build-solo-firmwares` command, backed by `build_all_firmwares_by_suffix \"_solo_dual\"`.", "notesHtml": "

MeshCore Solo Companion Firmware v1.18

\n

New device support

\n
    \n
  • GAT562 30S Mesh Kit — the firmware now supports the GAT562 30S alongside the Wio Tracker L1 family. Pre-built .uf2 files for all supported devices are published with each release — see the Supported Devices table.
    • \n
\n

What's new

\n
    \n
  • GAT562 30S Mesh Kit support — see above.
    • \n
  • Battery saving (radio) — two new independent toggles under Settings › Radio:
      \n
    • Pwr save — hardware duty-cycle receive (SX126x SetRxDutyCycle): the radio cycles RX↔sleep autonomously and wakes on a preamble, cutting average RX current with only a small increase in receive latency
      • \n
    • Auto pwr — Adaptive Power Control: trims TX power on strong links (based on ACK SNR) and ramps back up on weak or lost links; the home screen shows the live transmit power
      • \n
    \n
    • \n
  • BLE disconnect icon fix — the BLE status icon now updates immediately when the connection drops (e.g. out of range, supervision timeout). Previously it could stay active until the next UI polling cycle.
    • \n
  • Bot trigger preserves case — the auto-reply trigger phrase is now stored exactly as typed. Matching remains case-insensitive, so Ping, ping and PING all trigger the bot, but the trigger no longer gets silently lowercased when saved.
    • \n
  • Screenshot support in all solo builds — ENABLE_SCREENSHOT is now enabled in every solo firmware build. No need to use a separate _dev environment. Use the Solo Tools web app to capture screenshots directly from the browser.
    • \n
\n

Under the hood

\n
    \n
  • CI matrix for solo firmware builds is now fully dynamic — new devices are picked up automatically from platformio.ini based on the _solo_dual env suffix, no workflow changes required.
    • \n
  • AbstractUITask::onBLEDisconnected() virtual hook added — called by setHasConnection() on transition to disconnected; UITask overrides it to set _next_refresh = 0.
    • \n
  • build.sh gains build-solo-firmwares command, backed by build_all_firmwares_by_suffix \"_solo_dual\".
    • \n
\n" }, { "version": "v1.17", "name": "Solo v1.17", "datetime": "2026-06-09T15:33:39Z", "url": "https://github.com/MarekZegare4/MeshCore-Solo/releases/tag/v1.17", "prerelease": false, "notes": "## Wio Tracker L1 — Solo Firmware v1.17\r\n\r\n### What's new\r\n\r\n- **Nearby Nodes — navigate & save waypoints from the list** — the context menu now exposes _Navigate_ and _Save waypoint_ directly from the Nearby list and detail view, so you no longer have to open the separate Tools → Waypoints screen. Long-press Options in the detail view also opens a _Ping_ submenu.\r\n- **Nearby Nodes — TIME sort filter** — a new `[TIME]` filter sorts contacts by last-seen time (most recent first) instead of distance, useful when GPS is unavailable.\r\n- **Battery indicator calibrated** — the 100 % ceiling of the LiPo discharge curve was corrected from 4200 mV to 4170 mV, matching what the board's charger actually delivers.\r\n- **Advert sound scope control** — a new _Sound → Advert_ setting lets you choose whether advert notifications play for all nodes or only direct (zero-hop) neighbours, cutting noise on busy meshes.\r\n- **Sound slot \"None\" option** — DM, channel and advert melody slots can now be set to _None_ to silence that notification category entirely without muting everything.\r\n- **Mark-as-read feedback** — marking messages read (per-contact or per-channel) now shows a brief _\"N marked read\"_ confirmation on screen.\r\n- **[Web tool] GPX Downloader** — a standalone web page for downloading saved GPX trails from the device over the browser's Web Serial API, no desktop app required.\r\n\r\n### Under the hood\r\n\r\n- `SoundNotifier` extracted from `UITask::notify()` — all buzzer/melody logic lives in one place, reducing future merge conflict surface with upstream.\r\n- `KeyboardWidget` is now a single shared instance across screens (saves ~1.5 KB heap).\r\n- `onDiscoveredAdvert` extracted as a separate virtual so upstream `onDiscoveredContact` keeps its original 4-parameter signature.", "notesHtml": "

Wio Tracker L1 — Solo Firmware v1.17

\n

What's new

\n
    \n
  • Nearby Nodes — navigate & save waypoints from the list — the context menu now exposes Navigate and Save waypoint directly from the Nearby list and detail view, so you no longer have to open the separate Tools → Waypoints screen. Long-press Options in the detail view also opens a Ping submenu.
    • \n
  • Nearby Nodes — TIME sort filter — a new [TIME] filter sorts contacts by last-seen time (most recent first) instead of distance, useful when GPS is unavailable.
    • \n
  • Battery indicator calibrated — the 100 % ceiling of the LiPo discharge curve was corrected from 4200 mV to 4170 mV, matching what the board's charger actually delivers.
    • \n
  • Advert sound scope control — a new Sound → Advert setting lets you choose whether advert notifications play for all nodes or only direct (zero-hop) neighbours, cutting noise on busy meshes.
    • \n
  • Sound slot \"None\" option — DM, channel and advert melody slots can now be set to None to silence that notification category entirely without muting everything.
    • \n
  • Mark-as-read feedback — marking messages read (per-contact or per-channel) now shows a brief \"N marked read\" confirmation on screen.
    • \n
  • [Web tool] GPX Downloader — a standalone web page for downloading saved GPX trails from the device over the browser's Web Serial API, no desktop app required.
    • \n
\n

Under the hood

\n
    \n
  • SoundNotifier extracted from UITask::notify() — all buzzer/melody logic lives in one place, reducing future merge conflict surface with upstream.
    • \n
  • KeyboardWidget is now a single shared instance across screens (saves ~1.5 KB heap).
    • \n
  • onDiscoveredAdvert extracted as a separate virtual so upstream onDiscoveredContact keeps its original 4-parameter signature.
    • \n
\n" }, { "version": "v1.16", "name": "Solo v1.16", "datetime": "2026-06-06T16:35:39Z", "url": "https://github.com/MarekZegare4/MeshCore-Solo/releases/tag/v1.16", "prerelease": false, "notes": "## Wio Tracker L1 — Solo Firmware v1.16\r\n\r\nRebases the Solo fork onto upstream MeshCore **v1.16.0** (254 commits)\r\n\r\n### What's new (from upstream)\r\n\r\n- **NRF52 power-saving** — the companion now puts the MCU to sleep whenever there's no pending work, instead of looping continuously between events.\r\n- **Better reception of longer messages at low spreading factors** — the LoRa preamble is now 32 (was 16) for SF below 9, which makes longer frames more reliable on weak links.\r\n- **More robust sensors** — the I²C sensor subsystem was rewritten to probe the bus before touching any device, so an absent or misbehaving sensor can no longer hang or crash the node.\r\n- **Charging-aware shutdown** — the device no longer auto-shuts-down on low battery while it's on external power, and shows a shutdown warning on OLED.\r\n- **New companion command** for sending raw packets, plus assorted CLI additions (`flood.max.advert`, `flood.max.unscoped`, region hierarchy) and bounds-checking fixes that the phone app and repeaters benefit from.\r\n- **Battery-voltage reading fix** carried in from upstream.", "notesHtml": "

Wio Tracker L1 — Solo Firmware v1.16

\n

Rebases the Solo fork onto upstream MeshCore v1.16.0 (254 commits)

\n

What's new (from upstream)

\n
    \n
  • NRF52 power-saving — the companion now puts the MCU to sleep whenever there's no pending work, instead of looping continuously between events.
    • \n
  • Better reception of longer messages at low spreading factors — the LoRa preamble is now 32 (was 16) for SF below 9, which makes longer frames more reliable on weak links.
    • \n
  • More robust sensors — the I²C sensor subsystem was rewritten to probe the bus before touching any device, so an absent or misbehaving sensor can no longer hang or crash the node.
    • \n
  • Charging-aware shutdown — the device no longer auto-shuts-down on low battery while it's on external power, and shows a shutdown warning on OLED.
    • \n
  • New companion command for sending raw packets, plus assorted CLI additions (flood.max.advert, flood.max.unscoped, region hierarchy) and bounds-checking fixes that the phone app and repeaters benefit from.
    • \n
  • Battery-voltage reading fix carried in from upstream.
    • \n
\n" }, { "version": "v1.15.1", "name": "Solo v1.15.1", "datetime": "2026-06-05T11:31:47Z", "url": "https://github.com/MarekZegare4/MeshCore-Solo/releases/tag/v1.15.1", "prerelease": false, "notes": "## Wio Tracker L1 — Solo Firmware v1.15.1\r\n\r\nHotfix for Bluetooth pairing and buzzer regressions in v1.15 (introduced by the Advert-sound change). No schema change — upgrade in place from v1.15.\r\n\r\n### Fixes\r\n\r\n- **Bluetooth pairing PIN is shown again** — on the published OLED + e-ink (dual BLE+USB) builds the pairing PIN was never drawn, so the phone asked for a code that wasn't displayed and pairing failed. The PIN now appears on the **Bluetooth** home page while BLE is on and not yet bonded.\r\n- **Auto buzzer mute works again** — in v1.15 \"Auto\" was effectively always muted on dual builds (the connection state was hardcoded true). It now mutes only when a companion app is actually connected — **BLE bonded or a host holding the USB serial port open** — and stays audible on charge-only / no host. (Plain serial monitors that assert DTR count as connected.)\r\n- **Bluetooth status indicator** — the top-bar BT dot again reflects a real BLE connection instead of showing connected permanently.\r\n- **New-message display wake** — the screen wakes for an incoming message again when no app is connected.\r\n\r\n### Background\r\n\r\nv1.15's advert-sound feature broadened the internal \"connected\" flag from BLE-bonded to *any* transport, but the dual interface always reports its send-fallback as connected — so everything keyed off \"connected\" (PIN prompt, Auto mute, BT indicator, message-wake) misbehaved. This release splits the two notions: BLE-specific UI uses the BLE bond state, while Auto mute / message-wake use a new \"app connected over BLE or USB\" check (USB detected via the CDC DTR line).", "notesHtml": "

Wio Tracker L1 — Solo Firmware v1.15.1

\n

Hotfix for Bluetooth pairing and buzzer regressions in v1.15 (introduced by the Advert-sound change). No schema change — upgrade in place from v1.15.

\n

Fixes

\n
    \n
  • Bluetooth pairing PIN is shown again — on the published OLED + e-ink (dual BLE+USB) builds the pairing PIN was never drawn, so the phone asked for a code that wasn't displayed and pairing failed. The PIN now appears on the Bluetooth home page while BLE is on and not yet bonded.
    • \n
  • Auto buzzer mute works again — in v1.15 \"Auto\" was effectively always muted on dual builds (the connection state was hardcoded true). It now mutes only when a companion app is actually connected — BLE bonded or a host holding the USB serial port open — and stays audible on charge-only / no host. (Plain serial monitors that assert DTR count as connected.)
    • \n
  • Bluetooth status indicator — the top-bar BT dot again reflects a real BLE connection instead of showing connected permanently.
    • \n
  • New-message display wake — the screen wakes for an incoming message again when no app is connected.
    • \n
\n

Background

\n

v1.15's advert-sound feature broadened the internal \"connected\" flag from BLE-bonded to any transport, but the dual interface always reports its send-fallback as connected — so everything keyed off \"connected\" (PIN prompt, Auto mute, BT indicator, message-wake) misbehaved. This release splits the two notions: BLE-specific UI uses the BLE bond state, while Auto mute / message-wake use a new \"app connected over BLE or USB\" check (USB detected via the CDC DTR line).

\n" }, { "version": "v1.15", "name": "Solo v1.15", "datetime": "2026-06-04T15:35:06Z", "url": "https://github.com/MarekZegare4/MeshCore-Solo/releases/tag/v1.15", "prerelease": false, "notes": "## Wio Tracker L1 — Solo Firmware v1.15\r\n\r\nAdds a full **GPS navigation suite** on top of Solo v1.14 — the L1 becomes a standalone off-grid navigator, no phone required.\r\n\r\n### Highlights\r\n\r\n- **Waypoints** — mark your current spot or type coordinates, give it a short label, then get live bearing + distance back to it. Ideal for car / camp / water / a meeting point.\r\n- **GPS compass** — *Tools › Compass*: a heads-up heading tape derived from GPS course-over-ground. No magnetometer needed.\r\n- **Navigate to anything** — a saved waypoint, the start of your trail (backtrack), a node from Nearby Nodes, or a location someone texts you.\r\n- **Share & save locations over the mesh** — send a waypoint in a message; on the other end, navigate to or save any shared location with one menu.\r\n- **Global Units setting** — one Metric / Imperial switch (Settings › System) drives every distance and speed in the UI.\r\n- **Advert sound** — an optional audible \"in range\" heartbeat: the device chirps when it receives an advert from another node — pair it with Auto-Advert to keep tabs on a buddy hands-free.\r\n\r\n### Changes\r\n\r\n**Navigation (new)**\r\n\r\n- **Waypoints** — *Tools › Trail › Hold Enter*: **Mark here** drops one at the current GPS fix; **Waypoints** opens the list, which carries a synthetic **Trail start** backtrack row, a usage counter (`WAYPOINTS 3/16`), and a **+ Add by coords** row to enter a point by lat/lon/label with no fix required (hemisphere chosen with LEFT/RIGHT since the keyboard has no minus key). Per-waypoint **Rename / Delete / Send**, plus **Clear waypoints**. Stored in their own `/waypoints` file (16 max) — independent of the trail and **not** cleared by Reset trail.\r\n- **Navigate-to-point view** — distance plus two *absolute* bearings, **To:** (target) and **Hdg:** (your course over ground), compared by eye. Reused by waypoints, trail backtrack, Nearby-node navigation and message-shared locations.\r\n- **GPS compass** — *Tools › Compass*: a scrolling N..E..S..W heading tape under a fixed travel-direction pointer, with a large degrees + cardinal readout. Works whether or not a trail is recording.\r\n- **Navigate to a node** — Nearby Nodes detail → **Hold Enter** now opens an Options menu (**Navigate** / **Ping**); Navigate opens the bearing/distance view targeting the node's last-known position.\r\n- **Trail map as a live view** — the Map draws your current position and all waypoints continuously, even with no trail recording. While a trail exists it frames the recorded route and clamps far-off waypoints to the nearest edge (a distant mark can't blow up the scale); with no trail it auto-fits to your waypoints and position. Markers show the first two label characters, placed edge-aware so labels stay on-map.\r\n- **Navigate / save a shared location** — any message carrying a `lat,lon` (what `{loc}` inserts) or a `[WAY]lat,lon label` share offers **Navigate** and **Save waypoint** from its **Hold Enter** menu — on the history row or in fullscreen, for DMs and channels. **Send** on a waypoint shares it to a contact or channel, pre-filling the message to confirm.\r\n- **Waypoints in GPX** — the GPX export now includes saved waypoints as `` elements (label → ``, plus `