Releases: ebaauw/homebridge-hue
v0.5.8
v0.5.7
v0.5.6
Update dependencies:
- node v6.11.0 (or higher v6.x) or v7.10.0 (or higher v7.x) on install - node v8 is incompatible with homebridge-hue (issue #125);
- Bump to homebridge v0.4.21, which no longer creates the (hidden)
BridgingState
service and hopefully allows more accessories before the iCloud sync fails (issue #129).
Note: you need to upgrade to homebridge v0.4.21 (npm -g install homebridge --unsafe-perm
) before upgrading to homebridge-hue v0.5.6. If not, you'll see the following errors when starting homebridge:
[7/2/2017, 10:47:13 AM] ====================
[7/2/2017, 10:47:13 AM] ERROR LOADING PLUGIN homebridge-hue:
[7/2/2017, 10:47:13 AM] Error: Plugin /usr/local/lib/node_modules/homebridge-hue requires a HomeBridge version of ^0.4.21 which does not satisfy the current HomeBridge version of 0.4.20. You may need to upgrade your installation of HomeBridge.
at Plugin.load (/usr/local/lib/node_modules/homebridge/lib/plugin.js:56:11)
at Server.<anonymous> (/usr/local/lib/node_modules/homebridge/lib/server.js:132:14)
at Array.forEach (native)
at Server._loadPlugins (/usr/local/lib/node_modules/homebridge/lib/server.js:128:22)
at new Server (/usr/local/lib/node_modules/homebridge/lib/server.js:51:24)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:26:16)
at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
[7/2/2017, 10:47:13 AM] ====================
[7/2/2017, 10:47:13 AM] ---
[7/2/2017, 10:47:13 AM] Loaded config.json with 0 accessories and 1 platforms.
[7/2/2017, 10:47:13 AM] ---
[7/2/2017, 10:47:13 AM] Loading 1 platforms...
/usr/local/lib/node_modules/homebridge/lib/api.js:122
throw new Error("The requested platform '" + name + "' was not registered by any plugin.");
^
Error: The requested platform 'Hue' was not registered by any plugin.
at API.platform (/usr/local/lib/node_modules/homebridge/lib/api.js:122:13)
at Server._loadPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:284:45)
at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:80:36)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:40:10)
at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
v0.5.0
Now using the standard Color Temperature
characteristic, that Apple silently introduced in iOS 10.3. The iOS built-in Home app now supports setting Colour Temperature on Color Temperature Lights. See issue #121. Also deprecated the ct
setting in config.json.
Note this is a minor release, because any scene or automation containing colour temperature will be broken after updating homebridge-hue.
v1.0.0-0
Initial alpha release using dynamic platform accessories (see issue #4) and homebridge-lib v0.0.2-0.
Install using sudo npm -g install homebridge-hue@alpha
.
Note that this release isn't functional: it doesn't expose any lights, sensors, or other devices connected to a bridge. It does offer the following functionality:
- Discover Philips Hue and deCONZ bridges using their respective portals and UPnP;
- Persist accessories and all relevant settings (incl. username and heartbeat) in
~/.homekit/acccessories/cachedAccessories
; - Restore bridges discovered in a previous session from persistent storage;
- Enable/disable a bridge, including automatic creation and deletion of a bridge username;
- Setting heartrate per bridge;
- Support bridge configuration changes without restarting homebridge:
- Changed name. Unfortunately, the new name is only reflected in HomeKit after homebridge is removed and re-paired;
- Changed ip address;
- Deleted username;
- Cleanup cached accessories from
~/.homekit/acccessories/cachedAccessories
whenHue
platform is not specified inconfig.json
.