Add-on Zigbee2MQTT has been removed from the repository it was installed from?

Configuration Zigbee
45

Did you went through the steps I described HERE?

1 Like
46

Thank you!!

2 Likes
47

For me to get it working again, I needed do 1 addition step. Basically I followed Tamsy’s instructions to the letter, but while that I think partially fixed things, the Zigbee2MQTT was not starting successfully. Log showed issue with finding the adaptor for some reason. Adding :

adapter: zstack # <-- Add this line

line to the config as outline at (Z2M 2.0.0: `USB adapter discovery error (No valid USB adapter found)` · Koenkk/zigbee2mqtt · Discussion #24364 · GitHub).

With that and a restart of Z2M, it found my adaptor and all working again with old config and devices. Then I just did a “Reboot System” as outlined above to remove the warning.

I hope this helps someone.

48

“HA → Developer Tools → Restart → Advanced Options → Reboot System”

You’re right. I had to did it like this. The simple “restart after update” didn’t get rid of the notification.

Now I’m good. Thx for your time.

49

:warning: Beware! There are quite a few breaking changes if your system still runs on Z2M version 1.x.

Before doing that update to the latest version 2.0.0 you should definitely read about these breaking changes and adjust your config accordingly before doing the update!

50

There are a few more recommended config lines…

51

I have the same problem

52

Since this morning i also getting the message that the zigbee2mqtt addon is removed from the repository.
Did i miss something and is there another addon?

53

It’s a problem that already have solution.
Please check this: Add-on Zigbee2MQTT has been removed from the repository it was installed from? - #30 by Tamsy

I did it and helped me! Now is working

1 Like
54

I had a backup from 2 days ago and restore it, I don’t understand what is wrong with all things HA update broke a lot of things and now zigbee also. I accidentaly click the submit button. :angry:

55

It cannot be directly related to the update to 2.0, I have the exact same issue and I am still on software version 1.41.0-1.

56

I had same issue this morning. There was a fix in the available update : v.2.0.0-2. You install it, then reboot home assistant.

58

That’s what I did. Didn’t fix.

Edit: I was wrong. Rebooting the actual host (not just HA!) did fix the issue.

59

It’s not directly updated to 2.0 which I did very carefully and without issue. Well it is tangentially related for sure. This happened to me a day after updating to 2.0 successfully

60

The numbers once flowed, now fall to dust,
A vanished thread, once clear, now rust.
No more devices, no more entities,
Our paths diverged, no hand in mine.

I seek in vain through every thread,
Yet silence rules the passing night.
A fleeting contact, lost to time,
A distant echo, once sublime.

Farwell Z2Mqtt

61

Still not working…
I followed all steps @Tamsy suggested, restarted several times using several methods (restart Home Assistant, reboot system, restart the VM, restart the host computer). The repair message is gone, but z2m does not start.
After that bad result, I also looked at the z2m config file, verified that the “adapter: zstack” line was already there, included the “homeassistant_legacy_triggers: false” line, as suggested in other post, but no improvements.
Home Assistant 2024.12.5, SLZB-06P7, z2m 2.0.0-2
z2m log shows:


[17:08:50] INFO: Preparing to start...
[17:08:50] INFO: Socat not enabled
[17:08:51] INFO: Starting Zigbee2MQTT...
node:internal/modules/run_main:91
  const type = getNearestParentPackageJSONType(mainPath);
               ^
Error: Invalid package config /app/package.json.
    at shouldUseESMLoader (node:internal/modules/run_main:91:16)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:163:20)
    at node:internal/main/run_main_module:36:49 {
  code: 'ERR_INVALID_PACKAGE_CONFIG'
}
Node.js v22.11.0

My next step will probably be to restore the old z2m version…
Any suggestions before I restore the backup?

Thanks.

62

This definitely looks like a totally different type of error from the dongle ones.
It seems you may also have node red (perhaps?).

For me, now that they have fixed the config and merged the PR and it’s been picked up by the addon store, the repair message is gone and everything is fine.

You may want to look at the threat on the 2.0 migration and post on there. The reason I created this thread is because I knew it was only tangentially related to the 2.0 changes but it wasn’t caused by an incompatibility or anything else like that. I’m really sorry you are having to deal with this :frowning:

63

Hello, I do apologies in advance if I missed an answer to my question, the topic is very very long :frowning:

In simple answer what should this be changed to in order to update to the MQTT v2.0.0-2

  trigger:
    - platform: state
      entity_id:
        - sensor.button01_action
      to: single
      id: Button1_Single_Press
64

Hi Bobby, don’t think there’s a simple answer to your question unfortunately - there’s a good discussion on this topic here: https://community.home-assistant.io/t/using-the-new-action-events-in-zigbee2mqtt-2-0/

1 Like
65 
triggers:
  - domain: mqtt
    device_id: 7e2b4b7e723b80b8f05f863c93d247db
    type: action
    subtype: single
    trigger: device
    id: single