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

481–490 of 600 posts

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

#481

Post by FerretFred »

telltruth wrote: post #305
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.

The big problem here is that there are a lot of people that have spent a lot of money in buying quality hardware that isn't just for leisure, it's for protection. I'll cite my 4 Nest Protects and an outdoor camera as an example. If somehow they get "sunsetted" due to some Google whim, fad or Because They Can, then I'm going to be pretty p*ssed to say the least. Based on past experience I don't trust Google to act in the users interest.

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

#482

Post by Zenst »

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…

Reading thru it, it is not as brutal as it sounds, more that the they merged it into the Google Assistant API, removing direct access permission to the NEST device (remember microphone-gate with NEST) and consolidating those permissions into Assistant.

Whilst they are killing it off, they have a transition.

However, as far as timelines go - August 2019 kill off date for the NEST API is brutal and not exactly the grace period users of connected devices/software will appreciate or in many a cases with tech designed for non-technical people - know nothing until suddenly in August find what was working yesterday is now not working.

Be interesting to get the perspective of the Assistant API for NEST interaction over the current NEST API. Any functionality that is now no-longer an option and show-stopper? Any improvements?

Still, they could of done what they did with Map's and monerterised the API. Not that there is nothing stopping them doing that with the Assistant API. Which with some businesses has become the norm.

Maybe API's need some sort of Long Term Support flavours, least be much fairer for any transitions taken down the line.

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

#484

Post by bryanrasmussen »

bryanrasmussen wrote: post #356
PrimeDirective wrote: post #345

Earlier quoted context omitted.

I tried finding information on this, but couldn't. Could you provide links?

sorry, I thought I was clear in suggesting it as a law - although realistically in a lot of EU countries you could make the case and get it returned. For example I'm in Denmark and we have a consumer ombudsmand were you can make complaints about violations of your rights as a consumer https://www.consumerombudsman.dk/about-us/ (it talks about marketing but I the Nest was marketed to have functionality it no longer ha…

Update - I had an opportunity to ask someone who definitely knows exactly what the rules are in Denmark and they said that if Google refused to refund you would have to take them to court but they are also certain that any eventual legal process would find Google liable for refunding as long as the Nest was ever marketed for its now no longer functioning capabilities.

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

#485

Post by tw04 »

glitch003 wrote: post #258
tw04 wrote: post #173

Can't wait for them to tell me that Google Apps accounts aren't supported so I'll lose all access to my Nest devices... if that happens I'll be removing all of my Nest devices and selling my Google Home. I'm SO SICK of them acting like there needs to be a firewall between google apps accounts and everything else .

Well, Google Apps accounts are for businesses, so it makes sense that they wouldn't work like a personal account.

That's not at all how it started. It started as a way to host your own domain for free and that's how they advertised and supported it. 10 years on they changed their mind but that's bullshit.

I was your guinea pig so you could perfect the service for business users, now that you're done with that experiment you want to hang us all out to dry.

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

#486

Post by Marsymars »

agildehaus wrote: post #222
mc32 wrote: post #66

I used to be a fan of Google. They were the good ones, the open ones. Ha! I’ve feel like they played the long sucker game. How times have changed. Even Android feels like a ruse. And Chrome. And maps. The last thing will be search. At some point it’ll be curated for my own good. To be fair, Everyone has to make a living, but be honest don’t take people for suckers of make them into suckers.

I recall thinking, a long time ago, "You never see ads for Google stuff on TV. That's because what they make is so much better they don't need to advertise them." I think you can mark the spot where the business folk took the reins from the engineers by the date of their first TV ads.

I don't watch TV ads, but a giant Chromebook ad is now cycling on the billboard next to my office.

I really wish more jurisdictions would ban billboard ads.

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

#487

Post by swebs »

hyeonwho4 wrote: post #118
kd0amg wrote: post #95

Earlier quoted context omitted.

First they came for Google Wave, and I did not speak out—Because I never really understood what Wave was to begin with. Then they came for Google+, and I did not speak out—Because almost all the people I want life updates from are on Facebook. Then they came for Google Reader, and I did not speak out—Because I never actually heard of Reader until years after it was eliminated. Maybe Reader was actually first? Then th…

You don't seem fully serious, but the writing is probably on the wall for third party tools which integrate with GMail. I use InboxZero through Beeminder, and could see Beeminder being locked out.

They make it really difficult to use your Gmail account with K9 Mail. You have to jump through a bunch of hoops and "critical security warnings" for attempting to sign in with a non-Google app.

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

#488

Post by jordanbeiber »

iainmerrick wrote: post #457
jordanbeiber wrote: post #347

Earlier quoted context omitted.

Well for sure, when it comes to developer exposure. This point was about “enterprise” software in general and the fact that many a project has been abandoned and put down in this space without much fanfare. Also, many big companies tend to pay a lot of money for software the never actually use, hence “cushy”.

I think you have the wrong end of the stick. Plenty of companies do that, sure, but Microsoft has always been a very, very aggressive mass-market player. Their software is used in enterprise, sure, but it’s by almost every enterprise, not just isolated niches. They’re competitive on prices too (although it’s tough when many of your direct competitors are free). Compare MS Office with something like Maya or AutoCAD, s…

You might be missing my point a bit.

First of all I’m talking developer exposure.

Many angry devs have sat in their cubicle swearing at MS & others product teams for changes made or products dropped. These products doesn’t necessarily have the visibility of google services.

What I’m further trying to say is that it’s a culture thing.

Times are changing and with it the business model of selling standardized crap to clueless, ignorant customers.

How quick this change comes for a company is dependent mostly on the inertia of it’s customer base i guess.

Businesses are starting realize that you need to take back control of data and process to increase opportunities for innovation as well as speedy delivery.

This culture has in ways been pioneered by for example google and others selling/providing services rather than software suites.

They have constant change as an inherent property of their organization and this leaks.

This is ofc just my take on it.

(Digression regarding prices: maya and cad are business drivers. You need to compare them to SAP or possibly the bizdev stuff from MS == not cheap)

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

#489

Post by Marsymars »

jonstewart wrote: post #435

I bought two Nest thermostats this winter because they worked with only R-W wires. I turned off the learning feature, as it was useless for my house with its combination of passive solar and radiant heat. However, the API is/was quite simple and I was looking forward to writing my own controller. Still, I had this nagging feeling that I shouldn’t have bought them. Thanks for confirming my anxieties, Google! I can’t t…

> I bought two Nest thermostats this winter because they worked with only R-W wires.

FWIW, I've got a gas fireplace with no C wire that I added a 120V->24V AC adapter and a Fast-STAT common maker to for <$100 to wire my Ecobee thermostat without needing to alter any in-wall wiring.

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

#490

Post by EADGBE »

teej wrote: post #127
electrograv wrote: post #38

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.

Also, people who take Google's side on this don't see the downside; they're probably already Google Assistant users. Now they're just getting the functionality they always wanted with a device (Looks like that Homekit integration isn't going to happen after all...).
Post reply on HN