Integrate your Mammotion robotic lawn mower into Home Assistant: control, sensors, automations

A robotic lawn mower Mammotion is a bit like an autonomous colleague: as long as you let it work on its own via the official application, everything runs smoothly… until the day you want to impose real rules of life on it. Not going out when rain is threatening, avoiding operation when children are playing in the garden, taking advantage of a peak in solar production, or synchronizing mowing with the family schedule. This is exactly what Home Assistant allows: transforming the LUBA or the YUKA into a full-fledged smart device, with usable sensors, commands accessible everywhere, and especially automations that save time (and avoid some cold sweats). Today I suggest you discover how to integrate your Mammotion robotic lawn mower into Home Assistant so that mowing finally fits into your home… instead of being locked in an app.

What the Mammotion integration actually brings

The interest lies in bringing mowing out of the “application silo.” Once the LUBA or the YUKA is in Home Assistant, the robot becomes a smart device like any other: you retrieve sensors (battery, status, GPS, satellites, working area, connection type…) and you trigger actions (start, pause, stop, return to base/dock).

The result: your scenarios can finally make the right decisions in place of the robot (or in addition). A typical example: you cut short a mowing session if rain approaches, avoid the hottest hours, take advantage of a surplus solar slot, or prevent mowing when children are playing outside… in short, something tangible, not a gadget.

Prerequisites before starting

First, check that your Home Assistant is up to date: the integration requires a minimum version of Home Assistant 2025.3.0.

You also need HACS (Home Assistant Community Store), since we are installing a community integration here… and it’s not in the “default” HACS catalog; you need to add it as a custom repository.

Last important point: it is highly recommended to create a second Mammotion account dedicated to Home Assistant. Otherwise, by logging in with the main account, you risk being disconnected from the mobile app, which can quickly become annoying :)

Step 1: create a second Mammotion account

Open the Mammotion app and create a new account (another email is sufficient). Then, log back into your main account, go to device sharing to share your robot to this second account. Finally, log back into the second account and accept the share: this is the “secondary” account you will only use in Home Assistant.

Yes, it’s a bit “administrative”… but it avoids headaches later (and messages like “why does my app disconnect on its own?!”).

Step 2: install the Mammotion integration via HACS

In Home Assistant, open HACS, then go to Integrations. In the menu (the three dots in the upper right corner), open Custom repositories and add the repository https://github.com/mikey0000/Mammotion-HA by choosing the category Integration.

Then search for “Mammotion” in HACS, install the integration, and then restart Home Assistant.

Step 3: add the integration in Home Assistant

After the restart, go to Settings → Devices and Services → Add an integration, search for “Mammotion,” and then start the configuration.

At this stage, two concepts really matter:

• First, the connection. The integration supports Bluetooth (BLE) and Wi-Fi (including via SIM 4G, depending on the models), with a roadmap focused on control, scheduling, zones, etc.
• Next, if you go for Bluetooth and your Home Assistant is far from the robot, a Bluetooth Proxy ESPHome can be very useful (a small ESP32 placed in the right spot, and Home Assistant “extends” its BLE range).

Here we will go for a Wifi connection, which is simpler since the entire garden is perfectly covered.

Just enter the email address and password of the second Mammotion account created:

Step 4: check the entities and sensors reported

Once the integration is in place, you should see your robot appear with commands and several sensors. Here I am retrieving my Luba Mini AWD Lidar recently tested. As for useful information, we typically find battery level, status (mowing, charging, idle…), connection type, GPS position, number of satellites, working area, etc.

Step 5: start mowing from Home Assistant

The integration exposes a dedicated action mammotion.start_mow. To test quickly, go to Developer Tools → Services, choose mammotion.start_mow, target your mower, and then enter the parameters that your model supports.

Simple example (to adapt to your entities/areas):

action: mammotion.start_mow
data:
  is_mow: true
  speed: 0.3
  border_mode: "1"
  ultra_wave: "2"
  areas: [switch.mower_1]

According to the wiki, there are universal options (mowing order, speed, obstacle detection, trajectory mode, etc.), specific YUKA options (collect/drop-off, borders…), and specific LUBA options like cutting height.

Really useful automation ideas

From now on, it is possible to create various automations integrating your robotic lawn mower. For example:

• “Smart weather” stop. If your weather station (Netatmo, Zigbee sensors, or a weather integration) reports a high probability of rain, Home Assistant can return the mower to base before the garden turns into an ice rink.
• Anti-heatwave. If the outdoor temperature exceeds a threshold (30°C, for example), you can postpone mowing to the evening or the next day. It’s not just about comfort: on certain dry terrains, mowing in the full sun can also be less “clean”.
• Mowing with solar surplus. If you track your photovoltaic production in Home Assistant, triggering mowing when you have surplus during specific times (for example, late morning/early afternoon) is a simple trick to recharge your robot with the solar energy produced.
• “Garden presence” safety. If a gate opening sensor is triggered, if a camera detects a presence, or if the “barbecue” mode is activated, you can automatically pause the mower (because a discreet robot in the grass can be forgotten… until it goes to the wrong place).
• According to the family schedule. If you have integrated the family calendars into Home Assistant, it is easy to know when the robot will not disturb by roaming in the garden.

A personalized dashboard

With all the information retrieved from the robot, it is possible to create a personalized dashboard integrating your Mammotion robotic lawn mower. For example, I created this dashboard:

By using HA-Animated-Cards, for example, it is possible to do some pretty nice things (I still need to work on it, but the first two tiles give a glimpse).

Quick troubleshooting

If you encounter a timeout to the API api.link.aliyun.com, the repository mentions that you should check if your network or firewall is blocking services “hosted in China.” That’s the kind of detail that can waste an hour if you don’t know it.

And if the account addition rejects your email, the repository indicates that sometimes “the account number” works better than the email address (yes, it’s strange, but you might as well keep that in mind).

Conclusion

In the end, integrating a Mammotion robotic lawn mower (LUBA or YUKA) into Home Assistant is not just “adding one more gadget” to your dashboard. It is primarily about taking control of mowing again, linking it to real daily information: weather, presence in the garden, schedules, solar production, and the household’s lifestyle. Once the entities are in place, you quickly realize that the best gains come from simple automations: avoiding bad time slots, stopping at the right moment, and starting mowing when everything is in order. And that’s where Mammotion + Home Assistant makes perfect sense: a well-maintained lawn, without thinking about it, and without surprises.