External integration - Mammotion

Thanks Chris75 for the tests and screenshots
Fixes in 1.1.2

1. The map that disappears and then comes back

The Gladys Camera widget takes each new value from the device for the image.
The map was on the mower device: with each new value (battery, status, progress…), the image was replaced by this value, so no map until the next image.
The map is now a separate device: « Luba-VPMBS8RA – Map ».

2. « No image » from time to time

Gladys no longer displays an image older than one hour.
At the base, the mower doesn’t move, so no new image: after one hour, the widget was empty.
The image is now sent at least every 45 minutes.

3. « Return to base » after stopping mowing

When you turn off Mowing, Gladys puts the mower on pause. But the integration was waiting for the mower to confirm the pause.
If you pressed Return to Base right after, it thought the mower was still mowing: simple return, without Stop. The task remained on pause.
Now the pause is taken into account immediately: Return to Base sends Stop then Return, like the app.
And if the mower is already at the base with a task on pause, Return to Base sends only Stop.
If it comes back, can you send me the log? A new line shows what Gladys sent, for example: dock = 1 -> stopAndDock (work mode 19).

4. Zone order

Zones are now mowed in the order you turn on the switches, like in the app.
To change the order: turn off the zones, then turn them back on in the desired order.
The order is kept even after a restart of the integration.
In a scene: turn on the « Zone to mow – … » switches in the desired order, then Mowing.

After the update

  • Discovery tab → Update on the mower (the old map is removed from the mower).
  • Still in Discovery, add the new device « Luba-VPMBS8RA – Map ».
  • On the dashboard, in the Camera widget, choose this new device instead of the mower.

@cicoub13 for info: the Camera widget (updateDeviceStateWebsocket in Camera.jsx) takes any new state of the device for the image, regardless of the function. A camera that has other functions (battery, status…) therefore loses its image with each new value. A filter on the camera/image function would fix this.

V 1.1.2

  • the « image of the zones » device displays correctly and is refreshed properly
  • the order of the zones works
  • however, the « return to base » still does not send the STOP
    You have to go to the mammotion app to stop the task
    LOG
2026-10-06T13:55:49.275Z] [INFO] [mammotion] Sending "start" to Luba-VPMBS8RA
[2026-10-06T13:55:53.299Z] [INFO] [mammotion-mqtt] Luba-VPMBS8RA: route settings seen {"subCmd":2,"edgeMode":0,"knifeHeight":60,"channelWidth":27,"ultraWave":0,"channelMode":0,"toward":69,"speed":0.6,"zones":1,"reserved":[11,10,10,10,11,18,20,40],"towardMode":1,"towardIncludedAngle":0}
[2026-10-06T13:56:40.345Z] [INFO] onSetValue <- ext:ext-prohand-gladys-mammotion:mower:nNlJJBp0Cxx538To70i6000000:dock = 1
[2026-10-06T13:56:40.345Z] [INFO] Luba-VPMBS8RA: dock = 1 -> dock (work mode 13)
[2026-10-06T13:56:40.345Z] [INFO] [mammotion] Sending "dock" to Luba-VPMBS8RA
[2026-10-06T13:59:08.789Z] [INFO] onSetValue <- ext:ext-prohand-gladys-mammotion:mower:nNlJJBp0Cxx538To70i6000000:dock = 0
[2026-10-06T13:59:08.789Z] [INFO] Luba-VPMBS8RA: dock = 0 -> cancelDock (work mode 14)
[2026-10-06T13:59:08.789Z] [INFO] [mammotion] Sending "cancelDock" to Luba-VPMBS8RA
[2026-10-06T13:59:21.459Z] [INFO] onSetValue <- ext:ext-prohand-gladys-mammotion:mower:nNlJJBp0Cxx538To70i6000000:refresh = 1
[2026-10-06T13:59:21.459Z] [INFO] Luba-VPMBS8RA: refresh = 1 -> refresh (work mode 19)

Thanks for the feedback and the log, it clearly shows the issue :+1:

In your test, you pressed Return to Base during mowing, without a pause before (dock = 1 -> dock (work mode 13)). The 1.1.2 fix only covered the case of « mowing on pause ». While mowing, Gladys sent a simple Return, and the mower kept the task on pause.

In the next version, Return to Base will send Stop then Return as soon as a task is in progress, whether it is mowing or on pause. In the log, you should see: dock = 1 -> stopAndDock (work mode 13).

Note: Return to Base always ends the task. It no longer resumes after recharging.

Oops, I think I explained it wrong and we misunderstood each other, because it’s more complicated!

Here’s how the mammotion app works:

Then if you press « pause », the buttons (case 1) « recharge » and (case 2) « stop » and « resume mowing » are displayed

Case 1 >> If you press button 1 « recharge », the robot returns to the base to recharge and displays the buttons « stop » (cancels mowing) and « resume mowing »


Case 2 >> If you press button 2 « stop », the robot stops mowing but stays in place! You then need to press the « recharge » button for it to return to the base and recharge

Good luck, Claude!!

Thanks, that’s clear! The next version follows the app:

Return to base = « Recharge »: the mower returns, the task remains on pause, Mowing resumes it.
New Stop task button = « Stop »: the task is finished, the mower stays in place. Return to base then brings it back.

After the update: Discovery → Update on the mower to see the new button.

Available in 1.1.4

Fix en cours, merci fix: only display the image feature string states in the camera widget by cicoub13 · Pull Request #3173 · GladysAssistant/Gladys · GitHub

That’s perfect for me: everything works correctly and it suits me perfectly

Thanks