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

Zigbee2MQTT Update fails #331

New Issue
Closed
opened 2026-02-04 18:00:52 +03:00 by OVERLORD · 13 comments
OVERLORD commented 2026-02-04 18:00:52 +03:00
Owner
Copy Link

Originally created by @Hydro-guy on GitHub (Jan 14, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Zigbee2MQTT

📂 What was the exact command used to execute the script?

update

📝 Provide a clear and concise description of the issue.

ran update in container console. Got this error.

⠇ Updating Zigbee2MQTT to v2.0.0
[ERROR] in line 55: exit code 0: while executing command pnpm install --frozen-lockfile &> /dev/null

root@zigbee2mqtt:~#

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

run update. got error. restored container backup. tried again. same error.

❌ Paste the full error output (if available).

Zigbee2MQTT update error 2025-01-14 084831

🖼️ Additional context (optional).

No response

Originally created by @Hydro-guy on GitHub (Jan 14, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Zigbee2MQTT ### 📂 What was the exact command used to execute the script? update ### 📝 Provide a clear and concise description of the issue. ran update in container console. Got this error. ⠇ Updating Zigbee2MQTT to v2.0.0 [ERROR] in line 55: exit code 0: while executing command pnpm install --frozen-lockfile &> /dev/null root@zigbee2mqtt:~# ### ⚙️ What settings are you using? - [X] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. run update. got error. restored container backup. tried again. same error. ### ❌ Paste the full error output (if available). ![Zigbee2MQTT update error 2025-01-14 084831](https://github.com/user-attachments/assets/9a34588d-4665-453b-bd09-03718e11eee2) ### 🖼️ Additional context (optional). _No response_
OVERLORD commented 2026-02-04 18:01:10 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 14, 2025):

have you read the migration guide? looks not so

@MickLesk commented on GitHub (Jan 14, 2025): have you read the migration guide? looks not so
OVERLORD commented 2026-02-04 18:01:16 +03:00
Author
Owner
Copy Link

@Hydro-guy commented on GitHub (Jan 15, 2025):

I searched issues prior to posting - nothing found.

@Hydro-guy commented on GitHub (Jan 15, 2025): I searched issues prior to posting - nothing found.
OVERLORD commented 2026-02-04 18:01:32 +03:00
Author
Owner
Copy Link

@Hydro-guy commented on GitHub (Jan 15, 2025):

checked the install page as well - perhaps a link there would help.

@Hydro-guy commented on GitHub (Jan 15, 2025): checked the install page as well - perhaps a link there would help.
OVERLORD commented 2026-02-04 18:01:37 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 15, 2025):

Look at Changelog, search zigbee2mqtt. Look discussions, 1 min search time. Good Job

@MickLesk commented on GitHub (Jan 15, 2025): Look at Changelog, search zigbee2mqtt. Look discussions, 1 min search time. Good Job
OVERLORD commented 2026-02-04 18:01:49 +03:00
Author
Owner
Copy Link

@Hydro-guy commented on GitHub (Jan 15, 2025):

Not sure why you expect users to look all over the place for answers. First you look in issues - both open or closed. Then you check the install page. In any case - for anyone looking for help - go to https://github.com/community-scripts/ProxmoxVE/discussions/660 for a debian install. The link to Koenkk mentioned at the first of this is more general in the steps you need to follow as there are several required that are not listed in the discussion. In step 3 of the discussion check first that you don't already have the required statements - most will be there. Just paste the one you need. Step 4 - read the koenkk step - you just have to make sure that your serial path and adapter are defined. you may not have a Texas Instrument adapter in which case zstack is not correct - mine is ember. Step 5 - before you execute this command go to koenkk and follow the bare metal instructions. I didn't and got the "please commit your changes" and the update aborted. I followed the koenkk instructions (without looking a bit farther down) and still got an error at "./update.sh". "Installing dependencies...npm error code EUSAGE" and more errors. Ran the "git pull --no-rebase" mentioned a bit farther down in koenkk and got "Already up to date." ran "./update.sh" this time completed successfully. Go back to koenkk and complete the bare metal instructions. ran "pnpm run clean" at this point - figured it wouldnt hurt. Step 6 onwards no problems. reboot container.

@Hydro-guy commented on GitHub (Jan 15, 2025): Not sure why you expect users to look all over the place for answers. First you look in issues - both open or closed. Then you check the install page. In any case - for anyone looking for help - go to https://github.com/community-scripts/ProxmoxVE/discussions/660 for a debian install. The link to Koenkk mentioned at the first of this is more general in the steps you need to follow as there are several required that are not listed in the discussion. In step 3 of the discussion check first that you don't already have the required statements - most will be there. Just paste the one you need. Step 4 - read the koenkk step - you just have to make sure that your serial path and adapter are defined. you may not have a Texas Instrument adapter in which case zstack is not correct - mine is ember. Step 5 - before you execute this command go to koenkk and follow the bare metal instructions. I didn't and got the "please commit your changes" and the update aborted. I followed the koenkk instructions (without looking a bit farther down) and still got an error at "./update.sh". "Installing dependencies...npm error code EUSAGE" and more errors. Ran the "git pull --no-rebase" mentioned a bit farther down in koenkk and got "Already up to date." ran "./update.sh" this time completed successfully. Go back to koenkk and complete the bare metal instructions. ran "pnpm run clean" at this point - figured it wouldnt hurt. Step 6 onwards no problems. reboot container.
OVERLORD commented 2026-02-04 18:01:53 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 15, 2025):

to many steps, tteck would have said: “if you're too lazy to look at the changelog, you're broke.” I gave you the right hint, it's funny that probably a few hundred users, with a few exceptions, managed to do it without any problems.

@MickLesk commented on GitHub (Jan 15, 2025): to many steps, tteck would have said: “if you're too lazy to look at the changelog, you're broke.” I gave you the right hint, it's funny that probably a few hundred users, with a few exceptions, managed to do it without any problems.
OVERLORD commented 2026-02-04 18:01:59 +03:00
Author
Owner
Copy Link

@dreed47 commented on GitHub (Jan 16, 2025):

This is a joke right? The update script is broke and the steps in #660 are incorrect. For example step 6 says "adapter: zstack" well that ONLY works if thats your adapter, otherwise it fails. Step 5 update script fails because you have to git stash then git pull. I gave up in step 6 when test run failed. I'll go back and start from scratch with a debain CT and manually install and upgrade Z2M. And why is this issue closed? When the update script sill fails?

@dreed47 commented on GitHub (Jan 16, 2025): This is a joke right? The update script is broke and the steps in #660 are incorrect. For example step 6 says "adapter: zstack" well that ONLY works if thats your adapter, otherwise it fails. Step 5 update script fails because you have to git stash then git pull. I gave up in step 6 when test run failed. I'll go back and start from scratch with a debain CT and manually install and upgrade Z2M. And why is this issue closed? When the update script sill fails?
OVERLORD commented 2026-02-04 18:02:03 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 16, 2025):

You cant read the PR ? Many people have confirmed that it works and have actively worked with and tested it. At the way 660 is before the 2.0.0 version. Read the changelog and the corresponding PR, it says it all.

It's no joke and if you don't like it, just don't use the script and do it yourself. It's cheeky to react like this and expect volunteers like us to pray to you every step of the way. Be glad that someone cares at all.

And as an addition, below is the link from the maintainer as info on the subject of zstack, so you should be able to read a bit, especially as a developer?

"you can check it here: Koenkk/zigbee2mqtt#24364"

@MickLesk commented on GitHub (Jan 16, 2025): You cant read the PR ? Many people have confirmed that it works and have actively worked with and tested it. At the way 660 is before the 2.0.0 version. Read the changelog and the corresponding PR, it says it all. It's no joke and if you don't like it, just don't use the script and do it yourself. It's cheeky to react like this and expect volunteers like us to pray to you every step of the way. Be glad that someone cares at all. And as an addition, below is the link from the maintainer as info on the subject of zstack, so you should be able to read a bit, especially as a developer? "you can check it here: Koenkk/zigbee2mqtt#24364"
OVERLORD commented 2026-02-04 18:02:09 +03:00
Author
Owner
Copy Link

@dreed47 commented on GitHub (Jan 16, 2025):

Sorry for my tone, but just so I'm understanding. I can't read the PR? No PR referenced here. So I'll search and try to find the exact PR you're referencing. I'll do my best to read them and I try to guess what you're talking about. No worries, I won't ask what the PR # is because I know the response will be "What? you cant do a search??". I tried to follow what's outlined in the #660 discussion, those steps failed. No worries, I won't bother anyone here I'll do my best to figure it out on my own. Yes I am a developer and yes I've been involved in many open source projects and no, I EXPECT nothing from anyone doing this for free especially if their attitude is "RTFM and don't bother me". Your first response to this issue was "have you read the migration guide? looks not so". What migration guide ? Where? Your response is basically go find this info yourself and don't bother me. If you don't want to provide support for an open source project then step aside and let others do it.

@dreed47 commented on GitHub (Jan 16, 2025): Sorry for my tone, but just so I'm understanding. I can't read the PR? No PR referenced here. So I'll search and try to find the exact PR you're referencing. I'll do my best to read them and I try to guess what you're talking about. No worries, I won't ask what the PR # is because I know the response will be "What? you cant do a search??". I tried to follow what's outlined in the #660 discussion, those steps failed. No worries, I won't bother anyone here I'll do my best to figure it out on my own. Yes I am a developer and yes I've been involved in many open source projects and no, I EXPECT nothing from anyone doing this for free especially if their attitude is "RTFM and don't bother me". Your first response to this issue was "have you read the migration guide? looks not so". What migration guide ? Where? Your response is basically go find this info yourself and don't bother me. If you don't want to provide support for an open source project then step aside and let others do it.
OVERLORD commented 2026-02-04 18:02:17 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 16, 2025):

https://github.com/community-scripts/ProxmoxVE/pull/1221

Is the PR. I do the same like tteck. Ive create an Changelog with "Breaking Change" and I make a point of attempting to describe a possible solution path. In the case of zigbee2mqtt, it's challenging. I was on the dev branch (which aligns with 660), so my migration was "easier." I set up five additional LXC containers and, based on that, tried to write a migration that covers approximately 90% of cases. The other cases can be found as comments in the PR.

(PS: changelog.md 2025-01-05 entry)

It's not about that, but when creating an issue, you "confirm" that you've read the changelog, searched the discussions (including open ones), and especially issues and PRs. It becomes exhausting when the same topic (and yes, zigbee2mqtt was the most annoying of all) is brought up repeatedly with the exact same points.

Oh, and for your information, tteck often closed such issues without comment and was done with it.

@MickLesk commented on GitHub (Jan 16, 2025): https://github.com/community-scripts/ProxmoxVE/pull/1221 Is the PR. I do the same like tteck. Ive create an Changelog with "Breaking Change" and I make a point of attempting to describe a possible solution path. In the case of zigbee2mqtt, it's challenging. I was on the dev branch (which aligns with 660), so my migration was "easier." I set up five additional LXC containers and, based on that, tried to write a migration that covers approximately 90% of cases. The other cases can be found as comments in the PR. (PS: changelog.md 2025-01-05 entry) It's not about that, but when creating an issue, you "confirm" that you've read the changelog, searched the discussions (including open ones), and especially issues and PRs. It becomes exhausting when the same topic (and yes, zigbee2mqtt was the most annoying of all) is brought up repeatedly with the exact same points. Oh, and for your information, tteck often closed such issues without comment and was done with it.
OVERLORD commented 2026-02-04 18:02:28 +03:00
Author
Owner
Copy Link

@dreed47 commented on GitHub (Jan 17, 2025):

Thank you for the information.

For anyone else that stumbles upon this issue thread: The steps outlined in #660 worked for with the following changes...

Step 4: adapter: ember (instead of zstack)
Step 5: BEFORE running the update do a git stash then a git pull --no-rebase then a pnpm run clean then do step 5

@dreed47 commented on GitHub (Jan 17, 2025): Thank you for the information. For anyone else that stumbles upon this issue thread: The steps outlined in #660 worked for with the following changes... Step 4: adapter: ember (instead of zstack) Step 5: BEFORE running the update do a ```git stash``` then a ```git pull --no-rebase``` then a ```pnpm run clean``` then do step 5
OVERLORD commented 2026-02-04 18:02:33 +03:00
Author
Owner
Copy Link

@dreed47 commented on GitHub (Jan 17, 2025):

#1221

Is the PR. I do the same like tteck. Ive create an Changelog with "Breaking Change" and I make a point of attempting to describe a possible solution path. In the case of zigbee2mqtt, it's challenging. I was on the dev branch (which aligns with 660), so my migration was "easier." I set up five additional LXC containers and, based on that, tried to write a migration that covers approximately 90% of cases. The other cases can be found as comments in the PR.

(PS: changelog.md 2025-01-05 entry)

It's not about that, but when creating an issue, you "confirm" that you've read the changelog, searched the discussions (including open ones), and especially issues and PRs. It becomes exhausting when the same topic (and yes, zigbee2mqtt was the most annoying of all) is brought up repeatedly with the exact same points.

Oh, and for your information, tteck often closed such issues without comment and was done with it.

Seems like it could save a lot of support headaches if the update script recognized a 1.x to 2.0 z2m upgrade and stop and provide a link to #660 ...just an idea...

@dreed47 commented on GitHub (Jan 17, 2025): > [#1221](https://github.com/community-scripts/ProxmoxVE/pull/1221) > > Is the PR. I do the same like tteck. Ive create an Changelog with "Breaking Change" and I make a point of attempting to describe a possible solution path. In the case of zigbee2mqtt, it's challenging. I was on the dev branch (which aligns with 660), so my migration was "easier." I set up five additional LXC containers and, based on that, tried to write a migration that covers approximately 90% of cases. The other cases can be found as comments in the PR. > > (PS: changelog.md 2025-01-05 entry) > > It's not about that, but when creating an issue, you "confirm" that you've read the changelog, searched the discussions (including open ones), and especially issues and PRs. It becomes exhausting when the same topic (and yes, zigbee2mqtt was the most annoying of all) is brought up repeatedly with the exact same points. > > Oh, and for your information, tteck often closed such issues without comment and was done with it. Seems like it could save a lot of support headaches if the update script recognized a 1.x to 2.0 z2m upgrade and stop and provide a link to #660 ...just an idea...
OVERLORD commented 2026-02-04 18:02:37 +03:00
Author
Owner
Copy Link

@jeeftor commented on GitHub (Feb 28, 2025):

Having to search the ChangeLog to find a random issue is not super user-helpful. I'm still struggling to get the update working .. running into all sorts of issues. Might just make a new container and move my config over.

@jeeftor commented on GitHub (Feb 28, 2025): Having to search the ChangeLog to find a random issue is not super user-helpful. I'm still struggling to get the update working .. running into all sorts of issues. Might just make a new container and move my config over.
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
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#331
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?