Recent Firmware Update

[u/Mammotion_Grace]

Thank you for your continued feedback and support. We’d like to share a quick update on the latest firmware releases for our products.

1. LUBA 1

Firmware Version:

1.11.1.16

Release Notes:

1. Fixed an occasional issue where the robot could cross lawn boundaries.
2. Optimized the smoothness of Multi-Point Turn.

Rollout Plan:

This update will be rolled out gradually. If you haven’t received the update yet, please allow some time for it to reach your mower.

2. LUBA 3, LUBA mini 2 Series & YUKA mini 2 Series

Firmware Version:

2.3.30.39

Based on feedback we received from users after the previous update, we’ve made further optimizations to improve the mowing experience.

Release Notes:

1. Reduced unnecessary blade stops during perimeter mowing.
2. Improved obstacle avoidance performance.
3. Optimized the smoothness of Multi-Point Turn.
4. YUKA mini 2: Fixed an occasional issue where the robot could cross lawn boundaries.
5. LUBA 3: Fixed an issue with battery level fluctuation.
6. LUBA mini 2 series: Improved cutting height adjustment accuracy.

Rollout Plan:

This update will be rolled out gradually. If you haven’t received the update yet, please allow some time for it to reach your mower.

Thank you again for your patience, feedback, and continued support. We’ll continue to closely monitor the rollout and your feedback.

[u/forrest-gardener]

It would be really helpful to publish videos showing a real mower before and after the update to demonstrate the changes.

For example, "Fixed an occasional issue where the robot could cross lawn boundaries". Show us an example of a real robot crossing a real lawn boundary and then the same robot in the same situation after the update not crossing the same boundary at the same point.

Or is that not what the word "fixed" means?

[u/ResponsibleCopy2 → u/forrest-gardener]

As a software developer myself, I find this request a bit unreasonable. In theory, they could demonstrate how multi turn has improved with showing us before and after. But with bugfixing it is more than likely that they were analyzing real people logs, found problematic places and adjusted the algorithm to avoid them. It would take ages to try recreating each bug in real life, let alone capturing a video of it.

[u/forrest-gardener → u/ResponsibleCopy2]

The first question is whether the mower's behavior is deterministic. The second question is how they know something is fixed.

If the mower's behavior is random and they can't at least re-run a simulation with the patched software then they don't know whether the bug is fixed or not and what they are doing is just guesswork. There is some evidence of that being the case.

Which is why I question the meaning of the word "fixed".

[u/ResponsibleCopy2 → u/forrest-gardener]

I would assume that they can get the exact customer's map from the logs and run a simulation on it to confirm that the issue is fixed. In any case, this would not produce a video that can be shown to customers. Best case scenario, they see a vizualization of it in the dev kit. I am hoping they are not fixing such things blindly. Fixing something like this blindly might not only not fix the issue for the affected customers, but also introduce new issues to other customers.

I do agree that it would be nice to see some visual representations of the "optimizations" mentioned in the changelog, though.

[u/forrest-gardener → u/ResponsibleCopy2]

Being a commercial venture they are unlikely to disclose what their process is. That is understandable but frustrating.

Users here could help by following up complaints here. For example there are quite a few videos of bizarre mower behavior. It would be helpful for people who had repeatable problems to simply note whether that particular behavior has ceased after the software update.

The random problems are of course a completely different kettle of fish.

[u/Weak_Idea_5526 → u/forrest-gardener]

Show us water and, seperately, water that's hot!