[APP][Pro] Mammotion

Apps
,
1

Control your Mammotion robot mower Tags:robot-mower, bluetooth, homey-pro

Mammotion brings your Luba 2 or Luba 3 robot lawn mower into Homey. Start, pause, stop, or send it back to the dock, adjust blade height and cutting speed on the fly, and keep an eye on everything from battery level to RTK positioning accuracy — all from your device tile or a Flow.

It’s a ground-up TypeScript port, not a Python wrapper — pure Node.js, fully native to the Homey SDK.

Features

Control

  • Start / pause / stop / send to dock
  • Adjustable blade height and cutting speed (Low / Medium / High)
  • Headlamp, side LED and rain protection toggles

Sensors

  • Battery level, charge cycles, blade wear
  • Mowed area and progress, mowing speed, elapsed/remaining time
  • WiFi and Bluetooth signal strength
  • GPS satellite count and RTK positioning accuracy (No Fix / GNSS / Float / RTK Fixed)
  • Connection type (shows whether you’re on Bluetooth or cloud right now)

Flow cards

  • Triggers: mower started mowing, mower docked, mower reported an error, battery below X%
  • Conditions: is mowing, battery above X%, GPS signal good
  • Actions: start mowing (with blade height/speed/edge options), dock, pause, stop, set blade speed, set rain protection, read stored schedule

Dual transport Connects over the cloud by default and switches to a direct Bluetooth connection automatically when your mower is in range — faster, more local control with cloud as the reliable fallback. You can also force Bluetooth-only or cloud-only from the device settings.

Getting started

  1. Install the app from the Homey App Store: https://homey.app/a/net.tornbloms.mammotion
  2. Use a second Mammotion account for pairing. Mammotion’s mobile app logs you out of the account currently used by an external integration, so don’t use your daily-driver account. Share your mower(s) to a second account from the Mammotion app first, then pair that account in Homey.
  3. Add the device — Homey will list every mower (owned or shared) visible to that account.

If your account credentials change later, use the device’s Repair flow instead of deleting and re-adding it — your Flows and Insights history stay intact.

Screenshots

(attach a couple of screenshots here: the device tile, the mobile/timeline view, and a Flow example)

Links

Feedback welcome

This is an actively developed app — Bluetooth reliability in particular is still being tuned across different Homey hub models, so diagnostic reports are genuinely useful if something doesn’t work as expected. Feel free to post here or open a GitHub issue.

Acknowledgements

This app builds on reverse-engineering work already done by the community:

  • mikey0000/Mammotion-HA — the Home Assistant integration and its pymammotionlibrary are the primary reference for the protocol layer (cloud auth, MQTT, protobuf messages, Bluetooth framing). Large parts of this app are a direct TypeScript port of that work.
  • Lindhardsen/homey-mammotion — an independent, parallel Homey integration that helped confirm protocol details during development.
  • DNAngelX/ioBroker.mammotion — its product-key reference table helped catch a real command-routing bug in this app.

Thanks to all three for the groundwork.

2

The downloadlink doesn’t work for me.

3

Still awating for approval. You can use the test version

4

I have really been waiting for this app! Thanks for developing it.

I followed your guide; created a new account, shared from my default account, logged in with the newly created account in the app and accepted the mower.
But when logging in with the newly created account in Homey there is not any shared devices and the account is not saved in the app.

Please advice.

5

Please provide diagnostics from Homey. You might also try this newly created test version, Mammotion | Homey. I assessed both your version and the new one using my primary and secondary accounts, and they function correctly.

6

02f9609a-6728-4c5e-8b2c-07b54f2bd33f

Maybe I am using wrong user? Should it be the email adress of the second account?

7

Same here.

Have Luba2

No device found.

The connection to the account works, because it log me out from the mobile App.

Screenshot_20260703-082423_Homey
Screenshot_20260703-082423_Homey2560×1600 119 KB

8

I have a Yuka 2000 that worked without problems to add. It didnt want to use BLE it seam probably range. Mqtt seam to be working to get data over.

9

This is why you need a second account. Create a new user and invite it, accept your mower and use the new second account

10

Yes Anders you should after you have invited and accepted the secondary account use this account in the app.

11

I know, I mentioned it only that Homey logged to the account. My problem isn’t the logging and Logout. The problem is that the main account or the shared account in homey doesn’t see any Luba device.

12

I am using the second account.
It works fine in the Mammotion Android app but not in Homey, see my report above.

13

Plese test this version Mammotion | Homey as it has more logging. and send me a diagnostics

14

6f744960-4c6b-4e97-9864-b7d65d39bb55

15

The API provides no devices—have you confirmed device sharing acceptance in your secondary account? I’ve incorporated logic to approve this automatically in the current test version: https://homey.app/a/net.tornbloms.mammotion/test/

16

Yes I did accept both mowers using the secondary account. Logging in with the secondary account in the Android app I see both mowers.

I will retest with your new test version.

17

a0d9c4cf-430a-41eb-9e91-84b5bdf7e226

Still no devices

18

b9f2c3ba-6e48-4f64-b34b-73b532078b65

19

Go ahead and try 2.4.0. I now implemented the legacy API as well. Mammotion | Homey

Please provide feedback and diagnostics as we can develop this together

20

34b136be-9060-46f5-a17b-adf0bdf99013