Task Settings - Delay vs Interval

Moderators: grovkillen, Stuntteam, TD-er

Post Reply
Message
Author
whatsupskip
Normal user
Posts: 98
Joined: 28 Feb 2018, 07:40

Task Settings - Delay vs Interval

#1 Post by whatsupskip » 28 Feb 2018, 07:49

Just started using ESP Easy and I was confused by the field name "delay" in the Task Settings section. After some reading of the wiki it became clear what was meant by the term "delay".

I believe for reasons of clarity, the field name should be "Interval", rather than "Delay".
It is possible that a sensor reading has both an interval (frequency at which the reading is taken) and a delay (the time between the sensor being turned on and the actual reading being taken).

User avatar
grovkillen
Core team member
Posts: 3334
Joined: 19 Jan 2017, 12:56
Location: Hudiksvall, Sweden
Contact:

Re: Task Settings - Delay vs Interval

#2 Post by grovkillen » 28 Feb 2018, 08:59

Yes that makes more sense. Possible to add an issue on git?
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you :idea: :idea: :idea:

7keys
Normal user
Posts: 16
Joined: 23 Feb 2018, 13:30

Re: Task Settings - Delay vs Interval

#3 Post by 7keys » 28 Feb 2018, 09:57

is it possible ...

espeasy -> sleep mode (300s) ->wakeup-> read value temperature -> value = 38 -> esp sleep (300s)

wakeup -> read value temperature -> value = 38 -> not send to mqqt, no enable wifi - because there is no change in the sensor reading -> esp sleep mode (300s)

this setting is to save a maximum of battery.

whatsupskip
Normal user
Posts: 98
Joined: 28 Feb 2018, 07:40

Re: Task Settings - Delay vs Interval

#4 Post by whatsupskip » 28 Feb 2018, 10:27

7keys wrote:
28 Feb 2018, 09:57
espeasy -> sleep mode (300s) ->wakeup-> read value temperature -> value = 38 -> esp sleep (300s)
I understand this.
7keys wrote:
28 Feb 2018, 09:57
wakeup -> read value temperature -> value = 38 -> not send to mqqt, no enable wifi - because there is no change in the sensor reading -> esp sleep mode (300s)
I understand this, but I don't understand how you would configure it to do this. Also there will be situations where this isn't a good idea. That is the reading may not have been the same, but the reading was not received because of a comms issue or something else.

I am not sure what any of this has to do with the field name though.

7keys
Normal user
Posts: 16
Joined: 23 Feb 2018, 13:30

Re: Task Settings - Delay vs Interval

#5 Post by 7keys » 28 Feb 2018, 10:40

I am not sure what any of this has to do with the field name though.
it has nothing to do.

but I thought that someone might know how to do it .. in espeasy.
example:

Code: Select all

print("#"..i.."\t"..sid.."\currenttemperature: "..curtemp.."\lasttemperature: "..(lasttemp / div))
        rtcmem.write32(i,(curtemp * div))
        if (curtemp * 1) == (85 * 1) then bug85 = true end
       [b] if (curtemp * 1) ~= (lasttemp / div) then[/b]
            update = true
            
That is the reading may not have been the same, but the reading was not received because of a comms issue or something else.
the problem is solved by reading the time of the last measurement..

ok sorry for leaving the topic thread.

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 20 guests