All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
This project is versioned based upon the version of zigbee2mqtt. The versioning X.Y.Z
of the stable release of this add-on will track that of zigbee2mqtt. If there are new releases without upgrades to the zigbee2mqtt version (i.e., changes to the add-on that occur between releases of zigbee2mqtt), an additional number will be added to indicate this (X.Y.Z.A
, where A
indicates a new versioned release).
1.6.0 - 2019-09-11
- Upgrade zigbee2mqtt to 1.6.0
1.5.1.2 - 2019-07-30
- Create
$DATA_PATH
if it does not already exist - Fix default configuration typo (#197)
1.5.1.1 - 2019-07-22
- Adds several configuration items:
advanced.availability_blacklist
ban
whitelist
queue
(along withqueue.delay
andqueue.simultaneously
)mqtt.key
,mqtt.ca
,mqtt.cert
advanced.report
,advanced.homeassistant_discovery_topic
,advanced.homeassistant_status_topic
- Add back
zigbee_shepherd_debug
,zigbee_shepherd_devices
, anddisable_led
- Include default network key in default configuration, as this is used by zigbee2mqtt by default.
1.5.1 - 2019-07-20
- BREAKING CHANGE: restructured configuration to more closely mirror zigbee2mqtt
- upgrade zigbee2mqtt to 1.5.1
1.3.0 - 2019-04-08
- Update zigbee2mqtt to version 1.3.0
- Includes new config option from zigbee2mqtt:
homeassistant_discovery_topic
debounce
(device-specific config)
- Fixes logic bug that prevented configuration from being updated via the Hass.io frontend UI.
1.2.1 - 2019-03-10
- Update zigbee2mqtt to version 1.2.1
- Use Node.js 10 as base docker image
- Includes new config option from zigbee2mqtt:
report
1.1.1 - 2019-02-02
- Update zigbee2mqtt to version 1.1.1
1.0.1.1 - 2019-01-30
- Add
network_key
to options, defaulting to empty list. If left empty, the option will not be passed to zigbee2mqtt. - Update README to reflect requirements for
devices
andnetwork_key
options
1.0.1 - 2019-01-30
- update zigbee2mqtt to version 1.1.0
- Includes new config options from zigbee2mqtt:
soft_reset_timeout
last_seen
elapsed
network_key
devices
(device-specific configuration)
- Includes
overwrite
option, which can be set tofalse
to prevent the add-on from overwriting corresponding fields on startup that are already set in theconfiguration.yaml
file.
1.0.1 - 2018-12-17
- update zigbee2mqtt to version 1.0.1
1.0.0 - 2018-12-17
- update zigbee2mqtt to version 1.0.0
- Includes new or changed options for zigbee2mqtt:
reject_unauthorized
pan_id
channel
0.1.6 - 2018-09-26
- update zigbee2mqtt to version 0.1.6
0.1.5.1 - 2018-09-24
- Fixed bugs related to #53 and #54, regarding
log_directory
setting - Fixed README typo regarding
disable_led
. This option is now calleddisable_led
in accordance with zigbe22mqtt. Although this was changed in 0.1.3.1, README was not updated to reflect that.
0.1.5 - 2018-09-17
- update zigbee2mqtt to version 0.1.5
0.1.3.1 - 2018-09-17
- Includes new or changed options for zigbee2mqtt:
mqtt_client_id
disable_led
(renamed fromserial_disable_led
)cache_state
log_directory
log_level
rtscts
zigbee_shepherd_debug
0.1.3 - 2018-07-31
- Upgrade to version 0.1.3 of
zigbee2mqtt
0.1.2 - 2018-07-31
- Upgrade to version 0.1.2 of
zigbee2mqtt
0.1.1 - 2018-07-29
- Switch the edge and non-edge dockerfiles so they're actually correct. Sigh. This is why you don't write code after 28 hour shifts.
- Download release archives instead of git cloning the specific branch
- Upgrade to version 0.1.1 of
zigbee2mqtt
0.1.0 - 2018-07-16
Version 0.1.0 is the first versioned release of the add-on. The repository actually establishes two add-ons:
zigbee2mqtt
add-on, which will use the first released version of thezigbee2mqtt
library and will update as new versions of that library are releasedzigbee2mqtt-edge
add-on, which will build with the latest commit to thezigbee2mqtt
master branch. Each update to the library will trigger a new add-on image to be built. In effect, this add-on will function the same way that the pre-release version of this add-on did.