Meck v1.11 -- Private Channels, Channel Sharing, Config Export/Import #14
pelgraine
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
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.
First-Time Flashing -- Read This First
Each firmware is provided in two formats:
filename.bin-- the application firmware only. Use this for updating an existing Meck install (including OTA updates from your phone).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.If in doubt, use the
-merged.binfile. It will always work regardless of what was previously on the device.Flashing with the MeshCore Web Flasher (recommended)
.binor-merged.binfile and click FlashFlashing with esptool.py
What's New Since v1.10
Private Channels
Meck now supports private channels alongside the existing public hashtag channels. The difference is in how the channel secret is generated:
#(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.#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.How to create a private channel:
#prefix, then press EnterThe channel is created with a random secret. To let other Meck users join, use channel sharing (see below).
Channel Sharing via DM
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.
How to share a channel:
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.
On the T5S3, channel sharing works the same way via the CardKB keyboard.
Config Export/Import
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.
Exporting:
The config is saved as a timestamped JSON file in
/meshcore/on the SD card (e.g.meshcore_config_20260523_1430.json). The format is compatible with the MeshCore companion app config export.Importing:
Place a file named
import.jsonin the/meshcore/folder on your SD card. Then either:/meshcore/import.jsonat startup and imports it if foundIf the import includes a different identity (private key), the device reboots after applying the new identity. Channels and contacts are merged into the existing configuration.
Contact Recency Fix
A fix to the
onAdvertRecvhandler ensures that contacts are always bumped to the top of the recency-sorted contacts list when their adverts are heard, even if the advertising node has a stuck or behind clock. Previously, the MeshCore base class replay guard would silently discard adverts with timestamps that hadn't advanced, causing actively heard nodes to sink to the bottom of the contacts list over time.New Emoji
Two new emoji have been added: 💯 (hundred points) and 😁 (grinning face), bringing the total to 79 emoji. They appear near the top of the picker after the zany face emoji.
T5S3 Minesweeper Expanded
The Minesweeper grid on the T5S3 has been expanded from 9×9 (10 mines) to 14×14 (25 mines), taking advantage of the larger virtual display. The T-Deck Pro retains the original 9×9 beginner grid.
Other Changes
T-Deck Pro Firmware Variants
Six companion firmware variants for the LilyGo T-Deck Pro:
v1.11-Meck-4G-BLE.binFor 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, web browser, OTA firmware update, custom notification tones, games, config export/import, and private channel support. Up to 2,000 contacts and 40 channels.
v1.11W-Meck-4G-WiFi.binFor 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). No BLE companion app support. Up to 2,000 contacts and 40 channels.
v1.11-4G.SA-Meck-standalone-firmware (A7682E (4G) version).binFor T-Deck Pro 4G boards. No BLE or WiFi companion -- maximum battery life. The web browser, IRC client, map viewer, and OTA firmware update are all still available (they use WiFi independently, not as a companion transport). Up to 2,000 contacts and 40 channels.
v1.11A-Meck-Audio-BLE (PCM5102A Audio only).binEverything in the 4G-BLE build plus the audiobook player, alarm clock, sleep timer, auto-queuing, and voice notes over LoRa -- minus the 4G modem features. BLE companion support included. Custom notification tones with full MP3 flexibility. Up to 2,000 contacts and 40 channels.
v1.11AW-Meck-Audio-WiFi (PCM5102A Audio only).binSame as the Audio-BLE build but with WiFi replacing BLE as the companion transport. Includes voice notes over LoRa and custom notification tones. No BLE companion app support. Up to 2,000 contacts and 40 channels.
v1.11A-SA-Meck-standalone-firmware (PCM5102A Audio only).binSame as the Audio-BLE build but with Bluetooth and WiFi completely removed at compile time. Includes voice notes over LoRa and custom notification tones. 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 2,000 contacts and 40 channels.
T5S3 E-Paper Pro Firmware Variants
Three firmware variants for the LilyGo T5S3 E-Paper Pro (V2, H752-B):
v1.11-Meck-T5S3Pro-BLE_NOGPS.binBLE companion build. Connect to MeshCore companion apps via BLE. Touch-driven UI with virtual keyboard. Up to 2,000 contacts and 40 channels.
v1.11-Meck-T5S3Pro-WiFi_NOGPS.binWiFi companion build. Connect via MeshCore web app, meshcore.js, or Python CLI over local network (TCP port 5000). Includes the web browser, IRC client, and OTA firmware update. Up to 2,000 contacts and 40 channels.
v1.11-Meck-T5S3Pro-Standalone_NOWIFI_NOBLE_NOGPS.binNo BLE or WiFi -- maximum battery life. Touch-driven standalone operation with full messaging, contacts, reader, and notes. Up to 2,000 contacts and 40 channels.
All T5S3 variants include CardKB support (auto-detected via QWIIC).
MeshCore Companion Apps
BLE variants connect to the standard MeshCore companion apps:
WiFi variants connect via TCP on port 5000:
This discussion was created from the release Meck v1.11 -- Private Channels, Channel Sharing, Config Export/Import.
Beta Was this translation helpful? Give feedback.
All reactions