MowerWatch › Guides

Automower keeps stopping with no error code — the STOP/hatch clue

The most maddening Automower fault: the mower is stopped in the lawn, the app just says “stopped”, and there's no error code to Google. Here's the key fact, straight from Husqvarna's own API: no remote command produces the STOPPED state. If your mower reports STOPPED, something physically activated the STOP circuit — the big red button, or the hatch switch underneath it.

Since nobody's standing in your lawn pressing the button, a recurring no-code stop usually means the hatch switch circuit is triggering on its own: a worn or moisture-affected switch that opens with vibration, heat, or a bump.

How to narrow it down

1. Rule out humans first — family members, curious neighbours, children (and note that a docking bump is also a vibration event, so stops that cluster at the station can still be the hatch switch).
2. Open the hatch fully and close it firmly; check the hinge for play and the seal for debris.
3. Press and release the STOP button a few times — it should return crisply, not stick.
4. Track when the stops happen. Wet mornings? Rough sections of lawn? Right after docking? Clustering is the evidence a dealer can act on — bring the timestamps.
5. The fix is a dealer-fitted switch assembly; it's a known repair on well-used machines.

A real case: a 430X kept stopping with no code; the dealer quoted €149 just to look. The stop timestamps and states from the API identified a faulty STOP/hatch circuit without the mower leaving the garden.