HomeKit Control lets you control Apple HomeKit Exclusive accessories through Homebridge, This is especially useful to gain all the benefits of Homebridge alongside controlling them using other services and plugins through Homebridge, such as:
homebridge-gsh
plugin)homebridge-alexa
plugin)The Plugin currently supports the following Services provided by WLAN-based HomeKit enabled devices:
Please note that BLE is currently not supported, as it seems to be unstable when multiple BLE-enabled Plugins are installed. All supported sensors on any configured device are automatically discovered and added when Homebridge starts up.
sudo npm i -g homebridge-homekit-control
To pair your devices with Homebridge HomeKit Control, follow these steps:
Discover Devices:
homekitPair
homekitPair [network] [interface]
, for example: homekitPair -i wlan0
Select the device you want to pair, and enter the pairing code (including -
, example 123-45-678
).
Enter a filename to save pairing information in JSON format.
In the JSON file, you'll find the following information:
{
"id": "device id",
"name": "device name",
"address": "device ip",
"port": device-port,
"pairingData": {
"AccessoryPairingID": "xxx",
"AccessoryLTPK": "xxx",
"iOSDevicePairingID": "xxx",
"iOSDeviceLTSK": "xxx",
"iOSDeviceLTPK": "xxx"
},
"accessories": {
"accessories": [...]
}
}
Note down the "id"
, "name"
, "address"
, "port"
and "pairingData"
from the JSON file.
Go to Plugins page and Click on the SETTINGS button under Homebridge Homekit Control and fille out the information we noted from the JSON file in the previous steps
This Plugin supports the Configuration Interface in Homebridge UI (homebridge-config-ui-x). Simply add a new Device and paste the values you obtained above.
Here are some additional configuration parameters, not obtained by the Device Pairing:
services.enableHistory
(boolean): true will enable fakeGato for compatible Sensors. This will allow you to view a history in the EVE-Appservices.historyInterval
(optional, numeric): Determins the Interval used to take readings. The valus range is [30, 600]. The default value is 600services.proxyAll
(optional, boolean): By default we only proxy tested services and characteristics from your devices. When this mode is enabled, all available services and characteristics are proxied. Be carefull when activating, this may cause damage to your devices. The default value is falseservices.uniquePrefix
(optional, string): When a device is added to multiple HomeBridge instances in the same network, you will need to provide a unique prefix. Otherwise Eve-App will get confused.{
"platforms": [
{
"platform": "HomekitControl",
"services": [
{
"id": "device id",
"name": "device name",
"address": "device ip",
"port": "device port",
"enableHistory": false,
"pairingData": {
"AccessoryPairingID": "xxx",
"AccessoryLTPK": "xxx",
"iOSDevicePairingID": "xxx",
"iOSDeviceLTSK": "xxx",
"iOSDeviceLTPK": "xxx"
}
}
]
}
]
}
if you get the error M2: Error: 6
:
homekitPair
command in your Homebridge and enter the pin(!!! Use at your own risk !!!)
Please let me know if you use this plugin and got it to work with a new HomeKit-Accesory that is not listed above
The project was converted to the build system from https://github.com/homebridge/homebridge-plugin-template. Visual Studio Code is set up to lint on save.
Using npm run dev
will launch the develop environment, where your code is automatically compiled on save and the local homebridge server is automatically restarted.
The command npm rund build
will trigger the compilation of your project manually.