Mammotion LUBA stuck or offline: the documented troubleshooting tree

Read the LED before you read anything else

The single most useful diagnostic Mammotion publishes for the LUBA 3 AWD 3000 is the LED indicator table in section 2.2 of the LUBA 3 AWD Series user manual. It puts five distinct conditions behind one signal. A slow blinking red side LED means the STOP button is activated, or the battery is low, or the robot is stuck, or the security key is not properly installed, or the robot has been lifted, tilted or flipped over. A fast blinking red side LED means something else entirely: a robot system malfunction, or a failed system update. A side LED that is off means the robot is turned off, sleeping, has the side LED disabled in the app, or is in manual control mode but currently inactive.

That grouping matters because owners search for stuck when the machine is actually reporting a lifted or tilted state, or a security key that is not seated. Mammotion's own separate remedy for a Wi-Fi failure, published in its knowledge base, is to power the robot off, unplug the key on the rear, plug it back into the slot and power on, which is the same key that the LED table flags when it is not properly installed. If a LUBA is slow blinking red and refuses commands, checking the key is a two-second test that clears one of the five listed causes.

Two more LED tables in the same manual section decide whether the fault is in the robot at all. On the charging station, blinking green means the robot is docked, solid green means it is not in the station, solid red means charging station malfunction, and off means no power supply. On the RTK reference station, blinking green means initializing, solid green means the positioning mode is Antenna over Datalink and functioning well, solid blue means Antenna over Internet and functioning well, blinking blue means a firmware update is in progress, solid red means a malfunction, and off means either no power supply or that the local time is between 18:00 and 08:00. That last line is the one that saves a support ticket: an unlit reference station in the evening is documented behaviour, not a failure.

• Slow blinking red side LED: STOP pressed, low battery, robot stuck, security key not properly installed, or robot lifted, tilted or flipped over.
• Fast blinking red side LED: robot system malfunction or failed system update.
• Charging station: blinking green docked, solid green not docked, solid red station malfunction, off no power.
• RTK reference station: solid green Antenna over Datalink working, solid blue Antenna over Internet working, blinking green initializing, solid red malfunction.
• RTK reference station LED off between 18:00 and 08:00 local time is published as normal, not a fault.

Offline: which radio is actually down

A LUBA carries several independent links, and Mammotion publishes a separate fix for each, so offline is not one fault. The LUBA 3 AWD 3000 is published in our spec record with 4G, Bluetooth and Wi-Fi, a built-in 4G module, three years of free 4G service and lifetime free iNavi NetRTK service. The manual adds a fourth path used only for corrections: the LoRa datalink between the reference station and the robot.

For Bluetooth, Mammotion's published sequence is to power the robot off, unplug the security key and plug it back in, power on, then restart the app and try again. On Android it tells owners to open Settings and Bluetooth settings with the robot powered on and check whether a connection name containing Luba appears. On iOS it says a third-party tool is needed, names BLE Scanner from the App Store, and has owners filter for Luba to confirm the robot is advertising at all. For Wi-Fi, the article opens with the constraint that causes most of these tickets: Luba only supports the 2.4 GHz Wi-Fi connection, so a router that merges 2.4 GHz and 5 GHz under one name is the first thing to check. The published fix is the same key cycle, and the article suggests driving the robot near the router for firmware updates.

The 4G branch is where the record thins out. Mammotion's article titled How to Fix 4G Network Connection Issues is a YouTube embed with no written steps on the support page, so there is no text procedure to quote. What the manual does document is the setup path: the built-in SIM card is activated during robot linking, or afterwards by tapping the Status Bar on the Home page, then the 4G status button, then Activate. It also states that if you are using 4G mobile data you can skip Wi-Fi setup, but that connecting to Wi-Fi is recommended for optimal performance, and that your phone should be within 3 m (10 ft) of the robot during setup.

• Bluetooth: key cycle, restart the app, confirm the robot advertises (Android Bluetooth settings, or BLE Scanner filtered on Luba for iOS).
• Wi-Fi: 2.4 GHz only. Same key cycle. Drive the robot near the router for firmware work.
• 4G: activation via Status Bar, 4G status button, Activate. Mammotion's 4G troubleshooting article is video only.
• Setup proximity: keep the phone within 3 m (10 ft) of the robot.
• LoRa datalink: a separate correction path, diagnosed from the reference station LED, not from the app connection state.

Lost positioning is not the same as offline

Mammotion publishes four positioning states in the app under POS, and they define what the machine is allowed to do. Fix is fine positioning, accuracy less than 10 cm and up to 2 cm in a good open-sky area, and is the only state in which the robot can auto mow. Float is bad positioning at roughly 50 to 200 cm and cannot auto mow. Single is meter-level and cannot auto mow. None is no positioning at all. A LUBA that is connected to the app, answering commands and still refusing to start a task is usually sitting in Float, not offline.

The same article explains the counter that owners misread. It publishes three satellite figures: satellites the robot can see, satellites the reference station can see, and co-viewing satellites, which it defines as the number used when doing the RTK calculation. Its stated benchmark is that more than 20 satellites on both L1 and L2 co-viewed is good for stable RTK positioning. It then warns explicitly that signal quality shown as WEAK or BAD can leave the robot in Float or Single even with more than 20 co-viewed satellites, because trees, leaves, walls and fences degrade the signal from a satellite the receiver can still nominally see. Counting satellites is not the test; quality plus co-viewing is.

The placement numbers behind all of this are published in two places that do not agree, and we are not going to average them. The LUBA 3 AWD Series user manual (V3.0, 2026-06) says to maintain a distance of at least 3 m (10 ft) between the RTK reference station and any wall or tree, and to keep no obstacles within 1.5 m (4.9 ft) to the left, right and front of the charging station, a clearance the manual's earlier V1.0 revision gave as 1 m (3.3 ft). Mammotion's older LUBA knowledge-base troubleshooting article says to set the reference station in an open-sky area with no coverages within 5 m at least, or simply to mount it on a wall or roof. A separate knowledge-base article gives the geometric version: the distance from the reference station to walls, roof or trees should ideally be angled 45 degrees from the base to the height of those obstructions. A third states the whole-lawn requirement plainly, that Luba needs continuous signals from both the reference station and the satellites during the job and needs at least a 90 degree open-sky view, while adding that a fully unobstructed line of sight to the station is not required because the radio transmission works as long as the path is not fully obstructed.

• Fix: under 10 cm, up to 2 cm in open sky. The only state that permits auto mowing.
• Float (about 50 to 200 cm), Single (meter-level) and None: auto mowing is blocked.
• Co-viewing satellites above 20 on both L1 and L2 is Mammotion's published benchmark for stable RTK.
• WEAK or BAD signal quality can hold the robot in Float even above that satellite count.
• Reference station clearance: at least 3 m (10 ft) from walls and trees (LUBA 3 manual) versus no coverage within at least 5 m (LUBA knowledge base).
• Charging station clearance: no obstacles within 1.5 m (4.9 ft) left, right and front (V3.0 manual; 1 m in the earlier V1.0).
• Minimum sky view for the robot: 90 degrees.

Three positioning modes, three different failure modes

Section 5.5 of the LUBA 3 AWD Series user manual documents three positioning modes, switched under Status Bar and Positioning Mode, and each fails differently. Antenna over Datalink has the reference station send corrections straight to the robot over a dedicated low-latency LoRa signal, which Mammotion describes as the most stable, lowest latency and fastest correction path, recommended where there is a clear line of sight or minimal obstruction between station and robot and the robot stays inside LoRa range. Antenna over Internet routes the same corrections over the internet to extend operational range, recommended for large or complex lawns and for lawns with strong stable Wi-Fi coverage at both ends. iNavi NetRTK takes corrections from a remote cloud service over 4G with no local reference station at all, recommended where there is no suitable place to install a station and 4G coverage is stable.

The manual publishes range figures for the first two on AU and NA models of the 3000 and 5000: Net 5 km (3.1 mi) and Datalink 120 m (394 ft). Those two numbers explain a common pattern. A LUBA that holds Fix near the house and drops to Float at the far fence on Datalink mode has a distance problem, not a sky problem, and the published remedy is the mode switch rather than a station move.

One documentation conflict is worth stating plainly rather than smoothing over. Our spec record has the LUBA 3 AWD 3000 published on the US product page as Tri-Fusion navigation using NetRTK via the iNavi service, with no base station or wire. The LUBA 3 AWD Series user manual configuration table lists an RTK Reference Station in the box for AU and NA models of the 3000, 3000H, 5000 and 5000H, and only EU and UK models of those variants as robot plus charging station. Both statements are Mammotion's. The practical consequence for troubleshooting is that a US owner should check which hardware is actually in the yard before deciding whether the reference station LED table applies at all.

On the previous generation, the LUBA 2 AWD 3000HX is published with wire-free RTK GNSS plus UltraSense AI Vision and an included RTK300 reference station, so the station-based branch always applies. Mammotion's knowledge-base answer to whether LUBA 2 can continue to work when losing the RTK signal is that it will be able to continue work, and that the uninterrupted workflow is guaranteed by the complementary combination of 3D Vision and RTK. That is a claim about continuing to mow, not about maintaining Fix accuracy, and Mammotion publishes no duration or accuracy figure alongside it.

• Antenna over Datalink: LoRa, published range 120 m (394 ft) on AU and NA 3000 and 5000 models.
• Antenna over Internet: same station, corrections over the internet, published range Net 5 km (3.1 mi).
• iNavi NetRTK: cloud corrections over 4G, no local station.
• Moving the reference station after mapping requires deleting the map and remapping, unless it is reinstalled in its original position.

Physically trapped: the limits Mammotion publishes

When a LUBA is genuinely wedged rather than lost, the numbers that decide the outcome are in section 9.1 of the manual. The Standard version publishes a vertical obstacle passing ability of 50 mm (2 in) and the H version 80 mm (3.2 in), which is the height of step or root edge the machine is rated to climb. Maximum slope inside the task area is published as 80 percent (38.6 degrees), matching the 80 percent maximum climbing ability in our spec record, but maximum slope at the edge is published separately and much lower, at 40 percent (21.8 degrees). A boundary that runs across a bank steeper than that is outside the published envelope even on a machine rated to 80 percent inside the work area.

Traction is the other half. The manual's pre-mowing guidance states that mowing in the rain can make the grass stick on the robot and cause slipping, and that the robot should not be operated in standing water or during heavy rain. The rain sensor is documented to stop mowing and return the robot to the charging station automatically when rain is detected, enabled under Settings and Rain Protection. A LUBA that gets stuck repeatedly in one spot after wet weather is a traction case, and the published lever is scheduling rather than a setting change.

For places the machine keeps snagging, Mammotion documents two opposite map tools and they are easy to confuse. A no-go zone is an area the robot avoids completely, recommended for low flowerbeds especially below 20 cm (7.8 in), water edges without a clear boundary, transparent objects such as mosquito nets or glass doors, small low obstacles such as clotheslines, tent ropes or water pipes, pet houses, delicate plants and irrigation equipment. An Obstacle-Free Zone (named the no-stop zone in earlier manual revisions) does the reverse: it turns off obstacle avoidance while the robot is transiting to a task area or returning to charge, and Mammotion describes it as useful for complex but safe areas where the robot may otherwise get stuck, naming lawn areas that may be mistakenly recognized as invalid due to seasonal changes and areas with low, safe obstacles. Obstacle detection sensitivity is separately adjustable under Mow, Settings and Obstacle Detection Mode, with Sensitive increasing sensitivity to both standard obstacles and non-grassy areas such as pavement and gravel, Standard as the recommended default, and Off documented for use only in specific controlled environments.

To recover a trapped machine, the LUBA 3 control table documents a double-press to unlock only the robot after an emergency stop. Mammotion's separate unlock article, illustrated with a YUKA, says to press the Grass button and then START to continue work and unlock, or the Auto-return button and then START to send it back to the charging station.

• Vertical obstacle passing: 50 mm (2 in) Standard version, 80 mm (3.2 in) H version.
• Maximum slope inside the task area 80 percent (38.6 degrees); maximum slope at the edge 40 percent (21.8 degrees).
• Do not operate in standing water or heavy rain; wet grass sticks and causes slipping.
• No-go zone: the robot never enters. Obstacle-Free Zone: obstacle avoidance is disabled while transiting, for safe but complex ground.
• Obstacle Detection Mode: Sensitive, Standard (recommended default), or Off.

Blade disc jams and the contacts that stop a charge

A jammed cutting disc reads as stuck. Mammotion's published cleaning procedure for the LUBA 3 has the robot fully powered off, turned upside down on a soft clean surface with care not to press on the LiDAR module, then the cutting disc and the cutting blade guard removed and cleaned thoroughly, with a brush and never a sharp object. It warns against a high-pressure washer or solvents, and against leaving the robot inverted after washing, because water can leak into the motor. The LUBA 3 control table also documents a double-press that fully lowers the cutting disc for cleaning, which is the intended way to get at it.

On the blades themselves, Mammotion publishes a replacement interval of every 3 months or after 150 hours of use, more often in thicker grass, and states that the hub motor has an expected lifespan of 1500 hours of operation. Its warnings are specific: always wear protective gloves, never use an electric screwdriver on the cutting disc, replace all blades and their screws at the same time, never reuse the screws, and confirm after installation that every blade rotates freely. It also notes that wet grass is more likely to stick to the blades and the bottom of the robot, which impairs performance and forces more frequent cleaning.

One Mammotion maintenance item is easy to miss because it is published as a video in the LUBA 2 AWD X maintenance section rather than as a written procedure. Titled Boost Cutting Efficiency: Washer Removal and Screw Check, its published summary asks whether you are getting the clean cut you expect or noticing grass piling up around the blades, and says the tweak is to remove the washers between the blades and check that all screws are tight. Grass piling up around the blades is the state that precedes a disc jam, so it belongs in this branch even though it is filed under maintenance.

The other silent failure is charging. The manual instructs regular cleaning of the rear charging pads and infrared receiver with a cloth to remove grass clippings and dirt, and states directly that keeping these parts clean prevents charging failures. On the charging station side it has you unplug first, then clean the infrared transmitter and the charging contact with a brush and cloth. A robot that keeps returning and failing to take a charge is checked here before anything is replaced. If yours is not making it back to the dock at all, our guide to robot mowers that will not return to the dock covers that branch across brands.

Where the record has gaps

Four things are worth flagging so nothing here reads as more complete than it is. First, the sourcing. Mammotion's LUBA 3 AWD section of its support portal contains user manuals in a dozen languages and one bumper installation video, and nothing else. There is no LUBA 3 troubleshooting category. Every text troubleshooting article we could read sits under LUBA 1 AWD, LUBA 2 AWD or YUKA mini, and several are marked as updated a year ago. The positioning-state and satellite-count article, the poor positioning article, the Bluetooth and Wi-Fi articles and the working-condition article are all filed under LUBA 1 AWD. They are Mammotion's own documentation, but LUBA 3 owners are reading guidance written for earlier hardware.

Second, the manual's version history. Mammotion's portal serves the LUBA 3 AWD Series user manual as version 3.0, dated 2026-06, behind a document viewer that resists a plain download; we first read the same document at version 1.0, dated 12/2025, on a European Mammotion distributor's site, and subsequently obtained and re-verified the official V3.0 text. The figures above are quoted from V3.0. Two things changed between the revisions we read: the charging station clearance grew from 1 m to 1.5 m, and the no-stop zone was renamed the Obstacle-Free Zone. If your machine shipped with an older printed manual, its figures may match V1.0.

Third, several branches simply have no published text. The 4G troubleshooting article is a video with no written steps. There is no published error-code list for LUBA at all, no equivalent of the numbered codes other makers publish, so a fault that does not map onto one of the LED states or positioning states has no documented name. And no Mammotion document we found publishes a recovery behaviour for a stuck robot: there is no stated escape routine, no timeout, no figure for how long the machine tries before it stops and alarms.

Fourth, none of the placement numbers come with a curve. Mammotion publishes a 90 degree minimum sky view, a 20 satellite co-viewing benchmark, a 3 m station clearance in the manual and a 5 m one in the knowledge base, but no relationship between any of them and the accuracy you get, no time-to-reacquire figure, and no success rate for any step. Every article in this set ends the same way, with instructions to upload logs from the app and send photographs of the installation to Mammotion aftersales, which is where this guide stops too. For the same diagnosis on Segway hardware, see Navimow lost satellite signal; if the symptom is patchy coverage rather than a stop, see robot mower leaving uncut strips.