New addon update, now with a frontend, but I can’t use the networkmap or do anyhing on it, its always “loading”.
I use a USB ZigBee stick (CC2531) flashed with zigbe2mqtt 1.2 (not the 3.0 version) as a coordinator, and 10 different ZigBee devices (they work like charm).
I show you some screenshots.
Same here. Tried different browsers, updated to 0.116.1, same issue. Zigbee2mqtt assistant frontend (separate) works tho…
Might be some issue with old arguments in the zigbee2mqtt config?
Yup. config issue. I did a reset to default, and that fixed it. 
I’m gonna try and see
Are you able to see what changed? I’m not home at the moment and copy/pasting config on my mobile doesn’t work, so copying my current values, resetting to default and pasting them back is not desirable - but if it’s just a small edit I can do that remotely.
unfortunately I did not save the old one just copy pasted my custom values.
here is the bare config after a reset.
data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
base_topic: zigbee2mqtt
server: 'mqtt://core-mosquitto'
user:
password:
serial:
port: /dev/ttyACM0
advanced:
log_level: info
pan_id: 6754
channel: 11
network_key:
- 1
- 3
- 5
- 7
- 9
- 11
- 13
- 15
- 0
- 2
- 4
- 6
- 8
- 10
- 12
- 13
availability_blocklist: []
availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
port: 8099
experimental:
new_api: true
socat:
enabled: false
master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
restartdelay: 1
initialdelay: 1
options: '-d -d'
log: false
Brilliant thanks, I’ll have a look at mine shortly and have a game of ‘spot the difference’ 
For me, the difference in the config was:
experimental:
new_api: true
Now it works fine!
Indeed, working here with that added
Thanks all worked immidiatly
Hello all! I have kind of the same problem so I tag along in this thread…
I don’t have any zigbee devices to test with yet but I want to get everything working first 
I run everything in docker, always with the latest image. I tried changing to zigbee2mqtt-dev but no difference.
I tried to send/recieved in mqtt in home assitant, and it worked…
The frontend keeps loading… The “about” section in settings says:
Zigbee2MQTT version
Coordinator type: Unknown
Coordinator revision: Unknown
Frontend version: 0.3.114
My configuration file:
# Home Assistant integration (MQTT discovery)
homeassistant: true
# allow new devices to join
permit_join: true
# MQTT settings
mqtt:
# MQTT base topic for zigbee2mqtt MQTT messages
base_topic: zigbee2mqtt
# MQTT server URL
server: 'mqtt://192.168.x.xx:1883'
# MQTT server authentication, uncomment if required:
# user: my_user
# password: my_password
client_id: 'zigbee2mqtt'
include_device_information: true
# Serial settings
serial:
# Location of CC2531 USB sniffer
port: /dev/ttyACM1
disable_led: false
adapter: deconz
frontend:
# Optional, default 8080
port: 8099
# Optional, default 0.0.0.0
host: 0.0.0.0
# Optional, enables authentication, disabled by default
# auth_token: your-secret-token
experimental:
new_api: true
Part of my docker-compose:
mqtt:
container_name: mqtt
image: eclipse-mosquitto:latest
restart: unless-stopped
ports:
- 1883:1883
- 9001:9001
volumes:
- ~/iotstack/mqtt/config/:/mosquitto/config
- ~/iotstack/mqtt/data/:/mosquitto/data
- ~/iotstack/mqtt/log/:/mosquitto/log
user: 1000:1000
zigbee2mqtt:
container_name: zigbee2mqtt
image: koenkk/zigbee2mqtt:latest
volumes:
- ~/iotstack/zigbee2mqtt/data:/app/data
- /run/udev:/run/udev:ro
devices:
- /dev/ttyACM1:/dev/ttyACM1
#- /dev/ttyACM0:/dev/ttyACM0
# ports:
# - '8092:8080'
# - '8099:8099'
restart: unless-stopped
network_mode: host
# privileged: true
environment:
- TZ=Europe/Stockholm
Your “About” section in settings
Zigbee2MQTT version
Coordinator type: Unknown
Coordinator revision: Unknown
Frontend version: 0.3.114
shows that Zigbee2MQTT is not configured properly thus failed to start.
The Zigbee2mqtt configuration file you show looks like “screwed to death”. I recommend you set it back to “Default” and start all over again.
Also instead of fiddling with …/zigbee2mqtt/configuration.yaml why not simply use the web based editor? You will find it at Supervisor --> Zigbee2mqtt --> Configuration.
Here comes a skeleton of a Zigbee2mqtt configuration (through the web interface):
data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false # or set to "true" for letting devices join
mqtt:
base_topic: zigbee2mqtt
server: 'mqtt://192.168.x.xx:1883'
user: <your-mqtt-user>
password: <your-mqtt-password>
serial:
port: <see-below-regarding-my-comment-on-Serial-Settings>
advanced:
log_level: info
pan_id: 6754 # Default pan_id
channel: 11
network_key:
- 1
- 3
- 5
- 7
- 9
- 11
- 13
- 15
- 0
- 2
- 4
- 6
- 8
- 10
- 12
- 13
availability_blocklist: []
availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
port: 8099
experimental: {}
socat:
enabled: false
master: >-
pty,raw,echo=0,link=<see-below-regarding-my-comment-on-Serial-Settings>,mode=777
slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
options: '-d -d'
log: false
Instead of :
# Serial settings
serial:
# Location of CC2531 USB sniffer
port: /dev/ttyACM1
Try the following:
Go to CLI and execute:
sudo ls -l /dev/serial/by-id
Change:
port: /dev/ttyACM1
to:
port: /dev/serial/by-id/<output-of: sudo ls -l /dev/serial/by-id>
I.e. I am using Slaesh’s stick thus the output of sudo ls -l /dev/serial/by-id looks:
lrwxrwxrwx 1 root root 13 Apr 2 13:14 usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_21_CB_F3_AE-if00-port0 -> ../../ttyUSB0
which makes the setting for “port:” in the config looks like:
serial:
port: >-
/dev/serial/by-id/usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_21_CB_F3_AE-if00-port0
Restart the Zigbee2mqtt add-on and you should be good.
Since he is using docker-compose, he is running HA Container and not HA Supervised or HA OS, and there is no Supervisor.
The zigbee2mqtt configuration looks fine, except it has no ‘advanced’ section.
Oups, thanks for the note. I haven’t noticed. Sure, my instructions are certainly for HA Supervised (or HA OS)
However, something is wrong with his Zigbee2MQTT-config since it does not start correctly but shows:
Zigbee2MQTT version
Coordinator type: Unknown <-- !!!
Coordinator revision: Unknown <-- !!!
Frontend version: 0.3.114
Zigbee2MQTT obviously starts, since you see the front-end.
This is what I get in the front-end :
Zigbee2MQTT version 1.18.1 commit: a43d1f39
Coordinator type zStack12
Coordinator revision 20190619
Frontend version 0.3.76
Did you check the logs ? Either in the front-end under logs, or using the logs from portainer ?
This is the log from the zigbee2mqtt container… I checked it many times yesterday… It seems it cannot connect to the mqtt container?
2021-04-03T08:53:46.759426085Z Zigbee2MQTT:error 2021-04-03 10:53:46: Not connected to MQTT server!
2021-04-03T08:53:46.762993860Z Zigbee2MQTT:error 2021-04-03 10:53:46: Cannot send message: topic: 'zigbee2mqtt/bridge/state', payload: 'offline
2021-04-03T08:53:46.763911345Z Zigbee2MQTT:info 2021-04-03 10:53:46: Disconnecting from MQTT server
2021-04-03T08:53:46.768645085Z (node:16) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'end' of undefined
2021-04-03T08:53:46.768675330Z at MQTT.disconnect (/app/lib/mqtt.js:93:21)
2021-04-03T08:53:46.768686973Z at processTicksAndRejections (internal/process/task_queues.js:93:5)
2021-04-03T08:53:46.768696637Z at async Controller.stop (/app/lib/controller.js:193:9)
2021-04-03T08:53:46.768705520Z at async stop (/app/index.js:47:5)
2021-04-03T08:53:46.768714569Z at async process.handleQuit (/app/index.js:53:9)
2021-04-03T08:53:46.768723472Z (Use `node --trace-warnings ...` to show where the warning was created)
2021-04-03T08:53:46.768738243Z (node:16) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 589)
2021-04-03T08:53:46.768756137Z (node:16) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
2021-04-03T08:53:56.983454371Z Using '/app/data' as data directory
2021-04-03T08:53:57.224838688Z
2021-04-03T08:53:57.224857999Z > [email protected] start /app
2021-04-03T08:53:57.224861351Z > node index.js
2021-04-03T08:53:57.224872920Z
2021-04-03T08:53:57.828853675Z Zigbee2MQTT:info 2021-04-03 10:53:57: Logging to console and directory: '/app/data/log/2021-04-03.10-53-57' filename: log.txt
2021-04-03T08:53:57.845189503Z Zigbee2MQTT:info 2021-04-03 10:53:57: Starting Zigbee2MQTT version 1.18.2 (commit #abd8a09)
2021-04-03T08:53:57.846165239Z Zigbee2MQTT:info 2021-04-03 10:53:57: Starting zigbee-herdsman (0.13.88)
2021-04-03T08:53:57.972585612Z CREATED DECONZ ADAPTER
2021-04-03T08:53:57.995922357Z Zigbee2MQTT:info 2021-04-03 10:53:57: zigbee-herdsman started
2021-04-03T08:53:58.000183950Z Zigbee2MQTT:info 2021-04-03 10:53:57: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":74,"product":0,"revision":"0x264a0700","transportrev":0},"type":"ConBee2/RaspBee2"}'
2021-04-03T08:53:58.020716042Z Zigbee2MQTT:info 2021-04-03 10:53:58: Currently 0 devices are joined:
2021-04-03T08:53:58.021221683Z Zigbee2MQTT:warn 2021-04-03 10:53:58: `permit_join` set to `true` in configuration.yaml.
2021-04-03T08:53:58.021613417Z Zigbee2MQTT:warn 2021-04-03 10:53:58: Allowing new devices to join.
2021-04-03T08:53:58.021947026Z Zigbee2MQTT:warn 2021-04-03 10:53:58: Set `permit_join` to `false` once you joined all devices.
2021-04-03T08:53:58.022415333Z Zigbee2MQTT:info 2021-04-03 10:53:58: Zigbee: allowing new devices to join.
2021-04-03T08:53:58.025622422Z Zigbee2MQTT:info 2021-04-03 10:53:58: Started frontend on port 0.0.0.0:8099
Try :
mqtt:
base_topic: zigbee2mqtt
server: 'mqtt://192.168.x.x'
instead of
mqtt:
# MQTT base topic for zigbee2mqtt MQTT messages
base_topic: zigbee2mqtt
# MQTT server URL
server: 'mqtt://192.168.x.xx:1883'
Can you connect to mqtt with e.g. mqtt explorer or mqttfx ?
Didn’t work.
MQTT Explorer portable on windows works. I can see connections in MQTT container log but nothing when i start zigbee2mqtt…
It dosen’t matter what password I write or not in mqtt explorer, I can still connect.
Can’t post three posts in a row so here goes… 
This issue put me on a wild goose chase. I thought I activated the debug for zigbee2mqtt with:
advanced:
log_level: debug
but I missed the docker part…
-e DEBUG=zigbee-herdsman*
I looked through the logs and found that something probably was wrong with the adapter even though the initial logs seemed to tell me otherwise… After even more(!) googling I stumbled upon something about usb 2.0 and 3.0… Moved my Conbee II to a USB 2.0 port and MAGIC! This also explains why my z-wave dongle became unresponsive when i started the zigbee2mqtt container… Wow… I’m now running the latest containers of everything and so far it seems to work!
Thanks to @francisp and @Tamsy for trying to help! <3
I’ve tried everything I can think of… I can ping ip:1883 from the terminal in zigbee2mqtt container…
I found two configuration.yaml but when I change permit_join: to false it appears in the log so I guess I’m changing in the right file.
I’ve tried different ips… with/without port. With/without frontend and/or experimental… I set a password in mqtt and it worked as expected with other clients.
My current zigbee2mqtt configuration:
# Home Assistant integration (MQTT discovery)
homeassistant: true
# allow new devices to join
permit_join: true
# MQTT settings
mqtt:
# MQTT base topic for zigbee2mqtt MQTT messages
base_topic: zigbee2mqtt
# MQTT server URL
server: 'mqtt://192.168.1.59:1883'
# MQTT server authentication, uncomment if required:
user: 'mastrusr'
password: 'password'
client_id: 'zigbee2mqtt'
include_device_information: true
reject_unauthorized: false
# Serial settings
serial:
# Location of CC2531 USB sniffer
port: /dev/ttyACM1
disable_led: false
adapter: deconz
frontend:
# Optional, default 8080
port: 8099
# Optional, default 0.0.0.0
host: 0.0.0.0
# Optional, enables authentication, disabled by default
# auth_token: your-secret-token
experimental:
new_api: true
Should I write somewhere else?
I just realized I haven’t posted the solution here 
The zigbee usb dongle I used acted up when put in a USB 3 port. I moved it to a USB 2 and everything fired up as intended… Such a stupid problem. I’ve never run into anything like that before!