Live data from Hacker News

Works With Nest

nest.com

131–140 of 168 posts

Re: Works With Nest

#131
post #120

Earlier quoted context omitted.

Yes I have the heating on a timer and its off when I am at work. I turn it on if its cold and I working from home or its the weekend. I believe this is normal...

It's not normal. The majority of people can't be bothered switching it on or off, so they just leave it on all the time.

Any HVAC system installed or revamped in the past 15 years is likely to have a programmable thermostat. Whether people are using these _correctly_ or not (which as others have touched on here is not necessarily super intuitive, part of the problem Nest is meant to solve), I think attempts of some sort at saving energy with these is pretty common.

Re: Works With Nest

#132

I have a Nest. Nest doesn't allow you to access your own data that they are no doubt collecting, and their app only shows your energy use for the last 10 days. This makes it absolutely useless for trying to figure out how to optimize your energy usage on a month-to-month or season-by-season basis.

This is why I purchased an ecobee (www.ecobee.com) instead of Nest, despite the obviously superior interface provided by Nest.

Re: Works With Nest

#133

Earlier quoted context omitted.

I'm glad you mentioned HomeKit, because at this point, I'm really starting to fight my desire to go out and hook all of these things up to make sure they work with HomeKit. Apple doesn't exactly have a history of really releasing the standards they say they will (looking at you, iMessage), but I'm all for the idea of standardized home automation.

When did they ever say iMessage would be an standard? I recall them stating FaceTime would be, but didn't some patent nonsense get in the way?

I'm misremembering - it was FaceTime, not iMessage. Whoops.

Unless I'm continuing to misremember, there was some patent issue that blocked FaceTime from working over cellular on the first version, but it was cleared up when AT&T finally accepted that they were the only carrier not supporting it.

Re: Works With Nest

#134
post #125

Earlier quoted context omitted.

Otoh, home automation might finally go from being a hobby to something normal people actually can use to make their lives easier. I also dabbled with X10 in the 90s and personally I can't wait for apple to come along and do it right. Needless to say, I completely disagree with your final observation.

"normal people actually can use to make their lives easier" Normal people don't like capital investment of any sort either monetary or time, and newer technology seems not to change the total investment at all, beyond a modest increase, but only adjust the ratio between the two categories. There is also the stereotypical UI tradeoff that has existed for decades in computers of "make simple things easy" which is almos…

On the contrary, most people with the income to do so are in fact delighted to invest in things that simplify their lives and save them time. It's one of the pleasures of the modern era.

Regarding this claim about UI tradeoffs, you clearly do not remember the past seven years. Were I to travel back to 2006 and hand you an iPhone 5, you would think it was a gift from some distant alien civilization. The point being that great design continually defines upward what "make simple things easy" means. It is not diametrically opposed to making the difficult things possible.

Re: Works With Nest

#135

I have a Nest. Nest doesn't allow you to access your own data that they are no doubt collecting, and their app only shows your energy use for the last 10 days. This makes it absolutely useless for trying to figure out how to optimize your energy usage on a month-to-month or season-by-season basis.

https://developer.nest.com/documentation/api-reference For a while, you could pull that data through a private JSON API, the same one the iPhone app used. I'm assuming something changed a few months ago though, because the application I wrote to chart out that information stopped receiving those data points. This was probably part of the transition to a public API. Using the API, I was able to see that running just t…

One of the prohibitions when signing up for the developer program is this:

> [Prohibited] Collect, aggregate, re-syndicate, retain, log or store Customer Data (as defined below) received via the Nest API beyond 10 trailing days from the date when the data is received.

Re: Works With Nest

#136

Earlier quoted context omitted.

https://developer.nest.com/documentation/api-reference For a while, you could pull that data through a private JSON API, the same one the iPhone app used. I'm assuming something changed a few months ago though, because the application I wrote to chart out that information stopped receiving those data points. This was probably part of the transition to a public API. Using the API, I was able to see that running just t…

One of the prohibitions when signing up for the developer program is this: > [Prohibited] Collect, aggregate, re-syndicate, retain, log or store Customer Data (as defined below) received via the Nest API beyond 10 trailing days from the date when the data is received.

I wonder if the privacy "advocates" (and I really want to use the word "whiners" here) are to blame for that particular restriction. I can't see a business case for Nest to disallow that.

Re: Works With Nest

#137

Earlier quoted context omitted.

When did they ever say iMessage would be an standard? I recall them stating FaceTime would be, but didn't some patent nonsense get in the way?

I'm misremembering - it was FaceTime, not iMessage. Whoops. Unless I'm continuing to misremember, there was some patent issue that blocked FaceTime from working over cellular on the first version, but it was cleared up when AT&T finally accepted that they were the only carrier not supporting it.

No patent issue, just AT&T and money.

The patent issue is a DoD-connected company forcing Apple to abandon P2P and break the end-to-end encryption. Not unlike what happened with Skype, though quite a bit more hostile.

Re: Works With Nest

#138

Earlier quoted context omitted.

> "like override the schedule and turn the heat up when you take a day off work, or turn the heat down when nobody is home, all with no user interaction." Useful sure, but is it that useful? Which is to say, will people choose it over walking over and twisting a knob? The same argument can be made for motorized blinds. Sure, yeah, it'd be kind of cool for your blinds to raise and lower themselves with the day/night c…

I don't know how everybody else gets their nests, but I pay flat rate for power and my power company gives them out for free because it works out cheaper for them in the long run. So no, I probably wouldn't pay extra for a nest thermostat and the small amount of convenience it offers, but I like having it.

Once the Nest API gets more mature, watch power companies give these out with the ability to remotely turn your A/C up if the power grid starts to sag (that whole "rush hour" concept they're pushing).

Re: Works With Nest

#139

Earlier quoted context omitted.

One of the prohibitions when signing up for the developer program is this: > [Prohibited] Collect, aggregate, re-syndicate, retain, log or store Customer Data (as defined below) received via the Nest API beyond 10 trailing days from the date when the data is received.

I wonder if the privacy "advocates" (and I really want to use the word "whiners" here) are to blame for that particular restriction. I can't see a business case for Nest to disallow that.

It may be that they plan to introduce long-term energy use stats and information.

Re: Works With Nest

#140

Earlier quoted context omitted.

I'm glad you mentioned HomeKit, because at this point, I'm really starting to fight my desire to go out and hook all of these things up to make sure they work with HomeKit. Apple doesn't exactly have a history of really releasing the standards they say they will (looking at you, iMessage), but I'm all for the idea of standardized home automation.

Remember when Steve said he was going to the standards boards the next day with the spec for FaceTime? I checked intermittently for about a year afterwards: never saw any activity to substantiate that claim.

Would it have helped? It apparently infringes multiple patents Apple does not control. They lost to VirnetX and now Samsung is going after them.
Post reply on HN