Skip to content

MeshHome 1.2.0

Choose a tag to compare

@roach0816 roach0816 released this 12 Nov 23:03
· 13 commits to main since this release

MeshHome can now run on Meshtastic as well as MeshCore. Choose the mesh in Settings, and contacts, channels, messages, tracking and the rest of the app follow it.

MeshCore or Meshtastic

  • Where to choose: Settings → Radio → Radio connection → Mesh: MeshCore or Meshtastic.
  • What follows it: everything shows that mesh's contacts, channels, messages, notifications, bot replies, map and trackers.
  • Switching back: the other mesh's are kept, and come back when you switch.
  • With the radio HAT, MeshHome runs what the HAT runs: switching the HAT between ZephCore and meshtasticd switches MeshHome with it. The HAT stays selected as the radio either way.
  • Meshtastic radios:
    • The radio HAT running meshtasticd.
    • A Meshtastic node on the network (its API on TCP port 4403, e.g. an ESP32 node with Wi-Fi).
    • A simulated mesh: two trackers on your course, a router at the car, and a hiker who chats and answers messages.

Messaging on Meshtastic

  • Contacts are the nodes the radio has heard, with their node id, role, battery, signal and hop count. Favouriting and removing a node go to the radio.
  • Channels are the radio's own. An unnamed primary channel goes by its preset ("LongFast"), as in Meshtastic's apps. The + in the conversation list adds a channel, or joins another group's from their share link or QR code.
  • Direct messages:
    • The radio encrypts them end to end, and the recipient's acknowledgement shows as Delivered.
    • The radio retries on its own, so each message is sent once.
    • If the recipient refuses it because the two radios haven't swapped keys yet, MeshHome sends this radio's details and the message says to send it again.
  • Length: messages are up to 200 bytes.

Node settings for Meshtastic (Settings → Radio → Configure node settings)

  • The radio itself: name and short name, LoRa region, modem preset, hops and transmit power, role, and a fixed position (also the base on MeshHome's maps).
  • Channels:
    • Name, key (private, or Meshtastic's default), and how precisely positions are sent.
    • Each channel's QR code, to put it on trackers and other nodes. On an iPhone, scan it with the Camera app; on Android, use the scan button in the Meshtastic app's Settings → Channels.

Tracking on Meshtastic

  • Adding a tracker: Meshtastic trackers are added from the nodes the radio has heard, or from a contact, and every position they broadcast is recorded.
  • The channel: for exact positions only your team can follow, give the primary channel a private key with exact positions in Node settings, and scan its QR code into each tracker.
  • From 1.1: the separate "Meshtastic trackers" connection in Settings → Tracking is gone: Meshtastic is now the radio itself. A 1.1 setup carries over: the radio HAT running Meshtastic (or the Meshtastic node you'd set) becomes MeshHome's radio.

Each mesh's own features

  • Hidden on Meshtastic:
    • Repeater and room server administration.
    • Routes, traces and the preferred repeater.
    • Signed messages and contact QR codes.
    • Radio firmware updates and radio backups.
  • Hidden on MeshCore: the Meshtastic settings.

API change: these 1.1 endpoints are removed:

  • GET/PUT /api/settings/meshtastic
  • GET /api/tracking/meshtastic
  • POST /api/tracking/meshtastic/channel
  • GET /api/tracking/meshtastic/channel-url

The Meshtastic radio's settings are under /api/node/meshtastic. GET /api/status reports the technology in use as radio_config.tech, and MeshCore-only endpoints answer 409 while Meshtastic is in use. See docs/API.md.

Not yet tested on real Meshtastic radios. It was tested against meshtasticd 2.7.26 and MeshHome's simulator. Direct messages between radios were tested with the simulator only, because meshtasticd's simulated radio doesn't encrypt them.

Upgrading: update from Settings → Software, or run sudo meshhome update on the Pi. For containers, pull the new image (Kubernetes/Fleet picks up the pinned image automatically). Your data and settings carry over.