How to write a robot mower fault report that support can use

Sources awaiting check

Give support a short account of what the mower does, where it happens and what has changed. Clear observations can prevent a lengthy exchange of guesses.

Identify the complete installation

Record model, relevant accessories and software version. Note whether the system uses a wire, satellite positioning or another documented arrangement. Include the installation date and who carried it out.

Keep account and access credentials private. Supply serial details only through the provider's appropriate support channel, rather than posting them unnecessarily in a public discussion.

Describe one failure at a time

Write the exact message, approximate time and location. Say whether the mower stopped, failed to dock or behaved differently from its usual route. Attach a simple sketch and safe photographs.

Husqvarna UK: robotic mower FAQ illustrates how terrain, passages and positioning can vary by model. Those details are useful context; they are not enough to diagnose your installation remotely.

Record what preceded the fault

Include moved furniture, garden work, changed boundaries, maintenance or software changes. Explain any checks already performed under the manual or support instructions.

Avoid repeatedly resetting the device or deleting its map before support asks. You may remove information needed to understand the problem or create additional setup work.

Stop unsafe operation

If a fault affects boundary control, cutting safety or the safety of people and animals, stop the mower and follow the manufacturer's safe isolation instructions. Do not continue unattended use to collect a longer video.

Keep the resolution

Save the case number, advice and work completed. Ask whether the installation needs rechecking before the normal schedule resumes.

A good fault report ends with a clear question: what should be inspected next, who should do it and what operating restrictions apply meanwhile? That is more useful than an unexplained collection of screenshots.

Sources