06-15-2023, 02:59 PM
It was a bug...in a bug fix ;-) The "change report" will show you this is changed...but it is not actually a problem, OrBit won't write that config item to the car. So if you do or did write the config, all will be fine. This has already been fixed.
OrBit was updated some versions back, to deal with the "OTA" update problem, that those SW version configs need to change when you update OTA, as the "SW version" config items are written in the update, and they need to reflect the current update level of the car. However when I made that update...I did not originally think about and account for the case where you do exactly what you have done...load settings from a time when you had an earlier update level ;-)
It's fixed as of v0.5.3...have you been ignoring the update notification?? Or maybe you weren't prompted well anyways you should be getting prompted to download the update to the latest v0.5.4 by now, and that will resolve the issue.
OrBit was updated some versions back, to deal with the "OTA" update problem, that those SW version configs need to change when you update OTA, as the "SW version" config items are written in the update, and they need to reflect the current update level of the car. However when I made that update...I did not originally think about and account for the case where you do exactly what you have done...load settings from a time when you had an earlier update level ;-)
It's fixed as of v0.5.3...have you been ignoring the update notification?? Or maybe you weren't prompted well anyways you should be getting prompted to download the update to the latest v0.5.4 by now, and that will resolve the issue.