Same on mobile as on pc in webapp. No difference.
Great you have started the analyze already, here are my answers of your questions.
- I have currently one Zone mapped in the official app
- Basically depending of only 1 Zone it is always active i dont select a zone in the app before i start the mower, When i start the mover it pop up two informations - cutting hight and the self test after this two steps i confirm and because of 1 Zone it dont ask anymore which one and the mover start! Before i test to start the mower over Homey i run zone 1, but i made so many test also the Firmware Update, so in the meantime i dont run a complete run in the official app.
- Its not a scheduled run, difficult i must monitor this and will report
- I will create a. 2 Zone tomorrow and will test this point
Thx for helping, i keep you informed!
Well…which system / hardware do you use? Homey? Mobile Device? Mammotion and RTK Antenna?
Not sure that makes any difference but pixel 9 pro. Homey pro 2023. Yuka mini 800 with rtk. I’m might add that my rtk does not show up as a unit in the app and I cannot add it for some reason. but works fine and I can see it on the map.
Den tis 14 juli 2026 19:03# <notifications@athom.discoursemail.com> skrev:
Ok…no properly not but anywhere is a differnet because i had never problems to add the devices in homey and i have the same mower and RTK, this is what i try to understand…you mean with RTK is not in the original app as additional device, like in my picture below? Well i dont know if this have an impact or not for add the mower into homey? Maybe you should try to bring it into the mammotion app and start the complete procedure again…
Which Software Verison is installed on the mower…v1.15.21.1 this is the actual official release verion for the yuka mini 800…first time i add the mower i had installed this version…yesterday i installed the beta version like described in my post above…
Would it be possible to start a flow as soon as the Luba starts to return to the charging station?
I want to start the flow before it gets to the charging station.
Yeah thanks. My rtk does not show up as yours so I think im gonna reset both rtk and mower and readd them to the app to see if there’s any difference. Mine is on firmware 1.15.21.1 which seems to be the latest and rtk says 19929 not sure if thats the latest..
Brilliant news — this is already sorted and does just what you’re after! There’s a handy Flow trigger card called “Mower started returning to dock” that kicks in the moment your mower’s status switches to “returning” — that’s when it sets off back, not when it gets there. (In fact, it’s made for exactly this situation — the card’s own note says: “so a Flow can react before it actually docks, e.g. opening a garage door the mower needs to drive through.”)
Here’s how to set it up:
1. Make a new Flow in Homey
2. For the trigger (“When…”), choose your Luba mower device → “Mower started returning to dock”
3. Add whatever action you’d like (open a gate, switch on a light, send a notification, and so on)
This is different from “Mower docked,” which only triggers once it’s safely parked and charging — so you’ll want the “started returning” card, and it sounds like that’s just what you’ve discovered. No tweaks needed from my side — this has been available for a while now. Do let me know if it’s not working as hoped, and I’ll take a look at your diagnostic log.
Thank you!
Now I just need to get “tummen ur” and finish the garage.
180 users! Thank you — and a recap of everything that’s shipped recently
Small milestone that means a lot to me: the Mammotion app just crossed 180 users on the Homey App Store. For a one-person hobby project built in evenings and weekends, that’s genuinely surprising and I’m grateful for every single install.
It also means something more concrete than a nice round number: a big share of the fixes below exist because people took the time to submit a diagnostic report when something looked off. This app talks to a reverse-engineered cloud protocol and Bluetooth stack that Mammotion never documented, so a lot of the weird edge cases (a mower that reports its state a bit differently than mine, a cloud hiccup that only shows up under rate-limiting, an account setup that behaves differently on a shared mower) are things I simply can’t see from my own two mowers. Every log you’ve sent has gone somewhere. Thank you.
Here’s a plain-language recap of what’s changed since the last big update round, grouped by what actually matters day to day rather than as a version-by-version list.
Rock-solid connections — no more “just restart the app”
This was the biggest focus area, and it’s the one I’d call genuinely done now:
- If the app ever got stuck talking to Mammotion’s cloud (an expired login, an outage, a rate-limit), it used to either hammer the connection every few seconds forever, or need a manual Repair / app restart to recover. It now backs off properly, remembers it was rate-limited even across a restart, and logs itself back in automatically when needed — no manual intervention required anymore.
- Repair itself is now actually reliable: it used to sometimes leave a duplicate connection running alongside the old one (causing a burst of contradictory status updates), or fail to recover a mower that was stuck offline. Both are fixed — Repair now properly replaces the old connection instead of stacking a new one on top.
- Bluetooth retries now back off sensibly instead of scanning every 15 seconds forever for a mower that isn’t there, and pairing/using the app no longer requires Bluetooth hardware at all — it works fully over the cloud on Homey hubs that don’t have BLE (e.g. Homey Pro Mini without a Bridge).
Net effect: if your mower drops off, the app should now find its way back on its own far more often than it used to, without you having to notice and fix it.
The status tile now tells the truth
A handful of fixes around what “mowing / charging / paused / error” actually means:
- A mower paused while charging in the dock now correctly shows “charging” instead of “paused” — matches what the battery sensor was already telling you.
- A locked/faulted mower (think: stuck, wheel lifted, that kind of thing) now correctly shows as an error instead of quietly sitting there as “idle.”
- Fixed a case where some sensor updates (like battery cycle count on certain models) could silently stop arriving entirely rather than just being blank.
If you’ve ever glanced at the tile and thought “that doesn’t look right,” a good chunk of those cases should now be gone.
Mow specific zones, not just “everywhere”
This is probably the single most useful new capability if you build Flows:
- Fixed a real bug where Start Mowing could finish almost instantly and send the mower straight back to dock — it turned out the app was resuming whatever job the mower had cached (which could be one it had already finished) instead of properly picking which zone(s) to mow.
- Added a new “Start mowing zone…” Flow action card with a dropdown of your mower’s actual mapped zones, so a Flow can mow the front lawn on Tuesdays and the back on Thursdays, for example.
- Fixed zone mowing failing with “No mowing zones known” for yards that were never explicitly named in the official Mammotion app — the app now also reads the mower’s raw boundary data directly, so an unnamed default yard is found too.
- One tip while I’m at it: name your zones in the official Mammotion app. Unnamed zones still work here, but they need a slower on-the-fly scan every time; named zones are instant.
New sensors and controls
- Bumper Status (OK / Warning / Error) and Blade Active (on while the blade is actually spinning) — both new.
- Total Distance and Total Work Time — lifetime sensors tracking the mower’s whole history, not just the current job.
- Insights history now logs WiFi signal, Bluetooth signal, GPS satellite count and Blade Active over time, so you can graph signal quality or blade activity, not just see the current value.
- Headlamp and Side LED are properly fixed now — the headlamp toggle used to silently do nothing (Homey reported success, the mower did nothing); Side LED now uses its own correct command instead of piggybacking on the headlamp one, and both stay in sync if you flip them from the official Mammotion app instead of Homey.
- Rain Protection was silently being ignored by the mower due to a wrong command — fixed, and it now matches the toggle in the official app.
More Flow cards for automation
- New trigger: “Mower started returning to dock” — handy for things like opening a garage door or gate before it arrives.
- New condition: “Mower status is…” — lets advanced Flows check for an exact status (mowing, charging, returning, paused, error, idle) instead of only “is mowing.”
What’s next, and how you can help
The app is still Luba 2 / Luba 3 only — Yuka and Spino aren’t supported yet. Zone mowing is new enough that I’d expect a few rough edges on setups I haven’t personally tested (different regions, older shared accounts, unusual zone configurations), so if something behaves oddly, please send a diagnostic report from the device settings. That’s genuinely how most of the fixes above happened — a real report from a real mower doing something my mower never do.
Thanks again for 180 installs, and for every log, bug report and bit of patience while this got sorted out. More to come.
Great work, much appreciated.
If you drop me a DM, I’d be delighted to be invited as an account to help sort out your issue!
BTW, you diag helped. test this build; Mammotion | Homey
Thank you for being a person like you, I really appreciate it, great work 
Strange,i have install the test version,always the same message on my yuka 500 if i’m connecting with the 2email adress i have created for use with Homey:your robot is registred on the old mammotion cloud ect…
But if i’m connecting with my “official” email adress,the test app find the robot and finish the installation.
Hope it will work with the Yuka version and thanks again for your app
It looks like your second account might not be recognising the mower properly – no worries! Just pop into your iOS or Android app, sign in with the account you’d like to use with Homey, and see if you can control the mower just fine. Then use the account in Homey.
Ooh hey good to know. Just that I figured it out eventually. I forgot I was testing some geofence blocking on my unifi earlier and of course I had China blocked the app needs to check the Chinese servers although they’re supposed to be in EU to sync…
Edit:
Turned geoblocking back on and it works fine so far except one thing is even though I use another account for Homey, if I check the mower statuses or anything in the homey app I get kicked out on my main account and have to log back in when opening the app
You were right,my 2nd email adress wasn’t link with my mower,now Homey find the robot directly
Sadly the actions card and flows doesn’t work,i imagine it’s a lot of works to adapt your app with yuka version.
I will be patient and again Thanks for your app
Wonderful – could you share the cards that might not work, one by one? Please enter the diagnostics and make sure to switch on debugging within the app settings.
Hi Mathias,
short feedback from my side with the “Start” Problem, thx for your explanation how the “Start” button works, i had a different interpretation of that, i test it again and it works, if the mower will be started first time of the day out of the homey app it works perfect, in one of my posts above i wrote already it works, this is also clear why, my test was after midnight so the mower never had worked-no completed status:-)
Summery, my Could connection Problems i could solve with the firmware beta Update from mammotion and my “Start” Problem was never a problem seems to be :-)! So i can confirm Yuka Mini 800 is working properly!
This would be a great new feature for the future…thx for your support!
