Zigbbe2mqtt - no devices discovered

Hi Everyone,

I’m still pretty new to HA so sorry for probably dumb question, but I have been trying to solve this on my own for a while and finally decided to try asking here.

I’m running HA on RPi4 supervised (unsupported) and until now I have been handling my zigbee devices through my Xiaomi 3 gateway using the HACS integration since all my device where of the same maker.

I finally decided to try adding zigbee2mqtt to my system using the Sonoff Zigbee 3.0 plus dongle.
I followed multiple guides on how to flash and according to all I can see it was successful, conencted it to my pi and setup the MQTT broker and zigbee2mqtt addons base more guides and article. All seems to be running without issues…

As my first device I got 2 Blitzwolf BW-SHP15 that are supposed to be supported by this integration. No matter what I try, I’m not getting the plugs discovered when in pairing mode on both sides.

I confirmed that the plugs work, or as much as I could… I managed to get connection using my Xiaomi gateway and the default integration (it didn’t allow me to operate it as it is not a supported device, but is still paired).

these are my logs:

MQTT broker

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] mosquitto.sh: executing... 
[14:54:31] INFO: Certificates found: SSL is available
[cont-init.d] mosquitto.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[14:54:32] INFO: Starting NGINX for authentication handling...
[14:54:32] INFO: Starting mosquitto MQTT broker...
1649940872: mosquitto version 1.6.12 starting
1649940872: |-- *** auth-plug: startup
[14:54:33] INFO: Successfully send discovery information to Home Assistant.
1649940872: Config loaded from /etc/mosquitto/mosquitto.conf.
1649940872: Loading plugin: /usr/share/mosquitto/auth-plug.so
1649940872:  ├── Username/password checking enabled.
1649940872:  ├── TLS-PSK checking enabled.
1649940872:  └── Extended authentication not enabled.
1649940872: Opening ipv4 listen socket on port 1883.
1649940872: Opening ipv6 listen socket on port 1883.
1649940872: Opening websockets listen socket on port 1884.
1649940873: Opening ipv4 listen socket on port 8883.
1649940873: Opening ipv6 listen socket on port 8883.
1649940873: Opening websockets listen socket on port 8884.
1649940873: Warning: Mosquitto should not be run as root/administrator.
1649940873: mosquitto version 1.6.12 running
1649940873: New connection from 127.0.0.1 on port 1883.
1649940873: Socket error on client <unknown>, disconnecting.
1649940873: New connection from 172.30.32.1 on port 1883.
[14:54:33] INFO: Successfully send service information to the Supervisor.

zigbee2mqtt

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] socat.sh: executing... 
[15:01:32] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing... 
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[15:01:34] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start
> node index.js
Zigbee2MQTT:info  2022-04-14 15:01:41: Logging to console and directory: '/config/zigbee2mqtt/log/2022-04-14.15-01-38' filename: log.txt
Zigbee2MQTT:info  2022-04-14 15:01:41: Starting Zigbee2MQTT version 1.25.0 (commit #unknown)
Zigbee2MQTT:info  2022-04-14 15:01:41: Starting zigbee-herdsman (0.14.20)
Zigbee2MQTT:info  2022-04-14 15:01:42: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2022-04-14 15:01:42: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20220219,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2022-04-14 15:01:42: Currently 0 devices are joined:
Zigbee2MQTT:info  2022-04-14 15:01:42: Zigbee: disabling joining new devices.
Zigbee2MQTT:info  2022-04-14 15:01:42: Connecting to MQTT server at mqtt://172.30.32.1:1883
Zigbee2MQTT:info  2022-04-14 15:01:42: Connected to MQTT server
Zigbee2MQTT:info  2022-04-14 15:01:42: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
Zigbee2MQTT:info  2022-04-14 15:01:42: Started frontend on port 0.0.0.0:8099
Zigbee2MQTT:info  2022-04-14 15:01:42: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
Zigbee2MQTT:info  2022-04-14 15:01:50: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2022-04-14 15:01:51: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{"time":254,"value":true},"status":"ok","transaction":"x7f4k-1"}'

Any suggestions on how to validate that my coordinator is working? Or how more to debug what could be the issue?

MQTT broker configuration:

certfile: fullchain.pem
customize:
  active: false
  folder: mosquitto
keyfile: privkey.pem
logins: []
require_certificate: false

Zigbee2mqtt config:

data_path: /config/zigbee2mqtt
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: '-d -d'
  log: false
mqtt:
  server: mqtt://172.30.32.1:1883
  user: mqtt_user
  password: mqtt_password
serial:
  port: /dev/ttyUSB0

Your coordinator is working, and it’s waiting for devices to join the network:

Zigbee2MQTT:info  2022-04-14 15:01:50: Zigbee: allowing new devices to join.

Are you sure that a) you’re putting the devices in pairing mode correctly and b) they are within range of the coordinator?

z2m also has its own frontend running on port 8099 of whatever IP-address it’s running on.

Yes, I’m sure, as I mentioned, I got to pair to a different gateway, just not one that can operate it.
The plug is about a meter from the coordinator.

The Z2M frontend is working fine, that’s how I allowed discovery, just nothing get’s discovered, ever…
Unfortunately I currently don’t have any other devices I could pair try to pair.

So the devices are showing a blinking blue light when you put them in pairing mode? And the other gateway is turned off (or not in range) when you’re pairing them?

What Zigbee channel is configured for z2m?

Use an USB extension cable, and plug your dongle in an USB-2 port, to keep it away from interference.

1 Like

Yes that is correct. The other gateway pairing mode is disabled during this.

How do I found out what channel is used?

I’ll try this, thank you

In the z2m frontend: Settings > Advanced

channel 11

Looks like this solved it. I have no words :smile: multiple hours spend on a simple interference problem :smiley:

1 Like