Cancel/Confirm delayed Open Commands
Allow the system to cancel or have the user confirm open commands that got delayed when using an integrations. This happens when we issue a open command but the system didn’t respond so we manuallly open the garage and leave. Later the integration processes the command after we have already left. This could leave the garage open unintentionally.
Thanks Cameron. I will discuss this with our team. I don't know if this is even possible, or if it's a problem because I've never heard of it happening to anyone yet, and I haven't personally experienced this happening. I think once you do something like speak a command to Alexa or Google to open / close a door, it is up to those providers (Amazon, Google) to process those requests and then send the command to Tailwind. Tailwind itself has no idea when you would have spoken that command. It only knows when it receives an instruction from Amazon or Google to do something. However, it may be possible for us to offer something in our app that allows you to override any commands from integrations for the next X minutes for example.
I will check with the team on this.Comment actions
It was most likely a bug with IFTTT, the garage opened on 15 minutes after we left the house. I later discovered our key for IFTTT Webhooks changed by itself. But I agree unless the integration provider has a timestamp of when the command is issued then there wouldn't be a way for Tailwind to know.
Maybe you could implement a optional feature that if the authorized users' locations are far (> 1 mile) away then require a confirmation before opening.
I've actually been communicating with IFTTT as well as other integrations partners about this and I think we can resolve this fairly easily and quickly when it comes to our own triggers (door open/close).
That said, there isn't much we can do if someone makes their own custom applet. We are totally at the mercy of whatever trigger they choose. We have no idea what the user intent would be. All our system would know is that it received an action command from an authorized IFTTT account to open or close the door.
Ah - we can't control the web hook trigger delay. We didn't design that. We can only control how quickly the door opens when the command comes to open it. If the web hook trigger is delaying that would be a question for IFTTT.
What we CAN have some control over is how quickly the trigger fires when you door opens / closes, so for example, If door opens then ACTION. We are working with IFTTT to improve the trigger execution speed for this scenario.
Please sign in to leave a comment.