Mowed area sometimes not possible after Battery Load

[Twix121212]

What happened?

Hi,

i have still the problem, that sometimes after a charging pause, that the mowed area is not visible any more. I had no HA restart....

I made a new Bug because its a new App-Version. Hope it is ok.

App

HA

Its curious because during the last mowing stint (to complete the session), i can see the area which was mowed before (during second run after first battery load pause)...

So whats missing is the area which was mowed during the first run (as you can see 92% is done....so something is missing)

Edit:

And when job is done, you can see - only the mowed area from the last run is visible....nad nothing from before.

Integration version

1.62.0

Home Assistant version

2026.7.4

Mower model and firmware version

S1200

Diagnostics

No response

Relevant log output

[Twix121212]

I checked it once again.....look...

First run - all good

Battery charging after first run - all good

After charging – run two starts - all good

And in the middle of run two…the already mowed area disappeared

And a few seconds later you can see, that an additional area disappeared...(compared to the picture before)

And after finishing the job:

No HA restart - nothing....

[it-rec]

Please check in the latest release

[Twix121212]

Hi,

man thanks - Udpdate is done and i started a new mowing job....but the map does not delete the old mowed area from the last job. There are still some "mowed areas" from the last rund visible:

But i will check that once again today when my actual job is done - i will start a new one to be on the safe side.

[Twix121212]

Sorry to say that but its still not solved:

Version: 1.69.0

after first battery charging pause

And after finishing the job:

[it-rec]

Thanks for sticking with this through two rounds of "please check the latest release" that did not hold. Both of the things you reported turned out to be real and separate defects, and neither was actually fixed by what I shipped before.

The mowed area vanishing mid-job — your original report and the 27 July screenshots, where a patch disappeared and then another one seconds later. The archive of finished mow tracks was flooding: any in-place rewrite of the current path counted as "points lost", so the whole cached track was re-archived on every push. The archive filled with duplicates of the current leg until its point budget evicted the ground that had been mowed first. Patch by patch, exactly as you documented. Fixed in v1.70.0.

The previous job's area still showing — your 2 August comment. After a job completes, the firmware keeps serving that job's final leg as the current path. The next job's first payload replaced it after the new session had already latched, so the old leg was archived and drawn as ground the new job had mowed. Also v1.70.0.

The phantom lines reported alongside this in #332 came from the same saturated archive. Compaction had no limit on how far it could coarsen a track — the tolerance doubled from 25 mm to 1.6 m, and it compounded because it re-simplifies already-simplified points. Every track ended up a straight line across the lawn. v1.71.0 caps that at 200 mm and drops the oldest tracks whole instead.

Before you test

Neither fix repairs an archive that is already damaged. The stored segments survive a restart, so straight after updating you may still be looking at the old state — that is history being redrawn, not the bug recurring. The track archive is cleared when the next mowing session starts, so one full job should be enough. For the accumulated mowed area, clearing the auto-mode progress in the app resets it.

If it still happens — one honest caveat

The point budget still exists. If the archive genuinely fills up, the oldest coverage is still dropped, deliberately: the alternative is drawing lines through lawn nobody mowed. But with the flooding fixed it should not come anywhere near that budget on a normal lawn.

So if the area still vanishes, that is a real signal that the flooding is not fully fixed, and worth saying out loud rather than living with. If you can, note whether it disappears gradually — a patch at a time, like before — or all at once. Those point at different causes.

Leaving this open until you have run a full job on v1.71.0. Your screenshots are what made this findable in the first place, so thank you for that.

[Twix121212]

Looking good...first try and it worked :) Will check it during another mowing session and will give you feedback to be on the safe side that this is done!

GREAT WORK!