*Skip to here if you're not interested how it works*. ![]() So as you can see, there's quite a lot of back and forth going on, but it has proved to be very useful and reliable (despite many issues!) so far. To disable, Twilio sends another text to the gates resetting the primary calling number to our landline. Et voila, automatic opening gates which can be enabled/disabled at the push of a button, or set on timers, or activated via an Alexa command. Once again, it waits for a response back from the gates and then announces that the gates opened when it receives a confirmation. Once confirmed it tells Twilio to send a further SMS to the gates telling them to open. It checks the number and only continues if it's from the gate. ![]() It's this event that then triggers the rest of the automation. Now when someone presses the intercom buzzer it rings my Twilio number, which shows up as an event in Home Assistant. I use this SMS confirmation to announce on my Echo devices that it worked. The gates reply back to Twilio with a confirmation. The SMS tells the gates to change its primary calling number to the Twilio number. When I want it to engage, Home Assistant triggers a Twilio SMS to the gates. The reason I went for Twilio is because it integrates well with my home automation software (Home Assistant) with the main goal of being able to have the gates open automatically when someone calls, at certain times, useful for when I have deliveries but I'm out. It takes a regular phone SIM card to do this, I'm on Vodafone Pay-as-you-go £10 a month for unlimited calls/SMS to UK landlines/mobiles. The gates respond to SMS but also has a cellular intercom system. ![]() All it does is allow me to automatically send commands to some electric gates at the bottom of my drive. I need this number for a very specific purpose. EDIT - TWILIO ARE NOT CHARGING ME INTERNATIONAL PRICES.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |