An API for Tailwind?
As someone who really loves how APIs make everything programmable, naturally I'm very interested in being able to program my garage door. I can imagine two levels--one that's just event notification, a webhook that calls out to a URL that I can configure, and two, the ability to query the door state and trigger open/close.
I realize that there is a lot to consider when opening up an API, but this also seems like it has potential to be a differentiating feature. It doesn't hurt that the DIY-inclined are often a pretty vocal bunch that can really help with word of mouth.
-
Paul,
I'd like to help with this too. I've been using Tailwind for a few years, and have been an HA user for about a year and a half.
Up to this point, I've just been using my Tailwind via SmartThings via HA - and that works just fine - but if we have the ability to do a native HA integration, that's even better.
Thanks,
Ryan
-
That's great Paul! Just remember, we're going to add a token to it for security so there will be a small tweak required for that. I've been running with the local control APIs for months now and I actually have a beta version of the iOS app that supports local control as well. I love the fact that when I open the Tailwind app my garage door status is loaded instantly and if I tap on the app it executes the command in literally a few milliseconds. For all intents and purposes it is instantaneous. I know over the internet the control is still pretty fast but there's just something about "oh - I need to open the door", and being able to do that so incredibly fast due to the LAN connection between the phone app and the device is really the way to go.
I can't wait to release it for everybody!!!
-
Hi,
I have not yet purchased a Tailwind but I'm interested.
I use OpenHab and I'm a java software engineer.
Scott Riesebosch can you send me the docs?
-
Just a quick update on the Home Assistant integration: I've got the basics working (discovery, setup, state reporting and control).
Once I've tidied up some rough edges and made some improvements to the manual setup process, I'll test using it as a custom component in my main Home Assistant instance. From what I've seen during development, I don't think that automatic discovery will work when it's installed as a custom component (as it seems to need registering in some core code), but the enhancements to the manual setup should make it a pretty smooth process anyway. I'll then release the custom component for review/testing/feedback.
I think it's best to hold off on submitting it to HA until the security token process is finalised and added to the integration - and the firmware update is released (or we at least have a better idea when it will be released) - so that it'll be usable by all Tailwind + Home Assistant users at release.
-
I've just released the initial version of the Home Assistant integration. It's set up for installation via HACS (Home Assistant Community Store), as HACS enables the automatic discovery and UI-based configuration which (as far as I'm aware) is otherwise not available for custom integrations. See https://github.com/pauln/tailwind-home-assistant for installation instructions; if you find any issues, the issue tracker there is the best way to let me know (but replying here should hopefully also get my attention) - and for those who are programmers, please feel free to submit pull requests if you have any fixes or improvements.
Note that although there's currently no icon (or an "icon not available" placeholder), I'll be submitting the relevant imagery (which Scott has sent me) shortly - so you may find that the icon magically appears in the near future.
Once the firmware is finalised and released, the plan is to add support for the security token and submit the integration for inclusion in Home Assistant, so that the vast majority of Tailwind users won't have to worry about HACS - once they update Home Assistant to a version which includes the integration, their Tailwind device(s) will automatically be discovered and able to be set up.
-
Just tested out Paul Nicholls HACS plugin and it works great
-
Please email support@gotailwind.com and let the team know what email address you used to register your Tailwind account, and request the beta. Let them know what instructions you want (HomeKit / local control API / both).
-
I emailed support for the beta yesterday and I have not heard back.
Is the beta still available for request?
-
I have the beta Homekit setup and now I'm looking to start a OpenHAB plugin for total local control.
I see there are 2 http endpoints,
GET /status
POST /cmd <number>
I find polling to get status is less desirable than a message broker (MQTT) pub/sub
Has Tailwind considered implementing a MQTT API?
The Tailwind Controller is configured to connect with a MQTT broker
On state change and on a periodic basis, The Tailwind publishes status messages to the MQTT broker.
The Tailwind controller can subscribe to commands and queries from the MQTT broker
The Tailwind controller does not need to implement the MQTT broker and I very sure there should be an quality open source MQTT client available for the Tailwind controller operating system.
Then a new OpenHAB plugin or HA integration becomes unnecessary.
The MQTT protocol can be setup to be secure and the MQTT client would handle transport encryption and authentication, freeing Tailwind from a very complicated and easily borked task.
I'm pretty sure the Homie MQTT specification can provide a very good specification for a garage door/gate controller
-
Homie specification
https://homieiot.github.io/ -
Just a followup
Have you and your team been able to evaluate a MQTT API?
-
Some thoughts on 3 sensor inputs
Fully open sensor input
Motion sensor input
Obstruction sensor input
The motion sensor can tell the controller whether the door is moving
Having fully open, fully closed, and motion sensors, you can infer if the door is partially open and not moving
An obstruction sensor can trigger obstruction events as well as sense whether there is an obstruction
Can these be added without a hardware revision?
-
Hi Christopher,
It would definitely require some additional hardware because the sensor we have now is a reed sensor that will just detect the presence / absence of a magnet, and the sensor is stationary.
Sorry but we have been extremely focused on finishing HomeKit certification as well as trying everything under the sun to attempt to compensate for the CoreLocation iOS 15 bugs because they are hurting our main differentiating feature - the auto-open / close features as you come and go. While it doesn't impact all iPhone users it does impact enough of them to cause headaches, and our only recourse is to communicate what we know, and to test a lot to try and find clues about how the bugs behave and what we might be able to do to compensate for them.
-
An update for those of you who may still be following this thread, now that firmware V9.95 has been released (congrats, Scott and team!)
If you're using my custom HA integration (either via HACS or manually installed as a custom component), I've just released an update (v0.2.0) which works with the V9.95 iQ3 firmware.
After updating the component (and restarting HA), the integration will show as "Retrying setup: 'api_token'" as your configuration won't include the new Local Control Key; unfortunately, you'll have to remove the integration and re-add it (just click the 3 dots on the integration card, choose "Delete" and confirm; then click "Add integration" and re-add your Tailwind - specifying the Local Control Key, which you can find by following the instructions at the bottom of the README: https://github.com/pauln/tailwind-home-assistant
When re-added with the Local Control Key, it should keep its original unique ID, so your doors should hopefully still appear on any dashboards you've added them to, and automations etc should still work.
-
Scott Riesebosch
I'm following up on the MQTT API research question? How goes you local API development? -
And just to make your life even MORE interesting
Have you been following Matter? -
Hi Christopher. The API is available to anyone that wants it and some very talented people have written integrations for both Home Assistant and Hubitat. Just email support@gotailwind.com to receive all the details.
I have been following Matter and wanted to certify with them until I discovered the cost. It’s way too high for us.
-
Scott Riesebosch
It's open source and royalty free.$7k per year to join CSA and $3k to certify a product.
And that is only if you want to be able to put the logo on the box.
I'm sure you spent way more than that on your Homekit odyssey. I'm sure tailwind would greatly expand their market opportunity with Matter without having to write multiple integrations for all of the different IOT ecosystems.The only thing hardware thing, you may need to add a Bluetooth radio, only used for provisioning. For existing customers, Maybe offer a dongle like the Liftmaster security dongle?
Please sign in to leave a comment.
Comments
57 comments