Frontend #

Ongoing discussion can be found here:

Zigbee2MQTT has a built-in webbased frontend. To enable the frontend add the following to your configuration.yaml:

  # Optional, default 8080
  port: 8080
  # Optional, default
  # Optional, enables authentication, disabled by default
  auth_token: your-secret-token

To specify the auth_token in a different file set e.g. auth_token: '!secret auth_token', create a file called secret.yaml next to configuration.yaml with content auth_token: super-secret-token.

Screenshot #


Nginx proxy configuration #

In case you want to run the frontend behind a proxy you can use the following config as an example.

Due to WebKit Bug 80362, which prevents basic authentication from being used with WebSockets, the frontend will not work in WebKit-based browsers when this type of authentication is configured. This includes desktop Safari on Mac and all browsers and web views on iOS. To work around the issue, configure the frontendโ€™s auth_token to configure application-level auth and remove auth_basic from the web server config.

server {
    listen       80;
    return 301$request_uri;

server {
    listen      443 ssl http2;
    listen      [::]:443 ssl http2;

    # In case you want to use basic authentication:
    auth_basic "Login";
    auth_basic_user_file /zigbee2mqtt_htpasswd;

    ssl_certificate     /config/etc/letsencrypt/live/;
    ssl_certificate_key /config/etc/letsencrypt/live/;


    location / {
        proxy_pass http://localhost:8080/;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

    location /api {
        proxy_pass         http://localhost:8080/api;
        proxy_set_header Host $host;

        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";