To me it looks like a bug on the ewelink side or another undocumented logic of the scenes where A will not work if C occurs… It’s hard to say, @songal needs to comment.
Does the scene work and the trigger respond when there are no time settings at all?
Only bare IF for temperature and Then?
In this configuration, the scene is active all the time and the trigger to release it is a change in temperature. If it doesn’t work here, then the logic behind the sensor is to blame and it doesn’t work properly as a trigger, but it’s ewelink’s fault, not the user’s.
Since it works without a time interval, it looks like there is a problem in the correlation between the temperature-based trigger and the “Effective period” variable…
If you can, take this temperature sensor in your hand and heat it to 20C and let it drop below 18C. If the scene does not execute for the trigger, it is probably a problem with ewelink and how the triggers are handled in the case of variable temperature.
Hi Morgan, thank you. Yes that is exactly it. I tested using a different, non temperature based trigger and it works fine, I then did as you suggested and altered the temperature, to pass over a threshold during the effective period and it again worked, so YES it only works if the temperature passes that set threshold during the effective period. What a shame, could have been so good. Thanks again for all of your help.
This is quite a typical behavioral logic process. There must be a primary change to initiate action.
This is a domino effect - the fact that the dominoes are placed does not mean that it will initiate a reaction, the first touch is needed for a chain reaction to occur.
You will need 2 separate scenes one for the ON condition one for the OFF condition
for example
scene 1
If conditions… (temp > min_temperature)
then ON
Scene2
if conditions … (temp > max_temperature)
then OFF
Because each scene defines a SPECIFIC action, there is no implicit actions generated.
you have to declare each action SEPARATELY, there is no if/then/else condition with multiple actions.
Please note that min_temperature should be different from max_temperature.
This scenario will not be triggered at 10:00 on the dot, even if the temperature ≤ 18°C condition has been met before 10:00 on the dot.
You set the “Effective period” between 10:00 and 11:00, that is to say, after 10:00 and until 11:00, “IF” condition is triggered only after the change of the temperature is satisfied.
Thanks Viron, yes, this was where I had started. And then I noticed the “Effective period” control, which looked as if it was designed to overcome this rather cumbersome aproach. Hey ho. I will probably go back to my first plan which was to write the controls in Python using an Arduino.
Thank you Songal, It would be interesting (although now rather pointless) to know just how much the temperature would need to change for this to trigger. It has never triggered for me, despite a number of scenes and a number of days running with varying temperatures through thos periods. Anyway the tool is not suitable for my purpose, or at least there are better solutions, So it is of little point discussing further.
Just wanted to feed back that I have managed to produce a fairly effective heating control solution using ewelink. After trying a couple of other alternatives I came back and tried another aproach. This is how it works -
A scene to simply switch on the system at the required time(s).
A scene to switch it off at the required time(s).
A scene to switch off when we reach the upper temperature (this works fine with “effective period” as the temperature changes during the EP to get to the upper temp.
A scene to switch on (again using effective period) when the temp drops to my lower limit.
A set of four scenes such as this for each heating period - works just fine.
Thanks again all.
