A proper logbook for your robot mower.
You bought a small autonomous vehicle and let it loose in your garden. It deserves better than a sticky note on the charging station. Log every mow, repair, blade swap and firmware bump in structured entries, then see what everyone else with your exact model is running into.
The whole loop
From unboxing your mower to figuring out why it sulks behind the apple tree.
Register your mower
Brand, exact model, positioning (wire, RTK, vision), and the firmware versions running on each component. Later questions adapt to what you actually own.
Log what happened
Mow, repair, cleaning, blade swap, weird behaviour. Tap once to clone yesterday's entry when the answer is 'same as before, still chewing grass'.
Compare notes
Coming up: success rates per model and firmware, blade-life curves, and which lawn shapes wreck which navigation systems.
Structured logs and data that can be queried for insights
The usual mower forum is a 47-page thread titled "weird beep??" with no tags and one helpful reply on page 12. Mowlog goes the other way: enums, statuses, failure categories. Boring to write, beautifully GROUP BY-able later.
Firmware as a first-class citizen
Modern mowers run a small fleet of MCUs: main board, wheel controllers, RTK base, sometimes a camera SoC. Every log entry snapshots the exact versions on board at that moment, so eventually we can say things like v2.3 → v2.4 took stuck-rate from 38% to 9% with receipts.
Your data is yours, your name stays out of it
We need just enough to confirm there's an actual human with a mower on the other end, and then we stop asking. Public pages show the handle you picked, never your email. We don't sell your personal data, and we have no interest in where exactly your garden is.