Live data from Hacker News

Google Is Turning Off the Works-with-Nest API

nest.com

241–250 of 600 posts

Re: Google Is Turning Off the Works-with-Nest API

#241
post #30

If a developer has gone to the effort to integrate their solution with Nest, I'd be very surprised if they don't get their solution integrated with Google Assistant, and Apple HomeKit too while they're at it. So I assume that when end-users switch over their Nest devices to the Google Assistant platform, their existing Nest integrations will be available on the Google Assistant platform too. Doesn't appear to be as d…

I believe the kind of Google Assistant integration you would need to replicate this kind of access is impossible in publicly available APIs currently. Google has much more integration capabilities, but they seem to be this far "invite only", you can't request it.

So... The functionality exists and is currently in testing, it's only just become stable enough that we're hearing about it, and they're notifying developers targeting the current service as far ahead of time as possible? I mean, it won't do anything for stuff that's too crappy to take software updates, but that's an entirely different matter.

Edit: Finally went and read the announcement. They're really not giving people much time, are they? Nevermind, three months is pretty bad.

Re: Google Is Turning Off the Works-with-Nest API

#242
post #7

What's the point of creating an ecosystem if you won't support it? Typical Google. I understand shutting down or refocusing services that don't work. But decisions like this or to shut down Inbox make no sense to me. It feels like complete disregard of the user base.

Just an aside I was never able to successfully register my gmail account to work with Inbox. Even with the invite there was something wrong I could never get past. Google does big things, but "making stuff work" just isn't one of them afaict.

Re: Google Is Turning Off the Works-with-Nest API

#244

Earlier quoted context omitted.

I've been considering pasting this: https://killedbygoogle.com/ every time the argument comes up. Maybe Google proponents will make one for other companies notorious for killing services, but at least for now, the Google Graveyard grows.

I don't quite get what people expect... do they think that once google creates something, they are obligated to continue it indefinitely? That seems like an unreasonable expectation.

I think that many people naturally expect Google to work like a lot of other companies, which are focused on satisfying individual customers.

Google, though, is unusual that most of their users are not Google customers. They are the product. So Google's relationship to most individuals is statistical, not personal. If they care about me as an individual, I have never seen the slightest sign of it.

I also think that a lot of things at Google get started and killed not on the business merits, but due to shifting internal politics. Most of my Google friends have left, so I don't have recent examples, but from what I hear Google Plus is a fine example of something launched because a powerful executive got excited. As the political winds shifted, though, it got neglected, and then eventually killed.

Another interesting example for me is Google Reader. I liked the product, but was never clear to me why they built it. They ignored it for a long time and then shot it in the head. Giving it away crushed the market for commercial RSS readers. Once they stopped, that market came back, proving that Google could have had a successful commercial product if they had bothered to run it like a real business.

So no, I don't think we expect them to continue all things indefinitely. But I would love to see a more clear logic for what they will continue to support, because from my perspective it's erratic. I would be very unlikely to build a company that depended on Google; despite having used them for 20 years, I still don't think I can predict their business strategy. In contrast, I've been using Amazon for a similar period, and I have a pretty good idea of what they'll do. I'm not worried they'll EOL the AWS services I use, for example.

Re: Google Is Turning Off the Works-with-Nest API

#245

Earlier quoted context omitted.

They care for their user base. Their user base just isn't us people using their services.

At some point there has to be a value in marketing for keeping people happy, right? At least mothball upgrades and leave this running "slowly" or _anything_ other than just shut everything down for reasons... My daughter wrote a letter to a clothing manufacturer about how the embroidered lettering was falling apart on a brand name shirt. They sent her a new one, for free. That is good marketing. What Google is doing?…

> What Google is doing?

Google Doodles.

edit: by that I mean using many tools to project an image of clean smart friendliness.

Re: Google Is Turning Off the Works-with-Nest API

#246
post #127

I see Google API/ecosystem fans often defending or dismissing Google’s pattern of behavior here, using arguments like this: “Well, sure, they shut down that API I don’t use — big deal; all things come to an end eventually! But, they’d NEVER do that to this API I rely on — that would be so horrible, Google just would not do it!” I hope we all can acknowledge that this argument is on perpetually eroding ground, at the…

Maybe I spend too much time on HN, but I’ve literally never seen someone take Google’s side in these situations.

There are some in this very comment page who are taking Google's side. They are getting severely downvoted, but still.

Re: Google Is Turning Off the Works-with-Nest API

#247
post #22

> I’m a Works with Nest developer. Will I be able to access and control Nest devices moving forward? > No. The Actions on Google Smart Home platform does not provide open API access to Nest devices, so it cannot be used to access and control Nest devices. Instead, managing and controlling Google Home, Nest, and thousands of third-party smart home devices is done through the Google Home app and the Google Assistant. W…

“I’m a Works with Nest developer.” Not anymore you’re not.

Re: Google Is Turning Off the Works-with-Nest API

#248

Earlier quoted context omitted.

Once again HomeKit's design proves to be prescient. https://www.theverge.com/2017/8/3/16083996/internet-of-shit-...

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 v…

[deleted]

Re: Google Is Turning Off the Works-with-Nest API

#249
post #200

Literally bought a nest thermostat yesterday. Glad it's still in the box. Wondering what the best alternative is now.

I like my ecobee. The middle priced one seems best. The cheap one doesn't support per room sensors, and the expensive one adds a mic for alexa.

The cheap one supports add-on sensors, it just doesn't include any.

Re: Google Is Turning Off the Works-with-Nest API

#250
post #11

headline should be "that $300 doorbell is now a paperweight". in the future it will be "that $8000 trunk car driving computer is now a paperweight".

Pretty much straight up FUD. This is not bricking Nest devices.

Ok, more like “That remotely controlled car with integrated taxi service you bought?”

Well, now it’s “Just a car”

Post reply on HN