Hi all,
I am new to this list, so let’s introduce myself. I’m an indie doing contract work for a company which makes after market ignition hardware for classic cars. We made a prototype ignition that is working live in a vehicle that sends out the RPM to an IPhone. We were quite amazed that it just worked with all these high powered sources in between. We use a BlueRadios device.
Anyway, you can understand that security is quite a concern for us going forward with this prototype. That is why we want to enable security and authentication.
I came here by Google with a problem that another subscriber (Arnoldus Antonius) described as:
“However, I run into problems when I remove the pairing information, by going to the Bluetooth section in the Settings app and select "Forget this Device". After doing that, whenever I try to read the characteristic, it either gives me an authentication failure (via the error object in didUpdateValueForCharacteristic) without showing the popup, or I don't get a response at all (ie. didUpdateValueForCharacteristic is not called by the framework).
This ultimately means that when the user would remove the pairing info, that we cannot pair again, rendering the device useless.”
We can work around this problem by removing the pairing info in the BT device. Then the pairing dialog pops up again. But this isn’t always a viable solution, as in our particular use case, this would involve a special user interaction with the car, in order to trigger the clearing of the pairing info. And it would not be possible with a running engine, as that interrupts the Atmel handling the commands on the device to the BLE chip.
Sadly I could not find an answer in the archives. Is there any resolution to this problem?
Thanks,
Rogier