Yarbo still taking old paths after new update

Firmware V3.8.16 Optimizations & Fixes:

  • Fixed a module-route mismatch issue where Yarbo could run routes intended for a different module (e.g. mower executing snowblower routes).

Not fixed my rover with mower, is still taking a path made from the snowblower module. Firmware and app updated, data center restarted (after loss of HaLow after firmware update).

Pathways are universal and not specific to modules. Yarbo will always take the shortest path to and from the work area. I believe this fix is referring to where the rover would encounter patrol lines and follow them even though the SAM was not attached (ex, mower module was attached).

Hi there,

As Bryan mentioned, pathways are universal and not tied to specific modules. So if your Yarbo lawn mower is following general pathways that were originally created while using the snowblower module, that is expected behavior.

However, if the lawn mower is following a sidewalk route specifically designed for the snowblower module, that would be unusual and may require further investigation.

Could you please confirm which specific route the mower is taking? We appreciate you bringing this to our attention and are here to help resolve any issues.

1 Like

@Yarbo-Forum - As I understand it, the bugfix was for Buried Pathways – Pathways made between Areas used by the snowblower that are now buried underneath a big mower Area and have no endpoints in the mower’s Area. The mower was somehow picking up on that Buried Pathway and using it, at least in part. I’ve seen it once or twice. I do not know if that issue is fixed in the latest hotfix - I haven’t been watching closely, and it can be pure luck seeing the bug hit.

@B-Mod - yeah, in general Pathways, Areas, and No-go Zones are universal. “Buried” Pathways, though, with no endpoint in the Area your rover is in shouldn’t be taken right now, but Yarbo still needs to refine the handling of the whole snowblower vs. mower mapping – my map’s a mess and getting worse.

1 Like

Ken - your map is a mess is probably due to all that Guinness! :joy: Just a working theory.

2 Likes

It is taking a pathway that goes through the mower mapped area but does not stop in it. I mapped this mower area, and gave it a path, but it chooses the old snowblower path that goes through the area. I don’t want it to take that path as it is not how I want it to go. Why don’t they just keep the paths, sidewalks, areas all with the module? It would clean things up!

Please leave all routes, pathways, work areas with each module. We don’t need over lap. It just makes things confusing. I mapped a mow area, made a new path for it to get to charger. But instead it is taking a path from the snowblower. The snowblower path goes through the mow area but does not stop in it, so why take that instead of one I made from the mow area? Kinda crazy the mower can just choose it’s path.

We’re really sorry for the confusion this has caused. Based on the current algorithm, all the pathways are shared across all modules, and the system automatically chooses the closest pathway to reach the charger. We understand how this can be inconvenient, and we’ve passed your feedback along to our product department to explore possible improvements. Thank you for your understanding!

1 Like

@bryan.wheeler - It was a bad week to stop sniffing glue.

The map as it is today. I just threw up a little. And to think it’s in my head and makes sense there. In Technicolor. Scary.

With at least two more huge mower Areas to create to blanket the right side, the last of the snowblower Areas will be covered, at which point the map is officially kaput. I am unable to replace any Area I use the snowblower on, as to delete and replace an Area like the little rectangular one right of center would remove Pathways that I cannot re-create, as the endpoints would be within an overlap. Probably Sidewalks as well, and who knows if Edit Area works with overlaps, not sure.

I know Yarbo Dev has this module vs. module mapping issue somewhere on some burner on some stove, probably in a warming oven, hopefully not the broiler way down the bottom that nobody even knows what it is except to store things they don’t use. If it’s not addressed, at least some of my mowing areas likely have to be deleted when the snow flies. Thankfully No-go Zones are all the same regardless of module – and they can be turned on and off anyway.

1 Like

@Ken when you get done with your glue it might just be easier to move! :joy:

@Ken and @bryan.wheeler ,
Would the “Save” and “Restore” feature have any value for this? I’ve only saved maps but not restored.

Save the trainwreck,

Fry anything that isn’t for the M1 and save that,

Restore the trainwreck, fry anything that isn’t for the S1 and save that,

Restore the trainwreck, fry anything that isn’t for the SAM blah blah blah

…and so forth. Then restore the map that’s appropriate for the module.
And have a post-it note that details which one is what.

It currently doesn’t restore NGZ’s, pathways, and module settings (as I understand it). So it would just be blank maps, unfortunately. It has potential to be a solution if those things came back with it.

Makes me question who has the biggest map?

1 Like