starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 08:40:11 +03:00
Code Issues 23 Packages Projects Releases 10 Wiki Activity

[PR #1221] [MERGED] [Breaking] Update Zigbee2mqtt to v.2.0.0 (Read PR Description) #2934

New Issue
Closed
opened 2026-02-05 05:21:03 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-05 05:21:03 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/1221
Author: @MickLesk
Created: 1/4/2025
Status: ✅ Merged
Merged: 1/5/2025
Merged by: @MickLesk

Base: main ← Head: zigbee2mqtt_patch

📝 Commits (10+)

📊 Changes

2 files changed (+59 additions, -104 deletions)

View changed files

📝 ct/zigbee2mqtt.sh (+29 -85)
📝 install/zigbee2mqtt-install.sh (+30 -19)

📄 Description

Please read carefully for migration!

Do Step 1-8 and after this execute Script 1-2

For Error-Handling read PR Comments or Linked Issue comments.

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

✍️ Description

https://github.com/community-scripts/ProxmoxVE/discussions/660

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/ember/xxx # <-- Add this line (see following link)

ive used zstack, you can check it here: https://github.com/Koenkk/zigbee2mqtt/discussions/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

8.) Create an App_version.txt for next updates

touch /opt/zigbee2mqtt_version.txt
nano /opt/zigbee2mqtt_version.txt
=> add 1.9.0 in file and save
  1. Run bash (update or bashcall from website) 1-2 Times (Line 2)

Hint:

If you have other problems, have a look at the comments to see if your problem is among them.

An alternative solution would be to create a new LXC and export the data-folder from the old one and import it into the new LXC, but this is only theoretical.

🛠️ Type of Change

Please check the relevant options:

  • Bug fix (non-breaking change that resolves an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change unexpectedly)
  • [] New script (a fully functional and thoroughly tested script or set of scripts)

✅ Prerequisites

The following steps must be completed for the pull request to be considered:

  • Self-review performed (I have reviewed my code to ensure it follows established patterns and conventions.)
  • Testing performed (I have thoroughly tested my changes and verified expected functionality.)
  • Documentation updated (I have updated any relevant documentation)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE/pull/1221 **Author:** [@MickLesk](https://github.com/MickLesk) **Created:** 1/4/2025 **Status:** ✅ Merged **Merged:** 1/5/2025 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `zigbee2mqtt_patch` --- ### 📝 Commits (10+) - [`56febab`](https://github.com/community-scripts/ProxmoxVE/commit/56febab22e4caa9248f2d0cdc5b4261ce76a447e) Fix Zigbee2MQTT BreakingChange to Version 2.0.0 - [`79a2ff3`](https://github.com/community-scripts/ProxmoxVE/commit/79a2ff386c1eaed43406bcf1bb06336f29ed5dbf) Update zigbee2mqtt.sh - [`8f5fe06`](https://github.com/community-scripts/ProxmoxVE/commit/8f5fe06df6fc0703f17af7cb0aa8dad9cdc6323f) Fix Installation Zigbee2Mqtt 2.0.0 - [`57fc6c3`](https://github.com/community-scripts/ProxmoxVE/commit/57fc6c378f6735220197e03e12e714a5c3bf1eaf) Fix Zigbee2MQTT V.2.0.0 - [`c5ab055`](https://github.com/community-scripts/ProxmoxVE/commit/c5ab055ee7ca961c6618177a5d0c75ca5426ee4d) Update zigbee2mqtt-install.sh - [`c69bfd1`](https://github.com/community-scripts/ProxmoxVE/commit/c69bfd17cd39b7ab95c867a2c709798bf2afb253) update script - [`d883b6d`](https://github.com/community-scripts/ProxmoxVE/commit/d883b6d398687598fd92de7b29eef42c60f53104) Update install/zigbee2mqtt-install.sh - [`7465e20`](https://github.com/community-scripts/ProxmoxVE/commit/7465e20c1e8bb047b9e830d562e26c9e3ee0f7c7) add pnpm build - [`67403c5`](https://github.com/community-scripts/ProxmoxVE/commit/67403c5e217b1b70c306fb3e8cf91d3c5e8f45fc) add pnpm build - [`420a0a6`](https://github.com/community-scripts/ProxmoxVE/commit/420a0a63b88c9acce788a1c6dd450e17c4595637) update nodejs ### 📊 Changes **2 files changed** (+59 additions, -104 deletions) <details> <summary>View changed files</summary> 📝 `ct/zigbee2mqtt.sh` (+29 -85) 📝 `install/zigbee2mqtt-install.sh` (+30 -19) </details> ### 📄 Description ## Please read carefully for migration! Do Step 1-8 and after this execute Script 1-2 For Error-Handling read PR Comments or Linked Issue comments. ``` bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/zigbee2mqtt.sh)" ``` ## ✍️ Description https://github.com/community-scripts/ProxmoxVE/discussions/660 1.) Install pnpm ```bash npm install -g pnpm ``` 2.) Do an Update of your config ```bash systemctl stop zigbee2mqtt mkdir -p /opt/z2m_backup cp -r /opt/zigbee2mqtt/data/* /opt/z2m_backup ``` 3.) Change Configuration of configuration yaml ```bash nano /opt/zigbee2mqtt/data/configuration.yaml ``` add here in the right sections: ```yaml 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) ```bash nano /opt/zigbee2mqtt/data/configuration.yaml ``` check this part: ```yaml serial: port: /dev/ttyACM0 adapter: zstack/ember/xxx # <-- Add this line (see following link) ``` ive used zstack, you can check it here: https://github.com/Koenkk/zigbee2mqtt/discussions/24364 5.) go into main path and enter "./update.sh" ```bash 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 ```bash nano /etc/systemd/system/zigbee2mqtt.service ``` change "/usr/bin/npm start" to "/usr/bin/pnpm start" In ExecStart and start the service ```bash systemctl daemon-reload systemctl start zigbee2mqtt ``` 8.) Create an App_version.txt for next updates ```bash touch /opt/zigbee2mqtt_version.txt nano /opt/zigbee2mqtt_version.txt => add 1.9.0 in file and save ``` 9. Run bash (update or bashcall from website) 1-2 Times (Line 2) ## Hint: If you have other problems, have a look at the comments to see if your problem is among them. An alternative solution would be to create a new LXC and export the data-folder from the old one and import it into the new LXC, but this is only theoretical. - - - - Related Issue: #1215 #1478 --- ## 🛠️ Type of Change Please check the relevant options: - [x] Bug fix (non-breaking change that resolves an issue) - [x] New feature (non-breaking change that adds functionality) - [x] Breaking change (fix or feature that would cause existing functionality to change unexpectedly) - [] New script (a fully functional and thoroughly tested script or set of scripts) --- ## ✅ Prerequisites The following steps must be completed for the pull request to be considered: - [x] Self-review performed (I have reviewed my code to ensure it follows established patterns and conventions.) - [x] Testing performed (I have thoroughly tested my changes and verified expected functionality.) - [x] Documentation updated (I have updated any relevant documentation) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-05 05:21:03 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2934
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?