Two separate fixes landed on 14 October 2026 for Sonoff's S60 smart plugs, and both deal with the same weak spot: small loads. If you track a phone charger, a router or an LED lamp on one of these plugs, the readings have probably looked wrong.

Zigbee S60ZBTPF and S60ZBTPG: firmware 2.1.3

Sonoff firmware 2.1.3 for the Zigbee S60ZBTPF (Type F socket) and S60ZBTPG (Type G, the UK socket) was added to zigpy-ota, the firmware index used by the zigpy library that powers Home Assistant's ZHA integration. The release notes list one change: correct voltage, power and energy readings for loads below 110 W. The submitter marked the image as tested on a device, and it becomes the newest S60 image in the index, after 2.0.6.

Adding it to zigpy-ota is what makes it available to zigpy-based setups. Other Zigbee hubs and Zigbee2MQTT use their own firmware sources, so check there before assuming the update is waiting for you.

ESPHome: no more false zeros at a few watts

The second fix is for plugs running ESPHome, such as the Wi-Fi S60TPF with its CSE7759B metering chip handled by the cse7766 component. These chips can only calculate power once per energy pulse, and pulses get rarer as the load shrinks: about 2 ms apart at 2 kW, about 2 s apart at 2 W. Between pulses the driver reported 0 W. In Marcus Voß's measurements a 2.2 W lamp read zero in 75 of 79 reports, so an automation could decide that a running device was off.

Pull request #20631 keeps the last measurement while the next pulse is not yet overdue. Only loads with more than 1 s between pulses take the new path, which on the S60 means below about 5.4 W. The exact threshold depends on each device's calibration. Higher loads, including their time to show 0 W after switching off, behave exactly as before. The energy counter is unchanged because it counts pulses.

There is a trade-off, and the pull request spells it out. When a very small load switches off, 0 W now takes longer to appear: about 4 s at 2.5 W, 4.8 to 6.6 s at 1.7 W, and up to about 16 s below 1 W, where the chip's own timeout takes over. If an automation needs to react to a tiny load turning off within a second or two, keep that delay in mind.

The ESPHome change was merged into the development branch while 2026.10 is in beta, so expect it in a later release rather than 2026.10.0.