Conversion results: Drop your report in here

[adamsthws]

At the end of it's run the tool displays your conversion report, please drop that report in here.
Your report allows others to see whether it converted cleanly, stopped partway, or you
only ran the read-only checks. Every report helps.

So far every conversion has been a UK S60TPG run from Linux, so a report
from a European S60TPF, or from Windows or macOS, is exactly what moves those
from "should work" to "known to work". (The README's list of tested plugs and
computers is updated from this thread).

Found a bug that needs a code fix? Open an issue as well, and link it here.

[jetronic18s]

Successful S60TPF (EU / Type E/F) conversion & fix for stalled chunk transfers

I just successfully converted the European model (**S60TPF**, Stock 1.2.0) to official Tasmota! Relay switching and power monitoring (236 V) both work as expected.

```text
Result:               Converted
Plug model:           S60TPF
Plug type / region:   Europe (Type E/F)
Stock firmware:       1.2.0
Computer:             Ubuntu 22.04.5 LTS (WSL2), Python 3.12.10
Time taken:           ~4m 20s
Typed the Wi-Fi:      No
Joined setup network: No
Name in Tasmota:      Sonoff S60TPF
Relay:                Switches (seen on the meter)
Power meter:          On: 236 V, 0 W; off: 0 V, 0 W

Issue encountered during Stage 9 (E2):

During Stage 9, the script got stuck waiting at block 100 on the first attempt and block 43 on the second. Checking the Tasmota console on the plug revealed:
[migration_refused] GET /chunk/safeboot/43 returned HTTP -1

Root cause:

• fetch_chunk in Berry did not call client.close(), keeping TCP sockets lingering across hundreds of sequential requests.
• When transient Wi-Fi jitter caused a timeout (HTTP -1), the script immediately threw an unhandled exception and died, leaving the host waiting.

Solution:
I added an explicit client.close() and a retry loop (5 attempts, 150ms delay) to both stage.be.tmpl and restore.be.tmpl. After that, the run completed all 14 stages without a hitch.

I've opened a Pull Request with the fix: https://github.com/adamsthws/Sonoff-OTA/pull/

[amikot]

Success !
I have purchased eight plugs last week on Amazon.
This is result for first of them:

 Result:               Converted
 Plug model:           S60TPG
 Plug type / region:   UK (Type G)
 Stock firmware:       1.2.0
 Computer:             Ubuntu 26.04.1 LTS, Python 3.12.10
 Time taken:           5m 57s (this session; the run was resumed)
 Typed the Wi-Fi:      No
 Joined setup network: No
 Name in Tasmota:      Sonoff S60TPG
 Relay:                Switches (seen on the meter)
 Power meter:          On: 236 V, 44 W; off: 0 V, 0 W

Result for the second plug:

 Result:               Converted
 Plug model:           S60TPG
 Plug type / region:   UK (Type G)
 Stock firmware:       1.2.0
 Computer:             Ubuntu 26.04.1 LTS, Python 3.12.10
 Time taken:           8m 33s
 Typed the Wi-Fi:      No
 Joined setup network: No
 Name in Tasmota:      Sonoff S60TPG
 Relay:                Switches (seen on the meter)
 Power meter:          On: 236 V, 0 W; off: 0 V, 0 W

One more:

 Result:               Converted
 Plug model:           S60TPG
 Plug type / region:   UK (Type G)
 Stock firmware:       1.2.0
 Computer:             Ubuntu 26.04.1 LTS, Python 3.12.10
 Time taken:           6m 44s
 Typed the Wi-Fi:      No
 Joined setup network: No
 Name in Tasmota:      Sonoff S60TPG
 Relay:                Switches (seen on the meter)
 Power meter:          On: 236 V, 0 W; off: 0 V, 0 W

ON forth plug I have experienced an issue:

 Stage  5 of 14 - Installing bridge firmware       - Underway 3m 21s

 -- The bridge was not delivered
     The sender reported:
       [192.168.1.232] Request timed out: TimeoutError('timed out')
       [192.168.1.232] Request timed out: TimeoutError('timed out')
       WARNING: the device did not request every firmware byte.
    
     The plug never connected to this computer. That is almost always this
     computer's firewall, or this computer having changed address.
    
     A ufw firewall is on. This allows the plug in:
       sudo ufw allow from 192.168.1.232 to any port 8088,8089 proto tcp comment 'S60 autoflash'
 Stage  5 of 14 - Installing bridge firmware       - Stopped

 FAILED: bridge delivery failed

I think it was caused by weak wonky Wifi Signal - after moving plug to better spot I have restarted process with result:

 Result:               Converted
 Plug model:           S60TPG
 Plug type / region:   UK (Type G)
 Stock firmware:       1.2.0
 Computer:             Ubuntu 26.04.1 LTS, Python 3.12.10
 Time taken:           6m 11s (this session; the run was resumed)
 Typed the Wi-Fi:      No
 Joined setup network: No
 Name in Tasmota:      Sonoff S60TPG
 Relay:                Switches (seen on the meter)
 Power meter:          On: 228 V, 0 W; off: 0 V, 0 W

And next one converted without problems:

 Result:               Converted
 Plug model:           S60TPG
 Plug type / region:   UK (Type G)
 Stock firmware:       1.2.0
 Computer:             Ubuntu 26.04.1 LTS, Python 3.12.10
 Time taken:           6m 35s
 Typed the Wi-Fi:      No
 Joined setup network: No
 Name in Tasmota:      Sonoff S60TPG
 Relay:                Switches (seen on the meter)
 Power meter:          On: 234 V, 63 W; off: 0 V, 0 W

[michalicekmilan]

Two EU plugs converted, no issues experienced:

 Result:               Converted
 Plug model:           S60TPF
 Plug type / region:   Europe (Type E/F)
 Stock firmware:       1.2.0
 Computer:             Ubuntu 24.04.4 LTS, Python 3.12.10
 Time taken:           6m 30s
 Typed the Wi-Fi:      No
 Joined setup network: No
 Name in Tasmota:      Sonoff S60TPF
 Relay:                Switches (seen on the meter)
 Power meter:          On: 232 V, 0 W; off: 0 V, 0 W

[MalSmalley]

S60TPG Conversion - Using Mac-OS Sequoia 15.7.4 Python 3.12.2 (already installed)

1st Attempt failed at Stage 6 - On Screen messaging suggesting an AP had been created but this did not exist.

> [10:04:31] --- Stage 6 of 14 - Installing interim firmware
> [10:04:31] D1  Berry-capable Tasmota via bridge AP
> [10:04:31] Looking for the plug's Wi-Fi network...
> [10:05:35] 
> [10:05:35] -- Join the bridge's Wi-Fi network
> [10:05:35]     The plug is running our small installer, which has made its own Wi-Fi
> [10:05:35]     network. In the Wi-Fi icon in the menu bar, join:
> [10:05:35]         network   S60-OTA-Bridge-XXXX   (the XXXX varies)
> [10:05:35]         password  s60-ota-bridge      (already copied - just paste it)
> [10:05:35]     
> [10:05:35]     Your Wi-Fi internet drops while joined - expected. A wired connection,
> [10:05:35]     if this computer has one, can stay connected. This carries on by itself.

Retried attempting to continue the installation at the suggested IP

[18:01:33] FAILED: the plug at 192.168.0.22 did not answer the eWeLink discovery; check it is switched on and LAN Control is on in the eWeLink app

ewelink could still see the device so I tried again from scratch.

This time the installation did not pause at step 6 but continued to Stage 8

[18:20:36] --- Stage 8 of 14 - Verifying the memory layout
[18:20:36] E1  Preflight (read-only)
[18:20:36]     The Wi-Fi details could not be read off the plug: it did not say which network it is on.
[18:20:36] 
[18:20:36] -- Your Wi-Fi details are needed
[18:20:36]     They could not be read off the plug (the reason is above).
[18:20:36]     The startup firmware has to rejoin your Wi-Fi by itself after the
[18:20:36]     next stage, so it needs them written in.
[18:20:36]     
[18:20:36]     Use the 2.4 GHz network the plug should stay on. The password is held
[18:20:36]     in memory for this run only, never written to disk, and you are not
[18:20:36]     asked again later in the run.
[18:20:36] The bundle is set up for '<wifi-name>'.
[18:20:36] ? Wi-Fi password for '<wifi-name>' (q to quit):
[18:20:54] Stage 8 of 14 - Verifying the memory layout - stopped
[18:20:54] FAILED: the plug did not say which Wi-Fi network it is on, so the bundle's network cannot be checked. Nothing was written

The s60 was visible on the ip address and running Tasmota-safeboot.
This allowed me to upload the tasmota32c3.bin firmware and complete the conversion.

It's working however python3 tools/s60_autoflash.py step H1 --plug-ip 192.168.0.22
differs -

 Stage 14 of 14 - Verifying the conversion         - Underway 1s

   safeboot  0x010000   810,672  DIFFERS
     expected 364339a828c243ddf5fee3ed24f8bf352dffc87b2572ca9d7f48736bcb852bdc
     actual   d9714f745d9bf2bd1277c22807f8fede36184c98dfe3035d4e03cee546e0df1c
 Stage 14 of 14 - Verifying the conversion         - Stopped 

I'm not sure any of this is particularly MAC related. I was getting reports of -79dbm wifi. I'm not sure why, my wifi strength is much better than that but perhaps is connecting to a different repeater.

[adamsthws]

Thankyou for the report, and for being the first Apple user that we know of to attempt it!

I've not had chance to test on Mac yet, I'll spin up an emulator and see if I can reproduce (and fix) your result over the next few days. I'll report back here with my findings.

P.S. - If you manually flashed it would be expected to see a different hash at step 14. I wouldn't necessarily read this as having an issue / corruption with your plug.

Thanks, Adam

[MalSmalley]

Happy to send you the full logs if that would help.

[adamsthws]

Happy to send you the full logs if that would help.

That would be great actually. Paste might be our best bet

[MalSmalley]

Paste link gave me all sorts of redirects & Norton alerts !!
I've gone old school and emailed them to you.

[adamsthws]

Thanks for those logs. They've led to fixes that are now in the repo. (Nothing in it turned out to be Mac-specific)

• Stage 6 failure: the installer joined your Wi-Fi more slowly than the tool expected, possibly because of the weaker signal. The tool gave up looking for it after a minute and told you to join the plug's own network. The plug only creates that network if it can't join yours, so it never appeared. The tool now keeps looking on your Wi-Fi while it waits.
• Stage 10 failure: the memory-layout rewrite actually worked. Your log shows COMMIT RESULT: PASS. But the plug restarts straight afterwards - that cut off the reply so on the next run the tool couldn't tell the step had finished, and every way forward hit a dead end. Uploading tasmota32c3.bin yourself was the right call (it's what Stage 11 would have done next). The tool now handles the cut-off reply, and if a run is interrupted it re-reads the plug's status and carries on.

Your plug works as it is, but it's worth finishing to avoid future upgrade issue... From your Sonoff-OTA folder:

git pull  #Important - Fetches the latest fixes
python3 tools/s60_autoflash.py step G1 --plug-ip 192.168.0.22
python3 tools/s60_autoflash.py step H1 --plug-ip 192.168.0.22

• G1 is Stage 13. This should get your safeboot back to where we want it
• H1 (Stage 14) should then show all three regions as MATCH.

(Before writing anything, the plug checks itself: the memory layout, that official Tasmota is running, and that the temporary startup firmware is still in place. If anything doesn't match, it stops and nothing is written)

[janvand]

Just did a succesfull conversion from a WIndows 10 PC. Initially had issues connecting to the plug, because my IOT devices live on a seperate VLAN (although temp firewall rule to allow all traffic between my PC and the plug was in place). Workaround was moving my laptop to the IOT VLAN temporary.

[adamsthws]

Thankyou. You are the first Windows user to
report success. Much appreciated!

[zvezdaabzelil-png]

Hello! I need help recovering my Sonoff S60TPF.

• Model: Sonoff S60TPF, ESP32-C3
• Original firmware: 1.2.0
• Computer: Windows 10
• Sonoff-OTA stages 1–8 completed successfully.
• Stage 9 (E2 — Stage Safeboot into the spare slot) timed out twice after 30 minutes.
• Error: TIMEOUT: no complete, validated phase report was received.
• The device is still accessible at 192.168.0.15 and runs Tasmota 15.6.0.1.
• The server log shows successful HTTP 200 responses for the Berry script and both safeboot chunks, but no final phase report.
• Kaspersky Premium is installed.

Could you please advise on the safest recovery procedure? I have not manually uploaded any firmware files through the Tasmota web interface.

Thank you!

[adamsthws]

Hi, thanks for the report, let's get you sorted out...

Your plug is safe. Stage 9 only copies the startup firmware into a spare area of memory. It doesn't change the partition table or what the plug boots from, so you can retry again as many times as needed.

Another S60TPF user seems to have hit the same stop in Stage 9 (see the report above). The plug gives up on the first network hiccup while downloading, and doesn't tell the computer, so the computer just waits. A fix to add automatic retries is in the pipeline. You could keep retrying manually in the mean time (make sure the plug and computer both have strong Wi-Fi signal).

Kaspersky may also be part of it, because it can interrupt local network connections. If it keeps failing, you might try pausing Kaspersky's firewall for the run.

---

To find out why it stopped, it would be great if you send me these three things?

1. The plug's own error message. Open http://192.168.0.15 → Tools → Console. Look for a line starting S60 or migration_refused, for example [migration_refused] GET /chunk/safeboot/2 returned HTTP -1. Copy the whole console.
2. captures\<your-plug>\run.log from the Sonoff-OTA folder on your computer.
3. captures\<your-plug>\live\stage-server.log. You mentioned two safeboot chunks: about 198 should be fetched, so I'd like to see exactly where it stopped.

You can paste them here inside a ``` code block, or email them to me.
(see admatthews.co.uk for email address)