Dear community, i have created an advanced flow for my blinds.
Essentially the idea is to lower the blinds in my house by “following” the sun to keep the temperature inside the house manageable.
I have a fibaro smart sensor which works without any issue and i set the flow to start based on luminance and temperature levels (as per picture).
However, it is now 12.04pm, the sensor tells me that it is reading 914lx and the temp is 26 celsius (the sensor reported the luminance to homey 14 mins ago). Any reason why the flow related to time between 11.30 and 14.30 does not start?
Did i do anything wrong in the start of the flow?
You would probably need to use the time trigger to:
trigger every N minutes
test for the lux and/or temp conditions
test for the time window
execute what you want
I wouldn’t trigger any flow more often than every 5 minutes.
You could use Action Scheduler to execute every 5 minutes during the hours of 10-14. This would prevent unnecessary triggers. Time pattern for the app would be */5:10-14 meaning during the hours of 10:00 - 14:59, trigger every 5 mins.
Ok - thanks a lot!
I am clear about the triggering each N minutes and i will have a look into action scheduler.
The question is can I use always action scheduler to test lux and temp via the sensor?
Thanks
Ok thanks - i will have a look also on the advanced scheduler and then maybe come back to you if i have more questions…(i am quite new to homey so not that advanced yet) thanks for your patience and support
That would be neat, but can’t get it to work. Is it me?
While it is always a good practice to keep an eye on all triggers going on, I see no real issues in using a ‘every 5mins’ trigger, with a little variable delay (to prevent multiple triggers triggering flow conditions and -actions simultanuously).
Imho things can go really wild when one uses, like, every 1 or 2 or 3 sec triggers.
my simple advice is do not overthink,(KISS principle - Simple English Wikipedia, the free encyclopedia) the @jobs (date and time) are cronjobs in homey.
Drilling down using te date, time and seconds of the date and time cards should provide the requested results.
What happens after your Conditions on the right? (At the RED Arrow Down)
I don’t see Lines out of the Right-most conditions
So I guess you can’t know if the Trigger was active.
Hi @Dijker here is my complete flow…the bottom left part is the continuation but if i cannot fix the top part first it makes not so much sense to work on the rest.
@Peter_Kawa many thanks. I will clearly try your suggestion and let you know if that works.
As you can see i have added also a logic condition i.e. “Tapparelle EST Run” equal to NO.
This is because, at the end of my flow i have added also a logic condition according to which if the flow is completed the variable is set to yes.
Basically i am trying to avoid that within the same hour the same flow is triggered multiple times.
I do not know if this is the correct workaround for that
To ensure that this logic works everyday i have then created a condition base on which every day those variables are re-set to NO
Maybe i am messing around with this one and making it too complex but i am learning in between.
I think when you move the logic conditions like “Tapparelle EST Run is equal to no” right after the trigger delay, the rest of the flow stops and doesn’t get evaluated anylonger when these variables are Yes.
Although this is a bit ‘nitpick’ mode, it is a good practice to check which conditional cards stops a flow for the longest time every day in this case if the Tapparelle EST has run or not.
Like, the summer/spring cards only stops the rest of the flow in autumn/winter.
Oh, your ‘time is in between’ cards have the same values.
Thanks for the tips Peter. So this is how i have re arranged the flow (need to reorganize to make it having a tidier look) but essentially is this how it should be>
