False Collision detected error - no way to clean up, driving backwards 10m was not helping,
driving backwards is also is not good practice and this is not always possible if false error occurred in front of the wall. What is the point of Clear error button if its not used to clear real error.
Restarted Yarbo - front camera disconnected, started to move snow without auger turned on as plow, can not start it also manually from remote. Auger should be checked before starting to move, there is mic installed (noise), there is specific current during rotation.
Restarted Yarbo second time. This time all is ok. Resumed operation.
It should be extra option to clean U turn places at the end of the plan as yarbo moves snow by snow tracks here.
If All U-turns are done on single lines this line should be cleaned up at the end of the Plan or configurable number of perimeter laps option (as in my other brand lawn mower). I will try to do workaround with sidewalks for now.
Snow Blower is also not working to the edge (better than Plow but not always as expected). So both options to increase the decrease Area are required as in lawn mower. Currently only safety buffer to decrease area is available. Extend Area Boundary is not present.
Many short lines result to the dancing of Yarbo. Many unnecessary motions without result.
I believe better result can be achieved by continuing short lines to the long lines and always work end to end instead of many turns within short space. Actually people who work with manual snow blower, manual lawn mower know this in all details. Maybe Yarbo development team should do manual snow blowing and lawn mowing for a season to get new improvement ideas for yarbo behaviour and work plan.
SlopeModeBeta - is not unit tested by developers, how this is possible to deliver untested feature? Currently Yarbo Snow Blower moves snow (like Plow) uphill without auger off and is doing regular snow blowing with auger on downhill. According to the comments on the forum initial idea was that Yarbo goes uphill using the line already cleaned and is doing snow blowing only downhill, but this is not the case.
PS Finally all areas are mapped and tested. Hope items below will be resolved one day, especially fake Collision reset issue.
Hi there, thanks for the detailed feedback! We really appreciate you taking the time to share your experience. The false collision detection issue may require further investigation from our team.
Regarding your suggestions about U-turn cleanup, boundary handling, and Slope Mode behavior, I’ll pass these along to our product team for further review. We agree that there is room for improvement, and your feedback is very valuable for helping us refine the user experience.
Snowblower collision is caused when robot raises the blower either too fast or too far and for whatever reason it determines it has collided…
Restarting robot appears to be only way to “ fix “ this …. Sometime restarting needs to be done multiple times as it will lead to “ front camera failure “ .. .. entire blower having no power etc…
For collisions you generally have to reverse the robot for the error to clear.
For your other issues, if you haven’t heard ready to work and are watching the app while it’s booting, you can observe weird issues while it’s still stabilizing.
However, I’d recommend opening a ticket and note the times of your issues so they can look into it further. Might be something deeper going on.
Ya for whatever reason this is a self inflicted “ false “ collision due to the height the snow blower self raises…. Either it goes past full height or keeps trying to push it up.. not sure … but once it happens the blower module won’t respond…. The reboot does a raise lower maneuver during startup which clears it but then its normally front camera error and the entire blower module has no power until you restart a 2nd time…. Takes f o r e v e r ….
That’s not normal at all. Does it seem like the auger is getting raised higher than it should be? Like a limit switch or other sensor might be out of adjustment?
Either way, raising the auger shouldn’t cause Yarbo to think a collision occurred. So something’s certainly amiss. If you haven’t already, open a ticket so they can look into it. Hopefully it’s a quick fix.
Hi there, could you please submit a support ticket for this issue? Our support team will be able to look into the details, identify the cause, and help provide a proper solution.
