Revisiting this topic as it's been a while and a search doesn't turn up any recent activity.
I've had the @dbadge driver for Tailwind installed and working for a couple of years. I see that there is also a driver by @Gelix (Chaue Shen?) on HPM. Are there features/advantages for one over the other?
What I'd like to see, if possible, is a way to access the presence feature of the Tailwind app. It works very reliably in knowing a phone/vehicle is arriving to open a certain door. Much more reliably for arrival/departure than the Hubitat app has worked for HSM.
I've set up a Rule that runs when a door is opened to change mode/HSM, but of that's not ideal and not as secure. The Tailwind app can be configured to only open a certain garage door automatically based on both app presence and vehicle pairing (BT). It would be great to tap into that.
Or even if there were a way for Hubitat to know if the door was opened by the Tailwind controller vs a local button or remote. The Tailwind app can send push notifications based on a number of events including "within" or "outside" the Tailwind system.
For garage door control, you'd be better off installing something up-to-date that is directly supported by Hubitat. Like the Konnected blaQ or the RatGDO.
For geofencing, there are also better options - if you're an iOS user, the Apple Home app, Locative, and Geofency are good options. OwnTracks is a good option for Android users.
No offense, but that's not what I was asking. Maybe you can better explain why I should spend another chunk of money on garage controllers (2 doors) and install more software? Tailwind is still getting both app and firmware updates btw. The system works very well with Hubitat and many other integrations. And I don't know what you mean by "directly supported" as I don't see Konnected listed as a directly compatible device nor is there an official Hubitat app.
If there is a super compelling reason to switch I would consider it, but nothing I've seen on their website leads me to believe it can do more than what I have. I'll check out Owntracks though. I was hoping to not have to install yet another tracking app though.
As you point out, there's no active development on a Hubitat app for Tailwind. In contrast, there are several locally controlled products that are actively supported under Hubitat, including RatGDO and the Konnected blaQ.
If you want to have automations happen reliably based on phone location you are going to need some kind of cloud connection. The way that Tailwind handles location is really smart, no location information leaves your phone and it's not tracking all the time. Plus you can pair it to a vehicle (via BT or their sensor) so it only tracks when the phone is near the vehicle. It also means that both are required to open the door automatically on approach. In other words, someone else driving your car or getting a hold of your phone alone won't be able to open the door. They'd need both. There are also other features worth having. Bottom line, it works for me. If not for you no one is suggesting you should switch.
And FYI, it works without the cloud when you are on your local network. If your internet is down you can still control it with HE or your phone. And finally, each controller can operate up to 3 doors with add-on sensors.
For this to work, things like this usually are integrated by either an API that the manufacturer of the device publishes, or someone has to try and reverse engineer a phone app or sniff the network or similar.
I am too lazy to look and see if Tailwind has an API, but if it does, you may be able to fairly easily (relatively speaking) add these items to an existing driver/app. If this device doesn't have published/established commands, the barrier is infinitely higher to develop anything.
I guess as a first step, maybe you could research the availability of an API, or other sources of code where you might discover if there is even a possibility to add these desired devices into Hubitat.
The other alternative I forgot is to contact Tailwind, and ask if they would be willing to reach out to Hubitat staff to create an official integration.
I am fairly certain that due to the sheer number of companies that produce smart devices, staff do not have the time to chase down every potential device manufacturer. I also think Hubitat flies under the radar at times, so device manufacturers might not know that Hubitat even exists, or might have only heard of the name in passing.
If you facilitate Tailwind reaching out, maybe that will trigger the creation of an integration?
Try to find either official API docs, or some other integration for the same device that has the features you want. Then from there it should not be that difficult to add it to one of these drivers.
