Zigbee2MQTT 1.29.0: New Features and How to Use Them

Disclosure: This post contains affiliate links. If you click through and make a purchase, I will earn a commission, at no additional cost to you. Read my full disclosure here.

A new Zigbee2MQTT release introduces the ability to temporarily disable devices. This feature is particularly useful for those who use the application to control seasonal devices, like Christmas tree lights, allowing them to be disabled when not in use without generating offline warnings.

Contents

How to Disable a Device in Zigbee2MQTT

There are two methods to disable a device: editing the configuration.yaml file or using the dashboard. The dashboard method is recommended due to its ease of use and visual feedback. Follow these steps to disable a Zigbee device (e.g., light, switch, or controller):

  1. Open the Zigbee2MQTT dashboard.
  2. Select the device you want to disable.
  3. Enter the device settings.
  4. Check the new checkbox to disable the device.

Once disabled, the device will still appear in your dashboard, but you will no longer receive offline warnings. This can also help clean up your MQTT messages and save resources, as Zigbee2MQTT will not attempt to communicate with the device until it is re-enabled. To re-enable the device, simply power it on and uncheck the box.

The image is a screenshot of a section from the Zigbee2MQTT dashboard. It shows a configuration field labelled “Friendly name*” with the text “bedroom/light/ceiling_lamp” entered. Below this, there is a note stating, “Used in the MQTT topic of a device. By default, this is the device ID.” Two unchecked options are displayed beneath this: “Disabled” and “Retain.”
Zigbee Disable Update 02

Accessing the Zigbee2MQTT Dashboard Over SSL

Version 1.29.0 also introduces the ability to use HTTPS for the Zigbee2MQTT dashboard. This is useful if your dashboard is publicly accessible. Detailed instructions for enabling HTTPS can be found in the Zigbee2MQTT documentation.

Caution: This setting is advanced. Avoid exposing your dashboard to the internet unless you are confident in your ability to secure it. Unauthorized access could lead to significant issues.

Over-the-Air Updates for New Devices

A common limitation of using Zigbee2MQTT instead of a device’s official hub is the delayed availability of firmware updates. These updates often need to be hosted on GitHub, as not all vendors provide them directly. With the help of the community, Zigbee2MQTT has managed to secure a number of updates, which are now available for the following devices:

A fix for OTA updates failing to download is also included, addressing a long-standing issue for some users.

To check for and apply firmware upgrades, use the Zigbee2MQTT dashboard. The application will automatically detect devices that support OTA updates, simplifying the process.

The Smallest Zigbee2MQTT Docker Yet

The size of the Zigbee2MQTT Docker container has been significantly reduced in this release by switching from node-alpine to alpine images. This change makes version 1.29.0 the smallest Docker image released to date, saving around 50 MB of space. A smaller Docker container offers several advantages:

  1. Faster Deployment: Smaller containers can be pulled and started more quickly, reducing downtime during updates or initial setup.
  2. Reduced Resource Usage: With less disk space required, you can optimize storage and potentially run more containers on the same host.
  3. Improved Efficiency: Smaller containers typically have fewer components, which can lead to faster performance and easier management.
  4. Enhanced Security: With fewer dependencies, there is a smaller attack surface, potentially reducing vulnerabilities.

New Device Compatibility

This release also includes support for 60 new devices from IKEA, Tuya, Philips, and other manufacturers. Here is a small selection of what can now be integrated through Zigbee2MQTT:

For a complete list, refer to the release notes.

Summary

To sum up, The latest Zigbee2MQTT release offers several new features and improvements:

These enhancements make Zigbee2MQTT more versatile and user-friendly, helping you manage your smart home devices more effectively.

A portrait photo oif Liam Alexander Colman, the author, creator, and owner of Home Assistant Guide wearing a suit.

About Liam Alexander Colman

is an experienced Home Assistant user who has been utilizing the platform for a variety of projects over an extended period. His journey began with a Raspberry Pi, which quickly grew to three Raspberry Pis and eventually a full-fledged server. Liam's current operating system of choice is Unraid, with Home Assistant comfortably running in a Docker container.
With a deep understanding of the intricacies of Home Assistant, Liam has an impressive setup, consisting of various Zigbee devices, and seamless integrations with existing products such as his Android TV box. For those interested in learning more about Liam's experience with Home Assistant, he shares his insights on how he first started using the platform and his subsequent journey.

Leave a comment

Share to...