We’ve heard from a number of users that they are using IFTTT, but would prefer to
not need IFTTT. So I’d like to ask the community here:
What would it take from Bond so that IFTTT integration is not needed?
I’m assuming that Public Cloud API and SmartThings integration are top on the list. Other things?
Local Hubitat integration would eliminate the need for me, obviously so would cloud integration but if I’m asking might as well go for local since Hubitat does almost everything local as it is.
Terk, just curious. What are the advantages of Hubitat instead of SmartThings or even Home Assistant?
Hubitat performs locally with all zigbee/zwave devices and all apps even if the device driver or app is community created whereas SmartThings works locally with many but not all zigbee/z-wave devices that use built in device drivers only but doesn’t work locally with any community created apps or device drivers.
I don’t have experience with Home Assistant so I don’t know what the differences would be between those.
Did you see how Google Assistant devices are rolling out support of Local direct control? (See section titled 'Enable smart home devices to communicate locally’ here)
Might be something to consider, though I know there is already existing Bond + Google / Echo support.
It’s in the works 
Wink integration, specifically Wink Relay, as I’ve got one in each room that has a remote controlled fan.
I’m also curious what platforms us users here think Bond needs to officially support with “first party” integrations, and which we are fine with “third party” developers (such as ourselves on this forum or other people we know in our respective platforms) crafting from official Bond APIs (cloud and/or local). I think most people use IFTTT when there are neither “first party” nor “third party” methods to integrate, but if that assumption is incorrect I would like to hear why else a person would use IFTTT.
To me, if we inundate Bond with all the platforms we want them to support as a first party plugin, it sort of waters down the chance for the community to rise to the occasion provided to us with the official API, namely that we can develop our own “third party” integrations / drivers / plugins.
That being said, some platforms absolutely can benefit from first party (Bond maintained) support, and likely even some platforms that are closed except to official partner manufacturers.
For instance - I ask these next questions because I am ignorant currently. Not that I can’t search around and get some likely answers, but since you all have commented already…
Hubitat: sounds like there is a community of users who make and release integration methods (plugins, drivers, config files, whatever it is called in that platform), and that these “third party” created integrations work just fine either locally or cloud-based? Is there a reason to have Bond make and maintain a “first party” plugin?
SmartThings: sounds like there is a community of users who make and release integration methods, but that these “third party” created integrations refuse to work locally, and have to be cloud based? So an official Bond “first party” plugin would allow local control? Is that the case in both the ‘new’ and ‘classic’ SmartThings setups? I have read that there are differences but I haven’t dug into the details.
Home Assistant: is there is a community of users who make and release integration methods (plugins, drivers, config files, whatever it is called), and can these “third party” created integrations work just fine either locally or cloud-based?
Wink / Wink Relay: is there is a community of users who make and release integration methods (plugins, drivers, config files, whatever it is called), and can these “third party” created integrations work just fine either locally or cloud-based?
Yes this!!! I need wink relay support. The ifttt integration is horrid. I too have multiple fans controlled by relays.
There’s no community making 3rd party integrations for wink because it is closed platform mostly.
Yep, bad enough through IFTTT that it’s really not worth using. From button press to light on or off is measured in minutes. so only worthwhile as an emergency backup when I can’t find the remote. Native local support for Wink (relay) would allow the switch to function as intended.
So people are not able to use the OAuth API, or there just isn’t a strong community yet?
Would love to see a way to easily communicate with Universal Devices ISY controllers. Then I can control my fans from keypads, sensors and programs.
For the time being… https://forum.bondhome.io/t/local-api-control-integrating-with-isy994i/
Hope to get an ISY Node Server put together as soon as we have a way to subscribe to messages - something the Bond folks are currently considering.
Excellent! I’ll give it a try. IFTTT has not worked out for me.
@DCa71: Those old screenshots are for the direct TX call - now that State and Action calls are implemented in the Local API of Bond you can update the path / call used in your version of the ISY Network Resource to more fully take advantage of those instead.
thanks ! I have spent a bit of time today, first of all upgrading bond to the last version of firmware, then finding out there is a new app, installing that. I have started looking at the doc for the API.
Found out the IP address of the bond, now need to find how I can make it static with my router…
Denis
@DCa71 you can set Bond to a static IP using the WebGUI, available via a web browser:
Where Z… is your Bond ID. Latest firmware static IP actually works (all vintages I’d bond supported)
thanks a lot. I decided to use my Google fiber router to reserve a fixed address for the bond.
One suggestion- the bond actually shows as “Espressif” on my router. I realize this is the brand of the Wifi chipset or module you guys probably use… Would suggest changing that descriptor.
You can also just use mdns for discovery. Just reinitiare the discovery process if the device is unreachable.
