Greg, Mark,
Greg, you've got "dirty" builds (= built with not yet
checked in local changes) installed on both OTA
partitions now.
This points to the version currently available on your
update server having the "dirty" tag. Mark, I assume
that's your server, can you please check?
The OTA system treats a local "dirty" tag as sufficient
for triggering an update, also if the version on the
server has the same version, so that explains why you
get repeated updates: the OTA system doesn't expect a
version from the server being "dirty", so will update
repeatedly in this case as long as the hour matches.
Regards,
Michael
Am 01.06.26 um 06:02
schrieb Greg D.:
Hi Michael,
All the messages show 3.3.006, with nothing extra, as
displayed on the Android app. Looking at the
web-based Status screen, it shows the following:
Hardware: OVMS WIFI BLE BT cores=2
rev=ESP32/1; MODEM SIM7600
Firmware: 3.3.006-dirty/ota_1/eap (build idf
v3.3.4-854-g9063c8662 May 18 2026 23:49:43, product
v3.1)
Partition type: v3-30 (factory, ota1, ota2, 1MB
store)
Partition table: 0x8000
Running partition: ota_1
Boot partition: ota_1
Factory image: 3.1.001
OTA_O image: 3.3.006-dirty
OTA_1 image: 3.3.006-dirty
Since my original message there was another set of 4
download / update messages this past night (5/31
starting at 2:01 am local, UTC -7), so this is as of
right now. I've not been paying attention to the
firmware management commands for some time, so no
recollection on how to retrieve any of the logs. What
commands do I need to give?
Thanks,
Greg
Michael Balzer via
OvmsDev wrote:
Greg,
please be specific about the messages, were all of
them naming version "3.3.006"?
Background: there have been multiple releases to EAP
over the last days, but only the initial one was
"3.3.006" without a suffix.
EAP is currently following EDGE due to the Smart EQ
issue still needing changes to the release
candidate. The latest update was yesterday, it's now
at 3.3.006-57-g2035e13ac.
If you saw no sub version suffixes on later update
notifications, do you have some log excerpt covering
these update runs?
Regards,
Michael
Am 30.05.26 um 05:19 schrieb Greg D.:
Hi folks,
I had enabled EAP updates some time (years?) ago,
and with the recent release of 3.3.006 the module
in my Roadster updated. And updated. And
updated. Early in the AM of May 29th, the Android
app's view of the message log shows 5 pairs of
"New OTA firmware 3.3.006 is now being downloaded"
followed by "OTA firmware 3.3.006 has been updated
(OVMS will restart)". In the middle of the set is
a notice that charging is done (it was actually
done many hours before).
This also happened on May 257th, and the 27th.
The module seems to be working otherwise. Is this
expected? How can I stop it?
I suspect this is has something to do with the
image size / partitioning change, but I wasn't
following that discussion very closely.
Thanks,
Greg
_______________________________________________
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com
To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com
_______________________________________________
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com
To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com
--
Michael Balzer * Am Rahmen 5 * D-58313 Herdecke
Fon 02330 9104094 * Handy 0176 20698926