Hubitat Integration
Due to various problems with the Samsung SmartThings platform, many users have migrated onto the new more configurable Hubitat platform. I'd like better device integration there, with both status indications/triggers, and controls.
-
The local APIs are working fine in our internal testing. From a project perspective we tied them to our Apple HomeKit firmware release, so our HomeKit beta testers already have local control firmware - we just haven't provided the documentation yet. Working on that right now.
But HomeKit beta firmware is already deployed to beta testers, and once we give them the local control API documentation they will have all the tools needed to write any drivers they want. I am committed to making this happen, but I'm not sure how much work / risk is involved if we now separate the 2 developments so we can release the local control before HomeKit. Unfortunately the HomeKit process is long, tedious, and filled with roadblocks unlike anything I've ever seen. In fact we regularly have difficulty simply logging into their development portal - using a MacBook Pro running Safari to log into an Apple website using an Apple ID. So Apple from one end to the other - can't log in 50% of the time. That's just the tip of the iceberg.
Long story short - your best option to get local control quickly is to email me and request the HomeKit beta firmware. That will allow us to push firmware to your controller that is enabled with local control and we will get you the documentation soon. -
I’m always amazed at how fast you reply Scott, haha. That’s good to hear. I’ll probably email you for that beta once I get my hubitat all setup. I hear ya..dealing with HomeKit has been frustrating for a lot of developers. It’s almost like Apple doesn’t want people to develop HK integration :/
-
Scott Riesebosch Is there any update/movement on the API and potential for integration with Hubitat?
-
Christopher,
We have local APIs you can use but we don't have an official integration with Hubitat yet.
If anyone wants the local APIs just email support@gotailwind.com and request them. They're in beta right now but will be fully released soon.
Scott
-
I just found two:
https://github.com/kaimyn/Hubitat and https://github.com/Gelix/HubitatTailwind
It seems like kaimyn's is a bit more mature, but I haven't tried either one yet.
This thread has some info about them:
https://community.hubitat.com/t/code-review-tailwind-garage-door/79305?u=datavortexWhere was the third? Has anyone tried them yet?
-
I'm the author of https://github.com/Gelix/HubitatTailwind. Chaue.shen (Kaimyn) and I collaborated on creating our two different versions. As far as I know, both versions function well but have some minor differences (polling, etc.). I've been using my version on my 5 controllers 12 door mess without issue for the past month.
-
I tried installing yours from HPM but the package manifest is missing the main driver and only has the child driver.
-
I have Derek's installed on my garage tailwind and Kaimyn's version on the barn tailwind. Seems to be only minor differences between the two such as Kaimyn's reports intermediate statuses (opening...)
This is probably more for Scott Riesebosch but are we going to see any more detail in the history log in the tailwind app, such as "Opened by API" rather than "Somebody opened..."? Having name/key pairs could be nice too, where you have a key with the name Hubitat so it can say "Hubitat opened...."
-
Hi Guys,
Just tell me what you'd like to see in software developer speak. I'm not a software developer so I won't understand what you're saying most likely, but I will definitely pass the details along to our team.
From what I can see it looks like when you are using the local APIs you don't get any details on what opened the door, so if there was some kind of keys that you could assign to various things such as users or automations, and names to go with those keys, then you could have something like "Hubitat XYZ automation opened garage door 2" because the key for that automation was passed along with the door open command.
Is that accurate? -
Scott Riesebosch Exactly. At the simplest level, the Tailwind could report that it was the API that did the action and not somebody outside the Tailwind system and honestly with the majority of the users only ever having one API connector this would most likely be fine and not really require much development. The name/key pair would be the more complex solution, where 11122333 could be associated with Hubitat and then if 11122333 was used then it would know Hubitat was the originator of the action.
-
Michael Teator Oops, found the typo in my manifest batch file (json--version=1.0.1 missing a space). Thank you for that!
-
Derek Badge Thanks, can confirm your HPM install works now :)
No issues with either driver so far, other than my own fault of not adding a DHCP reservation for the Tailwinds so they jumped around IP addresses on me.
-
New documentation for local control API here.
NOTE: We are updating to JSON to make the API much more future friendly. This document will show you how to add the security token to your implementation and will work with firmware V9.95, but please note that when we implement JSON in future updates it will render this version obsolete and we will migrate to the JSON version.https://drive.google.com/drive/folders/1Y4CAscgn1FCmTAKg7YcLYHRRQPuNC6G0?usp=sharing
Please sign in to leave a comment.
Comments
52 comments