So the bug that I was worried about turned out to be fairly easy to track down and squash, thankfully. However I don’t understand why it’s happening in the first place, but I think it’s probably because I don’t understand the Bluetooth 4.0 spec as well as I thought. More studying is ahead…