System and method for controlling at least one device

[0001] The invention relates to a system and method for controlling at least one device, said system comprising at least one controlled assembly associated with said at least one device and a plurality of nodes for transmitting control signals to said at least one controlled module.

Background of the invention [0002] In control systems that include control points, sensors and actuators, such as e.g. home automation systems, certain priority rules can be established, e.g. to ensure that commands having a higher priority than others executed immediately, and furthermore to ensure that such commands can prevent lower priority commands from being executed, e.g. for a certain period.

[0003] Usually, such priority levels are ordered in decreasing order, e.g., in the order: user safety, product or environmental protection, manual user control, automatic comfort control. Thus, if e.g. a control signal is sent from the rain sensor to the window actuator, signaling that the open window must be closed due to rainfall, i.e. at the environmental control level, another control signal from the temperature sensor, indicating a high temperature, because of which, for example, a window should be opened for ventilation, i.e. at the level of automatic comfort control, the control signal sent from the temperature sensor due to priority will not be able to trigger action as long as the rain sensor signal works. Most home automation technologies are designed so that when a certain priority level is active, all lower levels are blocked.

[0004] However, this can cause confusion and dissatisfaction with the user's control system because he / she may not understand why the control signal sent e.g. from the remote control is not being executed. For example, the awning above the terrace can be locked in the upper position because the wind blows and the wind speed exceeds the set level, e.g. signaled by a wind sensor in the system. However, if the user tries to control the awning with his remote control to lower it, e.g. because the sun is shining, the user cannot understand why the awning does not lower. The user may think that the remote control is damaged, the awning is damaged or that the system as a whole is malfunctioning.

[0005] Furthermore, the control system may be configured to block certain actuations under certain circumstances, which may normally be beneficial, but which may at some times conflict with user requirements. For example, the system can be programmed to prevent the blinds / roller blinds from rising when the sun is shining, e.g. to protect furniture, rugs etc. from sunlight. In some cases, you may want to cancel this setting and raise the blinds / blinds using the remote control.

[0006] Document US 2005 046360 A1 tracks the current states of devices to be controlled in such a way that the behavior of the devices is consistent with the behavior expected by the device operator.

[0007] Thus, it is an object of the invention to provide a control system and method for controlling such a system that brings improvements over known systems.

[0008] Furthermore, it is an object of the invention to provide such a control system and such a method of controlling such a system, which avoids user confusion in such situations.

[0009] The object of the invention is also to provide such a control system and such a method of controlling such a system, by means of which the management capability of the control system, e.g. a home automation system, can be improved, allowing, for example, that the execution of commands from a particular type of node may be prevented.

[0010] These and other objects are achieved thanks to the invention, which is explained in detail hereinafter.

Summary of the Invention [0011] The invention relates to a system for controlling at least one device, such as e.g. actuator for doors, gates, windows, blinds, blinds, curtains, awnings or light sources, said system comprises at least a controlled module associated with said at least one device and a plurality of nodes for sending control signals to said at least one controlled module, in at least one of said many nodes for sending control signals is configured to send a command initiator, said command initiator contains identification data of the determined type of node from which the signal originates.

[0012] In this way, it is obtained that if a control signal sent from another node in the system, e.g. from a remote control, to the controlled module is rejected because the previous command / control signal has blocked the controlled module, the controlled module can inform that other node about the cause.

[0013] If we consider the example given earlier, in which the awning above the terrace is blocked in the upper position because the wind blows and the wind speed exceeds the set level, e.g. signaled by a wind sensor in the system, in which the user tries using his remote control lower the awning, e.g.

because the sun is shining, the user may receive information from the awning in response to a signal, for example a confirmation signal containing a failure state and an indication that the command cannot be carried out because the wind sensor has blocked the awning preventing it from moving.

[0014] It should be understood that the control signal may be transmitted from a different type of controller than the user-operated remote control, but also in this case information regarding the type of e.g. blocking node or sensor will provide useful information to the controller.

[0015] Advantageously, said at least one controlled module can be configured to store information regarding said command initiator, i.e. regarding a specific type of node from which the signal originates.

[0016] Preferably, said at least one controlled module may be configured to send information regarding said command initiator in response to a received control signal whose execution is negated due to the previous control signal to which the command initiator referred.

[0017] In this way, it is obtained that the user can be informed of the reason for the failure to execute the control signal which was transmitted e.g. from the remote control. [0018] According to a further preferred embodiment, said node from which the negated control signal was sent may include means for indicating information about the command initiator, e.g. a visual signal corresponding to the type of the node.

In this way, the user can be informed in a simple and understandable way about the cause, e.g. by means of an icon or symbol, which appears e.g. on the display of the remote control, e.g. a pictogram corresponding to a wind sensor, which can further flash or another way to attract the user's attention.

[0020] Preferably, said at least one controlled module may be configured to store information regarding a command initiator received with a control signal and said at least one controlled module may further be configured to reject a control signal from a node having a corresponding command initiator.

[0021] In this way, it becomes possible that the controlled module will selectively reject some control signals instead of rejecting all control signals when operation is blocked. It will be possible, for example, to reject signals coming from a wind sensor, while signals coming from a sun sensor may lead to an action.

[0022] Preferably, said at least one controlled module may comprise means for storing and handling command initiator information.

[0023] Preferably, said means for storing and handling command initiator information may be means in the form of a time relay function, whereby it is obtained that blocking can be time-dependent.

[0024] According to a further embodiment, said system may be configured to delete or temporarily neutralize stored information regarding a command initiator in response to the reception of a signal containing the determined command initiator. [0025] In this way, certain entries that have been entered into this controlled module can be canceled.

[0026] For example, referring to the example given earlier, in which the system can be programmed to prevent the blinds from being raised when the sun is shining, e.g. to protect furniture, rugs etc. from sunlight, this situation can be canceled by the user if it is desirable. According to this embodiment, the user may send a signal e.g. to an awning or roller blind, informing the system that the signal received from the sun sensor must be blocked, thus enabling the user to raise the blinds or roll up the awning, if desired, even if the sun is shining. For example, the remote control may be equipped, e.g. with the "sun sensor blocking" function key or the like.

[0027] Preferably, said fixed command initiator may be an emergency command initiator.

[0028] In this way, it obtains that the blocking entry or blocking entries to the controlled node can be neutralized or permanently, in which case they will be deleted, or for a specified period in specific emergency situations, where after activation in the command the signal will be it could be done, such as opening a window as an escape route.

[0029] It should be noted that a control signal including an emergency command initiator preferably cannot be blocked by other control signals. In addition, it should be noted that in general a control signal including an emergency command initiator may advantageously be transmitted from any module or node.

[0030] The invention also relates to a method of operating a device, such as e.g. actuator for doors, gates, windows, shutters, blinds, curtains, awnings or light source, which device is associated with the controlled module, said controlled module is intended to receive control signals from multiple nodes in the control system and to operate said device in accordance with with said control signals according to which the initiator of the command is assigned to the control signal, said command initiator contains identification data of the determined type of node from which the signal originates.

In this way, it is obtained that if a control signal sent from another node in the system, e.g. from a remote control, to the controlled device is negated or rejected, e.g. the control signal does not lead to actuation because the previous signal control has blocked the controlled module, the controlled module may inform the other node of the cause.

[0032] Preferably, said at least one controlled module may be configured to store information regarding said command initiator, i.e.

regarding the specific type of node from which the signal originates.

[0033] Preferably, said at least one controlled module may send information regarding said command initiator in response to a received control signal whose execution is negated due to the previous control signal to which the command initiator referred.

[0034] In this way, it is obtained that the user can be informed of the reason for the failure to execute the control signal which was sent e.g. from the remote control. [0035] According to a further preferred embodiment, information regarding the command initiator, e.g. a visual signal corresponding to the type of the node, may be indicated by the node from which the negated control signal was sent.

[0036] In this way, the user can be informed in a simple and understandable way about the cause, e.g. by means of an icon or symbol appearing e.g. on the remote control display, e.g. a wind sensor pictogram, which can also flash or otherwise attract user's attention.

[0037] Advantageously, information regarding the command initiator received with the control signal may be stored in said at least one controlled module, and said at least one controlled module may further reject the control signal originating from the node having the corresponding command initiator.

[0038] In this way, it becomes possible that the controlled module will selectively reject some control signals instead of rejecting all control signals when operation is blocked. It will be possible, for example, to reject signals coming from a wind sensor, while signals coming from a sun sensor may lead to an action. [0039] Preferably, said at least one controlled module may have means for storing and handling command initiator information.

[0040] According to a further preferred embodiment, said stored command initiator information may be rejected after a certain period has elapsed, whereby it is obtained that blocking can be time-dependent. According to a further embodiment, the stored information regarding the command initiator may be deleted or temporarily neutralized in response to receiving a signal containing the determined command initiator.

[0041] In this way, certain entries that have been entered into this controlled module can be canceled.

[0042] For example, referring to the example given earlier, in which the system can be programmed to prevent the blinds from being raised when the sun is shining, e.g.

in order to protect furniture, carpet etc. from sunlight, this situation can be canceled by the user if desired. According to this embodiment, the user can send a signal e.g. to an awning or roller blind, informing the system that the signal received from the sun sensor must be blocked, thus enabling the user to raise the blinds or roll up the awning, if desired, even if the sun is shining. For example, the remote control can be equipped e.g. in the function key "blocking the sun sensor" or similar.

[0043] Preferably, said fixed command initiator may be an emergency command initiator.

[0044] In this way, it is obtained that the immobilization entry or immobilization entries to the controlled node can be neutralized or permanently, in which case they will be deleted, or for a specified period in special emergency situations, where after activation in the command the signal can be made, such as opening a window as an escape route.

Figures [0045] The invention will be explained in detail hereinafter with reference to the figures in which:

Fig. 1 schematically shows an example of the control system according to the invention, Figs. 2a-b show examples of a priority and command management table we7 according to one embodiment of the invention, Fig. 3 shows examples of a priority and command level management table according to a further aspect of the invention.

Detailed description [0046] An example of a control system according to one embodiment of the invention, e.g. a home automation system or parts thereof, is shown in Figure 1. In this example, the building, house or the like 1 is schematically shown showing only part of the house in detail or room in which the window is located 2. Window 2 may be equipped with a window actuator, actuator or window opening device 4, which may comprise a drive mechanism generally designated 6 and a controlled node 5, e.g. a node comprising a radio receiver and a control device. In addition, the window 2 can be equipped with an awning 3 that can be rolled up as shown, moved by means of the actuator 8. This actuator 8 may include a drive motor generally designated 9 and a controlled node 10, e.g. a node comprising a radio receiver and a control device.

[0047] The control system may also have one or more sensors, such as e.g. a wind speed sensor 12, a sun sensor 16 and a rain sensor 19. As shown, such sensors may include a sensor portion, e.g. anemometer 13 and a photometer, respectively 17 and the transmitting part, e.g. 14 and 18, respectively, which transmitting parts may e.g. be RF radio transmitters or may operate on a wired connection basis. The rain sensor 19 may be a built-in window 2, but will also include a sensor part and a transmitting part (not shown). Further sensors or controllers can be introduced, also inside the room, e.g. in the form of a temperature sensor, etc.

Furthermore, as shown, the control system may comprise one or more remote controls 20 and 22, for operating the controlled devices, e.g. an opening device 4 for a window and an awning 3. These remote controls may be similar, e.g. they may have similar properties, but may also differ, e.g. they may have different properties, e.g., in terms of priority. One of them, e.g. remote control 20, can e.g. be the main remote control, while the other, e.g. remote control 22, maybe a slave remote control.

[0049] All of these remote controls 20 and 22 and sensors 12, 16 and 19 can send control signals to the controlled modules, e.g. to the controlled nodes 5 and 10, associated with window 2 and awning 3 respectively. It should be understood that the terms "control signals" in the present context include any signal sent from a node such as a sensor or remote control to a controlled module, including signals representing measured values, etc., and that the controlled module may respond or not respond when receiving such a signal , e.g. according to some pre-defined or established rules.

[0050] For example, the signal sent from the wind sensor 12 to the controlled module 10 associated with the awning 3 may block the awning, e.g. keep the awning 3 in the rolled up position when the wind speed exceeds a predetermined level. The command or control signal sent from the wind sensor 12 contains information regarding the type of device that sent the signal, e.g. "wind sensor", and this information is stored in the controlled module 10 associated with the awning 3. If the control signal is sent, e.g. from the remote control 20, recommending the unfolding of the awning 3, the controlled module 10 will determine whether the command is blocked by the wind sensor and a response signal, e.g. confirmation, is sent back to the remote control 20 with information that the operation cannot be performed, and the reason is the wind sensor.

[0051] It is understood that if the system shown in Fig. 1 includes two or more wind sensors located at different locations, the controlled module 10 at the awning would have to remember information that the blocking control signal was sent from the wind sensor, i.e. node type control system, not necessarily from a specific wind sensor. The information sent to remote control 20 would also indicate in this example that operation was not feasible due to the wind sensor. Information about a specific wind sensor would not provide the user with any useful information.

[0052] It should further be understood that when a control signal containing command initiator information is sent to a controlled node, which signal causes e.g. the controlled node to perform an action and then lock the device, a time relay function may also be involved. For example, if the signal from the rain sensor 19 causes the window actuator 4 to close and lock, e.g. controlled by node 5, which also remembers the information that the rain sensor has triggered this action, then a time relay can be set to hold the block for e.g. 10 minutes after the signal from the rain sensor to node 5 has arrived.

[0053] In addition, the command initiator information, i.e. information regarding the type of device from which the control signal was sent, can also be used to decide whether the command should be carried out or not.

For example, when a control signal from e.g. a rain sensor 19 is received at the controlled node 10, after which e.g. the awning is locked in the rolled position, it can be remembered that this lock is associated with a certain type of node, e.g. a sensor or by remote control. Furthermore, as explained above, it may depend on the time relay. It should also be understood that more than one signal carrying such information may be sent to the controlled node, each of which calls a setting as explained previously.

Thus, the reception of such a signal at the node may lead to an entry e.g. in Table 32, as shown in Fig. 2a, in which each line 36, 37, 38 corresponds to an incoming signal through which operation has been blocked, as given in column 34. For all entries in the table, the node will have the initiator record from which each signal was sent, e.g. "source initiator" as given in column 39, e.g. sensor a, sensor b and wind sensor. It should be understood that other types of controllers may also be involved. In addition, a time relay function may be active for each of them, e.g. indicating how long the interlock is active.

[0056] Furthermore, as shown in Fig. 2b, which corresponds to Fig. 2a, but in which column 33 has been added, the table 32 may also contain an indication of the type of device from which the control signal cannot be made. For example, the "X sensor" may be a sun sensor, the "Y sensor" may be a rain sensor, and the "remote control" may be the main remote control. It should be understood that other types of controllers may also be involved.

[0057] Thus, in the example shown in Fig. 2b, if the control signal from the remote control is received at the node, e.g. to unroll the awning, this control signal will be blocked due to input 38 and the signal will be sent from back to the remote control informing the user that execution is blocked due to a wind sensor, e.g. due to wind conditions.

[0058] In addition, the node may also have a command initiator record for other control signals that do not lead to blocking, but only apply e.g. to device startup.

As shown in Figure 1, such a table 32 can be allocated to each of the controlled nodes, e.g. 5 and 10 in the system.

[0060] When a control signal is received at such a node, the initiator of the command is identified. If the control signal is of a type leading to a blocked start, the command initiator is remembered as explained at the beginning. If the control signal initiates blocking the activation of certain types of devices, i.e. certain types of command initiators, an entry is made in column 33 in table 32 and the time relay function 35 is set. In addition, it should be noted that if the control signal requires a certain function, e.g., activation, it is evaluated from the point of view of the contents of the table, e.g. to check whether the function is prohibited by the contents of the table. If execution of the function is excluded, a response signal to confirm this may be sent e.g. to the respective node as explained previously.

[0061] Each time the controlled node receives the control signal, the table 32 is updated, e.g. if the time relay function has expired, the entry is deleted from the table before the control signal is evaluated taking into account the contents of the table.

[0062] It should be understood that for practical reasons the table will be limited in terms of the number of entries. If a control signal is received containing the content requiring an entry when the table is full, different solutions are possible. The simplest solution is to reject the control signal. However, there are other ways to handle this situation. For example, you can decide that the entry with the smallest remaining time relay setting value, etc. can be excluded.

[0063] According to a further embodiment, the node lock, e.g. a node-associated device, can be undone or neutralized. If we consider an example in which the system can be set so as to prevent, for example, raising blinds when the sun is shining, e.g. to protect furniture, rugs, etc. from sunlight, this situation can be canceled by the user if desired. According to this embodiment, the user can send a signal via the main remote control e.g. to an awning or roller blind, informing the system that the signal received from the sun sensor must be blocked, thus enabling the user to raise the blinds or awning if desired, even though the sun is shining. For example, the remote control may be equipped e.g. with the "sun sensor lock" function key or the like. Such cancellation may be time-dependent, e.g., causing entry 38 in table 32 of Fig. 2b will be canceled for a specified period of time, after which it will become active again if the original time relay function has not expired (n3 seconds). Furthermore, the cancellation can be permanent, which means that the entry, e.g. entry 38 in table 32 in Fig. 2b, is deleted from the table.

[0064] Other examples of such control signals containing information having the effect of being able to block the operation entry already applied can be canceled, e.g. permanently deleted or neutralized for a set period.

[0065] For example, a "failover" initiator can be assigned to a control signal, thereby causing that if such a signal is sent to a node that is blocked, the node will identify the initiator as an emergency initiator. In this case, the blocking entry or blocking entries in the node will be neutralized, either permanently, in which case they will be deleted, or for a set period of time, and the action specified in the control signal can be executed. As stated, such activation may be associated with safety aspects, e.g. in the event of a fire, when it is important to be able to open, e.g. a window, despite heavy rain falling, which will normally cause data entry from the rain sensor, preventing the device from starting opening window. Thus, the remote control can be equipped with a special emergency key, which when pressed will cancel any entries blocking operation in the node (s).

[0066] Preferably, the control signal including the emergency type command initiator cannot be blocked by any other control signals, e.g. by other entries already present in the table or by control signals received later. It should further be noted that in general a control signal including an emergency command initiator may preferably be sent from any other device or node.

[0067] It should be understood that the command initiator system according to the invention can be combined with other operating systems and methods used in control systems, eg in home automation systems. As an example of the above and according to a further aspect of the invention, priority and level management can be included, which will be explained in more detail below.

[0068] To manage priorities, e.g. in a system as shown in Fig. 1, signals from sensors of controlled nodes can be assigned priority information at a number of levels, and when these signals are received at controlled nodes, they can be recorded and stored in the management table, and an estimate is made based on the information stored in the table. Based on this estimate, the device associated with the controlled module is supported, e.g. started, turned off, stopped, started in the opposite direction, etc.

[0069] Such a management table can be combined with the command initiators system, as described earlier, in the form of a table that can take the place of table 32 of Figure 1, which is associated with each of the controlled nodes, e.g. nodes 5 and 10 in this example.

[0070] Details of such a table will be further explained with reference to Fig. 3, which shows an example of such a management table 40 for a controlled node or device in a control system.

[0071] According to usual practice, priority levels can be ranked in descending order, e.g., in the following order: human safety, protection of property or the environment, manual operation by the user, automatic comfort control. The number of levels can be set, e.g., to eight levels, as indicated by reference number 41 in Fig. 3, ranked from the highest level 0 to the lowest level 7, and of these levels, the lowest four can be allocated to the levels of automatic comfort control, levels 3 and 2 can be used for manual control by the user, while levels 1 and 0 are therefore intended for protection property or the environment and human safety.

[0072] When a signal is received from a node, the content of this signal regarding priority or priorities at certain command levels leads to the entry being stored in the management table as shown in Fig. 3. Here, each line corresponds to the signal sent from the node to the specific controlled node, and understand that each node controlled contains such a management table. For each command, the table can contain priority, e.g. "Allow" or "block" which will lead to the appropriate setting in the table. If the received signal does not contain the information "allow" or "block" for the priority level, the signal will not affect the estimation at this level. In addition, the control signal may also specify the period for which the command must be stored in the table, e.g. 15 minutes from the moment of receiving the command. Thus, the table will also contain column 43 informing about the operation of the time relay, e.g. giving the total period for the given command or the remaining time for that command. It is obvious that the controlled nodes contain means in the form of a time relay for operating the table 40. [0073] When the table is prepared and when a new command containing priority information is received, an entry is made in the table, the table is evaluated and the result of the estimation is remembered in estimation line 45. Various rules and algorithms can be used for estimation. For example, as shown in Fig. 3, it is stated for each level that the command level is locked when it has at least one "lock" priority. Another way to estimate the array could be e.g. a majority-based estimate.

[0074] An incoming new control signal that contains a command at a level that is blocked cannot be executed, while a command at a level that is not blocked can be executed.

[0075] As said, an estimate is made each time a signal containing priority information is received, but when a command is removed from the table because its period has expired, the estimate can also be performed again. It should also be understood that the table can be reassessed at regular intervals.

[0076] If a command is received that does not contain priority information leading to an entry, but requires, for example, only execution for execution, such a command is executed if the corresponding level has been allowed.

[0077] As shown in Fig. 3, table 40 also includes a column 46 giving a command initiator, e.g. as stated that the first entry relates to the subordinate remote control, the second entry refers to the sun sensor, the third entry relates to the rain sensor, etc.

In this way and as explained earlier, the information can be sent back to the control node in the event of the command being rejected, which information can be used to inform the user of the reason for the failure to perform the requested activation.

[0078] In this way, information about the initiator of the command may also be used in conjunction with the level and priority management system.

[0079] It will be apparent to a person skilled in the art that the method and system of the invention can be used in a wide range of applications, e.g. in home automation systems, and that such systems may include a number of controlled devices such as windows, doors, blinds, blinds, light sources, etc., and that such systems may similarly contain multiple nodes for providing control signals, e.g., measurement signals, sensor signals, etc. Thus, it should be understood that the example shown in Fig. 1 only represents a simple embodiment.

[0080] It should be understood that the invention is not limited to the specific examples described earlier and shown in the drawings, but can be modified in many ways and used in a variety of applications within the scope of the invention as defined in the claims.