MeshCoreTel-firmware release assets are published on:
There are currently two release tracks in this repo:
companion-wifirepeater-mqttDownload the asset that matches your board and firmware type.
Examples:
heltec_v4_companion_radio_wifi-v1.14.1-abcdef.binheltec_v4_repeater_mqtt-v1.14.1-vbart-meshcoretel-v1.0.1-abcdef.binheltec_v4_repeater_mqtt-v1.14.1-vbart-meshcoretel-v1.0.1-abcdef-merged.binThe important part is the board/env prefix:
*_companion_radio_wifi*_repeater_mqttUse the standard .bin file when you are updating an existing device with the same target and partition layout.
Use the -merged.bin file when you want a clean install after erasing flash. This is the full ESP32 image and is intended to be flashed from address 0x0.
Practical rule:
.bin = incremental update-merged.bin = erase and clean flash.bin, or erase the device first and flash the -merged.bin.The recommended flasher is:
It includes native support for:
companion_radio_wifi firmwarerepeater_mqtt firmwareRecommended usage:
.bin there when you are updating an existing device-merged.bin there after an erase when you want a clean flashIf this is your first time flashing MeshCoreTel-firmware, the easiest path is:
Companion WiFi, Repeater MQTT, or Custom.The flasher site includes two especially useful actions after flashing:
Repeater SetupConsoleRepeater Setup is the guided first-time repeater flow.
It is the traditional way to configure a repeater after flashing, including:
As of v1.2.1, the local repeater web panel also includes the same common repeater settings, so users can complete initial setup there and return for occasional troubleshooting or configuration changes. On MQTT repeaters that need maximum headroom, it is still best to disable the panel again when you are finished.
Console is the raw CLI interface.
It is especially useful, and often required, for the initial Wi-Fi setup on both firmware tracks:
set wifi.ssid <your-ssid>set wifi.pwd <your-password>This applies to:
companion_radio_wifirepeater_mqttrepeater_mqtt builds include the MeshCoreTel-firmware MQTT additions. Depending on the board, they may also include the local web panel.
Typical first steps after flashing:
wifi.ssidwifi.pwdmqtt.iataget mqtt.statusmqtt.owner and mqtt.emailletsmesh-eu or letsmesh-uscompanion_radio_wifi builds are for companion devices that expose the app interface over WiFi instead of BLE or USB.
Typical first steps after flashing:
get wifi.status