Build 2.3.30.26 spotted in the wild — Mammotion hasn't published notes for it. Reminder: back up your maps before updating.
MammoStatsMammoStats

Do I need to update the app AND the firmware? Owners say yes.

The most common confusion in our dataset isn't about any single build — it's that the mower firmware and the phone app version have to move together, and nothing in the update flow clearly says so. Everything below is what owners report or what Mammotion itself states, with counts and links. We don't give repair advice.

Does updating the app actually matter?

Yes, on the evidence. 5 reports in our dataset attribute an apparent mower fault to the phone app rather than the firmware. The starkest: an owner whose mower was unusable for three weeks — through two factory resets, a cloud restore and a refused downgrade request — until reinstalling the phone app fixed it. Another owner traced a blade cutting out during manual mowing to the iOS app after cross-testing on Android; app 2.3.17 resolved it.

Mammotion's own support told an owner directly (reported on roboter-forum, in our dataset) that app and mower firmware become incompatible, including the server connection, unless both are on matching versions. That is their explanation, quoted from their support channel — not our theory.

What do owners report when app and firmware are mismatched?

Connection failures, missing settings, and — the expensive one — behaviour changes with no firmware change at all. App 2.3.17 (2 August 2026) removed the turn-mode setting and owners report mowers silently switching from multi-point turns to tank turning with no owner action: 8 owners within 36 hours, several with turf damage. One LUBA 2 AWD 1000 owner was unaffected, so it isn't universal — which is exactly why we count reports instead of declaring rules.

This is also why our scores only count reports that blame the firmware — see how scores work. App-blamed reports (5) and integration-blamed reports (23) are shown on build pages under “Not the firmware”, not in any score.

How do I see my current firmware version?

In the Mammotion app: Settings → Device Information → Robot Version. The same screen shows the build you're being offered under “New Version”. That screen is also what our 30-second report flow reads — and we discard the screenshot after reading it.

Can I turn off automatic firmware updates?

Partly. Owners use the app's auto-update setting to reduce surprise updates, and it is the most-cited workaround in our dataset. But we hold reports of firmware installing with the setting off(“ohne mein Zutun” — without my doing), and one report of an update being forced during a service re-bind. So the honest statement is: disabling auto-update reduces, but does not eliminate, the chance of being updated.We won't pretend a reliable off-switch exists when owners have documented it failing.

My mower won't start after an update. What have owners done?

Not advice — this is what owners report, with counts. Three independent owners report the same sequence restoring function where factory resets and re-mapping failed: power down the charging station and the mower completely, pull the black safety key, wait, then re-power. One of them now does it after every update as personal policy. Reports of factory resets alone fixing post-update failures are rarer in our data than reports of them not helping.

Can I go back to an older firmware?

Not from the app. But our dataset contains an owner who obtained a firmware downgrade through a support ticketafter submitting logs — and one refused request, so it is discretionary, not guaranteed. Mammotion's published release notes are at support.mammotion.com ↗ if you want to cite a specific build in a ticket.

Every claim above is either an owner report in our dataset (counts shown, sources linked from each build's page) or Mammotion's own statement (linked). Not affiliated with Mammotion. If something here stops matching the evidence, tell us: hello@mammostats.com.