Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zigbee2MQTT port issue after 2.0.0 #1448

Closed
2 tasks done
Xiaoh-123 opened this issue Jan 13, 2025 · 1 comment
Closed
2 tasks done

Zigbee2MQTT port issue after 2.0.0 #1448

Xiaoh-123 opened this issue Jan 13, 2025 · 1 comment
Labels
not a script issue This is not a script issue

Comments

@Xiaoh-123
Copy link

βœ… 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?

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

πŸ“ Provide a clear and concise description of the issue.

Upon finishing the installation (regardless of default or advanced settings), the script gives http://lxcipaddress:9442 as the frontend URL, however this seems to be a mistake since by default, port 8080 is used for frontend as per Zigbee2MQTT official documentation, and no modification to the configuration.yaml file is made by the script to enforce port 9442.

Screen captures attached from a test run made while creating this post.

Maybe I'm just dumb but it bothered me when I ran tests before migrating my main Z2M instance to 2.0.0 the other day, so I wanted to report on what seems to me like an issue.

βš™οΈ What settings are you using?

  • Default Settings
  • Advanced Settings

πŸ–₯️ Which Linux distribution are you using?

Debian 12

πŸ”„ Steps to reproduce the issue.

Running the script with default or advanced settings (gives the same result).

❌ Paste the full error output (if available).

No error messages per se, just erroneous port information (IMHO).

πŸ–ΌοΈ Additional context (optional).

Capture d'Γ©cran 2025-01-13 121139
Capture d'Γ©cran 2025-01-13 121625

@MickLesk
Copy link
Member

image

@MickLesk MickLesk closed this as not planned Won't fix, can't repro, duplicate, stale Jan 13, 2025
@MickLesk MickLesk added the not a script issue This is not a script issue label Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not a script issue This is not a script issue
Projects
None yet
Development

No branches or pull requests

2 participants