Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Is Turning Off the Works-with-Nest API

nest.com

Post reply on HN
Print view View original

301–310 of 600 posts

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

#301

Post by doodliego »

wpietri wrote: post #244
cortesoft wrote: post #136

Earlier quoted context omitted.

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…

Why should anyone let a Google self-driving car on the road? They will just end support for it whenever "internal politics shift."

Let's ban Google from working on life-saving medical devices, because they will just get bored and stop supporting the software.

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

#302

Post by dehrmann »

ocdtrekkie wrote: post #194
palebluedot wrote: post #33

This seems to include all of us using them in open-source "hobbyist" environments, like Home Assistant and Node-Red. I'm quite frustrated by this; I'll never buy another Nest product again, and I now regret my purchase of the Nest Thermostat. All the rest of my IoT stuff is either open-source hardware/software, or at the least local-only with known protocol interfaces. This was the one exception I made for IoT "cloud…

The month Google originally bought Nest, I sold my thermostat to someone else and picked up an Insteon thermostat instead. My Insteon thermostat's been a reliable partner since, and doesn't send my data to anyone. I actually turned a profit on it, since I got rebate credit from my electric company originally for buying it.

My gripe is the design is nowhere near as good. It's like going from an iPhone to a feature phone.

I wish there were an open-source Nest firmware, or at least an open-source backend. Google doesn't need to know when I'm home.

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

#303

Post by Nullabillity »

hedora wrote: post #183
mirimir wrote: post #162

Earlier quoted context omitted.

Use a VPN in a private VM.

Or, duck duck go with the g! prefix, if you really must use google with bubbling turned off (instead of a reasonable alternative).

DDG isn't magic. It doesn't bubble you on its own results (or at least it claims not to), but it can't change how external providers behave.

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

#304

Post by fenwick67 »

inlined wrote: post #153

Does any attorney want to speculate whether Google could be forced to accept returns on Nest devices now that they’re materially worse through intentional actions?

Not a lawyer but there was a successful* class action against Sony for removing Linux support.

Customers could get $55 if they could prove* they used it, a low payout with a high burden of proof

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

#305

Post by telltruth »

gergles wrote: 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…

At Google, no one wants to work on existing things. You must create new product/feature to get promoted. Then you move on and thing gets shutdown. This is direct consequences of their internal incentive structure.

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

#306

Post by lrem »

wtvanhest wrote: post #289
DivisionSol wrote: post #57

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 didn't realize they killed chromecast audio. Pretty frustrating. I may not have committed so much to their echosystem in Dec.

They stopped selling it, once the stockpile run dry and the demand didn't warrant making another batch. Which was when I found a shop with them in stock and bought three. I believe they'll stay supported for a while.

Disclaimer: I work at Google, but don't have insider knowledge on this.

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

#307

Post by jjeaff »

jdofaz wrote: post #295
xyzzy_plugh wrote: post #207

Earlier quoted context omitted.

Yeah I fully expect imap to disappear in the next few years. I've started migrating to domains I own for this reason. I can see them keeping it around for enterprise for a bit longer, though.

I think it will stick around as long as it is the way the iOS Mail app connects

I don't know. Seems like an easy way to force everyone on to the iOS Gmail app. People aren't going to change their email address because it doesn't work with the iOS mail app.

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

#308

Post by bryanrasmussen »

sterlind wrote: post #283
panarky wrote: post #271

Earlier quoted context omitted.

Would love to see a comparison of products "killed by Google" to products "killed by Microsoft" or even "killed by General Electric". I'd bet a week's paycheck that Google's list would be the shorter one.

Microsoft hasn't killed many online services, and besides Azure doesn't have dominant control of the internet like Google does. MS kills support for old box products and hardware devices, but that doesn't mean you can't still use them! (Also, what would we even kill? Bing? MSN?) When Google pulls the plug on Nest, they burn an entire ecosystem, and piss off the people they should be working with on IoT. It's really s…

I gotta say, I would never develop anything on Google because I would worry I end up with some little niche business that brings a little extra for my efforts and then they'll kill it. It's an added risk.

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

#309

Post by izacus »

gboudrias wrote: post #74
GiorgioG wrote: post #37

Man, Google is the new Microsoft of the 90s. Fuck them. I have 3 Nest thermostats (bought prior to the Nest acquisition.)

Really curious how shutting down every service works as a business model.

Probably better than keeping products that lose money around?

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

#310

Post by welly »

KukicAdnan wrote: post #252

Google decides to unify APIs under a single IoT brand, thus shutting down redundant APIs. Google bad. Google maintaining multiple APIs that essentially do the same thing. Google bad. People are going to complain either way. I welcome this change personally and think it makes perfect business sense. I can't think of any Works with Nest that I have integrated in my home that's not already connected to my Google Home, s…

Given the comments in this post, I think people disagree with you.

Not sure how you came to the conclusion that because you can't think of any integrations you personally use that it won't affect others.

Post reply on HN