Ah, that's good to know. Still the fact that a temperature change done through HomeKit causes the thermostat to behave differently that a similar temperature change through the the native app or the actual thermostat itself.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
HomeKit Support for Nest Smart Products Unlikely Anytime Soon
- Thread starter MacRumors
- Start date
- Sort by reaction score
Ah, that's good to know. Still the fact that a temperature change done through HomeKit causes the thermostat to behave differently that a similar temperature change through the the native app or the actual thermostat itself.
Why would anyone at Google/Nest have any plans to incorporate a new technology less than two weeks after it was announced, much less a roadmap.
I mean, viability questions aside, this seems like tech sites are really jumping the gun with their prognostications here...
I mean, viability questions aside, this seems like tech sites are really jumping the gun with their prognostications here...
AFAIK, the only additional responsibility that devices will take on will be encrypting communications between it and the HomeKit hub. If you know of anything else, I'd love to learn about it!
In iOS 11, HomeKit reduces that amount of communication. It used to require two communications for a device to announce any changes to a hub. Now it only requires one.
So if the device wasn't talking that much to the hub in the first place, and iOS 11 reduces that amount even lower, it sounds like the "extra responsibility" the devices need to take on isn't necessarily onerous.
Google doesn't seem to give a **** about the nest any more. It was an amazing device when it first came out. Then google bought the company and now it's just lacking updates and creativity. How have they not released a standalone thermometer? Stupid really.
When people ask what smart thermostat should I get, my first response is " I wouldn't buy a nest anymore" maybe the Eco bee.
When people ask what smart thermostat should I get, my first response is " I wouldn't buy a nest anymore" maybe the Eco bee.
Never did. I automate with Alexa. However if they added HomeKit now I would be happy to have the option.
[doublepost=1497626011][/doublepost]
It sounds like software support is now possible. And people have hacked around the hardware requirement: https://github.com/nfarina/homebridge
All I was saying is that if they add it now through a software update per the new rules then I'll be happy to have the choice if it comes to that for me.
It's not about using the Home app. It's about building smart templates using conditionals which can trigger the heat or AC.
You can already add unofficial HomeKit support with a computer (Mac or raspberry Pi) and the HomeBridge software here https://github.com/nfarina/homebridge
I've got smartthings, nest, sonos, and belkin wemo working through HomeKit with this.
I've got smartthings, nest, sonos, and belkin wemo working through HomeKit with this.
Covered much of that in other posts in this thread. As far as hacking, besides potential performance issues why would you want to do this which negates the value of HomeKit over other voice control systems [bolded for emphasis] : sudo npm install -g --unsafe-perm homebridge?
Bottomline is Nest isn't going to make older Nests backwards compatible even if it eventually makes a HomeKit compatible product. If you want voice control Nest works with Alexa today. Why not go with that system if that is what you want? Alexa works with iOS and, frankly Dots are cheaper and more convenient than having a bunch of old iPads sitting around like I have.
I don't understand the obsession with using "the cloud" for home automation. Your internet connection goes down? Suddenly your automation products are useless. The provider gets hacked? They suddenly have access to your home and all its history data. Company goes out of business? The products become paperweights.
Local devices should always be controllable locally, over WiFi, without a single packet needing to leave the home network. The only time external servers should be involved is when you're controlling the devices from outside the home. This is how the Philips Hue systems works, for example, and it's excellent.
Apple has the right idea requiring local control. Screw all these companies that insist on making products slaved to their external servers.
No, that is correct, and what I said. Maybe I didn't summarize it succinctly enough, I don't know. But meaningful encryption and decryption isn't a light process and will affect performance on older processors on devices where the processor was not intended to take on that job.
As I noted, previously HomeKit devices had a chip exclusively for security precisely because of the heavy load that takes on processing and overall device performance. Even iDevices had that separate chip, they didn't depend on the Ax chip to do that alone. Under the new rules developers don't need a separate chip, but they do need a chip powerful enough to take on all tasks simultaneously with zero lag. If there is a performance hitch Apple will not certify that device.
[doublepost=1497627080][/doublepost]
You can isolate HomeBridge. Not like I'd run it on my regular working computer
As I said, I'm happy if they add support. I don't need it but I would welcome the option. Not sure why that's hard to understand.
There is potential, with out adequate security, for your smart device to be hacked which would then give access to your network and computers. Plenty of literature on this. It's not possible remotely if there is good security. Remove the security and all bets are off. Remove the Homekit and it's really easy for anyone who comes into your home to hack it and then control your network remotely. Takes about a minute.
But again, why are you hung up on HomeKit? Just move over to Alexa.
Agreed, I would rather have all of my information regarding my home automation stay locally for the reasons you pointed out.
Exactly, but I have a more nefarious view of using "the Cloud".
Let's say, for example, The State of California says that you don't need your house to be 72°, but has determined that you would be just fine at 85°. With the "the Cloud", the automation is done, and you don't really have a say in the matter without resorting to a paper clip to short the terminals together.
Acceptable losses during the heat wave are 1 person in 10,000,000, so it's OK if 50 people die, except, of course, if you're one of them. All for the greater good, of course.
Don't worry, there will be an appeal process, but unfortunately, there will be a 6 month delay on appeal hearings.
You need to review my very first post that I had. I already have Nest and subsequently I said I already use it with Alexa. I am not hung up on HomeKit as much as you are. From the first I said I would welcome the ability if it can be added. This shouldn't be hard to understand.
Well it is hard to understand when you keep responding to my posts regarding HomeKit. It also shouldn't be hard to understand that your Nest is never going to have HomeKit so why even waste a dream about it?
There are few major reasons for wanting HomeKit.
- In current implementation, HomeKit requires devices to be equipped with a secure chip that provides HomeKit-spec end-to-end encryption and DDoS protection.
- Integration and interoperability. HomeKit devices can pull configuration from HomeKit, such as rooms and scenes. Furthermore, HomeKit's automation framework can provide features 3rd party apps may not.
- Even when hardware maker goes out of business or stops providing a functional app, HomeKit devices will continue to work.
- Laggy. iOS 11 will supposedly fix this issue (especially Bluetooth), but currently, HomeKit devices are slower to respond than using 3rd party app directly.
- Smaller selection. No doubt due to Apple currently requiring secure chip and other specs.
- Siri. For many, Siri is not as reliable as Alexa and Google Now.
- No direct cloud access. Apple does not offer direct access to HomeKit devices (e.g., iCloud), only through a hub connected to the Internet (Apple TV, iPad, and soon HomePod). This makes it even laggier.
Last edited:
I reply when you reply to me. So I guess this will go on forever as the longest MacRumors thread... lol
From watching the WWDC video, it does look like iOS 11 will be faster. In iOS 10, it looks like when a device has an accessory state change, sends a notification to the hub. The hub accepts that notification, and then reaches back out to the device to see what the change was.
With iOS 11, it looks like the device can just send the accessory state change to the hub, and then the process is done. The hub will not have to reach back out to the device for anything.
You are right in the aspect that there is a *lot* of crap around. HomeKit for example has, typically.. garnered a false 'premium' for HomeKit accredited devices. The fact is, Siri is awful and Apple have no way to develop it further since the original Siri team left - what a surprise.
It gives a bad name to the whole 'Smart Home' perception - Google on the other hand (and Amazon w/ Alexa) however, are nailing it. Devices are cheaper and JUST as good - 90% made with the same materials and same tech, yet cost up to 75% less. The software is superior and the integration has come along nicely.