+7

2017.28 c528869

James 2 years ago updated by appleguru 2 years ago 15

With the new release of 2017.28 c528869 Tesla has changed the formatting of the version number.  Since the numbers and now letters used to display the version do not align with the prior formatting, TeslaFi's firmware tracker is not displaying the order correctly.


Before making changes to the tracker I would like to wait to see how the next version is formatted.  The main reason is that many of the TeslaFi vehicles being logged are reporting the initial install as being 17.28.27 but then within seconds or minutes the version changes to 2017.28 c528869.  These vehicles that happen to poll data before the version changes to 2017.28 c528869 are showing two software updates right next to each other.  If TeslaFi doesn't poll data until after the version changes then only one update is being logged, 2017.28 c528869.


So...do I toss out the 17.28.27 version number from the tracker display and only show 2017.28 c528869?  Do I keep both and have rather confusing data since it appears many cars updated twice?  Do I change the display to show 2017.28 c528869 as 17.28.27 and keep things uniform?


I think the best thing to do is wait and see what the next version number format is going to be.  And see if they are installed as two version numbers as well.  Perhaps this was a one time formatting, or perhaps not.


If anyone has any suggestions I'm always happy to hear them.  


Thanks,


James

+1

Let's wait and see what the next version shows up as

+3

I would opt for having the data displayed "as is".


You will probably never get official specs for how the version number is supposed to look or what the format means. So trying to guess is prone to being wrong. Also there is no way anybody else than Tesla can make things uniform.


Please just report the status quo and let everybody come to his own conclusions.

I agree with posting the version verbatim. I think we’re all hoping for some kind of consistent sequential increment that’s helpful to owner, but that may not be the case. It may be the result of a change to their build tracking system.

+1

wild guess here, "c528869" looks like a specific hotfix number accidentally displayed to the end user.  IBM/Lotus used to follow the x.x.x pattern and the support hot fixes were always longer strings. Each release would contain hundreds of individual hot fixes. If the software showed the string, support would know it's a special pre-release hot fix, or a hotifx that was not going to be included in the general release.  If this developer concept is true, then they will quickly roll out the full release and go back to the standard scheme.

+1

This is exactly what I meant. I don't mind everybody doing his wild guesses - but I'd rather not be impacted by them.


Looking at the numbers I can see that this is a wide release that is not specifically targeted at a small group of users.


Please report just the facts.

+2

I think I found a query logic to break down the version numbers into three parts and sort them individually which shouldn't break even if the next release version reverts back or contains both formats.  It's live now.

Seems to be working and sorting well! Nice work :-)

I noticed that while v 17.28.27 shows up in the "Latest Fleet Updates" table, it doesn't have its own version-specific table below, nor does it show up in the "TeslaFi Fleet Totals" summary tables.

@mkolowich that's likely because no cars are actually running 17.28.27

Hmmmm...why would there be 60 installs, including several today, if nobody's actually running 17.28.27?

+1

@appleguru is correct.  Per my initial post:


many of the TeslaFi vehicles being logged are reporting the initial install as being 17.28.27 but then within seconds or minutes the version changes to 2017.28 c528869.  These vehicles that happen to poll data before the version changes to 2017.28 c528869 are showing two software updates right next to each other.  If TeslaFi doesn't poll data until after the version changes then only one update is being logged, 2017.28 c528869.


Got it.  I can see that -- there are paired records in the fleet updates that appear to show two consecutive upgrades -- one to 17.28.27 and the next to 2017.28 cXXXXXX.  Sorry for the confusion.

+1

From personal experience, the updates installed as two separate updates on my vehicle.  I was out of town over the weekend and got two update notices and when installing, got two prompts for updates.  One right after the other.

Thanks.  That's good to know.

I only got one update notice, and the second update was applied immediately following the first automatically.