u/DoomSoldier83

Luba 3 – Any experiences with the new firmware 2.3.27.20?

Luba 3 – Any experiences with the new firmware 2.3.27.20?

​Hi everyone,

​I just noticed that a new firmware update (version 2.3.27.20) is available for the Luba 3. I am currently running version 2.3.27.16.

​To be completely honest, I am now terrified before clicking "Update" every single time. Back when the 2.3.25.16 update dropped, it completely broke my iNavi / NetRTK positioning. The robot showed up dozens of meters away from its actual location, threw constant 1000019/1000020 errors, and map/zone editing was entirely unusable for days until a hotfix arrived.

​Everything is currently running smoothly on my end with my current version, and I really don't want to mess up my maintenance routine again.

​Has anyone with a Luba 3 (especially those relying on iNavi / NetRTK) already installed 2.3.27.20?

​Are there any hidden bugs, map shifts, or positioning issues with this release?

​Does it feel stable enough to upgrade, or should I follow the "never touch a running system" rule for a bit longer?

​Thanks for sharing your experiences!

u/DoomSoldier83 — 2 days ago

CarStream (AAAD) invisible after June Android Auto Update (v17.0.662234)

Hi everyone,

I'm facing an issue with CarStream (v2.0.5) via AAAD Pro on the latest Android Auto build (17.0.662234, rolled out around June 10).

The Issue: CarStream completely disappeared from my Android Auto app launcher in the car screen.

What I've tried so far:

  • I cleared all data and cache for the Android Auto system app and reinstalled both AAAD and CarStream.
  • After doing this, the CarStream icon actually showed up again perfectly!
  • However, after turning the engine off and starting the system a second time, the icon was completely gone again.

It seems like Google's package verification blocks the sideloaded app after the initial background sync.

Has anyone found a permanent solution to prevent Android Auto from hiding the app after the first launch? Is toggling "Unknown Sources" in the AA Developer Settings still working for anyone on v17.0?

Thanks for any insights!

reddit.com
u/DoomSoldier83 — 14 days ago

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

​Hi everyone,

​I’m currently running into some frustrating issues with the Home Assistant integration for my Luba 3 and wanted to check how others are handling this.

​Following the general advice, I set up two separate Mammotion accounts:

​

​Account A: My main account, used exclusively on my smartphone.

​

​Account B: A secondary account. I shared the robot from Account A to Account B, accepted the invite, and used only Account B to log into the Home Assistant integration.

​

​

​Despite this setup, my smartphone app (Account A) still constantly logs me out whenever Home Assistant accesses the robot. I thought using two accounts was supposed to prevent exactly this session conflict.

​

​I have a couple of questions for the community:

​Is anyone else experiencing this even though you are strictly using a shared secondary account for HA?

​Does the standard automatic polling interval of the HA integration cause issues for you? I’m worried about Mammotion temporarily banning Account B due to aggressive polling, and I'm thinking about disabling automatic updates to use a manual time-pattern automation instead.

​

​Would love to hear how your setups are running and if you've found a way to stop the constant smartphone logouts.

​

​Thanks!

reddit.com
u/DoomSoldier83 — 16 days ago

Luba 3 (3000) – Massive NetRTK / iNavi positioning issues since recent update (Error 1000019 & 1000020)

Hi everyone,

​I wanted to check if anyone else is experiencing severe positioning issues with the Luba 3 (3000) over the last 2 days? I haven't changed anything on my property or the charging station setup, but everything broke right after the recent update.

​I am using iNavi / NetRTK (no physical RTK reference station, just Wi-Fi/4G cloud connection).

​Here is what is happening:

​In the charging station: The iNavi status completely drops to "Disconnected" (Signal quality: None, Satellites: L1 0 | L2 0). As soon as I manually drive the robot just a single meter out of the dock, it immediately connects again, gets a "Good" status, and sees over 35 satellites.

​The main error: Every time the Luba 3 tries to start a task and drives out of the station to localize, it gets stuck. I am constantly getting Error 1000019 (Positioning failed) and Error 1000020 (Positioning not responding).

​Map Offset / Ghost Location: Right now, the positioning is completely broken. Even though the App says "Connected" and iNavi signal is "Good" while outside the dock, the robot shows up on the map dozens of meters away from its actual physical location, completely outside of my mapped task areas.

​What I’ve already tried:

​Multiple standard reboots.

​Hard reset (turned off the Luba and pulled the orange security key for over 10 minutes).

​Restarted my Wi-Fi router.

​Nothing works. The map remains completely shifted. I really don't want to delete and remap my huge area because this looks heavily like a server-side sync bug or a broken firmware algorithm handling the iNavi coordinates.

​Has anyone faced this ghost-location issue after the update? Is there any known fix, or do we have to wait for Mammotion to fix their cloud servers?

​Thanks for any insights!

u/DoomSoldier83 — 20 days ago