Skip to content

mups18-3 (v1.18.0.mups3)

Latest

Choose a tag to compare

@m0urs m0urs released this 15 Nov 16:43

Use at your own risk. This firmware may contain bugs, and I accept no liability for its use.
Before flashing, make a backup if at all possible. Back up the device's private key first and keep it safe –
without it a device gets a new identity after a full erase or a change of firmware.

mups18-3 – MeshCore v1.18.0.mups3

Custom MeshCore firmware based on IoTThinks PowerSaving-v18 (MeshCore main v1.18.0, PowerSaving-v18 as of 2026-11-14).
Full documentation: MUPS18.md

Third release of the mups18 line, mainly a bug-fix release: please update from mups18-2. Same pull requests as mups18-2; the changes are listed below.
Behaviour that only shows over several days of operation (long-term power saving, resend statistics) is still being observed. Please report problems.

What is new compared to mups18-2

  • Fix: the trailing-blank handling of mups18-2 is removed again (repeater, room server, sensor). mups18-2 cut off blanks at the end of every CLI command. Some official commands need exactly that blank, so they failed:

    • "Remove All Neighbours" in the app (it sends neighbor.remove with a blank as an empty prefix) was rejected – the app showed "Firmware Update Required".
    • set owner.info with an empty value (clears the owner info) did not work.

    The CLI now behaves exactly like the official firmware again. This also means that get txdelay with a trailing blank is rejected again, as in the official firmware.

  • TRACE packets (path trace), contributed by Sebastian van de Meer (#25, #26): a repeater in the middle of a trace path no longer re-sends each trace up to max.resend times after the next hop has already forwarded it. The last hop before the trace destination now sends once through the normal channel check and is no longer counted as a resend in get max.resend. Normal messages are not affected. Both issues come from PR meshcore-dev#2670 and were reported there.

  • Base: PowerSaving-v18 as of 2026-11-14, among others: companion GPS follows the companion's powersaving setting (GPS on and off in cycles), new companion CLI commands gps, gps on, gps off, gps sync, GPS fix for the GAT562 30S, support for the INA228 current sensor.

  • File list: all devices of mups18-2, including the ones that were added to mups18-2 afterwards.

Defaults

No changed defaults compared to mups18-2. The packet filter is still off by default and in dry-run mode: after filter on the repeater only counts what it would drop and still forwards everything; check filter stats, then use filter dryrun off to really filter.

Included

Component Source Notes
RX duty-cycle power saving (radio.rxps), powersaving (companion), powerlog, sensor, reboot.interval IoTThinks PowerSaving-v18 base
Release fixes MeshCore main pinned to v1.18.0
Allow setting the clock backwards, elapsed-time underflow fix PR #1349
Separate replay counters for login and messages PR #2834 repeater, room server, sensor
Flood ACK on DM retries PR #3260
Beeps for buzzer on/off, T1000-E button debounce 20 ms PR #3536 companion
Repeater reply path (outpath) PR #2586 repeater
Repeated sending of direct packets (max.resend, on by default, 3) PR #2670 partial port: without noise-floor median estimator and RX-desync watchdog (both conflict with power saving); with the TRACE fixes from #25 / #26
Repeater packet filter (filter …) Dutch-MeshCore dmc-dev (7df3767c) repeater only, off by default; own defaults (dry-run on); own fixes: channel block by key (MAC), limiter setup
Airtime reserve for scoped floods (fwd.scoped.reserve) own, idea from ACETyr/MeshCore repeater only, off by default

Own changes

Radio preset (all roles): 869.618 MHz, BW 62.5, SF 8, CR 8

Duty cycle (all roles): 10 % (af 9.0)

Companion: hardware CAD before TX (cad) on by default, as on the repeater (set cad on|off).

Repeater defaults:

Setting Value
rxdelay / txdelay / direct.txdelay 2 / 1.0 / 0.4
advert.interval / flood.advert.interval 238 min / 167 h
flood.max / flood.max.unscoped / flood.max.advert 15 / 3 / 3
multi.acks / path.hash.mode 1 / 2
loop.detect moderate
agc.reset.interval 0 (off)
cad on

WiFi companions: the firmware contains no WiFi credentials of mine. The Heltec V3 WiFi image has the placeholders myssid / mypwd compiled in. Set your own with the companion CLI or the rescue CLI (long press of the PRG button within 8 s after boot, serial console 115200 baud):

set wifi.ssid <your SSID>
set wifi.pwd <your password>

then reboot. get wifi.status shows the state, set wifi.clear removes the stored credentials. The Heltec V3 BLE companion, the Heltec V4 (OLED) BLE companion and the Heltec V4.3 (OLED) BLE companion also contain the WiFi interface, but keep WiFi off until an SSID is set. The Heltec V4.3 TFT BLE companion is built without the WiFi interface.

Defaults apply to new installs / after erasing the settings only – existing devices keep their stored settings (set dutycycle 10, set flood.max 15, … on the repeater; rescue CLI or companion CLI on the companion).

Devices and files

Repeater: Heltec V3, Heltec V4 (OLED), Heltec V4.3 (R8, OLED and TFT), Heltec T096, Heltec T114 (without display), RAK4631, SenseCAP Solar, Xiao S3 WIO, Xiao nRF52, T1000-E, Wio Tracker L1 (standard variant, not 1W), ThinkNode M6, GAT562 30S Mesh Kit.
Room server: Heltec V3.
Companion (BLE): Heltec V3, Heltec V4 (OLED), Heltec V4.3 (R8, OLED and TFT), RAK WisMesh Tag, GAT562 30S Mesh Kit, T1000-E, Wio Tracker L1, LilyGo T-Echo, Xiao S3 WIO. Companion (WiFi): Heltec V3.

Device type File Use
ESP32 (Heltec V3, Heltec V4, Heltec V4.3, Xiao S3 WIO) *.bin Update (app image only) – web flasher (non-merged) or OTA; settings are kept
ESP32 (Heltec V3, Heltec V4, Heltec V4.3, Xiao S3 WIO) *-merged.bin New install / recovery (bootloader + partitions + app, written at 0x0). The web flasher erases the whole flash when a merged image is selected
nRF52 (RAK4631, RAK WisMesh Tag, GAT562 30S Mesh Kit, SenseCAP Solar, Heltec T096, Heltec T114, Xiao nRF52, ThinkNode M6, T1000-E, Wio Tracker L1, LilyGo T-Echo) *.zip Update via DFU – web flasher (serial) or nRF Connect app (BLE); settings are kept
nRF52 (same) *.uf2 Update via drag & drop – enter bootloader (usually double reset), copy file to the USB drive; settings are kept

.zip and .uf2 contain the same firmware – two ways to flash it. Neither erases settings.
For a clean install on nRF52, erase first (web flasher erase function, or rescue CLI erase on a companion), then flash.

Firmware version on the device: v1.18.0.mups3 (ver).

Default TX power (Heltec V4, Heltec V4.3 and Heltec T096; repeater and companion builds): the default is taken unchanged from the base (IoTThinks PowerSaving-v18) and is 17 dBm on these boards. The base's source comments say that 17 gives roughly 28 dBm at the antenna on these boards (the amplifier stage adds gain). I have not measured the real output. Please check what is permitted in your region and with your antenna, and set your own value with set tx <dBm> if needed. Like all defaults, this only applies to new installs / after erasing the settings.

The Heltec V4 repeater and companion (BLE) builds are the OLED variant (same environments as the official heltec_v4_repeater and heltec_v4_companion_radio_ble); the Heltec T114 repeater build is the variant without display. For the Heltec V4.3 there is one OLED and one TFT build each (heltec_v4_r8_… and heltec_v4_r8_tft_…); the name "V4.3 = R8" is taken from the base's commit message, so please check that your board is an R8 before flashing.

The LilyGo T-Echo build covers only the LilyGo T-Echo companion (BLE), not the T-Echo Lite or T-Echo Card.