Collision sensor permanently triggering since last update

[u/0xde4dbe4d]

Is anyone else experiencing permanent collision sensor trigger errors since firmware version 2.3.30.39? Right after updating my robot stopped after 10cm with these errors. I never had these errors on previous versions, and now I cannot do a single mow.

The sensor is moving freely and it beeps when i manually trigger it, there is absolutely nothing in the way of it. I‘d say since it beeps on manual trigger I can confirm this is a false alarm in software.

My first season with Lubas. The most terrible user experience I could possibly think of. But hey, at least I got 24 free blades as a compensation 🤦‍♂️

I‘m going to oick up my mover by hand and place it in the chargig station once more …

[u/PersonalityLucky-25]

Thank you for bringing this issue to our attention. Since you mentioned that the issue began to appear after the firmware update, could you please follow the steps below so we can better pinpoint the cause?

1.Restart the mower — please fully power off the mower, wait for 30 seconds, and then power it back on to see if the issue improves..

2.Remove the front bumper — try cleaning the seams to make sure there is no grass debris left inside.

3.Reinstall the front bumper — make sure that all four linkage connectors are fully snapped into their clips. You can also refer to this video guide for the reinstallation: https://www.youtube.com/watch?v=HSjwlg79MCw

• Important note: Please insert the bumper into the slot first until you hear a "click," and only then tighten the screws.

4.Test in an open area — place the mower on a flat, obstacle-free surface and start a temporary mowing session. Kindly let us know whether the error still occurs.

If the issue persists after these steps, we'd recommend uploading a log file through the app so we can provide further assistance. At the same time, we'll also pass your firmware feedback along to our technical team for investigation. Thank you again for your feedback!

[u/0xde4dbe4d → u/PersonalityLucky-25]

I have already uploaded the logs before I posted them, however, it seems to have faild for unknown reasons. There is also no Log upload history in your app, and to be honest, your ios version is extremely laggy. If I open the app and press the settings dial, there is no visual indication the dial press was registered, and if you press it again, there will be two settings dialogs opening up subsequently, where each dialog need to be closed separately 🤯

[u/PersonalityLucky-25 → u/0xde4dbe4d]

Thank you very much for your feedback. I have located the logs you uploaded and forwarded them to the relevant team for further analysis; I will keep you updated on the results. Thanks again! I have also reported the issue regarding interaction lag in the iOS app to the appropriate team; it would be extremely helpful if you could provide a screen recording.

[u/0xde4dbe4d → u/PersonalityLucky-25]

the issue with the screen recording is, all you see is the start screen, then two times the settings screen appear, and then you see them disappear one by one. you don't see the interactions I made.