
Software bug continues to be an issue
On the Luba 2 models, this issue continues to be present for over a year at least. The issue is when the Luba “gets stuck” and you press continue working… the robot is physically “stuck”/located at the pause symbol. The software recognizes that… but it thinks it’s mowed a lot more than it has because it wasn’t moving.
As shown in the picture here… the Luba was mowing the perimeter first. You can see the white line on the perimeter disappeared or “mowed” further ahead than the Luba got “stuck”. This has been an ongoing issue I’ve posted before. I own multiple Lubas and this is an issue on all of them.