Skip to content

MeshHome 1.1.0

Choose a tag to compare

@roach0816 roach0816 released this 12 Nov 18:28
· 17 commits to main since this release

Meshtastic trackers, such as a SenseCAP X1 running Meshtastic, can now be followed on the Tracking map alongside MeshCore trackers. The radio HAT can run Meshtastic to hear them.

Meshtastic trackers

  • Nothing is polled. Meshtastic trackers broadcast their position on their own (on a timer, or when they've moved with smart position), and MeshHome records every position it hears from a tracked node.
  • Course progress, pace, ETA and offline maps work the same as for MeshCore trackers.
  • The details shown:
    • The battery level the tracker reports.
    • Its temperature and pressure.
    • How the packet arrived: "via Car Router (2 hops) · SNR 6 dB", or "heard directly".
  • Add one from Tracking → Add a tracker → Meshtastic node, which lists the nodes the Meshtastic radio has heard, trackers first.
  • Ask now sends a position request. A Meshtastic tracker answers at most every 3 minutes.
  • After a reconnect, positions heard while MeshHome was disconnected are filled in from the node's own list.

Where they're heard (Settings → Tracking → Meshtastic trackers)

  • The radio HAT on this Pi, running Meshtastic (below).
  • A Meshtastic node on the network, through its API on TCP port 4403 (for example an ESP32 node with Wi-Fi).
  • Simulated: two trackers running your first visible course, plus a router at the car, to rehearse at home.

A private team channel

  • Why: on Meshtastic's default public channel, positions are sent blurred to about 1.5 km, and anyone nearby can follow them.
  • Setting it up: Set up a team channel gives the Meshtastic radio a private channel with a random key and positions at full precision, plus your region and modem preset.
  • The QR code: scan it with the Meshtastic app into each tracker and relay (Channels → scan → Replace). That also matches their radio settings to MeshHome's. The code holds the channel key, so keep it to your team.

The radio HAT can run Meshtastic

  • Switching: Settings → Radio connection → Radio HAT on this Pi → Switch to Meshtastic, choosing the RAK module (RAK13300 or RAK13302) and its IO slot. Or run sudo meshhome radio-hat setup --firmware meshtastic.
  • What it does:
    • Installs meshtasticd (Meshtastic for Linux) with apt from Meshtastic's own repository, after checking the repository key's fingerprint.
    • Keeps meshtasticd reachable from the Pi only.
  • While it runs Meshtastic, the HAT isn't MeshHome's MeshCore radio: that radio mode is turned off and remembered.
  • Switch to MeshCore brings ZephCore back with its identity, contacts and channels, and Meshtastic's channels are kept for next time.

API change

  • For Meshtastic trackers, contact_id and public_key are null, and the new source field reads meshtastic with a node_id. Scripts that read trackers through an API key should handle that.
  • New endpoints: /api/settings/meshtastic and /api/tracking/meshtastic/…. See docs/API.md.

Licences: MeshHome stays MIT. It talks to meshtasticd (GPL-3.0, installed separately) over its network API, using a reader written for MeshHome.

Not yet tested on real Meshtastic hardware. This was tested against meshtasticd 2.7.26 and in Debian 13 containers.

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, and nothing changes until you choose Meshtastic.