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

Zigbee2mqtt - install OK but can't access to web interface #284

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

Originally created by @Thiiib on GitHub (Jan 6, 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?

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

📝 Provide a clear and concise description of the issue.

Hi all

I managed to install it perfectly, it connected to my network .... but can't access to it
when looking in the console it show an IP
proxmox_zigbee2mqtt_ip
when looking in proxmox... no IP
proxmox_zigbee2mqtt_NO-ip

Let me know if i can help... I looked at /etc/network/interfaces and looks ok

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Launched the script, let him installed and try to acceed to the platform using IP:9442

❌ Paste the full error output (if available).

I don't have specific error message, just can't connect to the platform using IP:9442

🖼️ Additional context (optional).

No response

Originally created by @Thiiib on GitHub (Jan 6, 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? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/zigbee2mqtt.sh)" ### 📝 Provide a clear and concise description of the issue. Hi all I managed to install it perfectly, it connected to my network .... but can't access to it when looking in the console it show an IP ![proxmox_zigbee2mqtt_ip](https://github.com/user-attachments/assets/f54edfdd-64a1-4bdd-9a2f-12a3fb459ed7) when looking in proxmox... no IP ![proxmox_zigbee2mqtt_NO-ip](https://github.com/user-attachments/assets/01629e22-2ab2-48ca-8313-2c19374667e1) Let me know if i can help... I looked at /etc/network/interfaces and looks ok ### ⚙️ What settings are you using? - [X] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Launched the script, let him installed and try to acceed to the platform using IP:9442 ### ❌ Paste the full error output (if available). I don't have specific error message, just can't connect to the platform using IP:9442 ### 🖼️ Additional context (optional). _No response_
OVERLORD commented 2026-02-04 17:43:01 +03:00
Author
Owner
Copy Link

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

Cant reproduce this. Whats the Output of Service File?

@MickLesk commented on GitHub (Jan 6, 2025): Cant reproduce this. Whats the Output of Service File?
OVERLORD commented 2026-02-04 17:43:06 +03:00
Author
Owner
Copy Link

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

have you created the configuration.yaml and co?

Needed for working ui

image

@MickLesk commented on GitHub (Jan 6, 2025): have you created the configuration.yaml and co? Needed for working ui ![image](https://github.com/user-attachments/assets/482b4dd7-5c79-4706-9430-28ea6b7c4497)
OVERLORD commented 2026-02-04 17:43:17 +03:00
Author
Owner
Copy Link

@Thiiib commented on GitHub (Jan 7, 2025):

have you created the configuration.yaml and co?

Needed for working ui

image

Hi

Thank's for your reply

Unfortunately it doesn't works...

  1. I added my USB device to the container but the number of the device change at each reboot, I tried, in the container configuration, to map using the /dev/serial/id but KO, i tried also /dev/ttyACM0 but KO

  2. If i use the ID checking, before launching the container, the ID of the USB device in proxmox shell, I manage to launch the container and to edit the configuration file but restart doesn't allow me to connect...

Here is the file as I modified it,
promox-VM-zigbee2mqtt-configyaml_light

and how it looks after a restart
promox-VM-zigbee2mqtt-configyaml_light_afterreboot

but I can't connect to 192.168.68.105:9442
promox-VM-zigbee2mqtt-webaccess_refused

btw I don't know what should be the "user" and "password" in the configuration file ? i deleted this part

In addition you talked about "Output of Service File" how can I get it ?

@Thiiib commented on GitHub (Jan 7, 2025): > have you created the configuration.yaml and co? > > Needed for working ui > > ![image](https://private-user-images.githubusercontent.com/47820557/400341799-482b4dd7-5c79-4706-9430-28ea6b7c4497.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzYxOTU0OTAsIm5iZiI6MTczNjE5NTE5MCwicGF0aCI6Ii80NzgyMDU1Ny80MDAzNDE3OTktNDgyYjRkZDctNWM3OS00NzA2LTk0MzAtMjhlYTZiN2M0NDk3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAxMDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMTA2VDIwMjYzMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWU3OWJlNzRhMmM3MjVhYTZkMjg3NjIwNWQ0NGI1NjVmOWVhMjNiN2U1ZmNlZmNkMTlhMzdmNjIxYjk1OGU3MWUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.pWS4dPq2V7xc-dgWES1UAeDwm2X_56PsJ2RqpPkXbi4) Hi Thank's for your reply Unfortunately it doesn't works... 1. I added my USB device to the container but the number of the device change at each reboot, I tried, in the container configuration, to map using the /dev/serial/id but KO, i tried also /dev/ttyACM0 but KO 2. If i use the ID checking, before launching the container, the ID of the USB device in proxmox shell, I manage to launch the container and to edit the configuration file but restart doesn't allow me to connect... Here is the file as I modified it, ![promox-VM-zigbee2mqtt-configyaml_light](https://github.com/user-attachments/assets/7e51825b-bfc7-4226-afd8-0985a8cb9e4d) and how it looks after a restart ![promox-VM-zigbee2mqtt-configyaml_light_afterreboot](https://github.com/user-attachments/assets/e38a7cf5-69b3-4a9f-824d-ad28551cbd72) but I can't connect to 192.168.68.105:9442 ![promox-VM-zigbee2mqtt-webaccess_refused](https://github.com/user-attachments/assets/3ed7620c-89c1-476a-9ee1-d38cbc3d8d48) btw I don't know what should be the "user" and "password" in the configuration file ? i deleted this part In addition you talked about "Output of Service File" how can I get it ?
OVERLORD commented 2026-02-04 17:43:27 +03:00
Author
Owner
Copy Link

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

Space in Server. Stop Service cd into folder and pnpm start for more Output

@MickLesk commented on GitHub (Jan 7, 2025): Space in Server. Stop Service cd into folder and pnpm start for more Output
OVERLORD commented 2026-02-04 17:43:31 +03:00
Author
Owner
Copy Link

@Thiiib commented on GitHub (Jan 8, 2025):

Space in Server. Stop Service cd into folder and pnpm start for more Output

It's what you expected ?

root@zigbee2mqtt:/opt/zigbee2mqtt# cd /opt/zigbee2mqtt/ && npm start

> zigbee2mqtt@2.0.0 start
> node index.js

Starting Zigbee2MQTT without watchdog.
[2025-01-07 22:02:38] info:     z2m: Logging to console, file (filename: log.log)
[2025-01-07 22:02:38] info:     z2m: Starting Zigbee2MQTT version 2.0.0 (commit #unknown)
[2025-01-07 22:02:38] info:     z2m: Starting zigbee-herdsman (3.2.1)
[2025-01-07 22:02:38] info:     z2m: zigbee-herdsman started (resumed)
[2025-01-07 22:02:38] info:     z2m: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":120,"product":0,"revision":"0x26780700","transportrev":0},"type":"ConBee2/RaspBee2"}'
[2025-01-07 22:02:38] info:     z2m: Currently 0 devices are joined.
[2025-01-07 22:02:38] info:     z2m: Connecting to MQTT server at mqtt://192.168.68.105:1883
[2025-01-07 22:02:38] error:    z2m: MQTT failed to connect, exiting... (connect ECONNREFUSED 192.168.68.105:1883)
[2025-01-07 22:02:38] info:     z2m: Stopping zigbee-herdsman...
[2025-01-07 22:02:38] info:     z2m: Stopped zigbee-herdsman

It looks it don't manage to connect to mqtt server ? I'm going to install a mqtt container and try to connect to it

@Thiiib commented on GitHub (Jan 8, 2025): > Space in Server. Stop Service cd into folder and pnpm start for more Output It's what you expected ? ``` root@zigbee2mqtt:/opt/zigbee2mqtt# cd /opt/zigbee2mqtt/ && npm start > zigbee2mqtt@2.0.0 start > node index.js Starting Zigbee2MQTT without watchdog. [2025-01-07 22:02:38] info: z2m: Logging to console, file (filename: log.log) [2025-01-07 22:02:38] info: z2m: Starting Zigbee2MQTT version 2.0.0 (commit #unknown) [2025-01-07 22:02:38] info: z2m: Starting zigbee-herdsman (3.2.1) [2025-01-07 22:02:38] info: z2m: zigbee-herdsman started (resumed) [2025-01-07 22:02:38] info: z2m: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":120,"product":0,"revision":"0x26780700","transportrev":0},"type":"ConBee2/RaspBee2"}' [2025-01-07 22:02:38] info: z2m: Currently 0 devices are joined. [2025-01-07 22:02:38] info: z2m: Connecting to MQTT server at mqtt://192.168.68.105:1883 [2025-01-07 22:02:38] error: z2m: MQTT failed to connect, exiting... (connect ECONNREFUSED 192.168.68.105:1883) [2025-01-07 22:02:38] info: z2m: Stopping zigbee-herdsman... [2025-01-07 22:02:38] info: z2m: Stopped zigbee-herdsman ``` It looks it don't manage to connect to mqtt server ? I'm going to install a mqtt container and try to connect to it
OVERLORD commented 2026-02-04 17:43:40 +03:00
Author
Owner
Copy Link

@Thiiib commented on GitHub (Jan 8, 2025):

It looks better now with the install of mqtt container and linking Zigbee2mqtt to Mqtt container.

When I have a problem with my adapter I need to do systemctl stop zigbee2mqtt and npm start

However now everything looks launched, i manage to access to zigbee2mqtt web interface but... can't add zigbee devices

2025-01-08 00:22:20] info:     z2m: Zigbee: allowing new devices to join.
[2025-01-08 00:22:44] error:    z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'TIMEOUT'
[2025-01-08 00:22:44] info:     z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"TIMEOUT","status":"error","transaction":"a2fk4-2"}'

I restarted the container, needed also to do systemctl stop zigbee2mqtt and npm start to launch zigbee2mqtt

This time I managed to launched "join" and my device has been added !

@Thiiib commented on GitHub (Jan 8, 2025): It looks better now with the install of mqtt container and linking Zigbee2mqtt to Mqtt container. When I have a problem with my adapter I need to do `systemctl stop zigbee2mqtt` and `npm start` However now everything looks launched, i manage to access to zigbee2mqtt web interface but... can't add zigbee devices ``` 2025-01-08 00:22:20] info: z2m: Zigbee: allowing new devices to join. [2025-01-08 00:22:44] error: z2m: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'TIMEOUT' [2025-01-08 00:22:44] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"TIMEOUT","status":"error","transaction":"a2fk4-2"}' ``` I restarted the container, needed also to do `systemctl stop zigbee2mqtt` and `npm start` to launch zigbee2mqtt This time I managed to launched "join" and my device has been added !
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#284
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?