It is possible to control e.g. thermostats and blinds together.
There are a few possible approaches:
doc_tap_control_approaches;
doc_tap_Gro;
Create a group of thermostats / blinds in Virtual devices, and add slave devices that you want to control with this group.
Each device has autonomy, but when controlled by the group master, they all receive the same command.
doc_tap_Create_ther_comm;
Positives: docdoc_tap_1Positiv;
possible to assign automatic smart rules directly to group device response time is faster compared to Link smart rule approach
doc doc_tap_possible_response;
Negatives: doc doc_tap_1Neg;
Unable to see real values of grouped slave devices on the master device doc_tap_Unable;
doc_tap_1Avail;
Analog output group, Blind group, Slide group, Electric meters group
doc_tap_Analog_group;
Example:
Changing value of Blind group is also applying the change to both linked blinds.Please note that Blinds East is in Manual override mode, because it had active smart rule and a manual change was performed on Blind group.
doc_tap_Exa_Blind_group;
doc_tap_Linksr;
Connect multiple devices with "Link" smart rule. Master and slave devices can be defined.
doc_tap_multidef;
| Info |
|---|
IMPORTANT: Link smart rule only evaluates manual value changes. For example, if master thermostat if changed by Weekly schedule smart rule, this change is not applied to linked slave thermostat. doc_tap_Important_thermo; |
doc_tap_2Positiv;
simple setup, no need for creating extra virtual device possible to assign priority when evaluating Link smart rule
doc_tap_simple_rule;
Negatives: docdoc_tap_2Neg;
slower response time if evaluation is complex
doc_tap_slower;
Available for: docdoc_tap_2Avail;
Switch, Thermostat, Analog output
doc_tap_Analog_outp;
Example:
Manual change of temperature on Thermostat living room changes also temperatures on other master thermostats (Thermostat kitchen), as well as on other slave thermostats (bedroom, kids room 1 and 2).
However if Thermostat bedroom is manually changed, it does not affect any other thermostat, only itself, because it is defined as slave.doc_tap_Exa_Thermo_slave;
