I think this hits the nail on the head. A device developer will develop a bluetooth gadget. They test it, it works, but they know it's not great. But they know that when a consumer buys it, none of that matters as long as they buy the product and don't return it.
So the trick is to make sure you have a nice feature set which works well enough so that you can gaslight consumers into thinking the failure is their fault. So if it only works half the time, that's fine. Just tell them to turn their bluetooth off and on or to reboot their device. It'll probably fix it and now they think they are at fault.