Help required on logic of a flow

[Mark Hands]

Hi everyone,

I had a successful flow setup that would wait until a bluetooth connection to my car was established, and it would read WhatsApp notifications for "ETA <post code>", using the Google Distance Matrix API, my GPS location and the post code to return time when driving. This was useful for my fiancée if she knew I was driving back from a customer meeting and wanted to see what time I was due home.

However, I noticed moments where the flow wouldn't fire, like it wasn't detecting my phone was connecting via Bluetooth. I've come to the conclusion (and I may be wrong) that Automate isn't seeing the Bluetooth connection depending on if my phone is connecting itself via BT or if the BT connection is setup by connecting to Android Auto via cable.

So I've tried to amend the start of the flow to almost have an or logic, to start listening for WhatsApp messages if Car Mode activates or if my car connects via Bluetooth. The issue I'm running into is not having the fork go back to the main flow and creating more and more fibers.

One idea I had was to create a new flow start point for the listener service, and when the fibers loop back to check for either Car Mode or Bluetooth disconnecting, the No dot goes to a flow stop block - but it appears I can't reference a second flow to stop it? Using "content://com.llamalab.automate.provicer/flows/31/statesments/2" as an example gives a java.lang error.

Any help would be appreciated.

 

[Mark Hands]

I think I've solved this using a fork after the detection of both the Bluetooth and Car Mode blocks, the parent fiber goes back to the check to detect when they disconnect, and the child goes to the part that checks for the incoming WhatsApp message. The parent fibers stop the child fiber after the disconnect.