After the last update, Yarbo now sees a vehicle as it drives right up to the docking station and stops right in front of the dock. I have not moved anything. I do have the dog house over the dock, but it has been there since day one in January. I don’t want to turn off vision or whatever as Yarbo has to cross my driveway on the way to the dock.
I am moving the dock to a new location as where it is now it a mud pit since Yarbo killed the grass in front of the dock. Yarbo’s new spot will be paved with paving stones to hopefully fix that issue. But I plan on the dog house cover as I don’t like my stuff sitting outside for no reason.
You could try the no vision zone as Ken suggested. Put it over the spot where Yarbo is stopping. The other thing you can do is to turn off obstacle avoidance for that pathway to your dock. It’s under the pathway settings.
You can’t do it with the blower. But you can turn off obstacle avoidance on the blower. You can create a no vision zone with the SAM module or the mower.
Ok I did this, but can not get yarbo to start a plan, it thinks it sees a vehicle. If I manually drive it off dock, then start plan it is ok. I do have a dog soft shelter over dock, but it has been that way since day one. The blue box extends at least 8 feet in front of yarbo dock. Nothing there but grass and a tarp building to the right that has been there since day one also. I have had other false vehicle reports lately and either there is a tall weed, or it is going down a sidewalk and thinks there is a vehicle on the side walk. The pro mower seems to be some of the issue.
No I have not disabled that as I don’t want Yarbo to run into a real vehicle. The for sure broke something in that last update. On the last livestream I posted a few times the question of when is and what might be in the next update, they skipped right over those questions.
Is your dock and dock pathway near vehicles? Makes sense not to if so. Otherwise it could be a temporary work around. In theory that’s what you did with the no vision zone. It just doesn’t appear to be working for pathway obstacle avoidance. If you have the pro, you can disable vision vs ultrasonics independently. So you could leave the ultrasonics enabled.
As for releases, they don’t like to commit to dates until they are done wrapping up testing. Things can slip pretty easily and people get disappointed. However, I could’ve sworn they said on the live stream it would be early next month (round about).
Yeah all but two pathways from dock go about 30 feet in the grass, and then cross my driveway, and drive up my sidewalk. And then further, some cross my second driveway and parking lot area for my shop.
In the next few weeks I will be moving the dock and redoing all pathways, so I don’t want to do too much changing stuff for only a short amount of time.
Just seems so odd they can do an update and break charging. I used to be able to just send it out and mow, but now I have to babysit it every time it goes out and comes back. Even worse is when it goes out all the way across my property only to see a weed it thinks is a vehicle, and then without warning drives all the way back to the dock, and then fails to dock as it thinks there is a vehicle on the charger.
Yeah it is still a beta feature and they keep tweaking the vision algorithms. Have you opened a ticket on it by chance? They might be able to offer a solution we haven’t thought of or use the logs to train it to ignore the false positives.
I get frustrated that I try to open a ticket, and the first thing they want is a video of the issue, lol. I have enough of an issue baby sitting it let alone running out to video it just stuck on the charger. The Chinese really like to see videos, lol.
It honestly is the easiest way to get the whole picture. You put that with a timestamp down to the millisecond and they can really hone in on the logs to see what happened. Trust me, as a tester, it really helps when you can capture the issues on video for them. You can only get but so much staring at a log and the log isn’t always going to tell you something accurately if there is a software bug of some sort. The log said X, well the machine did Y. Hard to deny video proof it did Y.
But here is the problem. I don’t work for Yarbo. I should not have to spend my time doing beta testing for them with nothing in it for me. I bought this product with all their promises of how great it worked, and then it arrived and I found out most of the “tech” in it did not even work, it was all going to be fixed in the “next” update.
I really think they need to start over on their team that does software, there is just too much that is wrong, and then a long awaited update makes it worse.
The college I work at has a Yarbo, I got them to buy it. I can’t go more than a few days sometimes that I have to keep an eye on the data center and reboot it because the the halo drops out. Had a video meeting between our IT dept guy, Yarbo two techs, and I. Told them about the random IP address issue they have. They wanted proof, we gave it, and then they (yarbo techs) talked to each other before, they told us that it is a known issue and it will be fixed in the next update. Guess what that was in May or early June, still no fix. We have a very high dollar POE switch, I had to turn of POE on that port, plug in the crappy Yarbo POE injector, bring a wifi plug in switch from my house to control the rebooting of it as the IT guy was getting ready to kill me asking him to cycle the ports power to reset the data port. Now I have to keep an eye on it everyday. Great tech Yarbo!
I really like Yarbo but they need to clean things up!
I get asked all the time about the Yarbo product, I don’t know who I could recommend it to.
Bryan this is no dump on you I appreciate the help and recommendations! I just needed to vent some of my $8000 investment that now can’t cut the yard without me driving it every time, on or off the dock.
Completely understand. Trust me, they read it all and do act on most things (within reason of course). It just takes time, unfortunately. Here is a screenshot from their FB group about some of the upcoming software roadmap. There is a DC update next month. It’s possible that might fix the issue you mentioned. If you still have a ticket number for that, I’m sure @Yarbo-Forum could maybe check on that and see.
@B-Mod
We’re very sorry for the inconvenience this has caused. We understand the frustration, and we know improvements are needed to reduce false detections like this. Please rest assured that our team is actively training the visual segmentation model with a larger dataset to improve accuracy.
In the meantime, we’d really appreciate it if you could submit a support ticket regarding this issue so we can investigate further and provide more targeted assistance.
