Advance Flow (s) do not engage (start)

I combined most of the suggestions from the earlier reactions:

It doesn’t matter what day it is or what the temperature is: the boiler turns off at 23:30. Even on a sunday if you turned it on manually.

It doesn’t matter what day it is or what time it is: the boiler turns off when the temperature is above 61⁰.

At 6:15 the temperature is most likely below 55⁰. So if it not a sunday the boiler will turn on.

Between 6:15 and 23:30 the boiler will turn on if it isn’t a sunday and the temperature drops below 55⁰

My thermometer reports only every 10-15 minutes: so only when the temperature changes it is useful to test the conditions.

Off topic:

Let’s say the watertemperature normally drops in 54 minutes from 61⁰ to 55⁰ and the boiler needs 6 minutes to reheat to 61⁰. So 1 minute per 1⁰
So between 0:00 and 6:00 the boilers kicks in 6 times. 6 times 5 minutes is half an hour.
With the boiler turned of the temperature will drop slower when the watertemperature gets closer to the room temperature. Lets say the temperature drops to 35⁰.
To reheat the temperature from 35 ⁰to 61⁰ the boiler is on for 26 minutes. So you’re saving 4 minutes runtime.

1 Like

The scenario I posted last, above with the time card as trigger, did not run this morning.

@John_Loebenstein @Wim_Post Thanks for your latest input. I have revised the scenario as per Wims’ screenshot and see if it fires up tomorrow. I have narrowed down the time intervals so in case it does not fire up I ll still be at home to turn on manually so other people will have hot water to shower with.

The revised flow is as follows

But 15 Jan is a Thursday. You specified to only run Mon, Wed & Fri.

Yes, It will (or try to) run tommorow morning.

Lt’s see if it fires up.

Because something is not happening as expected, you cannot be sure that the flow did not run.

So start with this simple flow to be shure that your flow starts:

WHEN the time becomes 08:00 THEN send a message to the time line.

First test the second card in this flow, the send message” by starting the flow manually. Then wait till 08:00. Or more practically, set the start time to 5 minutes after the current time.

The combination flow as suggested by @Wim_Post DID run this morning !!. It started and stopped as expected.

Thanks very much Wim and also thanks to all of you for the time and effort you took to contribute to this thread and help.

Thanks again.

2 Likes

Exactly that is the Why not, The WHEN {Day is a,b,c…} triggers only at midnight and at midnight the time is not between 06:15 h and 23:30 h or whatever time range you take, unless it is a range that includes midnight.

1 Like

Dirk,
Tks for pointing that out. You are right.
So the flow should be:
When – the time is between x and y
And – the Day of Week is a or b or c
And - water temp is < t1

Then – Turn boiler on
Or – water temp >t2
Then – Turn boiler off

Do you agree?

John

This will not work, as no such flowcard exists. You can only trigger at a specific time: WHEN the time is x. The card you are referring to is an AND card.

If you need to check something continuously during a specific period, an option is to run the flow e.g. every few minutes:

  • WHEN Every x minutes
  • AND The time is between x and y
2 Likes

I have a question.

It starts on 6:15 and comes then to the card BETWEEN 6:15 and 22:30. But it is still 6:15 and not between 6:15 and 22:30.

So if the execution is greater than 6 15 instead of equal AND greater than 6:15 then it will never execute.

Just a thought.

Kind Regards

Hi @Henk_Haveman ,
frankly I could not find a definition in the App, if between includes or excludes the borders. It might work at 6:15 h as the could be a few milliseconds before the test on between is performed. But it could be even worse at 22:30 h. To avoid this, you could just check, if it works - or check on between 6:14 and 22:31.

I was faster making ths testflow then typing the answer.


You have a point but it still works !