Release 1.9.2

Fixed

• Fixed a bug introduced in [1.9.1] that caused several types of devices to stop working, due to a coding error. (see #535 for more details)

Release 1.9.1

⚠️ This release is broken. Do not use!

Fixed

• Added additional checks to prevent certain errors from occuring during creation of a service handler. (see #443)
• Removed some default values from config.schema.json to prevent certain illegal configurations from being created by accident.

Release 1.9.0

Added

• Some converters now have some additional configuration options which allows you to select an alternative implementation. (see
  #458 and related issues)
  • switch can be configured as a switch (default) or outlet
  • occupancy can be configured as occupancy (default) or motion
• device_temperature is now exposed as a temperature sensor. Due to a change in Zigbee2MQTT, you might need to update your Homebridge configuration to exclude device_temperature if you previously excluded temperature for some devices. (see #456)

Changed

• Refactored basic_sensor.ts as the file was getting way too huge. This should not change any behavior.

Release 1.8.0

Added

• It is now possible to include globally excluded properties for specific devices by using included_keys in the device configuration. (see #406)

Changed

• Support for Zigbee2MQTT Groups is now enabled by default. The experimental option GROUPS is therefore removed. (see #277)

Notes

• When using Homebridge v1.4.0 or newer, it is currently recommended to turn off state caching in Zigbee2MQTT (put cache_state: false in the configuration). See issue #383 for more information.

Release 1.7.0

Changed

• Ignore exclude: false if it is part of the defaults in the plugin configuration, as it may conflict with
  exclude_grouped_devices (also see #277)

Fixed

• Remove stale accessories when an updated group list is received.
• When determining the exposes information for a group, the endpoint specific information is removed. This should allow devices
  with multiple endpoints to be grouped as well.

Release 1.7.0-rc.1

Added

• Exposes information for an accessory (device or group) can be overridden via the JSON configuration, using the exposes key in the device configuration. This is not part of the configuration UI and uses the same exposes structure as Zigbee2MQTT.
• ⚠️ Experimental features: Starting from this release, features/changes can be introduced as experimental.
  This means that you have to enable these features/changes explicitly in your configuration and you must be aware
  that things might break. The main reason for adding this, is so that users can try out changes/features that
  are still being worked on and provide feedback based on their experiences. Please refer to the
  documentation on plugin configuration for more information.
• Experimental GROUPS:
  • Adds accessories for all the groups for which it can determine valid exposes information.
  • Configuration option to exclude all devices that are part of a group (exclude_grouped_devices, default: false).

Changed

• Experimental COLOR_MODE:
  • light: filter properties in state update based on color_mode, if provided. (see #208)
  • light: set Hue/Saturation based on Color Temperature (if color_mode is also received), to slightly improve the UX. Unfortunately the translation is far from perfect at the moment. (see #208)

Fixed

• Bug in exposesAreEqual causing differences in entries with features not to be recognized.

Release 1.6.2

Fixed

• Only log Zigbee2MQTT version when it is changed (or its the first discovery). (fixes #322)
• Air Quality sensor with a PM2.5 sensor were incorrectly exposed as a PM10 sensor in HomeKit.

Release 1.6.1

Fixed

• Removed unnecessary code from climate service.
• Polling mechanism for cover improved. In past releases the plugin could stop requesting updates too early. (see #292)

Removed

• This plugin is no longer tested against Node.js v10, as this version is no longer supported by the community.

Release 1.6.0

Added

• Vibration sensors are now supported and exposed as Motion sensors.
• Presence sensors are now supported and exposed as Occupancy sensors.

Release 1.5.0

Added

• Support for Air Quality Sensors (voc, pm10, pm25). (see #241)