I happened to glance at my PVOutput log and noticed that my Powerwall had been offline for a few minutes. So I checked the software version and it's now 20.40.1. That's a big jump in the numbering from 1.50.1 and would suggest a significant change. I wonder what? Needless to say, the revision log hasn't yet been updated.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Software Version 20.40.x
- Thread starter JohnRatsey
- Start date
It's possible they are just changing the version naming system so that it matches the one used by vehicles. v1.50.1 doesn't indicate the year or week so it's difficult to know how old the version is.
Back in 2016, Tesla had version numbers such as 2.50.114 for vehicles but then at the beginning of 2017, they changed to the YY.week.release version number such as 17.3.15 (where YY is the 2 digit year). Later in 2017, they changed the version to YYYY.week.release such as 2017.32.6.
With a version of 20.40.1, I would assume that it was the first version released released in the 40th week of 2020.
Back in 2016, Tesla had version numbers such as 2.50.114 for vehicles but then at the beginning of 2017, they changed to the YY.week.release version number such as 17.3.15 (where YY is the 2 digit year). Later in 2017, they changed the version to YYYY.week.release such as 2017.32.6.
With a version of 20.40.1, I would assume that it was the first version released released in the 40th week of 2020.
Perhaps this different software to provide extra functionality for the Tesla Energy Plan . However, Tesla normally seem to prefer to support all requirements for all market countries within the same software and someone in California reported receiving 20.40.1 . Maybe our Powerwalls are being used to test some unknown features.
woferry
Member
Probably Gateway2 vs. the original Gateway? Pretty sure they're different enough that they'd have to run different FW.
My PW was installed in March 2018 with a grey box gateway which, I think, is version 1.
Moderator note: This post (plus the 7 following posts) were merged in from another thread.
My gateway (v1) updated its firmware about an hour ago. The Powerwall release engineering folk must have changed their versioning schema because we went from 1.50.1 to 20.40.3. I wonder if they're adopting the same numbering as the vehicle software (the vehicle software used the last two digits of the year for a few months in 2017 until they switched again, to using all four digits of the year).
No release notes yet.
Bruce.
My gateway (v1) updated its firmware about an hour ago. The Powerwall release engineering folk must have changed their versioning schema because we went from 1.50.1 to 20.40.3. I wonder if they're adopting the same numbering as the vehicle software (the vehicle software used the last two digits of the year for a few months in 2017 until they switched again, to using all four digits of the year).
No release notes yet.
Bruce.
Last edited:
Mine also is was updated to 20.40.3. I always thought that using the time-based versioning was better than sequences versioning or semantic versioning for most end users. But this is far from settled in the development community
charlesj
Active Member
Still on 1.50.1 (as for months). Wonder if the delay was the shift to the ‘new’ release? (Whatever it may contain.) I welcome the time-based numbering also if it’s timely (lol).
Apparently I've just got 20.40.3 on my Gateway, I'm guessing around 21:00 this evening because that's when my logging script stopped recording meter data....
...Has anyone else seen the meters at /api/meters/aggregates go from INT to FLOAT values? Just me?
(Specifically the houseImport/houseExport, gridImport/gridExport, batteryImport/batteryExport and solarImport/SolarExport values... just became FLOAT values of the same resolution as the previous INT values - Wh)
...Has anyone else seen the meters at /api/meters/aggregates go from INT to FLOAT values? Just me?
(Specifically the houseImport/houseExport, gridImport/gridExport, batteryImport/batteryExport and solarImport/SolarExport values... just became FLOAT values of the same resolution as the previous INT values - Wh)
