I've got fixes for that, mainly that it can't open from the Home when we aren't home, and it announces when the garage door opens by literally "announcing" it through the home's speaker, as well as a notification on my phone. There's also some trickery that you can do with IFTTT's activation time variable and checking how long it's been since it was "asked" to do something vs when it got to my system.

It's not for everyone, but i'm really enjoying the setup. Although if i could I would remove IFTTT from the whole equation. Everything else is running off of a server in my house, so IFTTT is the only part that's really not fully in my control.

But as it's nothing but a "layer" on top of the rest as an "ease of activation" kind of thing, i'm not that worried.

My (now sidelined/back burnered) startup's main product was kind of like an advanced IFTTT that runs on your own hardware. The major difficulty was scaling up development and production without capital, and getting a basically Turing-complete system to be easy to use.

While I would love a "self hosted" IFTTT, the biggest issue to me would be getting the integrations.

IFTTT is the ONLY thing on Google home right now that lets you create fully custom voice actions. It's got a lot of things like this.

There are a few similar services, but at the end of the day, if it's within my capability to talk directly to a service, I'm going to just write my own code to talk to it (or my FOSS HA system will more likely support it very quickly).

IFTTT's power to me is completely in its ability to integrate with otherwise "locked down" services.