[FIXED] Zigbee2mqtt can not pair

Tags: #<Tag:0x00007fc3f4536618>

Hi

I got a USB stick with 2531, flashed it as described on zigbee2mqtt.io, all went ok.
On hassio, I’ve installed the most recent zigbee2mqtt addon 1.5.1 (also tried with zigbee2mqtt-edge)

All configs done, but can not pair non of my xiaomi sensors (tried several door and temperature sensors, absolutely new and those which was paired already to mi home) nothing working.

The pairing (permit_join) is enabled, enabled in lovelace as well, connecting to mqtt broker correctly, but not getting the devices ( the sensors are in reset mode with slow flashing led as described on zigbee2mqtt.io)

here’s my log:


./run.sh: line 16: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
2019-09-02T01:21:23: PM2 log: Launching in no daemon mode
2019-09-02T01:21:23: PM2 log: App [npm:0] starting in -fork mode-
2019-09-02T01:21:23: PM2 log: App [npm:0] online
> [email protected] start /zigbee2mqtt-1.5.1
> node index.js
  zigbee2mqtt:info 9/2/2019, 1:21:25 AM Logging to directory: '/share/zigbee2mqtt/log/2019-09-02.01-21-24'
  zigbee2mqtt:info 9/2/2019, 1:21:25 AM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
  zigbee2mqtt:info 9/2/2019, 1:21:25 AM Starting zigbee-shepherd
  zigbee2mqtt:info 9/2/2019, 1:21:26 AM zigbee-shepherd started
  zigbee2mqtt:info 9/2/2019, 1:21:26 AM Coordinator firmware version: '20190619'
  zigbee2mqtt:info 9/2/2019, 1:21:26 AM Currently 0 devices are joined:
  zigbee2mqtt:warn 9/2/2019, 1:21:26 AM `permit_join` set to  `true` in configuration.yaml.
  zigbee2mqtt:warn 9/2/2019, 1:21:26 AM Allowing new devices to join.
  zigbee2mqtt:warn 9/2/2019, 1:21:26 AM Set `permit_join` to `false` once you joined all devices.
  zigbee2mqtt:info 9/2/2019, 1:21:26 AM Zigbee: allowing new devices to join.
  zigbee2mqtt:info 9/2/2019, 1:21:26 AM Connecting to MQTT server at mqtt://core-mosquitto
  zigbee2mqtt:info 9/2/2019, 1:21:26 AM zigbee-shepherd ready
  zigbee2mqtt:info 9/2/2019, 1:21:27 AM Connected to MQTT server
  zigbee2mqtt:info 9/2/2019, 1:21:27 AM MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
  zigbee2mqtt:info 9/2/2019, 1:21:27 AM MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.5.1","commit":"unknown","coordinator":20190619,"log_level":"info","permit_join":true}'
  zigbee2mqtt:info 9/2/2019, 1:22:52 AM Zigbee: allowing new devices to join.
  zigbee2mqtt:info 9/2/2019, 1:22:52 AM MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.5.1","commit":"unknown","coordinator":20190619,"log_level":"info","permit_join":true}'
  zigbee2mqtt:info 9/2/2019, 1:25:32 AM Successfully reenabled joining
  zigbee2mqtt:info 9/2/2019, 1:28:12 AM Successfully reenabled joining
  zigbee2mqtt:info 9/2/2019, 1:30:52 AM Successfully reenabled joining
  zigbee2mqtt:info 9/2/2019, 1:32:53 AM Zigbee: disabling joining new devices.
  zigbee2mqtt:info 9/2/2019, 1:32:53 AM MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.5.1","commit":"unknown","coordinator":20190619,"log_level":"info","permit_join":false}'
  zigbee2mqtt:info 9/2/2019, 1:32:53 AM Zigbee: disabling joining new devices.
  zigbee2mqtt:info 9/2/2019, 1:32:53 AM MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.5.1","commit":"unknown","coordinator":20190619,"log_level":"info","permit_join":false}'
  zigbee2mqtt:info 9/2/2019, 1:32:55 AM Zigbee: allowing new devices to join.
  zigbee2mqtt:info 9/2/2019, 1:32:55 AM MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.5.1","commit":"unknown","coordinator":20190619,"log_level":"info","permit_join":true}'
  zigbee2mqtt:info 9/2/2019, 1:35:35 AM Successfully reenabled joining

Validated those sensors with xiaomi hub and they paired within a second.

Tried to flash the stick with CC2531_DEFAULT_20190608.zip and also with CC2531_DEFAULT_20190608.zip, absolutely the same behavior.

Can somebody help?

These things rarely work for me at 1.30AM either.

There is no sign of any zigbee activity at all in the period when joining was allowed. What exactly did you to to the sensors, and which sensors are they?

You’re about 1:30AM but tried today morning as well and nothing changed))

Anyway, I’ve tried to pair xiaomi door sensor (MCCGQ11LM) and xiaomi temp/humidity sensor (WSDCGQ11LM).

Attaching video showing how I use the pair of temp sensor:

Are you nice and close to the co-ordinator?

I’m nice) and was trying to pair when sensor is <5 cm from the USB stick.

1 Like

Tried flashing again with recommended FW CC2531_DEFAULT_20190608.zip
Still nothing

Can you tell how I can sniff zigbee signals with this stick?
For me it looks like the USB stick is working but without zigbee functionality…

You are unzipping the file first.

Don’t you think the flash will fail if I will NOT unzip the files?
Or will I see the FW version as I showed in my logs?

Anyway,
some magic happened… Yesterday (and also today) I was trying to switch between 2 usb ports and I wasn’t able to get any zigbee activity. But at the end, I just in case, decided to try to put it in additional, other (3 from 4) usb port and it started to work just perfect!

Pairing fine within long distance as well no problem.

According to the docs, you specify the port in the config file. The default is /dev/ttyACM0

# Required: serial settings
serial:
  # Required: location of CC2531 USB sniffer
  port: /dev/ttyACM0

Step 1 of the configuration instructions explains how to confirm which port the CC2531 is connected to and is the recommended procedure for identifying the port (as opposed to playing ‘port-roulette’).

FWIW, if you have more than one USB-connected device, Linux may re-map the ports on startup (there are ways to mitigate this behavior) … and that may cause you to play ‘port-roulette’ again.

If I had a problem with the port I would never get the FW version…

If you’re claiming you never had a problem with the port then your post marked as solution is misleading because it claims that changing ports fixed the problem.

Read my post.
I changed PHYSICAL USB PORT.
And yes, after I changed usb port the mapping is still remain /dev/ttyACM0

That’s how I understood it; you plugged the CC2531 into the available PHYSICAL ports until you found one that resolved the issue.

If you have only one device connected to the USB bus, that gambit will work (the first physically connected device is assigned ttyACM0). It won’t if there are several devices connected due to the way ports are dynamically mapped at startup.

Nope, you’re wrong.
It is logical enumeration.
Try connecting regular usb flash and check how it detected (for example sdb). Remove it, and put in other usb port. Check again how your usb appears now.

And regarding my issue, the port (logical) was configured just fine. Mostly probably that particular usb ports got not enough electrical power to feed the stick.

It’s what I’m saying but, apparently, not effectively. Regardless, there’s something peculiar about the notion that a (physical) USB port that can successfully transfer the CC2531’s entire firmware but then stumble with the operation of pairing devices. Odd.

Probably there’s enough power to read the FW from the chip but not enough to power zigbee interface…

That’s an interesting theory, implying there’s sufficient voltage (to allow the circuitry to minimally function) but insufficient current (to drive all of the circuitry when in full operation). Given that USB ports are sourced by a common power bus, the deficiency would affect more than one port. You did mention that two ports were affected whereas the other two were not. Perhaps the other two are connected to a separate bus.

yes, exactly, checked now in the schematics and looks like different buses…

Maybe your CC2531 is faulty?
e.g. perhaps the RF frontend is damaged and the zigbee processor thinks its listening but in reality will never receive a signal.

This is consistent the above.
The cc2351 is powered up and its microcontroller is operating and communicating via USB, but not able to communicate via 2.4ghz zigbee…

Also this said I have had much difficulty pairing some new devices with z2m 1.5.1.

Once moved to other physical usb port all working perfect so far.

1 Like