Google Is Turning Off the Works-with-Nest API

Re:Google Is Turning Off the Works-with-Nest API by asdfasgasdgasdg on Tuesday May 07, 2019 @10:17PM (#19855355)

Hrm. How so? HomeKit does not allow third party devs to write apps to control HomeKit devices, AFAICT. So they never added the capability that Google is removing. People can still develop devices that are triggered by Nest and Google Home. They just can no longer write apps that themselves trigger or modify Nest devices.

Or are you saying it's prescient because Apple saw that such capabilities were not economically viable in the long run, and so it was prescient of them to never develop the functionality in the first place?

[ Parent | on HN ]

Re:Google Is Turning Off the Works-with-Nest API by Despegar on Tuesday May 07, 2019 @10:39PM (#19855466)

HomeKit doesn't require an internet connection for smart home devices to work, it doesn't require you to use the smart home maker's garbage apps or sign up for accounts with them, it gives away for free features that smart home makers try to put behind subscription paywalls, and most importantly it was designed to be secure.

[ Parent | on HN ]

Re:Google Is Turning Off the Works-with-Nest API by Gaelan on Wednesday May 08, 2019 @12:26AM (#19855863)

I haven’t tested this, but I believe you could use Homebridge to create a virtual “button” that got “pushed” when you hit some API endpoint, then configure HomeKit to change something when the button gets pressed.

[ Parent | on HN ]

Re:Google Is Turning Off the Works-with-Nest API by iknowordidthat on Wednesday May 08, 2019 @01:54AM (#19856208)

HomeBridge can control HomeKit accessories just fine.

[ Parent | on HN ]

Re:Google Is Turning Off the Works-with-Nest API by icebraining on Wednesday May 08, 2019 @07:49AM (#19857916)

Can you show an example of HomeBridge controlling an HomeKit accessory? The description of the project says the opposite: it allows the control of non-HomeKit accessories from HomeKit.

[ Parent | on HN ]