Breaking changes in v0.8, see: https://github.com/ebaauw/homebridge-hue/issues/299.
Copyright © 2016-2018 Erik Baauw. All rights reserved.
This homebridge plugin exposes ZigBee lights, plugs, sensors, and switches connected to (1) a Philips Hue bridge or (2) a dresden elektronik deCONZ gateway to Apple's HomeKit. It provides the following features:
Please see the WiKi for a detailed description of homebridge-hue.
To interact with HomeKit, you need Siri or a HomeKit app on an iPhone, Apple Watch, iPad, iPod Touch, or Apple TV (4th generation or later). I recommend to use the latest released versions of iOS, watchOS, and tvOS.
Please note that Siri and even Apple's Home app still provide only limited HomeKit support. To use the full features of homebridge-hue, you might want to check out some other HomeKit apps, like Elgato's Eve app (free) or Matthias Hochgatterer's Home app (paid).
For HomeKit automation, you need to setup an Apple TV (4th generation or later), HomePod, or iPad as home hub.
You need a Philips Hue bridge or deCONZ gateway to connect homebridge-hue to your ZigBee lights, switches, and sensors. I recommend using the latest Hue bridge firmware, with API v1.22.0 (v2 bridge) or v1.16.0 (v1 bridge) or higher, and the latest deCONZ beta, v2.05.00 or higher.
You need a server to run homebridge. This can be anything running Node.js: from a Raspberry Pi, a NAS system, or an always-on PC running Linux, macOS, or Windows. See the homebridge Wiki for details. I run deCONZ and homebridge-hue together on a Raspberry Pi 3 model B, with a RaspBee add-on board.
I recommend using wired Ethernet to connect the server running homebridge, the Hue bridge, and the AppleTV.
The homebridge-hue plugin obviously needs homebridge, which, in turn needs Node.js. I've followed these steps to set it up on my macOS server:
/usr/local/binis in your
npm, and, later,
homebridgeinstall there. On a Raspberry Pi, these install to
sudo npm -g update npm@latest;
sudo npm -g install homebridge --unsafe-perm. Follow the instructions on GitHub to create a
~/.homebridge, as described;
sudo npm -g install homebridge-hue;
~/.homebridge/config.jsonand add the
Hueplatform provided by homebridge-hue, see Configuration;
config.jsonto include these, see Configuration.
Once homebridge is up and running with the homebridge-hue plugin, you might want to daemonise it and start it automatically on login or system boot. See the homebridge Wiki for more info how to do that on MacOS or on a Raspberry Pi.
sudo npm -g update doesn't always seem to work. To update homebridge-hue, simply issue another
sudo npm -g install homebridge-hue@latest. Please check the release notes before updating homebridge-hue. Note that a change to the minor version typically indicates that you need to review/redo your HomeKit configuration. Due to changes in the mapping how Hue bridge resources are exposed, HomeKit might treat them as new accessories, services, and/or characteristics, losing any assignment to HomeKit rooms, scenes, actions, and triggers. To revert to a previous version, specify the version when installing homebridge-hue, as in:
sudo npm install -g firstname.lastname@example.org.
config.json you need to specify homebridge-hue as a platform plugin. Furthermore, you need to specify what you want to expose to HomeKit, see the examples below. See the WiKi for a complete reference of the
config.json settings used by homebridge-hue.
The example below is a typical configuration for a v2 (square) bridge, which already exposes the Philips Hue lights, Hue motion sensors, Hue dimmer switches, and Hue taps to HomeKit. With this configuration, homebridge-hue exposes the non-Philips lights.
The example below is a typical configuration for a v2 (square) bridge where the native HomeKit feature for sensors isn't used. With this configuration, homebridge-hue exposes the non-Philips lights and all sensor resources, except those created by the Hue app for Home & Away routines.
For finer-grained control of what resources homebridge-hue exposes to HomeKit, create resourcelinks on the bridge / gateway for whitelists or blacklists. The
name of the resourcelink needs to be
description indicates the type of list:
"blacklist". Whitelists take precedence over blacklists. Both whitelists and blacklists take precedence over the settings in
For example, if you have a chandelier with three bulbs, you might want to expose this as a group instead of as three individual lights, by creating the following resourcelinks:
If you run into homebridge startup issues, please run a separate instance of homebridge with only the homebridge-hue plugin enabled in
config.json. This way, you can determine whether the issue is related to the homebridge-hue plugin itself, or to the interaction of multiple homebridge plugins in your setup. You can start this separate instance of homebridge on a different system, as a different user, or from a different user directory (specified by the
-U flag). Make sure to use a different homebridge
username, and (if running on the same system)
port in the
config.json for each instance.
The homebridge-hue plugin outputs an info message for each HomeKit characteristic value it sets and for each HomeKit characteristic value change notification it receives. When homebridge is started with
-D, homebridge-hue outputs a debug message for each request it makes to the bridge / gateway, for each state change it detects while polling the bridge / gateway, and for each push notification it receives from the deCONZ gateway. Additionally, it issues a debug message for each bridge / gateway resource it detects.
To capture these messages into a log file do the following:
homebridge -D 2>&1 | tee homebridge.log
Hit interrupt (ctrl-C) to stop homebridge.
ExecStartline of the service definition file, typically
/etc/systemd/system/homebridge.service. Then reload by
sudo systemctl daemon-reload sudo systemctl restart homebridge
To capture the log file, issue:
sudo journalctl -au homebridge > homebridge.log
Compress the log file by issuing
To aid troubleshooting, on startup, homebridge-hue dumps its environment, including its
config.json settings and the full state of all bridges / gateways into a gzipped json file,
homebridge-hue.json.gz. IP addresses, and bridge / gateway usernames are masked. This file is created in the user directory,
~/.homebridge by default.
If you need help, please open an issue on GitHub. Please attach a copy of
homebridge.log.gz (see Debug Log File) and of
homebridge-hue.json.gz (see Debug Dump File). Please do not copy/paste large amounts of logging.
For questions, you can also post a message to the #homebridge-hue channel of the homebridge workspace on Slack.
The homebridge-hue plugin is a hobby project of mine, provided as-is, with no warranty whatsoever. I've been running it successfully at my home for years, but your mileage might vary. Please report any issues on GitHub.
Homebridge is a great platform, but not really intended for consumers, as it requires command-line interaction.
HomeKit is still relatively new, and Apple's Home app provides only limited support. You might want to check out some other HomeKit apps, like Elgato's Eve app (free), Matthias Hochgatterer's Home app (paid), or, if you use
Xcode, Apple's HMCatalog example app.
The HomeKit terminology needs some getting used to. A accessory more or less corresponds to a physical device, accessible from your iOS device over WiFi or Bluetooth. A bridge (like homebridge) is an accessory that provides access to other, bridged, accessories. An accessory might provide multiple services. Each service corresponds to a virtual device (like a lightbulb, switch, motion sensor, ..., but also: a programmable switch button, accessory information, battery status). Siri interacts with services, not with accessories. A service contains one or more characteristics. A characteristic is like a service attribute, which might be read or written by HomeKit apps. You might want to checkout Apple's HomeKit Accessory Simulator, which is distributed as an additional tool for
HomeKit only supports 99 bridged accessories per HomeKit bridge (i.e. homebridge, not the Hue bridge). When homebridge exposes more accessories, HomeKit refuses to pair with homebridge or it blocks homebridge if it was paired already. While homebridge-hue checks that it doesn't expose more than 99 accessories itself, it is unaware of any accessories exposed by other homebridge plugins. As a workaround to overcome this limit, you can run multiple instances of homebridge with different plugins and/or different homebridge-hue settings, using the
-U flag to specify a different directory with a different
config.json for each instance. Make sure to use a different homebridge
port for each instance.
Internally, HomeKit identifies accessories by UUID. For Zigbee devices (lights, sensors, switches), homebridge-hue bases this UUID on the Zigbee mac address. For non-Zigbee resources (groups, schedules, CLIP sensors), the UUID is based on the bridge / gateway ID and resource path (e.g.
/sensors/1). By not using the resource name (e.g.
Daylight), homebridge-hue can deal with duplicate names. In addition, HomeKit will still recognise the accessory after the resource name has changed on the bridge / gateway, remembering which HomeKit room, groups, scenes, actions, and triggers it belongs to. However, when a non-Zigbee bridge / gateway resource is deleted and then re-created, resulting in a different resource path, HomeKit will treat it as a new accessory, and you will need to re-configure HomeKit.