Tested, and seem to be working as expected! 
There exist yet one edge case, which might not be picked up by the app? You can first ”pause” the mowing session, then ”end” it rather than resuming. The statuses would go like this:
Again, I will absolutely survive without this, but let me know if you change anything and want me to verify!
I saw that the latest version included a fix for paused to idle state. Tested, and reported ”mowing completed” correctly in app/trigger! 
I think there might be an issue with the error message/description being sent in the tag whenever the mower encounters an error. Regardless of what error my mower encounters (bumper, disk rotation failed, …) the error description tag always reports “normal operation”. See below flow and outcome, compared to dreame app outcome/notification.
The mower doesn’t update dock status to undocked , or mower is running . Only battery procent works . Mova 1000
The mower is running at print Screen
I would recommend you to remove your email address from your post. Note that this is a public forum, so everything you share in a reply is visible to anyone
Thanks for the detailed report! The trigger firing correctly is good to confirm — the wrong description is a separate issue.
The app reads the error code from the cloud API, but it seems the API returns it under a different field name for your device than what we currently check. I’ve expanded the lookup in v1.1.12 to cover more field name variants. The app will also write a diagnostic log entry every time an error is detected — it will look something like this in the Homey developer log:
[error] faultCode=23 — info keys: did, uid, model, latestStatus, deviceCode, …
Could you install v1.1.12 ( MOVA & Dreame Mower | Homey), trigger a mower error, and then open the Debug Console in the app settings and copy the [error] log line and send the Diagnostic Report? That will tell me exactly which field the API uses on your device and I can make sure the description is resolved correctly going forward.
Could you please send me the “Raw JSON” from your mower while it’s docked and while ist mowing (under app settings)?
Will do! Just noticed that the ”bumper error” does not actually trigger an homey error state, which makes this somewhat harder to test. But I will force the mower through a pile of pine cones, and it will surely lock up a disk 
will get back when I have more info to share.
Bumper error state in Dreame app, and this is state in Homey:
Thanks for testing this thoroughly! Two things to pass along:
Bumper error / “Paused” in Homey — confirmed. The mower reports a bumper collision as paused + fault code rather than as the error state, so Homey was showing “Paused” instead of “Error”. v1.1.14 fixes this: the app now detects that combination and promotes it to an error state. The “Mower error occurred” trigger should now fire correctly on bumper hits.
“Poll failed: Invalid Capability: mow_spot” — also fixed in v1.1.14. The debug poll now handles any invalid capability gracefully and completes the snapshot. Please try “Poll Now” again after updating.
Can you update to v1.1.14 once it’s available and test the bumper scenario again? The app will also write a [diag] line to the debug log for every paused/error state — if the error description still shows “Normal operation” after the update, please share that log line so we can identify the exact fault code field name your device is using.
