# Am I doing something stupid?

**URL:** <https://community.homey.app/t/am-i-doing-something-stupid/69123>\
**Category:** Flows\
**Tags:** advancedflow\
**Created:** [September 19, 2022, 2:43pm UTC](https://community.homey.app/t/am-i-doing-something-stupid/69123 "2022-09-19T14:43:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![FranklyEpic](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/franklyepic/32/48229_2.png) [@FranklyEpic](https://community.homey.app/u/FranklyEpic)\
**Post date:** [September 19, 2022, 2:43pm UTC](https://community.homey.app/t/am-i-doing-something-stupid/69123/1 "2022-09-19T14:43:26Z")

</div>

I may have just confused myself with which category to post this in, so many apologies if I have put it somwhere it shouldn’t be!

I am having great fun with advanced flows, in particular the fact I can have multiple triggers. However, I may have gotten myself stuck. In the attached example, will Homey know to check the “and” statement regularly or more than once?

Basically, the modes are covering a whole bunch of automation, so daytime turns things off and on everyday. However, if the light % outside is low (grey, wet, dull and horrible) then its going to do something different.

My question is, say its a nice sunny day when that happens but an hour later it goes disgusting, will homey know that, from this flow?

Thanks in advance!  
N

 ![Screenshot 2022-09-19 152729](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/7/571ed5cd6ed0d1cab622fed4988f5115b32050ed.png)

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [September 19, 2022, 3:35pm UTC](https://community.homey.app/t/am-i-doing-something-stupid/69123/2 "2022-09-19T15:35:21Z")

</div>

The And cards only gets ‘read’ when a triggercard fires.  
When you want a light dependable flow, add something like this to your flow:  
(`LichtsterkteNEP%` is just my name for your Light Percentage tag)

 ![Screenshot from 2022-09-19 17-33-08](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/d/4d3fac2f46c09d54ca196df46bd9a0a1b8199524.jpeg)

---

<div class="post-metadata">

**Author:** ![FranklyEpic](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/franklyepic/32/48229_2.png) [@FranklyEpic](https://community.homey.app/u/FranklyEpic)\
**Post date:** [September 19, 2022, 3:37pm UTC](https://community.homey.app/t/am-i-doing-something-stupid/69123/3 "2022-09-19T15:37:21Z")

</div>

Got it, I had thought that would be the most likely case but because I have an OCD, I liked to have all the modes on one flow… 🤪

Thank you for your help

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [September 19, 2022, 3:42pm UTC](https://community.homey.app/t/am-i-doing-something-stupid/69123/4 "2022-09-19T15:42:55Z")

</div>

YW!  
You can do it within one Aflow, just connect the blue output of the “is is-it-TooDarkOutside” logics card to the `any` card in front of your “is turned off” card

 ![Screenshot from 2022-09-19 17-41-14](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/8/a80f47f3e38efd84326fe6bb3f900b2da7e47b81.png)

---

<div class="post-metadata">

**Author:** ![FranklyEpic](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/franklyepic/32/48229_2.png) [@FranklyEpic](https://community.homey.app/u/FranklyEpic)\
**Post date:** [September 19, 2022, 4:01pm UTC](https://community.homey.app/t/am-i-doing-something-stupid/69123/5 "2022-09-19T16:01:11Z")

</div>

Got it… Doing that prompted me to use my big brain and I found a solution. The app i am using for light % did not have an obvious triggercard but the “change” trigger included the light % so problem solved!

Thanks again,  
Nick