Map: Mowed area & Paths not visible after mower is in docking station for loading

[Twix121212]

What happened?

Hi,

mowing area is not visible after mower is docked and loading (mowing session is still not completed)

IMO the mowed area shoulb be visible until the whole session is done and finished. Because like it is now, you can only see the mowed session until the mower returns to station for loading.

Also if you resume session the mowed area&paths are still no more visible.

But the area which was mowed after resume is visible...

So we would have to stick both together - area before reloading and after ist to have the whole picture (like in the app).

BR matthias

Integration version

1.34.0

Home Assistant version

2026.7.2

Mower model and firmware version

No response

Diagnostics

No response

Relevant log output

[it-rec]

This is sadly how their firmware works. The only reason that it works in the app is that it caches this. This is not what HA standarts want. But I can see if I can build this into the card itself.

Will check. Thank you for the detailed analsis and the helpful images. Thanks!

[Twix121212]

Installed the new version today...this is how it looks like during a loading pause....

Is it supposed to be like that?

[it-rec]

Yes — that is exactly how it is supposed to look now. 🎉 Your screenshots show the fix working: the mowed area and the session paths stay on the card while the mower sits in the station for a loading pause (before v1.44.0 they vanished the moment it docked).

Two things that are intentionally different from the app, so they don't look like bugs:

• Orientation: the card renders the map in the device's own coordinate frame; the app applies its own display rotation. You can rotate the card with a two-finger gesture (the compass button resets it).
• Colors: mowed coverage is the darker green fill + the path lines (the collapsible legend on the card explains each element); the app paints it turquoise.

We also put this through a full live test today on another device — job interrupted by a low battery, recharge dock in between, then the job was ended manually in the app: the coverage and session values survived the recharge dock the whole time, and only ended (and reset) when the job was actually over. One extra finding from that test worth knowing: the vendor app can show 100 % / all zones green even when a zone was never mowed — the card deliberately shows the device's real counters instead, so when the app and the card disagree, the card is the honest one. 😄

Thanks for verifying on your setup and reporting back with screenshots — much appreciated! 🙌

[Twix121212]

Thx for clarification but one question....

So the mowed area is now shown in HA via a green border....(light green lines is the mowed area)

But the mower also worked in this area =>

So should this in HA not look like this =>

Or do you mean that maybe the mower was never in this area?

[it-rec]

Good catch — and your suspicion goes the right way, just in the other direction: the mower almost certainly was in that area. 🙂

What you're seeing is a restart gap: you installed the update today, in the middle of that (rainy, multi-leg) job — and updating the integration restarts Home Assistant. The card accumulates the session's coverage in memory as the mower reports each leg, but the device itself only (re)sends the current leg's path. So everything mowed before the restart is simply no longer available locally — while the app shows it from its own long-term cache. The area your arrow points at was mowed in a leg before the update.

On my own map today — same kind of job (recharge pause in the middle), but no restart while it ran — the card looks exactly like your third picture: the whole worked area covered.

You've found a real limitation though, so I've opened #239 to persist the session paths across restarts. Once that ships, an update or reboot mid-job won't lose the picture anymore. Thanks for the sharp eyes and the perfect illustration of the case! 🙌

[Twix121212]

Ahhh perfect - many thanks for your hard work and it was exactly what you wrote...i installed the update in the middle of a mowing session and of course restarted.