Here we have set up the accessory via Accessory Setup Kit only, and later managing the connection from CoreBluetooth(not scanning). Could you help us what leads to central reporting PoweredOff when we try to discover a new accessory that too via Accessory Setup Kit in the same app. NOTE: It reports that state only only when the Accessory picker stays for upto 10 secs. Also if this is designed like this, Is there any recovery mechanism to connect back to the first persisted device back?

Here we have set up the accessory via Accessory Setup Kit only, and later managing the connection from CoreBluetooth(not scanning). Could you help us what leads to central reporting PoweredOff when we try to discover a new accessory that too via Accessory Setup Kit in the same app. NOTE: It reports that state only only when the Accessory picker stays for upto 10 secs. Also if this is designed like this, Is there any recovery mechanism to connect back to the first persisted device back?

Here we have set up the accessory via Accessory Setup Kit only, and later managing the connection from CoreBluetooth(not scanning). Could you help us what leads to central reporting PoweredOff when we try to discover a new accessory that too via Accessory Setup Kit in the same app. NOTE: It reports PoweredOff that state only when the Accessory picker stays for upto 10 secs.

Here we have set up the accessory via Accessory Setup Kit only, and later managing the connection from CoreBluetooth(not scanning). Could you help us what leads to central reporting PoweredOff when we try to discover a new accessory that too via Accessory Setup Kit in the same app. NOTE: It reports PoweredOff that state only when the Accessory picker stays for upto 10 secs.

Here we have set up the accessory via Accessory Setup Kit only, and later managing the connection from CoreBluetooth(not scanning). Could you help us what leads to central reporting PoweredOff when we try to discover a new accessory that too via Accessory Setup Kit in the same app. NOTE: It reports PoweredOff that state only when the Accessory picker stays for upto 10 secs. Also if this is designed like this, Is there any recovery mechanism to connect back to the first persisted device back?

Here we have set up the accessory via Accessory Setup Kit only, and later managing the connection from CoreBluetooth(not scanning). Could you help us what leads to central reporting PoweredOff when we try to discover a new accessory that too via Accessory Setup Kit in the same app. NOTE: It reports PoweredOff that state only when the Accessory picker stays for upto 10 secs.