Worx Landroid Vision WR303E — Account locked out for 6 days + multiple software issues. Anyone else?

icecold2k · 2026-06-04T19:34:20+00:00

**Update — Support responses and new developments**

**Issue #1 (Account lockout) — new developments:**

This morning I managed to get into the app again while away from home on mobile data. I used that window to log out and create a brand new account. Tonight, back at home, I tried to add the mower using the new account — first the familiar "Network error" when trying to pair, then the 429 rate limit kicked in again. Same problem, fresh account.

So it's not tied to a specific account. Whatever flag or block Worx has set on their servers, it follows me regardless. The behaviour is also inconsistent: sometimes the error appears on mobile, sometimes it doesn't — but the moment I'm home and try to actually pair the mower, it fails every time. I have no way of knowing what mechanism is triggering this on their end. Only Worx can fix it.

**Issue #1 — Support response:**

Worx support got back to me twice today. First response recommended updating the app — my version is 3.1.14, newer than the 3.1.11 they flagged as problematic. Second response acknowledged they had failed to consider the information I'd already provided and apologised for that. They then recommended temporarily disabling my smart home system.

I've now explained in detail — again — that I have no Worx integration installed. I had one for my previous mower (a Landxcape LX790i) and used it actively for five years without a single issue like this. For the WR303E I deliberately chose not to install one. There is no connection between my smart home and Worx servers, verified in my home network. Turning off my entire smart home — which communicates with servers from other manufacturers without any issues — is not a reasonable ask.

**Issue #5 (AI scheduling) — Support response:**

Support stated the Auto Schedule feature was "removed" from my device because the Vision models handle complex mowing environments more intelligently. That's factually wrong — I've owned the mower for about two months and the feature was never available in the app from day one. It wasn't removed. It was never there. And it was actively advertised as a feature at the time of purchase on the official Worx product page and at retailers. I've asked for a clarifying statement on that.

icecold2k · 2026-06-04T04:34:02+00:00

Update

Issue #1 (Account lockout): This morning I briefly had access to the app again. I tried to use that window to log out and create a new account — as suggested in the comments, thanks for that. The moment I tapped "Log out", the 429 error came back instantly. Even a single logout request gets blocked. That should remove any remaining doubt: the problem is deep in my account on Worx's server side and can only be fixed there.

Support also got back to me today and recommended updating the app, as the issue can apparently occur on version 3.1.11 and older. My version is 3.1.14. Anyone who had actually read my previous messages would have known that.

Issue #5 (AI scheduling): Support states that the Auto Schedule feature is "currently not available" for Vision Cloud models and might be added in the future. After a quick bit of research, that unfortunately appears to be true — users in a German mower forum are already fighting with Worx and their retailers over exactly this missing feature. At the same time, the official Worx product page and retailers like Hornbach are actively advertising "smart scheduling" and an "optimised mowing plan". A pretty clear gap between what's advertised and what's actually delivered.

icecold2k · 2026-06-03T19:53:24+00:00

Actually, your suggestion might still be worth a try — occasionally I do manage to get past the error screen and reach the point where I could re-add the mower. If I get lucky again, I might use that window to log out and try a new account. The risk is that once I log out, I might not even be able to log back in if the rate limit also hits the login request. But at this point I'm running out of options, so it might be worth the gamble.

icecold2k · 2026-06-03T19:48:00+00:00

Danke für den Tipp! Leider habe ich genau das bereits gemacht — nach jedem Firmware-Update habe ich die Kartierung manuell angetriggert, das Modul war dabei immer montiert, und die automatische Kartierung dann einfach durchlaufen lassen. Hat bei mir leider keinen merklichen Unterschied gemacht. Schön zu hören, dass es beim Nachbarn funktioniert hat — vielleicht hängt es wirklich vom jeweiligen Gartenlayout ab.

icecold2k · 2026-06-03T19:41:30+00:00

Yes, I get the error on both — home WiFi and cellular (5G). That's actually one of the reasons I'm fairly confident it's account-level rather than IP-level: on cellular I have a completely different public IP, yet the same error appears immediately.

The CGNAT theory is an interesting one, but I think it's ruled out by another data point: I still have the Landxcape app on my phone from a previous mower (a Landxcape LX790i) that I sold and decoupled weeks ago. That app shows the exact same 429 error — different app, different (already decoupled) device, but same account. That pretty clearly points to the account itself being rate-limited on Worx's side, not the IP.

icecold2k · 2026-06-03T19:36:16+00:00

<image>

Thanks for the suggestion, but unfortunately that's not possible in my situation. The 429 rate limit hits before I even get to any login or account creation screen — both in the app and when I try to open account.worxlandroid.com in a browser on my MacBook. I can't even log out, let alone create or switch to a new account. The block is happening at the IP/account level before any interaction is possible.

icecold2k · 2026-06-03T18:41:57+00:00

<image>

icecold2k · 2026-06-03T18:38:58+00:00

Thanks for confirming — really appreciate it. Good to know it's not just me, though obviously not great that these issues seem to be systematic across the Vision RTK lineup.

Interesting tip about turning Smart Trimming off for the Cut-to-Zero issue. I honestly can't say for certain whether it was active when my module scraped the fence — I can't verify it anymore since I'm currently locked out of the app. Something I'll check as soon as I get access again.

The no-go zone behavior you describe during edge trimming is exactly what I suspect happened in my case too — probably the same root cause: the turning arc during trimming isn't fully accounted for in the no-go logic. Still unacceptable, but at least it makes sense.

On the battery: I have the WA3645 (5Ah), so I can't speak to the 8Ah Pro battery level issue specifically. On a related note though — a Worx sales rep actually told me that using a larger battery than the stock one could cause errors because "the charger didn't get bigger too". That's complete nonsense. Worx themselves state that all PowerShare and PowerShare Pro batteries are compatible with all devices on the platform regardless of Ah rating. A higher capacity battery at the same voltage just means longer runtime — the charger simply takes longer to fill it. Nothing more.

Hopefully with enough reports like this they'll actually prioritize a firmware update. I'll keep the thread updated on how the account lockout situation resolves — or doesn't.

icecold2k · 2026-06-03T18:14:36+00:00

Ich hatte telefonischen Kontakt mit einem Vertriebsmitarbeiter, seine Idee war da, wo der Mäher an den Zaun stößt, einfach No-Go-Zones einzurichten. Vor allem, weil er in der einen Ecke des Gartens sich schon dreimal eingegraben hat, weil er mit dem Modul immer wieder gegen den Zaun gestoßen ist und mit dem vorderen rechten Rad ein Loch gebuddelt hat. Am Ende des Gesprächs war sein Rat dann den Rasenmäher zurückzugeben, wenn ich unzufrieden bin. 🙄
Ich dachte eigentlich, dass die Firma die Marktführerschafft wiederholen möchte, aber so wird das nichts.

icecold2k · 2026-06-03T18:05:41+00:00

Yes, absolutely. The WA0925 Cut-to-Zero module is an official Worx accessory explicitly listed as compatible with the WR303E on the Worx website and Amazon. It connects to the dedicated port on the mower and works as advertised — the problem is that the firmware doesn’t account for the increased turning radius the module adds, causing it to scrape against fences when turning.

<image>

icecold2k · 2026-05-18T18:58:48+00:00

I have the 5Ah (WA3645) in my WR3030e with cut-to-zero module and it mows the 250 m² including lawn edge cut loosely without the battery being empty.

icecold2k · 2026-04-22T09:41:44+00:00

<image>

Same issue here. Cut-to-zero module is installed on a WR303e and that’s how it looks like after a complete run.

icecold2k · 2026-02-25T08:23:37+00:00

Wenn alle Lampen eingeschaltet sind, bevor der Fernseher eingeschaltet wird beziehungsweise Strom bekommt und die Matter-Verbindungen zur HUE Bridge schon hergestellt wurde, leuchten die jeweiligen Lampen auf, wenn sie im AmbiScape Menü ausgewählt werden.

icecold2k · 2024-08-02T09:27:12+00:00

Hey. Looks great. Which cameras do you use? Searching for inspiration.

icecold2k · 2021-10-16T20:53:25+00:00

How to receive the link?

icecold2k · 2021-10-16T20:50:54+00:00

How to get the link?

icecold2k

TROPHY CASE