too fast update?

[bobybobybob]

I use TasmoCompiler to make custom Firmware. I download current esp8266 tasmota minimal (14.4.1)
I klick on TasmoAdmin on Update, manual update, set the minimal firmware and my new one.

Modul 13 (Tasmota_Ho)
[2024-12-15T17:20:11.591Z] Starte Update Prozess[2024-12-15T17:20:11.591Z] Checking version...[2024-12-15T17:20:11.809Z] Current version is 14.4.0(TasmoCompiler-esp8266generic)[2024-12-15T17:20:11.809Z] OTA Url => http://192.168.1.18:3004/data/firmwares/tasmota.bin.gz[2024-12-15T17:20:11.920Z] Starte Module update...[2024-12-15T17:20:12.053Z] Sleeping for 10s...[2024-12-15T17:20:22.061Z] Update gestartet[2024-12-15T17:20:22.061Z] Checking version...[2024-12-15T17:20:22.929Z] Version is 14.4.0(TasmoCompiler-esp8266generic)[2024-12-15T17:20:22.929Z] Device upgrade successful

It write, it has "upgrade to 14.4.0, not 14,4,1... but successful.... but that is not true.... when i go to that device it show it is still on minimal firmware. Start there the update again, then it work most time... not everytime...

No problems with esp32 firmwares and no problem when automatic is chosen for esp8266.

sometimes it also helps to select the two own files for update again in tasoadmin but then not to select any devices... the device then fetches the firmware from the local URL again... no idea... in any case with a longer wait it sometimes works.

I had the same problems a few days ago with 14.4.0 but thought it was due to an outdated minimal. Now I know it wasn't that.

TasoAdmin 4.2.0 in Docker on Linux Mint in Virtuall Box under windows 10.

[inverse]

The whole manual update logic could do with a massive overhaul due to the lack of version checking and assumptions made based on this.

For the automatic one we use the target version from the OTA URL and use this to compare against the version the device exposes via http://<ip>/cm?cmnd=Status%200 under Status.StatusFWR.Version

For custom firmware it just provides the OTA URL and skips all the checks.

I'm guessing this version is also defined under the endpoint we would just need a way to specify the target version (form input) or extract/infer from the binary some how 🤔 which would be less manual work.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[bobybobybob]

yes the problem persists... even compiled for esp8266 i have to do it again manually via the respective web interface.

[inverse]

Does the the device report the correct version on the API? under Status.StatusFWR.Version?

[bobybobybob]

I have found out in the meantime that when the program says that the update was successful, the corresponding Tasmota end devices are not yet finished with phase 1 where the minimum is installed first. Simply wait much longer and then phase 2 is also carried out. I don't know why this is the case now, some versions were not like this before.

[ollo69]

Same problem here, local update does not works.

[inverse]

@ollo69 do you know if the device provides the correct version on the API? e.g. under Status.StatusFWR.Version. If it does we could in theory ask for the target version number to be provided or somehow infer it from the binary artifact.

[ollo69]

I suppose that it provide correct version because on TasmoAdmin console version column report right version. Was this the question?

[inverse]

Nice - if we could know the version being uploaded than we could get it to work like the OTA one. Manually getting the user to provide this seems like overkill though.