# External integration - Mammotion **URL:** \ **Category:** Développement\ **Tags:** integration-externe\ **Created:** [September 27, 2026, 6:30pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915 "2026-09-27T18:30:52Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [September 27, 2026, 6:30pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/1 "2026-09-27T18:30:53Z")
Hello, Here is a new external integration that will soon be available on the store to manage your Mammotion lawn mowers: > **[GitHub - prohand/gladys-mammotion: Gladys external integration to connect Mammotion...](https://github.com/prohand/gladys-mammotion)** > > Gladys external integration to connect Mammotion in Gladys Assistant ---
**Author:** ![Chris75](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/6a8cbe/32.png) [@Chris75](https://community.gladysassistant.com/u/Chris75)\ **Post date:** [September 29, 2026, 10:35am UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/2 "2026-09-29T10:35:31Z")
I just installed this integration and it’s not working I did create a 2nd mammotion account to avoid disconnections ![Screenshot 2026-09-29 122920](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/2/3/238846f7d0be3cb73f45a5c19e9d5f4e81a0ac23.png) I’ll put the log in the next message ---
**Author:** ![Chris75](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/6a8cbe/32.png) [@Chris75](https://community.gladysassistant.com/u/Chris75)\ **Post date:** [September 29, 2026, 10:37am UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/3 "2026-09-29T10:37:07Z")
```auto [2026-09-29T09:46:08.275Z] [INFO] Starting the Mammotion integration... [2026-09-29T09:46:08.490Z] [INFO] [gladys-sdk] connected to Gladys (http://) [2026-09-29T10:25:10.406Z] [INFO] onConfigUpdated -> new configuration received [2026-09-29T10:25:10.622Z] [INFO] [mammotion] Logged in to the Mammotion cloud [2026-09-29T10:25:15.441Z] [INFO] 1 mower(s) found on the Mammotion account [2026-09-29T10:25:15.452Z] [ERROR] Mammotion initialization failed GladysApiError: devices[0].poll_frequency: invalid poll frequency at HttpClient.request (/app/node_modules/@gladysassistant/integration-sdk/lib/http-client.js:49:13) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async refreshMowers (file:///app/index.js:68:3) at async initialize (file:///app/index.js:110:20) at async file:///app/index.js:202:3 at async GladysIntegration._runHandler (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1590:7) at async GladysIntegration._handleMessage (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1430:9) { status: 400, code: 'BAD_REQUEST' } [2026-09-29T10:25:19.213Z] [INFO] 1 mower(s) found on the Mammotion account [2026-09-29T10:28:41.138Z] [INFO] onConfigUpdated -> new configuration received [2026-09-29T10:28:42.406Z] [INFO] 1 mower(s) found on the Mammotion account [2026-09-29T10:28:42.415Z] [ERROR] Mammotion initialization failed GladysApiError: devices[0].poll_frequency: invalid poll frequency at HttpClient.request (/app/node_modules/@gladysassistant/integration-sdk/lib/http-client.js:49:13) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async refreshMowers (file:///app/index.js:68:3) at async initialize (file:///app/index.js:110:20) at async file:///app/index.js:202:3 at async GladysIntegration._runHandler (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1590:7) at async GladysIntegration._handleMessage (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1430:9) { status: 400, code: 'BAD_REQUEST' } [2026-09-29T10:28:54.595Z] [INFO] 1 mower(s) found on the Mammotion account [2026-09-29T10:33:43.443Z] [INFO] 1 mower(s) found on the Mammotion account [2026-09-29T10:33:43.453Z] [ERROR] Mammotion initialization failed GladysApiError: devices[0].poll_frequency: invalid poll frequency at HttpClient.request (/app/node_modules/@gladysassistant/integration-sdk/lib/http-client.js:49:13) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async refreshMowers (file:///app/index.js:68:3) at async initialize (file:///app/index.js:110:20) { status: 400, code: 'BAD_REQUEST' } ``` ---
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [September 29, 2026, 3:20pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/4 "2026-09-29T15:20:40Z")
It’s available in 1.0.1 😉 : **Cause** - Gladys only accepts a few fixed values for `poll_frequency`, in **milliseconds** : 1000, 2000, 10000, 15000, 30000, or 60000. I checked this in Gladys’s source code. - The integration sent the user-set interval in **seconds** (e.g., `60`). Gladys therefore responded with « 400 invalid poll frequency. » - This error stopped the startup on every attempt, hence the repeated errors in the logs. **Fix** - `src/devices/mower.js`: The mower is now sent to Gladys with `30000` ms if the interval is under 60 s, otherwise `60000` ms. - `index.js`: As Gladys polls at most every 60 s, the integration ignores requests that arrive before the chosen interval. A 5 s margin absorbs small Gladys delays. - The setting in the configuration screen doesn’t change: still from 30 to 3600 s, 60 s by default. ---
**Author:** ![Chris75](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/6a8cbe/32.png) [@Chris75](https://community.gladysassistant.com/u/Chris75)\ **Post date:** [September 29, 2026, 4:21pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/5 "2026-09-29T16:21:49Z")
still having a small issue: ![Screenshot 2026-09-29 181957](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/8/1/812fca0533cd090d2675d685ef7a108fe46e3de2.png) LOG ```auto [2026-09-29T16:17:25.356Z] [INFO] Starting the Mammotion integration... [2026-09-29T16:17:25.573Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80) [2026-09-29T16:17:26.212Z] [INFO] [mammotion] Logged in to the Mammotion cloud [2026-09-29T16:17:32.304Z] [INFO] 1 mower(s) found on the Mammotion account [2026-09-29T16:17:32.415Z] [WARN] First poll failed for Luba-VPMBS8RA: user device not bind [2026-09-29T16:20:26.253Z] [INFO] 1 mower(s) found on the Mammotion account ``` ---
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [September 29, 2026, 4:39pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/6 "2026-09-29T16:39:59Z")
Correction published in the new version 1.0.2 😉 ---
**Author:** ![Chris75](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/6a8cbe/32.png) [@Chris75](https://community.gladysassistant.com/u/Chris75)\ **Post date:** [September 30, 2026, 4:45pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/7 "2026-09-30T16:45:08Z")
Well, it doesn’t work: the robot is detected but none of the states work ![Screenshot 2026-09-30 184351](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/1/0/1029ed0fa2dd5c12a7a44dfb5f7a3fe3396acfe6.png) ![Screenshot 2026-09-30 184403](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/7/2/72553fcaa378a92f082413a059a466e6ec13cc61.png) ![Screenshot 2026-09-30 184131](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/2/5/25fc938d8cad3457922b50268cca52e18050420d.png) ---
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [September 30, 2026, 5:20pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/8 "2026-09-30T17:20:32Z")
Could you please test with the new version 1.0.4? If you still encounter bugs, don’t hesitate to include the logs as well, which can be very helpful 😉 **The cause** - The message `user device not bind` comes from Aliyun, the old cloud of Mammotion. - Your Luba is indeed found on the Mammotion account, but it is not linked to Aliyun. However, the integration only read the status from Aliyun, so no value was received. - Recent accounts and firmware use the **Mammotion MQTT server**. There, the mower itself sends its status (battery, state, cutting height, counters). There is no on-demand reading. **The fix** - New file src/mammotion/mqtt.js: it connects to the Mammotion MQTT server, follows each mower, and keeps its latest values. - Upon discovery, a mower absent from Aliyun is marked to use MQTT. - If Aliyun responds with « not bind », the integration also switches to MQTT. - Received values are sent to Gladys immediately, at most once every 15 seconds per mower. - Mowing and Return to Base commands only go through the Mammotion API for these mowers. - Lint, format, and tests pass (52 tests, including 6 new ones). **What you should know** - Values arrive when the mower publishes them, not at startup. There may still be « No recent value » for a few minutes. - Your Luba is an older model. I’m not sure if it sends these status messages without being asked. - If nothing arrives, the next step would be to ask it for its status reports and decode them. This is more complex to code. ---
**Author:** ![Chris75](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/6a8cbe/32.png) [@Chris75](https://community.gladysassistant.com/u/Chris75)\ **Post date:** [October 1, 2026, 2:42pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/9 "2026-10-01T14:42:00Z")
It’s still not working ![Screenshot 2026-10-01 163556](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/3/d/3deb0bd6c8c9bf1726c029abbbd9484d2305d4bb.png) ![Screenshot 2026-10-01 163932](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/6/f/6f4b3367457032ae907ea543176e069c3489d983.png) Logs: ```auto [2026-09-30T20:00:40.238Z] [INFO] Starting the Mammotion integration... [2026-09-30T20:00:40.439Z] [INFO] [gladys-sdk] connected to Gladys [2026-09-30T20:00:40.739Z] [INFO] [mammotion] Logged in to the Mammotion cloud [2026-09-30T20:00:45.731Z] [INFO] 1 mower(s) found on the Mammotion account [2026-09-30T20:00:46.245Z] [INFO] [mammotion-mqtt] Connected to the Mammotion broker mqtt-eu.mammotion.com [2026-09-30T20:00:46.304Z] [INFO] [mammotion-mqtt] Following Luba-VPMBS8RA on the Mammotion broker [2026-09-30T20:01:16.125Z] [INFO] 1 mower(s) found on the Mammotion account [2026-10-01T14:35:37.820Z] [INFO] 1 mower(s) found on the Mammotion account [2026-10-01T14:36:34.624Z] [INFO] onSetValue <- ext:ext-prohand-gladys-mammotion:mower:nNlJJBp0Cxx538To70i6000000:dock = 1 [2026-10-01T14:36:34.626Z] [INFO] [mammotion] Sending "dock" to Luba-VPMBS8RA [2026-10-01T14:36:44.989Z] [WARN] Refresh after command failed for Luba-VPMBS8RA: states[0]: must have a numeric "state" or a string "text" ``` ---
**Author:** ![Chris75](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/6a8cbe/32.png) [@Chris75](https://community.gladysassistant.com/u/Chris75)\ **Post date:** [October 1, 2026, 2:44pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/10 "2026-10-01T14:44:35Z")
It would be great if other people could test it, because I feel like my model (Luba 2), which is from March 2025, is already too old!! @JKBS64 ---
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [October 1, 2026, 2:59pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/11 "2026-10-01T14:59:34Z")
Thanks for the logs Can you test with the new version 1.0.5 please 🙂 **The cause** - The mower’s « Status » text was sent to Gladys in the wrong place: in the form `state: { text: "..." }`. - Gladys expects the text in a separate `text` field, like `text: "..."`. - Gladys then refuses the entire submission, not just that line. This is the error `states[0]: must have a numeric "state" or a string "text"` in your logs. - Result: no value is recorded. Hence « No recent value » and « No value recorded » on all lines. **What I changed** - src/devices/mower.js: the status is now sent in the `text` field. ---
**Author:** ![Chris75](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/6a8cbe/32.png) [@Chris75](https://community.gladysassistant.com/u/Chris75)\ **Post date:** [October 1, 2026, 4:27pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/12 "2026-10-01T16:27:44Z")
There you go, the robot connected successfully and retrieved the information after 1 hour! ![Screenshot 2026-10-01 180552](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/c/f/cf0e7e5c12cacb18000444ff741715663ce6e5f5.png) So the 2 buttons don’t do anything, unfortunately, and the information takes a very long time to retrieve ![Screenshot 2026-10-01 172248](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/5/5/555a61bb888db0e0c2042a944b2ea5f1e0b211ee.png) Log ```auto [2026-10-01T15:22:16.622Z] [INFO] Starting the Mammotion integration... [2026-10-01T15:22:16.825Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80) [2026-10-01T15:22:17.155Z] [INFO] [mammotion] Logged in to the Mammotion cloud [2026-10-01T15:22:21.985Z] [INFO] 1 mower(s) found on the Mammotion account [2026-10-01T15:22:22.526Z] [INFO] [mammotion-mqtt] Connected to the Mammotion broker mqtt-eu.mammotion.com [2026-10-01T15:22:22.581Z] [INFO] [mammotion-mqtt] Following Luba-VPMBS8RA on the Mammotion broker [2026-10-01T15:22:40.572Z] [INFO] 1 mower(s) found on the Mammotion account [2026-10-01T16:02:24.996Z] [INFO] onSetValue <- ext:ext-prohand-gladys-mammotion:mower:nNlJJBp0Cxx538To70i6000000:mowing = 1 [2026-10-01T16:02:24.998Z] [INFO] [mammotion] Sending "start" to Luba-VPMBS8RA [2026-10-01T16:04:09.610Z] [INFO] onSetValue <- ext:ext-prohand-gladys-mammotion:mower:nNlJJBp0Cxx538To70i6000000:dock = 1 [2026-10-01T16:04:09.611Z] [INFO] [mammotion] Sending "dock" to Luba-VPMBS8RA [2026-10-01T16:06:29.162Z] [INFO] onSetValue <- ext:ext-prohand-gladys-mammotion:mower:nNlJJBp0Cxx538To70i6000000:dock = 1 [2026-10-01T16:06:29.163Z] [INFO] [mammotion] Sending "dock" to Luba-VPMBS8RA ``` ---
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [October 1, 2026, 5:18pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/13 "2026-10-01T17:18:46Z")
It’s fixed in version 1.0.6 **1. Mow / Return to Base commands did nothing** - **Cause:** the command was sent to the wrong robot card. Except for the Luba 1, all mowers (including your Luba-VP) wait for these commands on their « navigation » card. We were sending them to the main card. - **Why no errors in the logs:** the cloud accepted the command and transmitted it, then the mower ignored it without saying anything. - **Fix:** the command is sent to the correct card, with the same rule as PyMammotion (the library used by Home Assistant). **2. Information took about 1 hour to arrive** - **Cause:** we were waiting for the mower to send its status on its own, which it rarely does. - **Fix:** with each update, the integration asks the mower for its status, just like the Mammotion app does. The response arrives in a few seconds and Gladys is updated for the status, battery, and cutting height. - Total mowing time and total distance remain on the old schedule (they change little). - The **Refresh** button and the update 10 seconds after a command also make this request. ---
**Author:** ![Chris75](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/6a8cbe/32.png) [@Chris75](https://community.gladysassistant.com/u/Chris75)\ **Post date:** [October 2, 2026, 1:48pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/14 "2026-10-02T13:48:19Z")
Well, it’s not conclusive: - the « return to base » button works, but the mammotion app keeps disconnecting and reconnecting - the « mowing » button does nothing, but it crashes the mammotion app… The info still isn’t coming through I specify that I do have 2 different mammotion accounts I’d really like someone to test on another model! Also, will there be other functions/info available? because the goal is to replace the mammotion app, like the external integration « Dreame » which allows you to use only gladys, and all the changes made on gladys appear very quickly on the dreame app Log: ```auto [2026-10-02T13:25:32.777Z] [INFO] Starting the Mammotion integration... [2026-10-02T13:25:33.065Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80) [2026-10-02T13:25:33.400Z] [INFO] [mammotion] Logged in to the Mammotion cloud [2026-10-02T13:25:38.161Z] [INFO] 1 mower(s) found on the Mammotion account [2026-10-02T13:25:38.796Z] [INFO] [mammotion-mqtt] Connected to the Mammotion broker mqtt-eu.mammotion.com [2026-10-02T13:25:38.830Z] [INFO] [mammotion-mqtt] Following Luba-VPMBS8RA on the Mammotion broker [2026-10-02T13:33:35.019Z] [INFO] onSetValue <- ext:ext-prohand-gladys-mammotion:mower:nNlJJBp0Cxx538To70i6000000:dock = 1 [2026-10-02T13:33:35.021Z] [INFO] [mammotion] Sending "dock" to Luba-VPMBS8RA [2026-10-02T13:33:53.821Z] [WARN] [mammotion] Report request refused for Luba-VPMBS8RA: Device not responding [2026-10-02T13:37:18.218Z] [INFO] onSetValue <- ext:ext-prohand-gladys-mammotion:mower:nNlJJBp0Cxx538To70i6000000:mowing = 1 [2026-10-02T13:37:18.219Z] [INFO] [mammotion] Sending "start" to Luba-VPMBS8RA ``` ---
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [October 2, 2026, 2:09pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/15 "2026-10-02T14:09:32Z")
Indeed, it would be great if someone else could test, but I still sent your prompt to Claude: **What was happening, according to your logs** (I compared with PyMammotion, the code used by Home Assistant): - **Information not being received** : the mower only listens to the cloud ~10 seconds after a « sync » message. We never sent it, so it ignored our requests: that’s the « Device not responding » in the log. - **App disconnecting constantly** : every 60 seconds, we requested a report from the mower. Each request replaced the app’s request, which then thought the mower was lost. Additionally, it exceeded the Mammotion cloud quota (around 600 messages per 12 hours). - **Mowing crashing the app** : we sent a simple « start » without a route. The app, however, first prepares a route on the map (zones, settings). **What I changed:** - A « sync » is sent before each command and each report request. - A report request is sent at most every 5 minutes, and only right after a command or a click on « Refresh ». No request is sent when the mower is already sending its data, for example when the app is open. - **Mow button** : it **resumes** only a paused mow. If no task is paused, Gladys refuses (with a message in the logs) instead of crashing the app. A new mow is therefore still started from the app. - New information: - progress in the status, for example « Mowing (45 %) »; - remaining mowing time (min); - more reliable « Charging »; - total time and total distance read from the mower. - Clearer logs: « First data received from … » when data arrives, and a warning if the server refuses the subscription. It’s available in 1.0.7 ---
**Author:** ![Chris75](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/6a8cbe/32.png) [@Chris75](https://community.gladysassistant.com/u/Chris75)\ **Post date:** [October 2, 2026, 2:25pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/16 "2026-10-02T14:25:47Z")
I admit I don’t see the point of this integration anymore, since it can only pause/resume! Not even a mow it can’t start! Is it my model at fault or is it the mammotion API that doesn’t allow it? ---
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [October 2, 2026, 2:27pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/17 "2026-10-02T14:27:52Z")
You can start mowing here: ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/f/3/f37e5cdc7b2a44c0c0046e8e0dc9f9682515fc4d.png) Maybe the button isn’t appropriate Have you tried the latest version I deployed (1.0.7)? ---
**Author:** ![Chris75](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/6a8cbe/32.png) [@Chris75](https://community.gladysassistant.com/u/Chris75)\ **Post date:** [October 2, 2026, 2:39pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/18 "2026-10-02T14:39:13Z")
Yes! And the « mow » button crashes my Mammotion app and disconnects the robot Note: I don’t have a « refresh » button and I had to change the refresh time in the config, which was still set to 60, replaced by 300 ![Screenshot 2026-10-02 163754](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/1/4/14bcea8fe78c3d782c8679de164c9837b10c6cf6.png) ![Screenshot 2026-10-02 163714](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/8/c/8c3b343d43d5c5ea184ebe61da6b2aefe332d7d2.png) Log: ```auto [2026-10-02T14:28:59.403Z] [INFO] Starting the Mammotion integration... [2026-10-02T14:28:59.623Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80) [2026-10-02T14:28:59.921Z] [INFO] [mammotion] Logged in to the Mammotion cloud [2026-10-02T14:29:05.132Z] [INFO] 1 mower(s) found on the Mammotion account [2026-10-02T14:29:05.792Z] [INFO] [mammotion-mqtt] Connected to the Mammotion broker mqtt-eu.mammotion.com [2026-10-02T14:29:05.826Z] [INFO] [mammotion-mqtt] Following Luba-VPMBS8RA on the Mammotion broker [2026-10-02T14:29:05.947Z] [INFO] [mammotion-mqtt] First data received from Luba-VPMBS8RA (device_protobuf_msg_event) [2026-10-02T14:30:34.618Z] [INFO] onConfigUpdated -> new configuration received [2026-10-02T14:30:36.022Z] [INFO] 1 mower(s) found on the Mammotion account [2026-10-02T14:30:38.200Z] [INFO] 1 mower(s) found on the Mammotion account [2026-10-02T14:32:39.644Z] [INFO] onSetValue <- ext:ext-prohand-gladys-mammotion:mower:nNlJJBp0Cxx538To70i6000000:mowing = 1 [2026-10-02T14:32:39.644Z] [WARN] Luba-VPMBS8RA: No paused job to resume: start a new job from the Mammotion app [2026-10-02T14:37:05.631Z] [INFO] 1 mower(s) found on the Mammotion account ``` ---
**Author:** ![JKBS64](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/jkbs64/32/22723_2.png) [@JKBS64](https://community.gladysassistant.com/u/JKBS64)\ **Post date:** [October 2, 2026, 2:40pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/19 "2026-10-02T14:40:50Z")
Hello, yes I will test this weekend, my model is a Yuka mini. I’ll keep you posted. ---
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [October 2, 2026, 2:54pm UTC](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/20 "2026-10-02T14:54:47Z")
Thanks for the feedback! In 1.0.8: - the **Mow** button now starts a real mow when the mower is ready: it resumes an interrupted mow, otherwise it prepares a route across all zones on the map (like Home Assistant), then starts; - a rejected command no longer sends anything to the mower: that’s what was causing the Mammotion app to disconnect; - new **Refresh** button on the dashboard (click on « Update » in the Discovery tab to get it); - remaining time goes to 0 when not mowing; - recommended interval: 300 s. To choose a single zone, you still need to go through the app. If mowing doesn’t start, send me the logs: they indicate the zones found and the step that’s blocking. [Next page](https://community.gladysassistant.com/t/integration-externe-mammotion/10915.md?page=2)