---
title: "ekey bionyx"
description: "ekey bionyx is a built-in integration for Home Assistant. It has 225 installs sharing analytics and works locally."
canonical: "https://vulpo.app/integrations/core/ekeybionyx"
url: "https://vulpo.app/integrations/core/ekeybionyx.md"
last-updated: "2026-10-22"
version: "1.4"
---

# ekey bionyx

> ekey bionyx is a built-in integration for Home Assistant. It has 225 installs sharing analytics and works locally.

ekey bionyx is a built-in Home Assistant integration for ekey fingerprint controllers that exposes their functions as event entities. It adds event entities that are mapped to functions of the fingerprint controller, and each one can be given its own name. During setup, the system the entities belong to is chosen, along with a Home Assistant URL that the fingerprint controller can reach. The integration works locally and is configured in the interface, with a sign-in through the vendor's own page. It needs no separate installation because it ships with Home Assistant.

Automatic summary of Home Assistant's source code. Something wrong? [Get in touch](https://vulpo.app/contact)

[Open in My Home Assistant](https://my.home-assistant.io/redirect/config_flow_start/?domain=ekeybionyx)

## Supports

- **Works locally**: Talks to your devices on your own network. No vendor cloud in between.
- **Set up in the UI**: Add it in Settings, Devices and services. Nothing to download.
- **Sign in with the vendor**: Connects through the vendor's own sign-in page.
- **Bronze quality**: Home Assistant's own rating of its code and setup experience.
- **Updated with Home Assistant**: Ships and updates with every Home Assistant release.

## Setting it up

It is added under Settings, Devices and services, with Add integration.

### Choose system

- **System**: System the event entities should be set up for.

### Webhooks

- **Home Assistant URL**: Home Assistant instance URL which can be reached from the fingerprint controller
- **Event entity 1**: Name of event entity 1 that will be mapped into a function
- **Event entity 2**: Name of event entity 2 that will be mapped into a function
- **Event entity 3**: Name of event entity 3 that will be mapped into a function
- **Event entity 4**: Name of event entity 4 that will be mapped into a function
- **Event entity 5**: Name of event entity 5 that will be mapped into a function

Texts from Home Assistant's source code, [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0).

## At a glance

- Kind: Built-in integration
- Category: [Hubs and protocols](https://vulpo.app/integrations/category/hubs-and-protocols.md), Building automation
- Number: 225 installs sharing analytics
- Connection: Works locally
- Upkeep: Part of Home Assistant
- Needs: Built into Home Assistant
- Quality scale: Bronze quality scale
- Domain: `ekeybionyx`
- Source: <https://www.home-assistant.io/integrations/ekeybionyx/>

In Vulpo: Entity card (read-only)

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about)

Last updated 2026-10-22. Source: https://vulpo.app/integrations/core/ekeybionyx

---

- HTML version of this page: https://vulpo.app/integrations/core/ekeybionyx
- Site index for agents: https://vulpo.app/llms.txt
- Everything in one document: https://vulpo.app/llms-full.txt
- All pages: https://vulpo.app/sitemap.xml