New to Homey coming out of home assistant. I have read a few of “Flow does not start” topics here but I did not manage to find a solution.
I have created a very simple flow to turn on my water boiler through a smart switch, if the water temperature is bellow a value on specific days and times.
The second “leg” of the same flow checks when the temperature has exceeded a certain value and then it should turn the boiler off.
When I test it, it runs fine, turning the switch ON & OFF when the specific temperature thresholds have been reached.
But it will not start / run automatically in the morning.
Can anyone please let me know what might be wrong ?
The strange thing is that the flow works fine while testing. I click the initial trigger of the first “leg” when the temperature is bellow the value set, the switch turns on and then after a few minutes it turns off, having read the temperature correctly when above the threshold.
So the trigger of the second leg works just fine. But it is identical to the trigger of the first leg !
When using day / time conditions, it’s possible the (not very often triggered) temperature trigger will be ignored.
In addition to the temperature triggers, you’d add the time triggers to the boiler as well
When..
it’s 6.15
AND..
temperature is less than 55
Then..
Start boiler
When..
it’s 23.40
AND..
temperature is more than 62
Then..
Stop boiler
It seems like a valid argument but it will keep the boiler turned ON all day switching it OFF at night.
The boiler takes a few minutes to reach the cut off temperature and a few hours to cool bellow the lower value. During this “cooling” time I d like to have it turned off. Theoretically this On/OFF sequence can take place several times during those 15 hours.
Add a time line card to verify that your flow is never triggered.
“When the temperature becomes lower then 55 degrees” will never trigger when the temperature is already below 55 degrees. So most likely that is the case.
If the temperature falls below 55 overnight (between 23:30 and 06:15) then your flow will trigger but do nothing. If the temperature now stays below 55 (the heater has not come on so this will be the case) then your flow will never trigger because you already missed the moment when the temperature became below 55.
That’s why you need an additional trigger as well as what you’ve got which triggers when the time is 06:15 and checks whether the temperature is below 55 → switch the heater on exactly as @Peter_Kawa stated (and the equivalent one to trigger at 23:30 and switch heater off if temp > 61).
This will not result in the heater staying on all day as you suggested (unless your heater is broken) because at some point your water will reach 62 and your existing flow will turn the heater off at that point.
Hi @Va_Tzanetis ,
I hope the first part you missed and now understand is that a trigger starts only at that single event, when the result turns from No to Yes.
The solution proposed by @Rmb is good for testing and finding the right triggers. For standard usage I would avoid it where possible. Homey would start unnecessarily often. @Peter_Kawa 's solution is the right way, but you had four time conditions in your original flow.
So probably the temperature grew between 6:15 and 7:40 beyond the 61°C and as you did not tell it to check at 7:40 it kept on heating until it would by any reason drop below 61°C, which might happen - depending of the configuration of the heater itself - when you take a long hot shower, but probably not too often.
. If it is not too complex for you I would propose something like in the Multiple conditions example.
So you start with all triggers you can think of, *temperature drops below 55°C, increases above 61°C, time is 06:15, 23:30, 07:50, 23:40 and combine them with ANY then you check again all conditions Temperature is below 55°C or above 61°C, time is between 06:30 and 23:30 resp. 07:40 and 23:40, and it is a weekday.
Then you combine the combinations you want with an ALL card and in one case you switch on and ion the other one you switch off. I guess it is still legibile with your conditions, but you might think about why you need the different time zones and do not unify them as far as possible. If you do not understand what happens, when it works different from your expectations, you might return to more distinct trigger, i.e. starting points, even if those flows would look quite similar.
I apologize I totally missed the “in addition” part. That’s what happens when I post after midnight. No need to jump to conclusions. I ll certainly give it a go tonight.
Thanks for your solution and explanation. I ll give it a go with a simpler time card tonight and should it not work, I ll try the Multiple trigger scenario with ANY/ALL cards. Thanks very much.
Create Variable called (say) BoilerON? and set it to No
WHEN {Day is a,b,c…} AND {Timey-time between x & y} AND {BoilerON is YES}
[Variable is True - so this is the Blue connection Line:] AND {Temp<61} THEN {Switch Boiler Off} THEN {Set BoilerON to NO} AND [Send Ok & failed msgs to you}
[When BoilerON is No then the variable test is False - so this is the Orange Connection Line:]
AND {Temp<52} THEN {Switch Boiler On} THEN {Set BoilerON to Yes} AND [Send OK & failed msgs to you}
