MarekZegare4/MeshCore-Solo v1.18 on GitHub

MeshCore Solo Companion Firmware v1.18

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.

GAT562 30S Mesh Kit support — see above.
Battery saving (radio) — two new independent toggles under Settings › Radio:
- 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
- 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
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.
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.
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.

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.
AbstractUITask::onBLEDisconnected() virtual hook added — called by setHasConnection() on transition to disconnected; UITask overrides it to set _next_refresh = 0.
build.sh gains build-solo-firmwares command, backed by build_all_firmwares_by_suffix "_solo_dual".