system_objs

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revisionBoth sides next revision
system_objs [2019/03/14 15:39] – ingridsystem_objs [2019/03/14 15:43] – ingrid
Line 558: Line 558:
       *Delay factor: This property indicates the value of the time interval of the delay.        *Delay factor: This property indicates the value of the time interval of the delay. 
   * **Output group** This property represents the KNX group of the output value.   * **Output group** This property represents the KNX group of the output value.
-  * **Output sending behaviour** This property indicates when the result of the output operation has to be sent.+  * **Output sending behavior** This property indicates when the result of the output operation has to be sent.
     * //’On result change’:// indicates that the value is sent only when the result of the operation is different from the previous one.     * //’On result change’:// indicates that the value is sent only when the result of the operation is different from the previous one.
     * //’When a new input telegram is received’:// indicates that the value is sent whenever the server receives a telegram from on of the KNX groups specified in the inputs.     * //’When a new input telegram is received’:// indicates that the value is sent whenever the server receives a telegram from on of the KNX groups specified in the inputs.
Line 636: Line 636:
  
   * **Addends** This property represents the list of values coming from different KNX groups that will be summed .   * **Addends** This property represents the list of values coming from different KNX groups that will be summed .
-  * **Output sending behaviour** This property indicates when the result of output operation has to be sent.+  * **Output sending behavior** This property indicates when the result of output operation has to be sent.
     * //’On result change’//: indicates that the value is sent only when the result of the operation is different from the previous one.     * //’On result change’//: indicates that the value is sent only when the result of the operation is different from the previous one.
     * //’When a new input telegram is received’//: indicates that the result is sent whenever the server receives a telegram from one of the KNX groups specified in the inputs.     * //’When a new input telegram is received’//: indicates that the result is sent whenever the server receives a telegram from one of the KNX groups specified in the inputs.
Line 683: Line 683:
     * //sin// Calculates the sin of a number     * //sin// Calculates the sin of a number
     * //sqrt// Calculates the square root of a number\\ Alternatively, to view a complete list of available functions and their syntax click on the "?" button.     * //sqrt// Calculates the square root of a number\\ Alternatively, to view a complete list of available functions and their syntax click on the "?" button.
-  * **Output sending behaviour** This property indicates when the result of the output operation has to be sent. +  * **Output sending behavior** This property indicates when the result of the output operation has to be sent. 
     * ”On result change” indicates that the value is sent only when the result of the operation is different from the previous one.     * ”On result change” indicates that the value is sent only when the result of the operation is different from the previous one.
     * ”When a new input telegram is received” indicates that the result is sent whenever the server receives a new telegram from one of the KNX groups specified in the inputs.     * ”When a new input telegram is received” indicates that the result is sent whenever the server receives a new telegram from one of the KNX groups specified in the inputs.
   * **Output group** This property indicates which KNX group the result of the operation has to be assigned to.   * **Output group** This property indicates which KNX group the result of the operation has to be assigned to.
-  * **Type** Type of number to exrtact from the value read from bus.+  * **Type** Type of number to extract from the value read from bus.
  
 ==== Expression Editor ==== ==== Expression Editor ====
Line 701: Line 701:
   * **KNX group** This property represents the KNX group associated to the variable.   * **KNX group** This property represents the KNX group associated to the variable.
   * **Type** Type of number to extract from the value read from the bus.   * **Type** Type of number to extract from the value read from the bus.
-  * **Trigger computation** This property is particularly usefull in case the same KNX group is used for both the result and another variable: in those situations loop may occurs. Setting this property to “Disabled” store the value for next computations and avoids loops. If the property is set to “Enabled”, the incoming values will trigger the computation of the expression and the sending of the new value.+  * **Trigger computation** This property is particularly useful in case the same KNX group is used for both the result and another variable: in those situations loop may occurs. Setting this property to “Disabled” store the value for next computations and avoids loops. If the property is set to “Enabled”, the incoming values will trigger the computation of the expression and the sending of the new value.
  
 <WRAP center round important 60%> <WRAP center round important 60%>
Line 734: Line 734:
     * Trigger KNX value: Permits to choose the value that has to be sent to the trigger KNX group to invoke KNX variables write. There are three alternatives: “All values”, “Only 1”, “Only 0”.     * Trigger KNX value: Permits to choose the value that has to be sent to the trigger KNX group to invoke KNX variables write. There are three alternatives: “All values”, “Only 1”, “Only 0”.
   * **Trigger write timebased** Permits to force the server to send (write) the content of the KNX variables to the KNX bus basing on a timer with a defined interval. When set to “Enabled” following property will appear:   * **Trigger write timebased** Permits to force the server to send (write) the content of the KNX variables to the KNX bus basing on a timer with a defined interval. When set to “Enabled” following property will appear:
-    * Trigger time interva: Time interval (in seconds) after which a new KNX variable write to the KNX bus is invoked.+    * Trigger time interval: Time interval (in seconds) after which a new KNX variable write to the KNX bus is invoked.
  
 ==== Adding a variable ==== ==== Adding a variable ====
Line 774: Line 774:
      * On new value reception: The server will send the value to the cloud every time it receives a telegram from KNX. This option is useful when the user wants a precise representation of the data during the day, for example, for power consumption. This option is although space consuming so we recommend to use it carefully.      * On new value reception: The server will send the value to the cloud every time it receives a telegram from KNX. This option is useful when the user wants a precise representation of the data during the day, for example, for power consumption. This option is although space consuming so we recommend to use it carefully.
      * After a fixed time interval: The server will read the value from KNX after a determined time interval and store it on the cloud. This option can be used, for example, to read temperatures and all that values that doesn’t change that much during the day.      * After a fixed time interval: The server will read the value from KNX after a determined time interval and store it on the cloud. This option can be used, for example, to read temperatures and all that values that doesn’t change that much during the day.
-     * On over-threshold  change: The  erver will store locally the last value received from KNX and it will compare it with the latest incoming telegram, if the difference between the two values overcrosses a predefined  threshold  it  will  store  the  new  value on the cloud. The threshold represents the ratio between the gap of the two values and the previously stored value. This option is useful because allows the user to keep trace only of the significant changes of the value during the day.+     * On over-threshold  change: The server will store locally the last value received from KNX and it will compare it with the latest incoming telegram, if the difference between the two values overcross a predefined  threshold  it  will  store  the  new  value on the cloud. The threshold represents the ratio between the gap of the two values and the previously stored value. This option is useful because allows the user to keep trace only of the significant changes of the value during the day.
      * On over-threshold change and after time: This option combines the advantages of both previously explained techniques. Data will be stored when over-threshold change occurs and, in any case, after a fixed time interval.\\ If the Store trigger property is set to ”After a fixed time interval”, the following property will be displayed:      * On over-threshold change and after time: This option combines the advantages of both previously explained techniques. Data will be stored when over-threshold change occurs and, in any case, after a fixed time interval.\\ If the Store trigger property is set to ”After a fixed time interval”, the following property will be displayed:
   * **Store time interval** Time interval to wait before the server sends the value to the database.\\ If the Store trigger property is set to ”On over-threshold change”, the following property will be displayed:   * **Store time interval** Time interval to wait before the server sends the value to the database.\\ If the Store trigger property is set to ”On over-threshold change”, the following property will be displayed:
Line 857: Line 857:
  
   * //Authorized//: the connection to the Configurator isn’t the first one and it was already authorized.   * //Authorized//: the connection to the Configurator isn’t the first one and it was already authorized.
-  * //Not Authorized//: the connection to the Configurator isn’t authorized (it usually happens the first time the Configurator detect the bridge). To authorize the connection, click the ”Register bridge” button and follow the procedure explained in the new window. If this procedure has a positive ending, the bridhe will switch to ”Authorized”.+  * //Not Authorized//: the connection to the Configurator isn’t authorized (it usually happens the first time the Configurator detect the bridge). To authorize the connection, click the ”Register bridge” button and follow the procedure explained in the new window. If this procedure has a positive ending, the bridge will switch to ”Authorized”.
  
 Clicking the ”Select bridge” button the selected bridge is associated to the Hue gateway object. Clicking the ”Select bridge” button the selected bridge is associated to the Hue gateway object.
Line 880: Line 880:
   * **Saturation** Current saturation value.   * **Saturation** Current saturation value.
   * **Color Temperature** Current color temperature.   * **Color Temperature** Current color temperature.
-  * **Effect** Currect color effect.+  * **Effect** Current color effect.
   * **Color** Selected color, by changing this property the properties above will assume different values.   * **Color** Selected color, by changing this property the properties above will assume different values.
  
Line 911: Line 911:
     * Hue group: Hue group previously configured with the Hue Bridge Finder tool.     * Hue group: Hue group previously configured with the Hue Bridge Finder tool.
     * Group ID: Identifier used to match the Hue group in the Hue Bridge.\\ Both lights and groups have the following properties:     * Group ID: Identifier used to match the Hue group in the Hue Bridge.\\ Both lights and groups have the following properties:
-  * **Simulate type** Type of feature to control with ThinKnx server: Dimmer coloured, Dimmer white, ON/OFF coloured, ON/OFF white and RGB.\\ If the Simulate type is ”Dimmer colored” or ”ON/OFF colored” the following property will be displayed:+  * **Simulate type** Type of feature to control with ThinKnx server: Dimmer colored, Dimmer white, ON/OFF colored, ON/OFF white and RGB.\\ If the Simulate type is ”Dimmer colored” or ”ON/OFF colored” the following property will be displayed:
     * Start color: Base color for the element.\\ If the Simulate type is ”Dimmer white” or ”ON/OFF white” the following property will be displayed:     * Start color: Base color for the element.\\ If the Simulate type is ”Dimmer white” or ”ON/OFF white” the following property will be displayed:
     * Color temperature: Base color temperature for the element (warm or cold).\\ If the Simulate type is ”Dimmer colored”, ”ON/OFF colored”, ”Dimmer white” or ”ON/OFF white” the following property will be displayed:     * Color temperature: Base color temperature for the element (warm or cold).\\ If the Simulate type is ”Dimmer colored”, ”ON/OFF colored”, ”Dimmer white” or ”ON/OFF white” the following property will be displayed:
Line 987: Line 987:
     * Parity: Parity check modality     * Parity: Parity check modality
     * Stop Bits: Number of stop bits.     * Stop Bits: Number of stop bits.
-    * Comm. timings: Serial timings to optimize communication over the RS485 bus. It depents on bus adapter, slave devices timings etc.\\ If in the proprerty ”Commmunication Type” is selected the setting ”Modbus Serial on TCP” or ”Modbus TCP”, the following properties will appear:+    * Comm. timings: Serial timings to optimize communication over the RS485 bus. It depends on bus adapter, slave devices timings etc.\\ If in the property ”Communication Type” is selected the setting ”Modbus Serial on TCP” or ”Modbus TCP”, the following properties will appear:
     * IP Address: IP address of the device or of the serial adapter     * IP Address: IP address of the device or of the serial adapter
     * IP Port IP: port used when the device listen for communication (502 is a standard for TCP protocol).     * IP Port IP: port used when the device listen for communication (502 is a standard for TCP protocol).
Line 1005: Line 1005:
   * **Nodes** Collection of the Z-Wave nodes registered inside the controller   * **Nodes** Collection of the Z-Wave nodes registered inside the controller
   * **Ping Nodes** If enabled, all the nodes will be pinged every minute. In this way a failed node will be promptly reported.   * **Ping Nodes** If enabled, all the nodes will be pinged every minute. In this way a failed node will be promptly reported.
-  * **Auto-Healing** Healing is a procedure to reconstruct network in case of nodes not reachables or moved. If Auto-Healing is enabled, it will be performed in case of a node is marked as failed. Healing will be performed during right-time at 2.00 AM.+  * **Auto-Healing** Healing is a procedure to reconstruct network in case of nodes not reachable or moved. If Auto-Healing is enabled, it will be performed in case of a node is marked as failed. Healing will be performed during right-time at 2.00 AM.
  
 <WRAP center round important 60%> <WRAP center round important 60%>
Line 1075: Line 1075:
 Each Z-Wave module included can have some Parameters to edit its functioning Each Z-Wave module included can have some Parameters to edit its functioning
  
-In the "Device parameter editor" window, depending on the deive you are configuring, you will find different parameters that can be adjusted according to your needs.+In the "Device parameter editor" window, depending on the device you are configuring, you will find different parameters that can be adjusted according to your needs.
  
-As an example you can see a couple of paramenters defined by NETIChome for their dimmer device:+As an example you can see a couple of parameters defined by NETIChome for their dimmer device:
  
 {{ :catalog-3.png?direct&400 |NETIChome Dimmer Parameters}} {{ :catalog-3.png?direct&400 |NETIChome Dimmer Parameters}}
 <WRAP center 60%> <WRAP centeralign> NETIChome Dimmer Parameters </WRAP>  </WRAP> <WRAP center 60%> <WRAP centeralign> NETIChome Dimmer Parameters </WRAP>  </WRAP>
  
-The association function “associates” two devices, enabling them to communicate directly without the need for controller. On the "Device association editor" window, you can set an assiciation with other Z-Wave devices and define the type of assiciation.+The association function “associates” two devices, enabling them to communicate directly without the need for controller. On the "Device association editor" window, you can set an association with other Z-Wave devices and define the type of association.
    
 ===== iRoomController ===== ===== iRoomController =====
  • system_objs.txt
  • Last modified: 2024/03/16 09:42
  • by wikiadmin