feat: add Kisi locks brand guide#1254
Open
dawnho wants to merge 1 commit into
Open
Conversation
Documents the Phase 1 Kisi integration (cloud access control) whose doors appear as `kisi_lock` devices supporting remote unlock. Includes overview, setup guide, 5-step getting-started tutorial in all 7 SDK languages, and sandbox credentials, plus a clearly-labeled Planned Capabilities section for cloud keys, access grants, mobile keys, and cards. - Adds overview, setup guide, getting-started, and sandbox pages under device-and-system-integration-guides/kisi-locks/ - Updates docs.json nav, brand-guides index card, and SUMMARY.mdx Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Summary
Adds a brand integration guide for Kisi cloud access control. Kisi's doors are modeled as
kisi_lockdevices (the device/lock path), and the currently shipped capability is remote unlock only — Kisi has no remote re-lock endpoint and no keypad access codes.index.mdx) — what Kisi is, supported devices, supported features (unlock),kisidevice provider key, brand-specific restrictions, and a clearly-labeled Planned Capabilities section (cloud keys, access grants, mobile keys, cards) marked as not yet availablekisi-setup-guide.mdx) — how to generate a Kisi API key (My Account → API), connect via Connect Webview, verify, and troubleshootget-started-with-kisi-locks.mdx) — install → connect with API key → retrieve devices → unlock, in all 7 SDK languagessandbox-kisi-locks.mdx) — sandbox API keyfake_kisi_api_keydocs.jsonnav, brand-guides index card, andSUMMARY.mdx(alphabetical, between KeyInCode and Kwikset)Discovered from the
feat/kisi-providerbranch in seam-connect (Phase 1): provider keykisi, device typekisi_lock,can_remotely_unlock: true, single-API-key connect flow,kisi_metadata(lock_id,lock_name,place_name,description).Note
The Kisi provider is on the
feat/kisi-providerbranch and not yet merged/deployed in seam-connect. These docs describe Phase 1 scope and are ahead of the provider release; the sandbox flow will not work until the provider ships.Test plan
imgprop to the overview card🤖 Generated with Claude Code