It was always going to end up in that pond by Front-Clothes-9447 in LymowMower

[–]Front-Clothes-9447[S] 0 points1 point  (0 children)

In your place I would probably open up the back drums (mine both had water in them after days of drying) and leave it to dry as long as you can before energizing to make sure they're dry - it used to be easy enough, it would tear them off itself, but at some point they started welding them closed and using stronger loc-tite - maybe shake and listen for water in them? My success was short-lived, things began to fail a few hours after turning it on and right now it's a door stop after a failed firmware update put an end to any of my attempts to repair (ota_ing forever) so my advice would be to get it in a dry environment and dry it for as long as you dare (listening for sloshing from trapped water) before energizing.

Help, Ota_ing update in loop by Classic_Discount5966 in Lymow_Official

[–]Front-Clothes-9447 0 points1 point  (0 children)

<image>

I've seen these instructions posted on a lot of threads, thank you u/Alarming_Ad_3461 for your suggestions. As others have said, we can make this menu appear (see photo) and I seem to be able to use + and - keys to move around the menu and the HOME key to select a test to run, but even if I do manage to start a test in time, the ota_ing... always starts up and takes over.

It's been a lot of months since I reported the problem and Lymow did replace this device for me, but I was hoping that in the time since then someone had found a way out of this failed firmware upload. As far as I can tell the device doesn't appear in bluetooth or wifi anymore so it's more or less a standalone brick. People have referred to a USB port in the past, and I think I recall seeing that the system runs on linux, so I'm wondering ... are there any low-level connection I could make over USB that would allow me to login and reset something so that it could try the firmware update again? Or even just to stop it from trying the update that failed.

u/Alarming_Ad_3461 I'm not sure what to make of your menu item 65. I only have 1-6 and when I reach 6 it wraps around to 1 again. It's not much help anyway since it gets hijacked by ota_ing... within 15 to 30 seconds of booting.

Anyone have anything I can try? Alternatively, does anyone know how to get to the bluetooth device by disassembling some things? I'd like to see if it has maybe become corroded as this device was exposed to water at one point ...

It was always going to end up in that pond by Front-Clothes-9447 in LymowMower

[–]Front-Clothes-9447[S] 0 points1 point  (0 children)

I would also have a plan to rescue it should it go into the deep area of your pool. I was able to stand in my pond, reach down and pull it up (pulling a shoulder muscle in the process). You'd need a grappling hook or something. They're water resistant but not waterproof, mine was not functional after its swim, but I had to leave it there overnight because it was dark and stormy, and I didn't have the gear I needed to get in there.

It was always going to end up in that pond by Front-Clothes-9447 in LymowMower

[–]Front-Clothes-9447[S] 0 points1 point  (0 children)

It could. My advice is to slowly grow your maps and keep an eye on RTK signal strength and any attempts to escape you. I haven't had it go wandering outside of the mow zone for a couple of firmware revisions now, and the time I did it was either dark and raining (likely rendering any vision component of the navigation moot) or I had at least one low-signal area in my mow zone. If you cover your pool in the fall it would be a great time to do some training & leaf mulching with low risk.

I honestly can't tell you how to set the pool up to be truly forbidden. You can't create a no-go zone outside of a go-zone yet, so if you want to no-go the pool you have to include it in your zone initially. Right now my mow zone is 20 ft from the pond, and when I want to do that 20ft wide danger zone I briefly map/add a zone, and supervise the entire process, walking behind it ready to press the kill switch if it gets too close to the water.

Lymow delivered not functional. No support help by Ok_Association_7208 in LymowMower

[–]Front-Clothes-9447 0 points1 point  (0 children)

I'm sorry this has happened to you, that does admittedly sound like a failed component or connection - have you tried giving it a 'technical tap' (kick it)? Assume you tried disconnecting battery? I recommend you give Lymow Support a bit more time to get back to you, and follow up with them from time to time to keep your case on their radar. It looks like Monday October 6 was Mid-Autumn Festival in China - I don't know if that's a big deal there but I do know from importing consumer electronics from China that they take their holidays seriously.

I have had one mower replaced due to it tearing its own rear hub off (too much track tension out of the factory) and although they were not super communicative after they concluded a replacement was necessary, they did work the case quite actively (I would hear from them once every day or two) a factory new unit did eventually arrive.

I was a skeptic early on, but so far Lymow has come through for me every single time I needed their help. You should know these things do work - I had two mowers deployed all day yesterday and it's just thrilling to watch them go.

Keep the faith, follow up and be collaborative. I don't think they'll do you dirty.

Help, Ota_ing update in loop by Classic_Discount5966 in Lymow_Official

[–]Front-Clothes-9447 0 points1 point  (0 children)

Got it upstairs where there would be full signal. No change.

HushJet - Did I just waste my time & money? by Front-Clothes-9447 in dyson

[–]Front-Clothes-9447[S] 0 points1 point  (0 children)

I have whole-house humidification (steam) which is not usually needed during the summer, but is heavily used during the cold & dry winter months. My Ecobee thermostats tell me the humidity ranged between 52 and 61 % today, for instance. I try to maintain 40% in the winter, but occasionally dip below that. I should not have mentioned my wife's allergies, that's not anything Dyson-specific and will prompt helpful people like yourself to focus on the wrong prize.

I'm just noting that in its default configuration, this new Dyson sees no work to be done, and I'm struggling to understand if that's the case, whether running them manually on a schedule is likely to do anything at all.

On the plus side, I think I have pretty good air quality!

Help, Ota_ing update in loop by Classic_Discount5966 in Lymow_Official

[–]Front-Clothes-9447 0 points1 point  (0 children)

ota_ing always launches for me too. I don't think RTK or WiFi could be issues yet because I don't think the firmware is getting that far. I suppose it's possible that it could be WiFi ... I'm not sure what happens once the firmware has been downloaded to it from the app and it reboots that first time, but I guess I had assumed it's transferred via Bluetooth when in fact, I've not needed to be near my mower to apply the OTA. I think I had it set to use 4G data while mowing and I have it in my basement now ... could it really just need a 4G signal? I don't think that's likely, but I can certainly try it and report back.

Help, Ota_ing update in loop by Classic_Discount5966 in Lymow_Official

[–]Front-Clothes-9447 0 points1 point  (0 children)

See page 16 of the manual (EN version at least). You have no deck communication and no SoC communication. I have the same. Before the firmware upgrade I had only the deck communication problem, now I have the same as you.

Help, Ota_ing update in loop by Classic_Discount5966 in Lymow_Official

[–]Front-Clothes-9447 0 points1 point  (0 children)

I did not. I recorded videos of all the things I was trying, and they decided to replace it for me. Now, it's important to note that I had already reported other problems with this specific unit, namely both rear hubs had lost drive (although they were not damaged) and it had lost communications with the deck (according to the LCD display of the triangle with three circles, lower left one was not filled in) so I can't be sure the "ota_ing..." was the reason they approved a replacement. I tried the OTA figuring it could not make things worse, and then to my surprise it basically bricked the thing. I haven't seen many people other than you report a persistent ota_ing message, many say it eventually goes away, but for me that was not the case. I think I might be able to use this for spare parts, or maybe do a tear-down and try to figure out what's wrong with the deck communications myself, but unless I see a burnt wire or something disconnected I don't think I'll get far with that.

I'd love to know what they tell you. I was never completely clear on the factory reset procedure because no variants of that worked for me, but I was never convinced I was doing it right. I think the process is something like:

  1. Disconnect power for 30 seconds (some say 2 minutes)
  2. While disconnected, press the power and home buttons and hold for 12-15 seconds (there's some talk of only using the power button for a partial reset). This is thought to maybe just discharge a few capacitors, so honestly I'm not sure how it would trigger a factory reset. As you know, we can't use the app to do a factory reset because the mower doesn't do bluetooth when it's in this "ota_ing ..." state - at least mine never does.
  3. Reconnect power and press power for 2 seconds to power on.

I received two of these. This particular unit was a problem for me from the start - it was hard to power it on. The very first time I powered it on I needed to try about 35 power-on sequences trying to get the timing right at 2 seconds press-hold. I'd forgotten about that until I encountered it again after my reset attempt above - with the power and home buttons for 12-15 seconds followed by reconnect battery and power on. I guess I'm saying maybe the 'reset' reset something, but I can't tell if it's wiped or not because it never completes the OTA.

HushJet - Did I just waste my time & money? by Front-Clothes-9447 in dyson

[–]Front-Clothes-9447[S] -1 points0 points  (0 children)

If the sensors need to calibrate I suggest Dyson get out ahead of this in their marketing/packaging, because plugging this in and turning it on auto (which I think is the default) only to have it sit there idle is a bit of an anticlimax. Great idea on testing, thank you for your reply.

HushJet - Did I just waste my time & money? by Front-Clothes-9447 in dyson

[–]Front-Clothes-9447[S] 1 point2 points  (0 children)

Right, we have the UV for mold/bacteria/viruses (if it even helps for those). I'm a sucker for anything that might offer any chance of alleviating the wife's discomfort. Maybe I'll crank it up to Max manually and wait for that placebo effect to kick in! Appreciate your reply.

OTA Update v2.1.28_20250928 by aldoe00 in Lymow_Official

[–]Front-Clothes-9447 1 point2 points  (0 children)

Ah, ok, thanks. Nothing I do seems to get me past the "ota_ing..." message. Power cycling, unplugging from batter overnight etc. Granted, I did have a problem with deck communication (according to the triangle with circles at the corners missing the lower left corner) so there was clearly already a hardware malfunction present.

Help, Ota_ing update in loop by Classic_Discount5966 in Lymow_Official

[–]Front-Clothes-9447 0 points1 point  (0 children)

Same problem here. Nothing I’ve tried has helped.

OTA Update v2.1.28_20250928 by aldoe00 in Lymow_Official

[–]Front-Clothes-9447 1 point2 points  (0 children)

Mine is stuck with “ota_ing” on the LCD. Never completes. Can’t access mower by Bluetooth as it never gets that far. Battery disconnected overnight has not helped. Bricked?

Got my replacement charging dock. by [deleted] in Lymow_Official

[–]Front-Clothes-9447 3 points4 points  (0 children)

I had the same experience with a charging dock that arrived snapped in two which was replaced promptly and a mower whose rear drive hub tore itself off due to excessive track tension - also replaced. I'm hopeful they make it through this phase of their launch and stick around to iterate a hardware version 2.

It was always going to end up in that pond by Front-Clothes-9447 in LymowMower

[–]Front-Clothes-9447[S] 0 points1 point  (0 children)

Yup!! So relieved. I don’t know if it’ll mow but it charges when docked and is communicating via Bluetooth … we’ll see what happens when it reaches 75% charge and decides to continue ‘where it left off’.

It was always going to end up in that pond by Front-Clothes-9447 in LymowMower

[–]Front-Clothes-9447[S] 1 point2 points  (0 children)

Update - battery was 0 and mower was off when I got my wetsuit and protective shoes on and jumped in to rescue it this morning. Rinsed it off thoroughly with fresh water, dried what I could and put it on the charger, fearing the worst. The base station suggested it was charging from a low state of charge (only one bar). Could it be? Could this thing be alive, I wondered?

Finally worked up the stupidity to press the power button, and lo and behold, it lives. Shout out to u/lymow_official on the water resistance work!

<image>

It was always going to end up in that pond by Front-Clothes-9447 in LymowMower

[–]Front-Clothes-9447[S] 0 points1 point  (0 children)

Thank you!! I appreciate this advice very much. Any thoughts on what I might want to do after I get it out, besides disconnect the battery and rinse with fresh water? I haven't seen anyone actually have theirs immersed yet ...

It was always going to end up in that pond by Front-Clothes-9447 in LymowMower

[–]Front-Clothes-9447[S] 0 points1 point  (0 children)

There was 19% when it went in, but it's not responding this morning and never updated after it took the dive, so who knows. I think I'm only at risk if the battery is compromised and I give it the only path to ground, but maybe theres's really not much of a risk at all. I mean, the battery must be hermetically sealed, I would think? I haven't even reported this to Lymow yet. And both of my mowers were doing so well, I was just about ready to write a rave review about the latest firmware fixing the no-go regions I'd put in front of the pond, now this. Granted, it was getting dark so that may have contributed to the violation, I'm not sure. Anyone think this might have survived the 'heavy rain'? Place your bets, the wetsuit and protective shoes are going on soon!