4 ms·

> "HomeKit doesn't require a proprietary Apple chip, I have no idea where you got that idea." A few sources disagree: http://www.ibtimes.com/apple-homekit-dev

> "HomeKit doesn't require a proprietary Apple chip, I have no idea where you got that idea." A few sources disagree: http://www.ibtimes.com/apple-homekit-devices-wont-include-google-incs-nest-thermostat-1793516 http://www.ibtimes.com/apple-homekit-devices-wont-include-go... > "Apple’s MFi guidelines require manufacturers to use only Wi-Fi or Bluetooth, and also include a specialized chip for authentication" http://www.digitaltrends.com/home/everything-that-works-with-apple-homekit/ http://www.digitaltrends.com/home/everything-that-works-with... > "The certification ensures that these smart home devices have an authentication chip and have undergone rigorous testing to get Apple’s official seal of approval" http://www.eetimes.com/document.asp?doc_id=1327267 http://www.eetimes.com/document.asp?doc_id=1327267 > "Apple Inc. requires anyone making a device compatible with its HomeKit environment to buy and use a special identity chip." Now, I don't have access to the official docs for MFi - so maybe these sources are all wrong. But I'm pretty confident a special chip is required.

tinus_hn 10y ago
The Homebridge project provides HomeKit compatibility without Apple authorization. I don't know if Apple controls this using patents or trademarks but you don't technically need Apples authorization.
- artimaeis 10y ago
  From what I can tell from Homebridge they provide HomeKit emulation - not compatibility. You're running a local Node server to emulate the Homekit API. Still neat - but hardly the sort of thing that implies you can ship a product utilizing Homekit without following the MFi spec.
  - eridius 10y ago
    To emulate the iOS HomeKit API, meaning you can write plugins for it to provide support for non-HomeKit-enabled devices. But presumably Homebridge itself must still vend itself as a HomeKit-enabled device on the network or else you wouldn't be able to control it.
- stonesam92 10y ago
  I'm pretty sure that when you register a Homebridge instance to your Apple device though you get a message about the accessory being in test mode. Homebridge is presumably making use of some debug mode that you wouldn't use in a shipping product - and if you did, Apple wouldn't let you advertise it as officially compatible with HomeKit.
eridius 10y ago
Huh, you might be right. I've never run across any references to this before, all I've seen in the past is about how HomeKit has very high security standards and that's why a lot of devices don't work. Still, without access to the MFi documentation, it's not clear if this chip is actually required or if it's just the easiest way to meet the security requirements that HomeKit imposes.

tinus_hn 10y ago

The Homebridge project provides HomeKit compatibility without Apple authorization. I don't know if Apple controls this using patents or trademarks but you don't technically need Apples authorization.

artimaeis 10y ago
From what I can tell from Homebridge they provide HomeKit emulation - not compatibility. You're running a local Node server to emulate the Homekit API. Still neat - but hardly the sort of thing that implies you can ship a product utilizing Homekit without following the MFi spec.
- eridius 10y ago
  To emulate the iOS HomeKit API, meaning you can write plugins for it to provide support for non-HomeKit-enabled devices. But presumably Homebridge itself must still vend itself as a HomeKit-enabled device on the network or else you wouldn't be able to control it.
stonesam92 10y ago
I'm pretty sure that when you register a Homebridge instance to your Apple device though you get a message about the accessory being in test mode. Homebridge is presumably making use of some debug mode that you wouldn't use in a shipping product - and if you did, Apple wouldn't let you advertise it as officially compatible with HomeKit.

eridius 10y ago

Huh, you might be right. I've never run across any references to this before, all I've seen in the past is about how HomeKit has very high security standards and that's why a lot of devices don't work. Still, without access to the MFi documentation, it's not clear if this chip is actually required or if it's just the easiest way to meet the security requirements that HomeKit imposes.