hassio-zigbee2mqtt
hassio-zigbee2mqtt copied to clipboard
Addon 45df7312_zigbee2mqtt does not exist in the store
Description of the issue
I just wanted to install it and it has disappeared... Only Edge and Proxy are still available
Addon version
2.0.0-3
Platform
core-2025.1.0
Logs of the issue (if applicable)
No response
Same here. Want to update from 2.0.0-1 to 2.0.0-2 because of the adapter issue, but the addon is not in the store. Proxy and edge version is available. Of course I have the repository added.
I have exactly the same problem
The comma on line 7 of the config file is the issue. I just found out using the supervisor logs.
Same here.
Accidentally killed my Zigbee2Mqtt Instance because HomeAssistant asked to do so, after the supervisor figured out it was removed.
There is already a pull request made to fix it. It has even been approved, so when someone merges it, it will be live.
Wow, thanks to the team - amazing time2market
Same boat here,
Reinstalling HA. After adding the repository couldn't find zigbee2qmtt, while edge and proxy are still there.
OMG :(
Same thing here, Repair issue: Add-on Zigbee2MQTT has been removed from the repository it was installed from. and Addon 45df7312_zigbee2mqtt does not exist in the store
Heh, I commented on the https://github.com/Koenkk/zigbee2mqtt/issues/25464 regarding this :) Who can merge https://github.com/zigbee2mqtt/hassio-zigbee2mqtt/pull/694 please?
There is already a pull request made to fix it. It has even been approved, so when someone merges it, it will be live.
without changes
idem here
I also accidentally removed the add-on because Home Assistant Supervisor was asking me to do it. Did I lose all the devices, and will I have to repair them again? I'm panicking a bit because I had 100+ devices connected.
I also accidentally removed the add-on because Home Assistant Supervisor was asking me to do it. Did I lose all the devices, and will I have to repair them again? I'm panicking a bit because I had 100+ devices connected.
Same here!! Nothing is working right now! Lights, thermostats, sensors... can someone with the knowledge inform us how to get back without having to redo it all.
I also accidentally removed the add-on because Home Assistant Supervisor was asking me to do it. Did I lose all the devices, and will I have to repair them again? I'm panicking a bit because I had 100+ devices connected.
Same here!! Nothing is working right now! Lights, thermostats, sensors... can someone with the knowledge inform us how to get back without having to redo it all.
Restore from backup, this should get you back to the state prior to removing the add-on. Then wait for the merge to update Z2M.
Same here. Everything gone. Unforrunatly no Backup
My backups have already been moved off the system and HA is crashing (websocket error) when I try to upload it back.
Can I force the update adding the correct url and version manually?
I just inadvertently deleted my entire add on because of this. Yikes. 20+ devices to re-add.
Follow-up: I'm able to restore from a Proxmox backup and more or less get back to before this morning. I did add five devices today; what are the chances? Easier than reconfiguring everything. HA seems to have lost some memory on the restore and I have a bunch of custom settings I need to get right from memory, but that's unrelated.
Crazy how destructive the default button was on Home Assistant without thinking.
If you need ASAP Z2M Create a fork or use mine https://github.com/Travis90x/hassio-zigbee2mqtt (correct zigbee2mqtt/config.json line 7 -> "2.0.0-1") add digital archive in Add-on repo, refresh the page, Zigbee2mqtt re-appear install it. (edge & proxy appear twice) Copy configuration from Official Zigbee2mqtt , paste in the "forked", start it. Open the web interface from forked Z2m (in the left bar you can find the official).
When it will be ok, backup configuration of the forked, stop it and uninstall, so refresh update in addon e install the official.
Well. Dang... What a high risk button that Submit button was!
Fortunately, the auto backup from a few days ago saved me the hassle of setting everything back up again when the official fix is rolled out - phew.
@Travis90x
Thanks for the fork.
With respect to the process (I ve added numbers to each step):
- add digital archive in Add-on repo, refresh the page, Zigbee2mqtt re-appear install it. (edge & proxy appear twice)
- Copy configuration from Official Zigbee2mqtt , paste in the "forked", start it.
- Open the web interface from forked Z2m (in the left bar you can find the official).
Step 2: Im not sure which file and content apply here. in order to get the config back: would restoring from a good backup work? its can be easier than manual steps.
Do you think that would work?
I just inadvertently deleted my entire add on because of this. Yikes. 20+ devices to re-add.
When the addon is available on the store again, you can restore from the z2m folder..
Same here, waited a couple hours after the update was release and then updated. I saw the message about addon no longer in the repository, then clicked Submit. Addon was gone. Luckily, I made a backup before updating HACS. Restored everything, and now its back. Thank you for backups.
Same here - for anybody interested, I was afraid that HASS will helpfully remove it for me, you know just to be kind, and decided to uninstall the stock one and use "edge" in it's place while this stuff gets resolved - and it works.
Sadly it looks like the dev doesnt check his work before uploading and publishing it. I know this was just a typo but the 2.0.0-1 Update broke config for so many users, wouldnt be that Hard to inform the User what needs to be done before updating the addon.
However, it would also be great - to inform Home Assistant about this ‘weak point’ and also somewhat insecure method of ‘If repo not available - delete without confirmation prompt?’ and perhaps choose a secure method. Just a notification without a direct request to delete would be better!
However, it would also be great - to inform Home Assistant about this ‘weak point’ and also somewhat insecure method of ‘If repo not available - delete without confirmation prompt?’ and perhaps choose a secure method. Just a notification without a direct request to delete would be better!
But there is a confirmation prompt already?
It's because people just can't resist clicking without reading first, and then they have to deal with the consequences.
For those who killed their stable version, I moved over to the Z2M Edge version and just had to restore the MQTT en Adapter settings. Database en all devices configurations were still there and everything is up an drunning. Awaiting the fix for the stable version to move back the same way.
I noticed this morning, when the update/upgrade to 2.0.x disappeared. When checking the changelog it says the add-on no longer exists. Now this all echoes what has been said before, I just hope that there will be a proper upgrade path from 1.42 to 2.0.x