u/Active-Battle-1937

I chatted with Lymow Support about, among other things, the current issues and the “support backlog” situation. I learned that Lymow is currently working hard to expand its support structure and train new staff. However, this can't happen overnight—the new employees first need to be trained so they can effectively handle support and process support cases.

At the time of my chat with the employee from China, it was 1 a.m. on Sunday morning there. And even at that hour, many of her colleagues were working and had completely sacrificed their weekend to make headway with the high volume of support requests and keep up with their own goals, namely providing customers with quick feedback.

Even the development department was still active at that time, so she was able to tell me that many of the issues have been resolved in the currently produced model of the Lymow One Plus. Among other things, this includes the issue of broken springs (which occurred with my Lymow), as well as improved, more durable tracks and longer-lasting blades, and any customers who are experiencing issues with these springs or tracks on their "old" Lymow One Plus will be able to have them replaced free of charge with the improved versions from the production model.

Furthermore, they are currently working hard to resolve some of the software issues already known here.

She was also able to dispel my feeling that no one from Lymow is reading this and that our problems and ideas simply go unheard. It seems they are actively reading along here, and the ideas are indeed reaching the right people. She told me that, for example, the addition of a feature allowing users to resume an interrupted mowing session, or the idea that it would make a lot of sense on some properties to have a second charging station, had apparently been well received. However, understandably, urgent issues (keyword: ota_ing...) currently have a higher priority—and rightly so, in my view.

At the end of the conversation, I also gave her the (perhaps subjective, from my perspective) suggestion that it might make sense for Lymow to show a bit more presence here, as this would certainly contribute significantly to lifting the mood here.

All in all, my confidence in the company and its products was reaffirmed during this conversation. I’ve gained the impression that they’re currently doing everything humanly possible to achieve the goals they’ve set for themselves. They’re on the right track, but still need a little more time to reach their destination. I hope they reach their destination successfully and don’t have to overcome any further unforeseen obstacles. But I'm very sure they'll make it.

Update from May 13, 2026:

As promised by support, I just received my FedEx tracking number for the replacement unit. Even the replacement blades I ordered a little over a month ago are now on their way. Everything really seems to be going very smoothly now! I’m eagerly awaiting the arrival of Mowzilla #2 :-)

---

After sending several emails over the past few weeks to the two Lymow email addresses I knew, opening a support ticket, and constantly updating them on everything I’d done to try and fix the issues with my Mowzilla on my own—yet somehow never seeing any real progress on the matter—things now seem to be moving forward.

According to Lymow Support, a replacement unit is scheduled to be shipped to me next Monday, and a pickup date for my defective Mowzilla will be arranged (many thanks for that, Ally!).

Now my hope has returned that I’ll be able to keep the property in good shape this mowing season with the active support of the Lymow :-)

I know the support team must be extremely overloaded right now because, due to all the advertising campaigns (at least that’s the case here in Germany), there are likely a lot of new orders coming in, along with the corresponding support volume from all the new customers. But it has been extremely frustrating for me to see no signs of a solution to the problem of my Mowzilla—which is just sitting in the corner—even after two weeks. And then to receive so many emails from Lymow about offers and current promotions, even though I would have much preferred to get an email addressing the issues with my Mowzilla.

Now I see light at the end of the tunnel again and hope that other customers who may have been waiting longer for their problems to be resolved will soon have a similar experience.

Keep your fingers crossed that everything goes as well as it currently looks and that Mowzilla #2 can start working here soon.s

Since the short review was apparently too long for the reply form and probably wasn't sent, I'm sharing it here. Maybe it will be helpful to someone who has had a similar experience and wants to know they're not alone.

I’ve been using “Mowzilla” for about a month now. After setting it up and mapping the large, complex area (about 8,000 square meters, with lots of trees, bushes, and no-go zones), it mowed really well. However, it constantly required “babysitting” because, due to some kind of error, it had to be restarted repeatedly, moved out of a no-go zone it had driven into, the cutting deck height was no longer correct after recharging and resuming mowing, and so on.

At first, there were also recurring issues with charging the mower in the docking station. Sometimes it wouldn’t charge at all; other times, the charging process would simply stop halfway through. As I discovered, the cause was likely that the brushes used to clean the contacts were too stiff or had bristles that were too long. As a workaround, I simply unscrewed them, and I haven’t had any charging problems since.

Then, while mowing, it also had many strange issues where it would just stop, apparently reboot, and then continue after a pause. However, these became less frequent after an OTA update. After some time, I noticed that it treated the slightest unevenness in the lawn as obstacles. As I later found out, the problem was likely that a spring on the Omni-Wheels had broken, so it no longer had any support at the front end of the mowing deck and kept getting stuck everywhere. I sent an email to Lymow Support regarding this and asked for replacement springs to be sent—but I haven’t received a response to that yet. To be able to continue mowing, I bent the end of the broken spring so that it could at least provide some support for the mower deck at the front.

After about two weeks, “Lifting Motor Jammed Errors (E7)” occurred. These errors meant that, even though the mowing deck and the entire Lymow were completely clear and clean, the mowing process could no longer be started at all. However, when I pressed the buttons directly on the Lymow’s display, the mowing deck operated perfectly and could also be moved into the maintenance position. I had already opened a support ticket about this two weeks ago, but it wasn’t addressed until recently.

When I installed the OTA update to version .45 about two weeks ago, hoping to fix the E7 errors, it caused the mower to get stuck in an “ota_ing...” loop that lasted over a week. I tried all the troubleshooting options I could find online—disconnecting the battery (even for more than a day), restarting with every possible button combination, etc.—but to no avail. Eventually, though, when I was nearly at my wits’ end, I checked for an OTA update again, and it actually started installing the update, but lost all connectivity in the process.

It has been in this state for about a week now. It is completely unreachable—neither via Wi-Fi, 4G, nor Bluetooth. Reinstalling the app on multiple mobile devices, clearing the cache and data, etc., have not solved the problem so far. I hope that Lymow Support will provide me with a solution to this problem quickly or send me a replacement device as soon as possible.

Other issues I’ve noticed during the (unfortunately far too short) time I’ve been able to use the Lymow so far:

- In areas with poor GPS reception, the Lymow occasionally leaves the mapped area entirely or crosses no-go zones.

This led to it getting tangled up in a fence on the neighboring property (well outside the mapped zone) and nearly driving into a pond (also well outside the mapped zone), where it would have become a “submarine” if I hadn’t happened to notice it right away. My question regarding this: Shouldn’t VSLAM actually prevent this?

- In areas with variable GPS reception (partly with trees and bushes), the Lymow has already driven into a no-go zone several times, received a good GPS signal there, realized it shouldn’t actually be there, and responded with an “Out of Bounds” error. This, in turn, led to another “babysitting” session every time, since I couldn’t remotely guide the mower back into “permitted” territory. My question regarding this: Couldn’t this somehow be implemented in the app?

- After resuming mowing following a recharge, the cutting height was often incorrect—frequently much too low. This caused the mower to “shave” the lawn, though this could only be detected remotely by watching the video feed and seeing the bare strips. Question regarding this: Couldn’t the app display somewhere which settings are currently active (e.g., the mower deck height, the current speed, and blade speed settings)?

Further suggestions for improvement: A quick and well-documented way to reset the mower to a defined clean state. See also my post https://www.reddit.com/r/Lymow_Official/comments/1tc5h60/a_question_for_lymowis_a_proper_reset_function/

Conclusion based on my experience so far:

- The Lymow does an impressive job when it works! The lawn has never looked as good as it does after a successful mowing session with Mowzilla :-)

- I am completely convinced by the device and am also certain that no other competitor’s product would be able to handle my property the way the Lymow does.

- I’m pretty sure that Lymow can get the software bugs and minor hardware issues (-> springs on the Omni-Wheels) under control, and that the Lymow can then become the ultimate “lawn tank” for difficult terrain.

- However, there is still significant room for improvement in the support department. Many of my emails (as I found out today) ended up in Lymow’s spam folder, and the support response times (including for tickets) are “not exactly prompt.”

I hope to be able to use my Mowzilla again soon (-> Ticket #67402), just in case anyone reading this can help speed up the process ;-)

Reset possible?

Apart from a few software issues and minor hardware glitches (e.g., the broken springs on the Omni Wheels), I really like my Lymow One Plus. In the less than a month it’s been here, it’s managed to conquer the roughly 8,000 square meters of truly complicated lawn—with plenty of molehills, vole tunnels, branches, lots of bushes, and some areas covered by tall trees—and has already saved me a lot of work.

The only thing that really bothers me is that, due to some software issues, I’ve repeatedly been forced to restart the mower, disconnect the battery, wait a long time, and then hope that the mowing process will resume smoothly after this “babysitting” session. In the sources I’ve found so far, I’ve come across a wide variety of instructions on how to perform such a reset after software issues. Starting with power off/power on, to disconnecting the battery (instructions for the duration vary from a few seconds to hours and days), restarting the mower multiple times (I’ve read 2 to 10 times)—though there are also mentions of button combinations with the Home button held down and not held down.

From my (perhaps somewhat naive) perspective, the following options would be feasible for the existing model, i.e., without adding additional hardware buttons or anything like that:

- An officially documented key combination by Lymow that triggers a clean reset or reboot. This could also be activated only after entering a PIN on the PIN-protected screen.

- A way to initiate a clean reset or reboot from within the app.

- A way to connect the smartphone on which the app is installed via a USB-C cable to the USB-C port already built into the Lymow and then perform a clean reset or reboot. This option in particular would be great for my Lymow right now, since after an aborted software update to the .46 firmware, it is unfortunately no longer accessible via Wi-Fi, 4G, or Bluetooth.

Since "Mowzilla" was stuck in an ota_ing... loop last week and tried every conceivable approach to escape it, I believe that a clean reset/reboot function—however it is implemented—could solve many problems, reduce user frustration, and likely even drastically reduce the volume of support tickets at Lymow Support.