I’d like to briefly introduce the integration of ekey bionyx with Control4 using the ekey bionyx notification API, and point out where you can find the relevant resources. At the bottom you will find a link to a playlist for a detailed step-by-step guide.
What does this integration do?
The ekey bionyx notification API allows the ekey access control and fingerprint scanner system to communicate directly with third-party smart home systems such as Control4.
The API is based on HTTP(S) notifications that are sent from the ekey control unit within the local network to a defined endpoint whenever an access event occurs.
This enables, for example:
- Detection of access via fingerprint scanner
- Transmission of user IDs and finger IDs
- Triggering Control4 actions or scenes (e.g. lighting, alarm, music)
based on fingerprint scanners or digital inputs
Control4 driver
A dedicated Control4 driver is available that uses the ekey bionyx Notification API.
The Control4 integration consists of two driver types:
- One ekeybridge driver per Control4 project
- One ekeydevice driver for each ekey system or room
- If multiple ekey systems are installed within the same room, multiple ekeydevice drivers can be used
- If a project includes multiple ekey finger scanners, an ekeydevice driver must be added for each scanner, regardless of room location.
- The ekeydevice driver processes biometric events and provides the automation events used within Control4 programming.
- The ekeybridge driver handles discovery, configuration import and routing of biometric events.
The ekey bionyx Notification API license for Control4:
- Enables integration of ekey bionyx into Control4
- Actions and scenes can be triggered via user profiles, fingers, or digital inputs
- License covers up to 20 users / 20 fingerprints
- License is delivered digitally by email after activation
- Processing time is typically up to 4 working days
In most cases, the driver can be tested free of charge for a limited time (e.g. 5 days) before a license is required.
How does it work technically?
- Activate the Notification API
– In the ekey bionyx app under Smart Home Connections, enable the Notification API.
– The controller will then send HTTP(S) notifications to the configured endpoint on each access event. - Install the Control4 drivers
– Certified ekey drivers are available directly through the Control4 Online Driver Database.
– When an ekey Hardware Bridge is installed, Control4 can automatically discover the bridge via SDDP and deploy the required drivers.
– Drivers can also be added manually through Composer by searching for ekeybridge and ekeydevice.
– Configure events and bindings that react to incoming ekey notifications. - Link to Control4 programming
– Use Composer / Composer Pro to create programming logic that evaluates the received events and triggers the desired actions or scenes.
– Event programming is performed within each ekeydevice driver instance and can be linked to any Control4 automation logic.
User Groups
Users can be assigned to predefined groups:
- Group A – Family
- Group B – Service Personnel
- Group C – Friends & Visitors
Each group provides dedicated automation events that can be used within Control4 programming.
Duress Finger
Each user group can define a dedicated duress finger.
When used, a separate duress event is generated and can be used to trigger emergency automations, silent alarms or notifications within Control4.
Resources & documentation
Here you should find any further information and documentation needed for this integration.
- ekey developer forum – notification API
Documentation, activation guides, and examples for the notification API can be found here:
Notification API - ekey developer - Control4 documentation
Here you can find the complete Control4 documentation - Control4 integration/license
Information about the Control4 driver and the required license is available in the ekey download area:
Control4 driver - Installation & configuration videos → View playlist