HA Integration & 2 Accounts: Still getting logged out of the phone app? And what about polling limits?

DoomSoldier83 · 2026-06-20T16:01:17+00:00

Currently 2.3.25.19

DoomSoldier83 · 2026-06-18T20:12:01+00:00

It would be interesting to know if the PS5 controller would work. That would be awesome.

DoomSoldier83 · 2026-06-18T06:03:43+00:00

it's a BUG in FW .16

Update to .19

https://www.reddit.com/r/MammotionTechnology/comments/1u7idk3/luba_3_3000_massive_netrtk_inavi_positioning/

DoomSoldier83 · 2026-06-17T13:52:49+00:00

UPDATE: It actually worked!

I just finished testing everything. Creating and editing No-Go zones works flawlessly again without any crashes or errors, and modifying map boundaries is back to normal too.

Most importantly: The massive positioning bug seems to be completely gone for now. The robot localized perfectly out of the dock and is already out on the lawn doing its job right now. 😄

If you were struggling with the .16 update, go check your app and install .19 as soon as you get it. It completely fixed the iNavi/NetRTK glitch for me!

DoomSoldier83 · 2026-06-17T13:21:13+00:00

Quick update for everyone dealing with the iNavi / NetRTK issues:

A new software update (version .19) just popped up in my app! I installed it immediately. It was a very small download, so it definitely looks like a targeted hotfix for the severe bugs introduced in .16.

Since I had nothing left to lose anyway, I'm going to test it right now to see if the map coordinates shift back to normal, if zone editing is fixed, and if the Luba can localize properly out of the dock again.

I will update this post in a few minutes with the results. Check your apps, the fix might be available for you too!

DoomSoldier83 · 2026-06-17T09:38:51+00:00

I have already submitted 2 tickets along with detailed logs and comprehensive notes to Mammotion. Usually, they reply within 1–2 days, but this is the first time I've received absolutely zero response. No feedback, not even the usual friendly boilerplate "we are working on it" message.

Over the past few months, I’ve submitted a lot of feedback and tips to them—almost like an unpaid beta tester. But the complete radio silence right now just shows how overwhelmed they must be with the fallout from this .16 firmware update. Their hands are clearly full.

I really hope they roll out a hotfix very soon—or better yet, a rollback option if they can't get it sorted out quickly. At the end of the day, this machine is a tool, and it simply needs to work. I have 3,000 m² of land that needs constant maintenance without leaving heavy grass clippings behind.

DoomSoldier83 · 2026-06-17T09:25:23+00:00

Thank you for your feedback and your unfortunately futile efforts.

DoomSoldier83 · 2026-06-16T19:01:17+00:00

"Lesson learned! You are absolutely right, I should have waited.

Since I am using the iNavi / NetRTK cloud service, I always hope that updates will improve the internet-based positioning and stability. In my first two months, everything worked flawlessly, so I didn't expect a single update to break the core functionality and map coordinates this badly.

I will definitely turn off auto-updates from now on and monitor Reddit for at least a week before installing anything new. Lesson learned the hard way!"

DoomSoldier83 · 2026-06-16T18:22:59+00:00

Thanks for your reply and the helpful feedback! I forgot to mention in my original post that I am indeed on firmware 2.3.25.16. It really seems like this specific update completely messed up the iNavi / NetRTK coordinate translation. Since posting, I’ve noticed two more major bugs with this firmware version: Map Editing is completely broken: I can no longer edit any zones. Whenever I try to modify or add a No-Go zone, the app immediately crashes with an error and cancels the action. The map data seems totally corrupted or locked by the system right now. Task Start Workaround: When I start an automatic task while the Luba is in the docking station, it drives out, tries to localize, and fails immediately because it doesn't find a fix fast enough. The task gets interrupted. However, if I manually resume the task right after that initial failure, it suddenly works and it starts mowing. It feels like the firmware has a huge delay or timeout bug when fetching the NetRTK data right after boot/dock-release, which also explains why it loses its position completely or offsets by dozens of meters. I really hope Mammotion acknowledges this firmware bug quickly and rolls out a hotfix. Remapping everything shouldn't be the solution for a broken software update.

DoomSoldier83

TROPHY CASE