Repeater settings: - Each setting is declared once in repeaterSettingSpecs (key, section, input type, range, step, labels); the screen builds its control, refresh and save command from that list. - Add flood.max.advert, flood.max.unscoped, rxdelay, cad, adc.multiplier and extra.sf. adc.multiplier and extra.sf note their hardware limits (extra.sf is LR2021 only and its get reply has no "> " prefix). - Settings can be edited before they are fetched; only edited ones are sent. set radio needs freq, bw, sf and cr together, so a missing one is reported instead of silently skipping the radio. - Check tx delays against the firmware's 0-2 range. - Keep the not-loaded hint's list slot so the Advanced card doesn't collapse when the first value arrives. - New "Auto-fetch repeater settings" app setting, off by default: each get is a LoRa round trip. Fixes: - Adding a discovered contact sent its advert time as lastmod, making it the oldest contact; with overwrite-oldest on a full table the next add evicted it and it reappeared in the discovered list. Let the radio stamp its own clock. - Snackbars replace each other instead of queueing. Translations: add the new strings in all locales and fix widespread mistranslations in hu, ko, sk, sl and uk.
MeshCore Open - Feature Documentation
MeshCore Open is an open-source Flutter client for MeshCore LoRa mesh networking devices. These guides describe current user-facing features and their requirements. Reviewed against app 9.5.0+18 on October 11, 2026. Hardware behavior still depends on platform, radio, and firmware.
Start here
- Use compatible MeshCore companion firmware and connect a radio.
- Wait for synchronization, then open a channel or contact chat.
- For scoped floods, configure regions. For image packets, install the image model.
- If a device or feature is unavailable, use troubleshooting.
Table of Contents
- Scanner & Connection - BLE scanning, USB serial, and TCP connection with automatic reconnect
- Navigation - App flow, device screen, and quick-switch navigation
- Contacts - Contact management, groups, discovery, nearby-node scan, discovered-contact import/export, and sharing
- Chat & Messaging - Direct messages, location sharing, message status, reactions, and retries
- Channels - Broadcast channels, communities, channel chat, and auto-resend
- Map & Location - Node map, shared pins, path tracing, line-of-sight, and offline caching
- Settings - Device settings, app settings, radio configuration, and exports
- Notifications - System notifications, replies from watches and Android Auto, unread badges, and notification preferences
- Repeater Management - Repeater hub, status, CLI, telemetry, and neighbors
- Additional Features - GIF picker, localization, debug logs, SMAZ compression, and more
- Routing Paths - Path encoding, validation, device capability detection, and storage
- BLE Protocol & Data Layer - Technical reference for the communication protocol and data architecture
- Regions - App and radio default regions, unscoped sends, message labels, and reply regions
- Image Messages - Model setup, mesh image sending, recovery, and reconstruction
- Companion Radio Statistics - Noise, signal metrics, and airtime
- Troubleshooting - BLE, USB, browser, and firmware issues
- Review Mode - Simulated radio and reviewer instructions for Google Play and App Store review
- Network Map - Online repeater map, adding and managing repeaters from it, opt-in uploads, and hiding a repeater
App Overview
MeshCore Open connects to MeshCore LoRa mesh radios over BLE, USB, or TCP. Once connected, users can:
- Chat with other mesh nodes via encrypted direct messages
- Broadcast on shared channels (public, hashtag, private, or community-scoped)
- View nodes on a map with GPS locations, predicted positions, and path traces
- Manage repeaters with CLI access, telemetry, neighbor info, and settings
- Share contacts via
meshcore://URIs and QR codes - Share locations as map pins from chat or the map
- Scan for nearby nodes and import/export discovered contacts
- Configure radio settings including frequency, power, bandwidth, and spreading factor
- Cache offline maps for use without internet connectivity
- Analyze line-of-sight between nodes with terrain elevation profiles
- Use Android Auto to hear new messages and reply by voice while driving (Android)
What needs internet?
| Feature | Internet requirement |
|---|---|
| Radio messaging, region-scoped sends | No internet needed for the mesh transport |
| Mesh image encoding/reconstruction | Local after model installation |
| On-device translation | Local after model installation |
| Model downloads | Internet required |
| GIF search/display, URL image previews, and IPFS image/file uploads | Internet required to upload or retrieve content |
| Map display | Cached tiles work offline; uncached tiles need internet |
| Online network map and opt-in uploads | Internet required |
| Terrain LOS analysis | Elevation lookup needs internet unless the required data is already cached |
Keeping documentation current
When changing a feature, update its access steps, defaults, platform/firmware requirements, failure states, and screenshots. Keep binary framing details in the protocol reference and implementation links. See contribution guidelines.