Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

Smart Bluetooth Forum Discussions

Anonymous
Not applicable

 

After attempt to connect to a Bluetooth address for a peripheral that just powered off (battery died), central can no longer connect to any other powered-up peripherals.  (This would occur if central scans for and detects peripheral, but peripheral then is powered off before central connects to it.)

 

 

Peripheral with Bluetooth address '000000000001' is powered on, and peripheral '000000000002' is powered off.

 

Central connects to P1 okay and gets notifications. Then disconnects.

 

 

Central tries to connect to peripheral '000000000002'. 

 

Central disconnects.

 

 

Central tries to connect to '000000000001' again, but does not even get the connUp callback.

 

 

Why can't central re-connect with peripheral '000000000001' ?

 

 

0 Likes
1 Solution
MichaelF_56
Moderator
Moderator
Moderator
250 sign-ins 25 comments on blog 10 comments on blog

I believe you resolved this issue as part of the discussion here: Re: Why does lower high_scan_interval cause failure to connect?

Let us know if you are still having problems.

View solution in original post

0 Likes
1 Reply
MichaelF_56
Moderator
Moderator
Moderator
250 sign-ins 25 comments on blog 10 comments on blog

I believe you resolved this issue as part of the discussion here: Re: Why does lower high_scan_interval cause failure to connect?

Let us know if you are still having problems.

0 Likes