Honestly not sure if you’ll just go straight to 3.14.20.2 or if it is a two step update. I guess if you get prompted to update only once, then you in theory got the latest. But, the 3.14.20.2 is scheduled for rollout across a week as well, so support would have to confirm which version you are on (since we can’t see the 4th decimal of the version number).
Open a ticket. I don’t think this was ever stated in the release notes this was fixed.
You need to watch how you type your numbers 
Now do you see the issue? One of my rovers just got a update today, now which one did I just get? How does a person know what firmware they are really on? Why did they not use .21?
Yessir, preaching to the choir. Completely agree it was a poor choice. It actually should’ve been 3.14.22 since there are two changes (presumably from the release notes).
You’re the pioneer, go get um! Tell them about their errors! 
Both of mine are on 3.2.35, yet one only got one update. But it could have been a two update in one update kinda thing, thanks yarbo 
…
I got the patch this morning, and ever since, when I use Smart Vision to remotely drive around, Yarbo immediately loses all data connectivity to Halow.
Data comes back in a minute or so, but if I try to drive again, the same disconnect happens.
Power everything down and pull the battery and power cords on rover and DC for 5 mins and try again. If it still has the issue, I’d open a ticket with some video screen recording of what you are seeing.
Oh, I am and have been.
You forgot to mention that we have to walk around the core 3 times with our hands held together looking up while waiting for it to power back up.
I’m thinking the didn’t include the last .1 because the field that stores the version in the app has a defined length so they had to chop it off. They need to either increase that field or change their versioning standards.
After I updated, the location on the map moved from on the dock to a few ft behind it showed GPS reading that was way off with power signal. I power cycled the DC waited a few then restarted the core. About a minute later, it corrected itself on the map and signal is back.
Yeah, the case is why not use 21 or 22 instead of using 20.2
Mine’s been doing that for the good part of a year.
actually got a new one for another reason, and the new one keeps doing it too.
I think I got V3.14.20.nobody.knows - Did the customary restart everything routine. So far so good. We’ll see what happens on a recharge.
Does Smart Vision over Halow work for you after the update?
Yes it does, on 2 different cores.
Working for me as well. Do a core reboot if you haven’t.
@Glenn.Eldridge - I’ve hired a Witch Doctor and a Shawman to bring the world back into balance ( if it were that easy )