Thanks so much for sharing your experience and for taking the time to write such detailed feedback — it’s really valuable. Your suggestion about having clearer mapping guidelines makes a lot of sense, and I’ve shared it with the relevant team so we can look into improving that.
As for the issue you described, we generally recommend avoiding overlapping areas when setting up your map. Overlapping parts can sometimes cause unexpected behavior during operation, so it usually works best to keep areas separate and connect them using pathways instead.
Both mapping methods are supported — you can either create one long pathway that links all areas, or multiple shorter pathways connecting just two areas at a time.
From what you described, it sounds like the overlapping areas might be the cause of the “dancing” behavior. If you’re open to it, we’d be happy to take a closer look — please consider submitting a support ticket so our team can review your map details and help you troubleshoot more precisely.
Thanks again for your thoughtful input — feedback like yours really helps us keep improving Yarbo for everyone!
Thanks for your message.
Overlapping is absolutely required and should not raise any issues if its allowed on the map. If app allows such mapping yarbo should handle it properly or such cases should be blocked in the moment map is created (like this is done for my Mammotion lawn mower).
Lets discuss real life scenario with parking space for 2 cars and yarbo.
My car parking spot consists of 2 parking spaces and the road.
I mapped this area as multiple overlapping areas and I am using one or another area while triggering Plan based on the situation on the ground.
Area0 is complete Parking area and is used if no cars are parked. Area1 is area on the top of Area0 and is used if 1 car is parked. Area2 is area on the top of Area0 and is used if another car is parked. Area 3 (road) is on the top of Area 0 and is used if 2 cars are parked etc. All areas are intersecting and there are 2-3 layers in the same spot tagged as Blower area. Areas 1,2,3 also intersect on the borders.
And even more areas will be created on the same spot and will be tagget as Snow Blower areas later.
The following plans are executed based on scenario:
Plan 0 - no cars parked, Process Area0 black
Plan 1 - car parked in area1 green, process area2 yellow and area3 blue
Plan 2 - car parked in area2 yellow, process area1 green and area 3 blue
Plan 3 - 2 cars are parked, process only area3 blue
I plan to fully automate Parking space processing using HomeAssistant (HA): detect occupancy by hikvision cameras and trigger corresponding yarbo plan using API (hope it will arrive soon).
For example integration for Mammotion Luba2AWD is already available for Home Assistant and I am using it for many automation scenarios for example lawn watering (sparkling) of required area is stopped in the moment robot is entering this area, this is fully automated and I should not worry about it anymore etc.
PS for Yarbo. Please note, I am not comparing solutions, I am focusing on the best ideas implemented by different companies and trying to combine them to get perfect and convenient solution for my property.
I have set up a similar scenario - I have multiple areas created in my driveway for the snowblower that I can select based on how many cars are parked in the driveway at the time.
I also created multiple areas at the end of the driveway to deal with the mounds of snow that will quickly accumulate from the town snow plow.
Thanks for sharing experience, nice to hear that the same approach works also for snow blowing and is used by other users.
I will face first winter with Yarbo in next months. Snow blower is my main purchase point of yarbo and I hope it will meet my expectations.
Thanks for advice. I pressed Pause today immediately after it started to Dance without waiting for the error and clicked Resume in few second later. Yarbo continued work, crossed intersection of areas in one go and moved to the next area immediately as expected.
Dancing loop is 100% bug in software.
I started to observe closer and checked dancing in the other area. Actually during dancing yarbo in the app continues to work and mark lines in the area as expected but on the ground it rotates in circles completely in different location.
Tried to repeat this issue but ended up dancing only and obstacle error (same location in app as on the ground). Trying to record the issue now to submit.
Thank you so much for sharing your detailed use case — it’s really helpful for us to understand how you’re using Yarbo and how Home Assistant integration could make your setup even more convenient. We can absolutely see how having Yarbo as part of your automated system would bring more flexibility and efficiency.
We also appreciate you submitting a support ticket regarding the “dancing” behavior. Our team will review your case carefully to investigate whether there are any software-related issues or potential improvements needed.
Thanks again for your valuable feedback and for helping us make Yarbo smarter and better with every update!
Support processed my case really quickly. I opened ticket yesterday around 19CET, got first response immediately in 1.5h about forwarding my case to tech department and received final response today before 11CET. Great.
”This situation has already been identify and it will only happen with Leaf Blowers that navigating between 2 areas, it is already been repaired and schedule for update in the end of this month.”
Looks like it works as expected. No more dancing on transition between overlapping areas.
My Global Plan (includes ~10 areas) completed fully without interruption today.
I see that Yarbo left and returned to the docking station after the successful Plan finally (first time in my property).
PS It will be very useful if Yarbo will implement simplified transition between intersecting areas:
Transition between intersecting Areas in any point (shortest) if pathway is not created
or by pathway if its created (force yarbo to move between areas in specified place by pathway).
