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)

Release 1.4.0

Added

• The plugin will now log an error if the output format of Zigbee2MQTT (experimental.output) appears to have been configured incorrectly.
• Support for cover devices that only expose tilt and no position. (see #254)

Changed

• Take over numeric range for "passthrough" characteristics, if provided by Zigbee2MQTT.
  Set minimum value for Ambient Light Level to 0, if range is not provided. (see #235)
• Remove (top level) items with an undefined/null value from state updates.
  This should prevent the warnings mentioned in #234.

Release 1.3.0

Added

• Support for horizontal tilt of a cover (see #147)

Changed

For cover devices the following changes/fixes are in this release:

• Update target position, when the state is assumed to be "stopped", to improve Home.app UX. (see #189)
• Only request position when it is actually "gettable" and we did not receive an update recently (which should normally happen if the device supports reporting).
• Changed how the PositionState is updated based on the received positions. No longer try to interpret the direction (HomeKit does this automatically so it seems).

Release 1.2.0

Added

• Default device options can now be set using the defaults key in the plugin configuration.
• Add plugin option mqtt.disable_qos to force the QoS Level to 0 (best effort) for published messages. This might be needed
  when using certain (cloud) MQTT brokers. (see #150)

Release 1.1.3

Fixed

• Names of services are correctly updated when the friendly_name from Zigbee2MQTT has been updated. For the updated names to show up in the
  Home app, it might be necessary to restart Homebridge. (see #76)
• When a new list of devices is published to zigbee2mqtt/bridge/devices, only the changed accessories will be updated, instead of all of them.
  (Wrong default value for force_update argument of updateDeviceInformation has been corrected.))

Release 1.1.3 - PR #104 Verification

Pre-release to verify the changes for #104

Release 1.1.2

Fixed

• Set range for Color Temperature characteristic of Lightbulb to improve control experience. (see #88)

Changed

• Improved logging when handling a (potential) device update fails. (PR #78)
• Ignore empty device updates. (PR #78)

Release 1.1.1

Fixed

• Color change of lights using color_hs was not sent correctly. (fix for #57)