Potential Mapping Issue

[Neil-1980]

The problem

I’ve had my mower back from repair earlier this year though it lost all its maps when I got it back.

I’ve struggled for ages with the app trying to map the areas for a few weeks though the position kept freezing at random intervals for no apparent reason.

After reinstalling the app a few times and trying various things I was about to give up when my last attempt I decided to disable the HA integration…. It worked faultlessly.

I’ve just tried another area again and it’s perfect with the integration disabled.

I can only assume when mapping in the app the integration does something like asking for updates and it throws off the mapping but assuming that’s right it may be worth a mention if it’s something that’s not fixable

What Mammotion mower are you using?

Luba 2

What version of the Mammotion intergration are you using?

Unsure

What version of Home Assistant Core are you running?

2025.3.3

[mikey0000]

First up, really sorry that the integration has caused these issues for you. I've done modifying maps with the integration on without issue so it would be helpful to know what version your on, I've made a lot of changes over the past month as well to improve it. The main call the integration makes shouldn't mess with map creation and the newest version should be much better again. Did you have any maps present on your Luba at all? Because I'm thinking I may know what is the cause.

I think I have a few things I can test out which has to do with map synchronisation. Again newest version should be much better.

[mikey0000]

Would be good to send mammotion a log too, or try logging into your mower from the seperate account on another phone and trying to reproduce just with mammotion app.

If you can it's a problem that mammotion need to solve.

[Neil-1980]

No problem at all… really appreciate you’re efforts with the integration so thought it may help letting you know of an issue.

Versions are:
HA Core 2025.3.3
Supervisor 2025.03.
OS 14.2
Integration 0.2.4
iOS 18.3.2 on iPhone 15 Pro Max
App version 1.12.67
Luba2 firmware 1.11.511.603
RTK firmware 1.11.511.72

There were no maps on it as it came back map free though there were 3 areas mapped before it was sent for repair.

I actually opened a ticket with mammotion on Sunday when I was thinking it was an issue with their app before I tried disabling the integration but have heard nothing back as yet but if/when they reply I’ll let them know im using a second account also.

[mikey0000]

I'd really like to nail down where the issue is on this so I can sort it out. So the way the integration rolls it checks for maps changes once a day, this could interfere with making maps but would take up about 10 minutes max maybe so I doubt this is the thing causing the problem however I've got something I think I should change that should help when the robot has no maps.

The other repetitive call is a basic call for information e.g are you mowing and so on.

The way I'd test this out is.

Setup a phone with the shared account, open the app and just go into the map view of the robot.

while the second phone is open, try to create a map on your primary phone.

If it behaves the same, then its an issue with the mower firmware. If not, I need to look into how I can not create this issue.

If your able to test this out, that would be amazing, if not, that's all good too and I'll see about what I can do to resolve this.

[Neil-1980]

I haven’t got a spare phone sadly though may be able to borrow one to try this.

Give me a couple of days or so and I’ll let you know the outcome!

[KLucky13]

I've lost literally hours trying to remap my garden after I moved my RTK since last season and have the exact same issue as you are describing. I've been emailing support back and forth for days and no idea what is going on.. I will need to test this in the weekend if the HA integration is causing it. The workaround for me was every time the robot freezes in the app, click on the connectivity icon top right (where you can see the connection strength of every connection type) and close the menu again. This "unfreezes" the robot. It made it possible to map everything but it was a huge pain... Never thought about the HA integration being the issue! I'll try it out in the weekend

[Neil-1980]

Yeah that’s how I was unfreezing it initially but it would freeze again soon after which was a pain.

But yeah if you disable it in HA, do your mapping and then re-enable it it’s perfect. I’ve done a few larger areas this week (haven’t been able to get hold of another phone to test yet) but it mapped perfectly until I re-enabled and then it couldn’t map without freezing.

I have got a ticket open with Mammotion who seemed keen though said there was a new version coming out (the one that’s out now) and to try that and come back to them if it didn’t fix it. Needless to say it didn’t so I emailed them back though had no response from them. But if you want to tell them it’s the same issue as ticket 88783 to build up a bit more pressure on them feel free.

The whole thing though isn’t a problem when you realise you just have to disable it temporarily… it’s just the getting to the point where you realise what’s probably happening.

[KLucky13]

I also have the issue that I regularly can't connect to my Luba from the app. Well, just checked, that problem is also fixed by turning off the HA integration. I just removed the integration altogether from HA. That's 2 problems I lost so much time with and the added benefit from the integration is not that great anyway. Glad I got those 2 problems fixed!

[Neil-1980]

Did you create a second account so HA and your phone aren’t using the same login?

I used to have problems having to sign in all the time till I realised that (and it’s documented too but me being me I didn’t read it 😂).

[KLucky13]

Yes, I remember creating a second account for this. In my case it's not prompting me to log in again, it's just showing the robot as "offline" all the time unless I connect over bluetooth. I know being kicked out of the app and needing to login again is when you use the same credentials, but that's not what's happening in my case

[mikey0000]

Their app isn't the best... The whole point of sharing and using MQTT over WiFi is that multiple devices can send and receive events at the same time. I have a solution for when users are editing so that will come out soon.

[mikey0000]

Hey this should be resolved (hopefully) in the latest, I've added something that will stop requesting data when the mower is in any editing modes. If your up for testing this, that would be great.

[mikey0000]

Any update guys?

[mikey0000]

I tested my mower and was successful in creating an area and a channel so unless someone has something else to say, I'll close this.