All devices in the intraHouse system are virtual. They can be placed on mimic diagrams and used in scenes. Practically it is possible to configure the entire system without real physical devices (sensors and actuators).
The binding of virtual devices to real devices is done using plugins.
After adding a new device or by double-clicking on an existing device, the properties window opens:
On the Device tab, you can configure the following settings:
- Device ID – identification number of the device. This field is available only when adding a new device. Usually, in our practice, we try to assign an identification number in accordance with the schematic diagram of the automation system. This is convenient, but not necessary.
- Name – device name. The system sets the default name. It is recommended to change this name according to the real device. In this example, instead of “Universal analog sensor” it is better to write, for example, “Humidity sensor”
- Level – belonging of the device to any level.
- Zone – belonging of the device to any zone.
- Subsystem – belonging of the device to any subsystem.
- Unit – optional for analog values. For example, ºС. This parameter will be displayed along with the value.
- Number of decimal places – optional for analog values. The default is 0
"DB - Database" tab
The “Database” tab is only available when editing the device and when the database management system (MySQL) is installed.
On the DB tab, you can configure the following settings:
- Store value in the DB – Set that tick to store the device values in the database.
- Store in the DB only when changes – you can store in database only those values from the device that have changed from the previous value. This will help to save a hard disk space.
- Delta of change – you can store in database only those values that have changed more than the delta value.
- Store in database at interval – .
States are used for visualization, as well as for generating events. The states in which a device can be located are displayed for each device in the lower table. To call up the states table, select the device and click the button with two rectangles.
By default, devices have 2 states – 0 and 1:
For discrete devices: 0 (OFF) – switched off, no operation, … 1 (ON) – switched on, there is operation, …
For analog sensors: 0 – value is not removed, 1-value is removed
Double click on the state record to proceed to editing.
On the “General” tab, you can customize the name, image and color for the visualization:
On the “Logging” tab you determine whether it is necessary to fix in the log the transition to this state and what level is assigned to the message. The next two parameters determine whether the message requires interactive confirmation and how messages are hidden in the operational log. To save the edited parameters, you need to click the green diskette in the lower table.
Changing the state set
You can define a method for determining the state for each device on the “Additionally” tab.
A standard two-state method is used by default.
For analog sensors, you can change the method and use the intervals:
As it seen in the figure above, the following states were added to the sensor:
t <= 5 – Cold
5 < t <= 25–Warm
25 < t <= 40 – Hot
t > 40 – Scorching heat
New states are added by copying (the button next to the plus button).
For each state, you need to set the upper bound of the interval. States are numbered as the boundary value increases in succession.
Now when transitioning to a new state, messages will be generated, some of which will appear in the operative log.
After placing on the mimic diagram, the device will have 5 states, for which you can additionally adjust the visual effects directly on the mimic diagram.
- If intervals are specified, on the “Additionally” tab for the device, the attribute The method for determining the state should be set to Analog value – intervals;
- The states must be determined before placing the device on the mimic diagram
- Visual changes (changing the picture, color) made on the mimic diagram, do not affect the state settings in the table. This allows to create different visualizations for one device.
In addition to the basic dynamic property (current state), the device can have properties that can be added by a scene or plugin.
There are also several built-in optional properties that allow to implement standard functions, simplify scenes and visualization:
- blk – blocking;
- defval – threshold or default value;
- auto – automatic mode.
Activation of the built-in properties is performed in the device table in PM separately for each device.
The blk property
Blocking the sensor, usually discrete. Used to temporarily disable scenes that are executed when the sensor is triggered in the event of its incorrect operation. Also can be used to lock actuators.
Activated by the flag: The device can be blocked
Visualization: the lock indicator can be displayed on the icon, and also interactively switches (in the device settings window)
The defval property
Setpoint for analog sensors or default value for analog actuators. Activated by the flag: There is a setpoint
Visualization: the value can be displayed on the icon, and also changed by the slider (in the device settings window)
The auto property
Activated by the flag: There is an automatic mode
Visualization: indicator “A” is displayed on the icon, and also interactively switches (the side menu of the device)
There is the auto property in actuators. Used by scenes. What is it used for?
Automatic algorithms are good, but sometimes it’s convenient to disable them temporarily.
For example, regularly the light is turned on by the motion sensor and turns off after a specified time in the absence of movement. But we want to turn it off manually, despite the movement. Or the fan works on high humidity and turns off at normal. But it is necessary to turn on at normal (or on the contrary)
That is, you want to temporarily take over control.
It’s easy to implement this option by using the auto property: the scene works when the flag auto is set, and if auto is cleared, it does not work. That is, you can just disable auto, and the scene that implements automatic behavior will not work. At the same time, there is an indication on the device and we control the situation ourselves.
But this decision has two disadvantages: you need to disable the Auto mode somehow (from the interface, from the button …) and don’t forget to restore it.
You can go further – to assume that if the user started to switch the device himself (from the switch, from the interface), means he takes over control, so the auto mode is temporarily disabled and then automatically restored without user intervention.
For this solution, the Reauto mechanism and special aon/aoff commands are added to the system.
It works like this:
- A scene that implements automatic behavior only works if the auto mode is enabled;
- This scene performs switching by the special commands aon / aoff (automatic on / off)
- When switching the device without such a command it means that the device is manually controlled: auto is reset and a timer is cocked which will restore the automatic mode after a specified time. These times (separately when on and off) are set in the sidebar of the device properties on the Settings tab. During the temporary disconnection of auto on the device icon appears watch, instead of A, and on the Settings tab you can see the time when the machine will be restored. The user can restore / disconnect Auto by himself
Note 1: The reauto mechanism can be not use. In that case, set the time at 00:00:00
Note 2: The aon / aoff commands can be used in any scene. If the auto property is not connected to the device, or the times are set to 0, then on / off commands will be executed.
There are two options for group lighting off, for example:
Lamps with automatic scenes will be switched to reauto (watch), and won’t turn on by the motion for the specified time
Lamps with automatic scenes will retain the auto mode and will be turned on if there is a motion, despite a general trip
Note. subs is a subsystem.