Thanks a lot — seems to be a bug. The app writes the cutting height as part of a full settings block. Its layout was worked out on MOVA mowers and has never been verified on the A1, so on your mower changing the height can overwrite the mowing direction too.
You could help me fix this quickly. I need two log snapshots, one before and one after a change:
Before: Open the app settings in Homey → “App Logs”, copy everything and save it as “before”. Please also note the current cutting height and mowing direction shown in the Dreame app.
Change: In the Dreame app, change the cutting height and the mowing direction to clearly different values (e.g. height 35 → 50 mm, direction 0° → 90°) and note the new values.
Wait about 2 minutes so Homey can poll the new settings.
After: Go back to “App Logs” (reload if needed), copy everything again and save it as “after”.
Please send me both files together with the values before and after (a private message is fine). Comparing them shows exactly where the A1 stores each setting, so I can map them correctly. Afterwards you can set your preferred values again in the Dreame app.
Would anyone know if and how the message “Rain detected” shows?
I’m trying to automate the scheduled moving, after the weather conditions, and need to know if the mower stops due to rain, recharge or because it’s actually finished
Hi DeBossDK, thanks for the idea — it’s in the new test version 1.1.42, published now: MOVA & Dreame Mower | Homey
What’s new:
New trigger “Mowing interrupted”. It fires when the mower stops or returns early because of rain, frost, do-not-disturb or low battery.
“Mower returning to dock” and “Mower docked at station” now carry the reason as tokens:
Interruption type: rain, frost, do_not_disturb, low_battery, or none if the run wasn’t interrupted
Interruption reason: the text, e.g. “Scheduled task interrupted — rain”
Interruption code: the mower’s code (54–62)
“Mowing completed” no longer fires when a run was interrupted, so a rain stop is no longer reported as “finished”.
Example flow: When mower docked at station → And the interruption type token is rain (logic card “text is equal to”) → Then resume later or skip today’s schedule.
One thing I couldn’t test myself: if your MOVA 600 reports the rain reason only after it has docked, the dock card will still say none and the reason only comes through “Mowing interrupted”. So for rain I’d build the flow on “Mowing interrupted” directly.
Update: Well - The grass isn’t exactly growing wildly here in Denmark with 5 degree celcius
But it started today after 8 days of accumulation growth.
The “Completed” trigger still fires every time it returns to charge.
Now I have tried to use the new “interupted” trigger, and funny enough - it triggers for rain, even though I have set the app to ignore rain. (might be default text- but I’ll let you know.)
I have set in plenty logs to get every trigger from them now.
So - give me a little more time to test, and I’ll return with some usefull facts about what happens.
Hi again..
I think this was my final chance to test, since we will now have sub-zero degrees in the night (Mover moves inside for the winter).
My conclusion so far is, the “Completed” fires every time the mover returns.
I get great triggers from “Interrupted” when the moved decides to go back or is stuck etc, and the the “Completed” fires when it reaches the dock.
My best solution right now is to listen to “Completed” and check that battery level is above 15-20% - this should mean it’s done moving. (but it has obvious challenges naturally).
I CAN of course listen to the “Interrupted”, and start a countdown - leaving the mover eg. 5minutes to return to dock, where “completed” will fire, and then compare - But I think the battery level is equally good here..
Thanks a lot for you involvement - I’d happily continue this at spring..
Just for information; I have build a “Grass Growth” homey script - using amount of sun, temp, rain and moist to hourly calculate a number. This is accumulated and when it reaches a certain level, the mover is triggered.. I works quite well now, and I’m really excited to see how great it works in spring/summer-time..
thanks a lot for testing until the very end of the season, and for the clear description. That helped me find a bug.
“Mowing completed” was not supposed to fire after “Mowing interrupted”. The cause: if the mower briefly reported “mowing” again on its way home, the app forgot the interruption reason, so the dock looked like a normal finish. This is fixed in 1.1.44, now available as a test version. The reason is now kept until a genuinely new run starts.
Two notes:
“Mowing interrupted” covers rain, frost, do-not-disturb and low battery. Being stuck is reported as an error (“Mower error occurred”), so in that case “Completed” can still fire once the mower is home.
Instead of checking the battery level, you can use “Mower docked at station” and its Interruption type token: anything other than none means the run didn’t finish.
In spring it would help a lot if you could send me a diagnostic report right after a run where “Completed” fires when it shouldn’t. The log now records exactly when and why.
Your grass-growth script sounds great. I’d love to hear how it works in summer. Have a great weekend and a good winter!
