Interface Matrix
Supported Interfaces
Protocol support described by scope — not slogans.
“Supported” means defined scope
A protocol is only “supported” if scope, directionality, and constraints are declared. Vœrynth treats interfaces as operational contracts.
Protocol Support Matrix
| Interface | Mode | Access | Typical Scope | Constraints |
|---|---|---|---|---|
| KNX | Native | Read/Write | Lighting, shading, climate signaling | Commissioned via validated IP interface; topology rules apply |
| DALI-2 | Bridged | Read/Write | Lighting groups/scenes | Deployed behind certified gateway |
| Modbus TCP | Native | Read/Write | Plant/energy telemetry and control points | Scope defined per site; safety-critical remains external |
| Zigbee 3.0 | Native | Read/Write | Sensors, lighting, convenience devices | Certified coordinator + firmware pinning |
| Z-Wave | Native | Read/Write | Sensors, access peripherals | Region-locked controller; key management enforced |
| Bluetooth | Bridged | R/W (Ltd) | Convenience edge devices | Not used for safety-critical; best-effort tier |
| MQTT | Native | Read/Write | Event transport and device bridging | Scoped topics; policy gate applies to actuation |
| Matter | Variant | Variant | Interop layer for selected devices | Scope depends on certified controllers; not assumed universal |
| NMEA 2000 | Bridged | Read-First | Marine telemetry | Actuation boundaries are explicit and commissioned |
| Signal K | Native | Read-First | Unified marine data model | Used for situational awareness; safety-critical remains external |
Safety Boundaries
Where a subsystem is safety-critical (marine navigation, emergency systems, vendor safety loops), Vœrynth integrates at the boundary. Commissioned scope defines what is observed, what is controlled, and what is never actuated.
Need a protocol inventory review?
A pilot starts with interface mapping and commissioning scope.