Changing speed triggers blade jam 1202

[MichaelSordje]

The problem

Changing the working speed in Home Assistant corrupts the current saved mowing task.

The task was created in the Mammotion app with:

• Working speed: 0.4 m/s
• Cutting height: 60 mm

Home Assistant displays different values:

• number.luba_arbeitsgeschwindigkeit: 0.2 m/s
• number.luba_schnitthohe: 0
• Cutting-height limits: 20–65 mm
• sensor.luba_schnitthohe: 60 mm

I changed number.luba_arbeitsgeschwindigkeit from 0.2 to 0.3 m/s.

Afterwards, “Continue task” no longer starts the mower. The Mammotion app reports:

Cutting disc blocked (1202)

The cutting disc is physically free. The task worked before changing the setting in Home Assistant.

Steps to reproduce

1. Create a saved task in the Mammotion app:
   • Working speed: 0.4 m/s
   • Cutting height: 60 mm
2. Start it through button.luba_mahen.
3. Pause the mowing task.
4. Change number.luba_arbeitsgeschwindigkeit from 0.2 to 0.3 m/s.
5. Select “Continue task”.
6. The mower does not resume and reports error 1202.

Expected behavior

Changing the working speed should update only the speed.

Home Assistant should not overwrite other parameters with stale or invalid values such as a cutting height of 0.

The entities should also reflect the active saved-task settings from the mower.

Suspected cause

The working_speed entity calls async_modify_plan_if_mowing().

This rebuilds and sends the complete GenerateRouteInformation structure using coordinator.operation_settings.

Saved tasks are started using only their task ID. Their current parameters apparently are not copied into operation_settings.

Therefore, changing only the speed may also resend:

blade_height: 0

This likely causes the false cutting-disc error 1202.

Possible fixes:

• Synchronize operation_settings with the active saved task.
• Transfer only the changed parameter.
• Never send a cutting height outside the device limits.
• Prevent live modification when the active task settings are unknown.

Environment

• Device: LUBA mini AWD 360 LIDAR 1500
• Home Assistant: 2026.8.2
• Mammotion integration: 0.6.4
• PyMammotion: 0.8.14
• Task created in the official Mammotion app
• Task started through button.luba_mahen

Related issues

• Cutting height out of range #529
• Desire to improve the reliability of zone-based configuration commands (height, obstacles, random angle) #599
• Task settings #478

What Mammotion device are you using?

Luba mini AWD LiDAR

What version of the Mammotion integration are you using?

v0.6.4

What version of Home Assistant Core are you running?

core-2026.8.2

[mikey0000]

Thanks for the report, can you send me your diagnostic file please, your correct ive not accounted for users changing the blade height on tasks, will address that

[MichaelSordje]

Attached is a sanitized diagnostic file.

Please note that the diagnostic was downloaded later and currently contains a different task ("Nur Rand") with 0.4 m/s and 50 mm.

During the reported incident, I changed only the working speed in Home Assistant from 0.2 to 0.3 m/s. I did not change the blade height. Home Assistant displayed the blade-height number entity as 0, while the blade-height sensor reported the correct task value.

mammotion-diagnostics-redacted.zip