Huh .. it’s funny. This morning I had the update notification in app. I let Yarbo update the firmware. It did … But the firmware version in app still shows 3.13.15 (same shows in diag tools)
Yarbo rolled back latest firmware? Ir just app is glitching?
I’m sorry to hear that you’re experiencing more missed patches and stripes after the update. Thank you for sharing your feedback with us. I’ll make sure to pass this information along to our team for further review.
If it’s convenient for you, could you please submit a support ticket for this issue? I’ll help escalate it to the relevant team so they can investigate further.
Thank you again for your help and feedback. We really appreciate your support in improving Yarbo.
Sorry to hear that you’re experiencing this issue. Thank you for sharing the details with us. I’ll make sure to pass this feedback along to our team for further review.
Besides, could you please submit a support ticket for this issue? This will allow our support team to collect more details and investigate further to better understand what happened.
I see the same.
Yes, “overcorrects” is the word. I used to have Yarbo drive near the fence. But what it would do when it would see a fence post is not just drive around it, or just veer to avoid it. It would go so out of its way that when it would try to get back into line, it would now be almost 90 degrees facing the fence. Once it realized it couldn’t push the fence it would give up.
What could have been solved with a simple 10deg path change turns into a work-stopping cluster. So I don’t have it work there anymore. Yarbo’s path navigation algorithm really needs an overhaul. But it does the job for now, even if it seems a bit drunk when it does it.
Agreed, I think feedback and ideas really drive the end progress. Knowing it is a test and at least being able to work through what works, not, and work around helps developers. Otherwise they are built only for the scenario the developer thinks it will be used…
I turn it off, but use the vision areas in certain spots I am worried about antenna decapitation
Thanks @ Yarbo-forum. Before issuing a ticket, I will do some more testing.
I believe it has to do with vision and obstacle avoidance. I have also a new issue that it says the front camera is blocked although nothing is in the way, and it is clean. Once finished with this schedule I will do a reboot and see what the result is.
I did turn vision off for the moment and all works perfectly. I never had this issue before which makes me believe it is related to the latest update.
Anyone else experiencing this with the front camera?
Make sure it’s not got a speck or something very hard to see on it. It can be a little picky about it. Will also say this if it’s seeing a solid dark contrast like when it’s at the base of a hill. Generally it will clear on its own if it’s something like that.
Thanks @bryan.wheeler . I will check this. I think you are right with the contrast issue. I just noticed that this morning. But not sure if it clears on its own. I will keep testing.
Allowed the core to update to 3.14.0 this morning and now get “Power Board Issue” message that wasn’t there before.
@Yarbo-Forum - What do you mean “in a future update”? This requires a hot fix and timeline for release! I can no longer mow my yard without manually changing the speed in the MIDDLE OF EVERY PLAN. This is totally unacceptable! Worst case, I need some kind remote fix done to my machine to stop this behavior.
To me, the response you received is exactly what we should expect and desire.
They’ve determined that the issue was caused by a bug. So now the devs can work on a remedy (hotfix). They likely don’t have a timeline yet, because they need to add it to the backlog, prioritize it, determine level of effort, test, etc. so I wouldn’t be concerned that they didn’t say “we’ll have a fix next week”.
In general, hotfixes have been coming pretty regularly as of late. Hopefully this will be resolved in short order.
I read the response as this will be fixed in the next hotfix release.
They have replied again to the ticket and are rolling my firmware back. THAT is an acceptable solution until this resolved.
I didn’t see Hot Fix anywhere in the Yarbo’s response. “in a future update” could mean 6-months or a year from now.
I’m still curious why I haven’t see other reports of this issue.
Honestly you got me too scared to try tow mode after what it did to your core. If it ever rains again, I want mine to cut grass. I don’t want my new core using my wire fences like a cheese grader…
I activated tow mode on mine and am not seeing this. So it may not be the catalyst.
That’s a good interim solution.
So my app updated to the latest version but not the core yet. Whenever I try to make changes to any yard mapping I get the following error message. “Request failed, please check your network.”
I have tried with Bluetooth enabled/disabled, wifi enabled/disabled, and switching between netRTK and the DC.
This definitely started after the app updated. Could it be a version mismatch since the core didn’t update yet?
No, the app is compatible with the older firmware. Unless your firmware is really old. Try a restart of the core. Also make sure the app is actually connected to the core and not offline in the background.