v0.9.0-beta.2 — mower's own path, plus the US sign-in fix

Beta, for testers. Same as v0.9.0-beta.1 (the mower's own path on the map), plus the fix from v0.8.2:

• US accounts can sign in again (#29, fixed by @vahesoo in #30). If Home Assistant asked you to re-authenticate, update, restart, then enter your password once.

What to try and report is in the v0.9.0-beta.1 notes.

Changes since v0.9.0-beta.1: v0.9.0-beta.1...v0.9.0-beta.2

v0.8.2 — US accounts can sign in again

US accounts can sign in again

Since around October 20, accounts in the US region could neither renew their session nor sign in again: every attempt was refused with "The current app version is too low" (#29).

It was not the app version. The first US sign-in server the integration tried refuses every time, and that refusal was taken as final instead of trying the next server. The server the official app uses is now asked first. Found and fixed by @vahesoo (#30), confirmed by a US user. Other regions are unchanged.

If Home Assistant asked you to re-authenticate: update, restart, then enter your password again once.

Full changelog: v0.8.1...v0.8.2

v0.9.0-beta.1 — the mower's own path on the map (beta)

Beta, for testers. Everyone else stays on v0.8.1: HACS does not offer pre-releases unless you turn them on for this integration.

The mower's own path on the map

Until now the map rebuilt the mowed trail from the mower's position every few seconds. That leaves stripes between passes, draws its trips along the channels, and cannot know where the blade stopped (#15).

@vahesoo found that the cloud keeps the path the mower actually drove, zone by zone, with a flag that looks like the blade state. Where that path is available, this beta draws it instead, leaves out the stretches where the blade was stopped, and adds the newest positions on top so the map stays live.

Two new switches in Configure, both on:

• Draw the mower's own path (beta) — off brings back the old trail.
• Leave out where the blade was stopped (beta) — the blade flag is not confirmed yet. If you see gaps where the mower did cut, turn this one off.

zstandard is now a requirement (Home Assistant installs it), as some systems lack the decoder this needs.

How to try it

In HACS, open Navimow (Private), enable beta versions for it if v0.9.0-beta.1 is not listed, and download v0.9.0-beta.1. Restart Home Assistant.

What helps most, in #15: a screenshot of the HA map next to the app's after a mow, and a diagnostics file. path_status in it shows whether the path was read, with counts only (no coordinates).

Changes since v0.8.1: v0.8.1...v0.9.0-beta.1

v0.8.1 — commands are confirmed

Commands are confirmed

Start (a new mow), Pause and Dock now wait a few seconds for the mower itself to answer, instead of trusting that the cloud accepted them. Before, a command the mower ignored looked exactly like one it carried out: the button returned at once and nothing happened.

If the mower does not answer, you get an error saying so. The command may still be carried out, so keep clear of the mower until it has visibly stopped or docked. Resume is sent without waiting, since a mower with nothing to resume need not answer.

Found and measured on an H800 by @tampiss (#16, #17). Not tried on other models yet — if Start, Pause or Dock now report an error while the mower obeys, please say so in #17.

Full changelog: v0.8.0...v0.8.1

v0.8.0 — why the mower came home, and German

Why did the mower come home?

A new Last message sensor shows the newest entry of the app's message centre: why the mower went back to the dock, a fault, a rain hold. Its time, body, code and the last ten messages are attributes, so an automation can tell "battery low" from "done". It is checked now and then, and for a few minutes after the mower heads home, docks or stops on a fault. Asked for by @LievenBoes, with the source found by @vahesoo (#28).

This is new and has only been seen on a few models. If the sensor stays unknown on yours, please say so in #28 with a diagnostics file.

The Coverage sensor also carries the raw end-of-session code (last_end_code, and end_code per zone). What the numbers mean is not known yet.

German

The integration and both cards are now in German, thanks to @boerni (#19).

Full changelog: v0.7.7...v0.8.0

v0.7.7 — Start carries on with an unfinished job

Start carries on with an unfinished job

With the mower back in its dock and the job half done — after rain, for instance — Start began the job again from 0 %, while the app's Mow now carries on with it (reported by @daha24, #26). Start now continues the job when the mower is docked, the job is between 1 and 99 %, and no zones are picked. Picking zones still starts a new job on those zones.

No old trail on zones at 0 %

A zone the mower reports at 0 % could still be drawn as mowed, with a trail kept from an earlier version or an earlier job. Such a zone now shows only what has been mowed in the current job.

Not tried on a real mower — please say in #26 if Start does something unexpected.

Full changelog: v0.7.6...v0.7.7

v0.7.6 — the rain delay in the right hours

Rain delay shows the right number of hours

The rain delay was read wrongly for most values: 6 hours showed as 4.5, and 8, 9 and 10 hours as 5, 6 and 7. The mower reports it in hexadecimal, and it was read as decimal. Found by @jurassicparkicecream, with a full table of every step (#24). Setting it from Home Assistant was already correct.

Full changelog: v0.7.5...v0.7.6

v0.7.5 — zone mowing on the H800 and H1500

Zone mowing on the H800 and H1500

Picking zones and pressing Start (or calling navimow_pro.mow with zones) did nothing on an H800 or H1500, while "all zones" worked. These mowers ignore a zone mow that asks for a particular order. They are now sent the zones you pick without one, and mow them in an order of their own choosing.

Found on an H800 by @tampiss (#16), confirmed and tested on an H1500 by @gjuncu (#25). Other models are unchanged. If you have an H500 or H3000 and zone mowing does nothing, say so in #25 and it will be added.

Full changelog: v0.7.4...v0.7.5

v0.7.4 — no more stripes in a zone being mowed

No more stripes in a zone being mowed

A zone in progress showed thin unmowed stripes between passes, where the app shows solid mowed grass (reported by @deividas619 in #15). The mower's passes overlap by only a couple of centimetres, and the trail is rebuilt from the mower's position every few seconds, so at exactly the blade's width small errors left gaps.

The trail is now drawn a little wider than the blade (1.3×). It is still cut off at the zone edges, so it does not spill over a boundary.

Full changelog: v0.7.3...v0.7.4

v0.7.3 — sliders stay where you put them

Sliders stay where you put them

After changing the cutting height (or any other slider), it jumped back to the old value and only later showed the new one — the cloud keeps reporting the old value for a little while after a change. Reported by @deividas619, who also confirmed that the cutting height works both ways on an i220 LiDAR.

The value you set is now shown until the mower reports it, for up to 30 seconds. If the mower never takes it, the slider goes back to the real value (and for the cutting height you still get the notification). If the mower refuses the change — while mowing, for instance — the slider goes back at once.

Full changelog: v0.7.2...v0.7.3