Strange discussion, a flow is not like playing a record or so, a flow is started by a trigger and is then executed (within microseconds), if you don’t want it to run, disable it, and if you want to run it again, enable it. Disable and Enable can be done via a flow or manual. Every one with some experience in programming via flows can see, this the best way to handle.
2 Likes
Well that’s an easy one 
press and hold for menu with delete and disable/enable options
But that is 4 clicks! He finds that too much. So was just wondering.
No, there are only 3 cklicks! 
1 Like
Without delays in the Aktion cards, you are right.
But with delays the flow is running = max. delay.
4 clicks! 
- enter flowcard
- kog wheel
- enable/disable
4 save/check (waiting)
Save is not necessary!
Tell that to my boss
Request or not. Sense or nonsense.
In the meantime.
Create a flow for you batterie maintenance:
Wehen Flow
Is startet
Then disable all affected flows
And after x minutes enable all flows again.
In this case you have only one Klick instead of many clicks for each of your flows!
And that way i don’t have a few extra buttons on a tiny card which i can easaly click by accident.
And open device tiles normal with a short click so I don’t have to wait for the long press, win win
But short click is for on/off. U wanna move that also to the settings page?
The none on/off tiles like sensors🙂
Maybe you can use a button like I do for some scenes and vacations. 
Then it would be easier when a group of flows can be disabled for a while, when i need to disable a lot of flows it’s still a lot of work.
1 Like
