Hotfix Update: Firmware V3.13.7 & App V3.18.4

Pretty sure this update broke my Yarbo Saturday. App just reports network issue now and can’t connect to it at all. (Ticket #198849)

Have you tried resetting it? I updated it and had no network issues.

Unfortunately, after installing the update this morning, I did a quick check and Yarbo is still incorrectly planning to cut directly through a no go zone. No bueno :frowning:

Wow. This was the primary reason the for the hotfix. Do you have a ticket open to update the status?

I got the update this morning but haven’t tested it yet.

Could it be that it’s memorizing the old path? Have you tried changing it in another way and then trying to restore it to the current programming?

Yea, I was quite surprised when I did the quick test and the pathing still went straight through that NGZ. Might be good for other people to do a quick check like I did.

I don’t want to modify the zone or Workplan at all - I think it’s best to preserve the settings & plan as-is so Yarbo Support can determine why their hotfix didn’t resolve the problem.

Next I’m going to try actually running the plan and see if that NGZ transgression still shows up.

You can always save the map first and test it. Do as you like, but I wouldn’t want you to have to reset the work area for it to take on the changes, or maybe the app will show the map with the previous rules saved.

I have noticed the Previews and actually running the plan don’t always do same thing.

The concern would be that all the area settings don’t get retained with a map save/restore. If a setting is causing the issue it could get lost in the restore.

If the settings are not retained, it’s another big problem because then saving is useless… it has never happened to me so I didn’t know about this problem… it should be reported if it’s true

The map backups have been like this since implemented. I agree it’s a problem.

I don’t understand why this has never happened to me with the reset…it’s very strange

Ok. Next test completed. I actually started that Workplan to see if the path planning would remove the NGZ transgression. It did NOT. So with Yarbo actually running the Workplan, it still planned to drive through the NGZ.

Ticket #199175 opened.

This explains my situation - mucho no bueno!

Also - some further new problems, now in a wide-open yard it says a vehicle is blocking the path.

Anyone else having gps issues since the update?? My Yarbo went out for it’s scheduled mow that’s it has done before. But it keeps pausing, sometimes for over 45 minutes, waiting for a gps signal.

How might I fix this?

Photo of details

very strange…you can try to reboot the datacenter or otherwise set navigation without GPS

What does your DC scatterplot look like? Right now seems like a potential issue with your right side antenna.

that it has loosened?

It potentially has loosened or the cable inside the core connection has loosened. Other potential is it was bumped against something and damaged it (even if not visibly).