Hello,
I've a simple flow:
Trigger: Battery level "full" (new trigger in 0.19)
Condition: Power supply plugged
Action: Voice output something (...remove the cable...)
Action: Pause 10m.
With the new version the pause at the end (10m = 10 minutes) does not work anymore and the trigger will be re-activated after like 10 seconds.
This may be combined with the new trigger ignoring the pause action.
Can anyone reproduce this?
Re-Run flow conditions, periodic timer, enable/disable flows
Moderator: Martin
Re-Run flow conditions, periodic timer, enable/disable flows
Last edited by Iveco on 11 Oct 2013 20:35, edited 1 time in total.
Re: pause bugged combined with trigger battery full and voic
Hi,
Battery "full" will trigger the flow every few seconds depending on phone type (for example when the voltage or percentage changes). This setting is mostly useful if you want to update a widget with battery related information.
If you want to execute the flow only once you have to use the "becomes full".
The pause/sleep action at the end of a flow will not prevent the flow from executing again. Do you want to execute the flow every 10 minutes?
Regards,
Martin
Battery "full" will trigger the flow every few seconds depending on phone type (for example when the voltage or percentage changes). This setting is mostly useful if you want to update a widget with battery related information.
If you want to execute the flow only once you have to use the "becomes full".
The pause/sleep action at the end of a flow will not prevent the flow from executing again. Do you want to execute the flow every 10 minutes?
Regards,
Martin
Re: pause bugged combined with trigger battery full and voic
Ah I see. I thought the pause at the end would prevent the flow from running again.
Some triggers are executed really often, what is the best practice to prevent such a flow from executing too often within a particular timespan?
I do not like the way of having 3 flows, like first flow which sets a variable to 1, second flow which sets a variable to 2 and a third flow which has a condition depending on this variable. This is a bit too much.
Is there an easy way to execute it every 10 minutes without using variables and more flows? A simple flow setting option in the menu like "execute only every xxx time" would be great
. Or an "Re-Run-Condition" (new type of element?).
Some triggers are executed really often, what is the best practice to prevent such a flow from executing too often within a particular timespan?
I do not like the way of having 3 flows, like first flow which sets a variable to 1, second flow which sets a variable to 2 and a third flow which has a condition depending on this variable. This is a bit too much.
Is there an easy way to execute it every 10 minutes without using variables and more flows? A simple flow setting option in the menu like "execute only every xxx time" would be great

Re: pause bugged combined with trigger battery full and voic
There are different options. Checking Ignore temperature changes and Ignore voltage changes in the trigger helps on many devices.
You could also use a trigger Periodic Timer: every 10m and use a condition Battery Level to check whether the battery is full.
Following flow pattern can be used in some other situations:
-trigger XYZ
-action Set Flow State: Disable {flow_name}
-some actions
-action Sleep: 10m (allow device sleep)
-action Set Flow State: Enable {flow_name}
You could also use a trigger Periodic Timer: every 10m and use a condition Battery Level to check whether the battery is full.
Following flow pattern can be used in some other situations:
-trigger XYZ
-action Set Flow State: Disable {flow_name}
-some actions
-action Sleep: 10m (allow device sleep)
-action Set Flow State: Enable {flow_name}
Re: pause bugged combined with trigger battery full and voic
Excellent. Didn't think of this action. Thank you very much!!!
P.S. I've changed the title of the thread so it may help other users too.
P.S. I've changed the title of the thread so it may help other users too.