If you’ve been running the dev branch, much of this will look familiar.
For main branch users, this update pulls a large set of changes together — improved tracing, better diagnostics, and a more polished UI in one go.
And yes — with a PR this size, a few smaller improvements will inevitably slip past the release notes. You can treat those as a bonus, or an early New Year’s Easter egg.
Trace & Discovery Improvements
Visibility into system behaviour has been significantly improved (and made harder to accidentally misinterpret).
Expanded trace logging for packet flow and routing decisions
Invalid and malformed packets are clearly flagged and skipped
More consistent logging across trace and discovery handlers
The repeater can now be discovered with a scan!
Diagnostics & Metrics
More data, fewer guesses.
Noise floor monitoring with history, statistics, and chart-ready data
New and improved API endpoints for packets, routes, adverts, and neighbours
RRD-backed metrics for efficient long-term tracking
Data Handling & Storage
Packet and advert handling has been simplified and centralised, which also means fewer places to look when something breaks.
New StorageCollector for packets, adverts, and metrics
SQLite and RRDTool integration
Improved raw packet processing and serialisation
MQTT, Transport Security & Configuration
Infrastructure has been tightened up, with fewer sharp edges.
MeshCore to MQTT publishing using JWT authentication
Transport key generation and management via API
Configurable global flood policy
LetsMesh Integration
LetsMesh support is now built in and fully configurable. It can be enabled when needed, tuned to your deployment, or left disabled with no impact elsewhere.
Configuration allows you to:
Enable or disable LetsMesh publishing
Select region via broker index (for example EU or US West)
Provide optional metadata such as IATA code and contact details
Control status update frequency
Filter which packet types are published
UI & Dashboard Updates
No redesign for the sake of it — just clearer information where you need it.
Improved dashboard time formatting
Updated neighbours view with filtering
Better mobile responsiveness
More flexible packet-type graphs
Maintenance & Polish
A large PR means a lot of cleanup, most of it invisible until it isn’t done.
Removal of legacy HTTP template server
Web folder cleanup and CORS support
Improved install and upgrade scripts
Summary
This release brings the main branch up to date with the latest trace, discovery, and UI work. It improves visibility, stability, and day-to-day usability — along with a handful of smaller improvements quietly doing their job in the background.
What’s Next (Already in the Pipeline)
This update isn’t the end of the story — it’s the point where things start moving faster.
Several features are already close to the dev branch, including:
• Remote management and web-based authentication
• A repeater terminal for direct interaction and diagnostics
• Multi - Room server support (separate identity)
• UI-based ping and basic interaction tools
And that’s just the visible part. There’s plenty more planned and in progress, some of which will almost certainly sneak into dev before they make it into a neatly written release note.
As usual, if you’re tracking dev, you’ll see these arrive piece by piece.
If you’re on main, they’ll turn up together — eventually, and with fewer surprises.
Github: https://github.com/rightup/pyMC_Repeater
Join the chat: https://discordapp.com/channels/1343693475589263471/1431414286974189639