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

Zigbee2mqtt dev branch issue #141

New Issue
Closed
opened 2026-02-04 16:48:33 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-04 16:48:33 +03:00
Owner
Copy Link

Originally created by @Kuchiru on GitHub (Dec 5, 2024).

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

When running the default (non-alpine) version of the install script and choosing YES for the dev branch the installation of Z2M fails with an error.

The error shown is due to the use of npm ci, it will give an error regarding a missing lock file and does not continue after that, either it is missing npm install or it is because the dev branch recently changed to use pnpm instead which i think could also be the cause of this issue.
see: https://github.com/Koenkk/zigbee2mqtt/tree/dev?tab=readme-ov-file#developing

What settings are you currently utilizing?

  • Default Settings
  • Advanced Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

msg_info "Installing Zigbee2MQTT"
cd /opt/zigbee2mqtt
if [[ $DEV == "y" ]]; then
$STD git fetch origin dev:dev
$STD git checkout dev
$STD git pull
fi
$STD npm ci
msg_ok "Installed Zigbee2MQTT"

Please provide detailed steps to reproduce the issue.

  1. Copy the Z2M Default version of the install script to the proxmox shell
  2. Proceed with the installation using the defaults
  3. When asked to use the dev branch, answer y
  4. Wait a little and it will show the npm ci error.
Originally created by @Kuchiru on GitHub (Dec 5, 2024). ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. When running the default (non-alpine) version of the install script and choosing YES for the dev branch the installation of Z2M fails with an error. The error shown is due to the use of `npm ci`, it will give an error regarding a missing lock file and does not continue after that, either it is missing `npm install` or it is because the dev branch recently changed to use `pnpm` instead which i think could also be the cause of this issue. see: https://github.com/Koenkk/zigbee2mqtt/tree/dev?tab=readme-ov-file#developing ### What settings are you currently utilizing? - [X] Default Settings - [ ] Advanced Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. ``` msg_info "Installing Zigbee2MQTT" cd /opt/zigbee2mqtt if [[ $DEV == "y" ]]; then $STD git fetch origin dev:dev $STD git checkout dev $STD git pull fi $STD npm ci msg_ok "Installed Zigbee2MQTT" ``` ### Please provide detailed steps to reproduce the issue. 1. Copy the Z2M Default version of the install script to the proxmox shell 2. Proceed with the installation using the defaults 3. When asked to use the dev branch, answer `y` 4. Wait a little and it will show the `npm ci` error.
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
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#141
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?