Skip to content

Releases: itavero/homebridge-z2m

Release 1.11.0-beta.9

05 Jan 22:21
Compare
Choose a tag to compare
Release 1.11.0-beta.9 Pre-release
Pre-release

Changed

  • Lights: color_mode is now always used (no longer an experimental flag; also see #208)

Fixed

  • Minor changes to be compatible with the upcoming Homebridge v2 release, among others:
    • In most services where the (numeric) range of a characteristic is limited, the value is now set correctly before doing so, to prevent warnings from HAP-NodeJS.
    • Sanitize accessory names so they only contain alphanumeric, space, and apostrophe characters, and start with an alphanumeric character.

Release 1.11.0-beta.8

04 Jan 22:57
Compare
Choose a tag to compare
Release 1.11.0-beta.8 Pre-release
Pre-release

Changed

  • For numeric characteristics that have a range set, the range is automatically updated if an out of range value is received from Zigbee2MQTT.

Fixed

  • Processing JSON availability payload should not result in a TypeError anymore.

Release 1.11.0-beta.7

04 Jan 21:09
Compare
Choose a tag to compare
Release 1.11.0-beta.7 Pre-release
Pre-release

Changed

  • Light sensor will now use illuminance property if illuminance_lux is not available. This should fix compatibility with the new major v2 release of Zigbee2MQTT. (see #966)
  • Brightness for a Light is no longer requested by default. This should prevent issues when the light is off.
    Old behavior can be restored using the request_brightness option in the converter-specific configuration.
    (see #882)

Release 1.11.0-beta.6

30 Jun 18:43
Compare
Choose a tag to compare
Release 1.11.0-beta.6 Pre-release
Pre-release

Changed

  • Window Covering now uses motor_state (if provided) to improve the user experience in the Home.app (see #852 / #854)

Release 1.11.0-beta.5

21 May 20:53
Compare
Choose a tag to compare
Release 1.11.0-beta.5 Pre-release
Pre-release

Fixed

  • Overlooked an supported check in the previous version. This is now also removed, so devices not officially supported by Zigbee2MQTT can now be used.

Release 1.11.0-beta.4

21 May 20:33
Compare
Choose a tag to compare
Release 1.11.0-beta.4 Pre-release
Pre-release

Changed

  • Process devices not yet supported by Zigbee2MQTT if they provide exposes information. This should allow automatically detected features to already be exposed.

Fixed

  • Non-zero brightness levels below 1% are now rounded up to 1%. (see #673)

Release 1.11.0-beta.3

04 Jan 19:40
Compare
Choose a tag to compare
Release 1.11.0-beta.3 Pre-release
Pre-release

Changed

  • Drop support for unsupported Node.js version. Now only testing against v18 and v20 (current LTS releases).
  • Updated several dependencies, including mqtt.

Fixed

  • Compatibility with Zigbee2MQTT v1.35.0 fixed (see fixes in v1.9.3-rc.0)

Release 1.9.3

03 Jan 18:57
Compare
Choose a tag to compare

Fixed

  • Compatibility with Zigbee2MQTT v1.35.0 fixed (see fixes in v1.9.3-rc.0)

Release 1.9.3-rc.0

02 Jan 20:04
Compare
Choose a tag to compare
Release 1.9.3-rc.0 Pre-release
Pre-release

Fixed

  • Type checks on Z2M models now explicitly check that the input is not null or undefined, to prevent crashes when we get unexpected data. (see #794)
  • When creating or updating an accessory, previously it was only checked if the device definition was not undefined. Now we check if it seems to be a valid device definition. (see #794)

Release 1.11.0-beta.2

16 Jan 16:24
Compare
Choose a tag to compare
Release 1.11.0-beta.2 Pre-release
Pre-release

Added

  • Support for Carbon Dioxide (co2) sensors added. (see #609)

Changed

  • Moved the Availability feature behind an experimental feature flag (AVAILABILITY), as it is not working reliably yet. (see #593
  • Added additional options for Adaptive Lighting, to have it only update the color temperature when the light is on and to have it send a transition when updating the color temperature. These options are not yet available via the config user interface. (see #590)