Firmware 3.9.16 & App 3.15.4

same on android

@Yarbo-Forum - No. Pattern is set to Checkerboard.

the ticket # is 96063.

Thank you for the clarification. We’ll need to investigate this issue further. Could you please provide a support ticket for this case, along with an estimated timestamp of when you made the adjustment and ran the plan? We truly appreciate your patience and understanding!

@JayWozz - Do you recall if PPP reported boundary issue was dependent on pattern? In another thread, Support is saying they’re aware of the problem only in Spiral pattern. Well, I’m using Checkerboard.

With Yarbos long update circle at the moment, I fear we will get only one more update before mowing season is over in central europe (mid September).

They really need to up their game when it comes to development and bug fixing, instead of releasing new hardware - DO SMALLER UPDATES, MORE OFTEN!

FOCUS on your existing costumer base, get them happy before promising even more stuff for new not yet shipped products (trimmer, M1 pro). Stop luring even more people into this unfinished ecosystem with fancy, polished ads and promises.

You promised us a powerful, hill climbing, capable lawn mower, instead we got a slipping, cluttering, overheating, hardware failing (core), gps resisting, blind on 3/4 of its eyes testing rig.

Please yarbo get your stuff in order and put more people on developing! - FOCUS

I requested the same increase in release frequency and it was quickly shot down by support. They’re intent on sticking with the same failed approach.

I hope Dev puts a moratorium/freeze on new feature development until they can get basic functionality working. There are a number of deficiencies that are more than just lack of functionality, they are basic safety issues.

The way Yarbo will (or is every able to) go outside a work area, can navigate into no-go zones and can freewheel (coast) down slopes (in follow-me mode as well as at the end of every row in a work area) are serious safety issues.

I am astounded there is not an emergency stop triggered if Yarbo wanders into a no-go zone.

Our yard is all sloping and 50% of the work area boundaries are retaining walls or drop offs ranging from 3 to 15 feet down. If there was any documentation that the firmware would even permit autonomous navigating outside a work area or into a no-go zone we never would have purchased this.

I know, I tried tow mode downhill, didn’t know yarbo would not brake, had a little runaway.

Tow mode, another promised, advertised but not yet delivered feature.

Looking forward to the AMA on the 12th,will be an orgy of appologies and promises to do better….

Hi Deixi,

Thank you for your continued support for Yarbo and for your sincere suggestions regarding our current stage. We do understand that we need to fulfill all our promises and are diligently working towards this direction. We appreciate your patience and valuable feedback as we continue to improve our product and services.

I’m still on 3.8 and never put a ticket in… at this point I think I may just wait until the next release to say something, seems as many new issues have been introduced as have been fixed by this one :confused:

Come join the party… :face_with_spiral_eyes:

The zero-turn party :counterclockwise_arrows_button:

So, this is new with the latest firmware 3.9.16 update:

Yarbo has mowed this area 5-6 times, without issue; this is the first time mowing it since the firmware update, and yesterday, out of nowhere, Yarbo thinks there are obstacles where the red patches are (These are the ones Yarbo generates on the fly.) There’s NOTHING there. Just the same grass as everywhere else.

I have it set to “gentle contact”, so it’s not an effect of shadows.

It does appear to have mowed those patches anyway, so no big deal, but this is a new behavior since 9.16.

Anyone else seeing this?

Could be what it thinks is track slippage. Might be something with your IMU. Open a ticket so Yarbo can look into it.

Can’t hurt to clean the cameras. Just a thought.

Did you happen to see if any messages were displayed when the red areas appeared. If you’re set to Gentle Contact, track slippage is my guess.

I didn’t get any messages, no.

Track slippage is unlikely because that area of the front lawn is dry as a bone (no rain, but usually is, anyway) and the grass was mowed a week ago.

I’ll look into it.

Not a bad thought. But it’s set to gentle contact, as I said, does it use the cameras to determine obstacles?

I’ve been mowing all day without a repeat of the behavior, so I don’t think it’s a hardware issue.