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?

[MickLesk]

[dsiebel]

I see.

I'm still having a hard time following what places of documentation you are pointing to and
what "lines" you were referring to or what "Script 1-2" means here:

I also haven't found the dicussion, issue or PR from the screenshot above.
EDIT: looks like your screenshot was from the same discussion as mine (#660) but has changed since it was posted here.

My point was that the mentioned steps 1-8 didn't work, at least not in that order, because of the git conflicts. As was also pointed out by others.
As far as I can tell, this has nothing to do with what is going on in the dev branch.

[photomoose]

I think it means to run the following script twice from within the existing Z2M LXC console:

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

The first execution appears to sort out the upgrade and the second execution confirms that you are running at 2.0.0.

I could be wrong, however!

Note that despite following the steps, if I run the helper script update command (not the Z2M update.sh script), I get the following error:

Shutting down Zigbee2MQTT...
Generating a backup of the configuration...
Checking if any changes were made to package-lock.json...
error: pathspec 'package-lock.json' did not match any file(s) known to git
Failed to check package-lock.json.

[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?