Ticket Id #207488 is sitting there without any response for a week..
==== submitted on 6/7/2026
Dear Yarbo Support Team,
I would like to report an ongoing mapping issue that has become increasingly frustrating after several firmware and app updates.
Current versions:
- App: 3.18.5 → 3.18.6
- Firmware: 3.13.11
My current map has been working for mowing operations, and I have multiple saved map backups available (see attached screenshots). However, after recent three updates I have observed two major issues.
1. Map Drift / Coordinate Shift
The entire map appears to have shifted approximately 2–3 feet south compared to the original mapping position.
Because of this shift:
- area boundaries no longer align correctly with physical lawn edges
- no-go zones are no longer positioned accurately
- mowing paths are offset from their original locations
I attempted to use the drift adjustment/calibration functions, but this did not resolve the problem.
The issue is especially confusing because the RTK status appears healthy:
- RTK Fixed
- 20 satellites
- Strong signal
- Low data latency
Therefore, the drift does not appear to be caused by poor GPS reception.
2. WP005 Errors After Editing Maps (Major Issue)
This is currently the most serious problem.
My existing map continues to work.
However, whenever I:
- add a new area
- modify an existing area
- create a new pathway
- edit an existing pathway
the system frequently generates WP005 errors.
After these edits, Yarbo often becomes unable to navigate back to the docking station, even though:
- all areas remain connected
- pathways are connected correctly
- pathway widths follow the documented requirements
- overlap rules have been followed
- docking station location remains unchanged
I have carefully reviewed the mapping instructions and pathway requirements and believe I am following the recommended procedures.
My question is:
Which map definition is actually considered valid by the system?
Because a previously working map can suddenly become invalid after relatively minor edits.
This makes future map expansion extremely difficult.
Additional Feedback
Currently, restoring a previous map backup also restores an older version of the map structure, but I lose many of my current settings and task configurations.
It would be extremely helpful if future updates could allow:
- restoration of map geometry only
- preservation of mowing schedules
- preservation of work plans
- preservation of area settings
- preservation of task configurations
This would make map recovery much more practical.
Attached Information
I have attached:
- current map screenshots
- saved map history screenshots
- RTK diagnostic screenshots
- version information screenshots
Could your engineering team please review my logs and determine:
- Why the map has shifted approximately 2–3 feet.
- Why WP005 is generated after editing otherwise valid pathways.
- Why Yarbo becomes unable to return to the docking station after map modifications.
- Whether this is related to known issues introduced in recent firmware or app updates.
Thank you for your assistance.
==========
Additional observation (6/8/2026)
While attempting to split an existing area and create a new mowing zone, I observed that the new boundary (blue) is shifted significantly relative to the existing boundary (white). The offset is approximately 2–3 feet.
Because of this coordinate mismatch, editing or splitting areas frequently leads to WP005 errors and docking failures.
The existing map still works, but any new modifications become unreliable.
This behavior suggests a coordinate transformation or map synchronization issue rather than an RTK signal problem.
Please see attached screenshot showing the offset between the existing boundary and the newly recorded boundary.
Could engineering review whether this is a known issue associated with recent firmware/app updates?
