Supported capabilities
V5 distinguishes three claims:
- Recognized: the SDK knows the device and its evidenced capabilities.
- Represented: at least one primary-purpose member has an explicit HomeKit adapter.
- Controllable: at least one verified operation is available through HomeKit.
Current implementation status
| Area | Status |
|---|---|
| Account and device discovery | Runtime available |
| Contact sensor adapter | Published from complete runtime registry snapshots |
| Cameras, streaming, snapshots, talkback, HKSV | Implemented in the V5 closed beta |
| Motion and doorbell events | Deferred/in progress |
| Security modes, locks, lights, sirens, battery | Deferred/in progress |
Primitive type similarity never admits a mapping. Unsupported members remain diagnostic-only or blocked until verified SDK evidence and a semantic HomeKit contract both exist.
Accessory containers use the SDK entity serial as their physical identity input. Station, channel, endpoint, and discovery order do not affect identity. Identity metadata supplements an already represented accessory but cannot create one by itself.