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).
Task Settings - Delay vs Interval
Moderators: grovkillen, Stuntteam, TD-er
-
- Normal user
- Posts: 125
- Joined: 28 Feb 2018, 07:40
- Location: Melbourne, Australia
Task Settings - Delay vs Interval
Friends with kangaroos and some time koala rescuer.
- grovkillen
- Core team member
- Posts: 3621
- Joined: 19 Jan 2017, 12:56
- Location: Hudiksvall, Sweden
- Contact:
Re: Task Settings - Delay vs Interval
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
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you
Re: Task Settings - Delay vs Interval
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.
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.
-
- Normal user
- Posts: 125
- Joined: 28 Feb 2018, 07:40
- Location: Melbourne, Australia
Re: Task Settings - Delay vs Interval
I understand this.
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.
Friends with kangaroos and some time koala rescuer.
Re: Task Settings - Delay vs Interval
it has nothing to do.I am not sure what any of this has to do with the field name though.
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
the problem is solved by reading the time of the last measurement..That is the reading may not have been the same, but the reading was not received because of a comms issue or something else.
ok sorry for leaving the topic thread.
Who is online
Users browsing this forum: No registered users and 123 guests