Browse our FAQ database and find the answers you need, documents or additional information.
- Building systems
- Cloud & mobile
- DoorLock system
- Network Monitoring
- Security technology
When connecting to a Kentix device the web-browser gives out a warning that the device’s certificate is invalid or untrusted.
This is because the device uses a “self-signed” certificate created by Kentix.
This does not affect the security and/or encryption of the connection between the browser and the device. It just warns that the certificate is unknown for the browser.
To suppress or bypass the security warning, it is possible to load an own certificate into the device.
An example for creating such a certificate can be found in the respective device below the certificate upload. The example shows the creation using “Ubuntu”.
On a Windows server system, a certificate previously generated as “PFX” can be converted to a valid certificate in PEM format with the following command sequence:
openssl.exe pkcs12 -in server.pfx -out server_withkey.pem -nodes
Please note that the command sequence for creating the certificate using “openssl” can vary depending on the operating system.
However, due to the amount of different operating systems and system states, we can not provide technical support here.
All Kentix devices have their sensors inside the housing. This can have an effect on the measurement result, in particular when measuring temperature and humidity.
Therefore the devices are pre-calibrated on delivery. However, it can not be guaranteed that this calibration fits all installation types or room conditions.
For this reason, after the installation, the temperature value of the respective device should be compared with the actual room temperature – in the immediate vicinity of the Kentix device. This can be done with a commercially available room thermometer or better an infrared thermometer.
If a difference is detected during this measurement, this difference should be stored as an offset in the configuration of the respective device.
The temperature offset also automatically corrects the measured value of the relative humidity.
Please note that there may be a slight difference in humidity even if the temperature values for AlarmManager and MultiSensors are set identically.
Using a KIO7017 analogue module, it is possible to include sensors from other suppliers in the monitoring of the AlarmManager.
As a result, other parameters such as e.g. the amount of oxygen in the air can be measured.
In general sensors are supported that deliver either current (measuring range 4-20 mA) or voltage (measuring range 0-10 V) for transmitting the measured value.
For measuring the atmospheric oxygen, for example, the following sensor can be used:
GREISINGER OXY 3690 MP – Electrochem. Oxygen partial pressure sensor for measuring the oxygen content in the atmosphere and in systems without overpressure and underpressure.
If the connection with the Kentix360 mobile App fails, please check the following requirements:
- The AlarmManager or Kentix AccessPoint is connected to the Kentix360 cloud
(recognizable by a green cloud icon in the web interface of the device)
- For your user, the option for the Kentix360 cloud has been activated in the AlarmManager or AccessPoint.
- The profile in the smartphone was created using the displayed QR code.
- The password used is the password of your AlarmManager or AccessPoint user
(not the password for the Kentix360 cloud account!).
- Your smartphone uses mobile data for the connection (no WLAN).
In the case that WiFi shall be used it must be ensured that communication via TCP port 5222 to the internet is possible.
When changing or buying a new Kentix AlarmManager, existing Kentix MultiSensors can be reused without any problem.
Depending on the device, an update is required here.
Unfortunately, new MultiSensors (as of 02/2018) no longer work on an old AlarmManager (before 02/2018).
The following PDF document provides an overview of the compatibility:
The Kentix-devices AlarmManager, MultiSensor-LAN and AccessPoint provide the ability to record video images to a SD card.
For this purpose a SD card with up to 128 GB must be inserted into the respective device.
Cards with up to 64 GB are recognized directly. Here, if necessary, a formatting is automatically offered in case of a unmatching file system.
For 128 GB cards the recognition does not work if the file system differs. The card must then be formatted externally using another system (Windows PC, Mac).
The required file system is FAT(32).
After formatting the card can be reinserted into the device and fully used.
Bei MultiSensor-Door bzw. -Rack-Mini wurde ab Oktober 2016 der Start des Einlernvorgangs leicht verändert.
Bei neueren Sensoren muss der Einlerntaster des Sensors für ca. 3 Sekunden gedrückt werden.
Bei Geräten die VOR Oktober 2016 ausgeliefert wurden, muss der Taster für ca. 5 Sekunden gedrückt werden.
Beim Herunterdrücken erfolgt ein direktes Buzzern, nach 5 Sekunden ein weiteres Buzzern.
Nach dem 2. Buzzern befindet sich der Sensor für ca. 60 Sekunden im Einlernmodus.
Es empfiehlt sich außerdem, den Taster VOR dem Start der Sensorsuche zu betätigen. Der Start des Einlernvorganges bei bereits laufender Suche kann unter Umständen fehlschlagen.
At the MultiSensor-Door and -Rack-Mini the start of the learning process was slightly changed in devices delivered from October 2016 onwards.
For newer sensors, the teach-in button of the sensor must be pressed for approx. 3 seconds.
For devices that were delivered BEFORE October 2016, the button must be pressed for approx. 5 seconds.
When pressed down, a direct buzzing occurs, after 5 seconds a second buzzing follows.
After the second buzzing the sensor is in the teach-in mode for about 60 seconds.
It is also recommended to press the button BEFORE starting the sensor search. Starting the learning process while the search is already running may fail.
To connect your AlarmManager or Kentix AccessPoint with the Kentix360 cloud the creation of a customer account is required in the first step. This registration is done via the Kentix ControlCenter or the web interface of the AccessPoint and requires a connection to the Kentix cloud server “mykentix.com” on TCP port 443 (SSL secure connection).
To connect the device with the Kentix360 cloud also TCP port 5222 between AlarmManager/AccessPoint and the cloud server “mykentix.com” must be available. This must eventually be considered in the configuration of your network.
How to integrate a KABA B-NET 9250/9290 access control in a Kentix alarm system.
Kentix devices can be configured to send alarms to the configured users by e-mail.
This requires a valid e-mail account, which has to be entered in the “Configuration” section in the web interface of the device.
When the sending of an e-mail fails, there will be an entry in the system logbook.
In most cases the errors are caused by authentication problems – a failed attempt to login to the server, or the user data are invalid – either on the Kentix device or on the server side.
When having a problem with the sending of e-mails please always check/compare the entered data in the device.
Also take care that the encryption type and communication port are set in accordance to the e-mail server and the device is able to communicate through the firefall.
In case of a connection error in the ControlCenter when trying to access an AlarmManager please check the following points:
Please check the entered IP by entering it in the address field of a web-browser.
- When Dashboard of the AlarmManager does not appear in the browser, then please check whether the IP address is correct.
You can use the ControlCenter to search for available Kentix devices in the Network by selecting “Update -> Device search…” in the menu bar.
- If the web interface is available, but a connection via ControlCenter is still not possible, then login to the web interface with your user data and restart the AlarmManager by pressing “Perform restart” in the configuration section.
- If none of these points leads to a success, then please restart the AlarmManager by disconnecting it from power for approx. 5 seconds. After this try to reconnect with the ControlCenter.
When performing a firmware update of the AlarmManager, please check on the Kentix website if there are also new firmware versions for you MultiSensors.
We always recommend to update ALL devices together.
If there are still no measurement values after the update of all devices,
then please check, whether the option “AlarmManager communication” is still activated inside the MultiSensor’s web interface, and the correct AlarmManager-IP is specified (MultiSensor-LAN / -LAN-RF / -RACK).
Sollten auch nach dem Update der MultiSensoren keine Messwerte zu sehen sein,
überprüfen Sie zusätzlich ob im Web-Interface des MultiSensors die AlarmManager-Kommunikation noch aktiv und die richtige IP-Adresse des AlarmManagers hinterlegt ist.
Modify these settings if necessary and restart the MultiSensor by clicking the “Save” button.
The Kentix leakage sensor KLS03 sends its alarm using the digital input at the AlarmManager or a MultiSensor.
Please note that the alarm assignment of the “System input 1” at AlarmManager or MultiSensor has to be set to “Always-Active” to have an alarm notification.
The setup for the alarm assignment can be done in the ControlCenter in the section “Sensors-Devices” for every MultiSensor separately.
When the leakage sensor is connected to the MultiSensor using a Power-Adapter (KIO1 or KIO3), then please also note that a fully wired patch cable is required for the connection.
The Kentix leakage sensor KLS03 sends its alarm using the digital input at the AlarmManager or a MultiSensor.
As this input is always in “open state” without having wired an external component,
the leakage sensor will signalize a pending alarm when being connected as it closes this digital input.
To fix this simply log in on the AlarmManager using the Control Center and open the section “Sensors – devices”.
Select the device to which the leakage sensor is connected and change the alarm logic for “System input 1” from “Alarm when – Closed” to “Alarm when – Open”.
Also make sure that the alarm assignment right next is set to “Always-Active”.
Then click “Save” to transfer the configuration changes to the Alarm Manager.
The state of the MultiSensor’s input is now displayed with a green checkmark signaling “OK”.
You can now test the alerting e.g. with a damp cloth.
Overview of the requirements for integrating Kentix in a SCADA- or building management system using OPC.
This article describes how to query measurement values as XML data for further processing.
HowTo monitor distributed infrastructure using the MultiSensor-LAN-RF.
This article describes how to import a Kentix AlarmManager into PRTG using the AlarmManager MIB-file.
It is also described how the AlarmManager can be used out of PRTG as an SMS Gateway.