[Ovmsdev] Double updates - Normal?
mark at webb-johnson.net
Thu Jan 30 11:55:10 HKT 2020
It seems your car can’t pickup currently running firmware version:
ovms> open ROADSTER834B
Connected and logged in to ROADSTER834B
ovms> metric list version
By comparison, here’s mine:
ovms> metric list version
m.version 3.2.008-121-g4c6c9fe/ota_1/edge (build idf v3.3-beta3-775-gdc1ca69 Jan 29 2020 00:00:52)
ovms> ota status
Firmware: 3.2.008-121-g4c6c9fe/ota_1/edge (build idf v3.3-beta3-775-gdc1ca69 Jan 29 2020 00:00:52)
Running partition: ota_1
Boot partition: ota_1
Factory image: 3.2.002
OTA_O image: 3.2.008-120-gcfb7864
OTA_1 image: 3.2.008-121-g4c6c9fe
Your m.hardware metric is also blank.
I’ll keep looking, but at the moment this seems bizarre.
> On 30 Jan 2020, at 11:21 AM, Greg D. <gregd2350 at gmail.com> wrote:
> Hi Mark, Michael,
> Seems like what is happening is that the module keeps thinking a new
> update is available. Today was especially active for some reason.
> Screenshot of the Android application's log screen, attached. All
> versions appear to be the same. The car has simply been sitting in the
> garage on WiFi; no transitions of network access.
> Output of 'ota status' attached as well.
> Sorry, but I don't appear to have logging enabled. What specifically
> would you like logged?
> Mark Webb-Johnson wrote:
>> Not normal. Can you send us the logs. Also the output of ‘ota status’ would be helpful.
>> Are you sure this isn't just a notification of the update, and is the update itself? Perhaps a screenshot of the double notifications you receive?
>> Regards, Mark.
>>> On 25 Jan 2020, at 11:35 AM, Greg D. <gregd2350 at gmail.com> wrote:
>>> Hi folks,
>>> I moved my car's OVMSv3 to the Edge firmware a bit ago, and notice that
>>> every update seems to be doubled. Besides being a bit annoying, it ends
>>> up without a previous version to fall back to since both partitions end
>>> up being the same.
>>> Is this behavior normal? Can it be prevented?
>>> I'm only on Edge because of the bug in obd2ecu, and will probably move
>>> to EAP after we get an EAP build with the fix in it. Is the behavior
>>> the same there?
>>> I used to be on Main, and all seemed fine there.
>>> OvmsDev mailing list
>>> OvmsDev at lists.openvehicles.com
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com
> <Repeated updates.png><Repeated updates ota status output.txt>_______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OvmsDev