WARNING
homebridge-hue v0.8.x will break your existing HomeKit setup: HomeKit will no longer recognise the accessories and services as the ones previously exposed by pre-v0.8 versions of homebridge-hue. This will cause the accessories and services to be dropped from any HomeKit room, group, scene, and automation. Effectively, you'll have to redo you HomeKit setup. See #299 for more info.
Enhancements:
- On discovery, homebridge-hue fist collects the resources per device in a new HueAccessory object, before exposing the services related to each resource;
- Only expose one Label Index service per accessory;
- Add history for ZHAConsumption and ZHAPower sensors, with consumption characteristics added to lightbulb or outlet service (see #277);
- Plugs are now exposed as outlets; on/off lights are now exposed as lights; groups are now always exposed as lights (even a group of only plugs);
- No longer need to whitelist devices with multiple endpoints of the same type (see #198);
- Store fakegato history files in
~/.homebridge/accessories(or inaccessoriesunder the-Udirectory). Files are now namedhistory_id.json, where id is the new serial number (see #298)
Breaking Changes:
- For ZigBee devices, the accessory serial number is now based on mac address (with colons removed and in uppercase). For bridge/gateway based devices, the accessory serial number is the bridge ID (which was already based on the mac address with colons removed and in uppercase), followed by a dash (
-) and the sensor ID (CLIP sensors), orGand the group ID (for groups). The accessory UUID (by which HomeKit recognises the accessory) is based on this new serial number; - By default use a subtype to each service (except device-level services: Accessory Information, Battery, History and Label Index), not just for the services of whitelisted devices with multiple light resources.