Devices leave network right after (successful) interview

[adriaandotcom]

What happened?

I replaced my CONBEE II stick with the SLZB-06M. I upgraded z2m to 2.0.0. I'm re-pairing all my devices. The first few succeeded, the others don't. Now I can't pair any more devices.

What did you expect to happen?

It stayed on the network after joining.

How to reproduce it (minimal and precise)

• Allow joining
• Pair Tuya MTG235-ZB-RL (press reset button 5 seconds)
• Watch the logs (it joins and leaves right after)

Zigbee2MQTT version

2.0.0 commit: unknown

Adapter firmware version

7.4.5 [GA]

Adapter

SLZB-06M core v2.3.6, zigbee 20241127 (both EZSP & ember)

Setup

Home Assistant OS on Intel NUC

Debug log

info 2025-01-04 22:08:08z2m: Zigbee: allowing new devices to join.
info 2025-01-04 22:08:08zh:ember: [STACK STATUS] Network opened.
info 2025-01-04 22:08:09z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{"time":254},"status":"ok","transaction":"3w024-1"}'
info 2025-01-04 22:08:23zh:controller: Interview for '***' started
info 2025-01-04 22:08:23z2m: Device '***' joined
info 2025-01-04 22:08:23z2m: Starting interview of '***'
info 2025-01-04 22:08:23z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"***","ieee_address":"***"},"type":"device_joined"}'
info 2025-01-04 22:08:23z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"***","ieee_address":"***","status":"started"},"type":"device_interview"}'
info 2025-01-04 22:08:23z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"***","ieee_address":"***"},"type":"device_announce"}'
warning 2025-01-04 22:08:25z2m: Device '***' left the network
info 2025-01-04 22:08:25z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"***","ieee_address":"***"},"type":"device_leave"}'
error 2025-01-04 22:08:28zh:controller: Interview failed for '*** with error 'Error: DatabaseEntry with ID '2' does not exist'

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: {}
serial:
  port: tcp://192.168.0.94:6638
  baudrate: 115200
  adapter: ember
  rtscts: false
advanced:
  transmit_power: 20

Related? #25826

[adriaandotcom]

I did a full reset of the system (remove zigbee2mqtt folder, reinstall addon), now it seems to work.

[adriaandotcom]

Re-paired my whole network without problems. Then one device I wanted to repair again. That is causing the same error as above. Luckily the other devices are paired now. But I can't pair this one device anymore. It gives the same errors as in the description of this issue. I more debug info is needed, let me know.

info 2025-01-05 02:11:27zh:controller: Interview for '***' started
info 2025-01-05 02:11:27z2m: Device '***' joined
info 2025-01-05 02:11:27z2m: Starting interview of '***'
info 2025-01-05 02:11:27z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"***","ieee_address":"***"},"type":"device_joined"}'
info 2025-01-05 02:11:27z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"***","ieee_address":"***","status":"started"},"type":"device_interview"}'
warning 2025-01-05 02:11:28z2m: Device '***' left the network
info 2025-01-05 02:11:28z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"***","ieee_address":"***"},"type":"device_leave"}'
error 2025-01-05 02:11:28zh:controller: Interview failed for '*** with error 'Error: DatabaseEntry with ID '38' does not exist'

SLZB-06M config:

• Zigbee Coordinator: 20241127
• Core firmware version: v2.3.6
• 

[nbrownus]

Having the exact same issue. This device was bound to another device, I wonder if despite a factory reset that the binding is still being reported when interviewed and since z2m doesn't know anything about the other device that it's triggering the problem?

I was able to exclude the device and after an air-gapped restart it was able to pair.

[adriaandotcom]

It's indeed when a device was connected before. A full restart of the system didn't help for me. When I (force) remove a device from the network, I'm unable to add it again.

[adriaandotcom]

When re-pairing devices multiple times, I get them to pair. Enabling the Permit join (All) button after putting the device in pair mode seems to work more consistently.

It might be an issue in my network only, because I have 12 Tuya MTG235-ZB-RL devices that send a payload every second. But I think it's an issue between zigbee2mqtt and the SLZB-06M coordinator.

[kolopeter221]

coordinator SLZB-06M and 10 modules.
3 modules behaved the same as in the title.
They appeared and disappeared. it was impossible to complete the configuration.
Coordinator was set to channel 25. I changed the channel to 11 and the configuration of the first module was successful. But the rest of the modules were offline, so I restored channel 25 and searched for the first "problematic" module again. With success. Later I added the remaining two without any combinations and problems

[FriendlyFireDavid]

I'm reporting a similar problem.

I have a rather large network with 140 devices running for years now.
Yesterday, I wanted to install 3 new IKEA bulbs.
The first one paired normally and works.
Second pairs but then immediately leaves the network (sometimes with a notification, sometimes without).
Then I tried several new bulbs of the same type (new from the box), but all leave the network after pairing.

Funny thing is that after it pairs successfully, I can control it for a few seconds, but then it flashes and leaves the network.

I've tried to pair the 3rd Reality sensor after this, and I can pair and work normally.
I'll later try with other devices too (different from IKEA) to see if it's going to be any different.

Zigbee2MQTT version: 2.2.1 commit: unknown
Coordinator: Sonoff USB Dongle P (TI CC2652)
Coordinator type: zStack3x0
Coordinator revision: 20240710
Setup: Home Assistant OS on Lenovo ThinkCentre, updated to latest version

[github-actions]

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