HomeBridge is a lightweight NodeJS server you can run on your home network that emulates the iOS HomeKit API. It includes a set of "shims" (found in the accessories and platforms folders) that provide a basic bridge from HomeKit to various 3rd-party APIs provided by manufacturers of "smart home" devices.
Since Siri supports devices added through HomeKit, this means that with HomeBridge you can ask Siri to control devices that don't have any support for HomeKit at all. For instance, using the included shims, you can say things like:
- Siri, unlock the front door. (Lockitron)
- Siri, open the garage door. (LiftMaster MyQ)
- Siri, turn on the Leaf. (Carwings)
- Siri, turn off the Speakers. (Sonos)
- Siri, turn on the Dehumidifier. (WeMo)
- Siri, turn on Away Mode. (Xfinity Home)
- Siri, turn on the living room lights. (X10 via rest-mochad or Wink via wink-js)
If you would like to support any other devices, please write a shim and create a pull request and I'd be happy to add it to this official list.
There are 2 types of shims supported in HomeBridge.
- Accessory - Individual device
- Platform - A full bridge to another system
Accessories are individual devices you would like to bridge to HomeKit. You set them up by declaring them individually in your config.json file. Generally, you specify them by name or id and which system they use.
Platforms bridge entire systems to HomeKit. Platforms can be things like Wink or SmartThings or Vera. By adding a platform to your config.json, HomeBridge will automatically detect all of your devices for you.
Wink is currently the only supported platform at the moment.
All you have to do is add the right config options so HomeBridge can authenticate and communicate with your other system, and voila, your devices will be available to HomeKit via HomeBridge.
Technically, the device manufacturers should be the ones implementing the HomeKit API. And I'm sure they will - eventually. When they do, these shims will be obsolete, and I hope that happens soon. In the meantime, this server is a fun way to get a taste of the future, for those who just can't bear to wait until "real" HomeKit devices are on the market.
HomeBridge itself is basically just a set of shims and a README. The actual HomeKit API work was done by KhaosT in his HAP-NodeJS project. Additionally, many of the shims benefit from amazing NodeJS projects out there like sonos and wemo that implement all the interesting functionality.
I would call this project a "novelty" in its current form, and is for intrepid hackers only. To make any of this work, you'll need:
- An app on your iOS device that can manage your HomeKit database.
- An always-running server (like a Raspberry Pi) on which you can install NodeJS.
- Knowledge of Git submodules and npm.
You'll also need some patience, as Siri can be very strict about sentence structure, and occasionally she will forget about HomeKit altogether. But it's not surprising that HomeKit isn't rock solid, since almost no one can actually use it today besides developers who are creating hardware accessories for it. There are, to my knowledge, exactly zero licensed HomeKit devices on the market right now, so Apple can easily get away with this all being a work in progress.
Additionally, the shims I've created implement the bare minimum of HomeKit needed to provide basic functionality like turning things off and on. I haven't written any kind of good feedback or error handling, and although they support changing state, they don't support reading the current state, so if you ask questions like "Is my door unlocked?" Siri will respond with the default of "Nope!" no matter what.
OK, if you're still excited enough about ordering Siri to make your coffee (which, who wouldn't be!) then here's how to set things up. First, clone this repo and also init submodules to grab the HAP-NodeJS project which isn't in npm. You'll also need to run npm install on HAP-NodeJS:
$ git clone https://github.com/nfarina/homebridge.git
$ cd homebridge
$ git submodule init
$ git submodule update
$ npm install
$ cd lib/HAP-NodeJS
$ npm install
Node: You'll need to have NodeJS version 0.12.x or better installed for HAP-NodeJS to load.
Now you should be able to run the homebridge server:
$ cd homebridge
$ npm run start
Starting HomeBridge server...
Couldn't find a config.json file [snip]
The server won't do anything until you've created a config.json file containing your home devices (or accessories in HomeKit parlance) or platforms you wish to make available to iOS.
Once you've added your devices and/or platforms, you should be able to run the server again and see them initialize:
$ npm run start
Starting HomeBridge server...
Loading 6 accessories...
[Speakers] Initializing 'Sonos' accessory...
[Coffee Maker] Initializing 'WeMo' accessory...
[Speakers] Initializing 'Sonos' accessory...
[Coffee Maker] Initializing 'WeMo' accessory...
[Wink] Initializing Wink platform...
[Wink] Fetching Wink devices.
[Wink] Initializing device with name Living Room Lamp...
Your server is now ready to receive commands from iOS.
HomeKit is actually not an app; it's a "database" similar to HealthKit and PassKit. But where HealthKit has the companion Health app and PassKit has Passbook, Apple has supplied no app for managing your HomeKit database (yet). However, the HomeKit API is open for developers to write their own apps for adding devices to HomeKit.
Fortunately, there is at least one app that has slipped into the App Store that can manage your HomeKit devices. It's called MyTouchHome and it costs $2. This is by far the easiest way to get up and running.
You might also want to do a quick search in the App Store for "HomeKit" and see if any better/free options have popped up since the time of this writing.
Alternatively, if you have an Apple Developer account, you can build and run your own HomeKit iOS app. This is a lot of work but it's also free (if you happen to have a $99 Apple Developer account already).
There are a few open-source apps out there that let you manage your HomeKit database, but the best one I've found is BetterHomeKit, also made by KhaosT.
The tricky part is that, in order to run an app that uses HomeKit on your phone, you'll need to register your own unique App ID in the Apple Developer Portal, as if you were planning to submit this app to the App Store, and you'll need to enable the HomeKit "service" for that App ID in the Apple Developer Portal (similar to Game Center). You'll need to pick your own unique Bundle ID as well (like com.yourdomain.HomeKitApp), and actually change the BetterHomeKit Info.plist to use that bundle ID instead of the default org.oltica.BetterHomeKit.
Once you've gotten a HomeKit app running on your iOS device, you can begin adding accessories. The app should "discover" the accessories defined in your config.json file, assuming that you're still running the HomeBridge server and you're on the same Wifi network.
When you attempt to add a device, it will ask for a "PIN code". The default code for all HomeBridge accessories is 031-45-154. Adding the device should create some files in the persist directory of the HomeBridge server, which stores the pairing relationship.
Once your device has been added to HomeKit, you should be able to tell Siri to control your devices. However, realize that Siri is a cloud service, and iOS may need some time to synchronize your device information with iCloud.
Also, keep in mind HomeKit is not very robust yet, and it is common for it to fail intermittently ("Sorry, I wasn't able to control your devices" etc.) then start working again for no reason. Also I've noticed that it will get cranky and stop working altogether sometimes. The usual voodoo applies here: reboot your device, restart the homebridge server, run your HomeKit iOS app and poke around, etc.
One final thing to remember is that Siri will almost always prefer its default phrase handling over HomeKit devices. For instance, if you name your Sonos device "Radio" and try saying "Siri, turn on the Radio" then Siri will probably start playing an iTunes Radio station on your phone. Even if you name it "Sonos" and say "Siri, turn on the Sonos", Siri will probably just launch the Sonos app instead. This is why, for instance, the suggested name for the Sonos shim in config-samples.json is "Speakers".
HomeKit is definitely amazing when it works. Speaking to Siri is often much quicker and easier than launching whatever app your device manufacturer provides.
I welcome any suggestions or pull requests, but keep in mind that it's likely not possible to support all the things you might want to do with a device through HomeKit. For instance, you might want to hack the Sonos shim to play the specific kind of music you want and that's great, but it might not be appropriate to merge those specific changes into this repository. The shims here should be mostly simple "canonical examples" and easily hackable by others.
Good luck!