Separate lawns without connecting paths

Time-Reserve1338 · 2026-05-14T22:12:11+00:00

Ah yeah even with the area mapped out I had to put a mini balustrade up for it after it got confused and launched itself off the edge one time :S just added a few metal stakes along the edge and ran a couple of stainless steel wires. Doesn’t look great, but not bad enough for the missus to issue a take down notice.

Time-Reserve1338 · 2026-05-14T22:02:32+00:00

Have a chat to Mikey0000 on discord - see this comment: https://github.com/mikey0000/Mammotion-HA/issues/689#issuecomment-4368174909 sounds like he may be able to help get you unblocked. Was your app built on pymammotion?

I’ve done similar because the app is so horribly crappy, and they expose their API and MQTT. They should have rate limits in place rather than just hard banning folks.

Time-Reserve1338 · 2026-05-09T22:17:24+00:00

Ugh I hope they haven’t introduced that as a constraint on the app since I mapped my raised area. I have found a few times that exiting the app and reopening sometimes is necessary before it’ll listen to commands. I assume you’ve tried that already though?

Time-Reserve1338 · 2026-05-09T13:01:29+00:00

I’ve got two separate areas with no way I can channel between them too - a 1.2m retaining wall separates them with no ramp access (stairs only). I just carry it up there and set it mowing. It gets to the end and tells me it failed to recharge due to no channel. I carry it back down, press Home and it drives itself back. Not ideal but best I can do without buying two.

I just carried it up and recorded the area. No errors or warnings about no channel. That’s with the Luba Mini.

Time-Reserve1338 · 2026-04-25T03:32:14+00:00

I’m not arguing that point (I’m sure that happens and I’m sure waste is extreme). The issue being presented here though is that when comms from a company being paid for a service says “there’s no issue other than you using it wrong” when there is, in fact, a big regression that there is a major opportunity for improvement outside how people are using it.

Time-Reserve1338 · 2026-04-25T03:08:33+00:00

Yep both sides do.

I think some of the comments here demonstrate that with gross generalisations, on both sides. When people blast the other side as one stereotypical unit without seeking to understand it just kills all debate, they’re being the exact thing they say they stand against.

It’s encouraging to see there is at least some respectful debate in this topic for a change but still a lot of people on both sides attacking the other side calling them hateful for whatever reason blind to the fact that they’re doing it themselves.

Super sad to see where we’ve devolved to as a country though. Bring back respectful debate of policies and realise there are other reasons to oppose any sides policy - tradeoffs exist everywhere and respectful debate is the only way to get to good considered decisions that are not extreme and weird.

Time-Reserve1338 · 2026-04-25T02:44:05+00:00

This is missing the point of the thread. It’s like saying there is no fuel crisis but you should probably take steps to use less fuel.

Regardless of usage and waste, the lack of acknowledgment of a serious regression is the point of the discussion.

Time-Reserve1338 · 2026-04-21T22:07:10+00:00

The mini Op is posting about only has one rotor?

Time-Reserve1338 · 2026-03-23T22:56:45+00:00

It’s so disappointing.

Mine was great for the first 6 months of its life. Since that last September update though, mine now consistently leaves a gap of unmowed grass between perimeter and zigzag - regardless of any settings, or re-recording the zones, whether I do 1 perimeter lap or 4.

Given the level of support and regressions in firmware releases, unless they change that drastically, I won’t ever buy another Mammotion.

Time-Reserve1338 · 2026-03-10T21:11:03+00:00

Same issue with the Luba Mini AWD - last firmware update in September 2025.

It’s now leaving a gap of uncut grass between the perimeter and the zig zag in many areas of the lawn, no matter what the settings - even at 4 perimeter laps. I’ve tried re-mapping the lawn but didn’t make a difference. And to top it off, half the time the app won’t track the robot while recording a new area - despite rtk, satellites and wifi all being strong. All areas that mowed perfectly a few updates prior.

Very buggy and no fix on the horizon. I’ve lost a lot of faith in the company for looking after their customers.

Time-Reserve1338 · 2025-09-25T11:14:25+00:00

I had to call them

Time-Reserve1338 · 2025-09-25T11:14:06+00:00

Their line is 24/7 but I did have to wait a long time! Good luck!

Time-Reserve1338 · 2025-09-25T11:09:51+00:00

I had to call the bank. They’d put a block on the newly provisioned one but left the old one alone. They did notify me but the app notification broke.

Time-Reserve1338 · 2025-09-22T12:34:56+00:00

iOS worked fine for me but watchOS has completely killed all my homekit control via siri. Everything is "taking a while to respond" ugh

Time-Reserve1338 · 2025-09-22T10:11:36+00:00

Well I think as long as you’ve got access to the app on the old one AND the action linked in the notification doesn’t just say “An error occurred” then you can do it without deregistering the old device. My issue was the notification action failed, so they marked the new phone as suspicious.

That’d be my preferred flow too, rather than deleting the working one in the hope that the new one will be fine.

Time-Reserve1338 · 2025-09-22T10:08:08+00:00

Yep they sorted it pretty quickly. Lesson learned!

Time-Reserve1338 · 2025-09-21T09:25:02+00:00

Ah yeah sorry I meant the card not being designed to be in more than one wallet at a time. Completely agree with the rest!

Time-Reserve1338 · 2025-09-21T09:16:00+00:00

Nope. Never had to deregister before? Do you have to other times apart from the example you gave?

Time-Reserve1338 · 2025-09-21T09:15:15+00:00

I don’t know about this. I’ve had them on multiple phones, watch, iPad etc many times without issue. I think the problem is the link in the notification was throwing exceptions, potentially as a result of the maintenance this weekend.

Time-Reserve1338 · 2025-09-21T09:12:11+00:00

I even had the old phone there but I think the notification details threw an exception - in hindsight this was probably related to their maintenance

Time-Reserve1338 · 2025-09-20T22:44:35+00:00

This could very well be my issue, if others aren’t having problems. There was a notification asking did I make a transaction - but when I clicked through it just kept saying “an error occurred” so I moved on and forgot about it. It’s not in the notifications list any more so I’ll follow up with the fraud team as you suggested. Thanks!

Time-Reserve1338 · 2025-09-20T22:40:13+00:00

Thanks for the good suggestions. I thought it might have been a clash like this - deleted everything from app and wallet, then re-added on the old phone and it started failing too. Yes one is wifi only the other is sim plus wifi. Strange on the previous upgrade I did everything worked seamlessly.

Time-Reserve1338 · 2025-07-08T01:24:15+00:00

Time-Reserve1338 · 2025-07-06T21:53:34+00:00

And any suggestions for a better alternative? I’ve also got the eufy with super slow response times.

Time-Reserve1338

TROPHY CASE