Axis
Swedish IP cameras — VAPIX REST API and ACAP edge analytics for KNX security integration.
Axis Communications (Lund, Sweden — founded 1984) invented the first network camera in 1996 and remains the global leader in IP video surveillance, with product lines spanning fixed dome cameras, PTZ cameras, fisheye cameras, multi-sensor cameras, and modular camera systems. In KNX building automation projects, Axis cameras have no native KNX interface but integrate via two well-established paths: VAPIX REST API HTTP action profiles that fire webhooks to Home Assistant on motion detection or analytics events, and the Axis P8221 I/O relay module that provides physical dry-contact outputs wired directly to KNX binary input modules in the panel. The ACAP (Axis Camera Application Platform) edge analytics framework allows AI-powered person, vehicle, and animal classification to run directly on the camera processor — enabling more precise triggers for KNX alarm logic with far fewer false positives than conventional pixel-change motion detection. Axis cameras are standard in high-specification residential and commercial KNX projects across Europe, particularly in villa perimeter security, commercial lobby monitoring, and hotel entrance management.
Role in our panels
How we use Axis
The primary KNX integration path for Axis cameras uses VAPIX HTTP action profiles: when the camera detects motion or an ACAP analytics event fires, the camera executes a configured HTTP POST to a Home Assistant webhook URL. The HA automation then writes a binary 1 to a KNX group address, triggering KNX alarm logic, lighting scenes, or access control outputs. The VAPIX action URL for triggering a virtual input is structured as `http://[camera-ip]/axis-cgi/virtualinput/activate.cgi?schemaversion=1&channel=1`, and the round-trip latency from camera event to KNX group address write is approximately 300ms over a standard LAN. For projects requiring physical dry-contact outputs — for example connecting to a third-party alarm panel or to KNX binary inputs in the panel — the Axis P8221 I/O module provides 8 alarm inputs and 2 relay outputs that can be triggered by camera events and wired to KNX binary input modules. The ARTPEC-8 deep learning processor (used in 2023+ Axis cameras) runs person vs. vehicle vs. animal classification on-device, dramatically reducing false KNX alarm triggers compared to older motion detection methods.
Axis cameras carry no KNX bus connection — integration is exclusively via IP (Ethernet) and physical dry contacts. Panel design for Axis-in-KNX projects includes: a managed Ethernet switch on a dedicated security VLAN with PoE+ ports for Axis cameras (IEEE 802.3af for dome cameras, 802.3at for PTZ); KNX binary input modules (MDT SCN-BI8UP, ABB 6220/12.1) wired to Axis P8221 relay outputs for physical alarm-zone signaling independent of IP network availability; 24V power for the P8221 module from the panel SELV supply. Network architecture: cameras on security VLAN (e.g. 192.168.10.0/24) isolated from KNX IP subnet; Home Assistant on management VLAN with firewall rules permitting inbound VAPIX HTTP posts from camera VLAN and outbound KNX/IP UDP to KNX IP router. For PoE budget: P3245-VE draws 5W, Q6135-LE draws up to 25W — size the switch PoE budget accordingly. The VAPIX integration requires that the HA KNX integration is configured with the correct KNX IP interface address and group addresses matching the ETS6 project.
Used in these project types
Axis products
Key components we install
Axis P3245-VE Fixed Dome Vandal Camera
3MP fixed dome, IK10 vandal-resistant, IP66 weather-sealed, ARTPEC-6 processor, VAPIX v3 REST API, IR illumination to 30m. For outdoor perimeter monitoring at building entrances, underground parking, and building facades. VAPIX HTTP action profile: on motion detection, POST to HA webhook → KNX binary group address → lighting scene activation. Supports Axis ACAP application installation for on-camera analytics. PoE IEEE 802.3af (5.2W).
Axis Q6135-LE PTZ with Laser IR
32× optical zoom PTZ camera with laser IR illumination to 200m. ARTPEC-7 processor with deep learning person detection. For perimeter tracking: camera auto-tracks detected persons across a car park or site perimeter; ACAP analytics event fires VAPIX HTTP action → HA → KNX alarm group address. PoE+ IEEE 802.3at (25W). Used in commercial perimeters, industrial sites, and hotel exterior monitoring where human-tracking PTZ replaces multiple fixed cameras.
Axis A8207-VE MkII Outdoor Fisheye
6MP 360-degree fisheye camera with dewarping, outdoor IP66, IK10. ARTPEC-6. For lobby overview, car parks, and open-plan areas where one camera replaces 3-4 fixed domes. ACAP person detection on dewarped virtual PTZ streams. VAPIX action profile on detection → HA → KNX binary for lobby presence or crowd count. Used in commercial lobby KNX projects for occupancy-based lighting and HVAC control triggered by camera-detected presence rather than PIR sensors.
Axis FA54 Main Unit + FA1105-E Sensor
Modular system: one FA54 processing unit connects up to 4 FA1105-E sensor units on 15m cable. Sensor units are 6mm diameter — installable inside door frames, behind false ceilings, or embedded in lift shaft corners where a standard camera dome would be visible and damaged. Each sensor unit delivers 1080p HD. One IP address, one VAPIX API endpoint for all 4 sensors. For discreet retail or hotel corridor monitoring with VAPIX integration to KNX.
Axis P8221 I/O Relay Module
IP-connected I/O module: 8 dry-contact alarm inputs, 2 relay outputs (1A, 30V DC). Connects to Axis cameras and VMS via VAPIX I/O API. For KNX panel integration: relay outputs wire directly to KNX binary input module terminals — camera motion event triggers relay output → KNX binary input activates group address → KNX alarm logic runs. Provides physical alarm path independent of IP network health. Also accepts door contact, PIR, and glass-break inputs from third-party security sensors.
Axis FAQ
How does Axis camera motion detection trigger a KNX group address?
Axis cameras use VAPIX HTTP action profiles — a built-in rule engine that executes HTTP requests when camera events fire. Configure a VAPIX action rule in the camera web interface: trigger = motion detection (or ACAP analytics event); action = HTTP POST to a Home Assistant webhook URL. The HA automation receives the POST, processes the payload, and calls the KNX service to write a binary 1 to a KNX group address. The HA KNX integration then sends a KNX telegram on the TP or IP bus to the configured group address. End-to-end latency from camera event to KNX telegram delivery is approximately 300ms over a standard wired LAN. A second VAPIX action rule with the opposite event (motion stopped) writes binary 0 to the same group address to reset the KNX alarm state after a configurable timeout.
What is ACAP and how does it improve KNX alarm accuracy?
ACAP (Axis Camera Application Platform) is a software framework that allows third-party AI applications to run directly on the camera processor chip — ARTPEC-7 and ARTPEC-8 in current Axis hardware. Instead of triggering on any pixel-change in the motion detection zone (which fires on wind-blown vegetation, rain, and headlight sweeps), an ACAP application such as Axis Object Analytics classifies detected objects as person, vehicle, or unknown before deciding whether to fire an event. Only a classified person detection triggers the VAPIX HTTP action to Home Assistant and onwards to the KNX alarm group address, dramatically reducing false KNX alarm triggers in outdoor applications. ACAP applications are installed via the camera web interface from the Axis App Store or directly as ACAP packages; no external server is required because inference runs on the camera CPU itself. For KNX perimeter projects, this means the KNX alarm logic receives far more reliable binary inputs, reducing false siren activations and unnecessary KNX scene changes.
Can Axis cameras integrate with 2N intercoms and KNX simultaneously?
Yes — this is a common villa and hotel entrance configuration because both integrations run on independent IP paths. The 2N IP intercom (any 2N Helios IP series) subscribes to the Axis camera RTSP stream directly and displays the live video on 2N indoor panels (2N Indoor View, 2N Indoor Compact) when the doorbell is pressed — no KNX involvement in the video path. Simultaneously, the Axis camera fires a VAPIX HTTP action to Home Assistant on motion detection or doorbell press event; HA writes to KNX group addresses for entrance lighting, a KNX binary output for door status logging, or a KNX announcement scene on Gira G1 panels. The 2N intercom can also trigger KNX via its own SIP and automation rules, so a door open event from 2N can simultaneously update a KNX group address for access log visualisation on a KNX touch panel. The key point is that Axis, 2N, and KNX all coexist via Home Assistant as the integration hub with no conflicts.
Need a panel with Axis components?
We select, procure, assemble and certify. Free initial consultation.
Request consultation →