Error 1201 'Robot is trapped' on open ground after updates: LUBA 2 and LUBA mini AWD LiDAR

What owners report

• A LUBA owner says theirs gets trapped all the time. It stops in the middle of the garden with error 1201 several times a week, and the only alert on the phone is "The task has been paused."¹
• A LUBA mini AWD LiDAR warned that it was trapped five times in one mow of about 729 m² (⅛ acre), on open ground with nothing in front or behind. Its owner dates it to the first update in August, after six months without it². A month later the same owner said it happens in a different place each time, at night and on cloudy or rainy days as well, and that pressing start again is enough³.
• A third owner posted photos of the mower stopped as trapped on clear ground. Once it is moved, they say, it ends the task early³. The same day they posted about their LUBA 2 on 1.30.29.26⁵. In that thread a fourth owner says theirs stops the same way whatever the camera mode, and a German owner says they get it going again from the app, which only works since they put a WiFi hotspot on the property. A Mammotion account asked whether it happens at the same spot each time, and for a log and the device name³.
• A LUBA 2 3000H on the .26 firmware gets "Robot is trapped" so often, its owner says, that the blade problem below happens a lot⁴. A fifth owner in that thread says theirs started getting trapped after the update⁴.

When you press Continue, the blades may stay off

The LUBA 2 3000H owner found that after a trapped stop, pressing Continue in the app often sends the mower on its way with the blades still off, about half the times in their experience. It then drives its rows without cutting. Pause and Continue in the app did not turn them back on. Pressing the red STOP button on the mower, then Grass and Start, did⁴. A Mammotion account asked that owner to upload a log⁴.

What Mammotion says to check

In its return-to-charge guide of September 20, Mammotion's support team lists 1201 as a stop in the mowing area. It says to check that the channel between zones is clear of obstacles, No-Go Zones and Virtual Fences and wide enough to pass, then to delete and recreate it if it still fails. On 2025 and 2026 models an Obstacle-Free Zone in that spot may also help. The guide also says to clean the vision or LiDAR module and to check the positioning status in the app⁶. A Mammotion account gave the first owner above the same advice for a narrow spot, and asked for photos, the time and the logs. That owner replied that a zone does not help a mower that stops in open grass¹. The LiDAR owner says Mammotion's answer to their logs was to remap, add a no-go zone or lower the obstacle sensitivity³.

A shadow can do it

One owner whose mower gets trapped on its way back to the charger on sunny afternoons traced it to a hard shadow in front of the station, which it reads as an obstacle³. That does not explain stops at night or on cloudy days, which the LiDAR owner reports³, but it is quick to rule out.

The full list of what the codes around this one mean is on the fault-code page.