Kisi with legacy reader and legacy controller
Use case example
You can integrate Kisi with your legacy reader and controller, while maintaining your existing strike wiring to the legacy controller.
Benefits
- Reuse your existing readers and credentials
- Maintain your existing strike wiring to the legacy controller
- Enable physical card and mobile in-app unlocks with Kisi
- Let Kisi decide how to handle unknown credentials: reject or pass through to legacy system
How it works
This deployment maintains your existing legacy controller while adding Kisi intelligence. The Kisi Controller Pro 2 with Wiegand board acts as an intermediary between your legacy reader and legacy controller.
Power supplies are required for the Network Switch, Kisi Controller Pro 2, and legacy controller. Check the individual hardware documentation for appropriate DC power adapters.
Access logic
Physical credential access
- The user taps a card on the legacy reader
- The Kisi Controller Pro 2 receives credential data and checks with Kisi cloud for verification
- If authorized, Kisi sends unlock command to the legacy controller which opens the door strike
Mobile app access
- The user taps to unlock in the Kisi mobile app
- Kisi cloud verifies the credential and sends unlock command to the controller
- The controller transmits unlock command to the legacy controller which opens the door strike
This setup allows you to configure Kisi to either reject unknown credentials or pass them through to the legacy system for fallback authorization. As this deployment uses legacy readers, available access options include physical credentials through the legacy reader and mobile in-app unlocks. Mobile Tap to unlock, MotionSense, and Bluetooth unlocks are not available as they require Kisi readers. See migration paths to check what access options are available for different deployment methods.