Energy Saving - FengtianGu/Sonoff-Tasmota GitHub Wiki

Using the Sleep command you can instruct Tasmota to sleep for the set milliseconds in its main cycle. While sleeping your device will consume less power.

Dynamic Sleep is enabled by default with a value of 50. To continue using Normal Sleep you may disable it by using the command:

SetOption60 1

Setting Sleep to lowest value 1 reduces power consumption already about ~30% in idle mode (relay off) and button presses are still noticed without any delay. Setting this around 50 ms reduces power consumption from ~1.1 W to ~0.6 W on an idling (relay off) device and button presses are still noticed correctly. With this setting you have to concentrate very hard to click the button so fast that it is not recognized by the device.

If your device needs to do something continuously, this will be affected. E.g., device LED will flicker and Sonoff POW will not be able to correctly total the energy consumption. Spot readings of power, voltage, etc. will however remain correct.

From the release notes: Expect overall button/key/switch misses and wrong values on Sonoff Pow

Also, if using KNX IP Protocol, Sleep needs to be 0 in order to avoid losing any telegram.

Notes:

• Starting with Tasmota 6.1.1.12 Sleep ≠ 0 has no impact on real time related commands like Uptime, Delay, PulseTime, TelePeriod and Blinktime.
• As the WiFi Modem on an ESP8266 is the major consumer - using Sleep with WiFi AP mode enabled is more or less without effect.

Most low-price plug-in home energy meters like Sonoff devices are very imprecise for power consumption < 10 W and become more and more imprecise for power consumption (< 1.5 W). Furthermore, the results of such meters are very strongly dependant on the load type (capacitive/inductive) and are absolutely imprecise for non-ohmic load types having switch-mode power supplies.

In addition, using Sleep - which periodically cycles the power of the device between 20% and 100% - on such meters makes their readings more or less useless.

The following measurement was done directly on 230 V/AC line using a Sonoff Dual R2 and two different Sonoff S20 connected on different MID calibrated meter (Eastron SMD630 MID/saia-burgess ALE3).

Device	Sleep 0	Sleep 1	Sleep 50	Sleep 200
Sonoff Dual R2	1.24 W	0.84 W	0.76 W	0.68 W
Sonoff S20	1.11 W	0.77 W	0.59 W	0.51 W

All measurements were done with

• WiFi STA mode, enabled and connected (70%)
• MQTT enabled and connected
• Syslog enabled and connected
• TelePeriod 60 for debugging
• Relays off
• Measurement period of 24-56 hours to reduce measurement discrepancies

The first impression is that a higher sleep value reduces the consumption, but only slightly. The second result is that using Sleep <value> (value ≠ 0, e. g., 1) is good enough to reduce the power consumption anywhere between 1/3 and up to 45% (value=200).

To find out why Sleep reduces the power consumption and how its value should be set, the current of the 3.3V DC ESP8266 of an ESP-12 module was measured using an oscilloscope and (for easy reading the oscilloscope diagram) a 1 Ω shunt which results in a 1:1 interpretation between voltage and current.

This measurement simplified the measure of a time based power consumption; no integration must be done. On the other side note that the quantity measurement does not respect the effectiveness of the complete device circuit.

Using Sleep 0 there are no delay() calls in Tasmota main loop and therefore the power consumption is continuous at current ~80 mA:

Due to the fact that the Tasmota main loop now calls delay() (even with 1ms) it seems it results in periodically (100ms) enabling the WiFi Modem Sleep mode within the WiFi Manager library. It results in periodically lowering the current to 15-20 mA for ~90ms of each loop:

By increasing the sleep value, there are more and more ~90ms periods with additional lowering of the current to 8-10 mA - I really don't know where this comes from:

As already noticed with Sleep 100 the number periods having 8-10 mA instead of 15-20 mA increase again:

The quantity measurement confirms the suspicion that a Sleep value ≠ 0 results in reducing the power consumption about 1/3.