Tasmoadmin: Automatic download of Minimal FW and applying full FW not working

[radokristof]

I have tried the Automatic method for updating a Sonoff switch through TasmoAdmin.
It said that the firmware is found, selected the device to update, however it uploaded the full firmware first... after a little wait, it said that it has been upgraded, but not, the version number is the same.

What I'm missing? Where I can specify that it should install the minimal first?

Thanks!

[reloxx13]

it will do it automatical, thats tasmotas OTA Magic (check the tasmota wiki for more infos regarding this).

if the update is not working, its properly because the tasmoadmin ota server url is wrong or not reachable.

you can see the url in the logs while updateing, try to call the url with your browser and check if the fw download starts within your browser.

tasmotas otamagic does not give a response if it was successfull or not, so atm there is no way to check if it was successfull or not. its more "hey device, here is the url where you find the fw, do your stuff".

tasmoadmin will just download the latest fw of the github releases page and provide them for all your devices.

[radokristof]

I have tried getting auto-update to work, but I have failed....
What the OTA Server IP should be if I want it to download from the original Sonoff-Tasmota repo?

TasmoAdmin adds this to the end of the URL: data/firmwares/sonoff.bin, but it should be tasmota/sonoff.bin. I couldn't get this around...

[ajfriesen]

I think I got the problem too.
I am using the tasmoadmin hassio add on from frenck.

My tasmoadmin is only reachable internally via http on: http://192.168.178.60:9541
I set my OTA Server IP and port accordingly.
Choose automatic.

I have a few sonoff devices with version 6.2.1 and a few with 6.4.0(sonoff).

I check all of them to update.

They all get the 6.4.1(minimal) first.
Then just a few get the full firnware 6.4.1(sonoff). It seems, that all my sonoff pows and S20 do get the full firmware, but the basics get stuck with the minimal.

I can safely update them wie mqtt afterwards, but this is an odd behavior.

Here my output if it helps:

[25-12-2018 12:21:32][GLOBAL] Start update process
[25-12-2018 12:21:32][ID-2][STEP-2][GLOBAL] Start Step 2
[25-12-2018 12:21:32][ID-2][STEP-2][CHECK] Check Connection | TRY => 1
[25-12-2018 12:21:32][ID-3][STEP-2][GLOBAL] Start Step 2
[25-12-2018 12:21:32][ID-3][STEP-2][CHECK] Check Connection | TRY => 1
[25-12-2018 12:21:32][ID-4][STEP-2][GLOBAL] Start Step 2
[25-12-2018 12:21:32][ID-4][STEP-2][CHECK] Check Connection | TRY => 1
[25-12-2018 12:21:32][ID-6][STEP-2][GLOBAL] Start Step 2
[25-12-2018 12:21:32][ID-6][STEP-2][CHECK] Check Connection | TRY => 1
[25-12-2018 12:21:32][ID-7][STEP-2][GLOBAL] Start Step 2
[25-12-2018 12:21:32][ID-7][STEP-2][CHECK] Check Connection | TRY => 1
[25-12-2018 12:21:32][ID-8][STEP-2][GLOBAL] Start Step 2
[25-12-2018 12:21:32][ID-8][STEP-2][CHECK] Check Connection | TRY => 1
[25-12-2018 12:21:32][ID-9][STEP-2][GLOBAL] Start Step 2
[25-12-2018 12:21:32][ID-9][STEP-2][CHECK] Check Connection | TRY => 1
[25-12-2018 12:21:32][ID-10][STEP-2][GLOBAL] Start Step 2
[25-12-2018 12:21:32][ID-10][STEP-2][CHECK] Check Connection | TRY => 1
[25-12-2018 12:21:32][ID-11][STEP-2][GLOBAL] Start Step 2
[25-12-2018 12:21:32][ID-11][STEP-2][CHECK] Check Connection | TRY => 1
[25-12-2018 12:21:33][ID-2][STEP-2][CHECK] Connection Successfully! | Current Version => 6.4.0(sonoff)
[25-12-2018 12:21:33][ID-2][STEP-2][OTAURL] Set OTA URL for Firmware => NEW FW
[25-12-2018 12:21:33][ID-2][STEP-2][OTAURL] OTA Url => http://192.168.178.60:9541/data/firmwares/sonoff.bin
[25-12-2018 12:21:33][ID-6][STEP-2][CHECK] Connection Successfully! | Current Version => 6.2.1
[25-12-2018 12:21:33][ID-6][STEP-2][OTAURL] Set OTA URL for Firmware => NEW FW
[25-12-2018 12:21:33][ID-6][STEP-2][OTAURL] OTA Url => http://192.168.178.60:9541/data/firmwares/sonoff.bin
[25-12-2018 12:21:33][ID-4][STEP-2][CHECK] Connection Successfully! | Current Version => 6.4.0(sonoff)
[25-12-2018 12:21:33][ID-4][STEP-2][OTAURL] Set OTA URL for Firmware => NEW FW
[25-12-2018 12:21:33][ID-4][STEP-2][OTAURL] OTA Url => http://192.168.178.60:9541/data/firmwares/sonoff.bin
[25-12-2018 12:21:33][ID-3][STEP-2][CHECK] Connection Successfully! | Current Version => 6.4.0(sonoff)
[25-12-2018 12:21:33][ID-3][STEP-2][OTAURL] Set OTA URL for Firmware => NEW FW
[25-12-2018 12:21:33][ID-3][STEP-2][OTAURL] OTA Url => http://192.168.178.60:9541/data/firmwares/sonoff.bin
[25-12-2018 12:21:33][ID-7][STEP-2][CHECK] Connection Successfully! | Current Version => 6.4.0(sonoff)
[25-12-2018 12:21:33][ID-7][STEP-2][OTAURL] Set OTA URL for Firmware => NEW FW
[25-12-2018 12:21:33][ID-7][STEP-2][OTAURL] OTA Url => http://192.168.178.60:9541/data/firmwares/sonoff.bin
[25-12-2018 12:21:33][ID-8][STEP-2][CHECK] Connection Successfully! | Current Version => 6.2.1
[25-12-2018 12:21:33][ID-8][STEP-2][OTAURL] Set OTA URL for Firmware => NEW FW
[25-12-2018 12:21:33][ID-8][STEP-2][OTAURL] OTA Url => http://192.168.178.60:9541/data/firmwares/sonoff.bin
[25-12-2018 12:21:33][ID-11][STEP-2][CHECK] Connection Successfully! | Current Version => 6.4.0(sonoff)
[25-12-2018 12:21:33][ID-11][STEP-2][OTAURL] Set OTA URL for Firmware => NEW FW
[25-12-2018 12:21:33][ID-11][STEP-2][OTAURL] OTA Url => http://192.168.178.60:9541/data/firmwares/sonoff.bin
[25-12-2018 12:21:33][ID-6][STEP-1][OTAURL] OTA URL set for Firmware => NEW FW
[25-12-2018 12:21:33][ID-6][STEP-2][UPDATE] Trigger device update...
[25-12-2018 12:21:33][ID-10][STEP-2][CHECK] Connection Successfully! | Current Version => 6.4.0(sonoff)
[25-12-2018 12:21:33][ID-10][STEP-2][OTAURL] Set OTA URL for Firmware => NEW FW
[25-12-2018 12:21:33][ID-10][STEP-2][OTAURL] OTA Url => http://192.168.178.60:9541/data/firmwares/sonoff.bin
[25-12-2018 12:21:33][ID-9][STEP-2][CHECK] Connection Successfully! | Current Version => 6.4.0(sonoff)
[25-12-2018 12:21:33][ID-9][STEP-2][OTAURL] Set OTA URL for Firmware => NEW FW
[25-12-2018 12:21:33][ID-9][STEP-2][OTAURL] OTA Url => http://192.168.178.60:9541/data/firmwares/sonoff.bin
[25-12-2018 12:21:33][ID-2][STEP-1][OTAURL] OTA URL set for Firmware => NEW FW
[25-12-2018 12:21:33][ID-2][STEP-2][UPDATE] Trigger device update...
[25-12-2018 12:21:33][ID-4][STEP-1][OTAURL] OTA URL set for Firmware => NEW FW
[25-12-2018 12:21:33][ID-4][STEP-2][UPDATE] Trigger device update...
[25-12-2018 12:21:33][ID-6][STEP-2][UPDATE] Device update triggered
[25-12-2018 12:21:33][ID-6][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:21:33][ID-3][STEP-1][OTAURL] OTA URL set for Firmware => NEW FW
[25-12-2018 12:21:33][ID-3][STEP-2][UPDATE] Trigger device update...
[25-12-2018 12:21:33][ID-11][STEP-1][OTAURL] OTA URL set for Firmware => NEW FW
[25-12-2018 12:21:33][ID-11][STEP-2][UPDATE] Trigger device update...
[25-12-2018 12:21:33][ID-8][STEP-1][OTAURL] OTA URL set for Firmware => NEW FW
[25-12-2018 12:21:33][ID-8][STEP-2][UPDATE] Trigger device update...
[25-12-2018 12:21:33][ID-10][STEP-1][OTAURL] OTA URL set for Firmware => NEW FW
[25-12-2018 12:21:33][ID-10][STEP-2][UPDATE] Trigger device update...
[25-12-2018 12:21:33][ID-3][STEP-2][UPDATE] Device update triggered
[25-12-2018 12:21:33][ID-3][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:21:33][ID-7][STEP-1][OTAURL] OTA URL set for Firmware => NEW FW
[25-12-2018 12:21:33][ID-7][STEP-2][UPDATE] Trigger device update...
[25-12-2018 12:21:33][ID-9][STEP-1][OTAURL] OTA URL set for Firmware => NEW FW
[25-12-2018 12:21:33][ID-9][STEP-2][UPDATE] Trigger device update...
[25-12-2018 12:21:33][ID-2][STEP-2][UPDATE] Device update triggered
[25-12-2018 12:21:33][ID-2][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:21:33][ID-4][STEP-2][UPDATE] Device update triggered
[25-12-2018 12:21:33][ID-4][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:21:33][ID-8][STEP-2][UPDATE] Device update triggered
[25-12-2018 12:21:33][ID-8][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:21:33][ID-11][STEP-2][UPDATE] Device update triggered
[25-12-2018 12:21:33][ID-11][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:21:33][ID-9][STEP-2][UPDATE] Device update triggered
[25-12-2018 12:21:33][ID-9][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:21:33][ID-7][STEP-2][UPDATE] Device update triggered
[25-12-2018 12:21:33][ID-7][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:21:33][ID-10][STEP-2][UPDATE] Device update triggered
[25-12-2018 12:21:33][ID-10][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:22:34][ID-6][STEP-2][DONE] ============= Update done! =============
[25-12-2018 12:22:34][ID-3][STEP-2][CHECK UPDATE] Update not done now
[25-12-2018 12:22:34][ID-3][STEP-2][CHECK UPDATE] Wait for update | Seconds => 30
[25-12-2018 12:22:34][ID-4][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:22:34][ID-4][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:22:34][ID-8][STEP-2][DONE] ============= Update done! =============
[25-12-2018 12:22:34][ID-11][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:22:34][ID-11][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:22:34][ID-9][STEP-2][CHECK UPDATE] Update not done now
[25-12-2018 12:22:34][ID-9][STEP-2][CHECK UPDATE] Wait for update | Seconds => 30
[25-12-2018 12:22:38][ID-10][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:22:38][ID-10][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:22:39][ID-7][STEP-2][CHECK UPDATE] Update not done now
[25-12-2018 12:22:39][ID-7][STEP-2][CHECK UPDATE] Wait for update | Seconds => 30
[25-12-2018 12:22:44][ID-2][STEP-2][CHECK UPDATE] Update not done now
[25-12-2018 12:22:44][ID-2][STEP-2][CHECK UPDATE] Wait for update | Seconds => 30
[25-12-2018 12:23:05][ID-3][STEP-2][CHECK UPDATE] Update not done now
[25-12-2018 12:23:05][ID-3][STEP-2][CHECK UPDATE] Wait for update | Seconds => 30
[25-12-2018 12:23:09][ID-7][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:23:09][ID-7][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:23:12][ID-9][STEP-2][DONE] ============= Update done! =============
[25-12-2018 12:23:14][ID-2][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:23:14][ID-2][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:23:34][ID-4][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:23:34][ID-4][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:23:35][ID-11][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:23:35][ID-11][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:23:36][ID-3][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:23:36][ID-3][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:23:38][ID-10][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:23:38][ID-10][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:24:10][ID-7][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:24:10][ID-7][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:24:15][ID-2][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:24:15][ID-2][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:24:35][ID-4][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:24:35][ID-4][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:24:36][ID-11][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:24:36][ID-11][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:24:37][ID-3][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:24:37][ID-3][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:24:39][ID-10][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:24:39][ID-10][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:25:11][ID-7][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:25:11][ID-7][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:25:16][ID-2][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:25:16][ID-2][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:25:36][ID-4][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:25:36][ID-4][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:25:37][ID-11][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:25:37][ID-11][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:25:38][ID-3][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:25:38][ID-3][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:25:40][ID-10][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:25:40][ID-10][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:26:12][ID-7][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:26:12][ID-7][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:26:17][ID-2][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:26:17][ID-2][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:26:37][ID-4][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:26:37][ID-4][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:26:38][ID-11][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:26:38][ID-11][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:26:39][ID-3][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:26:39][ID-3][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:26:41][ID-10][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:26:41][ID-10][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:27:13][ID-7][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:27:13][ID-7][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60
[25-12-2018 12:27:18][ID-2][STEP-2][CHECK UPDATE] MINIMAL IS INSTALLED NOW, WAIT FOR MAIN FW!
[25-12-2018 12:27:18][ID-2][STEP-2][CHECK UPDATE] Wait for update | Seconds => 60

[MaceMoneta]

They all get the 6.4.1(minimal) first.
Then just a few get the full firnware 6.4.1(sonoff). It seems, that all my sonoff pows and S20 do get the full firmware, but the basics get stuck with the minimal.

I'm having exactly the same problem.

[radokristof]

They all get the 6.4.1(minimal) first.
Then just a few get the full firnware 6.4.1(sonoff). It seems, that all my sonoff pows and S20 do get the full firmware, but the basics get stuck with the minimal.

I'm having exactly the same problem.

I have managed to get auto-update working, but the Basic modules stay on Minimal.
If I press manually the start upgrade from it's web server (the same OTA IP URL which is set in TasmoAdmin) it updates itself.

[ajfriesen]

@radokristof I also did update them manually and it worked.
But I think I uploaded my sonoff.bin by hand.

Neither way there is something odd happening.

[GasTurbineMan]

I have been seeing similar issues updating my devices with my modified .bin files. Odd thing is that I had selected a batch of 3 Sonoff Basics and 2 ESP01 devices for upgrade. All 5 reported that update was successful however only the 2 ESP01's actually showed the updated version. The basics were later successfully updated via the webgui.

Not sure this is the issue, but seems my update issues started after updating 6.4.0 to 6.4.1.2. and likewise trying to update to 6.4.1.4. Using Tasmoadmin on one of the Basics that would not update, I reverted back to 6.1.x which went well and then updated to 6.4.1.2 and all worked well.

[GasTurbineMan]

Additional testing this morning on 4 Sonoff Basics. 1 had version 6.4.1.2 and the other 3 had 6.4.1.4 . The 3 with 6.4.1.4 on them were some of the ones that would not update via Tasmoadmin in my prior post. Generated my normal slightly modified version of 6.4.1.5 and attempted a batch update via Tasmoadmin. All 4 units reported being updated via Tasmoadmin however when I went back to device list the only ones that actually took the update were the 3 having 6.4.1.4 on them. The one that had 6.4.1.2 on it would not update via Tasmoadmin. I tried one more time with Tasmoadmin without success.
I then went into the WebGui and uploaded FW from there - no issues.

[radokristof]

I'm using the original release from Tasmota with my Sonoffs, no custom modified firmware (as I suppose, you do some modifications in the firmware). But I think somehow this is related to Tasmota and not TasmoAdmin. Or not?
If I'm right, the minimal and normal selection is done by the firmware and not by TasmoAdmin. So basically what the TasmoAdmin does is downloads the binary firmware file and request an update on the selected devices with the link to the firmware. Tasmota recognizes that this firmware won't fit into the memory, so downloads the minimal firmware (but how? From Github? If yes, why does TasmoAdmin pre-loads the firmware on the device, running TasmoAdmin? Why not let the Sonoff itself download the firmware and additionally download the minimal firmware? Only optional to use local link to update firmware (for custom firmwares)).

Also the 6.4.1 firmware seems buggier for me, than 5.1.x was.

[reloxx13]

heyaaaa,

ill update my devices tonight and check it.

tasmoadmin downloads the minimal and full firmware from the tasmota github.
after that it provides the fw just as @radokristof descriped.
instead of every device starting to download minimal and full fw over internet, they download it from your local tasmoadmin server.

since this "otamagic" got added, i cannot get feedback back from the device if the new fw was successfull or not.

to debug, you can try to enter the firmware url, written in the update log, in ur browser and see if the download starts. this have to work, if not, the sonoffs wont receive the fw neither.

for @ajfriesen it would be this line:
[25-12-2018 12:21:33][ID-8][STEP-2][OTAURL] OTA Url => http://192.168.178.60:9541/data/firmwares/sonoff.bin

http://192.168.178.60:9541/data/firmwares/sonoff.bin

and additional open the devices GUI in ur webbrowser and look at the logs, the update process and errors is written there.

@radokristof

What the OTA Server IP should be if I want it to download from the original Sonoff-Tasmota repo?

this wont work. if u want do it like this, i would recommend to use the console at bottom of the devices list to start it for all/selected devices.
ull need the tasmota commands OtaUrl and Upgrade

[radokristof]

@reloxx13
Thanks for specifying how this really works!
I have tried the link as well, it download the right firmware for me. Is there a link to the minimal as well?
Also links should work (I think), because other devices got updated flawlessly. So I don't think that the links are not good.
How the sonoffs request the minimal firmware? Or when starting the update process, the minimal fw and full fw path are also defined?

[reloxx13]

the minimal link gets generated by tasmota, it adds "-minimal" at the end.

like this:
http://192.168.178.60:9541/data/firmwares/sonoff-minimal.bin

[reloxx13]

if both files are available, its to 99% an tasmota problem.

if it fails, go on teh devices GUI, go into the console

check if the firmware url is set correctly by entering the command OtaUrl.

edit it with command
OtaUrl http://TASMOADMIN_IP:TASMADMIN_PORT/data/firmwares/sonoff.bin

if this is correct, start the update with the command Upgrade 1 and look what happens, tasmota should tell what the problem is in the console.

tasmoadmin is doing exactly this.

[radokristof]

Otaurl seems correct. Now I'm on the latest firmware so I can't (and I don't want...) to upgrade.
However I see a really odd behaviour on the Sonoff Basic (sadly now I only have 1 Basic device): it always disconnects and reconnects to my MQTT broker. I don't know why, the S20 doesn't have any problems like this.
Why I'm saying this is because when this disconnection happens, the web interface also seems to be not very responsive (it takes around 20 secs to load the page). Maybe some bug in Tasmota which somehow breaks the stable connection, thus breaks the upgrade process?

[reloxx13]

i got the same problem with iobroker, but its not lagging for me or i did not notice lagging. i use the TASMOTA_MQTT_LIBRARY.
check the my_user_config.h file to change the MQTT library (ull need to build your own fw than).

u can give my mod version a try, this is just my own pre-configured tasmota and i upload the binaries.
in past there were some changes in the mod, but most of them got meanwhile included in the official tasmoata repo.

https://github.com/reloxx13/Sonoff-Tasmota-Modified/releases
this is the config of my mod:
https://github.com/reloxx13/Sonoff-Tasmota-Modified/blob/modified/sonoff/my_user_config.h

and the builded bins are with arduino esp lib 2.3.0.

but better build it urself, tasmota community wont support the mod, which is understandable.

[radokristof]

Thanks!

First I will monitor the device, maybe I will try resetting it (I have upgraded from an older fw, mainly because of some MQTT issues which seems fixed with this, but introduced new ones).

I will try your mod if this not works well...