mirror of
https://github.com/mtan93/homebridge.git
synced 2026-03-08 05:31:55 +00:00
README update; npm run start uses DEBUG
This commit is contained in:
28
README.md
28
README.md
@@ -1,9 +1,9 @@
|
|||||||
|
|
||||||
# HomeBridge
|
# Homebridge
|
||||||
|
|
||||||
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](accessories/) and [platforms](platforms/) folders) that provide a basic bridge from HomeKit to various 3rd-party APIs provided by manufacturers of "smart home" devices.
|
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](accessories/) and [platforms](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:
|
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](https://lockitron.com))
|
* _Siri, unlock the front door._ ([Lockitron](https://lockitron.com))
|
||||||
* _Siri, open the garage door._ ([LiftMaster MyQ](https://www.myliftmaster.com))
|
* _Siri, open the garage door._ ([LiftMaster MyQ](https://www.myliftmaster.com))
|
||||||
@@ -17,7 +17,7 @@ Since Siri supports devices added through HomeKit, this means that with HomeBrid
|
|||||||
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.
|
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.
|
||||||
|
|
||||||
# Shim types
|
# Shim types
|
||||||
There are 2 types of shims supported in HomeBridge.
|
There are 2 types of shims supported in Homebridge.
|
||||||
|
|
||||||
* Accessory - Individual device
|
* Accessory - Individual device
|
||||||
* Platform - A full bridge to another system
|
* Platform - A full bridge to another system
|
||||||
@@ -28,9 +28,9 @@ Accessories are individual devices you would like to bridge to HomeKit. You set
|
|||||||
|
|
||||||
## Platforms
|
## Platforms
|
||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
# Why?
|
# Why?
|
||||||
|
|
||||||
@@ -38,7 +38,7 @@ Technically, the device manufacturers should be the ones implementing the HomeKi
|
|||||||
|
|
||||||
# Credit
|
# Credit
|
||||||
|
|
||||||
HomeBridge itself is basically just a set of shims and a README. The actual HomeKit API work was done by [KhaosT](http://twitter.com/khaost) in his [HAP-NodeJS](https://github.com/KhaosT/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.
|
Homebridge itself is basically just a set of shims and a README. The actual HomeKit API work was done by [KhaosT](http://twitter.com/khaost) in his [HAP-NodeJS](https://github.com/KhaosT/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.
|
||||||
|
|
||||||
# Before you Begin
|
# Before you Begin
|
||||||
|
|
||||||
@@ -50,8 +50,6 @@ I would call this project a "novelty" in its current form, and is for **intrepid
|
|||||||
|
|
||||||
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.
|
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.
|
|
||||||
|
|
||||||
# Getting Started
|
# Getting Started
|
||||||
|
|
||||||
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:
|
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:
|
||||||
@@ -66,7 +64,7 @@ Now you should be able to run the homebridge server:
|
|||||||
|
|
||||||
$ cd homebridge
|
$ cd homebridge
|
||||||
$ npm run start
|
$ npm run start
|
||||||
Starting HomeBridge server...
|
Starting Homebridge server...
|
||||||
Couldn't find a config.json file [snip]
|
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. You can start by copying and modifying the included `config-sample.json` file which includes declarations for all supported accessories and platforms.
|
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. You can start by copying and modifying the included `config-sample.json` file which includes declarations for all supported accessories and platforms.
|
||||||
@@ -74,7 +72,7 @@ The server won't do anything until you've created a `config.json` file containin
|
|||||||
Once you've added your devices and/or platforms, you should be able to run the server again and see them initialize:
|
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
|
$ npm run start
|
||||||
Starting HomeBridge server...
|
Starting Homebridge server...
|
||||||
Loading 6 accessories...
|
Loading 6 accessories...
|
||||||
[Speakers] Initializing 'Sonos' accessory...
|
[Speakers] Initializing 'Sonos' accessory...
|
||||||
[Coffee Maker] Initializing 'WeMo' accessory...
|
[Coffee Maker] Initializing 'WeMo' accessory...
|
||||||
@@ -94,18 +92,18 @@ Fortunately, there are now a few apps in the App Store that can manage your Home
|
|||||||
|
|
||||||
There are also some free apps that work OK. Try [Insteon+](https://itunes.apple.com/US/app/id919270334?mt=8) or [Lutron](https://itunes.apple.com/us/app/lutron-app-for-caseta-wireless/id886753021?mt=8) or a number of others.
|
There are also some free apps that work OK. Try [Insteon+](https://itunes.apple.com/US/app/id919270334?mt=8) or [Lutron](https://itunes.apple.com/us/app/lutron-app-for-caseta-wireless/id886753021?mt=8) or a number of others.
|
||||||
|
|
||||||
|
If you are a member of the iOS developer program, I highly recommend Apple's [HomeKit Catalog](https://developer.apple.com/library/ios/samplecode/HomeKitCatalog/Introduction/Intro.html) app, as it is reliable and comprehensive and free (and open source).
|
||||||
|
|
||||||
## Adding HomeKit Accessories
|
## Adding HomeKit Accessories
|
||||||
|
|
||||||
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.
|
Once you've gotten a HomeKit app running on your iOS device, you can use it to add your Homebridge devices. The app should "discover" the single accessory "Homebridge", assuming that you're still running the Homebridge server and you're on the same Wifi network. Adding this accessory will automatically add all accessories and platforms defined in `config.json`.
|
||||||
|
|
||||||
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.
|
When you attempt to add Homebridge, it will ask for a "PIN code". The default code is `031-45-154` (but this can be changed, see `config-sample.json`). This process will create some files in the `persist` directory of the Homebridge server, which stores the pairing relationship.
|
||||||
|
|
||||||
# Interacting with your Devices
|
# Interacting with your Devices
|
||||||
|
|
||||||
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.
|
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".
|
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".
|
||||||
|
|
||||||
# Final Notes
|
# Final Notes
|
||||||
|
|||||||
@@ -3,7 +3,7 @@
|
|||||||
"description": "HomeKit support for the impatient",
|
"description": "HomeKit support for the impatient",
|
||||||
"version": "0.0.0",
|
"version": "0.0.0",
|
||||||
"scripts": {
|
"scripts": {
|
||||||
"start": "node app.js"
|
"start": "DEBUG=* node app.js"
|
||||||
},
|
},
|
||||||
"repository": {
|
"repository": {
|
||||||
"type": "git",
|
"type": "git",
|
||||||
|
|||||||
Reference in New Issue
Block a user