Ok, so I had this weird idea, when I am on my motorcycle, when I get close to home I want my west garage door to open, but when I am in my car I want my east garage door to open.
How to determine what one I am driving would be kinda simple. Bluetooth. if I am connected to my car, then East, connected to my helmet Bluetooth, West.
IFTTT kinda of has this functionality, but its only if you connect to anything or nothing.. so that wont work. my next Idea was Tasker, as I know that can determine what BT im connected to, but tasker does not connect to HE.
Anything else? would be cool if I could get Tasker to connect to IFTTT for example, but that does not seem to be an option.
I concur w/ @bptworld. I have lots of Tasker Profiles that send HTTP Requests to Maker API addresses to control individual devices or to Cloud/Local endpoints to trigger rules. It will be MUCH faster than relying on IFTTT.
In maker API, there is a local option for each HTTP Request and a cloud one. In Tasker, do an If-then based on connected to your home Wifi. If not connected, send cloud request; if connected, send local. Same goes for the endpoints to trigger rules in RM.
I HIGHLY recommend Tasker for this. I have an old Android that all it does is take Notifications from Wyze, Eufy Doorbell, and Amcrest Cameras (which do not integrate with HE) and send HTTP Requests to HE to control virtual motion sensors or trigger rules. Since it is always at home, I use local for this case. And it's fast & reliable so far.
You can also use Tasker as another presence sensor while your at it.
I read up on Maker API and that did work also, just have Tasker send a POST to that URL.. not a bad idea. obvioulsy there is a bit more open security attached to doing this as I have to expose the switch, but the fact that I can select only this switch, the worse case is that someone forces me to open the other garage when I get close.. lol
I did get it to work. I have Tasker sending a MakerAPI and flipping a switch. IF BT from my helmet is connected, then the switch is on, if it's not on my helmet it goes off (or turns off if my car is attached just in case) .
then I have a geo rule, when I am close, it reads the switch and opens the appropriate garage
The OAuth2 security is actually very good. The http post to the Maker API will be via https, so everything is encrypted when using a Hubutat cloud endpoint, including the URL. Nothing is transmitted or received in clear text. The is exactly the same way your phone communicates with most all cloud providers that do not require you to log in every time your device connects.
Keeping IFTTT out of the equation will definitely speed things up and make it more reliable.