Meshtastic canned-message setting can brick Muzi SuperBase, report says

A single canned-message toggle on the Muzi SuperBase can push the board into a state where Bluetooth, the serial interface, the Android app, and the CLI all drop out at once. For Meshtastic owners who rely on the device itself to keep working, that is not a minor glitch. It is a recovery problem.

The failure was filed in Meshtastic firmware issue #10692 on June 11, 2026, and the reproduction path is precise. Flash Meshtastic 2.7.15 onto a Muzi SuperBase using firmware-muzi-base-2.7.15.567b8ea.uf2, pair it with the Android app, open Modules Configuration, enable Canned Message with Up/Down/Select input enabled, save, and let the node reboot. After that reboot, the reporter said Bluetooth was unavailable, the Meshtastic serial interface was unavailable, the node no longer appeared in the Android app, the CLI could not connect, and the device seemed to live only in UF2 bootloader mode.

What makes the report stand out is persistence. The problem survived normal reboots and even firmware reinstallation. Recovery took a much harder route: enter UF2 mode, flash nrf_erase2.uf2, reconnect with `meshtastic noproto`, then reflash the normal firmware image. That is the kind of sequence most users do not expect to need after changing a settings page.

The canned-message module is supposed to do the opposite. It lets users send predefined messages directly from the device without reaching for the phone app, and the documentation lists Rotary Encoder Enabled and Up Down Encoder Enabled as supported input paths. It also notes input-broker pin and event mappings, and says the module was tested with a generic rotary encoder, an up/down/select 3-button logic interface, and certain I2C keyboards. The same docs warn that GPIO access is fundamentally dangerous and can physically damage hardware if it is configured incorrectly.

That warning matters here because Muzi’s BASE System is built around extensive I/O, and Meshtastic’s own Muzi documentation describes it as a modular development platform. Base Uno and Base Duo are supported through the Backer Program, which makes board-specific input mapping and startup sequencing bugs especially painful when they touch a core feature like on-device messaging.

The issue also fits a broader pattern. Meshtastic Android issue #4112 reported that USER_PRESS and ALT_PRESS options were unavailable for CW/CCW input events in canned-message configuration, even though those events are required for proper rotary encoder operation with BaseUI. Taken together, the reports point to a simple but serious lesson: on a compact board, one input setting can be enough to brick normal access paths if startup and peripheral handling are not locked down.