Unpaired device stays connected

[molnarti]

Does the issue really belong here?

• I definitively want to report a bug within deCONZ or its REST-API

Is there already an existing issue for this?

• I have searched the existing issues and there is none for the bug at hand

Describe the bug

For some reason i cannot unpair the one of the LYWSD03MMC devices from my Conbee.
The unpairing looks good from Phoscon, however i cannot pair it to any coordinator. Also, if i plug in the Conbee into any random USB port, the BT icon on the device disappears, implying its still connected.
And whenever i hit "Add new sensor" in Phoscon, the device just connects back, without putting it into pairng mode first (but does not connect to any other coordinator).
I have successfully unpaired 3 other devices of the same type, but this one is stuck.

I am running Deconz as a baremetal install on my Linux desktop as i have already decommissioned the server it was originally on, so i cannot access Deconz to try to unpair it from there.

Any other ideas how to kick that device from the Conbee for good?

Steps to reproduce the behavior

1. Go to phoscon/sensors
2. Select "sticky" device
3. Delete and confirm
4. Observe the BT indicator on the sensor - its still hidden, indicating persistent connection
5. Pull out the Conbee from USB - BT indicator appears on device
6. Stick back Conbee into USB - BT indicator disappears
7. Add new sensor in Phoscon, without shorting the pins on the sensor to enter pairing mode - device pairs instantly

Expected behavior

Device unpairs and stays disconnected

Screenshots

No response

Environment

• Host system: ArchLinux desktop, but also reproduced in Docker setup on Debian
• Running method: Bare-metal on Arch linux and deconz-docker container
• Firmware version: 0x26720700
• deCONZ version (not Home assistant Addon version!): 2.31.2, also on 2.32
• Device: ConBee II
• Do you use an USB extension cable: tried both
• Is there any other USB or serial devices connected to the host system? If so: UPS via NUT

deCONZ Logs

No response

Additional context

No response

[mattreim]

@molnarti It is not a deCONZ bug; you need to perform a factory reset on your device, just as is necessary with all Zigbee devices before connecting.

[molnarti]

I tried the "factory reset" like a hundred times. It did not work until i unpaired the device from deconz. in the end i was somehow able to unpair from deconz, as the phoscon unpair did not go tough fully apparently.

[Smanar]

As @Mimiix says, you can't "disconnect" a sensor. One time the device is included, it have information to rejoin, the only way is the "factory reset".
Even if you delete it from the database it will be back as unknow device "0xXXXX" name format.

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.