Direct stock → ESPHome install on the S60TPF, reusing Sonoff-OTA's updater code

[mvoss96]

The README mentions a direct Sonoff → ESPHome conversion as "coming soon". I have a working version of that for the S60TPF and published it here:

https://github.com/mvoss96/sonoff-s60tpf-esphome

It does not go through Tasmota. send_firmware.py wraps an ESPHome OTA image with tools/build_vendor_ota.py and sends it with the eWeLink upgrade command, using the delivery code from tools/s60_readout.py. The stock updater writes ESPHome into the spare app slot. Bootloader, partition table and NVS are left untouched.

Because NVS survives, the ESPHome config reads the per-plug factory calibration (user_unusual / calib_coefficient0) at boot and applies it like the stock firmware does, including the 1.02 factor selected by GPIO6/10/19.

Before installing, the guide takes a full flash backup with tools/s60_readout.py. Since Sonoff-OTA ships the readout bridge only as source, the repo includes a build of archive/bridge (env s60-ota-bridge-flash-readout, commit 9a20bf0) under GPL-3.0, with a NOTICE pointing to the source.

Tested on two S60TPF with stock 1.2.0 and ESPHome 2026.9.1. Not tested: the S60TPG, and returning to stock from ESPHome.

send_firmware.py imports internal functions from Sonoff-OTA, so changes there may break it. If you would rather fold this into Sonoff-OTA itself, I'm happy to help.

[WildeRNS]

Can someone tell how to migrate from tasmota to esphome? I try compile esphome friwm, and when I flash factory.bin from tasmota device's page - I receive Safeboot with Upload filed warning. I eve try in console, SetOption78 1, and still same safeboot...

[adamsthws]

@WildeRNS - A factory.bin is a whole-flash image intended for USB/serial flashing (rather than through Tasmota's upload page)... Just landed: v2 - should get you straightened out. Run it and choose the ESPHome conversion. It handles a plug stuck in Safeboot like yours. You might need to give it the plug's address with --plug-ip.

# MacOS / Linux
cd Sonoff-OTA
sh start.sh run --plug-ip 192.168.x.x

# Windows
cd Sonoff-OTA
.\start.ps1 run --plug-ip 192.168.x.x

Any issues please send me your logs.
Thanks!

[WildeRNS]

I converted from Tasmota to ESPHome with one try, even without --plug-ip.
Thanks for this project!

[adamsthws]

Thankyou for the update, I'm pleased to hear you were able straighten it out with the new version!

[adamsthws]

The README mentions a direct Sonoff → ESPHome conversion as "coming soon"

Just landed: v2
The tool now converts to ESPHome directly.
(It also moves a plug between Tasmota, ESPHome and Sonoff's own firmware in any direction, plus many new safeguards).

ESPHome config reads the per-plug factory calibration

If you would rather fold this into Sonoff-OTA itself, I'm happy to help.

@mvoss96, I'd love to take you up on your offer. The calibration code (calib_coefficient0 plus the 1.02 board factor) would be a great addition to ESPHome/sonoff_s60.yaml. The plug's NVS survives our ESPHome route, so it would work as it is. Would you be up for opening a PR?

Great work!

[mvoss96]

Opened #7 with the calibration for ESPHome/sonoff_s60.yaml.

[WildeRNS]

as i see, in version ESPHome 1.4.0: the meter calibrated. how i can use this calibration option, when i already have converted firmware?
p.s. i already have config in my esphome dash board with my custom config.

[adamsthws]

@WildeRNS - Yes, you can add it to your own config. Your plug went through Tasmota, which erased the calibration Sonoff stored on it, so there are two steps:

1. Add the calibration to your config. From ESPHome/sonoff_s60.yaml, copy:

• the on_boot block at priority: 600 (it reads the board's 1.02 factor and any calibration the plug still has)
• the globals raw_power, meter_factor, calibration, calibration_status, calibration_from_backup and calibration_given
• the autoflash_calibration action under api:
• the Calibration text sensor
• the lambda filters on the cse7766 current, voltage, power and energy sensors (the energy one also adds to the daily/monthly/yearly/total globals, so take those too, or remove those lines)

Flash it from your dashboard. The Calibration sensor should now show missing, factor 1.02 (or 1.00): the board factor is applied, but the factory calibration isn't there yet.

2. Send the plug its factory calibration. The tool saved it in the plug's Sonoff backup. On the computer you ran the tool on, from the Sonoff-OTA folder, print it with:

python -c "import sys; sys.path.insert(0, 'tools'); from autoflash import plugs; from autoflash_cli import sonoff_backup_calibration as c; [print(b.mac, c((b.directory / 'flash.bin').read_bytes())) for b in plugs.backups()]"

That prints each backed-up plug's MAC address and a list of 18 numbers. In Home Assistant, go to Developer tools → Actions, switch to YAML mode and run:

action: esphome.<your_device_name>_autoflash_calibration
data:
  coefficients: [<the 18 numbers, as printed>]

The plug saves them, so you only do this once. They're kept through restarts and future updates, as long as your config keeps those globals. The Calibration sensor should then show from backup, factor 1.02.

If the command prints nothing, the backup isn't on that computer. You'll still have the board factor from step 1, which was most of the error (about 2%).

[WildeRNS]

thanks! everything went ok, i restored factory calibrations.