Re: Long running connection requests and iOS peripherals
Re: Long running connection requests and iOS peripherals
- Subject: Re: Long running connection requests and iOS peripherals
- From: Rick Mann <email@hidden>
- Date: Thu, 22 Aug 2013 16:45:34 -0700
I've been using a single reconnect call to get our peripheral to reconnect. Seems to work, but I've only tested it by power-cycling the peripheral, and not for more than a minute or so.
On Aug 22, 2013, at 13:01 , William Henderson <email@hidden> wrote:
> Yep, I've hit this bug as well. But AFAICT, iOS reconnection doesn't work like other devices – even after establishing an encrypted link.
>
> --
> Will
>
> On Thursday, August 22, 2013 at 12:56 PM, Andras Kovi wrote:
>
>> Sure it will not work with non-encrypted connection, but once the connection is encrypted and the devices are paired, iOS devices will be able to find each other. At least this is what I understood from the discussions on this list. I wasn't eager enough to try it myself until now.
>>
>> A bigger issue that I encountered is if the connect/disconnect cycle happens quickly, then iOS (6.1.3) can stuck in the connecting state. This is hard to reproduce but if this is the case, then the connect never succeeds. This is an evil error as it stays latent until you cancel the connect and retry (in which case it succeeds immediately). I'm just mentioning so that if you encounter this phenomenon, then know you're not alone with it.
>>
>> Andras
>>
>>
>> On 2013.08.22., at 19:04, William Henderson <email@hidden> wrote:
>>
>>> The docs explain the use of long running connections in the case of a BTLE door lock:
>>>> When the user leaves home, the iOS device may eventually become out of range of the lock, causing the connection to the lock to be lost. At this point, the app can simply call the connectPeripheral:options: method of the CBCentralManager class, and because connection requests do not time out, the iOS device will reconnect when the user returns home.
>>> This sounds great, but this doesn't seem to work with iOS-based peripherals because of the rotating UDID/CBPeripheral scheme. Hence, in this case you need to advertise and scan continuously. Can anyone comment on this?
>>>
>>> William
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Bluetooth-dev mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent to email@hidden
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Bluetooth-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
--
Rick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden