A successful integration starts with a named device and firmware version. Confirm the SDK or protocol, authentication, user and event fields, command flow, offline storage, time synchronization and upgrade responsibility on sample hardware.
Comparison
Put the decision factors side by side.
Use the table to expose assumptions that should be tested on the selected device and installation.
| Integration area | Questions to resolve | Evidence to request |
|---|---|---|
| Version scope | Which device, firmware and software mode are in scope? | Current version list and sample identifiers |
| Data contract | Which user, credential, event and image fields move? | SDK/API documentation and sample payloads |
| Offline behavior | What continues locally and how are events synchronized? | Capacity, retry and duplicate-handling test |
| Access control | Which commands and physical interfaces control the door? | Wiring diagram and command test |
Decision checklist
Information to collect before the supplier review.
- 01
Named production model and firmware
- 02
Supported SDK language or protocol
- 03
Authentication and network security
- 04
User, credential and event-field mapping
- 05
Offline capacity and synchronization behavior
- 06
Upgrade, support and regression-test ownership
Related TIMY paths