[Ovmsdev] Double updates - Normal?

[Greg D.]

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?

Greg


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.
>>
>> Thanks,
>>
>> Greg
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Repeated updates.png
Type: image/png
Size: 323215 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20200129/42b464d2/attachment-0002.png>
-------------- next part --------------
OVMS# ota status
Running partition: ota_0
Boot partition:    ota_0
Factory image:     3.1.001
OTA_O image:       3.2.008-121-g4c6c9fe
OTA_1 image:       3.2.008-121-g4c6c9fe
Server Available:  3.2.008-121-g4c6c9fe (is newer)

Tue Jan 28 16:03:10 UTC 2020 Automated build (markhk8)

Toolchain path: /home/openvehicles/build/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc
Toolchain version: crosstool-ng-1.22.0-80-g6c4433a
Compiler version: 5.2.0
App "ovms3" version: 3.2.008-121-g4c6c9fe
Python requirements from /home/openvehicles/build/esp-idf/requirements.txt are satisfied.
Total sizes:
 DRAM .data size:   16096 bytes
 DRAM .bss  size:   34296 bytes
Used static DRAM:   50392 bytes ( 130344 available, 27.9% used)
Used static IRAM:  105513 bytes (  25559 available, 80.5% used)
      Flash code: 1863954 bytes
    Flash rodata:  904016 bytes
Total image size:~2889579 bytes (.bin may be padded larger)

*   cd55eb3 (origin/spiram-fix-test) Merge branch 'master' into spiram-fix-test
|\  
| * 4c6c9fe (HEAD, origin/master, origin/HEAD, master) Docs: put SSH cipher info in a note box
* |   5773423 Merge branch 'master' into spiram-fix-test
|\ \  
| |/  
| * cfb7864 New plugin: ChgInd: Charge State Indicator
* |   c9ff599 Merge branch 'master' into spiram-fix-test
|\ \  
| |/  
| * bb40fcf EGPIO: address multiple ports by input & output command
| * aa87d64 Tesla Roadster: Ambient temperature is signed #326
* |   5c4425a Merge branch 'master' into spiram-fix-test
|\ \  
| |/  
| * a862373 New plugin: PwrMon: Trip Power Chart
| * b417463 Docs: add screenshot for AuxBatMon plugin



OVMS# boot status
Last boot was 777 second(s) ago
Time at boot: 2020-01-30 03:01:18 GMT
  This is reset #95 since last power cycle
  Detected boot reason: FirmwareUpdate (12/12)
  Reset reason: Exception/panic (4)
  Crash counters: 0 total, 0 early