- Posted on
Tue Sep 19, 2017 4:42 pm
-
jay (support)
offline
- Site Admin
-
- Posts: 18260
- Joined: Mar 19, 2008
- Location: Austin, Texas
-
Thoughts: first, you're actually describing a triggering event (you want it to fire when humidity level becomes less than a calculation based on a variable value). This isn't a condition but rather an event. Further, if you know the value at which the fan kicked on (because you coded the value into the the triggering event) then you can just use that as the basis for the calculation, and then use a normal device state changed trigger to turn the fan off.
Second, you're saving off the humidity value to a variable when you trigger - instead, it seems like you'd save off the calculated target value into a variable rather than the start value. This would be an action rather than a condition (and there may be a plugin that does that but I don't recall what it is).
So, based on this use-case, I don't think you're looking for calculations in conditions, but rather calculations as part of events and/or calculations as part of actions. Is that a fair assessment?