mirror of https://github.com/arendst/Tasmota.git
Updated Energy Saving (markdown)
parent
bbeebd8b85
commit
6a149d189c
|
@ -21,9 +21,9 @@ Also, if using [KNX IP Protocol](KNX-Features), `Sleep` needs to be 0 in order t
|
|||
|
||||
## Sonoff power consumption and measurement
|
||||
|
||||
The result of the most low price plug-in home energy meters are very imprecise for power consumption < 10 W and become more and more imprecise for power consumption like Sonoff devices have (< 1.5 W); furthermore the results of such meters are depending very strong of the load type (capacitive/inductive) and is absolutely imprecise for non-ohmic load types having switch-mode power supply like Sonoff devices.
|
||||
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 like Sonoff devices.
|
||||
|
||||
Additional to that, using `Sleep` - which periodically cycles the power of the Sonoff between 20% and 100% - the result of such meters are more or less useless.
|
||||
In addition, using `Sleep` - which periodically cycles the power of the Sonoff between 20% and 100% - on such meters makes their readings more or less useless.
|
||||
|
||||
## Example of power consumption
|
||||
|
||||
|
@ -45,11 +45,11 @@ All measurements were done with
|
|||
- Relays off
|
||||
- Measurement period of 24-56 hours to reduce measurement discrepancies
|
||||
|
||||
The first impression is that a higher sleep value reduce the consumption, but slightly. The second result is that using `Sleep <value>` (`value` ≠ 0, e. g. 1) is enough reducing the power consumption at minimum 1/3 up to 45 % (value=200).
|
||||
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).
|
||||
|
||||
### Quantity measurement of ESP-12 module/ESP8266 3.3V line
|
||||
|
||||
To find out why Sleep reduce the power consumption and with which quantity, the 3.3 V DC current of 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.
|
||||
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 Sonoff circuit.
|
||||
|
||||
|
@ -58,15 +58,15 @@ Using `Sleep 0` there are no `delay()` calls in Tasmota main loop and therefore
|
|||
![sleep 0](https://user-images.githubusercontent.com/6636844/36341353-2c67b1e8-13ed-11e8-8e45-b75136704291.png)
|
||||
|
||||
#### Sleep 1
|
||||
Due to the fact that the Tasmota main loop now calls `delay()` (even with 1 ms) it seems it results in periodically (100 ms) enabling the WiFi Modem Sleep mode within the WiFi Manager library. It results in periodically lowering the current to 15-20 mA for periodically ~90 ms:
|
||||
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:
|
||||
![sleep 1](https://user-images.githubusercontent.com/6636844/36341400-f129a18a-13ed-11e8-882b-d6640a0c5d61.png)
|
||||
|
||||
#### Sleep 100
|
||||
Further increasing the sleep value there are more and more ~90 ms periods with additional lowering the current to 8-10 mA - I really don't know where this comes from:
|
||||
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:
|
||||
![sleep 100 1](https://user-images.githubusercontent.com/6636844/36341463-04485df0-13ef-11e8-8f93-2b6d4c42b4b1.png)
|
||||
|
||||
#### Sleep 250
|
||||
As already noticed with `Sleep 100` the number periods having 8-10 mA instead of 15-20 mA are again increasing:
|
||||
As already noticed with `Sleep 100` the number periods having 8-10 mA instead of 15-20 mA increase again:
|
||||
![sleep 250 1](https://user-images.githubusercontent.com/6636844/36341493-5696bf48-13ef-11e8-8155-44ac90200df8.png)
|
||||
|
||||
The quantity measurement confirms the suspicion that a sleep value ≠ 0 results in reducing the power consumption about 1/3.
|
||||
The quantity measurement confirms the suspicion that a `Sleep` value ≠ 0 results in reducing the power consumption about 1/3.
|
||||
|
|
Loading…
Reference in New Issue