Description
+ POINTS
- Perfect integration of Axis network devices into application scenarios
- Stronger combination of both systems. Motion detector (KNX) starts the action or Cross Line Detection (camera) switches on the light
- Private sphere (masking) can be controlled via KNX, for instance, through presence and absence
- Camera responds directly to KNX/IP after successful installation
- Third-party applications on the camera can also communicate with KNX
- In addition to network cameras, all Axis network devices with ACAP are also supported
New firmware, new possibilities
Firmware version 2.3 for the SMART APP KNX Axis plug-in available!
Onward camera firmware version 5.60 please use the software for the SDK2.
Please note that when updating from version 1.0 to version 2.2 or to version 2.3, the action rules must also be revised. When updating from version 2.2 to version 2.3, no adjustment of the action rules is required.
If you want to upgrade from version 1.0 up to version 2.x, you will need a new license file. We are happy to exchange your current license for free, specifying the camera serial number and the license code for a current license. Please contact our sales department at sales@ise.de.
An update of the product database entry (KNXPROD) is REQUIRED when updating from version 1.0 up to 2.x with the new firmware.
New AXIS camera firmware
Compatibility up to firmware version 10.5.2
Due to a new AXIS camera firmware, there are currently compatibility issues with the SMART APP KNX Axis.
Please use firmware version 10.5.2 as the highest firmware.
Features
- Support of Axis network cameras
- Support of Axis WLAN cameras 1
- Support of Axis D2050 -VE Network Radar Detector
- Support of Axis door stations
- Support of Axis network loudspeakers
- 30 communication objects for sending from KNX to the Axis camera (1 bit)
- 30 communication objects for sending from
- the Axis camera to KNX (variable bit length)
- Control of actions on the camera
- Triggering of image, video and/or camera message sending
- With PTZ cameras, predefined positions can be focused on
- Camera settings (properties) can be read out and sent to the KNX
- Sending of a message to the KNX with access to the camera’s live stream
- Monitoring of the camera itself, e.g. for overheating or breaking of the connection to the saving location for videos
- Third-party applications can send values to the KNX
- Simple integration into KNX (can be completely configured via ETS and the camera’s event system)
Technical data
KNX communication: KNX/IP (Routing), S-Mode |
The following Axis camera models and |
all models with aarch64 processors |
are currently not compatible with AXIS App: |
Axis M3064-V, Axis M3065-V, Axis M3066-V, |
Axis M3075-V, Axis M3205-LVE, Axis M3206-LVE, |
Axis P3719-PLE, Axis Q6010-E, Axis Q9216-SLV. |
Note:
The plug-in can only be used on network devices from Axis Communications with ACAP support.
For ETS5 or higher
Communication and Installation
The “SMART APP KNX Axis” plug-in is installed directly on a network device (e.g. network camera) based on an Axis ACAP (Axis Camera Application Platform). After successful installation, the Axis network device is a KNX/IP device and communicates with the world of KNX via KNX/IP routing. The plug-in is configured on the network device (event system) and in the ETS. KNX installations are usually implemented with two wires (TP), meaning that a KNX/IP router has to be present in this installation (often already present in KNX visualisation systems) to enable communication between KNX/IP and KNX/TP.
EAP installation package
If you are not sure which installation package you need, you can query the required processor type on your camera. Please replace <Camera IP> with the actual IP address of the camera.
http://<camera-IP>/axis-cgi/param.cgi?action=list&group=root.Properties.System.Architecture
Test version
You can also register the application as a 30-day test licence and download it from the Axis communications web page.
IMPORTANT! With the test version, communication with the KNX is cut off after 2 hours. Communication will only work again for 2 more hours after restarting the application.