KNX platform shim for homebridge. This cannot run stand-alone in node!
Please also visit homebridge github homepage first.
Latest to homebridge-knx changes can be found in the CHANGELOG.md
This node module requires a running (and properly configured) knx daemon (knxd). You can find the latest version here.
I cannot support the knxd. Please address issues directly at the knxd issue pages. It might help to search the existing issues, as your problem might have been solved already.
sudo npm install -g homebridge
<any>directory you want; If you installed homebridge globally I recommend to do so with homebridge-knx:
sudo npm install -g homebridge-knx
KNX-sample-config.jsonto a new folder
.homebridgein your user folder (on a default installation raspberry, it's
/home/pi) and rename it to config.json
~/.homebridge, and adapt them to your needs (knxd address and some test devices in
knx_config.json). You do not need a
homebridge. If you have chosen a local install, go to the homebridge folder and do a
bin/homebridge --plugin-path <any>/homebridge-knxwith the path to the homebridge-knx installation.
Since homebridge-knx is not an Apple-certified HomeKit device some functions are limited:
This is something completely new.
A lot of changes at once
Without using a special handler (add-in) for the service, homebridge-knx assumes the following:
|HomeKit type||KNX addresses DPT|
Devices instead of accessories:
Changed capitalization (harmonized)!
See the complete Doc!.
Add-in (aka handlers) can change the default behavior. See the article
The new (well, 1/2016) API of homebridge allows homebridge to cache the accessories for platforms that can add or remove accessories during runtime. As a next step in evolution, homebridge-knx already connects to that API.
Allow homebridge-knx to start the webserver by adding
"AllowWebserver":true, at the beginning of your knx_config.json!
As a consequence remain devices, that homebridge-knx does not reconnnect to at start-up, stale and unreachable in HomeKit. To remove those shadows from HomeKit, use the little web server at
Clicking on the
delete from cache link will only remove the devices from the current homebridge instance and their cache, not from the knx_config.json, that means they will be rediscovered upon next startup as new device in the default room!
This is for debugging of your knx_config.json only. If you need homebridge to restart, you can use the setting
"AllowKillHomebridge":true in your knx_config.json (right on top where the knxd properties are).
You'll get a new link at the bottom of the page at
<your-homebridge>:18081/list that will homebridge-knx to throw an exception ("Committed_Suicide") which then causes homebridge to fail.
You should remove this setting after completing your knx_config.json for security reasons!