ZBOSS device unable to interview

[Mowglli]

What happened?

I have trouble interviewing new devices. It just hangs at fail on timeout.

What did you expect to happen?

I expected that it would succesfully interview the device. Like it does with example Sonoff ezDongle running ember.

How to reproduce it (minimal and precise)

Configuration: homeassistant: enabled: false mqtt: base_topic: zigbee2mqtt server: mqtt://localhost serial: port: COM11 adapter: ember baudrate: 115200 advanced: channel: 15 log_level: info frontend: enabled: true port: 8080 version: 4 availability: enabled: true active: timeout: 10 passive: timeout: 1500 permit_join: false

mosquitto_pub.exe -h localhost -t "zigbee2mqtt/bridge/request/permit_join" -m "{\"value\": true, \"time\": 254}"

Zigbee2MQTT version

master branch

Adapter firmware version

2.2.5

Adapter

NRF52840 Dongle

Setup

Windows

Debug log

log.log

[kirovilya]

https://www.zigbee2mqtt.io/guide/configuration/logging.html#debugging Please, turn on the debug logs and record the pairing process.

By the logs, the device does not report its endpoints:

[2025-03-18 16:12:52] info: 	zh:controller: Interview for '0xd0cf5efffe03927b' started
[2025-03-18 16:12:52] info: 	z2m: Starting interview of '0xd0cf5efffe03927b'
[2025-03-18 16:12:52] info: 	z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0xd0cf5efffe03927b","ieee_address":"0xd0cf5efffe03927b","status":"started"},"type":"device_interview"}'
[2025-03-18 16:13:13] error: 	zh:zboss:driv: ==> Error: Error: {"commandId":769,"tsn":27} after 10000ms
[2025-03-18 16:13:33] error: 	zh:controller: Interview failed for '0xd0cf5efffe03927b with error 'Error: Interview failed because can not get active endpoints ('0xd0cf5efffe03927b')'
[2025-03-18 16:13:33] error: 	z2m: Failed to interview '0xd0cf5efffe03927b', device has not successfully been paired

Perhaps the connection between the device and the coordinator is poor

[Mowglli]

@kirovilya , Sorry, i have updated the log with debug enabled. The device and dongle is approx. 40 cm from each other. It can also be found here: log.log

[kirovilya]

For some reason, the device descriptor could not be requested - timeout, the device did not respond.

[2025-03-19 09:45:32] debug: 	zh:zboss:uart: --> package type 6, flags 11{"isACK":true,"retransmit":false,"sequence":0,"ACKseq":1,"isFirst":false,"isLast":false}
[2025-03-19 09:45:32] debug: 	zh:zboss:uart: -->  ACK: dead05000611c0
[2025-03-19 09:45:32] debug: 	zh:zboss:uart: --> DATA (2,1,0): dead05000611c0
[2025-03-19 09:45:32] debug: 	zh:zboss:uart: --> [dead05000611c0]
[2025-03-19 09:45:32] debug: 	zh:zboss:uart: <-- FRAME: 00010402180585
[2025-03-19 09:45:32] debug: 	zh:zboss:driv: <== Frame: {"version":0,"type":1,"commandId":516,"tsn":24,"payload":{"category":5,"zdoClusterId":32770,"zdo":[133,null]}}
[2025-03-19 09:45:32] debug: 	zh:zboss: processMessage: {"version":0,"type":1,"commandId":516,"tsn":24,"payload":{"category":5,"zdoClusterId":32770,"zdo":[133,null]}}
[2025-03-19 09:45:32] debug: 	zh:controller: Received ZDO response: clusterId=NODE_DESCRIPTOR_RESPONSE, status=TIMEOUT, payload=undefined

check that there is no interference nearby, for example: USB3 devices, microwaves, Wi-Fi routers. maybe it is worth putting the coordinator on a USB extension cord.

[Mowglli]

@kirovilya, okay thanks, i'll test that later today and then give a report on that.

[Mowglli]

@kirovilya Hello i have been testing today, it didnt help with the suggestions. i have been using NCP host firmware from Nordic Semiconductor from 2.2.1 to 2.2.5, some crashes, some just never finishes interview

[mrrdmr]

@Mowglli Could you try 3.0.0-p1 fw?

[Mowglli]

@mrrdmr How do you program the device with just the hex ? via NRF Connect Desktop ? - Do i need to include a special softdevice version ? :)

[mrrdmr]

@Mowglli I've build uf2 file for flashing via Adafruit Bootloader. You can flash that bootloader and then zboss fw. Or I can build hex later.

[mrrdmr]

Done.

nrf52840dongle_nrf52840_zboss_3.0.0-p1.zip

Hex, Nordic MBR needed to boot.

[Mowglli]

@mrrdmr Thank you! I just tried your firmware, it also fails the interview. The CC2531 and Sonoof eZ Dongle has no problem interviewing the devices. It's a bit odd.

[kirovilya]

@Mowglli what device does not connect? where can I buy it to check?

[Mowglli]

@kirovilya Im using a Danalock V3 BTZB. Im using a NRF52840 Dongle

[kirovilya]

@kirovilya Im using a [Danalock V3 BTZB]

I see. It will be difficult for me to buy one like that.

[Mowglli]

@kirovilya, I see that. I can try buying another zigbee-device and test that. And see if the issue persist.

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

[Szewcson]

I have similar issue. NCP based on nrf25840 dongle and newest ncs-zigbee either can't form the network, or don't see manufacturer and other fields. NCP based on esp32c6 work in the same setup, as well as ember based one. What could be the issue here?

[Den41k92]

Same issue. Using nRF52840 module as NCP with ZBOSS protocol. Interview always fails with Tuya Smart plug Error: Failed to send SIMPLE_DESCRIPTOR_REQUEST(cmd: 517). While same device works fine with with Sonoff Dongle 3.0 Firmware: https://github.com/captainlettuce/zboss_adapter_nice_nano_v2 Zigbee2Mqtt version : 2.6.3

log.log