{ "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 reference 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", "scope": "universal", "lifecycle": "active", "maturity": "stable", "distribution": "community", "lineage": { "kind": "fork", "upstreamFirmwareId": "meshcore", "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" } ], "popularity": { "githubStars": 56, "githubForks": 5, "githubWatchers": 3, "githubOpenIssues": 8, "githubContributors": 178, "releaseDownloads": 924, "latestReleaseDownloads": 59, "lastChecked": "2026-08-05" }, "verification": { "sourceAvailable": true, "releasesAvailable": true, "ciBuilds": true, "lastChecked": "2026-08-05" }, "source": { "path": "data/firmwares/meshcore-solo/firmware.yaml", "updatedAt": "2026-08-05T14:13:46Z" }, "latest_version": "1.24", "released": "2026-07-29", "releases": [ { "version": "v1.24", "name": "Solo v1.24", "datetime": "2026-07-29T20:58:38Z", "url": "https://github.com/MarekZegare4/MeshCore-Solo/releases/tag/v1.24", "prerelease": false, "notes": "## MeshCore Solo Companion Firmware v1.24\r\n\r\n### What's new\r\n\r\n- **Auto-Reply Bot is renamed to Remote Bot.** It's grown beyond auto-replies into remote device control (Actions, below), so the Tools screen entry and docs now say \"Remote Bot\" — same screen, same settings, nothing to reconfigure.\r\n- **Remote Bot gains Actions: `!buzz`, `!gps`, `!advert`.** A new **Actions** toggle (per target — Direct/Channel/Room, nested under each target's existing **Commands** toggle) enables three commands that change the device's own behaviour instead of just reporting on it: `!buzz [seconds]` sounds the buzzer as a find-me signal (default 5s, capped at 30s, sounds even if the buzzer is muted), `!gps on`/`!gps off` toggles GPS, and `!advert` sends an immediate advert (0 hop). Off by default; combines with the existing query commands in one message the same way (`!batt !gps on` → `4.10V | GPS: on`).\r\n- **`!gps fix [seconds]` — single-shot GPS location, no need to leave GPS running.** Turns GPS on (if it wasn't already), waits for a stabilised fix (HDOP ≤ 2.0 — falls back to ≥8 satellites on GPS hardware that doesn't report HDOP — then averages for 10s), sends the position, and restores GPS to whatever state it was in before — up to a 90s timeout by default (override with an optional argument, clamped to 15-300s, for a poor sky view where 90s isn't always enough), after which it reports a partial fix (if it got at least some samples) or failure. Replies in two parts: an immediate \"acquiring fix...\" ack, then the actual position as a follow-up message once ready. Only one fix request can be in flight at a time (a second one gets \"fix already pending\"); same Actions toggle as `!buzz`/`!gps`/`!advert`.\r\n- **Bot Trigger fields accept multiple phrases.** Pack several trigger words into one Trigger field, comma-separated (`hi,hello there,yo`) — matching any one of them fires the reply, same as before for a single phrase.\r\n- **Remote Bot Actions gain `!gpio1`..`!gpio4`** (Wio Tracker L1 only — 4 otherwise-unused pins). Each pin is independently set to Off/Input/Output (GPIO1/GPIO2 also offer Analog) from a new **Tools › GPIO** screen; `!gpio1 on`/`!gpio1 off` drives an Output pin remotely, a bare `!gpio1` reports the current mode and reading (including a millivolt value in Analog mode). Gated by the same per-target Actions toggle as `!buzz`/`!gps`/`!advert`.\r\n- **GAT562 30S solo builds now use the same OLED font as the Wio Tracker L1.** The misc-fixed 6x9 font (full Latin, Greek and Cyrillic) had only ever reached the SH1106 and e-ink drivers, so on this board every keyboard alphabet beyond ASCII, and every accented contact name, was still being transliterated (`Łódź` → `Lodz`) or drawn as a filled block. Solo builds only — the font costs ~14 KB of flash and the repeater/companion builds have no keyboard to type those alphabets on; they keep the built-in font and are byte-for-byte unchanged.\r\n\r\n _Work in progress territory_ \r\n- **Optional CardKB support (Wio Tracker L1, Grove I2C) — full keyboard-only navigation.** Plug an M5Stack CardKB into the Grove connector and it's auto-detected at boot — no setting to flip. Typing goes straight into the message/name field instead of navigating the on-screen keyboard grid, always as plain Latin text regardless of the Settings › Keyboard language/type — arrows and Esc work as expected everywhere else too (including inside the placeholder and accent popups). Enter acts like the physical centre button (advances the on-screen grid selection) rather than submitting, so **Fn+Enter** sends the message/confirms the field from anywhere, and **Fn+``** opens that letter's accent popup directly (no arrow-hunting needed — handy for Polish/Czech/etc. diacritics — and works no matter what language/keyboard type is configured, since CardKB always types Latin either way). **Tab** is the Hold-Enter equivalent everywhere, including message reply/navigate and the Bot/Admin/Repeater menus — same single shortcut whether or \n…", "notesHtml": "

MeshCore Solo Companion Firmware v1.24

\n

What's new

\n\n

Work in progress territory

\n\n" }, { "version": "v1.23.1", "name": "Solo v1.23.1", "datetime": "2026-07-24T19:41:29Z", "url": "https://github.com/MarekZegare4/MeshCore-Solo/releases/tag/v1.23.1", "prerelease": false, "notes": "## MeshCore Solo Companion Firmware v1.23.1\r\n\r\n### Fixes\r\n\r\n- **Tools › Admin login could get stuck on \"Logging in...\" forever** if the remote node never sent back a reply — most commonly after its admin/room password was changed, since the on-device UI auto-retries the old saved password with no timeout to fall back on. It now gives up after the same estimated-timeout window the rest of Admin's commands use, forgets the stale saved password, and returns you to the picker to try again with the new one.\r\n- **Changing a remote's admin password from Tools › Admin › System didn't update this device's own saved copy** — the very next login attempt to that node retried the password you'd just replaced, hitting the \"stuck on Logging in…\" case above. The confirmation the remote echoes back is now saved as the new on-device password to match.\r\n- **A slow-to-arrive Admin login reply, after you'd already given up on it (Cancel or the new timeout above), could get delivered to whatever screen you'd since moved to and silently overwrite your saved password for that node with unrelated data.** Giving up on a login now also stops tracking it mesh-side, so a late reply is simply dropped instead of misrouted.\r\n- **Opening Admin on a second, password-less node while an earlier room/repeater login elsewhere was still in flight could wrongly show you as logged in as admin on the new node** — a reply meant for the earlier login was accepted as this node's own since both merely looked like \"a login is pending,\" without checking it actually named this node. Now checked.", "notesHtml": "

MeshCore Solo Companion Firmware v1.23.1

\n

Fixes

\n\n" }, { "version": "v1.23", "name": "Solo v1.23", "datetime": "2026-07-17T20:17:33Z", "url": "https://github.com/MarekZegare4/MeshCore-Solo/releases/tag/v1.23", "prerelease": false, "notes": "## MeshCore Solo Companion Firmware v1.23\r\n\r\n### What's new\r\n\r\n- **Nodes is now the single node hub.** \"Nearby Nodes\" is renamed **Nodes** and gains on-device contact management — no phone app needed: **Hold Enter** on a row opens **Add contact** (for a scanned-but-unknown node), **Favourite/Unfavourite** (pins to the first free Favourites Dial slot, shown as a star in the list), and **Delete contact** (confirm first, defaults to Cancel). The filter strip (**LEFT/RIGHT**) is now a visible, wraparound tab carousel instead of a hidden mode. The old read-only **Recent adverts** home page is retired — its passively-heard nodes now simply show up in the Nodes list (All filter) — so there's one list instead of two.\r\n- **On-device channel management.** Messages › Channels gets a **\"+ Add channel\"** row and per-channel **Edit**/**Delete** — no phone app required. Adding a channel now starts with a **type picker**, matching the phone app: **Public** (re-adds the well-known default channel, no typing needed), **Hashtag** (type just a topic name, e.g. `test` — the channel name and secret are both derived from it, same convention as the app's `#topic` channels), or **Private** (manual Name + Secret, typing either a passphrase hashed to the channel secret, or the exact 32-hex-character key from a channel QR code).\r\n- **Tools › Admin — administer a remote repeater/room from the device.** Log into a node you have admin rights on (same self-healing saved-password handshake as room logins) and browse its settings in category tabs — **System** (name, owner info), **Radio** (Frequency/Bandwidth/Spreading factor/Coding rate/TX power), **Routing** (Repeat/Advert interval/Flood advert interval/Max hops), **Actions** (reboot, send advert, sync clock, …) — plus a free-text **Custom command…** escape hatch (with **{}**-key command-name completion) for anything not covered. Radio and Routing fields use a type-appropriate editor instead of raw text — a digit-cursor for Frequency (the same widget Settings' own Radio screen uses locally), discrete-set stepping for Bandwidth/Spreading factor/Coding rate, plain number steppers for the rest, and an ON/OFF toggle for Repeat — adjusting a value costs no mesh traffic until you actually confirm it with **Enter** (**Cancel** sends nothing). Reachable either from **Tools › Admin** (opens the same Nodes list to pick a target) or directly via a repeater/room's own **Hold Enter › Admin** action.\r\n- **Auto-Reply Bot gains a third target: room servers**, alongside DM and Channel, with its own trigger/reply/commands — the screen is redesigned as a circular tab carousel (**Direct/Channel/Room/Other**, **LEFT/RIGHT** to switch, **UP/DOWN** within a tab) instead of one long list. Each target's **Enable** and **Commands** toggle is now fully independent (they used to secretly share the DM tab's setting for Channel/Room too). New `{name}`/`{hops}` reply placeholders, a DM allow-list (all chat contacts or favourites only), and a dedicated stepper for Quiet Hours.\r\n- **Keyboard: accent popup, selectable main script, better editing.** Holding **Enter** on a Latin letter with accented variants (`a c d e i l n o r s t u y z`) now opens a one-row popup of that letter's accents — e.g. holding `a` offers `á à â ã ä å ą` — covering every European Latin-diacritic letter (Polish, Czech, Slovak, German, French, Spanish, Portuguese, Nordic, …) from one popup instead of a separate page per language. **Settings › Keyboard** splits **Alphabet** into **Main** and **Additional**: Main picks which script (Latin/Cyrillic/Greek) the keyboard opens on by default, Additional picks the second one reached via the **#@/abc** cycle key — so a Cyrillic or Greek typist can make their own script the default instead of always landing on Latin first. Shift is now **one-shot** by default (capitalises just the next letter; **Hold Enter** on Shift toggles the old sticky caps-lock back on), **Hold Enter** on Backspace clears the whole field, and **UP** from th\n…", "notesHtml": "

MeshCore Solo Companion Firmware v1.23

\n

What's new

\n\n" }, { "version": "v1.22", "name": "Solo v1.22", "datetime": "2026-07-06T19:29:14Z", "url": "https://github.com/MarekZegare4/MeshCore-Solo/releases/tag/v1.22", "prerelease": false, "notes": "## MeshCore Solo Companion Firmware v1.22\r\n\r\n### What's new\r\n\r\n- **T9 on-screen keyboard** — a new keyboard option under **Settings › Keyboard**. Alongside the existing alphabetical **ABC** grid, pick **T9** for phone-keypad-style entry: each key is labelled with its digit and a letter group (e.g. `2abc`), and repeated **Enter** presses cycle through the letters and then the digit. (The alphabetical grid was previously mislabelled *QWERTY* in Settings — it's always been a-b-c order and is now correctly named **ABC**.)\r\n- **Auto-save GPS trail on shutdown** — a new **Tools › Trail › Settings › Auto-save** toggle (default off). With it on, the live trail is written to flash automatically at power-off, so a **low-battery auto-shutdown** no longer loses the whole route. It only writes when the trail actually has points, so an empty trail can't overwrite a previously saved one. Saves to the same `/trail` file as the manual **Trail › Save**.\r\n- **Clock Tools from the Tools menu** — the Alarm / Timer / Stopwatch screen (reachable by pressing **Enter** on the Clock home page) now also has its own entry under **Tools › System**, so it's discoverable without first finding it on the clock face.\r\n- **Map & Shutdown pages are reorderable** — the **Map** home page shipped with no entry under **Settings › Home Pages**, so it was always shown and couldn't be moved. It's now a first-class page there: **toggle its visibility** and **reorder it** like any other (visible by default; existing users keep it on). Reordering also now covers the **Shutdown** page, which was previously pinned to the end of the carousel.\r\n\r\n### Fixes\r\n\r\n- **Battery reads high and jittery on Wio Tracker L1** — a power-saving change had switched the battery-voltage divider on for only ~10 ms before each reading, too short for the high-impedance divider node to settle, so a full LiPo could report 4.6–5.0 V. The divider is now held on continuously again (a negligible ~2 µA on the 2×1 MΩ divider), giving stable, accurate readings. The CPU-sleep and LED energy savings from the same optimisation pass are untouched.\r\n- **Home page visibility no longer resets on update** — the prefs schema-migration that turned the **Favourites** page on ran on *every* firmware update (any schema-version bump), so a page you'd deliberately hidden kept coming back after each release. It's now gated to the single upgrade that introduced Favourites, so your hidden pages stay hidden.\r\n- a **locked device didn't show the alarm** — it woke the display, then immediately re-blanked, so a ringing alarm played to a dark screen. The lock screen now draws the alert and holds the wake for the whole ring.\r\n- **background-mode status icons vanished when Bluetooth was off** — the auto-advert / live-share / trail / repeater indicators were nested inside the \"BT on\" check and are now always shown while their mode is active.\r\n- a **long alert message** (\"GPS on, tracking started\") spilled past its box on a narrow screen — it now wraps to up to three lines and the box grows to fit.\r\n- a **contact name pushed from the phone app** wasn't guaranteed to be NUL-terminated.\r\n- the **timer / alarm could mis-fire** for a deadline landing past the ~49-day `millis()` rollover.\r\n- toggling a **channel's favourite from its context menu** could retarget the menu onto a different channel once the list re-sorted.\r\n- **A repeater could appear twice** on the discovery scan and in the app — a discover response often arrives more than once (the direct copy plus a re-flooded copy carry different packet hashes, so the mesh's duplicate filter passes both), and each copy was listed. Duplicate copies of the same response are now dropped for a few seconds after the first.\r\n- **Favourites self-heal** — a pinned favourite whose contact no longer exists (e.g. after clearing contacts) now reverts to an empty **+** tile instead of showing **(gone)**, and the stale pin is cleared from prefs.\r\n- **Radio preset names no longer seed `{loc}`/`{time}\n…", "notesHtml": "

MeshCore Solo Companion Firmware v1.22

\n

What's new

\n\n

Fixes

\n\n" }, { "version": "v1.21", "name": "Solo v1.21", "datetime": "2026-06-30T20:48:57Z", "url": "https://github.com/MarekZegare4/MeshCore-Solo/releases/tag/v1.21", "prerelease": false, "notes": "## MeshCore Solo Companion Firmware v1.21\r\n\r\n### What's new\r\n\r\n- **Live Location Sharing** — broadcast your position over the mesh as `[LOC]` messages, **movement-gated**, to a channel or a single contact. Others who share theirs show up as pins on the map with live **distance/bearing in Nearby Nodes**, and a **status-bar indicator** appears while your own share is active. `[LOC]` is parsed in DMs, channel messages **and room messages**; DM shares name the sender.\r\n- **Locator** (geofence) — arm a geofence around a **target** — a saved waypoint *or* a person (their live `[LOC]` or last-known position) — and get an alert when you **arrive/leave** or they get **near/far**, with an optional **homing beeper** that ticks faster the closer you get (and overrides a muted buzzer). Arm it from **Tools › Locator** or straight from **Nearby Nodes** / **Waypoints**; pick the target from a list (favourites first, then any contact), and clear it via a **\"None\"** entry. The active target is drawn as a **flag** on the map.\r\n- **One active target across Locator / Navigate / Map** — a single **\"Set as target\"** action everywhere, backed by a shared resolver that prefers a live `[LOC]` share over the last-advertised GPS, so the three features always agree on where you're headed.\r\n- **Follow live contacts** — **Navigate** to a contact who is live-sharing and the view **follows them as they move**, adding an **ETA** line. **Quick-share** your own position straight from the Map.\r\n- **Map & status-bar upgrades** — the home mini-map gains a **north marker** and a **scale tick**; the status line shows the tracked-node count and, with a fix, an **arrow + distance to the nearest tracked contact** (e.g. `Track:3 →120m`); a **GPS fix icon** sits in the top status bar (boxed once a fix is valid, plain while searching), shown only on GPS boards while **GPS** is enabled in Settings.\r\n- **Trail auto-pause** — recording **freezes on stops** (banking elapsed time and breaking the map line across the idle gap) and **resumes on movement** without ending the session; the home-screen blink keeps going while paused.\r\n- **Collapsible Tools** — tools are grouped into fold-in-place **Location / Comms / System** sections, the same model as Settings (Tools always opens folded to the section list), and the home carousel now uses **page-indicator icons** instead of dots.\r\n- **Clock tools — alarm, timer, stopwatch** — press **Enter** on the Clock page for three time utilities: a **one-shot wake alarm** (set hour/minute with the digit editor; a **bell** marks it on the clock face and the status bar while armed), a **countdown timer** (full **HH:MM:SS**, single-digit cursor), and a **stopwatch**. The alarm and timer **ring with a melody — overriding mute** — and are silenced by **any key**. They keep running with the display off or locked, and the alarm is scheduled as an **absolute instant** so it survives the clock re-syncs the mesh / app / GPS / CLI can trigger at any time (it can't wake the device from a full Shutdown, where the CPU is off).\r\n- **Waypoint coordinate editor** — add a waypoint by scroll-editing its latitude/longitude digit by digit.\r\n- **On-device room login with saved passwords** — log in to a room server straight from the device (no phone app): pick the room and the password prompt appears automatically (a blank password works for open rooms), or re-login any time via the room's **context-menu \"Login…\"**. The password is **remembered across reboots**, so a room you've used before logs back in without retyping; a failed login (e.g. the server's password changed) forgets the stale password so the next attempt prompts again. Room passwords entered via the **phone app** are saved on the device too, so it can post to that room standalone after a reboot. Saved passwords are written with the same atomic, crash-safe persistence as contacts and channels.\r\n\r\n### Fixes\r\n\r\n- **Critical — low-heap hang and contact loss on RAM-tight builds.** With `MAX_CONTACTS=350` an\n…", "notesHtml": "

MeshCore Solo Companion Firmware v1.21

\n

What's new

\n\n

Fixes

\n\n" }, { "version": "v1.21-rc2", "name": "Solo v1.21-rc2", "datetime": "2026-06-26T22:52:12Z", "url": "https://github.com/MarekZegare4/MeshCore-Solo/releases/tag/v1.21-rc2", "prerelease": true, "notes": "## MeshCore Solo Companion Firmware v1.21 Release candidate 2\r\n\r\n### What's new\r\n\r\n- **Live Location Sharing** — broadcast your position over the mesh as `[LOC]` messages, **movement-gated**, to a channel or a single contact. Others who share theirs show up as pins on the map with live **distance/bearing in Nearby Nodes**, and a **status-bar indicator** appears while your own share is active. `[LOC]` is parsed in DMs, channel messages **and room messages**; DM shares name the sender.\r\n- **Locator** (geofence) — arm a geofence around a **target** — a saved waypoint *or* a person (their live `[LOC]` or last-known position) — and get an alert when you **arrive/leave** or they get **near/far**, with an optional **homing beeper** that ticks faster the closer you get (and overrides a muted buzzer). Arm it from **Tools › Locator** or straight from **Nearby Nodes** / **Waypoints**; pick the target from a list (favourites first, then any contact), and clear it via a **\"None\"** entry. The active target is drawn as a **flag** on the map.\r\n- **One active target across Locator / Navigate / Map** — a single **\"Set as target\"** action everywhere, backed by a shared resolver that prefers a live `[LOC]` share over the last-advertised GPS, so the three features always agree on where you're headed.\r\n- **Follow live contacts** — **Navigate** to a contact who is live-sharing and the view **follows them as they move**, adding an **ETA** line. **Quick-share** your own position straight from the Map.\r\n- **Map & status-bar upgrades** — the home mini-map gains a **north marker** and a **scale tick**; the status line shows the tracked-node count and, with a fix, an **arrow + distance to the nearest tracked contact** (e.g. `Track:3 →120m`); a **GPS fix icon** sits in the top status bar (boxed once a fix is valid, plain while searching), shown only on GPS boards while **GPS** is enabled in Settings.\r\n- **Trail auto-pause** — recording **freezes on stops** (banking elapsed time and breaking the map line across the idle gap) and **resumes on movement** without ending the session; the home-screen blink keeps going while paused.\r\n- **Collapsible Tools** — tools are grouped into fold-in-place **Location / Comms / System** sections, the same model as Settings (Tools always opens folded to the section list), and the home carousel now uses **page-indicator icons** instead of dots.\r\n- **Waypoint coordinate editor** — add a waypoint by scroll-editing its latitude/longitude digit by digit.\r\n- **On-device room login with saved passwords** — log in to a room server straight from the device (no phone app): pick the room and the password prompt appears automatically (a blank password works for open rooms), or re-login any time via the room's **context-menu \"Login…\"**. The password is **remembered across reboots**, so a room you've used before logs back in without retyping; a failed login (e.g. the server's password changed) forgets the stale password so the next attempt prompts again. Saved passwords are written with the same atomic, crash-safe persistence as contacts and channels.\r\n\r\n\r\n### Fixes\r\n\r\n- **Critical — low-heap hang and contact loss on RAM-tight builds.** With `MAX_CONTACTS=350` and `OFFLINE_QUEUE_SIZE=256` the device ran with very little free heap; an allocation in the input/menu path could then fail and **hang the UI** (notably when entering Diagnostics), and a crash or reset mid-save could **wipe all contacts**. Fixed by two independent changes:\r\n - **Right-sized message-history rings** — the on-device scrollback rings were halved (96→48 channel, 64→32 DM), recovering **~14 KB of free heap** (measured 3 → 17 KB). History is RAM-only, so the only cost is shorter on-device scrollback.\r\n - **Atomic persistence** — contacts, channels and prefs are now written to a temp file and **atomically renamed** into place; an interrupted save (crash, reset, full flash) leaves the previous good file intact instead of truncating it.\r\n- **USB host stall** — `Serial.write\n…", "notesHtml": "

MeshCore Solo Companion Firmware v1.21 Release candidate 2

\n

What's new

\n\n

Fixes

\n\n" }, { "version": "v1.21-rc1", "name": "Solo v1.21-rc1", "datetime": "2026-06-25T17:17:12Z", "url": "https://github.com/MarekZegare4/MeshCore-Solo/releases/tag/v1.21-rc1", "prerelease": true, "notes": "## MeshCore Solo Companion Firmware v1.21 Release candidate 1\r\n\r\n### What's new\r\n\r\n- **Live Location Sharing** — broadcast your position over the mesh as `[LOC]` messages, **movement-gated**, to a channel or a single contact. Others who share theirs show up as pins on the map with live **distance/bearing in Nearby Nodes**, and a **status-bar indicator** appears while your own share is active. `[LOC]` is parsed in DMs, channel messages **and room messages**; DM shares name the sender.\r\n- **Locator** (geofence) — arm a geofence around a **target** — a saved waypoint *or* a person (their live `[LOC]` or last-known position) — and get an alert when you **arrive/leave** or they get **near/far**, with an optional **homing beeper** that ticks faster the closer you get (and overrides a muted buzzer). Arm it from **Tools › Locator** or straight from **Nearby Nodes** / **Waypoints**; pick the target from a list (favourites first, then any contact), and clear it via a **\"None\"** entry. The active target is drawn as a **flag** on the map.\r\n- **One active target across Locator / Navigate / Map** — a single **\"Set as target\"** action everywhere, backed by a shared resolver that prefers a live `[LOC]` share over the last-advertised GPS, so the three features always agree on where you're headed.\r\n- **Follow live contacts** — **Navigate** to a contact who is live-sharing and the view **follows them as they move**, adding an **ETA** line. **Quick-share** your own position straight from the Map.\r\n- **Map & status-bar upgrades** — the home mini-map gains a **north marker** and a **scale tick**; the status line shows the tracked-node count and, with a fix, an **arrow + distance to the nearest tracked contact** (e.g. `Track:3 →120m`); a **GPS fix icon** sits in the top status bar (boxed once a fix is valid, plain while searching), shown only on GPS boards while **GPS** is enabled in Settings.\r\n- **Trail auto-pause** — recording **freezes on stops** (banking elapsed time and breaking the map line across the idle gap) and **resumes on movement** without ending the session; the home-screen blink keeps going while paused.\r\n- **Collapsible Tools** — tools are grouped into fold-in-place **Location / Comms / System** sections, the same model as Settings (Tools always opens folded to the section list), and the home carousel now uses **page-indicator icons** instead of dots.\r\n- **Waypoint coordinate editor** — add a waypoint by scroll-editing its latitude/longitude digit by digit.\r\n\r\n### Fixes\r\n\r\n- **Critical — low-heap hang and contact loss on RAM-tight builds.** With `MAX_CONTACTS=350` and `OFFLINE_QUEUE_SIZE=256` the device ran with very little free heap; an allocation in the input/menu path could then fail and **hang the UI** (notably when entering Diagnostics), and a crash or reset mid-save could **wipe all contacts**. Fixed by two independent changes:\r\n - **Right-sized message-history rings** — the on-device scrollback rings were halved (96→48 channel, 64→32 DM), recovering **~14 KB of free heap** (measured 3 → 17 KB). History is RAM-only, so the only cost is shorter on-device scrollback.\r\n - **Atomic persistence** — contacts, channels and prefs are now written to a temp file and **atomically renamed** into place; an interrupted save (crash, reset, full flash) leaves the previous good file intact instead of truncating it.\r\n- **USB host stall** — `Serial.write()` is bounded so a stalled USB host can no longer hang the device indefinitely.\r\n\r\n### Under the hood\r\n\r\n- **Streaming trail simplification** — GPS points are simplified as they're recorded via a fixed-corridor (Reumann–Witkam) pass: straight runs collapse to their two endpoints while curves stay bounded to within the **Min dist** tolerance of the real track, so the 512-point buffer covers a far longer route than a flat point budget would suggest.\r\n- A UITask-decoupled active-target resolver (`resolvePersonPos` / `activeTargetPos`) replaces the duplicated target-resolution logic that lived sepa\n…", "notesHtml": "

MeshCore Solo Companion Firmware v1.21 Release candidate 1

\n

What's new

\n\n

Fixes

\n\n

Under the hood

\n\n" }, { "version": "v1.20", "name": "Solo v1.20", "datetime": "2026-06-22T08:51:38Z", "url": "https://github.com/MarekZegare4/MeshCore-Solo/releases/tag/v1.20", "prerelease": false, "notes": "## MeshCore Solo Companion Firmware v1.20\r\n\r\n### What's new\r\n\r\n- **Repeater mode** — a solo companion can now opt in to relaying mesh traffic, configured from a dedicated **Tools › Repeater** screen that consolidates the toggle, the forwarding filters, live forwarding stats, and a separate radio profile:\r\n - **Forwarding filters** (all flood-only, off by default) — *skip-advert* (don't re-flood the highest-volume advert traffic), *max-hops* (drop a flood once it has travelled too far), *yield* (extra retransmit-delay so a mobile node defers to better-sited fixed repeaters), and *min-SNR* (don't re-flood marginal fringe packets). Plus **overhear suppression**, which cancels a queued retransmit if a peer relays the same packet first.\r\n - **Dedicated radio profile** — an optional \"Custom\" Freq/SF/BW/CR used only while relaying, separate from the companion's own network and band-matched to the companion frequency by default. It's applied everywhere a radio change can happen (boot, on-device toggle, app-driven `CMD_SET_RADIO_PARAMS`, Settings edits) so the device never silently relays on the wrong params.\r\n - While relaying, **Adaptive Power Control is pinned to the ceiling** and **duty-cycle RX is forced off** — a repeater needs to hear and relay at consistent power.\r\n- **Radio settings overhaul** (Settings › Radio) — **16 community-suggested presets** plus manual Freq/SF/BW/CR tuning (digit-by-digit frequency editor), and **4 persisted user preset slots**. Presets and the manual editor are now **shared between Settings and the Repeater screen** — a preset saved from either place shows up in both, and you can **save the current profile as a named preset** or **delete one** from either screen.\r\n- **On-device Diagnostics** (Tools › Diagnostics) — a single scrollable screen showing packet counts by category (RX/TX), radio noise floor / RSSI / SNR, packet-pool free count and outbound queue length, actually-forwarded packet count, uptime, and live heap/stack headroom, with a reset-counters popup.\r\n\r\n### Fixes\r\n\r\n- **Channel storage hardening** — `saveChannels()` skips unused (all-zero) slots, so `/channels2` holds only configured channels instead of always writing ~2.7 KB; and `findChannelIdx()` rejects an all-zero secret so a corrupted/empty channel can't match an unused slot and misroute messages.\r\n- **e-ink UI scaling** — self-sizing popup menu scaled for landscape e-ink (no stray header gap, tighter row tiling); popup menu uses the shared proportional scroll indicator instead of raw `^`/`v` glyphs and stops the selection bar before the scrollbar gutter; compass tape ticks/pointer and trail-map markers scale for e-ink, with wrap-around map navigation.\r\n- **Joystick rotation** is now persisted on e-ink builds.\r\n- **Trail capacity guard** — a `static_assert` fails the build if `TrailStore::CAPACITY` ever outgrows the `uint16_t` save-header count, instead of silently truncating.\r\n\r\n### Under the hood\r\n\r\n- Packet pool bumped 16 → 32 so queued retransmits no longer starve incoming-packet allocation while relaying.\r\n- Shared, UITask-decoupled `RadioPresetPicker` and `RadioParamsEditor` (plus `nearestBwIndex()` in `RadioPresets.h`) replace ~6 duplicated methods and several state fields per screen.\r\n- Mesh `Dispatcher` gains generic per-payload-type RX/TX counters and pool-free / queue-length getters; a new `DeviceDiag` helper reports nRF52 heap (linker-symbol + `sbrk`) and stack (FreeRTOS high-water-mark) headroom.\r\n- `build.sh` tolerates control characters in `pio project config`'s JSON dump.", "notesHtml": "

MeshCore Solo Companion Firmware v1.20

\n

What's new

\n\n

Fixes

\n\n

Under the hood

\n\n" }, { "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 `