Releases: itavero/homebridge-z2m
Releases · itavero/homebridge-z2m
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 exposetilt
and noposition
. (see #254)
Changed
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 to0
(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 forforce_update
argument ofupdateDeviceInformation
has been corrected.))
Release 1.1.3 - PR #104 Verification
Pre-release to verify the changes for #104
Release 1.1.2
Release 1.1.1
Fixed
- Color change of lights using
color_hs
was not sent correctly. (fix for #57)
Release 1.1.0
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
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
Fixed
LockCurrentState
wasn't updated because the monitor was not initialized properly. (fix for #46)