mtrudel
commented
3 months ago Flaky pairing is unfortunately a fact of life with HomeKit; 'just try it again' is my usual advice. There are a couple of things to note though:
- Changing the
identifierin your configuration to a new one often helps. iOS seems to cache some aspects of device setup based on this identifier - Waiting a few minutes between attempts in order to let mDNS caches expire often helps
- All of the state in HAP is contained in whatever
data_pathis set to (this depends on the target; see the docs for details). Deleting this and restarting should get you back to a clean state.
Thinking about this, I wonder if a HAP.reset_pairing function would be useful for such cases, that would remove any of the persistent information / pairing data and reset the device to a clean slate. WDYT?
teovoinea
I had setup the demo in nerves livebook and HAP printed the connection code, the Home App identified the accessory, but at connection time a but in my code caused a failure. Ever since, HAP no longer prints the connection code after starting the accessory server. I've tried reflashing, restarting, killing the process.
It's definitely an issue on my end, I just don't know how to reset/restart for debugging purposes.