Chapter 7.1 – Configuring the DOMIQ Remote Control App in the DOMIQ System Configurator

The user interface in DOMIQ’s control apps is fully configurable, letting you tailor it to each client’s individual needs. Configuring the interface structure is therefore one of the most important tasks in the entire DOMIQ configuration process.

We offer a dedicated control app:

1. DOMIQ Remote – an app for mobile devices running Apple iOS and Android.
   
   • The DOMIQ Remote app can operate in one of two modes:
     
     • Menu – This mode consists of lists of controls that let you control the building or display the current state of devices/variables. Menu mode is displayed by default when the mobile device is held in portrait orientation. It’s also possible to set Menu mode for both device orientations. To do this, activate the Menu mode only option in the mobile app’s settings. Menu mode is not available in the AirDisplay app. The Remote tab is used to configure this Menu mode.
     • Visualization – Visualization mode is a graphical representation of the building (background), on which the active controls and elements displaying the state of devices/variables are shown. Visualization mode lets you instantly see an overview of the entire building/floor. Thanks to navigation functions, it’s possible to create a visualization consisting of multiple screens. The Visualization tab is used to configure this mode.
       
   • RECOMMENDATION: If this is your first time configuring the Base module, we recommend that, before moving on to the next stage, you install the DOMIQ/Remote app and familiarize yourself with its built-in demo mode. This will help you understand the structure of the user interface and make it easier to grasp the concepts discussed further on. Menu mode does not require a connection to the Base module. The app is available for free on the App Store and Google Play.
     
   • IMPORTANT! The app uses a shared configuration on every device, so it displays the same interface structure everywhere. To differentiate the structure of the displayed Menu, use user profiles, which are created in the DOMIQ system’s configurator.
     

Remote #

The Remote tab in the DOMIQ system’s configurator contains the editor for building the Menu mode interface structure for the DOMIQ Remote app. The screen is divided into two parts.
On the left is a list of available controls that can be used to build the user interface. The available elements are divided into four main groups:

1. Structure
2. Channel Controls
3. LCN
4. IDS

The right part of the window displays the user interface structure.

1. New elements are added using drag and drop. So, to add a new element to the structure, select it from the list of available controls, then drop it in the desired location in the structure tree.
   
2. To change the position of an element in the structure, drag the selected element and drop it in the new location.
3. If an element cannot be added in the selected place, you will see a red indicator. For correct operations, the indicator is green.
4. Several rules regarding the hierarchy of elements apply in the structure tree:
   • Only elements of type Page can be added at the top level.
   • Only elements of type Section can be added directly inside Pages.
   • Inside Sections, all available controls can be placed, except for another Section.
     
5. To change the properties of a selected element, double-click on it – a control editing window will then be displayed.
   
6. To delete element(s), select them by clicking the checkbox on the right side of the label, and then click the Delete button or the Backspace key on the keyboard. If the interface element being deleted has nested elements, they will also be deleted.
7. To copy an element, click on it (a blue rectangle will appear to the right of the label), then click the Copy button or use the keyboard shortcut Ctrl+C. The element is now copied and stored on the clipboard.
   
8. To paste the copied element, use the Paste button or the Ctrl + V keyboard shortcut. The copied control will be placed in the following location:
   • Below the currently selected control;
   • at the end of the section, if a Section-type element is selected;
     
9. The search field lets you quickly find elements in the structure. You can search by label and by control type. Typing “dimmer” in the search bar, for example, will display all controls of that type found throughout the entire configuration.
   
10. The Select All checkbox allows for quick selection of all elements in the structure. This is particularly useful when you want to quickly delete the entire structure.

At the top of the tab is a bar with buttons:
The Copy, Paste, and Delete buttons have already been covered.

1. Import – Allows importing an .xml configuration file.
2. Export – Allows saving the current interface structure to an .xml file.
3. Export selected – Lets you save to a file only the elements whose checkbox is checked. It’s common to duplicate a given piece of functionality across multiple installations. This way, you can export just part of the interface and use it in another location.
4. Save – Saves the current configuration in the memory of the Base module.
5. Restore – Loads the last saved configuration into the structure tree.

The rest of this subsection describes all the available controls.

1. Structure
#

1.1. Page #

A Page is the basic building block of the Menu mode structure in the DOMIQ/Remote app. The main view of Menu mode in the Remote app is an icon grid – a well-known and very popular design used, among other things, on the home screens of mobile device operating systems. In the Remote app, the grid elements are links to Page-type controls located at the top level of the structure. This gives the user instant access to the most frequently used pages of the interface.

Think of a Page-type element as a parent container in which other controls are placed. Each page corresponds to a separate screen in the app. Only Section-type elements can be added directly to a Page. Additional Pages can then be nested within them, making it possible to build hierarchical structures.
The most common approach to building the structure is dividing controls:

1. by room – The structure is divided by the rooms in the building. With this approach, the top level of the structure contains pages corresponding to individual rooms, with the controls available in that room placed inside them.
2. by functionality – The top level of the structure contains pages that group controls for a specific building function, e.g. lighting, heating, blinds, alarm, cameras, etc. Controls for individual devices are then placed inside the relevant page.
   Additionally, for better organization, it’s worth grouping the controls assigned to a given room inside Section-type elements. Of course, a combined approach can also be used.

CONTROL EDITING

Every page must have a label assigned (the Label field). It’s recommended that top-level controls have an icon assigned, since they will then be displayed within the grid on the home screen (the Icon dropdown list). A page can have a list of commands assigned that will be executed when the mobile device is shaken (iOS only, and only when the page is currently displayed)
– the Shake tab. It’s also possible to assign a list of commands that will be executed when a given page is displayed in the app – the Press tab.
The Actions table is described in subsection 8.4, Actions.
The Access Control table lets you select the user profiles that should have access to this element. Users without permission will not see this element in the Remote app on their devices.

1.2. Section #

A Section is an element that lets you group controls, e.g. a lighting control section, ventilation, etc.

As mentioned earlier, Pages can be added to a Section, allowing you to build more complex user interface structures. A Page added to a Section is marked in the Remote app with an angle-bracket symbol to the right of the label.

CONTROL EDITING

A Section may or may not have a label assigned. Like a Page, it also has an Access Control table.

CHANNEL CONTROLS

The controls in this group are based on the identifiers described in Chapter 5, State, Commands, and Events. A detailed description of identifiers can be found in Chapter 12, Identifiers.

2. General Control
#

2.1. Button Group
#

This user interface element lets you group Buttons together. Its default use is to group buttons that perform some shared functionality. One example is a group of buttons for controlling the ventilation speed setting, where each button has a command assigned with a specific speed setting. Another example is a group of buttons that trigger lighting scenes in a room.

CONTROL EDITING

1. Label – The label will be displayed in the app above the button group.
2. Number of columns – Determines how many columns the buttons will be grouped into. You can choose a value from 1 to 8. Selecting 1 means the buttons will be displayed one below another. If 2 is selected, the buttons will be displayed in two columns, and so on. Default value: 4.

2.2. Button #

A Button is a very universal user interface element. It can be part of a button group or appear on its own. A Button distinguishes between a short press, a long press (over one second), and releasing the button.

CONTROL EDITING

1. Label – The label will be displayed in the Remote app next to the button.
2. Icon – The icon that will be displayed inside the button.
   
3. A list of commands can be assigned to each type of action – this is done via the Short, Long, and
   Release tabs. Each tab contains an Actions table, which is covered in subsection 8.4, Actions.
   

2.3. Camera #

The Camera element is used to display a video feed from an IP camera in MJPEG format.

CONTROL EDITING

1. Label – The label displayed in the Remote app’s menu.
2. URL – The address of the MJPEG video stream.
3. Username – The username for logging in to the camera.
4. Password – The user’s password for logging in to the camera. The Username and Password fields are optional. They should be filled in if access to the stream requires authorization.
5. Type – Possible values: Any MJPEG, Vivotek, Axis, Mobotix, Any JPEG. If you’re using Axis, Mobotix, or Vivotek cameras, you only need to provide the hostname and/or port in the URL field; the rest of the address is not required.
6. Pan-tilt head – This option should be checked if the camera has a pan-tilt head.
7. Zoom control – This option should be checked if the camera has a controllable lens zoom and you want to control it.

The remaining fields only need to be filled in for cameras with a controllable pan-tilt head. Moving your finger across the screen of the device running the DOMIQ/Remote app will move the camera’s head. You’ll need to look up the exact command content in the camera’s user manual.

1. Left – The command for moving the camera left.
2. Right – The command for moving the camera right.
3. Up – The command for moving the camera up.
4. Down – The command for moving the camera down.
5. Zoom in: – Currently unsupported feature
6. Zoom out: – Currently unsupported feature

You can read more about using cameras in the Remote app in the tutorial: https://domiq.pl/wiki/domiq-remote/kamery-w-remote/

2.4. Chart #

A control designed for displaying charts from Grafana software.

CONTROL EDITING

• Label – The label displayed in the Remote app’s menu.
• Local URL – The URL under which the chart is available on the local network.
• Remote URL – If the chart preview should be available outside the local network, enter the address of the Grafana dashboard that is reachable from the Internet in this field.

You can read more about integration with Grafana software in the tutorial:
https://domiq.eu/wiki/grafana-en/charts-in-the-domiq/

2.5. Switch #

A Switch is one of the most frequently used interface elements, letting you control any identifier by toggling its value between two states. By default, the switch sends the value on for the on state, and off for the off state. A Switch can be used to control, for example, a relay output or a dimmable output, to set the values of variables (VAR, MEM), etc.

CONTROL EDITING

1. Label – The label displayed in the Remote app’s menu.
2. Channel – The name of the identifier the Switch is to control.
   • LCN.relay.0.36.1 Controls relay No. 1 in the LCN module at address 36.
3. On (optional) – The value that will be sent to the identifier when the switch is turned on.
4. Off (optional) – The value that will be sent to the identifier when the switch is turned off.
5. Parameters – Additional parameters that will be sent along with the command. If several parameters are to be sent, separate them with a semicolon.
   • ramp:3
     This is an example of using a parameter to control lighting with a ramp. It can be used, among other things, to control an LCN dimmable output or a DMX channel.
   • pin:12345
     This is an example of using a parameter to control an output on a Satel control panel.
6. Invert value – Checking this field reverses the switch’s operating logic.

2.6. Dimmer #

A Dimmer is designed for controlling any identifier within a declared range of values. The default range is 0-100. A Dimmer can be used to control lighting, fan speed, volume, temperature, etc.

A Dimmer is displayed in the Remote app as a slider. Clicking the label showing the current value toggles the value between the minimum and maximum of the assigned range.

CONTROL EDITING

1. Label – The label displayed in the Remote app’s menu.
2. Channel – The name of the identifier the Dimmer is to control.
3. Minimum – The minimum value the slider can be set to. Range: -99999 to 99999.
4. Maximum – The maximum value the slider can be set to. Range: -99999 to 99999.
5. Step – Determines the minimum change that can be made by moving the slider. Default value: 1.
   Range: -99999 to 99999.
   • LCN.output.0.112.1
Controls dimmable output No. 1 in the LCN module at address 112
   • UAV.volume.Biuro
     Controls the volume of a Sonos player.

2.7. RGBW Light #

The RGBW Light control is a universal control for controlling RGB(W) lighting. The white (W) channel is optional.
Examples of use:

1. Controlling LED lighting using the DMX-512 protocol and the Serial-4DX module. You can read more about this type of control in the tutorial:
   https://domiq.eu/wiki/domiq-modules/led-lighting-control-2/
2. Controlling lighting connected to the dimmable outputs of an LCN module.

CONTROL EDITING

1. Label – The label displayed in the Remote app’s menu.
2. Red – The identifier responsible for controlling the red component.
3. Green – The identifier responsible for controlling the green component.
4. Blue – The identifier responsible for controlling the blue component.
5. White – The identifier responsible for controlling the white component.

The RGBW Light control, as displayed in the Remote app, consists of:

1. Brightness slider: Controls the lighting’s brightness (shared across all components). To turn off the lighting, move the slider all the way to the left. When the lighting is off, the Color selection ring is inactive.
2. Saturation slider: Controls the saturation of the lighting’s color.
3. Color selection ring: Used to select a color from the RGB color range.
4. Current color indicator: Displays the currently selected color, taking brightness and saturation into account.
5. White component brightness slider – Only displayed when the White field is filled in. Controls the brightness of the white lighting.
   

2.8. Value #

The Value control is a universal interface element for setting and displaying values. This control can be used to set and display temperature, change VAR/MEM variable values, etc.
In “Read-only” mode, it acts as a universal element for displaying the state of any identifier in the DOMIQ system. Thanks to additional parameters in the control’s settings, it’s possible to determine the format of the displayed value.

CONTROL EDITING

1. Label – The label displayed in the Remote app’s menu.
2. Channel – The identifier you want to control or whose state you want to display.
3. Unit – The unit of the displayed value.
4. Read-only – When this field is checked, the control only displays the identifier’s state, without the ability to change the value.
5. Minimum – The minimum value that can be set. Range: -99999 to 99999.
6. Maximum – The maximum value that can be set. Range: -99999 to 99999.
7. Step – Determines the minimum change that can be made. Default value: 1. Range: -99999 to 99999.
8. Offset – The value entered here will be added to the identifier’s current value. Range: -99999 to 99999. Default value: 0
9. Multiplier – A value by which the identifier’s current value will be multiplied. Range: -99999 to 99999. Default value: 1.
10. Decimal places: Determines how many decimal places will be displayed. Range: 0 to 4. Default value: 0.
    

2.9. Roller blind #

A universal control for operating blinds. The control sends the commands: up, down, and stop to the specified identifier.

CONTROL EDITING

This element’s definition consists of the following properties:

1. Label – The label displayed in the Remote app’s menu.
2. Channel – The identifier responsible for controlling the blind. Examples of identifiers below:
   • LCN.motor.0.36.1
     Controls positioning blind No. 1, connected to the LCN module at address 36, in segment 0.
   • EXP.shutter.1.1
     Controls blind No. 1 using the DOMIQ/Expander module, connected to the SATEL INT-IORS module at address 1.
   • rolety.parter
     Controls the state of a custom identifier, rolety.parter.

2.10. Status #

The Status control is used for the graphical representation of the state of any identifier, e.g. an LCN output or relay, an IDS system sensor, a logical variable, etc.

CONTROL EDITING

1. Label – The label displayed in the Remote app’s menu.
2. Channel – The identifier whose state is to be displayed.
3. Icon on: The graphical representation for the on state.
4. Icon off: The graphical representation for the off state.

2.11. Thermostat #

A Thermostat is a universal control for controlling temperature. The control’s graphical representation in the Remote app consists of a setpoint element and a chart of the temperature measured by the sensor specified in the configuration. The chart shows temperature changes over the last 24 hours. The chart’s source data is not retained after the Base module is restarted.

CONTROL EDITING

1. Label – The label displayed in the Remote app’s menu.
2. Channel for the setpoint value – The identifier to which commands with the target temperature value will be sent.
3. Channel for the current value – The identifier of the temperature sensor being measured. The temperature chart is built based on this identifier’s value.
4. Minimum – The minimum setpoint temperature value.
5. Maximum – The maximum setpoint temperature value.

IMPORTANT! Kontrolka ma wbudowane skalowanie wartości wg skali LCN. Wyraża się ona wzorem:

wartość * 10 + 1000.

So, for the setpoint element to work correctly and for the chart to be plotted, you need to make sure the values passed to the identifiers are expressed according to this scale. The examples below contain pairs of identifiers, where the first is the setpoint value, and the second is the current value:

• LCN.regulator.0.10.1
LCN.value.0.10.t
The setpoint value will be sent to/from LCN regulator No. 1 in the module at address 10, in segment 0. The current temperature value will be read from variablet (variable 1 in newer modules).
  IMPORTANT! For the LCN system, for backward compatibility, only the first three variables and the LCN.value identifier may be used. The first three variables correspond to the identifiers:
  LCN.value.S.M.t
LCN.value.S.M.r1where S and M are the segment and module. LCN.value.S.M.r2
• MEM.set
MEM.current
An example of control using MEM variables.

2.12. Text #

The Text element is used to display any text content, e.g. labels, measured values, relay states, logical variable states, etc.

CONTROL EDITING

1. Label – The label displayed in the Remote app’s menu.
2. Channel – The identifier whose content you want to display as text.

2.13. Selection #

The Selection control is a very universal element, applicable anywhere the system needs to give the user a choice from a predefined list of values.
Examples of use:

1. selecting the days of the week on which a given time-based rule is to be executed;
2. selecting the heating/air conditioning operating mode;
3. selecting the ventilation speed;
4. selecting the zones to be watered;

CONTROL EDITING

1. Label – The label displayed in the Remote app’s menu.
2. Channel – The identifier to/from which the value of the options selected by the user will be sent.
3. At least one – If this option is checked, the user must select at least one of the available options in order to change the identifier’s current state.
4. Multiple selection – If enabled, the user can select multiple options from the available list. If the user selects several options, their values will be saved in the identifier’s state, separated by commas (see examples below). If this option is not checked, the control operates in single-selection mode (like a typical radio button).
5. Read-only – The control displays the selected values based on the identifier’s current state, without the ability to change them (the selection screen is unavailable). This is very useful anywhere you need to convert numeric values into text values – e.g. from day-of-the-week numbers to their names, or from numeric fan speed settings to more user-friendly names.
6. Value table – This is the main element of the control, used to define the set of options that will be displayed in the selection list in the Remote app.
   • Add – Click to add a new row to the table.
   • Delete – Select an item and click this button to delete row(s) from the table.
   • Value – In this column, enter the value that will be sent to the identifier when this option is selected by the user.
   • Short name – The value entered here will be displayed next to the label in the control list in the Remote menu.
   • Full name – The value entered here will be displayed in the selection view in the Remote app.

Below are examples of Selection control configurations from real-world implementations. #

1. Selecting the days of the week on which a time-based event is to be executed.
   Note! The first day of the week is Sunday.
   Channel: MEM.days
   Multiple selection: checked

Let’s say the user selects the days from Monday to Friday. In that case, the MEM.days identifier will have the value: 2,3,4,5,6.
The MEM.days identifier can then be used in a timer definition as the data source for the days of the week on which the timer should be triggered. An example definition of such a timer can be found at the end of Chapter 8.3, Timers.

2. Selecting the ventilation speed.
   Integration with ventilation systems is most often carried out using the MODBUS protocol, in which case speed is controlled by changing the value of a MODBUS register on the ventilation control unit. You can find out more about integration using the MODBUS protocol in Chapter 9.2, MODBUS.
   Channel: MODBUS.int.vent.speed
   Multiple selection: unchecked
   At least one: checked

The value assigned to the option selected by the user will be sent as a command to the identifier entered in the Channel field, thereby changing the ventilation speed.

2.14. Time #

The Time control is an interface element that lets the user select the hour and minute at which a time-based event will be triggered.
An example of defining a time-based event using the Time element is presented in Chapter 8.3, Timers.

CONTROL EDITING

1. Label – The label displayed in the Remote app’s menu.
2. Channel for hours – The name of the identifier in which the hour selected by the user will be stored.
3. Channel for minutes – The name of the identifier in which the minute selected by the user will be stored.

Identifiers referring to non-volatile MEM-type variables are most often used for minutes and hours, since they ensure that the settings entered by the user are not lost even if the Base module loses power.

3. LCN #

The LCN control group contains elements dedicated for use in conjunction with LCN modules.

3.1. Dimmer #

A Dimmer is designed for controlling a dimmable output on an LCN module within a declared range of values. The default range is 0-100.
A Dimmer is displayed in the Remote app as a slider. Clicking the label showing the current value toggles the value between the minimum and maximum of the assigned range.

CONTROL EDITING

1. Segment – The segment number in the LCN system where the selected LCN module is located.
2. Module – The LCN module’s ID within the selected segment.
3. Select from list – Clicking this displays a window with a list of LCN modules available in the installation, letting you select the command’s recipient.
4. Label – The label displayed in the Remote app’s menu.
5. Output – The dimmable output number (1-4).
6. Minimum – The minimum value the slider can be set to. Range: 0 to 100.
7. Maximum – The maximum value the slider can be set to. Range: 1 to 100.
8. Step – Determines the minimum change that can be made by moving the slider.
   Default value: 1. Range: 1 to 99.

3.2. Switch #

A Switch lets you define a multifunctional interface element. Depending on the option selected in the Type field, different functions are performed. The way this element is defined also differs for each option:

RELAY

If Relay is selected, the control operates a relay in the LCN module.

CONTROL EDITING

1. Segment – The segment number in the LCN system where the selected LCN module is located.
2. Module – The LCN module’s ID within the selected segment.
3. Select from list – Clicking this displays a window with a list of LCN modules available in the installation.
4. Label – The label displayed in the Remote app’s menu.
5. Type – Relay
6. Relay: The relay number assigned to this element. Possible values: 1 to 8.
7. Invert value: Checking this option reverses the button’s operating logic.
   

WYJŚCIE

If Output is selected as the type, the Switch controls a dimmable output on the LCN module, but in on/off mode.

CONTROL EDITING

1. Segment – The segment number in the LCN system where the selected LCN module is located.
2. Module – The LCN module’s ID within the selected segment.
3. Select from list – Clicking this displays a window with a list of LCN modules available in the installation.
4. Label – The label displayed in the Remote app’s menu.
5. Output: The number of the proportional output assigned to this element. Possible values are 1-4.
6. Threshold: The output value above which the output is considered to be on. Allowed range: 1-100
7. Ramp: The ramp value with which the output changes its value. Available range: 0-20.
8. Invert value: Checking this option reverses the button’s operating logic.
   

3.3. Temperature #

Temperature is a user interface element that displays the current and setpoint temperature. Clicking the control displays a new page with a chart of temperature changes (last 24h) and the ability to change the setpoint temperature (only if Thermostat was selected as the temperature control method).

CONTROL EDITING

This element’s definition consists of:

1. Segment – The segment number in the LCN system where the selected LCN module is located.
2. Module – The LCN module’s ID within the selected segment.
3. Select from list – Clicking this displays a window with a list of LCN modules available in the installation, letting you select the command’s recipient.
4. Etykieta – Etykieta wyświetlana w menu aplikacji Remote.
5. Sensor – The variable in the LCN module from which the current temperature is read; possible values are TVar, R1Var, or R2Var (in the new generation of modules, this corresponds to variables 1 through 3).
6. Control method – Available options: Thermostat, Threshold value. If Thermostat is selected, temperature will be controlled using a proportional LCN regulator. If Threshold value is selected, control will be carried out using threshold values programmed in LCN-Pro.
7. Minimum – The minimum temperature value that can be set using the control.
8. Maximum – The maximum temperature value that can be set using the control.

Thermostat

• Thermostat Regulator: The regulator in which the setpoint temperature is set. Allowed values: 1-2.
  

Threshold value

• Threshold value – the number of the threshold value that the control applies to.
• Programmed value – The programmed threshold value, relative to which the changes are made. Range: -200:200

3.4. Roller blind #

Shutter is an interface element that operates a shutter motor.

CONTROL EDITING

1. Segment – The segment number in the LCN system where the selected LCN module is located.
2. Module – The LCN module’s ID within the selected segment.
3. Select from list – Clicking this displays a window with a list of LCN modules available in the installation, letting you select the command’s recipient.
4. Label – The label displayed in the Remote app’s menu.
5. Type – The shutter control method. The following types are available:
   • Relays (without positioning) – the shutter is controlled using a pair of relays, with no positioning information.
   • Relays (with positioning) – the shutter is controlled using a pair of relays with positioning information (requires the LCN-BS4 module).
   • Analog output – shutters connected to the dimmable outputs on the LCN module.
6. Motor: The number of the motor the shutter is connected to. Only available when relay-based shutter control is selected. Each motor requires a pair of relays. The first relay of the pair powers the motor, while the second controls the shutter’s direction of movement.
   Available options:
   • 1, 2, 3, 4 – controlling individual motors
   • 1+2, 3+4 – controlling pairs of shutters
   • 1-4 – controlling the entire relay block – 4 shutters

3.5. LCN Binary Input #

LCN Binary Input displays the current state of a binary input on an LCN module.

CONTROL EDITING

1. Segment – The segment number in the LCN system where the selected LCN module is located.
2. Module – The LCN module’s ID within the selected segment.
3. Select from list – Clicking this displays a window with a list of LCN modules available in the installation, letting you select the command’s recipient.
4. Label – The label displayed in the Remote app’s menu.
5. Sensor: The number of the LCN binary input whose state is to be shown. Allowed value: 1-8
6. Icon on: The way the input is represented in the on state.
7. Icon off: The way the input is represented in the off state.

4. IDS #

The elements in the IDS (Intrusion Detection System) group are dedicated for use with the SATEL Integra alarm system.

4.1. IDS Input #

IDS Input is a control that displays the current state of an alarm system input. This control can be used, for example, to display the open/closed state of windows, doors, or PIR sensors.

CONTROL EDITING

1. Label – The label displayed in the Remote app’s menu.
2. Input – The number of the IDS system input whose state is to be displayed. The allowed value depends on the number of inputs on the given alarm control panel (max. 256).
3. Icon on: The way the input is represented in the on state.
4. Icon off: The way the input is represented in the off state.

4.2. IDS Output
#

IDS Output is a control that displays the current state of a single alarm system output.

CONTROL EDITING

1. Label – The label displayed in the Remote app’s menu.
2. Output – The number of the IDS system output whose state is to be displayed. The allowed value depends on the number of outputs on the given alarm control panel (max. 256).
3. Icon on: The way the output is represented in the on state.
4. Icon off: The way the output is represented in the off state.

4.3. IDS Zone #

IDS Zone is a user interface element that displays the current state of an alarm zone and lets you arm and disarm it. Clicking the control displays a screen with a keypad for entering the PIN code.

The alarm zone’s state is represented by the control’s differing appearance. There are five distinct states:

1. Gray control – zone disarmed.
2. Green control – zone armed.
3. Red control – alarm.
4. Blinking gray/green – exit delay.
5. Blinking gray/red – entry delay.
   

CONTROL EDITING

1. Label – The label displayed in the Remote app’s menu.
2. Zone: The alarm zone number.