Bluetooth drops, or the mower won't connect

The mower cannot be found or connected

A LUBA 2 owner could no longer connect over Bluetooth after reinstalling the camera, powering off and reinstalling the app¹. Mammotion's reply was to try a different phone to see whether the phone is the cause, and if it still fails, to upload the device logs and give the device name¹. Another owner says that for a stretch the mower could not be reached by Bluetooth or Wi-Fi at all, although it looked switched on⁸.

Everything stops at once, often after an update

After updating a LUBA 2 X3000 to firmware 1.30.29.26, the mower stopped answering on Wi-Fi, then connected over Bluetooth only once, and after reinstalling the app Bluetooth worked but the mower could not reach its RTK². Mammotion's advice was to unplug the safety key and restart. The owner reports that taking the key out for 30 minutes fixed it².

A second owner's LUBA 2 AWD would not move under Bluetooth control and then would not connect to the app after a restart. Another poster in that thread says turning the mower fully off and on again cleared a strange post-update state⁴. The full power-cycle order for the mower, charging station and RTK station is on Charging & docking fixes that work across models.

Two owners with the same outcome is a small sample, and neither names a cause. Treat the power-off as the cheapest thing to try, not a confirmed cure.

One owner's fix for random failures: a 2.4 GHz-only network

A LUBA 2 AWD owner in their second season, who had been fighting Bluetooth that would not connect, schedules that did not run, RTK that was not available and poor Wi-Fi, found that the mower and the RTK station had joined a 5 GHz network. They created a separate network limited to 2.4 GHz for the mower and RTK, and advise others to make sure both are on a 2.4 GHz-only network¹¹. The owner says the mower is specified not to use 5 GHz, and does not know why it now seems able to; this site has not checked that. It is one owner's finding, offered after a firmware and app mismatch and repeated restarts, and it is the owner's reading of the cause.

Bluetooth works but the app still cannot connect

A LUBA mini AWD LiDAR owner can find and connect to the mower over Bluetooth but cannot finish the connection to the app⁹. That points at Wi-Fi, cloud or RTK rather than Bluetooth. See App vs firmware vs RTK for how to tell the layers apart, and LUBA 3 firmware 2.3.25.12: Wi-Fi/4G drops and docking failures for one connection problem tied to a release.

Manual driving drops at close range

This is the most widely reported case, and no one has a fix.

• A LUBA 3 3000 owner on firmware 2.3.27.0 says Bluetooth and the video feed disconnect after a while³. Support asked for a log file and a screen recording³.
• A LUBA 2 owner on firmware 1.30.29.8 says the Bluetooth range has been shrinking until it falters in manual mode while they stand beside the mower⁵.
• One owner is cut off at about 15 ft, with strong Bluetooth in sight⁶.
• A LUBA 2 owner on firmware 1.11.511.575 and iOS 18 saw delayed control from 3 ft away, and restarting the app seemed to help⁷.
• Another owner says manual mowing quits on a weak Bluetooth signal unless they walk directly behind the mower, not beside it⁸.

Mammotion's LUBA 2 AWD X manual gives one figure: while mapping, keep the controller within 1.5 m (4.9 ft) of the robot to maintain a stable connection¹⁰. Mammotion gives no Bluetooth range for driving, and no support reply names a cause or a known bug.

What is not known

• Which firmware, if any, fixed a Bluetooth problem. No owner reports one.
• Whether the close-range drops come from the phone, the app, the mower's radio or the update. Reports span the LUBA 2 and LUBA 3.
• Whether the full power-off works beyond the two cases above.

If yours is not covered here, send us a public report with your model, firmware and app version, and what you tried.