Yarbo needs to keep the map, module data, schedules and workplans regularly backed up to the cloud, so that core replacement does not need remapping (or involving support to move the maps which takes multiple days).
Replacing the core or any modules should just sync with the cloud and download the user selected backed up map data to facilitate prompt setup.
Ideally, cloud backup should also have an opt-out option for those who value privacy over the inconvenience.
This really came to light for those of us who mapped for the snowblower in the winter and then started mowing, plopping mowing Areas fully overlapped on top of snowblower Areas/Pathways/Sidewalks. Yarbo’s one map handling multiple modules became unworkable, at least for me. A way to back up (and import) EVERYTHING the App knows, even locally, would have been helpful as a way to keep multiple sets of maps, as a backup mechanism, and, possibly, to move maps/settings/work plans/schedules to a new core.
Yarbo development is investigating ways to have a map that address my use case. They have mentioned filtering and the ability to have workable Pathways in overlapped Areas, but I have no details or a time frame. I made my snowblower Areas/Pathways/etc as complete as possible before mapping for the mower, but I would like to make a few changes and may need to delete part of my mowing map items to do it.
So, yeah, a full backup (map, Work Plans, Settings, Schedules) would have been great to do after the winter was over, but that capability isn’t there except for just bare bone mapped items (from what I understand).
There is legislation and other regulations that make this extremely complex for a global company. But, yes for those countries that allow this, I believe it would be a good option. As you said, optional but it should be not opt out but an opt in.
Add the ability to back it up to the Yarbo app on your phone. Gets around most countries legislation.
I’d love to see the ability to back the map up somewhere locally or cloud based that can be reloaded if a module/data center is replaced instead of having to go through the entire mapping process again.
Thank you for your suggestion!
We understand how helpful cloud backups for maps, module data, schedules, and work plans would be—especially to make core or module replacement much easier.
We’ve shared your idea with our product team, including the option to opt out for users who prefer more privacy.
Thanks again for your feedback—we really appreciate it and will continue working to improve the Yarbo experience!
My mowing map has grown quite complex and getting more so as I refine it to make the unit more autonomous and it’s plans more resiliant. I’d really hate to have to recreate it should the DC failure!
Having a backup that I could restore after a DC failure or relocation would be great!
If your data center fails, you can initiate a “replace data center” in the app and you won’t lose your maps. It does warn you that it will erase your maps but in this instance it won’t. A “reinstall data center” will erase your maps. Relocating the data center changes the reference point location and invalidates the calculated maps.
For future reference, maps current and saved are stored on the core. If you require a core replacement and your old core is still accessible, support can typically copy the maps from the old to the new core.
I’d like to have an option to export/ backup maps using absolute addresses rather than relative ones. (Import/ Restore should convert from absolute to relative addresses as needed. )
This would make the whole mapping topic much more resilient.
If Yarbo will provide access/ documentation regarding the maps, I strongly suspect someone will develop such a utility.
@bryan.wheeler - Yarbo just said that the maps (or maybe it’s the backups) are stored “in the App.” I’ve added a question about that to the thread. I thought the maps AND the backups are all on the rover, yeah. Holy single point of failure, Batman!
I can most assuredly confirm they are not stored in the app. Delete your app and see if your maps are gone. They are absolutely stored on the core. This is why a new core will be completely blank when you get one and why support has to have the old core online and accessible to the Internet in order to copy the maps from one to the other. Where did Yarbo state this? Happy to ask for clarification from them.
This one, @bryan.wheeler: Upload/Download map
If you look, what Yarbo Official said was that you can ‘save your map locally’. They never specifically said anything about the app. ‘Locally’ means on-robot from their perspective. Just not very well written.
Yep, I agree that’s what they meant. @Ken
@rgloverii - We’re looking at different places, hence the inconsistency, I think.
What I saw: Firmware 3.9.10 & App 3.15.3 – Feature Highlights
…which you always could (Save Current Map). So “what changed”? They limit you to the number of maps and auto-save one you edit. Else the maps are where they’ve always been – on the rover, which I guess is “locally”?
“Locally” to me means “on my phone.”
Ahhh, GUI. And words and stuff. 
You lose a lot in translation between all the languages they have to convert for too (global company).
@Ken your brain “read” what it wanted to hear. 
@ken.w.gregory my brain is “fed” with plenty of beer? What an odd thing to say. Anyone else use a Taryl Fixes All bottle opener fridge magnet?
Translation please
I feel threatened by a bottle opener…
