Repository navigation
MeshHome 1.0.20
More on each tracker: how far along the course, pace and ETA, battery percentage, which repeater its answer came through, and its sensor readings, in metric or imperial units.
Course progress
- Each runner's position is placed on their course: "Red Loop · 3.2 of 6.5 mi · 49%", or "Off Red Loop (400 ft away)" when they're more than about 120 m (400 ft) from the line, or finished.
- Choose the loop in the tracker's Edit dialog. At a handoff, change the label and the course together. Automatic uses the course the tracker's position is on, which can be wrong where loops share trail.
- Start and finish: where a loop's start and finish meet, and on out-and-back sections, MeshHome follows on from the previous position, so a runner coming in reads 99%, not 1%.
Pace and ETA
- "9:35 /mi · ETA 3:42 PM (20 min)" (or per km): pace is the distance covered along the course over the last ten minutes, and the ETA assumes that pace for the rest of the loop. A good cue for waking the next runner.
- Without a course: pace uses the straight-line distance between fixes, which reads slower on twisty trail. A runner who has stopped shows Not moving.
Battery percentage
- The battery shows as an approximate percentage worked out from the voltage, in red at 20% or below. The voltage is still shown in the list.
- High-voltage batteries: a tracker that has ever reported over 4.25 V is taken to have a high-voltage cell (full at about 4.35 V), like the SenseCAP MeshTracker X1's. It reads lower for the same voltage, so it doesn't sit at 100% for the first hour.
Which repeater it came through
- "via Car Repeater · SNR 4.8 dB", or "heard directly", read from the radio's log of the packets it hears. Tap the tracker on the map for the whole route and RSSI. This shows where your coverage hands over between repeaters along the course.
- Repeaters are named after your contacts whose key starts the same way.
Sensors
- If the tracker shares its environment readings (MeshCore app → Telemetry → Environment), its temperature, barometric pressure and altitude from the barometer are shown too.
- The temperature is measured inside the tracker, so in a pocket it mostly reads the runner's body heat.
- Trackers whose firmware doesn't report a barometer simply don't show these.
Metric or imperial
- One Units setting for all of MeshHome: metric (km, m, °C, hPa) or imperial (mi, ft, °F, inHg). It covers the Tracking page (course distances, pace per km or per mile, off-course distance, altitude, temperature, pressure), the radio's sensors and the
/envbot reply. - Where to change it: in Settings → Tracking, or where it already was, with the radio's sensors. Changing it in one place changes both.
- Your existing choice carries over: if you'd already chosen imperial for the sensors, Tracking uses imperial too. The API always uses metric.
Rehearse at home: the simulated radio's tracker now reports a slowly draining high-voltage battery and sensor readings. Its answers come through the simulated repeaters.
Not yet tested on a real tracker. Please report how progress, the repeater shown and the sensor readings look on your X1s.
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 the new columns are added automatically.