alarm_device

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
alarm_device [2019/10/21 19:12] – [Alarm device] ingridalarm_device [2023/02/27 13:57] (current) – [Inim Prime webAPI] ingrid
Line 2: Line 2:
  
 {{ :system_obj_-_security.png?nolink&100 |}} {{ :system_obj_-_security.png?nolink&100 |}}
 +
 +  * [[#alarm_object| Alarm Object]]
 +  * [[#object_commands| Object Commands]]
 +  * [[#adding_partitions| Adding Partitions]]
 +  * [[#adding_sensors| Adding Sensors]]
 +  * [[#bentel_interface| Bentel Interface]]
 +  * [[#Tecnoalarm_interface| Tecnoalarm Interface]]
 +  * [[#Siemens/vanderbilt_SPC| Siemens/Vanderbilt SPC]]
 +  * [[#Paradox_evo| Paradox Evo]]
 +  * [[#inim_prime_webAPI| Inim Prime webAPI]]
 +==== Alarm Object ====
  
 This object is used to integrate the central alarm in the project; it allows the server to arm or disarm the central, to read partitions or sensor status and to singularly control them. All alarm panels integrated in the system provide the user with the same graphical effect; they can be selected from the following list of models: This object is used to integrate the central alarm in the project; it allows the server to arm or disarm the central, to read partitions or sensor status and to singularly control them. All alarm panels integrated in the system provide the user with the same graphical effect; they can be selected from the following list of models:
   * **Device type** This property allows to select the alarm panel model.   * **Device type** This property allows to select the alarm panel model.
 +
 +<WRAP group>
 +<WRAP column half> 
 +    * //ArrowHead Elit SX//
     * //AVS Electronics XTream 640//     * //AVS Electronics XTream 640//
     * //Bentel Absoluta//     * //Bentel Absoluta//
Line 15: Line 30:
     * //Brahms series B4 CMP64//     * //Brahms series B4 CMP64//
     * //Elkron MP508 TG//     * //Elkron MP508 TG//
 +    * //Elmo (ETRx, ET8plus, NETx, Villegio, Pregio, Tacora)//
     * //GE security/Aritech ATS//     * //GE security/Aritech ATS//
 +    * //GE security/Aritech ATS Adviser Master//
     * //Honeywell Galaxy Dimension//     * //Honeywell Galaxy Dimension//
 +    * //Iess (Genio)//
 +</WRAP>
 +<WRAP column half>
 +    * //Inim Prime webAPI// 
     * //Inim Smartliving 10100//     * //Inim Smartliving 10100//
     * //Inim Smartliving 1050//     * //Inim Smartliving 1050//
     * //Inim Smartliving 515//     * //Inim Smartliving 515//
 +    * //Paradox EVO//
     * //Rokonet RP128//     * //Rokonet RP128//
     * //Rokonet RP128 BRTE//     * //Rokonet RP128 BRTE//
 +    * //Satel Integra//
     * //Siemens SPC//     * //Siemens SPC//
     * //Tecnoalarm TP16-256//     * //Tecnoalarm TP16-256//
 +    * //Tecnoalarm TP20-440//
     * //Tecnoalarm TP8-64//     * //Tecnoalarm TP8-64//
     * //Tecnoalarm TP8-88//     * //Tecnoalarm TP8-88//
     * //Urmet 1067//     * //Urmet 1067//
 +    * //Wago Switzerland//
 +</WRAP>
 +</WRAP>
   * **Communication:** This property allows to select the type of communication established with the server; it can be selected from the following list:   * **Communication:** This property allows to select the type of communication established with the server; it can be selected from the following list:
     * //RS232:// Connected through serial cable.     * //RS232:// Connected through serial cable.
     * //RS232overTCP_IP:// Connected through link with TCP media converter.     * //RS232overTCP_IP:// Connected through link with TCP media converter.
     * //TCP_IP:// Connected through network link.\\ If the property ”Communication” is set to ”RS232”, the following properties will appear:     * //TCP_IP:// Connected through network link.\\ If the property ”Communication” is set to ”RS232”, the following properties will appear:
-      * Serial Port: This property represents the system serial port number.\\ If the property ”Communication” is set to ”TCP/IP”, the following properties will appear:+      * Serial Port: Serial port number that changes depending on the server used. Click [[port_numbers| here]] to get the correct port number. \\ If the property ”Communication” is set to ”TCP/IP”, the following properties will appear:
       * IP Address: Device IP address or RS232overIP address.       * IP Address: Device IP address or RS232overIP address.
       * Port Number: TCP/IP port number for ethernet connection.       * Port Number: TCP/IP port number for ethernet connection.
Line 106: Line 133:
   * **New /state of the output** ON=1, OFF=0.   * **New /state of the output** ON=1, OFF=0.
 ++++ ++++
 +
 +==== Adding partitions ====
 +
 +Click on the button displayed on the right to open partitions editor window, click on ”Add” and then adjust the properties in the grid:
 +
 +  * **Area Name** Label of text to identify the area.
 +  * **Central index** Insert the number of the partition programmed in the security system.
 +  * **Disarming** Enable/disable the option to deactivate the alarm system through a KNX command.
 +  * **Arming** Enable/disable the option to activate the alarm system through a KNX command.
 +  * **Command bit** KNX group address to command arming of the area (1 bit - 1=arm, 0=disarm)
 +  * **Command Byte** KNX group address to command area in byte.
 +  * **Command 14 Byte** KNX group address to command area in with 14 bytes object. The string should be in the form 1|xxxx or 0|xxxx where xxxx represents the user code and 0 or 1 is used to decide if the partition should be armed or disarmed.
 +  * **Status byte** 1 byte KNX group address sent by the server containing the partition status.
 +  * **Area name** Insert the partition name.
 +
 +==== Adding sensors ====
 +
 +Click on the button displayed on the right to open sensors editor window, click on ”Add” and then adjust the properties in the grid:
 +
 +  * **Index number** Insert the number of the sensor you programmed in your security system.
 +  * **Group** Insert a KNX group address to communicate with the sensor (f.e. to turn on a light using an alarm system motion sensor).
 +  * **Name of the sensor** Sensor name.
 +  * **Send all states** If enabled, the sensor sends all states, if disabled, the sensor sends only alarm state (only value 1).
 +  * **Send on change** If enabled the sensor sends its state only on change (otherwise, sensor status will be sent on every polling).
 +
 ==== Bentel Interface ==== ==== Bentel Interface ====
  
Line 145: Line 197:
 {{ :spc_settings3.png?direct&600 |}} {{ :spc_settings3.png?direct&600 |}}
  
-==== Adding partitions ====+==== Paradox Evo ====
  
-Click on the button displayed on the right to open partitions editor window, click on ”Add” and then adjust the properties in the grid:+To interact with a Paradox Evo device, the Printer Module PRT3 must be used as an interface between the home automation system and the control panel.  
 +{{ :paradox_PRT3.png?direct&600 |}}
  
-  * **Area Name** Label of text to identify the area. +To ensure correct communication with the Thinknx server, the device must be configured as seen in the picture below: 
-  * **Central index** Insert the number of the partition programmed in the security system. +  * Set Baud Rate: 57600 
-  * **Disarming** Enable/disable the option to deactivate the alarm system through a KNX command. +  * Set Printer Module's serial port to either "Event Reporting (off)" or "Home Automation (on)".
-  * **Arming** Enable/disable the option to activate the alarm system through a KNX command. +
-  * **Command bit** KNX group address to command arming of the area (1 bit - 1=arm, 0=disarm) +
-  * **Command Byte** KNX group address to command area in byte. +
-  * **Command 14 Byte** KNX group address to command area in with 14 bytes object. The string should be in the form 1|xxxx or 0|xxxx where xxxx represents the user code and 0 or 1 is used to decide if the partition should be armed or disarmed. +
-  * **Status byte** 1 byte KNX group address sent by the server containing the partition status. +
-  * **Area name** Insert the partition name.+
  
-==== Adding sensors ====+{{ :paradox_config_1.png?direct&600 |}} 
 + 
 +To properly connect the device to the Thinknx server, see below diagram: 
 + 
 +{{ :paradox_config_2.png?direct&800 |}} 
 + 
 +==== Inim Prime webAPI ==== 
 +To interact with Inim Prim webAPI, it is necessary to generate an API key from the alarm's configuration page. The API key should be copied inside the Alarm object in the configurator. Make sure to save and reboot the alarm panel after generating the API key.  
 + 
 +{{ :inim_alarm_1b.png?direct&850 |}}
  
-Click on the button displayed on the right to open sensors editor window, click on ”Add” and then adjust the properties in the grid: 
  
-  * **Index number** Insert the number of the sensor you programmed in your security system. 
-  * **Group** Insert a KNX group address to communicate with the sensor (f.e. to turn on a light using an alarm system motion sensor). 
-  * **Name of the sensor** Sensor name. 
-  * **Send all states** If enabled, the sensor sends all states, if disabled, the sensor sends only alarm state (only value 1). 
-  * **Send on change** If enabled the sensor sends its state only on change (otherwise, sensor status will be sent on every polling). 
  • alarm_device.1571677954.txt.gz
  • Last modified: 2019/10/21 19:12
  • by ingrid