User Timers #1091
User Timers #1091
Conversation
|
+1 on this... was just looking through the codebase and issues to see if tasmota had schedule/timer feature support without explicit need for external command input |
|
+1
While I don’t have a use case for timers, I would like to see feature rich Tasmota.
While code space might be a concern, I don’t believe in universal images and think everyone should compile their own image with settings and modules they actually need.
In the end, if someone really needs everything, we might want to work on automated 2-step upgrade procedure (minimal+full) to break past infamous 512kb limit.
//_ on phone
… On Oct 30, 2017, at 08:24, Jens J. ***@***.***> wrote:
+1 on this... was just looking through the codebase and issues to see if tasmota had schedule/timer support without explicit need for external command input
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Hi, Do you plan to add timer for relays ? |
|
Nope. Not at this time. |
|
Hi, Do you plan to add status of switch button state without relays set ? I discovered issue with Wemeos, that no commands button options not works at all either button or switch, I canot switch to AP reset to default etc. |
|
what sort of timer are you looking for?
we already have a timer to shut off a relay after a specific time (see
pulsetime)
other than that, you are probably better off doing the timing with your home
automation system.
|
|
Hi, It nice to have autonomus device, scheduler is always extent :-), BTW haw to use that timer set to relay start or stop after some period time i.e. 15 min after switch on, automaticaly switch off after that period time. |
|
On Wed, 29 Nov 2017, roblad wrote:
It nice to have autonomus device, scheduler is always extent :-)
True, but the code space is limited, and the mission of Tasmota is not to do
everything possible, but to allow a MQTT server to control everything possible
, BTW haw to
use that timer set to relay start or stop after some period time i.e. 15 min
after switch on, automaticaly switch off after that period time.
this is exactly what pulsetime does.
|
|
Hi, Haw to set for 15 min 112..64900 | Set PulseTime for relay with 1 seconds increment starting with 12 seconds (113 = 13 seconds etc.) |
|
On Wed, 29 Nov 2017, roblad wrote:
Haw to set for 15 min
112..64900 | Set PulseTime for relay<x> with 1 seconds increment starting with 12 seconds (113 = 13 seconds etc.)
15 min is 900 seconds, so 112+900=1012, set pulsetime to 1012 and it will turn
off after 15 minutes
|
|
Hi, I did not think about it :-) |
|
+1 |
|
I am new user of Sonoff. I loaded the TASMOTA on my 4Ch Sonoff. |
|
@flexiti can you send me complete code for sonoff basic ??? i had changing code but error on arduino. thanks !!! |
|
Hi @flexiti, I also would like the code. Thanks. Edit: Tried the timers code on v5.12.0c but found that now there is a lot to update. Several internal variables from tasmota have changed. So should be needed a rework to adapt timers to new tasmota version. |
|
The code was complete for the previous tasmota version, now there are some conflicts. I suppose that new patterns for colored leds chains are more important ;) If there is a demand, I can publish it in my fork |
|
@flexiti if it's published in your fork, that wonderful |
|
It is published on: https://github.com/flexiti/Sonoff-Tasmota branch usertimers Do not use //#define ONOFF_TEMPERATURE_LOWHIGH // timer on/off is temperature dependent |
|
Hi @arendst, I have automated my patio watering for irrigation of my plants but there, my wifi is weak. So, using Home Assistant to tell Sonoff Tasmota to open valves is not an option. One solution can be using timers like the ones proposed by @flexiti. Timers are an alternative. Can be added this feature to the main version as an optional? I tested that version and works but would be great to have that on the main tasmota 😄 |
|
Is there relly no chance to force the implementation of a timer in the "original" repository a simple timer function based on a electronic timer? :-// It would be a great feature for users like me to have "one" firmware to switch with commands from a controller e.g. FHEM and a simple timer function within the unit for areas without WLAN or LAN-access. I would like to have a timer for security reason during my holiday.... without connection to FHEM-controller... |
|
Convinced. I'll start working on timers keeping in mind the current @flexti implementation as documented in this PR but as a separate xdrv_09_timers.ino file. Stay tuned... |
|
Great! Thanks a lot!
El jue., 22 de mar. de 2018 09:45, Theo Arends <notifications@github.com>
escribió:
… Convinced.
I'll start working on timers keeping in mind the current @flexti
implementation as documented in this PR but as a separate
xdrv_09_timers.ino file.
Stay tuned...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1091 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ahw-h1enszvydUm0JWfnKNRtv9sf9Fs9ks5tg5zqgaJpZM4QKSA6>
.
|
5.12.0i * Add 16 timers using commands Timer and Timers (#1091)
|
Timers are great and useful. Please consider replacing |
|
@ionciubotaru Nice idea but would take too much storage as the backlog string will need to be cached. So for now you will have to setup three different timers. That's why you have sixteen of them :-) |
|
Many thanks!!! for the timerfunction -it works great 👍 At time I have two newbie questions: |
|
To "delete" a timer you could set Arm to disable (0) or in the next release use command I'm working on an optional "small" web config page. Have it functional but still too big for production (7k).
|
|
Works Great!!! Thanks!! 👍 |
|
Would be great to see this integrated with #481, have a power option of auto which would then allow entry of upper and lower limits |
|
Is this implemented in the current 5.12 release? I'm not seeing a timer option in the menu? |
5.12.0i * Add 16 timers using commands Timer and Timers (arendst#1091)
I sent it from a temporary git repository that I have already removed (maybe too fast ), if there are any problems I can re-publish.😉#define USE_USERTIMERS //Local timers funcionality active
;;; if not defined, there is no user timers, only config memory is alocated for future compatibliity
;;; no extra code is generated if not defined
#define USE_USERTIMERSWEB // view user timers on WEB
;;; timer are programed via MQTT, if this define is active, also via WEB interface
;;; user timer code is generated , without web code
#define MAX_USERTIMERS 16 // fixed configuration memory max size , do not change it
;;; fixed max config size
#define USED_USERTIMERS 8 // realy used timers 1 to 16
;;; actualy used timers 8
13:09:54 MQT: main/sonoff/33/tele/STATE = {"Time":"2017-10-29T13:09:54", "Uptime":0, "POWER1":"OFF", "POWER2":"OFF", "Wifi":{"AP":1, "SSId":"T100", "RSSI":90, "APMac":"00:1E:8C:CE:F7:93"}, "UTimers":8}
;;; "UTimers":8 menas that we have used 8 timers ( info for other apk)
13:29:35 MQT: main/sonoff/33/tele/INFO1 = {"Module":"Witty Cloud", "Version":"5.8.0p", "FallbackTopic":"DVES_CD0211", "GroupTopic":"sonoffs", "UTimers":"8"}
;;; the same at startup module info
Command:
Topic: UTimer5
Payload: {"UTimer":{"UTrelay":2, "UTtime":"09:23","UTmode":1,"UTday":"21","UTonce":1}}
(Not all parameters must be specified)
;;; Command UTimer1 ... UTimer(USED_USERTIMERS)
;;; UTrealy = Relay no
;;; UTtime = action time
;;; UTmode = action type: 0 -nop, 1 -on, 2 -off
;;; UTday = day (2 digits Hex value, bit 0 - Mon, bit 1 Tue,...
;;; UTonce = one time action if 1, after that mode automaticly set to nop
Validation of the entry is weak, but it does not have bad affect to the sonoff.
You can add something here , For example, the time must only be in 06:30 format, not 6:30, but we use less memory 😉
13:10:03 CMD: UTimer1
;;; Timer status
13:10:03 MQT: main/sonoff/33/stat/RESULT = {"UTimer":{"No":1, "UTmode":"1", "UTtime":"12:11", "UTrelay":"1", "UTonce":"0", "UTday":"41"}}
;;; answer
User timer number 1, will on relay1 at 12:11 every monday and sunday