How do I roll back an addon to a previous version

Configuration
1

Zigbee2MQTT 2.0 completely breaks the way switches are integrated into HA, and I no longer have control of any lights without getting my phone out every time.

I need to roll back to the previous version. But there is nothing in the UI to control this, and no --version flag to ha addons update (there should be!)

I can’t find where on the disk the files are for the addon.

How can I go back to a previous version without restoring an entire backup of Home Assistant?

And are there any plans to make this easier? This probably isn’t the first time an addon has made breaking changes that mess things up for HA users, and it certainly won’t be the last…

2

Is there nothing in Settings | System | Backups from the last time Z2M was updated?

3

No it doesn’t you just need to adjust your config. See: Action entity missing for zigbee switches - Zigbee2MQTT - #20 by jdbrookes

Add-ons have never been version controlled. The only way to roll back to a previous version is by restoring a backup of the add-on.

Unfortunately since core-2025.1 the automatic backup when an add-on is updated has been removed. Now you have to find your last full backup and do a partial restore - only select the add-on to restore.

The best option is to fix your z2m and automation configs to work with z2m 2.0.

4

You can turn back on legacy action entities in the UI until you fix it all. The feature is deprecated, but still available as an option for the time being…

This is how I’m telling my users to get over the hump…
🧯 Zigbee2MQTT - Xiaomi Cube Controller - #228 by Sir_Goodenough.

5

Thanks — of course, the Zigbee2MQTT docs still claim that “event entity is experimental and may break in the future.” So this doesn’t sound like a particularly stable solution.

It also doesn’t seem to be editable via the GUI without resorting to YAML — if I select a state trigger with attribute Action, it doesn’t present a list of available actions in the To dropdown, unlike using a device trigger.

Too much of a pain — I did manage to restore from backups so I’m now running 1.14.0 again and everything works. I’ll stick with that until the dust settles.

I don’t suppose there’s a way to mark an addon as “don’t show available updates for this” so I don’t constantly have a badge against Settings nagging me to upgrade?

6

They also say: "This will become the recommended method with 2.0.0. ", which you just updated to.

Change your triggers using sensor.*_action to event.*_action and use the event_type attribute instead of main state in your automations.

The dust has settled. This is the way forward.

There is not.