Advanced Features

This section covers software updates, network requirements, the clock, the serial console and storage.

Over-The-Air (OTA) Software Updates

MeshDisplay checks for software updates over Wi-Fi and installs them securely over HTTPS from the TopBytes update service. Updates need Wi-Fi; without it the display carries on with its current software.

How OTA Works

  • About 30 seconds after Wi-Fi comes up, MeshDisplay asks the update service whether a newer release is available for this unit (identified by its Device ID).

  • After that it checks again every hour.

  • Automatic checks only install a strictly newer released version.

Manual Update Check

In Settings → Software update, tap Check now. The row shows the result: Checking for updates..., Up to date, Version X.Y.Z available, or a reason the check failed (for example No Wi-Fi connection or Update server unreachable). If a version is available, it is downloaded and installed straight away.

Beta / Pre-Release Builds

Some units are enrolled for beta (pre-release) builds. Installing a beta is never automatic on a manual check — MeshDisplay asks first:

Beta version X.Y.Z

This is a pre-release test build and may be less stable than the
released version. Install it now?

[ Cancel ]   [ Install ]

On units enrolled for betas, Check now offers a choice of the latest Release and the latest Beta, marking the one installed. Automatic updates then follow the version you choose.

The Update Progress Screen

During an update a full-screen page shows Installing MeshDisplay X.Y.Z with a progress bar and the warning Do not switch off. The display restarts when the update is done. The screen stays steady while the new software is written.

On success it shows Update installed. Restarting... and restarts into the new version. If the download fails it shows Update failed. Nothing was changed; carrying on. and returns to normal — the existing software is untouched.

Your settings, paired radios, message history and map cache are kept across updates.

Warning

Do not remove power during an update. The running software is only replaced once the new one has been fully downloaded and checked, so a power cut mid-download leaves the old version running — but it is still best to let it finish.

Network Administration

MeshDisplay only makes outbound connections over Wi-Fi; it does not accept incoming connections.

Ports Used

Port

Protocol

Purpose

53

UDP (DNS)

Name resolution

123

UDP (NTP)

Time synchronisation

443

TCP (HTTPS)

Software updates (u.topbytes.net); map tiles (tile.openstreetmap.org)

1883 / 8883

TCP (MQTT / MQTT over TLS)

MQTT gateway only, to the broker set on your radio (default mqtt.meshtastic.org)

Firewall Considerations

For normal operation, allow outbound:

  • HTTPS (443) to u.topbytes.net and tile.openstreetmap.org

  • NTP (123) to pool.ntp.org / time.google.com

  • DNS (53)

  • MQTT (1883 or 8883) to your broker, if you use the MQTT gateway

Bluetooth

MeshDisplay talks to your radio over Bluetooth Low Energy using the standard Meshtastic client service, with the link encrypted and authenticated by the radio's PIN. Pairings are stored on the display, so a radio is only paired once.

Time Synchronisation

MeshDisplay takes the time from two sources:

  • Your radio, which knows the time from its GPS, from a phone app or from the mesh. MeshDisplay sets its clock from the radio as soon as they connect.

  • The internet, via NTP (pool.ntp.org and time.google.com), shortly after Wi-Fi comes up.

Until one of these has set the clock, the top bar shows --:--.

Serial Console

Connect MeshDisplay to a computer with a USB-C data cable and open a serial terminal at 115200 baud. The start-up log looks like this:

Starting mesh
[log] LittleFS mounted (2304 / 8064 KB)
Building UI
[ble] host synced
[mesh] history: 152 messages
[ble] connecting to A4:CB:8F:CD:06:09 type 0
[map] tile cache: 117 tiles, 2048 KB
Ready.
[ble] link encrypted
[net] online: MyHomeWiFi ip=192.168.1.42 rssi=-58
[mesh] config complete: node 8fcd0608, 13 nodes, fw 2.7.26
[clock] NTP synced

The console also accepts commands, typed followed by Enter. The most useful are:

help

List the commands

stat

Software version, radio, link state, Wi-Fi, gateway, map cache and memory

nodes

The radio's node list

convs

The chats, with unread counts

msgs [n]

The last n messages

scan

Scan for nearby radios; results lists them

disconnect

Disconnect from the radio

wifi

Saved and nearby Wi-Fi networks

update

Check for a software update now

theme <n>

Switch theme: 0 Classic, 1 Neon, 2 Console, 3 Guide

reboot

Restart the display

Storage

MeshDisplay has about 7.9 MB of storage for its own data, shared by:

  • Message history — the newest 1,500 messages for each paired radio

  • Map cache — up to about 3 MB of map tiles; the cache never leaves less than 2 MB free for messages

Settings → About shows how much is used. Forgetting a radio deletes its message history.

Power Consumption

  • Typical: ~2–4 W at 5 V (mostly the LCD backlight)

  • Peak (Wi-Fi and Bluetooth busy, during an update): up to ~1 A at 5 V

  • Use a quality 5 V / 1 A or higher USB-C supply

  • USB-C power banks work for portable use — handy for field days, events and emergency-communications exercises

  • Use Screen off after to switch the backlight off when the display is idle

Security Notes

  1. MeshDisplay sees every message your radio receives on its channels, and keeps a history. Place it where that is acceptable, and Forget a radio to erase its history from the display.

  2. Use a WPA2/WPA3 Wi-Fi network; avoid open networks.

  3. Keep the software up to date — the update check runs hourly.

  4. Messages relayed by the MQTT gateway to a public broker can be read by anyone with the channel key; the default LongFast key is public. Only uplink channels you are happy to share.

What's Next?