BLUF: My Segway Navimow has generally done a good job mowing my property, but one side of my yard has become a recurring RTK problem area. After repeated storms, the mower drifted outside its mapped boundary, wandered into my neighbor’s lawn, damaged two more sprinkler heads, and eventually prompted my neighbor to place bricks along the property edge to try to stop it. The strange part is that after sending the mower home, letting it sit for about 10 minutes, clearing the mowing progress, and starting over from scratch, it completed the same area perfectly.
This Is Not Happening Everywhere
One of the most important details about this problem is that the Navimow is not losing its positioning across my entire property.
During the July 19 mowing session, the mower completed my backyard and another mowing zone without any noticeable problems. The navigation issue showed up specifically on one side of the house.
That same side has now caused repeated trouble.
- The mower has crossed into my neighbor’s yard more than once.
- It has struck and damaged sprinkler heads.
- It sometimes appears confused when trying to return home from that area.
- The rest of the yard can still mow normally during the same session.
That makes this feel less like a complete RTK system failure and more like a location-specific positioning problem.
Another Week of Storms, Another Navigation Problem
We had another stretch of storms leading up to the July 19 mowing session.
When I finally sent the Navimow out to cut the grass, it once again drifted into my neighbor’s yard.
I have noticed this type of behavior after periods of heavy weather before, although I cannot say that the storms are directly causing the RTK problem. What I can say is that there appears to be a repeating pattern worth documenting.
The mower was operating normally in other zones, but when it reached this particular side of the house, its boundary accuracy was clearly off.
It Ate Two More Sprinkler Heads
The navigation error was not just cosmetic.
During this session, the mower damaged two additional sprinkler heads.
One sprinkler body was completely pulled from the ground, which means the mower did more than simply brush against it. Once a robotic mower starts operating several inches or more away from where you expect it to be, objects that were safely outside the mowing path can suddenly become obstacles.
This is one of the reasons I think long-term ownership reports are more useful than first-week reviews. A robot mower can perform beautifully most of the time and still create expensive or irritating problems when its positioning becomes inaccurate.
The Neighbor Problem Has Escalated
This issue has now gone beyond damaged sprinkler heads.
Because the Navimow has repeatedly drifted onto my neighbor’s lawn, my neighbor eventually placed bricks along the property edge in an attempt to physically stop the mower from crossing over.
That is a pretty significant real-world consequence of virtual boundary drift.
The entire point of an RTK-based robotic mower is that physical boundary wire should not be necessary. When a neighbor feels the need to create a physical barrier because the mower keeps entering his property, something is clearly not working the way it should in that specific area.
And to be fair, I understand his frustration. Regardless of why the positioning error occurs, my mower should not be cutting his grass.
The Strange Part: A Simple Restart Fixed It
After finishing my trimming around the yard, I sent the Navimow home.
I let it sit for approximately 10 minutes.
Then, instead of continuing the existing mowing session, I selected the option to Clear Progress and Start from Scratch.
I sent it back out to mow the same problem area.
This time, it performed perfectly.
No wandering into the neighbor’s yard. No obvious boundary errors. No strange navigation behavior.
That makes this problem particularly frustrating because there does not appear to be a permanent mapping error. If the map itself were simply wrong, I would expect the mower to make the same mistake every time.
Instead, it can fail badly during one session and then mow the exact same area correctly after restarting.
A Troubleshooting Step Worth Trying
If your Navimow suddenly begins mowing outside its normal path, I would try a simple reset before immediately rebuilding your entire map.
- Send the mower home.
- Allow it to sit for several minutes.
- Clear the current mowing progress.
- Start a completely new mowing session.
- Watch the problem area closely during the first pass.
In my case, this restored normal operation without remapping the yard or changing the RTK hardware.
That does not explain why the positioning error happened, but it did get the mower working correctly again.
What Could Be Causing the Problem?
Because the issue is concentrated on one side of the house, there are several possible explanations.
- Reduced satellite visibility in that section of the property.
- Signal reflections or multipath interference from the house or nearby structures.
- Trees, foliage, or other obstructions affecting positioning.
- Temporary RTK degradation after periods of severe weather.
- A software or session-related positioning error that clears after restarting.
I am not claiming that any one of these is definitely the cause. At this point, I am simply documenting what I am seeing during normal ownership.
What I Have Learned From Owning the Navimow
The Navimow can be incredibly impressive when everything is working correctly.
Most of my property is handled without problems, and even this troublesome section can sometimes be mowed perfectly.
But RTK positioning is also one of the most important parts of the entire system. When the positioning is wrong, everything downstream becomes wrong too: boundaries, obstacle avoidance, mowing paths, sprinkler clearance, and neighboring property lines.
That is why occasional RTK drift is not a minor inconvenience.
In my case, it has already resulted in damaged sprinkler heads and a frustrated neighbor.
The Real-World Takeaway
I am not ready to say the Navimow is unreliable overall, because that would not accurately reflect my experience.
Most mowing sessions are still successful.
What I am seeing is a recurring navigation weakness in one specific part of my property. Sometimes it works perfectly. Other times the mower seems to lose enough positional accuracy to cross a boundary it normally respects.
The most useful discovery so far has been surprisingly simple: send it home, let it sit, clear the mowing progress, and restart the job from scratch.
At least for me, that has restored normal operation without rebuilding the map.
I will continue documenting this issue because long-term behavior matters far more than how a robot mower performs during its first few days out of the box.
Final Thoughts
A robotic mower should make lawn maintenance easier, not create a property-line dispute.
My Navimow still does plenty of things well, but the repeated RTK drift on this side of the house has become one of the biggest issues I have encountered during ownership.
When your neighbor starts putting down bricks to keep your robot mower out of his yard, the problem has officially moved beyond a software quirk.
For now, I am keeping a close eye on that section of the property and using the clear-progress restart whenever the mower begins behaving strangely.
This is exactly why I document technology after living with it for months. The interesting problems rarely show up during the first weekend.
