Zigbee2MQTT allows you to temporarily disable devices

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

A new Zigbee2MQTT release might have come just in time for those that were using the application to control their Christmas lights: the ability to temporarily disable devices. As suggested, this functionality allows you to disable your smart Christmas tree lights during the rest of the year, without Zigbee2MQTT yelling at you because they are offline.

There are two ways to disable a device: by editing the configuration.yaml file or using the dashboard. I would definitely recommend the latter, as it lets you easily see which devices are disabled. To disable a Zigbee device, be it a light, switch, or controller, you simply select it, and enter the settings. There, you will see a new checkbox that allows you to do so.

A screenshot of the Zigbee2MQTT dashboard, showing a checkbox to disable a device.

Once disabled, the device will still show up in your Zigbee2MQTT dashboard, but you will not be warned about it being offline any more. This functionality should also clean up your MQTT messages and save a few resources, as Zigbee2MQTT won't be attempting to reach it until it's enabled again. Once you power on the device again, it can be enabled.

A screenshot of the Zigbee2MQTT dashboard showing a disabled device.

Access the Zigbee2MQTT dashboard over SSL

Another change that came with Zigbee2MQTT version 1.29.0 is the ability to use HTTPS for the dashboard. If you were to have the dashboard publicly facing, this should be practical. How this is accomplished is detailed in the documentation.

Be warned that this setting is categorized as advanced for good reason. If you do not know what you are doing, I do under no circumstances recommend exposing your Zigbee2MQTT dashboard to the internet. If the wrong person can access it, they could wreak havoc.

Over-the-updates for new devices

One downside of using Zigbee2MQTT over a device's official hub, is that firmware updates might not be available, or only come at a later date. This is due to many packages having to be intercepted and hosted on GitHub, as not every vendor makes them easily accessible. With every Zigbee2MQTT release, over-the-updates (OTA) are enabled for new devices, and version 1.29.0 includes an extensive list:

Additionally, a fix is provided for OTA updates failing to download. This is an issue that was plaguing some user for a long period, and the fix has hopefully put a smile on their faces for the new year.

The easiest way to check for, and apply, firmware upgrades for your Zigbee devices is by using the Zigbee2MQTT dashboard. The application will automatically find devices that support OTA updates, making it a very hands-off process.

The smalles Zigbee2MQTT Docker yet

The size of the Zigbee2MQTT Docker container has been cut in half. This was achieved by changing from node-alpine images to alpine images. This change makes Zigbee2MQTT 1.29.0 the smallest Docker image ever released. While the ~50 MB savings likely won't make a noticeable difference, it is good to know that unnecessary bulk is being removed.

Zigbee devices now compatible with Zigbee2MQTT

This release includes support for 60 new devices. Below is a small selection, while the full list can be seen in the release notes.

Leave a comment

Share to...