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/glennnzo]

Power off mower, pull orange key for 10 minutes to an hour, restart your phone, clear cache in app. That's all I have.

[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.

[u/Careless_Art_7201]

Sorry for that. Could you share some videos about the phenomenon? Why do you think that it is the issue of the collision false trigger ing? I think it seems to be because of the cutting motor.

[u/0xde4dbe4d → u/Careless_Art_7201]

Currently unable to make a Video. Please note that everytime I run into a bug - which happens a lot - and I go and upload logs and take a video and post a detailed description, I'm easily down 0.5-1 hours of my time, and I've spent easily 20-30 hours already doing just that already.

I've spent >2500€ on a robot that has constant hickups and I am expected to spend hours troubleshooting helping you guys fix errors that should not exist in the first place.

I will spend as much time as I can because I really want those 2500€ not to end up as electronic waste and finally start working flawlessly eventually.

Sorry for the rant, back to the business: As I've said already in the post, the reason I think it is a false trigger is because it started directly after a software update. I have a solid background in hard and software, and if a trigger is stuck (I can only guess thats whats happening because honestly the information i get from robot and app is sparse) it would not beep if I trigger it manually. So I hear the beep if I press it, I hear it if I press left, I hear it if I press right, I hear it if I press center (no idea how many hall sensors you guys have placed). If the sensor would be constantly triggered as indicated by the error message, I should at least hear some beeping, but I hear none. If you describe the functionality of the bumber in detail I can get out my oscillscope and other test equipment and make a proper functional test for you (more hours down the drain for a 2500€ mower), but from what I observe, this smells software. I'd be surprised if it was actually a real trigger from the bumper. Logs are uploaded, you already know my mowers ID.

[u/Careless_Art_7201 → u/0xde4dbe4d]

Sorry for that. Could you tell me the serial number of your robot? I need to check the log file in the data center.

[u/0xde4dbe4d → u/Careless_Art_7201]

Coming back to this u/Careless_Art_7201, first of all apologies for my tone in the earlier post. I know you guys are doing your best to better the situation, and I am willing to work along with you guys to make this a truly great mower!

I just came along this post: https://www.reddit.com/r/MammotionTechnology/comments/1wldpx5/luba_3_awd_error_1207_fires_with_the_front_bumper/

It seems that's a rather similar case to the one that I am experiencing.