Xiaomi plug suddenly disconnected

Hello all,
this is my first post. I am using the deCONZ docker community image of on a Raspberry Pi 4 with ConBee II and some Xiami equipment in conjunction with openHAB.

grafik

For several months my LUMI sensors and one Smart Plug were running quite well. A few weeks ago the Smart Plug was no longer connected and so the sensors that need the plug to reach the mesh, were also gone. I tried multiple ways to get it reconnected without success.

I now updated the Phoscon application to version 2.17.01 but nothing changed. Then I removed the Smart Plug from the gateway, pressed “learn new lights” and pressed the plug’s switch long until the blue LED was flashing. Just some moments later the plug appeared and I was happy. In openHAB I needed to change the device Id and then the plug and the sensors were connected successfully. After that success I updated the firmware to version 26720700.

The next day the Smart Plug was gone again. I tried several steps again without success. So the symptoms are similar to the scope of this thread.

18:53:53:709 Mgmt_Lqi_req zdpSeq: 114 to 0x00212EFFFF06C0D7 start index 0
18:53:53:710 APS-DATA.request id: 146, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:53:53:722 APS-DATA.confirm id: 146, status: 0x00 SUCCESS
18:53:53:722 APS-DATA.confirm request id: 146 -> confirmed, timeout 0
18:53:53:726 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:53:53:726 APS-DATA.indication request id: 146 -> finished
18:53:53:727 APS-DATA.request id: 146 erase from queue
18:53:53:728 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:53:53:728 ZDP Mgmt_Lqi_rsp zdpSeq: 114 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:53:53:729     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:53:57:550 Mgmt_Lqi_req zdpSeq: 115 to 0x00212EFFFF06C0D7 start index 0
18:53:57:551 APS-DATA.request id: 163, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:53:57:562 APS-DATA.confirm id: 163, status: 0x00 SUCCESS
18:53:57:563 APS-DATA.confirm request id: 163 -> confirmed, timeout 0
18:53:57:566 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:53:57:567 APS-DATA.indication request id: 163 -> finished
18:53:57:568 APS-DATA.request id: 163 erase from queue
18:53:57:568 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:53:57:569 ZDP Mgmt_Lqi_rsp zdpSeq: 115 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:53:57:570     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:01:390 Mgmt_Lqi_req zdpSeq: 116 to 0x00212EFFFF06C0D7 start index 0
18:54:01:391 APS-DATA.request id: 181, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:01:404 APS-DATA.confirm id: 181, status: 0x00 SUCCESS
18:54:01:405 APS-DATA.confirm request id: 181 -> confirmed, timeout 0
18:54:01:408 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:01:409 APS-DATA.indication request id: 181 -> finished
18:54:01:410 APS-DATA.request id: 181 erase from queue
18:54:01:410 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:01:411 ZDP Mgmt_Lqi_rsp zdpSeq: 116 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:01:411     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:05:230 Mgmt_Lqi_req zdpSeq: 117 to 0x00212EFFFF06C0D7 start index 0
18:54:05:231 APS-DATA.request id: 198, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:05:239 APS-DATA.confirm id: 198, status: 0x00 SUCCESS
18:54:05:241 APS-DATA.confirm request id: 198 -> confirmed, timeout 0
18:54:05:249 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:05:251 APS-DATA.indication request id: 198 -> finished
18:54:05:251 APS-DATA.request id: 198 erase from queue
18:54:05:252 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:05:253 ZDP Mgmt_Lqi_rsp zdpSeq: 117 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:05:254     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:07:053 APS-DATA.request id: 207, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
18:54:07:055 send permit join, duration: 65
18:54:07:055 APS-DATA.request id: 208, addrmode: 0x02, addr: 0xfffc, profile: 0xA1E0, cluster: 0x0021, ep: 0xF2 -> 0xF2 queue: 1 len: 6 tx.options 0x00
18:54:07:056 Delay APS request id: 208 to 0xFFFC, profile: 0xA1E0 cluster: 0x0021 node already has busy 1
18:54:07:106 Delay APS request id: 208 to 0xFFFC, profile: 0xA1E0 cluster: 0x0021 node already has busy 1
18:54:07:154 Delay APS request id: 208 to 0xFFFC, profile: 0xA1E0 cluster: 0x0021 node already has busy 1
18:54:07:201 APS-DATA.confirm id: 207, status: 0xE1 
18:54:07:313 APS-DATA.confirm id: 208, status: 0xE1 
18:54:09:069 Mgmt_Lqi_req zdpSeq: 118 to 0x00212EFFFF06C0D7 start index 0
18:54:09:070 APS-DATA.request id: 218, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:09:081 APS-DATA.confirm id: 218, status: 0x00 SUCCESS
18:54:09:082 APS-DATA.confirm request id: 218 -> confirmed, timeout 0
18:54:09:085 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:09:086 APS-DATA.indication request id: 218 -> finished
18:54:09:086 APS-DATA.request id: 218 erase from queue
18:54:09:087 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:09:087 ZDP Mgmt_Lqi_rsp zdpSeq: 118 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:09:088     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:12:910 Mgmt_Lqi_req zdpSeq: 119 to 0x00212EFFFF06C0D7 start index 0
18:54:12:911 APS-DATA.request id: 235, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:12:922 APS-DATA.confirm id: 235, status: 0x00 SUCCESS
18:54:12:923 APS-DATA.confirm request id: 235 -> confirmed, timeout 0
18:54:12:926 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:12:927 APS-DATA.indication request id: 235 -> finished
18:54:12:928 APS-DATA.request id: 235 erase from queue
18:54:12:929 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:12:929 ZDP Mgmt_Lqi_rsp zdpSeq: 119 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:12:930     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:16:749 Mgmt_Lqi_req zdpSeq: 120 to 0x00212EFFFF06C0D7 start index 0
18:54:16:750 APS-DATA.request id: 252, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:16:761 APS-DATA.confirm id: 252, status: 0x00 SUCCESS
18:54:16:762 APS-DATA.confirm request id: 252 -> confirmed, timeout 0
18:54:16:765 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:16:766 APS-DATA.indication request id: 252 -> finished
18:54:16:766 APS-DATA.request id: 252 erase from queue
18:54:16:767 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:16:767 ZDP Mgmt_Lqi_rsp zdpSeq: 120 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:16:768     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:20:590 Mgmt_Lqi_req zdpSeq: 121 to 0x00212EFFFF06C0D7 start index 0
18:54:20:591 APS-DATA.request id: 14, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:20:602 APS-DATA.confirm id: 14, status: 0x00 SUCCESS
18:54:20:604 APS-DATA.confirm request id: 14 -> confirmed, timeout 0
18:54:20:606 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:20:607 APS-DATA.indication request id: 14 -> finished
18:54:20:608 APS-DATA.request id: 14 erase from queue
18:54:20:609 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:20:609 ZDP Mgmt_Lqi_rsp zdpSeq: 121 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:20:610     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:24:429 Mgmt_Lqi_req zdpSeq: 122 to 0x00212EFFFF06C0D7 start index 0
18:54:24:430 APS-DATA.request id: 31, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:24:441 APS-DATA.confirm id: 31, status: 0x00 SUCCESS
18:54:24:441 APS-DATA.confirm request id: 31 -> confirmed, timeout 0
18:54:24:444 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:24:444 APS-DATA.indication request id: 31 -> finished
18:54:24:445 APS-DATA.request id: 31 erase from queue
18:54:24:445 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:24:445 ZDP Mgmt_Lqi_rsp zdpSeq: 122 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:24:445     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:28:269 Mgmt_Lqi_req zdpSeq: 123 to 0x00212EFFFF06C0D7 start index 0
18:54:28:270 APS-DATA.request id: 48, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:28:282 APS-DATA.confirm id: 48, status: 0x00 SUCCESS
18:54:28:283 APS-DATA.confirm request id: 48 -> confirmed, timeout 0
18:54:28:286 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:28:287 APS-DATA.indication request id: 48 -> finished
18:54:28:287 APS-DATA.request id: 48 erase from queue
18:54:28:288 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:28:288 ZDP Mgmt_Lqi_rsp zdpSeq: 123 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:28:289     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:32:110 Mgmt_Lqi_req zdpSeq: 124 to 0x00212EFFFF06C0D7 start index 0
18:54:32:111 APS-DATA.request id: 66, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:32:122 APS-DATA.confirm id: 66, status: 0x00 SUCCESS
18:54:32:123 APS-DATA.confirm request id: 66 -> confirmed, timeout 0
18:54:32:126 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:32:127 APS-DATA.indication request id: 66 -> finished
18:54:32:128 APS-DATA.request id: 66 erase from queue
18:54:32:128 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:32:129 ZDP Mgmt_Lqi_rsp zdpSeq: 124 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:32:130     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:35:949 Mgmt_Lqi_req zdpSeq: 125 to 0x00212EFFFF06C0D7 start index 0
18:54:35:950 APS-DATA.request id: 83, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:35:961 APS-DATA.confirm id: 83, status: 0x00 SUCCESS
18:54:35:961 APS-DATA.confirm request id: 83 -> confirmed, timeout 0
18:54:35:965 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:35:965 APS-DATA.indication request id: 83 -> finished
18:54:35:966 APS-DATA.request id: 83 erase from queue
18:54:35:967 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:35:967 ZDP Mgmt_Lqi_rsp zdpSeq: 125 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:35:968     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:39:789 Mgmt_Lqi_req zdpSeq: 126 to 0x00212EFFFF06C0D7 start index 0
18:54:39:790 APS-DATA.request id: 100, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:39:801 APS-DATA.confirm id: 100, status: 0x00 SUCCESS
18:54:39:802 APS-DATA.confirm request id: 100 -> confirmed, timeout 0
18:54:39:805 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:39:806 APS-DATA.indication request id: 100 -> finished
18:54:39:807 APS-DATA.request id: 100 erase from queue
18:54:39:807 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:39:808 ZDP Mgmt_Lqi_rsp zdpSeq: 126 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:39:808     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:43:630 Mgmt_Lqi_req zdpSeq: 127 to 0x00212EFFFF06C0D7 start index 0
18:54:43:631 APS-DATA.request id: 118, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:43:643 APS-DATA.confirm id: 118, status: 0x00 SUCCESS
18:54:43:644 APS-DATA.confirm request id: 118 -> confirmed, timeout 0
18:54:43:648 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:43:649 APS-DATA.indication request id: 118 -> finished
18:54:43:650 APS-DATA.request id: 118 erase from queue
18:54:43:650 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:43:651 ZDP Mgmt_Lqi_rsp zdpSeq: 127 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:43:652     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:47:469 Mgmt_Lqi_req zdpSeq: 128 to 0x00212EFFFF06C0D7 start index 0
18:54:47:470 APS-DATA.request id: 135, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:47:481 APS-DATA.confirm id: 135, status: 0x00 SUCCESS
18:54:47:482 APS-DATA.confirm request id: 135 -> confirmed, timeout 0
18:54:47:485 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:47:486 APS-DATA.indication request id: 135 -> finished
18:54:47:487 APS-DATA.request id: 135 erase from queue
18:54:47:487 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:47:488 ZDP Mgmt_Lqi_rsp zdpSeq: 128 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:47:488     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:47:584 Device TTL 6840 s flags: 0x7
18:54:51:310 Mgmt_Lqi_req zdpSeq: 129 to 0x00212EFFFF06C0D7 start index 0
18:54:51:311 APS-DATA.request id: 153, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:51:323 APS-DATA.confirm id: 153, status: 0x00 SUCCESS
18:54:51:324 APS-DATA.confirm request id: 153 -> confirmed, timeout 0
18:54:51:327 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:51:328 APS-DATA.indication request id: 153 -> finished
18:54:51:329 APS-DATA.request id: 153 erase from queue
18:54:51:329 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:51:330 ZDP Mgmt_Lqi_rsp zdpSeq: 129 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:51:330     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:53:554 GW firmware version is up to date: 0x26720700
18:54:55:149 Mgmt_Lqi_req zdpSeq: 130 to 0x00212EFFFF06C0D7 start index 0
18:54:55:150 APS-DATA.request id: 170, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:55:162 APS-DATA.confirm id: 170, status: 0x00 SUCCESS
18:54:55:163 APS-DATA.confirm request id: 170 -> confirmed, timeout 0
18:54:55:166 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:55:167 APS-DATA.indication request id: 170 -> finished
18:54:55:168 APS-DATA.request id: 170 erase from queue
18:54:55:169 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:55:169 ZDP Mgmt_Lqi_rsp zdpSeq: 130 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:55:170     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:54:58:992 Mgmt_Lqi_req zdpSeq: 131 to 0x00212EFFFF06C0D7 start index 0
18:54:58:993 APS-DATA.request id: 187, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:54:58:005 APS-DATA.confirm id: 187, status: 0x00 SUCCESS
18:54:58:006 APS-DATA.confirm request id: 187 -> confirmed, timeout 0
18:54:58:009 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:54:58:010 APS-DATA.indication request id: 187 -> finished
18:54:58:011 APS-DATA.request id: 187 erase from queue
18:54:58:011 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:54:58:012 ZDP Mgmt_Lqi_rsp zdpSeq: 131 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:54:58:012     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:55:02:830 Mgmt_Lqi_req zdpSeq: 132 to 0x00212EFFFF06C0D7 start index 0
18:55:02:831 APS-DATA.request id: 205, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:55:02:844 APS-DATA.confirm id: 205, status: 0x00 SUCCESS
18:55:02:845 APS-DATA.confirm request id: 205 -> confirmed, timeout 0
18:55:02:849 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 221, rssi: 30
18:55:02:850 APS-DATA.indication request id: 205 -> finished
18:55:02:850 APS-DATA.request id: 205 erase from queue
18:55:02:853 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:55:02:854 ZDP Mgmt_Lqi_rsp zdpSeq: 132 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:55:02:854     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:55:06:670 Mgmt_Lqi_req zdpSeq: 133 to 0x00212EFFFF06C0D7 start index 0
18:55:06:671 APS-DATA.request id: 222, addrmode: 0x03, addr: 0x00212effff06c0d7, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 0 len: 2 tx.options 0x00
18:55:06:683 APS-DATA.confirm id: 222, status: 0x00 SUCCESS
18:55:06:684 APS-DATA.confirm request id: 222 -> confirmed, timeout 0
18:55:06:687 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 0, rssi: 0
18:55:06:688 APS-DATA.indication request id: 222 -> finished
18:55:06:689 APS-DATA.request id: 222 erase from queue
18:55:06:689 ZDP 0x00212EFFFF06C0D7 cluster: 0x8031 status = 0x00 -> SUCCESS
18:55:06:690 ZDP Mgmt_Lqi_rsp zdpSeq: 133 from 0x00212EFFFF06C0D7 total: 1, startIndex: 0, listCount: 1
18:55:06:691     * neighbor: 0x00158D0004620FCD (0x3728), LQI: 255, relation: 0x01, depth: 1, rxOnWHenIdle: 0
18:55:08:054 APS-DATA.request id: 229, addrmode: 0x02, addr: 0xfffc, profile: 0x0000, cluster: 0x0036, ep: 0x00 -> 0x00 queue: 0 len: 3 tx.options 0x00
18:55:08:055 send permit join, duration: 65

I activated all debug parameters, so the log is rather big. I only pasted the latest 2 minutes.
Thanks for any help!

Regards Christoph

I’ve moved your post to a seperate topic.

Hello again,

yesterday I was browsing through other issues in this forum and read about interferences, that might come up when the ConBeeII ist connected via USB3. I remembered that from the early times working with ConBeeII and deCONZ, but in the meantime this knowledge must have been gone…

My stick was indeed mounted via USB3 connection over a USB3 hub. So I changed the plugs accordingly and they were still recognized by deCONZ, because of my udev rules and the right mapping in the docker container, that I applied just the day before. I tried to pair the Smart Plug in the same room as the gateway and it was recognized instantly. Even after moving the plug back to its intended position in the washing machine room, its war working as expected. I was happy!

Today the Smart Plug lost the connection again. Now I started to investigate the deCONZ UI a little deeper and levered up the position of the ConBeeII stick in my working room, where the raspi4 is running. I once again removed the Smart Plug and tried a new pairing. It reappeared now with device ID 3. Updating this in openHAB was easy to do. All devices are now connected and the more fare ones are not going over the Smart Plug any more. You can see them marked red in the graph with a rather high LQI:


With this knowledge I expect they will now keep working even without the Smart Plug, so one risk seem to be removed. The Smart Plug itself has now an LQI about 80, may be this will be enough? We will see.

Do you confirm my conclusion? Have you any further ideas for optimization?

Thanks again, the forum put me on the right track!

Regards Christoph