Repository navigation
Port pairing to the SDK 0.4.0 draft contract - #11
Merged
Merged
Conversation
Drop pending_pairings.json and resuming unsaved pairings: the Hub's unpair(draft) removes the pairing from the accessory instead.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ports the integration to the SDK 0.4.0 pairing contract. Part of one change across the SDK, the Hub and the 5 integrations; needs the SDK released first.
physical_id; the Hub ownsid.unpairdoubles as the rollback of a failed pairing, undoing only what blocks a clean re-pair, and is safe to call again.pair_deviceconfirms state a failed attempt left behind instead of refusing it.physical_id=by keyword.Tested: unit tests (41 passed). Reviewed.
Depends on MajorDom-Systems/integration-sdk#21.