Zigbee logging

Hi,

Anyone seen this before? I know zigbee devices can drop offline etc, and Xiaomi are classic examples. But I haven't seen this, or perhaps its the first time its been caught.

One of my Xiaomi buttons, which I'd re-paired this afternoon (I'd been doing some channel organizing), became known as "20B3" in the Zigbee logging, its also not executing what it should. It was checking in fine, and appears to still do so but without its Device name, which has now changed.

20B32018-10-09 18:11:30.542 profileId:0x104, clusterId:0x0, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:239, lastHopRssi:-72
20B32018-10-09 17:50:18.173 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-74
20B32018-10-09 17:50:18.071 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-75
20B32018-10-09 17:50:16.681 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-73
20B32018-10-09 17:50:16.579 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-74
20B32018-10-09 17:50:14.913 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-75
20B32018-10-09 17:50:14.811 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-74
20B32018-10-09 17:50:12.686 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-74
20B32018-10-09 17:50:12.484 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:226, lastHopRssi:-73
20B32018-10-09 17:09:45.846 profileId:0x104, clusterId:0x0, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-76
20B32018-10-09 16:09:29.913 profileId:0x104, clusterId:0x0, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-77
Sofa Button 12018-10-09 14:32:32.828 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-78
Sofa Button 12018-10-09 14:32:32.620 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-77
Sofa Button 12018-10-09 14:32:30.854 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-77

Has anyone else seen this, or know whats going on. Or has it simply not connected well in the first place?

Cheers