I have published mups18-2 (MeshCore v1.18.0.mups2), the second release of my custom MeshCore firmware based on IoTThinks PowerSaving-v18. It uses the same base and the same pull requests as mups18-1. The changes are mostly about seeing what a repeater actually does with the radio channel.

See why receiving fails.

“get rx.errors” on a repeater shows receive errors by cause: correctly received frames, CRC errors split into payload and header errors, and everything else. “get rx.errors snr“, “get rx.errors rssi” and “get rx.errors len” give histograms, and “get rx.errors last” lists the latest broken frames with age, RSSI, SNR, length and first bytes.

See how often the channel is busy.

“get cad” now also counts how often a send attempt found the channel busy and had to wait, and how often the repeater transmitted anyway after the maximum wait. I also fixed a timer in the channel check: an old busy episode could make the next packet go out immediately.

Smaller things:

  • Trailing blanks in CLI commands are ignored on repeaters, room servers and sensors, so e.g. “get txdelay ” works. Passwords are left exactly as typed.
  • The packet filter’s filter age now also drops group texts stamped too far in the future, taken over from Dutch-MeshCore. It stays off by default and in dry-run mode.
  • The base moved to the PowerSaving-v18 state of 2026-11-04. New in the file list: Xiao S3 WIO as repeater and companion.

Changed defaults (new installs only; existing devices keep their settings):

“advert.interval” is now 238 minutes instead of 240,
“agc.reset.interval” is 0 (the official default) instead of 12 s,
and the filter’s hop limit for REQ, RESPONSE and ANON_REQ is 5 instead of 6.

As always: use at your own risk, make a backup first, and back up the device’s private key. Without it a device gets a new identity after a full erase or a change of firmware.

Download and details: https://github.com/m0urs/MeshCore/releases/latest

MeshCore V1.18.0.mups2 is out: Better Tools For Finding Out Why Packets Get Lost
Tagged on:

Leave a Reply

Your email address will not be published. Required fields are marked *