mirrors
/
Tasmota
mirror of https://github.com/arendst/Tasmota.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Energy Saving (markdown)

Michael Ingraham 2019-02-23 10:44:36 -05:00
parent 2b4c1144ed
commit bc72bd0998
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Energy-Saving.md

@ -1,10 +1,10 @@
Using the [Sleep command](https://github.com/arendst/Sonoff-Tasmota/wiki/Commands#management) you can instruct Tasmota to sleep for the set milliseconds in its main cycle. While sleeping your device will consume less power.
Using the [Sleep command](Commands#sleep) you can instruct Tasmota to sleep for the set milliseconds in its main cycle. While sleeping your device will consume less power.
As of 6.3.0.15 Dynamic Sleep is enabled by default with a value of 50. To continue using Normal Sleep you may disable it by using the command:
As of 6.3.0.15 [Dynamic Sleep](Dynamic%20Sleep) is enabled by default with a value of 50. To continue using Normal Sleep you may disable it by using the command:
`SetOption60 1`
[Click here to see the Wiki for Dynamic Sleep](https://github.com/arendst/Sonoff-Tasmota/wiki/Dynamic%20Sleep)
[Click here to see the Wiki for Dynamic Sleep](Dynamic%20Sleep)
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) sonoff 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.
@ -23,7 +23,7 @@ Also, if using KNX IP Protocol, sleep needs to be 0 in order to avoid losing any
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.
Additonal to that, using Sleep - which periodicaly cycles the power of the Sonoff between 20% and 100% - the result of such meters are more or less useless.
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.
## Example of power consumption
@ -41,7 +41,7 @@ All measurements were done with
- WiFi STA mode, enabled and connected (70%)
- MQTT enabled and connected
- Syslog enabled and connected
- `Teleperiod 60` for debuging
- `Teleperiod 60` for debugging
- relays off
- measure period of 24-56 h to reduce measuring fault
@ -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 peroidically (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 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:
![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 additonal lowering the current to 8-10 mA - I realy don't know where this comes from:
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:
![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:
![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 reduce the power consumtion about 1/3.
The quantity measurement confirms the suspicion that a sleep value ≠ 0 results in reduce the power consumption about 1/3.