EastMesh 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-eastmesh-v1.0.1-abcdef.binheltec_v4_repeater_mqtt-v1.14.1-eastmesh-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-merged.binFor custom firmware files, use:
Recommended usage:
.bin there when you are updating an existing device-merged.bin there after an erase when you want a clean flashrepeater_mqtt builds include the EastMesh MQTT additions. Depending on the board, they may also include the local web panel.
Typical first steps after flashing:
get mqtt.statusletsmesh-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