Page 1 of 1

General broadcast (user present)

Posted: 12 Aug 2019 13:01
by Rafi4
Hi all
When I am using general broadcast user present trigger speech output action working twice .
Example as below

Speech output action= today is Monday (speech output text)
But speech output is "today is Monday today is Monday"
Is this a bug? How can I solve this?

From record4

Re: General broadcast (user present)

Posted: 12 Aug 2019 15:37
by Desmanto
Check your flow log, maybe it really execute twice. You can try to change the FEP to skip, or you can try a new flow with Trigger "user present", instead of General broadcast.

Re: General broadcast (user present)

Posted: 12 Aug 2019 17:24
by Rafi4
Hi Desmanto
Why the broadcast (user present) trigger running twice?
I have checked the log as you said the flow running twice.
Any solution without fep?

From record4

Re: General broadcast (user present)

Posted: 12 Aug 2019 17:52
by Desmanto
I am not sure with yours. At mine, both Trigger User present and General Broadcast - User Present only execute once, default parallel FEP. Maybe you put the trigger twice, you have other duplicate flow or maybe it is the bug with your phone that send the event twice to Automagic.

You can try to disable any existing General broadcast flow, try to lock-unlock and make sure no flow triggered. Then create another new flow, with only that trigger, add debug dialog. Try lock-unlock again and see if the debug dialog executed twice.

Re: General broadcast (user present)

Posted: 13 Aug 2019 01:50
by Rafi4
Hi Desmanto
I have checked general broadcast trigger with screen on screen off actions.I have checked everything as you said. every time it was executing only once. But when I am using user present it was executing twice. If in my device anything need to execute general broadcast (user present) only once. I mean category list
Data scheme list etc

From record4

Re: General broadcast (user present)

Posted: 17 Aug 2019 16:19
by Desmanto
So maybe the user present trigger is buggy at your device. I don't know if this is device-specific bug or Automagic. Maybe you should send the debug log to Martin, to analyze it.

In mean time, you can simply use FEP skip to block the second trigger. Or you can protect it with a simple condition execution count, timed 1s. Only use the false part to execute your main flow. Leave the true part blank.