A proper logbook for your robot mower.
You spent real money on a little robot and let it loose in your garden. Mine works really well, when it does. But sometimes it just doesn't. It moves out of the charging station for no reason in the middle of the night, and powers off. It suddenly bumps into obstacles when it circumvented them 100 times beforehand. So I wanted to put actual data around as many perspectives to troubleshooting as possible, and tap into 'crowd knowledge' in the hope to build a giant database of robotic mower datapoints that eventually would help everyone to live happier lives with their robots!
Made for Luba, Navimow, Automower, Goat, Yuka and all the others. If it is a robot and it cuts grass, it belongs in here.
Early access, so things may change and data may be wiped. See the disclaimer.
The days it pays you back
A few moments where having written it down changes the outcome.
The update that broke it.
An update arrives during the night, and suddenly the mower gets stuck behind the same shed it passed without any problem the whole summer. Was it better on the older firmware? If you wrote it down, you know. If not, you can only guess, and I have done a lot of guessing already.
The warranty call.
Something stops working, you call support, and the first question is always when you last serviced it and what you changed. With the whole history in one place, that conversation becomes a lot shorter.
Selling it later.
When you upgrade one day, a sentence like 'here is the complete service and firmware history since the first day' gives you a better price, and a buyer who does not start to negotiate everything.
The corner it hates.
Mine sulks in the same corner every time it rains. It took me a long time to notice, because the information lived in my head and not on paper. Once it was written down, the pattern was obvious. It was not haunted after all. Only drainage.
Is it me or the mower?
Most of the time you simply want to know if the problem is your machine, or a bug that everybody has. This part is coming. Once enough of us log the same models, you will be able to check.
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
This is the part I am most excited about, and also the part that is not finished yet. Once enough people log the same mowers, you will see what is normal and what is a known problem for your exact model and firmware. It can only work if there is data inside, so the early logs really matter. To be honest: join now, and help to build the thing you will want to use later.
Connect your tools
A public HTTP API lets you push entries from Home Assistant, your own scripts, or anything that can POST JSON. Read the docs and grab a token on the developers page.
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. One day I would like to write a sentence like 'v2.4 brought the stuck rate down from 38% to 9%', and really have the numbers to support it. Today we cannot, and that example is invented. This is exactly why logging exists. With enough real entries, we can finally give a real answer.
Your data is yours, your name stays out of it
I only need to know that there is a real person with a real mower on the other side, and then I stop asking. The public pages show the handle you chose, and nothing more. I am not selling anything here, and honestly, I have no interest in where exactly your garden is.