Big Breaking Changes @ Zigbee2MQTT

[MickLesk]

Hi,

there are a massive breaking change into zigbee2mqtt. I work on an new Script for this, but at first you can do following:

Checkout:
Koenkk/zigbee2mqtt#24198

1.) Install pnpm

npm install -g pnpm

2.) Do an Update of your config

systemctl stop zigbee2mqtt
mkdir -p /opt/z2m_backup
cp -r /opt/zigbee2mqtt/data/* /opt/z2m_backup

3.) Change Configuration of configuration yaml

nano /opt/zigbee2mqtt/data/configuration.yaml

add here in the right sections:

advanced:
  homeassistant_legacy_entity_attributes: false
  homeassistant_legacy_triggers: false
  legacy_api: false
  legacy_availability_payload: false
device_options:
  legacy: false

4.) Check if your Adapter is correct configured (i had the same issue)

nano /opt/zigbee2mqtt/data/configuration.yaml

check this part:

serial:
  port: /dev/ttyACM0
  adapter: zstack # <-- Add this line

ive used zstack, you can check it here: Koenkk/zigbee2mqtt#24364

5.) go into main path and enter "./update.sh"

cd /opt/zigbee2mqtt
./update.sh

6.) if all is correctly deployed, you can do an testrun

cd /opt/zigbee2mqtt && pnpm start

=> if it works, fine, update done

7.) Edit Service for Zigbee2MQTT

nano /etc/systemd/system/zigbee2mqtt.service

change "/usr/bin/npm start" to "/usr/bin/pnpm start" In ExecStart and start the service

systemctl daemon-reload
systemctl start zigbee2mqtt

[BjornWill]

These steps don't seem to be for the Alpine variant. What will be the upgrade path for those instances?

[dsiebel]

I think it means to run the following script twice

Ah, that could be it, thanks. The thought hasn't crossed my mind to run it multiple times.
I expected it to just work the first time 😅

Looking at the output you posted, It seems you were running an outdated version of the update script. The current version should work for you now.

[gomble]

Alpine has a other package. Thats not an git package

What does that mean?
How to update on Alpine is there some tutorial?

[dsiebel]

Via the Alpine package manager apk add --upgrade zigbee2mqtt.
But you probably won't get the latest version (v2.0.0) from the Alpine package repository.

[MickLesk]

yep its an alpine thing, havent try it hours

[gomble]

Its not available yet for alpine

[hacscred]

Your instructions are partially incorrect. If you have ever programmed a computer you should know that if you say something, you should make it 100% correct.

I won't correct you, because I don't believe in helping people that don't know the difference between correct and incorrect.

[MickLesk]

Correct or incorrect is in the eye of the beholder, it all depends on the version of the predecessor, I used the Dev Branch for a long time, so it worked the same for me. Also with my test LXC. A lot depends on which previous version, what the status of the previous version is, which OS is used and which version of it, privileged or unprivileged, etc.

But next time I can also link you for a “correct” guide.gerversion on it, I used the Dev Branch for a long time, so it worked the same for me. Also with my test LXC. There is a lot involved, which previous version, what are the statuses of the predecessor, which OS is used and which version of it, privileged or unprivileged etc.

But next time I can also link you to a “correct” guide.

[hacscred]

So, do input validation. If your instructions only work for certain inputs, you should just check those and not imply that your instructions would apply.

A neutral title for what you did can even be created by ChatGPT.

Correctness isn't a matter of opinion, something you would know, if you had an academic background. If, you did graduate from some university, I recommend you ask for a refund.

It would be better to just introduce yourself as someone without any proven skills at the beginning of whatever you write such that nobody follows your advice in the future.

[NAVspecialist]

Thanks @MickLesk - I simply could not update from 1.42 but your suggestion worked flawlessly. Much Appreciated!

Thanks mate.

[luck3rhoch3]

Had to do a
"git stash" after changing the configuration.yaml, otherwise the update won't install.

And for me it's
/usr/local/bin/pnpm
otherwise it won't work as service.

[photomoose]

One thing I did notice after following this procedure was that the global helper script update command did not work any more. To fix this issue, I had to modify the contents of the /usr/bin/update from:

bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/zigbee2mqtt.sh)"

to:

bash -c "$(wget -qLO - https://raw.githubusercontent.com/community-scripts/ProxmoxVE/refs/heads/main/ct/zigbee2mqtt.sh)"

Now when running update from inside the container, it will pull down and execute the correct script. (Note that is this the helper script command from this repo, not the update.sh file that exists in the Z2M repo).

[MickLesk]

Exactly for this topic (General), we have an Script to update all LXC "update" functions

https://community-scripts.github.io/ProxmoxVE/scripts?id=update-repo

[photomoose]

Perfect! Didn't realise that existed. Thanks!

[dmshimself]

Is there a newer version of this guide to assist moving from to 1.42 to V2 of zigbee2mqtt? I've tried to follow this one and hit various road blocks which I'm happy to document, but I wonder if there is another guide I should follow first so I'm not reinventing the wheel?

[MickLesk]

No. There won't be either. It's the same. If you always fail, you should consider setting up a new LXC

[MickLesk]

This Here is an old Guide. The Main Guide is in Changelog in linked breaking Change. Users reported there many ways

[dmshimself]

Many thanks. I found the Main Guide you refer to easy to follow, but like other people I had quite a few issues along the way. I know some of these were addressed in different ways by different people, so I thought I would ask, just to be sure. Thanks for the steer and the reminder of the option of starting with a new one and restoring a backup.

[quax1]

Would it be possible to update the Proxmox VE Helper-Scripts of tteck ? Currently a fresh install ends with error
npm error code EUSAGE
npm error
npm error The npm ci command can only install with an existing package-lock.json or ....

[MickLesk]

No. Use the Repo Here lol

[quax1]

ah thanks, I got it - I used an old direct link ( https://tteck.github.io/Proxmox/ ) and did not notice that the home was changed

[kylepyke]

These directions worked for me coming from 1.42. A couple of notes:

Make sure when you copy the above lines to your configuration.yaml, you don't duplicate any lines that already exist. For example, I already had:

legacy_api: false legacy_availability_payload: false

Make sure your update script is correct, if you used the old tteck script to setup your LXC (see @photomoose's comment here. If you get a git merge error at step 5, your update script is not correct.