Skip to content

MeshHome 1.3.0

Choose a tag to compare

@roach0816 roach0816 released this 13 Nov 14:26
· 7 commits to main since this release

Settings → Health & logs: what's working and what isn't, and MeshHome's own log.

Health

  • What's checked, every 30 seconds:
    • the radio connection, the radio HAT, and when the radio last heard the mesh
    • sending and collecting messages
    • trackers
    • the database, MeshHome's background services, notifications, the HTTPS certificate and updates
    • on Linux: the computer's disk, memory, temperature, power supply and clock
  • When something isn't working, its line opens by itself with what it means in plain words, numbered steps to fix it, the facts behind it, and links to the setting and to its log lines. For example: "Nothing is accepting connections at 192.168.1.40:4403" rather than "Errno 111", or "The radio HAT's software (meshtasticd) isn't running".
  • Where you'll notice it: a dot beside Health & logs in Settings when something needs attention, and a What's wrong? link in Settings → Radio while the radio is offline.
  • Copy report (Download report without HTTPS) copies the whole check, recent problems and the radio's connection history as text, to paste when asking for help. It contains no passwords or keys, but does include network addresses and names.

Log

  • History keeps warnings, errors and events for 30 days. Events are the radio connecting and going offline, MeshHome starting and stopping, and radio settings, radio HAT changes and updates being requested. A line that repeats, such as the radio retrying all night, is one entry with its count and time span.
  • Since start shows every line since MeshHome started.
  • Filters: part of MeshHome, problems only, and text search.
  • Database outages: lines are kept in memory while the database is unavailable and saved when it's back, so an outage shows up in the history too.
  • Stopped services: a background service that stops after an error is now reported.

API: GET /api/system/health returns the same checks and can be read with an API key, so monitoring tools can watch it. GET /api/system/logs and GET /api/system/health/report are for signed-in browsers. See docs/API.md.

Not yet tested on a Raspberry Pi: the radio HAT and "This computer" checks. They read the same system information as sudo meshhome status.

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; the log history starts with this version.