Integrations

Integrations are how OpenApp connects to access control hardware, automation systems, and protocols while keeping the core product consistent.

Why integrations exist

Physical security is an ecosystem: different vendors, different deployment models, and different APIs. Integrations let OpenApp:

• Connect to vendor/protocol specifics without locking the rest of the product to any one system
• Evolve support over time as vendors change firmware, APIs, and capabilities
• Provide a consistent model for devices, entities, and actions across providers

Why modularity matters

Modularity keeps the platform maintainable and safe:

• Isolation: provider-specific logic is contained so changes don’t ripple through unrelated parts of the system
• Extensibility: new providers can be added without redesigning the core data model
• Operational clarity: support, debugging, and upgrades can be scoped to an integration

Request a new integration

Need a provider we don’t support yet? File an integration request here:

• Request a new integration

Include:

• Vendor/product + model(s)
• How it connects (cloud, LAN, protocol like MQTT/KNX, etc.)
• Links to vendor docs and any existing open-source integrations (e.g. Home Assistant)
• Example payloads, identifiers, and expected actions (open/close/toggle, etc.)

Integration support

Integration support is best-effort and depends on provider capabilities and the quality/stability of upstream APIs.

When reporting an issue, include:

• Provider type (e.g. home_assistant, knx)
• Integration config fields (redact secrets)
• Device/entity external_id values involved
• Steps to reproduce + expected vs actual behavior

Available integrations

Sensitive config fields (API keys, tokens, passwords) are stored securely in AWS Secrets Manager.

Each integration includes:

• Product and manufacturer links
• Links to similar open-source integrations
• A practical getting-started guide
• A setup reference (required fields + explanations)

Home Assistant

→

Connect OpenApp to an existing Home Assistant instance.

go2rtc

→

Watch IP cameras in the browser with low-latency WebRTC via go2rtc.

KNX

→

Connect OpenApp to a KNX/IP gateway for local building automation control.

MQTT

→

Control devices by publishing MQTT messages to your broker.

PalGate Cloud

→

Control PalGate gates and controllers via the PalGate cloud API.

Shelly Cloud

→

Control Shelly devices via Shelly Cloud.

Shelly Websocket

→

Connect to Shelly devices using a local websocket transport (currently limited).

Virtual Budget

→

Track and update budgets as virtual entities inside OpenApp.

Virtual Access

→

A virtual provider type for portal-related workflows (directories, portals, apartments/units, and invite-driven capabilities).

Waveshare

→

Connect OpenApp to Waveshare relay boards via MQTT + Modbus RTU.