Anyway, there is a fix pending in the repo to remove a erant comma (yes, that’s all) that broke the config files. You can read more here - Unbreak config.json by mundschenk-at · Pull Request #694 · zigbee2mqtt/hassio-zigbee2mqtt · GitHub 71 this is what caused the repo to go AWOL."
See full answer marked as solution.
I updated to 2.0 yesterday from a very recent version. I read the release notes very carefully (or so I thought) and only had to add one extra param (the zstack thing as my dongle wasn’t auto-discovered) and also a couple of lines to disable legacy in the zigbee config (many were already present).
I’ve done multiple restarts of HA since but I’m now suddenly noticing this
Any ideas what I need to do to fix this? Did I miss some obvious step? I’ve tried googling for “Zigbee2MQTT has been removed from the repository it was installed from” and also on these forums but nothing popped up so I’m braving the possibly dumb question…
UPDATE: so looks like possibly the official repository has changed to GitHub - zigbee2mqtt/hassio-zigbee2mqtt: Official Zigbee2MQTT Home Assistant add-on
Does anyone know if it’s possible to change the repository that an addon is associated with “in-place”? Asking because I cannot add this new repository without deleting the old one, but I cannot delete the old one without deleting that addon it seems, which I do not want to do.
I’m sure there must be a way to update its associated repo somehow.
I’m having the exact same issue. Do you have any good links to share in your rabbit hole of trying to figure this out? I have 116 zigbee devices on my current installatin, and lots of automations relying on them lol. I really don’t want to hit that submit button. Let me know if you find a way over or around this strange issue!
For what it’s worth I’m not sure it’s a direct result of an update, at least not in my case, that triggered it. I was getting ready to update, and noticed that I had a few old snapshots in the proxmox VM that my HA runs in, and as usual I deleted them. As part of my update process, I always - 1. reboot HA, 2. Create a manual backup, 3. Create Proxmox snapshot. 4. Update one of the itmes… then rinse and repeat until all updates are done. I’ll come back later and delete snapshots. Either way. I received this error Immediatly after the reboot before any backups, snapshots or updates were applied.
Same issue here. Accidentally hit the submit button
Reverted back to my backup from 2024.12, but somehow that did not restore Zigbee2MQTT (all devices offline). Now going back to my backup from 2025.01, but WTF?!
WTH, Zigbee2MQTT completely removed without any warning, backup-option or anything. Going to move everything to ZHA now. Redo all automations, dashboards etc. Thanks for al the work this is giving me. Sjezus, this is way more than annoying…
I do not know how to fix this for you but this is whats happening:
Its all related to this:
The 2.0.0 was a very breaking change for some people, but people were blindly / automatically updating to it. In order to stop that from happening someone used the facility to mark it as a breaking change so that would not happen.
It looks like that has had the unintended consequence of removing it as a HA addon entirely.
They should have used the breaking changes flag to prevent it from the first 2.0.0 release. HomeAssistant provides the auto update toggle and the means to protect people from auto updating breaking changes. Blaming people for having their stuff broken by using things provided right up front (like the autoupdate toggle is) seems unfair.
