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 12 Packages Projects Releases 10 Wiki Activity

Zigbee2MQTT 2.1.3 Update fails #577

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

Originally created by @tomfrenzel on GitHub (Mar 3, 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.

I'm currently running Zigbee2MQTT 2.1.1 (New Install on 01.03.2025).
When updating the LXC using the update command, i get the following error:
✔️ Stopped Service ✔️ Backup Created ⠹ Updating Zigbee2MQTT to v2.1.3 ERROR  Failed to switch pnpm to v10.4.1. Looks like pnpm CLI is missing at "/root/.local/share/pnpm/.tools/pnpm/10.4.1/bin" or is incorrect spawnSync /root/.local/share/pnpm/.tools/pnpm/10.4.1/bin/pnpm ENOENT ⠸ Updating Zigbee2MQTT to v2.1.3 [ERROR] in line 52: exit code 0: while executing command $STD pnpm install --frozen-lockfile

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Enter LXC console
Type update
Press enter
Proceed with either verbose on non-verbose logging

❌ Paste the full error output (if available).

✔️ Stopped Service
✔️ Backup Created
⠹ Updating Zigbee2MQTT to v2.1.3 ERROR  Failed to switch pnpm to v10.4.1. Looks like pnpm CLI is missing at "/root/.local/share/pnpm/.tools/pnpm/10.4.1/bin" or is incorrect
spawnSync /root/.local/share/pnpm/.tools/pnpm/10.4.1/bin/pnpm ENOENT
⠸ Updating Zigbee2MQTT to v2.1.3
[ERROR] in line 52: exit code 0: while executing command $STD pnpm install --frozen-lockfile

root@zigbee2mqtt:~#

🖼️ Additional context (optional).

No response

Originally created by @tomfrenzel on GitHub (Mar 3, 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. I'm currently running Zigbee2MQTT 2.1.1 (New Install on 01.03.2025). When updating the LXC using the update command, i get the following error: ` ✔️ Stopped Service ✔️ Backup Created ⠹ Updating Zigbee2MQTT to v2.1.3 ERROR  Failed to switch pnpm to v10.4.1. Looks like pnpm CLI is missing at "/root/.local/share/pnpm/.tools/pnpm/10.4.1/bin" or is incorrect spawnSync /root/.local/share/pnpm/.tools/pnpm/10.4.1/bin/pnpm ENOENT ⠸ Updating Zigbee2MQTT to v2.1.3 [ERROR] in line 52: exit code 0: while executing command $STD pnpm install --frozen-lockfile` ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Enter LXC console Type update Press enter Proceed with either verbose on non-verbose logging ### ❌ Paste the full error output (if available). ✔️ Stopped Service ✔️ Backup Created ⠹ Updating Zigbee2MQTT to v2.1.3 ERROR  Failed to switch pnpm to v10.4.1. Looks like pnpm CLI is missing at "/root/.local/share/pnpm/.tools/pnpm/10.4.1/bin" or is incorrect spawnSync /root/.local/share/pnpm/.tools/pnpm/10.4.1/bin/pnpm ENOENT ⠸ Updating Zigbee2MQTT to v2.1.3 [ERROR] in line 52: exit code 0: while executing command $STD pnpm install --frozen-lockfile root@zigbee2mqtt:~# ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 20:05:02 +03:00
OVERLORD commented 2026-02-04 20:05:13 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 3, 2025):

pnpm -v?

@MickLesk commented on GitHub (Mar 3, 2025): pnpm -v?
OVERLORD commented 2026-02-04 20:05:25 +03:00
Author
Owner
Copy Link

@tomfrenzel commented on GitHub (Mar 3, 2025):

pnpm -v?

10.5.2

@tomfrenzel commented on GitHub (Mar 3, 2025): > pnpm -v? 10.5.2
OVERLORD commented 2026-02-04 20:05:50 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 3, 2025):

Can you try Update this before?

@MickLesk commented on GitHub (Mar 3, 2025): Can you try Update this before?
OVERLORD commented 2026-02-04 20:05:59 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 3, 2025):

hm. tested with pnpm 9.5.x - that works, 10.5 not.

try this:
npm install -g pnpm@10.4.1 - that works

@MickLesk commented on GitHub (Mar 3, 2025): hm. tested with pnpm 9.5.x - that works, 10.5 not. try this: npm install -g pnpm@10.4.1 - that works
OVERLORD commented 2026-02-04 20:06:14 +03:00
Author
Owner
Copy Link

@tomfrenzel commented on GitHub (Mar 3, 2025):

That give me this:

root@zigbee2mqtt:~# pnpm self-update
Nothing to stop. No server is running for the store at /root/.local/share/pnpm/store/v10
The currently active pnpm v10.5.2 is already "latest" and doesn't need an update

Altrough, when navigation into /opt/zigbee2mqtt and running pnpm -v i get 9.15.4

@tomfrenzel commented on GitHub (Mar 3, 2025): That give me this: ``` root@zigbee2mqtt:~# pnpm self-update Nothing to stop. No server is running for the store at /root/.local/share/pnpm/store/v10 The currently active pnpm v10.5.2 is already "latest" and doesn't need an update ``` Altrough, when navigation into /opt/zigbee2mqtt and running pnpm -v i get 9.15.4
OVERLORD commented 2026-02-04 20:06:19 +03:00
Author
Owner
Copy Link

@tomfrenzel commented on GitHub (Mar 3, 2025):

hm. tested with pnpm 9.5.x - that works, 10.5 not.

try this: npm install -g pnpm@10.4.1 - that works

Can confirm that this resolves the problem so the update runs trough afterwards

@tomfrenzel commented on GitHub (Mar 3, 2025): > hm. tested with pnpm 9.5.x - that works, 10.5 not. > > try this: npm install -g pnpm@10.4.1 - that works Can confirm that this resolves the problem so the update runs trough afterwards
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 bug
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#577
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?