NG-Key
NG-Key
Smart building

Siemens Building X, Home Assistant, and KNX — governed bridges from buses to readers

Real campuses ship Siemens visitor mirrors, KNX telegrams, and Home Assistant automations beside MQTT readers. NG‑Key keeps those surfaces tenant‑scoped, edge‑mediated, and observable — so OT curiosity does not erode security posture.

Siemens Building X integrations sync visitor lifecycles, map structural hierarchy to areas and readers, and move security signals with configurable handoff discipline — facility teams stop maintaining duplicate Building X spreadsheets.

Home Assistant tenants enable MQTT bridges, signed webhooks, and edge‑delivered configuration bundles so automations stay reproducible — not one‑off YAML pasted into production.

KNX integrates through gateway‑mediated connections with explicit device mappings — telegrams become policy‑aware actions instead of mystery broadcasts.

Edge gateways provide the LAN realism OT demands (latency, TLS, segmentation) while cloud governance stays authoritative for credentials and audit.

Every bridge exposes operator‑visible state: which gateway serves KNX, whether HA automation is live, and how Siemens structure rows map to NG‑Key inventory.

Spotlight

Why these integrations survive audits

  • Siemens Building X — visitor correlation, structure refresh, reader creation helpers, and monitored security handoffs instead of silent scripts.
  • Home Assistant — tenant‑scoped webhooks and MQTT paths with secrets that rotate through normal admin hygiene.
  • KNX — mapping telegrams to managed devices via selected edge gateways — fewer flat networks blasting door commands.
  • Edge mediation — OT traffic lands on gateways you already commission; cloud retains credential authority.
  • Incident pairing — building alarms and access audits share identifiers when integrations are configured intentionally.
  • Partner realism — integrators reproduce flows using published hooks instead of VPN‑only incantations.
Abstract smart building mesh with secure edge gateway — NG-Key integrations marketing tile

Depth

Coverage rooted in shipping surfaces

Siemens structure → facility graph

Refresh Building X hierarchy, align areas, and spawn reader inventory with mapping discipline — fewer orphan doors.

Home Assistant MQTT & webhooks

Signed inbound webhooks and broker integration let automation participate without exposing admin APIs to the LAN.

KNX ↔ reader mappings

Bind KNX actions to managed devices through an explicit gateway — telegrams stay traceable per tenant.

Edge gateway coupling

KNX and HA integrations honour which gateway anchors LAN connectivity — matching how appliances are deployed on site.

Segmentation discipline

Keep life‑safety and occupant comfort domains from silently steering physical security without review.

Traceable automation

Explain which integration fired which outcome — critical when insurers ask for timelines spanning OT and IT.

Motion

Delivery rhythm that scales portfolios

01

Choose gateways

Decide which edge appliances anchor KNX, HA, and Siemens traffic — document failover expectations.

02

Map structures

Align Siemens or facility hierarchies to NG‑Key areas before automation triggers propagate.

03

Pilot floors

Prove webhook + MQTT behaviour with bounded automation — observe logs before portfolio defaults.

04

Operationalise

Hand integrations to facility + security ops with dashboards and escalation paths — not hero engineers.

Measured improvements

Fewer brittle scripts maintained by a single integrator on vacation.

Building operations and security share identifiers during incidents — OT noise decreases.

Procurement sees bounded integration scope with explicit gateways and tenants.

Surprise automation that bypasses governance drops materially.

Related reading

Continue in neighbouring hubs

Deep dives that pair naturally with this integration chapter.

Facility suite

Indoor routing, elevators, visitors — where Siemens and reception integrations meet facility storytelling.

Open Operations · Edge & gateways

Gateway commissioning, MQTT bridges, and fleet posture for appliances on site.

Open Platform · Readers & MQTT

How readers participate in cloud and LAN MQTT contracts without diluting policy.

Open

Product preview

Chapter walkthrough

Short cinematic clip for this integrations chapter — muted, looped in-page players follow your motion preferences elsewhere on the site.

Integrations hub

Every integration chapter at a glance

Open a chapter for full narrative and product video — identity cloud, smart-building bridges, and developer APIs.

Identity cloud

Identity cloud

Entra ID joins, Microsoft 365 visit API automation, and cohort semantics that match grants — no parallel IAM theatre.

Open
Smart building

Smart building

OT bridges, building signals, and edge gateways with explicit segmentation discipline.

Open
Developer APIs

Developer APIs

Tenant API v1 — OpenAPI, Postman, device provisioning, edge commands, and M365 visit sync with granular scopes.

Open

Continue exploring

Open workspace identity, facility topology, or ledger exports — or return to the platform core.

Platform core Workspace Ledger