Works like a charm Arie! I love it 
Thanks for thinking with me and acting so fast.
Thanks, much appreciated!
Could you send me this post as PM?
N.b. I certainly plan on bringing al those new options into the mix, but those take some time.
Another question on your great app:
I used AVD’s when the status had to be set with the special status parameter.
However now you can use any variable as status. But the mobile app is not always updated so fast when a parameter is changed. Only the blocks “Set Status to …” have the option of forcing the update on the mobile app. For me that is the only reason to continue using these blocks. Is there any other option to force the mobile app update?
Thanks again
Well yes: dont use the status field anymore, its deprecated.
You can now use any textfield for the same purpose now. And it uses waaaay less resources.
I’ll give that a try too.
Then I have to update all of my existing AVD’s one by one in the coming time…
Yeah, that can take some time i suppose 
But believe me, textfield function much better and faster.
The whole reason i started building the AVD was a way of creating a device which could have a text indicator / status field. Back then, this was not possible, but i found a way of misusing the Unit field to allow for text as the device-tile-indicator/status.
During the HP2023 migration, there was a discrepancy between how that field was shown in the web app and homey app.
When communicating that with Emiel/athom, he proposed to just make textfield able to be picked as status indicators.
Since that now has been fully implemented, its a way beter solution, especially because updating the Unit field (which the old status field uses for its text), is respurce-heavy for homey.
Hi. I have a question about the modus from this Flow card. I am fairly new to Homey so sorry for this question. I was under the impression it would do the action just one time, but it keeps sending notifications (anti crack function dryer) in this flow…
Could an option be added to the modus like execute just one time (voer een keer uit)?
Thx. Doesn’t work as my dryer does an anti crack run after a while and the energy becomes higher than 100W again… Therefore I looked at the Device Capabilities card hoping that modus would just execute once…
That’s why the card checks whether the power remains less than 100W for 60 seconds (hence it is called a sustained value flowcard).
So, if the power becomes less than 100W for 10 secs and then becomes higher than 100W, the card won’t trigger.
You might want to lower the wattage threshold. I personally use a threshold of 2W for 5 seconds. That works for my dryer, but it might be different for yours.
Well, my card does the exact same as the (new) default cards (but i made mine first! 
).
But if your tubler keeps going below 100w and above, yeah, it will keep triggering the cards.
Its about fine turning which W means he is still busy. Like, what is the peak W before its actually finished?
Edit: if your tumbler is like mine, it will anti-crack-spin every (about) 5 minutes?
So using those flowcards like that is gonna be triggered every few minutes.
I would watch for the Peak W, have it watch for that value, like, if the tumbler is less then 500W for 5 minutes. Something like that might work much better.
No no!
Lets call it like it is: a copyright infringement!
(Obviously kidding, im happy its finally a default out of the box flowcard).
I am wondering though (never used that card before), does it keep working after a homey reboot or app restart?
I think I just don’t understand it and need to think about how things work, my thinking is fundamentally wrong I guess.. Because if I put it on 2W for 5 sec, when the dryer goes to lets say 100W again for the anti crack run, that it is above 2W so it will trigger again, or not?
I will try it though…
You should charge them a license fee! Like a monthly perpetual subscription 
.
No I think your rationale is good 
. You just need to solve the puzzle of which combination of power and duration works best in your situation/for your dryer.
I had exactly the same: my dryer goes into a similar cycle after completing its program as yours. I use the 2W threshold so that I know the dryer has stopped (and Homey calculates the session costs), because I manually switched it off or it has stopped by itself after the anti-crease cycle.
I did not find a suitable combination for a completion notification. So I am not sending one.
My Washing Machine has a similar Anti-Crease feature, that rotates the drum every few minutes to stop your washing getting creased and a mess. My solution was to use the Clockwork app to detect when the smart plug power went above 1000W for 5 minutes (i.e. the heating element was on during a cycle) and store a flag. Then when trying to detect the end of the cycle low power from the smart plug, only trigger the notification if the cycle flag has first been set. It works for my Washing Machine, Dishwasher, and Ice Maker like a charm. You just have to remember to Reset the flags timestamp after you send the notification, so it won’t trigger again until the cycle has run again.
This method would work for both the Device Capabilities card and the smart plug card…
I hope this helps 
Oh m8, i love the way you’re thinking
Indeed, something like this is the best solution, i have a similar calculation to determine if my tumbler is finished.
Thats why i asked for the peak W. That has to be reached, then you can activate a variable or something. Then, if the power is less then a few W for a few minutes, its (probably) finished: send a notification and reset the peak-has-been-reached variable.
Hello @Arie_J_Godschalk, did something change in one of the recent updates of the Device Capabilities app in how your original ™ ( ) sustained values flowcards work for boolean values?
I have a flow that triggers based on the two top most flowcard in the below screenshot (red rectangle). The cards check if a specific button (‘Stand 2’ and ‘Stand 3’) is on for 5 minutes. The button value used to be either true (on) or false (off). Both triggers have stopped working.
Instead, I am now using Homey’s own built-in flowcards for sustained values (the two lower ones), which now also work with boolean values. They work as expected.
Any idea why the original triggers are not working anymore?
Well, no, i have changed anything about those flowcards for about 2 years i guess.
But ill check this week somewhere, see if i mistakenly changed something that impacts that card.
