Skip to content

Releases: itavero/homebridge-z2m

Release 1.3.0

20 Jun 15:53
Compare
Choose a tag to compare

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

14 May 18:47
Compare
Choose a tag to compare

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

08 Mar 13:56
Compare
Choose a tag to compare

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

07 Mar 19:26
Compare
Choose a tag to compare
Pre-release

Pre-release to verify the changes for #104

Release 1.1.2

03 Mar 21:06
Compare
Choose a tag to compare

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

09 Feb 18:35
Compare
Choose a tag to compare

Fixed

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

Release 1.1.0

07 Feb 18:06
Compare
Choose a tag to compare

Changed

  • Improved config.schema.json to improve the plugin configuration screen a bit.

Most important changes since v0.0.10

  • Requires Zigbee2MQTT v1.17.0 or newer
  • Uses device information provided by new API in Zigbee2MQTT, so all supported devices should work immediately.
  • Added support for remote controls (action) and thermostats / radiator valves (climate).
  • 鈿狅笍 IMPORTANT: Because of this major change, it might be that you have to reconfigure some of your accessories in your HomeKit setup, if you are coming from v0.0.10 or earlier, as names/identifiers of certain services might have changed. This should be a one time action only, because of this new major version.

Release 1.1.0-beta.4

07 Feb 08:39
Compare
Choose a tag to compare
Release 1.1.0-beta.4 Pre-release
Pre-release

Fixed

  • Temperature sensors showed up as unavailable if the temperature dropped below 0掳C, because the default range in HomeKit is 0 to 100掳C (see #49).

Release 1.1.0-beta.3

30 Jan 16:58
Compare
Choose a tag to compare
Release 1.1.0-beta.3 Pre-release
Pre-release

Fixed

  • LockCurrentState wasn't updated because the monitor was not initialized properly. (fix for #46)

Release 1.1.0-beta.2

30 Jan 12:55
Compare
Choose a tag to compare
Release 1.1.0-beta.2 Pre-release
Pre-release

Added

  • Device documentation is now available on the website and generated based on information from the zigbee-herdsman-converters package,
    which is also used by Zigbee2MQTT.
  • Support for climate devices added (like thermostats and TRVs). (see #40)

Changed

  • Removed unhandled exceptions to prevent Homebridge from crashing. If the plugin does not work as expected, please investigate the
    Homebridge logs up on startup to see if there is anything wrong with your plugin configuration or any of the dependencies.