Communicating with and controlling load control system

Through communication between network devices and load control systems, intelligent control of loads such as lighting and HVAC is achieved, which solves the problem of difficult to achieve automated management in the existing technology, and improves the efficiency and user experience of energy management.

CN118915552APending Publication Date: 2024-11-08LUTRON TECHNOLOGY COMPANY LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411037171.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2019-01-07
Filing Date
2019-09-04
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

The existing load control system is difficult to achieve intelligent and automated control of electrical loads such as lighting and HVAC in the user environment, and lacks unified communication and management methods.

Method used

Through communication between network devices and load control systems, display screens, processors and memory devices are used to realize the use of graphical user interfaces and software instructions, allowing users to remotely control and monitor lighting, HVAC and other loads, and adopt system controllers and control source devices. Wireless communication with the control target device to realize automatic control of electrical load.

Benefits of technology

It realizes intelligent control of loads such as lighting and HVAC in user environments, improves the efficiency and user experience of energy management, and provides remote monitoring and management capabilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118915552A_ABST
    Figure CN118915552A_ABST
Patent Text Reader

Abstract

One aspect of the disclosure relates to communicating with and controlling a load control system. Systems and methods are disclosed for communicating with a load control system of a respective user environment via a communication network; receiving information on the load control system via the communication network; displaying a graphical user interface based on the received information; and controlling and configuring the load control system via a graphical user interface by communicating messages to the load control system via the communication network.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the invention patent application "Communicating with and controlling a load control system" with an application date of September 4, 2019 and application number "201980073146.X".

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 726,755, filed September 4, 2018, and U.S. Provisional Patent Application No. 62 / 789,412, filed January 7, 2019, the entire contents of each of which are incorporated herein by reference. Background Art

[0004] A user environment (e.g., a residence, an office building, or a hotel) can be configured to include various types of load control systems. For example, a lighting control system can be used to control lighting loads in the user environment. An electric window treatment control system can be used to control the natural light provided to the user environment. A heating, ventilation, and air conditioning (HVAC) system can be used to control the temperature in the user environment. Summary of the invention

[0005] It may be desirable to communicate with and control the load control system via a network device.

[0006] As an example, an apparatus may include a display screen, a communication circuit, and at least one processor, and may also include at least one tangible memory device communicatively coupled to the at least one processor. The at least one tangible memory device may have software instructions stored thereon, which, when executed by the at least one processor, may instruct the at least one processor to receive information communicated by a controller from a communication network via the communication circuit. The controller may be configured to communicate with a lighting control device. The lighting control device may be configured to control a lighting load. The lighting load may include a plurality of light emitting diodes (LEDs) including a red light emitting diode, a green light emitting diode, and a blue light emitting diode, and may be configured to generate any of a plurality of different colors through the plurality of LEDs. The information may include an indication of the color that the lighting load is currently configured to generate. The software instructions, when executed by at least one processor, may further instruct the at least one processor to display a graphical user interface on a display screen, the graphical user interface comprising: an on-off actuator for turning the lighting load on and off, a dimming actuator for changing the intensity of the lighting load, a warm-cool actuator for configuring the lighting load to generate a color on a blackbody curve, and a full-color actuator for configuring the lighting load to generate a color within a color gamut formed by a plurality of LEDs constituting the lighting load. The software instructions, when executed by at least one processor, may further instruct the at least one processor to display an indicator in the graphical user interface together with the on-off actuator indicating the color that the lighting load is configured to currently generate.

[0007] The above advantages and features are representative embodiments only. They are not to be considered as limiting. According to the accompanying drawings and claims, the additional features and advantages of each embodiment will become apparent in the detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 is a system diagram illustrating an exemplary load control system including a control device.

[0009] Figure 2 is a system diagram illustrating a system for communicating with and controlling a load control system using a message passing based interface.

[0010] Figure 3 is a system diagram illustrating a system for communicating with and controlling a load control system using a messaging-based interface and / or an HTTP-based interface.

[0011] Figure 4 is a system diagram illustrating another system for communicating with and controlling a load control system using a messaging-based interface and / or an HTTP-based interface.

[0012] Figure 5is a system diagram illustrating another system for communicating with and controlling a load control system using a messaging-based interface and / or an HTTP-based interface.

[0013] Figures 6A to 6Z and Figure 6AA Exemplary graphical user interfaces of applications that may allow a user to determine information about and control a load control system and / or control device are shown.

[0014] FIG. 7A to FIG. 7B Another exemplary graphical user interface of an application that may allow a user to determine information about and control a load control system and / or control device is shown.

[0015] FIG. 8A to FIG. 8D Yet another exemplary graphical user interface of an application that may allow a user to determine information about and control a load control system and / or control device is shown.

[0016] FIG. 9A to FIG. 9G Yet another exemplary graphical user interface of an application that may allow a user to determine information about and control a load control system and / or control device is shown.

[0017] FIG. 10A to FIG. 10C Another exemplary graphical user interface of an application that may allow a user to determine information about and control a load control system and / or control device is shown.

[0018] FIG. 11A to FIG. 11Q Another exemplary graphical user interface of an application that may allow a user to determine information about and control a load control system and / or control device is shown.

[0019] Fig.12 is a block diagram of an exemplary network device.

[0020] Fig.13 is a block diagram of an exemplary system controller.

[0021] Fig.14 is a block diagram of an exemplary control target device.

[0022] Fig.15 is a block diagram of an exemplary control source device. DETAILED DESCRIPTION

[0023] Figure 1A high-level diagram of an exemplary load control system 100 is shown. The load control system 100 may include a system controller 150 and load control devices for controlling (e.g., directly and / or indirectly) one or more electrical loads in a user environment 102 (also referred to herein as a load control environment). The exemplary user environment / load control environment 102 may include one or more rooms of a house, one or more floors of a building, one or more rooms of a hotel, etc. As an example, the load control system 100 may implement automatic control of lighting systems, window shades, and heating, ventilation, and air conditioning (HVAC) systems and other electrical loads in the user environment.

[0024] The load control device of the load control system 100 may include a system controller 150, a control source device (e.g., elements 108, 110, 120, and 122 discussed below), and a control target device (e.g., elements 112, 113, 116, 124, and 126 discussed below) (the control source device and the control target device may be individually and / or collectively referred to as a load control device and / or a control device herein). The system controller 150, the control source device, and the control target device may be configured to communicate (transmit and / or receive) messages, such as digital messages (although other types of messages may also be communicated), between each other using wireless signals 154 (e.g., radio frequency (RF) signals) (although wired communications may also be used). "Digital" messages are used herein for discussion purposes only.

[0025] The control source device may include, for example, an input device configured to detect conditions within the user environment 102 (e.g., user input via a switch, occupancy / vacancy conditions, changes in measured light intensity, and / or other input information), and transmit a digital message to a control target device in response to the detected condition, the control target device being configured to control an electrical load in response to the instruction or command received in the digital message. The control target device may include, for example, a load control device configured to receive a digital message from the control source device and / or the system controller 150 and control a corresponding electrical load in response to the received digital message. A single control device of the load control system 100 may operate as both a control source device and a control target device.

[0026] According to one example, the system controller 150 may be configured to receive digital messages transmitted by a control source device, interpret these messages based on the configuration of the load control system, and then transmit the digital messages to the control target device for the control target device to then use to control the corresponding electrical load. In other words, the control source device and the control target device may communicate via the system controller 150. According to another and / or additional example, the control source device may communicate directly with the control target device without the assistance of the system controller 150. The system controller may still monitor such communications. According to another and / or additional example, the system controller 150 may initiate a digital message and then communicate digital messages with the control source device and / or the control target device. Such communications performed by the system controller 150 may include programming / configuration data (e.g., settings) for the control device, such as configuring a scene button on a light switch. Communications from the system controller 150 may also include, for example, messages directed to the control target device and containing instructions or commands for the control target device to control the corresponding electrical load in response to the received message. For example, the system controller 150 may convey messages to change light levels, change shade levels, change HVAC settings, etc. These are examples, and others are possible.

[0027] The communication between the system controller 150, the control source device, and the control target device may be performed via a wired and / or wireless communication network as described above. An example of a wireless communication network may be a wireless LAN, in which the system controller, the control source device, and the control target device may communicate via, for example, a router, which is located locally in the user environment 102. For example, such a network may be a standard Wi-Fi network. Another example of a wireless communication network may be a point-to-point communication network for direct communication, in which the system controller, the control source device, and the control target device use, for example, Bluetooth, Wi-Fi Direct, a proprietary communication channel (such as CLEAR CONNECT), or a wireless communication channel such as WI-FI. TM ) etc. Other network configurations may be used, such as a system controller acting as an access point and providing one or more wireless / wired-based networks through which the system controller, control source devices, and control target devices may communicate.

[0028] In order for the control target device to respond to the message from the control source device, the control source device may first need to be associated with the control target device. As an example of an association procedure, the control source device may be associated with the control target device by actuating a button on the control source device and / or the control target device by the user 142. The actuation of the button on the control source device and / or the control target device may place the control source device and / or the control target device in an association mode to associate with each other. In the association mode, the control source device may transmit one or more association messages to the control target device (directly or through a system controller). The association message from the control source device may include a unique identifier of the control source device. The control target device may locally store the unique identifier of the control source so that the control target device may be able to recognize a digital message (e.g., a subsequent digital message) from the control source device, which may include a load control instruction or command. The control target device may be configured to respond to the digital message by controlling the corresponding electrical load according to the load control instruction received in the digital message from the associated control source device. This is only one example of how control devices can communicate and associate with each other, and other examples are also possible. According to another example, the system controller 150 may receive a configuration instruction from a user, the configuration instruction specifying which control source devices should control which control target devices. Thereafter, the system controller may communicate this configuration information to the control source device and / or the control target device.

[0029] As one example of a control target device, the load control system 100 may include one or more lighting control devices, such as lighting control devices 112 and 113. The lighting control device 112 may be a dimmer, an electronic switch, a ballast, a light emitting diode (LED) driver, etc. The lighting control device 112 may be configured to directly control the amount of power provided to one or more lighting loads, such as the lighting load 114. The lighting control device 112 may be configured to wirelessly receive a digital message (e.g., a message originating from a control source device and / or the system controller 150) via the signal 154, and control the lighting load 114 in response to the received digital message. It will be appreciated that the lighting control device 112 and the lighting load 114 may be integral and therefore part of the same fixture, or may be separate.

[0030] The lighting control device 113 can be a wall-mounted dimmer, a wall-mounted switch, or other keypad device for controlling one or more lighting loads (such as the lighting load 115). The lighting control device 113 can be suitable for installation in a standard electrical wall box. The lighting control device 113 can include one or more buttons for controlling the lighting load 115. The lighting control device 113 can include a toggle actuator. Actuation (e.g., continuous actuation) of the toggle actuator can toggle (e.g., turn off and on) the lighting load 115. The lighting control device 113 can include an intensity adjustment actuator (e.g., a rocker switch or an intensity adjustment button). Actuation of the upper or lower portion of the intensity adjustment actuator can increase or decrease the amount of power delivered to the lighting load 115, respectively, and thus increase the intensity of the receptive lighting load from a minimum intensity (e.g., about 1%) to a maximum intensity (e.g., about 100%) or decrease from the maximum intensity to the minimum intensity. Lighting control 113 may include a plurality (two or more) of visual indicators, such as light emitting diodes (LEDs), which may be arranged in a linear array and may illuminate to provide feedback of the intensity of lighting load 115 .

[0031] Lighting control device 113 may be configured to wirelessly receive digital messages (eg, messages originating from a control source device and / or system controller 150) via wireless signals 154. Lighting control device 113 may be configured to control lighting load 115 in response to the received digital messages.

[0032] The load control system 100 may include one or more other control target devices, such as electric window treatments 116 for directly controlling covering material 118 (e.g., via an electric motor); ceiling fans; tabletop or plug-in load control devices 126 for directly controlling floor lamps 128, table lamps, and / or other electrical loads that may be plugged into plug-in load control devices 126; and / or temperature control devices 124 (e.g., thermostats) for directly controlling an HVAC system (not shown). The load control system 100 may also or alternatively include an audio control device (e.g., a speaker system) and / or a video control device (e.g., a device capable of streaming video content). Furthermore, these devices may be configured to wirelessly receive digital messages (e.g., messages originating from a control source device and / or system controller 150) via wireless signals 154. These devices may be configured to control corresponding electrical loads in response to the received digital messages.

[0033] In addition to being configured to wirelessly receive digital messages via wireless signals and control corresponding electrical loads in response to received digital messages, control target devices may also be configured to wirelessly transmit digital messages via wireless signals (e.g., to the system controller 150 and / or one or more associated control devices). Control target devices may communicate such messages to acknowledge receipt of messages and actions taken, report conditions (e.g., light level), etc. Furthermore, control target devices may also or alternatively communicate via wired communications.

[0034] With respect to control source devices, the load control system 100 may include one or more remote control devices 122, one or more occupancy sensors 110, one or more daylight sensors 108, and / or one or more window sensors 120. The control source device may wirelessly send or communicate a digital message to an associated control target device via a wireless signal (such as signal 154) for controlling an electrical load. The remote control device 122 may send a digital message for controlling one or more control target devices after actuating one or more buttons on the remote control device 122. For example, one or more buttons may correspond to a preset scene for controlling a lighting load 115. The occupancy sensor 110 may send a digital message to a control target device in response to occupancy and / or vacancy conditions (e.g., movement or lack of movement) sensed within its observable area. The daylight sensor 108 may send a digital message to a control target device in response to detecting a certain amount of light within its observable area. The window sensor 120 may send a digital message to a control target device in response to a measured light level received from outside the user environment 102. For example, the window sensor 120 can detect when sunlight is directly shining into the window sensor 120, when it is reflected onto the window sensor 120, and / or when it is blocked by external devices such as clouds or buildings. The window sensor 120 can send a digital message indicating the measured light level. The load control system 100 can include one or more other control source devices. Again, it will be appreciated that the control source devices can also or instead communicate via wired communications.

[0035] Turning again to the system controller 150, it can facilitate the communication of messages from the control source device to the associated control target device and / or monitor such messages as shown above, so as to know when the control source device detects an event and when the control target device is changing the condition / state of the electrical load. The system controller can communicate programming / configuration information to the control device. The system controller can also be a control message source for the control target device, for example, instructing the device to control the corresponding electrical load. As an example of a control message source, the system controller can run one or more clock operations that automatically communicate messages to the control target device based on the configured schedule (e.g., communicate a command to the lighting control device 113 to adjust the lamp 115, communicate a command to the electric window treatment 116 to directly control the covering material 118, etc.). For descriptive purposes only, blackout curtains will be used herein to describe the functions and features related to electric window treatments. Nevertheless, it will be recognized that the features and functions described herein are applicable to other types of window coverings, such as drapes, curtains, blinds, etc. Other examples are also possible.

[0036] According to another aspect of the load control system 100, the system controller 150 can be configured to communicate, for example, with one or more network devices 144 being used by the user 142. The network device 144 can include a personal computer (PC), a laptop computer, a tablet computer, a smart phone, or an equivalent device. The system controller 150 and the network device 144 can communicate via a wired and / or wireless communication network. The communication network can be the same network used by the system controller and the control device, or it can be a different network (e.g., a wireless communication network using a wireless signal 152). As an example, the system controller 150 and the network device 144 can communicate via a wireless LAN (e.g., located locally in the user environment 102). For example, such a network can be a standard Wi-Fi network provided by a router local to the user environment 102. As another example, the system controller 150 and the network device 144 can communicate directly with each other using, for example, Bluetooth, Wi-Fi Direct, etc. Other examples are also possible, such as the system controller acting as an access point and providing one or more wireless / wired-based networks, through which the system controller and the network device can communicate.

[0037] In general, the system controller 150 may be configured to allow a user 142 of a network device 144 to determine, for example, the configuration of the user environment 102 and the load control system 100, such as the rooms in the environment, which control devices are in which rooms (e.g., the location of the control devices within the user environment, such as which rooms); determine the status and / or configuration of the control devices (e.g., light levels, HVAC levels, shade levels); configure the system controller (e.g., change a clock schedule); issue commands to the system controller to control and / or configure the control devices (e.g., change light levels, change HVAC levels, change shade levels, change presets, etc.), etc. Other examples are possible.

[0038] Figure 1 The load control system 100 may be configured such that the system controller 150 is only able to communicate with the network device 144 when the network device 144 is local to the system controller 150, in other words, to communicate directly with the network device 144 in a point-to-point manner or through a local network specific to the user environment 102 (such as a network provided by a router local to the user environment). It may be advantageous to allow users of the network device 144 to communicate with the system controller 150 and control the load control system 100 from a remote location (such as via the Internet or other public or private network). Similarly, it may be advantageous to allow third-party integrators to communicate with the system controller 150 in order to provide enhanced services to users of the user environment 102. For example, a third-party integrator may provide other systems within the user environment 102. It may be beneficial to integrate such systems with the load control system 100.

[0039] Reference now Figure 2 , an exemplary system 200 is shown. The system 200 may include one or more user environments, as represented by user environments 202a and 202b. More specifically, the system 200 may be configured to support a variety of user environments, of which only two user environments 202a and 202b are shown to assist in describing the system 200. Each user environment may be substantially identical, each including a corresponding load control system 210a and 210b, the load control systems 210a and 210b including corresponding system controllers 250a and 250b and corresponding control devices 220a and 220b (e.g., control source devices and / or control target devices). In general, the system controllers 250a and 250b and the control devices 202a and 202b of the load control systems 210a and 210b may be functionally similar to those described above. Figure 1The system controller 150 and control devices discussed are operated. The difference between each user environment 202a and 202b of the system 200 can be that the user environment can be owned by different entities. For example, each user environment can be a residential house owned by different users / homeowners, can be a business, etc., or can be a combination of them. For descriptive purposes only, user environments 202a and 202b can be referred to as residential houses owned / rented by homeowners in this article. Therefore, each user environment can include different control devices and different configurations of these control devices and system controllers. In this way, for example, system 200 can include many different houses. Compared with load control system 100, system 200 can include a system for users and / or third parties to interface with load control systems 210a / 210b from locations far away from the corresponding user environments 202a / 202b, such as through the Internet or other private or public networks.

[0040] As shown, each user environment 202a and 202b of system 200 may include a respective system controller 250a and 250b (although a user environment may include more than one system controller) and a control device, collectively referred to as elements 220a and 220b (again, system controller 250a and control device 220a may constitute load control system 210a, and system controller 250b and control device 220b may constitute load control system 210b). System 200 may also include one or more message brokers 270 and one or more network devices 280a and 280b. Network devices 280a and 280b may represent computing devices being used by respective users of respective user environments 202a and 202b. For example, network device 280a may be a device being used by a homeowner of user environment 202a (e.g., a phone, PC, laptop, tablet computer, smartphone, or equivalent device), and network device 280b may be a device being used by a homeowner of user environment 202b (e.g., a cell phone, etc.). As another and / or additional example, network devices 280a and 280b can be third-party integrators that provide services to the corresponding users / homeowners of user environments 202a and 202b. Here, for example, network devices 280a and 280b can each be one or more computing servers. Furthermore, system 200 can include many network devices 280a and 280b, wherein only two network devices are shown for description purposes. According to system 200, network devices 280a and 280b can be far away from the user environment (e.g., not located in the user environment). Nevertheless, network devices 280a and 280b can also be located in the user environment locally (e.g., located in the user environment), and use message broker 270 to communicate with system controller 250a and / or 250b, as described below.

[0041] The system 200 may also include networks 282 and 283, which may include private and / or public networks, such as the Internet. The networks 282 and 283 may be at least partially the same network. In general, the system controllers 250a and 250b may be configured to communicate with the message broker 270 via the network 282, and each network device 280a and 280b may be configured to communicate with the message broker 270 via the network 283. By using the message broker 270 and other mechanisms described herein, the network device 280a may, for example, communicate with the system controller 250a of the user environment 202a and interact with the control device 220a of the environment. As one example of system 200, a user may use network device 280a to communicate with system controller 250a, and through these communications may determine, for example, the configuration of load control system 210a / user environment 202a (e.g., such as the rooms in the environment and the location of control devices in the user environment (e.g., which rooms)), determine the status and / or configuration of control device 220a (e.g., light level, HVAC level, shade level), configure system controller 250a (e.g., change a clock schedule), issue commands to system controller 250a to control and / or configure control device 220a (e.g., change light level, change HVAC level, change shade level, change preset, etc.). These are merely examples. As another example, network device 280a operated by a third-party integrator may communicate with system controller 250a to determine the status of load control system 210a and control load control system 210a (as described herein), and also use this functionality to integrate features of load control system 210a with features of another system in user environment 202a that the third-party integrator may control. As an example, the third-party integrator may be a home security provider and in response to detecting a problem in the user environment 202a through a system (e.g., an alarm system) provided by the third-party integrator, instruct the system controller 250a to actuate the lights in the user environment. Other examples are also possible. For example, a third-party integrator may provide one or more voice / speaker-based devices located in the user environment 202a. The user may interface with such devices auditorily (e.g., through voice commands), which in turn may communicate with a network device 280a (e.g., a computing server of a third-party integrator). The network device 280a may in turn communicate with the system controller 250a to control the load control system 210a based on how the user interfaces with the voice / speaker-based device. Alternatively, the network device 280a may communicate with the system controller 250a to determine the status of the load control system 210a, and may communicate with the voice / speaker-based device to audibly report the status to the user. Again, this is an example. In a similar manner, the user and the third-party integrator may communicate with any user environment of the system 200.

[0042] Referring now more specifically to system controller 250a (system controller 250b may be similarly configured), for example, it may include one or more general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, microcontrollers, integrated circuits, programmable logic devices (PLDs), field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or any suitable controller or processing device, etc. (not shown) (hereinafter collectively referred to as one or more processors). The one or more processors of system controller 250a may be configured to execute one or more software-based applications and / or firmware-based modules, which may include instructions that, when executed by the one or more processors, may configure the one or more processors to perform signal encoding, data processing, input / output processing, or any other functions and / or features of the system controller as described herein. These features and functions are provided in part by Figure 2252 and 260 in the system controller 250a are represented, which are further described below. For example, modules 252 and 260 can be executed as one or more software-based processes. It will also be recognized that in addition to and / or as an alternative to software-based instructions and processes, the features, functions and processes described herein can also and / or alternatively be provided by hardware. The system controller 250a can also include one or more memory modules / devices (including volatile and non-volatile memory modules / devices) that can be communicatively coupled to one or more processors. The memory module / device can be implemented as one or more external integrated circuits (ICs) and / or as one or more internal circuits of one or more processors. One or more memory modules / devices can store software-based applications and can also provide execution space when the processor executes the application. The system controller 250a can also include one or more communication interfaces / transceivers / network interface devices (not shown) that are communicatively coupled to the processor and / or memory device / module. The communication interface can allow the system controller 250a to communicate through one or more wired and / or wireless communication networks. As an example, the communication interface can allow the system controller 250a to communicate wirelessly with the control device 220a, as similarly described for the load control system 100. The communication interface can also allow the system controller 250a to communicate wirelessly with a router (not shown) and / or communicate with the router via one or more wired connections, for example, the router is located locally in the user environment 202a and provides a local network to the user environment. Through this local network, the system controller 250a can communicate with the network device 144 local to the user environment 202a, and can also communicate with the network 282 (such as through an Internet service provider not shown). The system controller 250a can also include one or more databases 254, as further described herein. These databases can be flat databases, relational / SQL databases, NoSQL / non-SQL databases, and / or time series databases, etc., but any form of one or more databases can be used. The system controller 250a can also include one or more user interfaces, such as a display monitor, a keyboard, a mouse, a speaker, an audio receiver, etc. Although system controller 250a is shown with exemplary modules 252 and 260 and exemplary database 254, the system controller may include fewer, other, and / or additional modules and databases.

[0043] Referring more specifically to modules 252 and 260 and database 254, database 254 may maintain configuration information for load control system 250a. For example, this information may include: control devices 220a of the load control system; configuration of the user environment 202a, such as the rooms in the environment, which control devices 220a are located in which rooms, the communication addresses of the control devices required to communicate with the devices, which control source devices can be controlled by / associated with which control target devices; configuration information for the control devices (e.g., button scene configurations, occupancy / vacancy sensor configurations, etc.); system configurations (such as clock schedules), etc. The database may also maintain status information for the control devices (e.g., error conditions, light levels, shading levels, HVAC levels, power consumption levels, etc.). The database may also maintain event-based information, which may include a record of events when events occur within the system, as described below. These are examples only, and other and / or additional or less information is possible.

[0044] For the purpose of description, module 252 may be referred to herein as a core module or core 252, and may be configured to execute as one or more software-based processes. Core 252 may be configured to act as a communication module between control device 220a and a system controller, assist and / or monitor communication between a control source device and a control target device, and store relevant information in a database 254. This information may include, for example, changes in the association of which control source devices with which control target devices. The information may also include event-based information, such as (i) events detected by a control source device (e.g., occupancy / vacancy as detected by sensor 110, light levels as detected by sensors 108 and 120, detection of a button actuated on a remote control device 113 or a wall panel / switch 113, etc.), (ii) commands communicated by a control source device to a control target device to change settings based on detected events (e.g., changes in light levels, shade levels, HVAC levels, etc.), and (iii) commands from a control target device indicating / confirming changed settings. The core 252 may receive status messages directly from the control devices, such as error conditions, light levels, shade levels, HVAC levels, power consumption levels, occupancy / vacancy conditions, etc., and store such information in the database 254. The core 252 may also run a clock schedule and communicate messages to the control devices according to those schedules. Again, the core 252 may store such changes to the control devices and / or confirmations from the control devices in the database 254. The core 252 may also communicate information / messages to the module 260 (which may be referred to as a gateway module or gateway 260 for descriptive purposes), as described below. The core 252 may receive messages from the gateway 260, which may cause the core to change configuration parameters of the system controller (e.g., clock settings), or communicate messages to the control devices (such as changing light levels), or adjust configuration / operation parameters of the control devices (e.g., changing scene buttons on switch buttons, occupancy / vacancy sensor configuration), etc. The core 252 may respond back to the gateway 260 after performing such operations. Core 252 may also receive requests from gateway 260 for any information stored in database 254 as discussed above, and report that information back to the gateway. These are examples, and core 252 may perform other and / or additional functions and operations.

[0045] Turning to gateway 260, it can be configured to act as an interface between system controller 250a and external devices (such as local network device 144 and remote network devices 280a and 280b located in user environment 202a). For example, gateway 260 can receive messages from network device 144 and / or network devices 280a and / or 280b, and route those messages within system controller 250a, such as to core 252 for execution. Gateway 260 can also receive responses to such messages, such as from core 252, and route them back to network devices 144, 280a and / or 280b. For example, gateway 260 can also receive information based on conditions and events, such as from core 252, and route the information to network devices 144, 280a and / or 280b. These are examples, and other examples are also possible. To perform such functions and operations, the gateway 260 may include an API (application programming interface) server 264, a local shell client (also referred to herein as a shell client) 262, and an MQTT (message queue telemetry transport) client 266. Each of the API server 264, the local shell client 262, and the MQTT client 266 may operate as one or more software-based processes within the system controller 250a, but other configurations are possible. It will be appreciated that the names API server, local shell client, and MQTT client as used herein are for descriptive purposes only.

[0046] The local shell client 262 may be configured to serve as or act as an interface point to a network device 144 that is local to the system controller 250a (e.g., on the same local network as the system controller and / or within the user environment 202a). The local shell client 262 may be configured to support a communication connection 234 with the network device 144. The connection may be, for example, a connection based on TCP / IP (Transmission Control Protocol / Internet Protocol) or UDP / IP (User Datagram Protocol), although other connections may also be used. The local shell client 262 may provide a shell-type interface (e.g., a command-line type interface) to the network device 144 through the connection. The interface may be a secure shell interface (e.g., using the Secure Shell (SSH) protocol). It will be appreciated that although the local shell client 262 is described herein as an interface point to a network device 144 that is local to the system controller 250a, a network device that is located on a different network than the system controller (i.e., not on the same local network as the system controller) and / or that is not within the user environment 202a may also communicate with the system controller using the local shell client 262.

[0047] The MQTT client 266 can be configured to be used as or act as an interface point to the message broker 270, and therefore used as or act as an interface point to the network devices 280a and 280b at the far end of the system controller 250a. The MQTT client 266 can support a communication connection 230a with the message broker 270. This connection can be, for example, a connection based on TCP / IP, but other connections can be used. On this connection, in the case where the MQTT client 266 acts as a client of the message broker 270, the MQTT client 266 can support, for example, a message delivery protocol based on MQTT publish-subscribe with the broker. As further described below, the MQTT client 266 can send a message from the system controller to the message broker by publishing the message to one or more defined topics, thereby sending it to the network devices 280a and / or 280b, because the term is used in a protocol based on messaging. Similarly, the MQTT client 266 can receive messages from the network devices 280a and / or 280b from the message broker, for example, by subscribing to one or more defined topics.

[0048] The system controller 250a may support an application programming interface (API) that may include a well-defined set of commands and responses (generally referred to herein as an API or as "API messages") for interacting with the network devices 144, 280a, and / or 280b. Service-based applications (e.g., software-based applications) provided by or executed on the network devices 144, 280a, and / or 280b may interact with the system controller using the API. For these communications, the API server 264 may serve as a source and destination within the system controller 250a. For example, the network devices 144, 280a, and / or 280b may execute one or more software-based applications that provide a set of defined services to the user. These services may be based at least in part on interaction with the system controller 250a. For example, the network device 144 may provide a software-based application to the user that allows the user to control lights or shades within the user environment 202a. Similarly, the network device 280a may provide a software-based application to the user that allows the user to control lights or shades from a location outside the user environment. As another example, as described above, network device 280a may provide alert-based services.

[0049] To provide such services, the network device may communicate an API message to the system controller 250a using the API of the system controller 250a. For example, the network device 144 may communicate the API message to the local shell client 262, which may then forward the message to the API server 264, which may then interpret and execute the message. Similarly, the network device 280a may communicate the API message to the MQTT client 266 via the message broker 270, which may then forward the message to the API server 264, which may then interpret and execute the message. To execute / interpret the API message, the API server 264 may communicate the message (or a translated form of the message) to the core 252 to provide / execute the message, the API server may communicate with the database 254 to retrieve and / or store information, and / or the API server may process the message itself. Other examples are also possible.

[0050] Similarly, to provide such services, the system controller 250a may communicate API messages to the network devices 144, 280a, and / or 280b. For example, the core 252 may communicate information intended for the network device by sending the information to the API server 264. This information may include a response to a message (e.g., a message for controlling the control device 220a) received from the network device and executed by the core 252 or a result from the message. This information may include information retrieved from the database 254 by the core 252 in response to a message received from the network device. Similarly, the API server 264 may retrieve information directly from the database 254 in response to a message received from the network device. For example, when the API server 264 receives information from the core 252 and / or the database 254, it may format the information according to one or more appropriate API messages, and then forward the message to the local shell client 262 for forwarding to the network device 144, and / or forward the message to the MQTT client 266 for forwarding to the message broker 270 and the network device 280a and / or 280b. Other examples are also possible.

[0051] With respect to information flowing out from the system controller 250a to the network devices 144, 280a, and / or 280b, in some cases, as described above, the information may be responsive to messages received from the network devices. In some cases, the API server 264 may communicate such response messages to both the local shell client 262 and the MQTT client 266, regardless of where the original message originated (i.e., whether it came from the network device via the local shell client 262 or from the network device via the MQTT client 266). In other cases, the API server may forward the response message to only one or the other of the local shell client 262 and the MQTT client 266, depending on which interface the original message originated from.

[0052] According to another aspect of the system controller 250a, the core 252 may continuously report condition and / or event-based information originating from within the load control system 210a to the API server 264. For example, the core 252 (i) may report to the API server 264 events detected by control source devices from within the user environment 202a (e.g., occupancy / vacancy detected by sensor 110, light levels detected by sensors 108 and 120, detection of a button actuated on a remote control device 113 or a wall panel / switch 113, etc.), (ii) may report to the API server 264 changes in electrical load states that may result from messages from control source devices (e.g., changes in light levels, shade levels, HVAC / thermostat levels / readings, etc.), and (iii) may report to the API server 264 changes in electrical load states due to, for example, clock events. The core 252 may also report to the API server 264 changes in the configuration of the load control system, such as the addition of new control devices, changes or creation of associations between control source devices and control target devices, etc. Generally speaking, the API server 264 can forward any such information received by the API server 264 from the core 252 as an API message to the local shell client 262 and / or the MQTT client 266 for forwarding to the network device 144 and the message broker 270, and thus to the network device 280a and / or 280b. In this way, the network device can be informed of the status of the load control system 210a in a "real-time" manner without having to query the load control system for its status.

[0053] Now referring more specifically to the MQTT client 266, the message broker 270 (note that Figure 2270; nevertheless, it will be appreciated that the system 200 may include multiple message brokers) and network devices 280a and 280b, each of which may include a client process that supports a corresponding connection 232a and 232b (e.g., a TCP / IP connection, but other connections may also be used) with the message broker 270, and may, for example, support an MQTT publish-subscribe based messaging protocol with the message broker through the connection. The message broker 270 may be one or more computing devices (e.g., one or more computing servers) that act as an MQTT message broker, for example, supporting the MQTT publish-subscribe messaging protocol. For example, the computing device of the message broker 270 may include one or more general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, microcontrollers, integrated circuits, programmable logic devices (PLDs), field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or any suitable controller or processing device, etc. (hereinafter collectively referred to as one or more processors) (not shown). One or more processors of the message agent 270 may be configured to execute one or more software-based applications and / or firmware-based modules, which include instructions that, when executed by one or more processors, may configure one or more processors to perform signal encoding, data processing, input / output processing, or configure the message agent 270 to provide any other function or operation of the MQTT message agent functions and operations as described herein. It will also be recognized that in addition to and / or as an alternative to software-based instructions and processes, the features, functions, and processes described herein of the message agent 270 may also be provided by and / or alternatively by hardware. The message agent 270 may also include one or more memory modules / devices (including volatile and non-volatile memory modules / devices) that may be communicatively coupled to one or more processors. The memory modules / devices may be implemented as one or more external integrated circuits (ICs) and / or as one or more internal circuits of one or more processors. One or more memory modules / devices may store software-based applications and may also provide execution space when the processor executes the application. The message agent 270 may also include one or more communication interfaces / transceivers / network interface devices (not shown) communicatively coupled to the processor and / or memory devices / modules. The communication interfaces may allow the message agent 270 to communicate over one or more wired and / or wireless communication networks (such as networks 282 and 283).

[0054] For example, when the MQTT clients 266 of the corresponding system controllers 250a and 250b establish corresponding connections 230a and 230b with the message broker 270, and form corresponding MQTT connections with the message broker through the connections 230a and 230b, the message broker can, for example, start corresponding processes (such as software-based processes) 272a and 272b with each MQTT client 266. Similarly, for example, when each network device 280a and 280b establishes corresponding connections 232a and 232b with the message broker 270, the message broker can start corresponding processes (such as software-based processes) 274a and 274b with each network device. According to one example of the MQTT protocol, the message broker 270 can receive corresponding API messages from the MQTT clients 266 via the connections 230a and 230b at the processes 272a and 272b, respectively, and forward those messages to the processes 274a and / or 274b. Processes 274a and 274b may then forward the API messages to network devices 280a and 280b via connections 232a and 232b, respectively. Similarly, message broker 270 may receive corresponding API messages from network devices 280a and 280b at processes 274a and 274b, respectively, via connections 232a and 232b, and forward those API messages to processes 272a and / or 272b. Processes 272a and 272b may then forward the API messages to MQTT clients 266 of system controllers 250a and 250b, respectively, via connections 230a and 230b. In general, network devices 280a and 280b may undergo an authentication process with message broker 270 before the message broker may forward messages between the network devices and the system controllers.

[0055] According to an example of the MQTT protocol, for example, when the MQTT client 266 of the system controller 250a receives API messages from the API server 264, it can communicate those messages to the message broker 270 through the connection 230a by publishing the API messages to the defined topic "A". For example, assuming that the network device 280a desires to receive information from the system controller 250a, it can subscribe to the same topic "A" with the message broker 270. After subscribing to the topic "A", the message broker 270 can forward the API messages it receives from the system controller 250a at the process 272a through the connection 232a to the network device 280a via the process 274a. Similarly, in order for the network device 280a to communicate the API messages to the system controller 250a, the network device 280a can communicate those messages to the process 274a at the message broker 270 through the connection 232a by publishing the API messages to the defined topic "B" (it will be recognized that the topics A and B can be the same or different). To receive API messages from network device 280a, MQTT client 266 of system controller 250a may subscribe to topic "B" with the message broker. After subscribing to topic "B", message broker 270 may forward the API messages it receives from network device 280a at process 274a to MQTT client 266 of system controller 250a via process 272a over connection 230a. Other examples are also possible.

[0056] Now with specific reference to the subject matter described above, according to one example, each system controller 250a and 250b of the system 200 may have an assigned communication address, such as a MAC address (Media Access Control address) (or possibly more than one address). For example, this may be an address assigned to a communication interface or transceiver or network interface device of the system controllers 250a and 250b that supports the connection 230a and 230b with the message broker, respectively (for descriptive purposes, MAC addresses will be used herein. Nevertheless, different addresses assigned to each system controller may alternatively be used in place of MAC addresses as discussed herein (such as utilizing subject matter)). The MAC addresses of each system controller 250a and 250b of the system 200 may be different / unique. In this example, the system controller 250a may have a MAC address "A1:B1:C1:D1:E1:F1", and the system controller 250b may have a MAC address "A2:B2:C2:D2:E2:F2" (as indicated by the labels 222a and 222b). The MAC addresses will be discussed further below. According to another aspect of the system 200, each system controller 250a and 250b may be assigned a unique identifier (ID) value (Unique ID Value), which may be a random value. In this example, the system controller 250a may have a unique ID value "ABC123", and the system controller 250b may have a unique ID value "ABC789" (as indicated by the annotations 222a and 222b). These are merely examples. According to yet another aspect of the system 200, a common universal identifier may be assigned to all system controllers 250a and 250b of the system 200. In this example, each system controller 250a and 250b has a common universal identifier "1201" (as indicated by the annotations 222a and 222b). Again, these are merely examples. (It will be appreciated that while the system controllers may be described herein as having unique identifiers, MAC addresses, and universal identifiers associated therewith, these values ​​may also be generally considered to be associated with the system controller's corresponding load control system and / or corresponding user environment). The topics used by the system controllers 250a and 250b and the network devices 280a and 280b of system 200 may have a format that uses, for example, (i) a unique ID value assigned to the system controllers 250a / 250b, (ii) a universal identifier assigned to all system controllers, and (iii) one of several different topic identifiers / values, such as "Request" and "Response", although additional and / or other values ​​may also be used.As an example, the format of the topics used by system 200 may be of the form: " / u / universal identifier / d / system controller ID / topic identifier," where in this example, the universal identifier may be "1201," the system controller ID may be "ABC123" or "ABC789," and the topic identifier may be "request" or "response." Again, this is merely an example, and other variations are possible. For example, the topics used by system controllers 250a and 250b and network devices 280a and 280b of system 200 may have a format that uses, for example, (i) a MAC address assigned to system controllers 250a / 250b, (ii) a universal identifier assigned to all system controllers, and (iii) one of several different topic identifiers / values, such as "request" and "response," although additional and / or other values ​​may also be used. As an example, the format of the topic used by system 200 may be of the form: " / u / universal identifier / d / MAC address / topic identifier," where the universal identifier may be "1201," the MAC address may be "A1:B1:C1:D1:E1:F1" or "A2:B2:C2:D2:E2:F2," and the topic identifier may be "request" or "response." In one aspect, the two examples are similar in that each example uses a universal identifier, a unique identifier (e.g., a MAC address of a system controller or a unique ID value assigned to a system controller), and a topic identifier / value. For ease of description, this document will use a topic of the form " / u / universal identifier / d / system controller ID / topic identifier" to describe the exemplary system. Again, other variations are possible and may be used.

[0057] According to one example, whenever the MQTT client 266 of the system controller 250a sends an API message to the message broker 270, it may publish the API message to the broker along with the topic “ / u / 1201 / d / ABC123 / response”. Similarly, whenever the MQTT client 266 of the system controller 250b sends an API message to the message broker 270, it may publish the API message to the broker along with the topic “ / u / 1201 / d / ABC789 / response”. For example, if the network device 280a, for example, wishes to receive API messages from the system controller 250a, it may subscribe to the topic “ / u / 1202 / d / ABC123 / response” with the message broker (it will be appreciated that the network device 280a may only need to subscribe to a portion of the topic, such as “ / u / # / d / ABC123 / response”, where “#” represents a wildcard value). Similarly, if network device 280a, for example, wishes to receive API messages from system controller 250b, it may subscribe with the message broker to the topic " / u / 1202 / d / ABC789-response" (or, for example, simply " / u / # / d / ABC789 / response"). In this manner, when the message broker receives an API message published by system controllers 250a and 250b, it may examine the associated topic, determine which network devices 280a and 280b may have (at least partially) subscribed to the topic, and forward the message via processes 272a / 272b and 274a / 274b. As can be seen, by using the system controller ID, network devices 280a and 280b may receive API messages from the desired system controllers 250a and 250b.

[0058] According to another example, for example, whenever the network device 280a wishes to send an API message to the system controller 250a, it may publish the message to the message broker 270 using the topic “ / u / 1202 / d / ABC123 / request”. Similarly, for example, whenever the network device 280a wishes to send an API message to the system controller 250b, it may publish the message to the message broker 270 using the topic “ / u / 1202 / d / ABC789 / request”. In other words, by using the system controller ID, the network devices 280a and 280b may communicate with the desired system controllers 250a and 250b. In order for the system controller 250a to receive the API message from the network device 280a, the MQTT client 266 of the system controller 250a may subscribe to the topic “ / u / 1202 / d / ABC123 / request” (or, for example, simply “ / u / # / d / ABC123 / request”). Similarly, in order for system controller 250b to receive API messages from network device 280a, the MQTT client 266 of system controller 250b can subscribe to the topic " / u / 1202 / d / ABC789 / requests" (or, for example, simply " / u / # / d / ABC123 / requests"). In this way, when the message broker 270 receives API messages published by network devices 280a and 280b, it can check the associated topics, determine which system controllers may have (at least partially) subscribed to the topics, and forward the messages via processes 274a / 74b and 272a / 272b. Thus, by using the system controller IDs, network devices 280a and 280b can send API messages to the desired system controllers 250a and 250b.

[0059] As described above, when events occur within the corresponding load control system, in addition to publishing API messages that respond to commands from network devices, system controllers 250a and 250b can also continuously publish API messages to the message broker 270. Network devices 280a and 280b that subscribe to receive API messages from the corresponding system controller (e.g., whose subscription is based on the topic of "response" and the system controller ID of the system controller) can then continuously receive API messages. If no network device 280a and 280b subscribes to receive messages published by the corresponding system controller 250a and 250b, the message broker can simply discard the message. Multiple network devices 280a and 280b can also subscribe to receive API messages from a given system controller at the same time. As can also be seen from the above, network devices 280a and 280b can communicate specific commands to the system controller and / or request information from the system controller by publishing API messages to the message broker using a topic based on "request" and the appropriate system controller ID for the specific system controller 250a and 250b. Similarly, the network device may receive responses to API messages from the corresponding system controller by subscribing with the message broker 270 to messages having a topic based on "response" and the appropriate system controller ID.

[0060] Although system 200 is described herein as being based on the MQTT protocol, other message-based protocols, such as the Advanced Message Queuing Protocol (AMQP), may also be used.

[0061] The system 200 uses an MQTT message based system to enable the network devices 280a and 280b to communicate with the system controllers 250a and / or 250b of the corresponding user environments 202a and 202b. Figure 3, an exemplary system 300 is shown. While system 200 uses an MQTT message-based system to enable network devices 280a and 280b to communicate with system controllers 250a and / or 250b, system 300 allows, for example, network device 380 to communicate with system controllers 250a and / or 250b using an HTTP (Hypertext Transfer Protocol)-based interface. Network device 380 may be similar to network devices 280a and 280b in that it may be a device being used by a user (e.g., a homeowner of a user environment) and / or may be a third-party integrator configured to provide one or more services based on interaction with corresponding system controllers 250a and / or 250b through APIs supported by these controllers. Specifically, system 300 may allow network device 380 to use an HTTP interface to receive API messages published by corresponding system controllers 250a and 250b. The information of these API messages may include, for example, event and condition based information occurring in the respective load control systems 210a and 210b and continuously published by the system controllers 250a and 250b to the message broker 370 (which may also include API messages responsive to messages from network devices). Figure 4 The exemplary system 400 of (discussed below) illustrates an exemplary system that also allows the network device 380 to communicate API messages to (and receive responses from) the respective system controllers 250a and 250b using an HTTP interface. Figure 3 Only one network device 380 is shown, but there may be many such devices in system 300.

[0062] System 300 may include one or more message brokers 370 (one shown here) which may operate similarly to message broker 270 as described for system 200. System 300 may also include one or more user environments 202a and 202b and respective system controllers 250a and 250b (and associated control devices 220a and 220b) which may have an MQTT interface with message broker 370; and may also include one or more network devices 280a and 280b which may communicate with message broker 370 via the MQTT interface. System controllers 250a and 250b, message brokers 370, and network devices 280a and 280b may operate similarly as described for system 200. System 300 may now also include one or more data aggregators 310 (one shown here), one or more network servers 340 (one shown here), and one or more network devices 380 which may communicate with network server 340 (where one or more network devices are in communication with network server 340). Figure 3 380).

[0063] Furthermore, although the system 300 is described herein as being based on the MQTT protocol, other message-based protocols, such as the Advanced Message Queuing Protocol (AMQP), may also be used.

[0064] For example, the data aggregator 310 may be one or more computing devices (e.g., one or more computing servers) that may include one or more general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, microcontrollers, integrated circuits, programmable logic devices (PLDs), field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or any suitable controllers or processing devices, etc. (hereinafter collectively referred to as one or more processors) (not shown). The one or more processors of the data aggregator 310 may be configured to execute one or more software-based applications and / or firmware-based modules that include instructions that, when executed by the one or more processors, may configure the one or more processors to perform signal encoding, data processing, input / output processing, or any other function that configures the data aggregator to operate as described herein. It will also be recognized that the features, functions, and processes of the data aggregator 310 described herein may also and / or alternatively be provided by hardware in addition to and / or as an alternative to software-based instructions and processes. The data aggregator 310 may also include one or more memory modules / devices (including volatile and non-volatile memory modules / devices) that may be communicatively coupled to the one or more processors. The memory module / device may be implemented as one or more external integrated circuits (ICs) and / or as one or more internal circuits of one or more processors. One or more memory modules / devices may store software-based applications and may also provide execution space when the processor executes the application. The data aggregator 310 may also include one or more communication interfaces / transceivers / network interface devices (not shown) that are communicatively coupled to the processor and / or memory device / module. The communication interface may allow the data aggregator 310 to communicate with the message agent 370 and the network server 340 via one or more wired and / or wireless communication networks (not shown). The data aggregator 310 may also include one or more user interfaces, such as a display monitor, a keyboard, a mouse, a speaker, an audio receiver, and the like.

[0065] The data aggregator 310 may include an MQTT client module 312 (also referred to herein as an MQTT client), a pipeline module 314 (also referred to herein as a pipeline), and a filter module 316 (also referred to herein as a filter) (it will be appreciated that the names data aggregator, MQTT client, and pipeline as used herein are for descriptive purposes only). Each of these modules may be configured to operate as one or more software-based processes within the data aggregator, but other configurations may also be used. Although the data aggregator 310 is shown as having exemplary modules 312, 314, and 316, the aggregator may also include fewer, other, and / or additional modules. Starting with the MQTT client 312, it may be configured to support a communication connection 332 with a message broker 370. This connection may be, for example, a TCP / IP-based connection, but other connections may also be used. Over this connection, in the case where the MQTT client 312 acts as a client of the message broker 370, the MQTT client 312 may support a MQTT publish-subscribe-based messaging protocol with the message broker. For example, when the MQTT client 312 of the data aggregator 310 establishes a connection 332 with the message broker and forms an MQTT connection with the broker, the message broker can start a corresponding process 376 with the MQTT client 312. According to one example, the MQTT client 312 can subscribe to the topic " / u / 1202 / d / # / response" (where "#" represents a wildcard value) with the message broker 370. By subscribing to a topic using a universal identifier (here "1201") common to all system controllers 250a and 250b, the message broker 370 can forward all API messages published by the system controllers 250a and 250b to the message broker 370 using a "response"-based topic from the corresponding process 272a / 272b to the process 376. In turn, the process 376 can forward the API message to the MQTT client 312 via the connection 332. It will be appreciated that other topics can also be used. For example, the MQTT client 312 may also subscribe to the topic " / u / 1202 / d / # / requests" (or alternatively the topic " / u / 1202 / d / # / #") with the message broker 370. Here, the message broker 370 may also forward all API messages published to the message broker 370 by the network devices 280a and 280b using the "requests" based topic from the respective processes 274a / 274b to the process 376 (and thus to the MQTT client 312). Again, these are merely examples, and other mechanisms may be used for the message broker 370 to forward API messages to the data aggregator 310.For example, the data aggregator may subscribe to receive API messages from a particular set of system controllers, for example, by specifying the full topics used by the respective controllers (e.g., " / u / 1202 / d / ABC123 / / responses" and " / u / 1202 / d / ABC789 / responses"). Assuming that the data aggregator subscribes only to the "responses" based topic from all system controllers 250a and 250b, when the message broker passes the API message to the process 376, the process may then communicate the API message to the MQTT client 312 via the connection 332. The process 376 may also communicate along with the API message the full topic to which the API message was published by the respective system controllers 250a and 250b (i.e., the topic may include the system controller ID of the respective system controller, such as " / u / 1202 / d / ABC123 / requests" or " / u / 1202 / d / ABC789 / requests"). When the MQTT client 312 receives an API message (and associated topic) from the message broker 370 , it may forward the API message / topic to the conduit module 314 .

[0066] The pipeline module 314 can be configured to act as a data cache / message queue, for example, it receives API messages and possible topics from the MQTT client 312, processes the API messages (e.g., aggregates several API messages into larger blocks to improve data efficiency), places / writes the API messages into the message queue, and controls the filter 316 to read the API messages from the message queue for further processing. According to another example, the pipeline module 314 can be a plurality of message queues, wherein the MQTT client 312 places the API messages into the corresponding queues in the queues. In this way, the pipeline module 314 can act as a temporary storage device until the filter 316 processes the API messages, as described below. According to another aspect, depending on the number of user environments 202a and 202b / load control systems 210a and 210b in the system 300, there can be multiple message brokers 370, wherein different message brokers provide services for different system controllers 250a and 250b. Here, the data aggregator 310 can have multiple MQTT clients 312, each of which leads to a corresponding message broker. According to this example, the pipeline module 314 can receive API messages from each MQTT client 312 and aggregate these messages into one message queue or multiple message queues (e.g., one message queue for each MQTT client) for processing by the filter 316.

[0067] Filter 316 can represent one or more modules (e.g., which can operate as one or more software-based processes) that read and / or receive API messages (and associated topics) from pipeline module 314, filter those API messages based on one or more criteria, and then forward the resulting information to one or more destinations. In one aspect, there may be multiple filter modules executing at any given time, each filter module analyzing the same API message read / received from pipeline module 314, and each filter module searching and analyzing specific data and routing the resulting information to a corresponding destination. According to another aspect, assuming that pipeline module 314 is a plurality of message queues, each queue can have one or more corresponding filters. Filter 316 can be dynamic, in that an administrator can change the filter according to the desired configuration of system 300. Filter 316 can filter based on specific fields of the API message itself and / or based on topics associated with the corresponding API message. Different filters can be configured to have different functions. For example, one filter may operate to simply remove / discard certain types of API messages (e.g., there may be certain status information generated by system controllers 250a and 250b that is not required by network device 380) and route the remaining API messages (and associated topics) to a certain destination. Another filter may be configured to operate to search for and detect certain API messages and / or topics and route those API messages (and associated topics) to a certain destination. Another filter 316 may be configured to perform operations on API messages read / received from pipeline module 314 (such as performing statistical analysis on the API messages) and forward the results to a specific destination. It will be appreciated that other examples are possible.

[0068] According to the exemplary system 300, the filter 316 can have a communication connection 334 with the network server 340. This connection can be, for example, a TCP / IP or UDP / IP based connection, although other types of connections can also be used. The network server 340 can support an HTTP / HTTPs (Hypertext Transfer Protocol / Secure Hypertext Transfer Protocol) interface on this connection using standard methods (such as GET, PUT, POST, DELETE, etc.), but it will be appreciated that other interfaces can also be used. When the filter 316 receives API messages from the pipeline module 314, the filter can discard certain messages based on one or more fields of the message and pass the remaining API messages (e.g., together with their corresponding topics published by the system controllers 250a and 250b) to the network server 340 via the connection 334. The filter 316 can do this by using a standard HTTP method such as a PUT command, but other commands can also be used. Again, the data aggregator 310 can include other filters that route API messages / information to other destinations. As an example, the system 300 may also include a data storage system 390 that receives information from the filter 316 and stores this information in a database. The database 390 may be a flat database, a relational / SQL database, a NoSQL / non-SQL database, and / or a time series database, etc., but any form of one or more databases may be used. It will be appreciated that the filter 316 may communicate the API messages to the network server 340 one at a time or in periodic batches (such as every X seconds or minutes, every Y messages, and / or when Z bytes of messages are ready to be forwarded, etc.). Other variations are also possible.

[0069] As described above, the pipeline module 314 can be a plurality of message queues, each with a corresponding filter 316. Here, each filter 316 can have a corresponding connection 334 with a network server 340, and can be similarly configured to discard certain API messages received from its corresponding message queue and communicate the remaining API messages to the network server 340 through its corresponding connection.

[0070] According to a specific example, Amazon Web Services can provide one or more operations / functionalities of data aggregator 310, wherein API messages from message broker 370 can be fed to a Kinesis stream consisting of one or more shards, and wherein one or more Lambda functions can obtain API messages from the Kinesis stream, filter the API messages to discard certain messages, and forward the remaining API messages (and associated topics) to network server 340 through one or more HTTP interfaces 334. Other examples are also possible.

[0071] For example, now turning to the network server 340, it can be one or more computing devices (e.g., one or more computing servers) that can include, for example, one or more general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, microcontrollers, integrated circuits, programmable logic devices (PLDs), field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or any suitable controllers or processing devices, etc. (hereinafter collectively referred to as one or more processors) (not shown). The one or more processors of the network server 340 can be configured to execute one or more software-based applications and / or firmware-based modules, which include instructions that, when executed by the one or more processors, can configure the one or more processors to perform signal encoding, data processing, input / output processing, or any other function that configures the network server 270 to function / operate as described herein. It will also be recognized that the features, functions, and processes described herein of the network server 270 can also and / or alternatively be provided by hardware in addition to and / or as an alternative to software-based instructions and processes. The network server 340 can also include one or more memory modules / devices (including volatile and non-volatile memory modules / devices) that can be communicatively coupled to the one or more processors. The memory module / device may be implemented as one or more external integrated circuits (ICs) and / or as one or more internal circuits of one or more processors. One or more memory modules / devices may store software-based applications and may also provide execution space when the processor executes the application. The network server 340 may also include one or more communication interfaces / transceivers / network interface devices (not shown) that are communicatively coupled to the processor and / or memory device / module. The communication interface may allow the network server 340 to communicate via one or more wired and / or wireless communication networks (not shown). On these networks, the network server 340 may support one or more connections 334 with the data aggregator 310, and may support corresponding connections 336 and 338 with corresponding network devices 380. The network server 340 may use standard methods on these connections to support HTTP / HTTPS-based interfaces, such as to communicate with the data aggregator 310 and the network device 380. On the one hand, the network server 340 may act as an HTTP publish-subscribe server.

[0072] The network server 340 may include a network service module 342 (also referred to herein as a network service) and a worker service module 344 (also referred to herein as a worker service) (it will be appreciated that the names network server, network service, and worker service as used herein are for descriptive purposes only). Each of these modules may operate as one or more software-based processes within the network server. For example, a message queue 348 may connect the network service module 342 and the worker service module 344. This message queue may be implemented as a Redis cache, but other implementations may also be used. The network server 310 may also include one or more databases, such as a subscription database 346. The subscription database 346 may be a flat database, a relational / SQL database, a NoSQL / non-SQL database, and / or a time series database, etc., but any form of one or more databases may also be used. Although the network server 340 is shown as having exemplary modules 342 and 344, a message queue 348, and a database 346, the server may also have other configurations.

[0073] Beginning with subscription database 346, it may include at least one entry for each system controller 250a and 250b of system 300. As further described below, network service 342 may treat / use the MAC addresses of system controllers 250a and 250b as topics or channels (as this term may be used for HTTP publish-subscribe servers) to which network device 380 may subscribe, but this is one example and other examples are possible. Assuming this format is used, subscription database 346 may include the MAC address for each system controller 250a and 250b, and may also include the corresponding topics that the system controller publishes and / or subscribes to with message broker 370 and associates / correlates each MAC address. For example, and as indicated by label 350, for system controller 250a, subscription database 346 may include the MAC address of the system controller ("A1:B1:C1:D1:E1:F1") and may associate this address with one or more of the topics used by system controller 250a (here, " / u / 1202 / d / ABC123 / requests" and " / u / 1202 / d / ABC123 / responses"). Similarly, for system controller 250b, subscription database 346 may include the MAC address of the system controller ("A2:B2:C2:D2:E2:F2") and may associate this address with one or more of the topics used by system controller 250b (" / u / 1202 / d / ABC789 / requests" and " / u / 1202 / d / ABC789 / responses"). A system administrator may configure and maintain this database. Thus, as new user environments 202 with corresponding system controllers 250 are added to the system 300, the subscription database 346 may be updated to include the MAC address of the new system controller and the associated topics. Again, this is one example, and other examples are possible. As another variation, the network service 342 may treat / use the system controller IDs of the system controllers 250a and 250b as topics or channels to which the network devices 380 may subscribe. Assuming this format is used, the subscription database 346 may include the system controller ID for each system controller 250a and 250b, and may also include and associate / correlate one or more of the corresponding topics that the system controller publishes and / or subscribes to with the message broker 370 with each system controller ID. For example, the subscription database 346 may be configured as follows:

[0074] System Controller ID :ABC123

[0075] theme : / u / 1202 / d / ABC123 / request

[0076] theme: / u / 1202 / d / ABC123 / response

[0077] System Controller ID :ABC789

[0078] theme : / u / 1202 / d / ABC789 / request

[0079] theme : / u / 1202 / d / ABC789 / response

[0080] Again, this is an example, and the network service 342 may associate any value / identifier with the respective system controllers 250a and 250b and use that value / identifier as a topic or channel and associate that value / identifier with one or more of the topics used by the system controllers. For purposes of description, the network service 342 is described herein as using the MAC addresses of the system controllers 250a and 250b as topics / channels.

[0081] Turning to network service 342, as shown, it may treat each of the MAC addresses listed in subscription database 346 as a topic or channel to which network device 380 may subscribe via interface 336. Network service 340 may be configured to operate as follows. Network device 380 may desire to receive API messages published to message broker 370 by, for example, system controller 250a. To this end, network device 380 may communicate with network service 342 via connection 336 to subscribe to the MAC address of system controller 250a (i.e., subscribe to MAC address "A1:B1:C1:D1:E1:F1"). When subscribing to the MAC address with network service 342, network device 380 may also provide the network service with a notification address (e.g., a uniform resource locator (URL)) to which network service 340 may publish any API messages. The network service may store the notification address in subscription database 346 along with an indication that network device 380 has subscribed to the MAC address of system controller 250a. In a similar manner, network device 380 may also communicate with network service 342 via connection 336 to unsubscribe a MAC address of a system controller, such as system controller 250a. Network service 342 may then update subscription database 346 to indicate that network device 380 has unsubscribed from the MAC address of system controller 250a. Network service 342 may otherwise store which network devices 380 have subscribed to which channels.

[0082] According to one example, the network service 342 may receive API messages published by all system controllers 250a and 250b as described above from the data aggregator 310 via one or more connections 334 (or a subset thereof if certain API messages, such as certain status messages, have been removed by the filter 316). Again, these API messages may have topics associated with them in the form of, for example, " / u / 1202 / d / ABC123 / response" and " / u / 1202 / d / ABC789 / response". When receiving the API messages, the network service 342 may use the configuration information of the subscription database 346 to translate the topics into MAC addresses. For example, the network service 342 may translate the topic " / u / 1202 / d / ABC123 / response" of the API message from the system controller 250a into the MAC address "A1:B1:C1:D1:E1:F1" of the system controller 250a. The network service 342 may then determine whether any network device 380 has subscribed to this MAC address. If the network device 380 has subscribed to the MAC address, the network service 342 may write, for example, the API message to the message queue 348 along with its associated topic and / or MAC address. Conversely, if no network device 380 has subscribed to the API message, the network service 342 may discard the API message. As an alternative to translating the topic of the API message received from the data aggregator 310 into a MAC address as just described, when the network device 380 subscribes to the MAC address, the network service 342 may use the subscription database 346 to translate the MAC address into a topic or portion thereof (e.g., translating the MAC address "A1:B1:C1:D1:E1:F1" of the system controller 250a into the topic " / u / 1202 / d / ABC123 / response"). When the network service receives an API message published by the system controllers 250a and 250b from the data aggregator 310, it may compare the topic associated with the message with the "topic" to which the network device 380 has subscribed. If the network device 380 has subscribed to the topic, the network service 342 can write the API message to the message queue 348 along with its associated topic and / or MAC address. Conversely, if no network device 380 has subscribed to the API message, the network service 342 can discard the API message. Other variations are also possible. In general, the network service can at least partially correlate / associate a received API message with a message that the network device expects to receive, via a MAC address as specified by the network device and via a system controller ID portion of the topic associated with the API message.

[0083] As described above, the network service 342 can receive API messages published by the system controllers 250a and 250b from the data aggregator 310 (or a subset thereof if the filter 316 has removed certain API messages), and can then determine or analyze each API message to determine whether any network device 380 has subscribed to receive the corresponding API message. As another variation, when the filter 316 receives API messages from the pipeline module 314, it can discard certain messages (such as certain status messages) and then periodically batch the remaining messages into blocks. The manner in which the messages are batched into blocks may vary. Some examples may include (i) batching messages based on time (e.g., batching messages within an X minute period), (ii) batching messages for multiple API messages (e.g., creating blocks of X API messages), (iii) batching messages based on size (e.g., creating blocks of X bytes or less), or some combination thereof. With respect to each batch of API messages, the filter 316 can determine the topics associated with the messages and communicate a list of these topics to the network service 342 via the connection 334. For example, filter 316 may provide the complete topic (e.g., " / u / 1202 / d / ABC123 / response" and " / u / 1202 / d / ABC789 / response") or just a portion of the topic (e.g., just the system controller ID). Alternatively, filter 316 may access subscription database 346 (as shown by connection 318) and translate the topic into a MAC address and pass the MAC address to network service 342. Other examples are also possible. In any case, filter 316 may not forward the actual API message at this time. Upon receiving the list of topics, network service 342 may determine for each topic whether network device 380 is currently subscribed to the topic (e.g., by correlating the topic with an already subscribed MAC address) and communicate back to filter 316 via connection 334 an indication of those topics that are already subscribed (or alternatively, not subscribed). Upon receiving this communication from network service 342, filter 316 may discard those API messages that are not subscribed from the batched API messages and forward the remaining API messages to network service 316 via connection 334. Upon receiving the API messages, network service 342 may write each API message and its associated topic and / or MAC address to message queue 348. Filter 316 and network service 342 may then repeat the process, with filter 316 batching another set of API messages and communicating with the network service to determine which associated topics are currently subscribed. Other variations are also possible. One advantage of this configuration is that less data needs to be communicated from data aggregator 310 to network server 340, thereby providing more efficient communication.

[0084] According to yet another variation, for example, each time a network device 380 subscribes to a network service 342 for a MAC address of a system controller 250, the network service 342 may translate the MAC address into a topic (e.g., for system controller 250a, it may translate the MAC address "A1:B1:C1:D1:E1:F1" into a topic " / u / 1202 / d / ABC123 / response"). The network service 342 may then communicate the topic to the filter 316 via connection 334, thereby instructing the filter 316 to forward any API messages with the corresponding topic. Alternatively, for example, assuming that the filter 316 has access to a subscription database 346, the network service 342 may pass the MAC address to the filter 316, which may then translate the MAC address into a topic. Other examples are also possible. It will be appreciated that if multiple network devices 380 subscribe to API messages from the same system controller, the network service 342 may only communicate with the filter 316 once. In any case, when the filter 316 receives the API message from the pipeline module 314, it may discard certain messages (such as certain status messages) and then compare the topic of the API message with the topic provided to it by the network service 342 to determine whether the network device 380 has subscribed to receive the message. If the network device 380 has subscribed to the topic, the filter 316 can forward the API message (and its associated topic) to the network service 342 via the connection 334. The network service 342 can then write the API message and its associated topic and / or MAC address to the message queue 348. Conversely, if no network device 380 has subscribed to the API message, the filter 316 can discard the API message. Similarly, whenever the network device 380 unsubscribes from the MAC address of the system controller 250 to the network service 342, the network service 342 can translate the MAC address into a topic and then communicate the topic to the filter 316 via the connection 334, thereby instructing the filter 316 to stop forwarding the related API messages. It will be appreciated that if multiple network devices subscribe to the same MAC address at the same time, network service 342 may not communicate this instruction to filter 316 while the other devices are still subscribing. Again, this is merely an example, and other variations are possible.

[0085] Turning to the worker service 344, it can read the API message from the message queue 348, determine the notification address of each network device 380 that is subscribed to receive the API message, and use the notification address to communicate the API message to the corresponding network device via the corresponding connection 338 (it will be recognized that the notification address may be different from the network device). The worker service 344 can use the subscription database 346 to determine the notification address as shown above, but other mechanisms can also be used to determine the address. When communicating the API message to the network device, the worker service 344 can include a topic associated with the API message and / or the MAC address of the corresponding system controller. Thereafter, for example, the network device 380 can receive the API message and act on it.

[0086] Although the network service 342 and the worker service 344 are shown and described as communicating via a message queue 348, this queue may not be required, and the two modules may communicate in other ways. However, in one aspect, the message queue 348 can provide a mechanism for temporarily storing API messages in high data demand situations. Moreover, for example, it is not necessary to use MAC addresses (rather than the "request" and "response" topics) as a mechanism for the network device 380 to subscribe to API messages, and the network service 342 and the network device 380 can be configured to subscribe directly to the topic (i.e., the network device 380 can subscribe to " / u / 1202 / d / ABC123 / response"). Nevertheless, the configuration using MAC addresses or variations thereof has at least one benefit, for example: the system controller 250 and the subscription database 346 can be updated in the future to use different topics. For example, a network device using a MAC address (which can be a static value) associated with the topic can allow the topic to change without affecting the service application provided by the network device.

[0087] Furthermore, a given network device 380 may subscribe to receive API messages generated by many system controllers from the network server 340. Similarly, many different network devices may subscribe to receive API messages generated by the same system controller from the network server 340.

[0088] Now go to Figure 4 , an exemplary system 400 is shown. System 400 may be similar to system 300, but in addition to receiving API messages from system controllers 250a and 250b, network device 380 may also communicate API messages to designated system controllers 250a and 250b (such as to control light levels in corresponding user environments), for example, using an HTTP interface.

[0089] According to the system 400, the network server 340 can now also include an MQTT client module 472, which can support a communication connection 474 with the message broker 370. This connection can be, for example, a TCP / IP-based connection, but other connections can also be used. On top of this connection, for example, when the MQTT client 472 acts as a client of the message broker 370, the MQTT client 472 can support a MQTT publish-subscribe-based messaging protocol with the message broker. For example, when the MQTT client 472 of the network server 340 establishes a connection 474 with the message broker and forms an MQTT connection with the broker, the message broker can start a corresponding process 476 with the MQTT client 472.

[0090] In order to communicate the API message to a specific system controller 250, such as system controller 250a, the network device 380 can publish the API message to the network service 342 via connection 336, and specifically, the message can be published to the MAC address of the system controller 250a (i.e., "A1:B1:C1:D1:E1:F1"). It should be noted that the network device has published the API message to the MAC address, and the network service 342 can use the subscription database 346 to translate the MAC address into a "request" topic associated with the MAC address (here " / u / 1202 / d / ABC123 / request"). Thereafter, the network service can, for example, forward the API message and the " / u / 1202 / d / ABC123 / request" topic to the MQTT client 472. The MQTT client 472 can then use the topic " / u / 1201 / d / ABC123 / request" to publish the API message to the message broker 370 via connection 474. At the same time, the MQTT client 472 can also subscribe to the "response" topic associated with the MAC address of the controller 250a (i.e., " / u / 1202 / d / ABC123 / response") with the message broker 370 through the connection 474, for example, which can also be forwarded to the MQTT client 472 by the network service 342. By subscribing to the "response" topic of the system controller 250a, the MQTT client 472 can receive any response to the API message from the system controller 250a.

[0091] Accordingly, when process 476 receives an API message from MQTT client 472, message broker 370 may forward the API message to process 272a for forwarding to system controller 250a (controller 250a which has subscribed to the topic “ / u / 1202 / d / ABC123 / request” as discussed above). When system controller 250a processes the API message, it may generate a response API message, which may be published to message broker 370 using the topic “ / u / 1202 / d / ABC123 / response”, for example, as described for systems 200 and 300. Because MQTT client 472 subscribes to the topic “ / u / 1202 / d / ABC123 / response”, message broker 370 may forward this response API message from process 272a to process 476, which may then forward the response API message to MQTT client 472 via connection 474. After receiving the response API message, for example, the MQTT client 472 may unsubscribe from the topic “ / u / 1202 / d / ABC123 / response” and may forward the response API message to the network service 342. Thereafter, the network service 342 may translate the topic of the response API message from “ / u / 1202 / d / ABC123 / response” back to the MAC address of the system controller 250a and communicate the response API message to the network device 380 via the connection 336. Again, other variations are possible, such as, for example, the network device 380 subscribing to the system controller ID instead of the MAC address.

[0092] According to another aspect of the system 400, the network server 340 can have multiple (two or more) MQTT clients 472 with corresponding connections 474 to the message broker 370. The network service 342 can use corresponding ones of the MQTT clients 472 (one at a time) to communicate API messages from the network device 380 to the corresponding system controller 250, and receive responses thereof.

[0093] Although system 400 is described herein as being based on the MQTT protocol, other message-based protocols, such as the Advanced Message Queuing Protocol (AMQP), may also be used.

[0094] Although the system 300 and the system 400 are described herein as including the data aggregator 310, another variation of these systems may not include this module. Here, the message broker 370 may communicate the API message directly to the network server 340. For example, if the message broker 370 is receiving a limited amount of information from the load control systems 210a and 210b, and / or if there are a limited amount of load control systems providing information to the message broker, the data aggregator 310 may not be needed. Similarly, variations of the system 300 and the system 400 may include the data aggregator 310, but may not necessarily include a filter 316 configured to remove the API message from the API message stream from the pipeline module 314. In other words, the data aggregator 310 may forward all the API messages it receives from the message broker to the network server 340, instead of removing some messages. Nevertheless, it will be appreciated that the data aggregator and its corresponding filter module can provide an exemplary mechanism for controlling the rate at which information flows into the network server 340 and the amount of data that flows in and needs to be communicated to the network server. Additionally, although the system controllers 250a and 250b have been described herein as generally forwarding a large volume of information / API messages to the message broker in a non-selective manner, and the data aggregator then filtering this information, the system controllers may be configured to selectively forward only certain API messages to the message broker. However, this may be undesirable because it may be difficult to access all of these systems and difficult to make modifications if it is later realized that additional information from the system controller may be needed / wanted. One advantage of the system controller non-selectively forwarding a large volume of information / API messages to the message broker and the filter module 316 being configured to selectively discard certain API messages is that if it is later realized that the filter 316 may need to forward additional information or discard other information, the administrator can simply update the filter.

[0095] Now go to Figure 5, an exemplary system 500 is shown. For example, system 500 is similar to system 400, but now also allows network device 580 to communicate messages with (i.e., send messages to and receive messages from) designated system controllers 250a and 250b using an API different from the API supported by the system controllers. In other words, as discussed with respect to system 400, network device 380 can communicate with system 400 using an API supported by system controllers 250a and 250b. According to system 500, network device 580 can communicate with system 500 via an HTTP interface, but now uses a third-party API that may be specific to the network device, where system 500 translates between the API supported by the system controllers and the third-party API. For descriptive purposes only, messages formatted according to the API supported by system controllers 250a and 250b will be referred to herein as "API messages", and messages formatted according to the third-party API supported by network controller 580 will be referred to herein as "third-party API messages."

[0096] Network device 580 may be similar to network devices 280a and 280b and network device 380 in that it may be a device currently being used by a user (e.g., a homeowner of a user environment) and / or may be a third-party integrator configured to provide one or more services based on interaction with corresponding system controllers 250a and / or 250b. Figure 5 Only one network device 580 is shown, but there may be many such devices, each configured to communicate with one or more system controllers, possibly simultaneously.

[0097] Compared to system 400, data aggregator 310 of system 500 may now include gateway module 502 (also referred to herein as a gateway) and API translator module 504 (also referred to herein as an API translator) (it will be appreciated that the names gateway and API translator as used herein are for descriptive purposes only). Although gateway module 502 and API translator module 504 are shown as part of data aggregator 310, these modules may alternatively be provided by one or more other computing devices, such as, for example, provided by network server 340 or message broker 370, or by another computing device or devices separate from any of message broker 370, data aggregator 310, or network server 340. Each of gateway module 502 and API translator module 504 may operate as one or more software-based processes within the data aggregator, but other implementations are possible.

[0098] Starting with the gateway 502, it can be configured to support a corresponding network communication connection 508 with each system controller 250a and 250b that the network device 580 is communicating. The gateway 502 can support an HTTP / HTTPS-based interface on the connection 508, and the network device 580 can communicate with the gateway 502 using the HTTP / HTTPS-based interface. As shown, the services provided by the network device 580 can be based on a third-party API. In this way, the network device 580 can communicate third-party API messages for specific system controllers 250a and 250b to the gateway 502. The gateway 502 can be configured to then forward the third-party API message to the system controller, as further described below. Similarly, if the system controller responds with an API message, the response message can be forwarded to the gateway 502, and then the gateway can forward the response message as a third-party API message to the network device. Similarly, the network device 580 can communicate with the gateway 502 to subscribe to receive API messages published by specific system controllers 250a and 250b. The gateway 502 may be configured to forward the subscription request to the network server 340. When the network server receives API messages from the subscribed system controller, the network server may forward these messages to the gateway 502, which may then forward the messages to the network device as third-party API messages. According to one example, the gateway 502 may be independent of the specific third-party API used by the network device 580, but may be configured such that the format of the third-party API used by the network device needs to be based on a standard. As an example, the gateway 502 may be configured such that the third-party API may need to be a RESTful (representational state transfer) based API, wherein, for example, the network device 580 communicates with the gateway 502 using standard methods (e.g., GET, PUT, POST, DELETE, etc.), and wherein, for example, the system controllers 250a and 250b and the control devices 220a and 220b are, for example, considered as resources. Again, this is one example, and other examples are possible.

[0099] Turning to the API translator 504, it can provide API translation services for the system 500. In particular, the API translator 504 can have a connection 510 with the gateway 502. When the gateway 502 receives a third-party API message destined for a particular system controller 250a or 250b from the network device 580, the gateway can forward the message to the API translator 504. The API translator 504 can be configured to then translate the third-party API message into an API message (i.e., an API message supported by the system controller) and forward the API message to the system controller. Similarly, assuming that the system controller responds with an API message, the message can be forwarded to the API translator 504. The API translator 504 can be configured to then translate the API message into a third-party API message and forward the third-party API message to the gateway 502, which can then forward the message to the network device 580. Similarly, when gateway 502 receives a subscription request from network device 580 to receive API messages published by a particular system controller (such as system controller 250a), the gateway can forward the request to the network server, which may be translated by API translator 504 if necessary. Assuming that the network server receives one or more API messages published by system controller 250a at connection 334, the network server can forward the one or more API messages to API translator 504. API translator 504 can be configured to then translate the one or more API messages into one or more third-party API messages and forward the one or more third-party API messages to gateway 502, which can then forward the one or more messages to network device 580.

[0100] According to one example, the system 500 may include multiple API translators 504, each of which is configured to translate messages between an API used by a system controller and a third-party API used by a network device, and each of which has a corresponding connection 510 with a gateway 502. When a network device 580 desires to communicate with and / or receive messages from a particular system controller 250a or 250b, the gateway 504 may use an "available" API translator 504 for that communication. In other words, a given API translator 504 may only support communication with one system controller 250a and 250b at any given time. According to one example, the API translator 504 may exist statically (i.e., there is a defined number of "runs" or executions at any given time), and the gateway 502 may use available / free translators as needed. According to another example, an API translator may be created by the gateway 502 as needed. According to this example, the gateway 502 and one or more API translators 504 may be specific to a particular third-party API. As discussed below, additional instances of gateway 502 and one or more API translators 504 may be used to support additional third-party APIs.

[0101] Assume that the system 500 includes multiple API translators 504, such as Figure 5 As further shown, each API translator can have a corresponding communication connection 512 with the network server 340 and specifically with the network service 342. This connection can be, for example, a TCP / IP or UDP / IP based connection, but other connections can also be used. The network server 340 / network service 342 can support an HTTP / HTTPS based interface over this connection using standard methods as discussed herein.

[0102] Reference will now be made to an exemplary operation of the system 500. In order to, for example, communicate a particular command or request to a particular system controller 250 (such as system controller 250a), the network device 580 can communicate a third-party API message to the gateway 502 via the communication connection 508. For example, the network device can use a standard POST command to communicate the message. Using this third-party API message, the network device can include the MAC address of the system controller 250a (i.e., "A1:B1:C1:D1:E1:F1") (but the system controller unique ID value can also be used, for example). Upon receiving the message, the gateway 502 can forward the third-party API message (and the MAC address) to the corresponding API translator 504 via the corresponding connection 510. Upon receiving the message, the API translator 504 can translate the third-party API message into an API message. Thereafter, for example, the operational flow can be similar to that described with respect to Figure 4As discussed above. The API translator 504 can then publish the API message to the network service 342 via the corresponding connection 512, and specifically, can publish the message to the MAC address of the system controller 250a (i.e., "A1:B1:C1:D1:E1:F1"). It should be noted that the API translator has published the API message to the MAC address, and the network service 342 can use the subscription database 346 to translate the MAC address into a "request" topic associated with the MAC address (here " / u / 1202 / d / ABC123 / request"). Thereafter, the network service can forward the API message and the " / u / 1202 / d / ABC123 / request" topic to the MQTT client 472. The MQTT client 472 can then use the topic " / u / 1201 / d / ABC123 / request" to publish the API message to the message broker 370 via connection 474. At the same time, the MQTT client 472 can also subscribe to the "response" topic associated with the MAC address of the controller 250a (i.e., " / u / 1202 / d / ABC123 / response") with the message broker 370 through the connection 474. By subscribing to the "response" topic of the system controller 250a, the MQTT client 472 can receive any response to the API message from the system controller 250a.

[0103] Accordingly, when process 476 of message broker 370 receives an API message from MQTT client 472, the message broker can forward the API message to process 272a for forwarding to system controller 250a (controller 250a that has subscribed to the topic " / u / 1202 / d / ABC123 / request" as discussed above). When system controller 250a processes the API message, it can generate a response API message, which can be published to message broker 370 using the topic " / u / 1202 / d / ABC123 / response", for example, as described for systems 200, 300, and 400. Because MQTT client 472 subscribes to the topic " / u / 1202 / d / ABC123 / response", message broker 370 can forward this response API message from process 272a to process 476, which can then forward the response API message to MQTT client 472 via connection 474. After receiving the response API message, the MQTT client 472 can unsubscribe from the topic “ / u / 1202 / d / ABC123 / response” and can forward the response API message to the network service 342. Afterwards, the network service 342 can translate the topic of the response API message from “ / u / 1202 / d / ABC123 / response” back to the MAC address of the system controller 250a and communicate the response API message to the API translator 504 through the connection 512.

[0104] After receiving the API response message from the network service 342, the API translator 504 can translate the API message into a third-party API message (such as a response message) and forward the third-party API message to the gateway 502 via the connection 510. Thereafter, the gateway 502 can forward the third-party API message to the network device 580. Again, other variations are possible.

[0105] Similarly, for example, to subscribe network device 580 to receive API messages published by a system controller (such as system controller 250a), network device 580 can communicate with gateway 502 via communication connection 508 to subscribe to the MAC address of system controller 250a. Upon receiving the subscription request, gateway 502 can forward the request to corresponding API translator 504 via corresponding connection 510, and then the API translator can forward the request to network service 342 via corresponding connection 512 to translate the request if necessary. Alternatively, gateway 502 can forward the subscription request directly to the network service. Regardless, for example, the operational flow can then be similar to that described with respect to Figure 3 As discussed herein. When the network service 342 receives API messages published by the system controller 250a from the data aggregator 310 via the connection 334, the network service can determine that the network device (such as the network device 580) has subscribed to receive these API messages as discussed herein. The network service 342 can then forward these API messages (e.g., with their associated topics and / or MAC addresses) to the corresponding API translator 504 via the corresponding connection 510. Alternatively, the network service 342 can forward these API messages to the worker service 344 (such as through the message queue 348), which can then forward the API messages (e.g., with their associated topics and / or MAC addresses) to the corresponding API translator 504 via the corresponding connection 510. Other variations are also possible. After receiving the API message from the network service 342, the API translator 504 can translate the API message into a third-party API message and forward the third-party API message to the gateway 502 via the corresponding connection 510. Thereafter, the gateway 502 may forward the third party API message to the network device 580. When communicating the third party API message to the network device, the message may include a subject associated with the API message and / or MAC address of the corresponding system controller 250a. Again, other variations are possible.

[0106] As shown above, according to Figure 5In the example shown, gateway 502 and one or more API translators 504 may be specific to a particular third-party API. According to another aspect of system 500, the system may support multiple different third-party APIs. Here, system 500 may include multiple instances / pairs of gateway 502 and one or more API translators 504, wherein each gateway / API translator pair supports a corresponding third-party API. Depending on which API the network device 580 uses, the device may communicate with the corresponding gateway (e.g., each gateway may have a corresponding address / URL with which the network device communicates).

[0107] According to a specific example, one or more of the gateway 502 and the one or more API translators 502 can be provided by Amazon Web Services, where the gateway 502 can be an Amazon API Gateway, and where each respective instance of the API translator can be a respective Lambda function configured to perform API translation as discussed herein and communicate with the network server 340 as discussed herein. Here, the Amazon API Gateway can expose an endpoint to the network device 580, and can assign a Lambda function configured as described herein to a respective gateway endpoint.

[0108] Referring now to yet another aspect of systems 300, 400, and 500, as discussed herein, network server 340 may view / use, for example, the MAC addresses of system controllers 250a and 250b as topics or channels to which network devices 380 and 580 may, for example, subscribe and / or publish messages. Subscription database 346 may include the MAC addresses of the system controllers and may associate this address with one or more of the topics used by system controllers 250a and 250b, as indicated by label 350. Again, this is an example.

[0109] According to another example, authorization / access tokens may also be associated with the respective system controllers 250a and 250b, and these tokens are then associated with one or more of the topics used by the system controllers, wherein the systems 300, 400, and 500 use the tokens in a manner similar to how MAC addresses may be used as described herein. For example, for security purposes, in order for a network device 380 or 580 (i.e., a third party) to communicate with a network server 340 or gateway 502 to obtain access to a user environment 202a or 202b / load control system 210a or 210b, the network device may need to include, for example, an authorization / access token in an HTTP message, which the network server 340 and / or gateway 502 may use to ensure that the network device is allowed to access the user environment 202a or 202b / load control system 210a or 210b. A user of the user environment / load control system (such as a homeowner) may obtain such a token using, for example, an OAuth (e.g., OAuth 2.0) based service. Such a service may be provided separately from the systems 300, 400, and 500. In the process of a user obtaining such a token, the token may be stored, for example, in subscription database 346, and may also be provided to a third party and used by the third party and network server 340 and / or gateway 502 for authentication / authorization purposes.

[0110] In this regard, the authorization tokens may be considered to be associated with the user. According to one aspect of systems 300, 400, and 500, these tokens may also be associated with the system controllers. For example, assume that a user / homeowner of user environment 202a obtains token "XYZ123" through an OAuth-based service, and assume that a user / homeowner of user environment 202b obtains token "XYZ456" through an OAuth-based service. In addition to using these tokens for security purposes, for example, these tokens may also be stored in a subscription database 346 (or alternatively, in another database such as an authorization database, where database 346 has links to the tokens stored in the authorization database) and associated with the respective system controllers 250a and 250b, thereby being associated with one or more of the topics used by the system controllers, such as. Figure 5 As shown in the label 350.

[0111] As about Figure 3As discussed in connection with the system 300 of FIG. 300 , for example, in order for the network device 380 to receive API messages published by the system controller 250a, the network device may subscribe to the MAC address “A1:B1:C1:D1:E1:F1”, as discussed herein. With respect to the authorization token, when the network device 380 communicates an HTTP message to the network server 340 to subscribe to receive API messages from the system controller 250a, the network server 340 may treat / use the authorization token (i.e., “XYZ123”) within the HTTP message as a request to subscribe to the authorization token, wherein the system 300 now uses the token in a manner similar to that in which it uses the MAC address in order to determine that the API message published by the system controller 250a should be forwarded to the network device.

[0112] Similarly, as regards Figure 4 As discussed above with respect to system 400, for example, in order for network device 380 to communicate an API message to system controller 250a, the network device may publish the message to the MAC address of the system controller. With respect to the authorization token, when the network device communicates an HTTP message to a network server to publish an API message to system controller 250a, network server 340 may treat / use the authorization token (i.e., "XYZ123") within the HTTP message as a request to publish the API message to the authorization token, wherein system 400 now uses the token in a manner similar to how it uses the MAC address in order to communicate API messages with system controller 250a.

[0113] Similarly, as regards Figure 5As discussed above with respect to the system 500 of FIG. 5 , for example, in order for the network device 580 to communicate a third-party API message to the system controller 250a, the network device may communicate the MAC address of the system controller to the gateway 502. With respect to the authorization token, when the network device 580 communicates an HTTP message (which includes the third-party API message) to the gateway, the gateway may forward the authorization token (i.e., “XYZ123”) from the HTTP message to the API translator 504, which may translate the third-party API message into an API message. When the API translator 504 communicates the HTTP message to the network server 340 to publish the API message to the system controller 250a, the API translator may include the token in the HTTP message (e.g., for authorization purposes). Thereafter, the network server 340 may treat / use the authorization token (i.e., “XYZ123”) within the HTTP message as a request to publish the API message to the authorization token, wherein the system 500 now uses the token in a manner similar to the manner in which it uses the MAC address for API message communication with the system controller 250a. The authorization token may also be used in a similar manner in system 500 to subscribe network device 580 to receive API messages published by the system controller. Again, other exemplary processing flows are possible.

[0114] In general, it will be appreciated that the functions and operations described herein as message broker 370, data aggregator 310, and network server 340 can each be performed on different computing devices or the same computing device or some combination thereof. One or more of these modules can also be a cloud-based system. Similarly, it will be appreciated that the functions and operations described herein as being performed by message broker 370, data aggregator 310, or network server 340 can be performed by other modules. For example, network server 340 can provide filter 316 instead of data aggregator 310. In addition, although the functions and operations are described herein as being performed by message broker 370, data aggregator 310, and network server 340, the functions and operations can also be performed by other modules. For example, network service 342 and worker service 344 can be distributed on multiple computing devices. Subscription database 346 can be a database management system separate from network server 340, etc. Other variations are also possible.

[0115] Reference now Figures 6A to 6V , an exemplary control application 1103 (which may be executed at least in part on the network device 680) is now described. Fig.12). The network device 680 can be similar to any of the network devices 144, 280a-280b, 380, and 580 as described herein, and can be, for example, a personal computer (PC), a laptop computer, a tablet computer, a smartphone, or an equivalent device, but may also be another type of computing device. The control application can be a graphical user interface (GUI) based application that can provide a GUI-based interface / GUI-based "window" to a user via the network device 680, and can allow a user of the network device to interact with, control, and / or configure control devices within a user environment (such as the control device 220a of the user environment 202a). For illustrative purposes only, the load control system 210a of the user environment 202a and the load control system 210a of the user environment 202a are described in detail. Figures 2 to 5 The described communication system will be used herein as an exemplary load control system and communication system to describe the control application. Nevertheless, the features and functions of the control application 1103 described herein are applicable to other types of control devices, load control systems, and communication systems. As an example, the user environment 202a can be a residence or house, and the user of the network device 680 can be an occupant of the house. Nevertheless, the exemplary control application can also be applicable to other types of user environments, such as buildings, hotels, etc.

[0116] Fig.12An exemplary block diagram of a network device 680 is shown (e.g., this figure may also apply to any of the network devices 144, 280a-280b, 380, and 580). The network device 680 may include one or more general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, microcontrollers, integrated circuits, programmable logic devices (PLDs), application specific integrated circuits (ASICs), etc., and / or may also include one or more other processing elements, such as one or more graphics processors (hereinafter collectively referred to as one or more processors 1102). The one or more processors 1102 may control the functionality of the network device and may execute control applications 1103 in addition to executing other software applications such as one or more operating systems, database management systems, etc. to provide features and functions as described herein. The one or more processors 1102 may also perform signal encoding, data processing, power control, input / output processing, and / or any other functionality that enables the network device 680 to perform as described herein. The network device 680 may also include one or more memory modules / devices 1104 (including volatile and non-volatile memory modules / devices), which may be non-removable memory modules / devices and / or removable memory modules / devices. The memory modules / devices 1104 may be communicatively coupled to the one or more processors 1102. The non-removable memory modules / devices 1104 may include random access memory (RAM), read-only memory (ROM), one or more hard disks, or any other type of non-removable memory storage device. The removable memory modules / devices 1104 may include a subscriber identity module (SIM) card, a memory stick, a memory card, or any other type of removable memory. The one or more memory modules / devices 1104 may store the control application 1103 and may also provide execution space when the one or more processors execute the control application. The network device 680 may also include one or more visual display screens / one or more terminals 1106, which may be communicatively coupled to the one or more processors 1102. The one or more visual display screens 1106 can work with the one or more processors 1102 to display information to a user via one or more GUI-based interfaces / GUI-based "windows" as described herein. The one or more display screens 1106 and the one or more processors 1102 can communicate bi-directionally, as the display screens 1106 can include a touch-sensitive visual screen module configured to receive information from a user and provide such information to the one or more processors 1102.The network device 680 may also include one or more input / output (I / O) devices 1112 (e.g., keyboard, touch-sensitive pad, mouse, trackball, audio speaker, audio receiver, etc.) that can be communicatively coupled to the one or more processors 1102. For example, the I / O device can allow a user to interact with the control application 1103. The network device 680 may also include, for example, one or more transceivers / communication circuits (collectively referred to as one or more communication circuits 1108) for communicating (transmitting and / or receiving) via a wired and / or wireless communication network. The one or more communication circuits 1108 may include one or more RF transceivers or one or more other circuits configured to perform wireless communication via one or more antennas. The one or more communication circuits 1108 may communicate with the one or more processors 1102 to transmit and / or receive information. Each of the modules within the network device 680 may be powered by a power supply 1110. The power supply 1110 may include, for example, an AC power supply and / or a DC power supply. The power supply 1110 may generate a supply voltage V for powering the modules within the network device 680. CC .

[0117] In addition to including, for example, GUI-based software modules that provide graphical features and visual images described herein, the control application 1103 may also include one or more logic engines for providing features of the GUI and features of the application as generally described herein. The GUI-based software modules and / or logic engines may be one or more software-based modules that include, for example, instructions that are stored on and / or executed from one or more tangible memory devices / modules of the network device as shown above. The features of the control application may also and / or alternatively be provided by firmware and / or hardware that is a supplement to / as a replacement for the software-based modules. Again, the network device 680 is an example, and the control application may be executed on other types of computing devices.

[0118] As shown, the network device 680 can be similar to any of the network devices 144, 280a-280b, 380, and 580 as described herein. Accordingly, the control application can communicate with the system controller 250a of the user environment 202a via a network (such as a Wi-Fi network) local to the user environment similar to the device 144 as described herein, can communicate with the system controller 250a using a message-based protocol (e.g., MQTT) and a message broker (e.g., message broker 270) similar to the network devices 280a-280b as described herein, and / or can communicate with the system controller 250a using an HTTP-based interface similar to the network device 380 and / or the network device 580 as described herein. Nevertheless, it will be appreciated that the control application 1103 / network device 680 can communicate with the system controller 250a using other communication systems and / or protocols, etc. In addition, the control application 1103 is described herein as a stand-alone application, for example, which executes on a network device and communicates messages with the system controller 250a. In other words, the logic of the control application and the generated graphics associated with the application are described herein as being executed from a network device. Nevertheless, the features and / or graphics of the control application can be implemented in other ways, such as a network-hosted application, where the network device uses a local application (e.g., a web browser or other application) to interface with the network-hosted application to provide the features and functionality described herein.

[0119] In general, for example, while the user environment 202a may include control devices 220a that the control application / network device 680 may interact with, control, and / or configure via the system controller 250a, the user environment may also include other types of control devices (e.g., devices configured to communicate via wireless and / or wired-based networks) that may be, for example, Wi-Fi-enabled and / or HomeKit-enabled control devices. For descriptive purposes only, such other control devices (i.e., control devices with which the control application / network device 680 does not communicate via the system controller) will be referred to herein as Wi-Fi-enabled and / or HomeKit-enabled control devices. Nevertheless, it will be appreciated that the features described herein are not limited to Wi-Fi-enabled and / or HomeKit-enabled control devices. Examples of such other control devices may include lighting control devices / bulbs, thermostats, fans, etc. For example, the network device 680 and these Wi-Fi enabled control devices can be configured to communicate directly with each other without having to communicate through the system controller 250a (e.g., if the network device is also HomeKit enabled), and / or can communicate, for example, via one or more cloud-based servers, and also without having to communicate through the system controller 250a. According to one aspect of the control application 1103 described herein, assuming that the network device is configured to communicate with such Wi-Fi enabled control devices (e.g., via HomeKit), the control application can be configured to interact with these devices in addition to the control device 220a, control these devices and / or configure these devices. In doing so, the control application can combine information obtained, for example, from such Wi-Fi enabled devices with information obtained on the control device 220a controlled by the system controller 250a within the graphical interface described herein. The control application can also provide an interface that allows a user to control both, for example, a Wi-Fi enabled control device and a control device 220a controlled by the system controller. For ease of description, the control application is described herein as interacting with the control device 220a of the load control system 210a. However, similar functionality as described herein may also be applicable to Wi-Fi enabled devices that are not controlled by the system controller 250a and with which the network device may communicate directly and / or indirectly. The type of device with which the control application interacts may not be obvious to the user. It will also be appreciated that the control application described herein may alternatively only control Wi-Fi enabled devices that, for example, the network device is configured to directly and / or indirectly control / interact with. Further, it will be appreciated that although the control application described herein may be used in conjunction with the load control system 210a and the communication system (such as the reference Figures 2 to 5The control application 1103 is described in the context of those described in the examples above, but the features and functionality of the control application are applicable to other types of control devices, load control systems, and communication systems, including, for example, Wi-Fi enabled and / or HomeKit enabled systems.

[0120] As one example, the network device 680 may display an icon associated with a control application to a user via a visual display screen. The network device may detect a user selection of the icon (such as detecting a touch of the icon), and in response, may start (also referred to herein as launching, running, executing, activating, and / or invoking) the control application (it will be appreciated that the control application may be started in other ways, including configuring the network device to automatically start the application upon reset and / or power-up). In response to starting or launching, the control application (e.g., in addition to performing security / authentication procedures) may, for example, communicate one or more messages to the system controller 250a to obtain / request / query various information, such as the status / state and / or configuration information of the load control system 210a, and use this information to initially generate a graphical user interface (such as a graphical user interface). Fig. 6A The control application may also communicate with the system controller 250a, for example, at the beginning, for example, and with a Wi-Fi enabled device with which the network device has been configured to communicate. Thereafter, the control application may continue to request and / or receive various information from the system controller 250a at various times, depending on the information that the control application may need to display to the user and / or the information generated by the system controller. (Again, the control application may also communicate with the Wi-Fi enabled device in a similar manner.) Upon receiving a request for information (such as a request for status and configuration information) from the control application, the system controller 250a may respond by, for example, communicating with the control device 210a and / or the database 254 to determine and provide the requested information and respond to the control application with one or more response messages. For example, in addition to determining the status and configuration of the load control system, the control application may also allow the user to communicate a message to the system controller 250a to modify, edit, or change the configuration and / or state of the load control system 250a, as further described herein. Additionally, the system controller 250a may also provide status and configuration information to the control application asynchronously (e.g., providing an indication of a change in the status / state of the control device without requiring the control application to query such changes). The control application may use this information to update various graphical user interfaces displayed to the user via the network device 680. (Again, the Wi-Fi enabled device and the control application / network device may interact in a similar manner.) Again, the control application / network device 680 and the system controller 250a may use the same graphical user interfaces as described above with reference to FIG. Figures 2 to 5 The mechanism in question communicates.

[0121] Before moving to the various graphical user interfaces, the control application may provide the user with a description of exemplary types of information that the control application may request / receive, for example, from the system controller 250a to produce the interface discussed first. It will be appreciated that these are examples and that other types of information may also be provided. In addition to receiving such information from the system controller, the control application may also modify such information at the system controller, as described below.

[0122] The control application may request / obtain information from the system controller 250a regarding the configuration and current state / condition of the load control system 210a. Such information provided by the system controller 250a may include specific control devices that are part of the load control system 210a, including identifiers indicating the type of the control devices. The specific control device types may include: one or more lighting control devices (also referred to herein as lighting devices), each lighting control device directly controlling one or more corresponding electrical lighting loads / lamps; one or more temperature control devices (such as and also referred to hereinafter as one or more thermostat devices), which directly control corresponding HVAC systems; one or more ceiling fan devices (also referred to herein as fan devices), each ceiling fan device directly controlling one or more corresponding fans (e.g., on, off, fan speed); one or more audio control devices (e.g., speaker systems); and one or more window shade devices, each window shade device directly controlling the position or level of one or more corresponding shades (it will be recognized that although shade devices and shades are discussed herein as examples of motorized window treatments and window coverings, other types of motorized window treatments and window coverings are possible, such as drapes, curtains, blinds, etc.). The control device may also include one or more keypads, such as a wall mounted keypad, a desktop keypad, and / or a remote control / handheld keypad and device. As an example, a given keypad may include one or more actuators, such as buttons (although other types of actuators are possible), and may be configured to control one or more control devices / electrical loads (e.g., a lighting control device / one or more lighting loads, one or more HVAC systems, one or more window shades, one or more fans, and / or one or more speakers, etc.). In general, a keypad may include different types of actuators, such as an on / off actuator, a lift actuator for a light or window shade, a fan speed actuator, a scene actuator, etc. A scene actuator may set one or more control devices / electrical loads controlled by the keypad to a preset configuration.

[0123] The control device may also include one or more occupancy / vacancy sensors and / or one or more vacancy-only sensors. As an example, an occupancy / vacancy sensor may signal detected occupancy events / conditions and detected vacancy events / conditions (e.g., after an occupancy event is detected) to other control devices. When the sensor detects an occupancy event, the sensor may signal these events by generating one or more occupancy signals / messages, when the sensor detects a persistent occupancy event, the sensor may signal these events by generating one or more periodic occupancy signals / messages, and / or when the sensor detects a vacancy event (e.g., after an occupancy event is detected), the sensor may signal these events by generating one or more vacancy signals / messages. As another example, the sensor may signal a vacancy event by stopping generating one or more periodic occupancy signals / messages. A vacancy-only sensor may signal detected vacancy events / conditions (e.g., after an occupancy event is detected) to other control devices. When the sensor detects a vacancy event (e.g., after an occupancy event is detected), it may signal these events by generating one or more vacancy signals / messages. In this example, when the sensor detects an occupancy event, the sensor may still generate one or more signals / messages, but the control device may not respond to such signals. As another example, a vacancy-only sensor can signal a vacancy event by stopping generating one or more periodic occupancy signals / messages. It will be appreciated that these are examples and that the sensor can operate in other ways based on the detected occupancy / vacancy events. It will also be appreciated that when the sensor detects occupancy and / or vacancy events, it can communicate these events in various ways, such as communicating signals or messages, etc. Such signals, etc. can be communicated via wireless communication, wired communication, optical communication, etc. Other examples are also possible. For ease of description, occupancy / vacancy sensors and vacancy-only sensors are collectively referred to as occupancy sensors in this article, and the sensors are referred to as generating signals when occupancy and / or vacancy events are detected.

[0124] The load control system 210a can be configured so that one or more control devices 220a can respond to signals from a given occupancy sensor (e.g., respond to occupancy and / or vacancy events detected by the sensor). For example, the load control system 210a can be configured so that one or more lighting control devices can respond to occupancy and vacancy signals from a given occupancy sensor. For example, in response to an occupancy signal from an occupancy sensor, a given lighting control device that is turned off (i.e., one or more corresponding lighting loads are in the off state) can turn on one or more corresponding lighting loads, and specifically, one or more lighting loads can be set to one or more defined lighting / dimming levels. In response to a vacancy signal, a given lighting control device (when turned on) can turn off one or more corresponding lighting loads or can reduce one or more lighting levels to one or more defined lighting / dimming levels. As another example, the load control system 210a can be configured so that one or more lighting control devices can respond only to occupancy signals from a given occupancy sensor. As another example, the load control system 210a can be configured so that one or more lighting control devices can respond only to vacancy signals from a given occupancy sensor. For example, in response to an occupancy signal from an occupancy sensor, a given lighting control device may ignore the signal. In response to a vacancy signal, a given lighting control device (when turned on) may turn off one or more of its corresponding lighting loads or may reduce one or more of its lighting levels to one or more defined lighting / dimming levels. The manner in which a given lighting control device responds to an occupancy and / or vacancy signal from a given occupancy sensor may, for example, be stored at the sensor and communicated to the lighting control device as part of the signal, may be stored at the lighting control device itself, and / or may be stored at the system controller 250a, which may receive occupancy and vacancy signals and may subsequently control the lighting control device. It will be appreciated that a given lighting control device may respond to signals from more than one occupancy sensor. Similarly, multiple lighting control devices may respond to signals from the same occupancy sensor and may each be configured to react to the signal in a different manner. It will also be appreciated that the load control system 210a may be configured so that other control devices (e.g., fan devices, shade devices, thermostat devices, and audio devices, etc.) may respond to occupancy and / or vacancy signals from one or more occupancy sensors. Generally speaking, an occupancy sensor can be a stand-alone device, that is, a device separate from a control device (such as a lighting control device) that can respond to the signal generated by the sensor. As another example, an occupancy sensor can be integrated with another control device (such as a lighting control device).The control device in which the sensor is integrated may respond to the signal generated by the sensor, and / or a control device separate from the control device in which the sensor is integrated may respond to the signal generated by the sensor. It will be appreciated that other examples are possible. It will be appreciated that the load control system 210a may include other types of control devices.

[0125] The information provided by the system controller 250a may also include a location indicator for each control device, which may indicate the location of the device within the user environment 202a and / or the location of the electrical load controlled by the device. This indicator may be in the form of a location name (e.g., a text string) and / or an indicator that can be translated into a location name (e.g., a text string), but other mechanisms may also be used. For example, assuming that the user environment is a house, possible locations may include standard locations such as "kitchen", "living room", "family activity room", "dining room", "master bedroom", "bedroom", "master bathroom", "bathroom", "basement", "front porch", etc. Locations may also include secondary locations in a room, such as "basement - lounge area", "basement - play area", "basement - work area", "basement - storage area", etc. Locations may also include user-defined / customized locations, such as: "Mary's bedroom", "John's bedroom", etc. When the load control system 210a is installed within the user environment 202a, the user may program the location of the control device into the system (and, for example, store it in the database 254). It will be appreciated that these are examples.

[0126] For lighting control devices, the information provided by the system controller 250a may also include a type indicator, which may indicate the type of one or more lighting loads (also referred to herein as one or more lamps) controlled by the control device. The type of the lighting load may include, for example, the function / purpose of the lighting load within its defined location, and / or indicate / suggest a specific location of the lighting load within its defined location (e.g., ceiling lamp vs. floor lamp). The type indicator may be in the form of a name / function (e.g., a text string) and / or an indicator that can be translated into a name / function (e.g., a text string), but other mechanisms may also be used. As an example, assuming that the user environment 202a is a house, the standard types may include ceiling lamps or ceiling lamps, chandeliers, one or more chandeliers, one or more table lamps, one or more floor lamps, one or more wall lamps, one or more sink lamps (e.g., for kitchens or bathrooms), one or more bar lamps (e.g., for kitchens), one or more closet lamps, etc. The type may also include a user-defined / customized type. When the load control system 210a is installed in the user environment 202a, the user may program the type of the lighting load into the system (and, for example, store it in the database 254). It will be appreciated that these are examples. Types may also apply to other control devices, such as fans, shades, and keypads. Again, the type indicator may provide an indication of a specific function and / or location within a defined location of the device. Other exemplary types may include "left shade", "right shade", "center shade", "wall keypad", "desktop keypad", etc.

[0127] The information provided by the system controller 250a may also include an indication of an icon to be used with an application (such as a control application) to graphically represent the control device on a graphical interface. When the load control system 210a is installed within the user environment 202a, the type of icon used to associate with the device may be programmed into the system (and stored, for example, in the database 254) by the user or automatically.

[0128] The information provided by the system controller 250a may also include the current status / state and / or configuration of one or more of the control devices. For example, for a lighting control device, the status information may include whether one or more corresponding lighting loads are in an on state or an off state, and if in an on state, whether they are in a dimmed state and possibly also the dimming level. For a window shade device, the status information may include whether one or more corresponding window shades are open / retracted, closed / lowered, partially open / retracted, and if partially open / retracted, their actual level. For a thermostat device and its corresponding HVAC system, the status information may include the set point / target temperature of the system, the current room temperature measured by the thermostat device, the current mode setting (e.g., heating, cooling, automatic, off), the current fan setting (e.g., on, automatic), and schedule information (e.g., on vs. off, assuming the thermostat device is programmable with a schedule). For a ceiling fan device, the status information may include whether one or more corresponding fans are in an on state or an off state, and if in an on state, possibly including the fan speed. For audio control devices (e.g., speaker systems), the status information may include whether the device is, for example, on / playing music, or off and / or muted. For keypad devices such as wall-mounted, desktop, and / or handheld / remote keypads, the status information may include which actuator of the device was last actuated (i.e., currently activated), and if the keypad has one or more actuators corresponding to scenes, the configuration of each scene (e.g., which control devices are part of the scene, the settings of these devices for the scene (such as light level or fan speed), etc.). The control application may allow the user to modify these scenes and create new scenes via the network device. For occupancy sensors, the status information may include, for example, whether the sensor has detected an occupancy event / condition and / or is in an occupied state, whether it has detected a continuous occupancy event / condition and / or is in a continuous occupancy state, and / or whether it has detected a vacancy condition and / or is in a vacancy state. Again, these are examples and other information is possible.

[0129] As another example, the system controller 250a may maintain information regarding one or more pre-programmed scenes that may be actuated by a user from an application such as the control application 1103. A scene may be, for example, certain settings of one or more lights, shades, etc. The system controller 250a may maintain corresponding scene configuration information in a database 254. The control application may obtain information regarding these pre-programmed scenes from the system controller and, as further described below, thereafter allow a user to select a given scene via a network device, thereby generating control application instructions for the system controller to configure the control device 220a according to the selected scene (e.g., to set one or more light levels, fan speeds, shade levels, etc.). As also described below, the control application may allow a user to modify the pre-programmed scenes maintained by the system controller and create and store new scenes at the system controller that may subsequently be selected by a user.

[0130] As yet another example, the system controller 250a may maintain various clock schedules, where a schedule may be, for example, a certain setting of one or more control devices (e.g., lights, shades, etc.) that the system controller automatically configures based on the schedule. The system controller 250a may maintain corresponding clock schedules and the status of these schedules, such as whether a given schedule is active, inactive, or disabled, in the database 254. The control application may obtain control information related to these clock schedules from the system and, as further described below, thereafter allow the user to modify these schedules and create new schedules via the network device.

[0131] Now go to Fig. 6A, which shows a graphical user interface 610 that can be initially displayed to a user by a control application via a network device 680 when the application is initially started (such as by the user selecting and starting the application at the network device). Again, the information displayed in the user interface 610 can be based on information obtained by the control application from the system controller 250a after starting the application. The user interface 610 can include three sections (which may also be referred to herein as panes or areas or spaces), including a status section (or pane) 620, a menu selection section (also referred to herein as a menu selection pane, a tab section or a tab pane) 640, and an information section (or pane) 660. As further described below, the status section 620 can provide the user with the status / state of the control device 220a within the load control system 210a. The menu selection section 640 can provide the user with selectable tabs (three tabs are shown here, including a "device" tab 642, a "scenario" tab 644, and a "schedule" tab 646, but the section can include fewer or additional tabs, including three tabs in a different order than shown). For example, section 640 may be scrollable, for example, left or right, to display additional tabs. The control application may change and / or display information in section 660 depending on which tab is selected, and thus, section 660 may depend on the selected tab. In general, information section 660 may provide the user with different status information and controls for controlling and / or configuring load control system 210a. Fig. 6A In the example shown in FIG. 6 , the device tab 642 is active (as indicated by underline 643, but other means, such as reverse highlighting, etc., may be used to indicate which tab is currently active). Here, section 660 shows information corresponding to the device tab 642. When the control application starts, it may default the user interface 610 to the device tab 642 being active, but one of the other tabs may also be the default active tab.

[0132] Beginning with section 620, as shown, this section may display the status / state of one or more control devices 220a within the load control system 210a. In this example, the control application displays three icons, each indicating different status information. Icon 622 may be referred to herein as a lighting device icon, which indicates to the user the number of lighting control devices whose corresponding lighting loads within the load control system are currently turned on. Icon 624 may be referred to herein as a window shade device icon, which indicates to the user the number of window shade devices whose corresponding window shades within the load control system are currently opened / retracted (where open / retracted may be any window shade state other than fully closed / down). Icon 626 may be referred to herein as a thermostat device icon, which indicates to the user the current temperature in the user environment 202a. It will be appreciated that in section 620, the control application may display fewer and / or additional icons that convey additional and / or other information to the user. For example, Figure 6B Another exemplary graphical user interface 601 is shown that includes icons 628, which may be referred to herein as audio device icons, which may indicate to a user the status of audio devices within the load control system, such as whether any audio devices are currently turned on / playing music and / or the number of devices that are currently turned on / playing music. The control application may be configured such that section 620 may be "scrolled" (e.g., left to right or up and down) by the user to display additional icons. As another example, section 620 may be configured such that multiple rows of icons are displayed to the user at one time. As another example, section 620 may include icons such as Figure 6L An icon, referred to herein as fan icon 776, is shown, which can indicate to the user the status of the fan devices within the load control system, such as the number of fans currently turned on. Section 620 can also be configured by the user of the application so that only certain icons and corresponding status information are displayed to the user, while other icons and corresponding status information are not displayed. According to another example, if there is no status report for a given load control device (such as all lighting devices are off), the control application may not display the corresponding icon at all. Other examples are also possible. Reference will now be made in more detail to representative icons that can be displayed by the control application in section 620.

[0133] Beginning with icon 622, as shown, it may be a lighting device icon that indicates to the user the number of lighting control devices whose corresponding lighting loads within the load control system 210a are currently turned on. The control application may determine this number based on information obtained from the system controller 250a. A given lighting control device may control more than one lighting load, and may control these loads in unison (or may control these loads separately to different states). According to one example, the control application may treat a given lighting control device and its corresponding lighting load as one device. In this example, as long as one lighting load controlled by the lighting control device is in the on state, the control application may count this as one (1) with respect to the number associated with icon 622, regardless of the number of controlled loads that are actually controlled by the device (and may actually be turned on). Nonetheless, it will be appreciated that the number associated with icon 622 may represent the actual number of lighting loads controlled by each lighting control device. Here, the control application may view each lighting load controlled by a given lighting control device separately. In this example, the number associated with icon 622 may represent each lighting load. Thus, if two lighting loads controlled by the lighting control device are in the on state, the control application may count this as two (2) with respect to icon 622. For descriptive purposes, the control application is described herein from the perspective of the lighting control device, where the lighting control device and its corresponding lighting loads are considered a single unit. Fig. 6A In this example of FIG. 250 , the control application has determined that eight lighting control devices have loads currently turned on (where turned on may include the lighting loads being in a dimmed state and / or a fully turned on state) based on information received from system controller 250 a. The control application may Fig. 6AThe displayed number "8" shown associated with icon 622 indicates this determination to the user (although it will be appreciated that other variations are possible, such as displaying the word "eight" or a symbol representing 8 (such as 8 dots), etc.). As one example, the control application may actually perform a count to determine the number 8 based on information received from the system controller (e.g., searching a list of lighting control devices and determining how many lighting control devices are in an on state), or the system controller may perform the count and report the resulting value to the control application. Other variations are also possible. In addition to displaying the number of lighting control devices determined to be currently on (i.e., having at least one of their corresponding lighting loads turned on), the control application may actively update (increase / decrease) the number displayed by icon 622 based on, for example, system controller 250a actively monitoring the on / off state of lighting control devices in the user's environment (e.g., due to users in the environment turning lights on and off) and asynchronously reporting (such as in "real time" or when a state change event occurs) this information to the control application. As another alternative, the control application may periodically request the status of the lighting control devices and / or lighting loads from the system controller 250a after startup, and update the number displayed by the icon 622 based on the response from the system controller 250a. In this way, the icon 622 allows the user to quickly and easily determine from the network device 680 whether any lighting loads in the user's environment are turned on. If it is determined that no lighting loads are currently turned on, the control application may use the icon 622 to display the value "0", may use the icon to not display any value, may not display the icon at all (thereby indicating that no lighting control devices are turned on, etc.). Other variations are also possible. For example, instead of displaying a number with the icon 622, the control application may display the icon when any lighting load is turned on, and not display the icon when all lighting loads are turned off. As yet another example, the icon 622 may indicate the number of lighting control devices that have caused the corresponding lighting load to be in the off state.

[0134] Icon 622 can also be selected by the user. When detecting / determining that the user has selected icon 622, the control application can display the following to the user via network device 680: Figure 6C702 is shown. Interface 702 can continue to display icon 622 and the number of lighting control devices that have at least one lighting load determined to be currently turned on. Interface 702 can also include a "turn off all lights" icon 704 that can be selected by the user (although other text and / or icons can also be used). Interface 702 can also include a corresponding icon 706 for each lighting control device that has a lighting load that is currently turned on (again, according to this example, the control application can be configured to treat the lighting control device and its one or more corresponding lighting loads as a unit, thereby uniformly representing the unit as an icon. As an alternative, each lighting load controlled by the lighting control device can be represented by an icon in interface 702 or some combination thereof). Each of these icons can also be selected by the user. In this example, eight icons 706 are shown in conjunction with the value "8" shown as icon 622. The control application can use the location indicators associated with each lighting control device to display with each icon an indication of the location of the corresponding device / lighting load in the user's environment (in this example, text information such as "Kitchen", "Living Room", "Front Porch" and "Master Bedroom" is used, but other mechanisms are possible, such as separating icons by location, similar to Fig. 6A The control application may also use a type indicator associated with each lighting control device in conjunction with each icon to display further indication of the location and / or function of the device / lighting load (in this example, text information such as "ceiling light", "chandelier", "sink light", "wall light", and "desk light" is used, but other mechanisms are possible). Figure 6C As further shown, different icons may be used for various lighting control devices / lighting loads (here, exemplary icons representing pendant lights, table lamps, wall lamps, and light bulbs are used, and other icons are possible). As shown, the system controller may provide an indication of the type of icon that the control application should use. As another example, the control application may use a location indicator and / or a type indicator associated with each lighting control device, for example, to determine which icon to use. In general, the control application's use of textual information and customized icons allows the user to more easily determine the actual lighting control device / lamp in the user's environment to which the icon refers.

[0135] According to another aspect of interface 702, in a manner similar to the control application actively updating the number displayed by icon 622, e.g., based on system controller 250a actively monitoring the status of lighting control devices in the user's environment, the control application can actively update icon 706 displayed to the user when a lighting control device in the user's environment changes state from on to off or from off to on (i.e., when a lighting load controlled by the device changes state). In other words, when a lighting control device turns on one or more of its corresponding lighting loads (e.g., at least one of the loads), the control application can receive an indication of this change from system controller 250a (e.g., automatically or in response to a query by the control application) and (in addition to increasing the number associated with icon 622) display an additional icon 706 associated with the lighting control device to the user in interface 702. Similarly, when a lighting control device turns off all of its corresponding lighting loads, the control application can receive an indication of this change from system controller 250a and (in addition to decreasing the number associated with icon 622) remove icon 706 associated with the lighting control device from interface 702. As another example, the control application may change the appearance of an icon (e.g., changing its color or contrast compared to other icons) to indicate closing, rather than removing the icon from interface 702. If interface 702 is subsequently closed, and then returned to by the user, the control application may now not display the icon. Other variations are also possible.

[0136] Turning now to icon 704, as shown, this icon can be selected by the user and can allow the user to turn off all lighting control devices, thereby turning off the lighting loads currently turned on in the load control system 210a. Upon detecting / determining that the user has selected the icon, the control application can communicate one or more messages to the system controller 250a, thereby instructing the system controller to turn off all lighting control devices / lights. Once completed, the system controller 250a can provide a response to the control application (e.g., automatically or in response to a query), thereby indicating that the lighting control devices are now turned off. In response, the control application can, for example, change the number associated with the icon 622 to "0" (or, for example, not display any value), and, for example, remove all icons 704 from the interface 702 or change the appearance of the icons. Since all lighting control devices / lights are turned off, the control application can also deactivate the icon 704 (where deactivation can include making the icon unselectable by the user and / or changing the appearance of the icon 704 (such as by changing its color or contrast compared to other icons), removing the icon from the interface 702, etc.). Once a lighting control device is returned to the on state (such as by a user in user environment 202a turning on a light), in addition to, for example, incrementing the number associated with icon 622 to "1" and displaying icon 704 representing the lighting control device in interface 702, the control application may also activate / reactivate icon 704 (where activating an icon may include making the icon selectable by the user and / or changing the appearance of icon 704 (such as by changing its color or contrast compared to other icons), displaying the icon in interface 702, etc.). It will be appreciated that other examples are possible, such as interface 702 also / alternatively including a "turn all lights on" icon, which, once selected, may cause the control application to communicate one or more messages to the system controller to turn all lights in the user environment to the on state (or turn a set of preprogrammed lights to the on state). Again, such an action by the user may cause the control application to increment the number associated with icon 622 and display a corresponding icon 706 accordingly. As an alternative and / or in addition to selecting icon 704, icon 706 may also be selected by the user and allow the user to respectively control the lighting control device, and therefore the lamp / lighting load associated with the icon (it will be appreciated that, as an alternative, if the control application is configured to display icon 706 in a manner indicating that the corresponding lighting control device is off, the icon may continue to be selectable by the user to also control the device). Upon detecting / determining that the user has selected a given icon in icons 706, the control application may display an interface for controlling the corresponding device to the user.

[0137] For example, assuming the control application detects / determines that the user has selected the icon 706 labeled "kitchen ceiling light," the control application may display Fig.6D 708 is shown (in this example, all lights as a whole are controlled to a common state). For example, control interface 708 may be shown separately or superimposed on interface 702. It will be appreciated that control interface 708 is an example and other controls are possible. The control application may determine whether the "kitchen ceiling light" is configured as a dimmable light or is only configured as an on / off light, etc. based on information provided by the system controller (e.g., from the type indicator), and based on this determination, an appropriate control interface may be displayed. In this example, the "kitchen ceiling light" may be configured as a dimmable light, and therefore, the control application may display a control interface 708 having a movable / slidable actuator 710 (e.g., a vertically movable actuator) that may be actuated / moved by a user. As in this example, the control application may initially display actuator 710 to provide the user with an indication of the current dimming state of the light (e.g., the actuator is approximately midway along its possible path). Based on detecting that the user moves the actuator 710 (such as to raise or lower the intensity of the light, turn the light off, etc.), the control application can communicate one or more messages to the system controller 250a to instruct the controller to reconfigure the lighting control device / light based on the user's instructions. If the user turns off the light, such as by moving the actuator 710 to its lowest position at 709, as similarly discussed above, this update can be reflected in the icon 622 (e.g., decreasing the number) and interface 702 by removing or changing the appearance of the icon 706 corresponding to the "kitchen ceiling light". Fig.6D As shown, the control interface 708 may also include an optional "edit" icon 712, which, when selected, may cause the control application to display a user interface that allows the user to reconfigure the corresponding lighting control device / light (here, "kitchen ceiling light"). Fig. 6E, shows an exemplary configuration interface 790 that the control application may display to the user upon detecting selection of the “Edit” icon 712. The interface 790 may include a field 791 and / or an actuator / icon 791′ configured to enable the user to change a type indicator (here, “ceiling light”) associated with the lighting control device (e.g., via an order menu defining the type obtained via actuation of the actuator 791′, free text field 791, etc.). The interface may also include an actuator / icon 792 configured to enable the user to change a location indicator (here, “kitchen”) associated with the lighting control device (e.g., via a drop-down menu defining the location obtained via actuation of the actuator 792). The interface 790 may include an actuator / icon 793 configured to enable the user to change an icon associated with the lighting control device / light (e.g., via a drop-down menu defining the icon obtained via actuation of the actuator 793). The interface may include an actuator / icon 794 configured to enable a user to adjust or configure a trim level of the lighting control device / lamp, such as a low-end trim level (e.g., a minimum light level to which one or more lamps can be controlled) and / or a high-end trim level (e.g., a maximum light level to which one or more lamps can be controlled) (e.g., via a drop-down menu defining the trim level obtained via actuation of actuator 794). Interface 790 may include an actuator / icon 795 configured to enable a user to adjust or configure whether the lighting control device controls the dimming level of its one or more corresponding lamps via forward phase dimming or reverse phase dimming (e.g., via a drop-down menu obtained via actuation of actuator 795). Further, the control application may display editable features of the lighting control device (such as trim and phase) based on a determination that the lighting control device controls one or more dimmable lamps. The interface may also include a "delete device" icon 796. Actuation of this icon 796 may cause the control application to instruct the system controller to remove the lighting control device from the load control system. Assuming that the user makes changes to the lighting control device via interface 790, once completed, the user can select "Save" or "Cancel" as shown in the interface (although other mechanisms can also be used) to return to the control interface 708, for example, and save or not save the changes / configuration. Any saved changes made by the user regarding the editing of the lighting control device can be communicated by the control application to the system controller, which can then reconfigure the lighting control device accordingly. It will be recognized that the control interface 708 and configuration interface 790 are examples, and other controls are also possible. The user can exit the interface 708 by touching an area of ​​the display screen of the network device 680 outside of the control interface 708. Other examples are also possible.

[0138] As another example of a control interface for controlling a lighting control device, assume that interface 702 includes an icon 706 for a table lamp in a master bedroom, the icon is labeled "Master bedroom master reading light", and the control application detects / determines that the user has selected this icon 706 from interface 702. In response, the control application may display Fig. 10A 21. The exemplary control interface 2100 shown. It will again be appreciated that the control interface 2100 is an example and that other control interfaces are possible. It will also be appreciated that the control interface 2100 can be displayed to the user in response to other actions made by the user via other interfaces and / or in response to other determinations made by the control application and / or the system controller. The control application can determine, based on information provided by the system controller (e.g., from the type indicator), whether the "Master Bedroom Master Reading Light" table lamp is configured as a dimmable lighting load or is configured only as an on / off lighting load, etc., and based on that determination, an appropriate control interface can be displayed. In this example, the "Master Bedroom Master Reading Light" table lamp can be configured as a dimmable lighting load, and therefore, the control application can display the control interface 2100 to provide dimming control. According to this example, the control interface 2100 may include an actuator 2102 (e.g., which may be referred to as a dimming actuator herein) that is movable / slidable (e.g., vertically movable) along a control line 2108c, an increase actuator 2104a, a decrease actuator 2104b, and an on / off actuator 2106.

[0139] As shown in this example, starting with actuator 2106, it can be displayed as an icon similar to the icon shown in interface 702, but it will be appreciated that other icons and / or controls can be used. Actuator 2106 can be selected by a user to turn the lighting control device on and off (and therefore turn one or more corresponding lights / lighting loads on and off). According to one example, the control application can display the appearance of actuator 2106 differently (e.g., change the color or contrast of the icon) based on the on / off state of the lighting load. For example, Fig. 10A and Fig. 10C An example of using reverse contrast to show on / off state is shown (as discussed below), where Fig. 10A Actuator 2106 is shown in a state indicating that the lighting load is on, and Fig. 10C The actuator 2106 is shown in a state indicating that the lighting load is off. It will be appreciated that other examples are possible.

[0140] Turning to the actuator 2102, it can be an actuator that is movable / slidable along the control line 2108c (e.g., vertically movable, but it will be appreciated that the actuator 2102 can alternatively be, for example, horizontally movable) and allows a user to increase the intensity / intensity level or brightness of the lighting load (e.g., by moving the actuator vertically upward toward position 2108a) or decrease the intensity of the lighting load (e.g., by moving the actuator vertically downward toward position 2108b). The actuator 2102 can allow the user to control the intensity of the lighting load from a maximum intensity (position 2108a), such as 100%, to a minimum intensity, which can be 0% (position 2108b), and thereby it can turn off the lighting load. In other words, moving the actuator 2102 to position 2108b can turn off the lighting load. The control application can display the position of the actuator 2102 along the control line 2108c to indicate the current relative intensity of the lighting load. The control application may also display an indicator 2109 with the actuator 2106 that numerically represents the current intensity of the lighting load, shown here as a numerical percentage value of 70%, although other exemplary numerical representations may be used. As an example, the value of the indicator 2109 may vary between 0% and 100%, with 0% representing off. The control application may also dynamically change the value of the indicator 2109 as the user moves the actuator 2102 vertically up and down. Fig. 10A As shown, the portion of the control line 2108c located below the actuator 2102 can be shown with a different intensity or line thickness (here, greater intensity / line thickness) than the portion of the control line 2108c located above the actuator 2102.

[0141] Similar to actuator 2102, increase actuator 2104a and decrease actuator 2104b can also enable a user to increase and decrease the intensity of the lighting load, respectively. As an example, each of actuators 2104a and 2104b can be selected with a single action (e.g., by clicking and releasing a mouse button, or by touching and releasing a display screen of network device 680). Here, each individual actuation of increase actuator 2104a can increase the intensity of the lighting load by a defined amount (e.g., 1%), and similarly, each individual actuation of decrease actuator 2104b can decrease the intensity of the lighting load by a defined amount (e.g., 1%). The defined amount can be user-definable. As another example, each of actuators 2104a and 2104b can be selected for an extended duration (e.g., by pressing and extending the release of a mouse button, or by extending the touch of the display screen of network device 680). Here, for example, the actuation can increase / decrease the intensity until the mouse button is released or the touch to the screen is removed. According to one example, when the user selects to increase actuator 2104a or decrease actuator 2104b, the control application may also automatically move actuator 2102 in an upward or downward direction, respectively, and update the value of indicator 2109 accordingly.

[0142] Generally speaking, for example, after the control application initially detects / determines that the user has selected icon 706 labeled "Master bedroom master reading light" from interface 702, the control application may initially display actuator 2102 and actuator 2106 of control interface 2100 to provide the user with an indication of the current on / off state and dimming state of the lighting load. For example, assuming the lighting load is on and in a dimmed state of 70% intensity, the control application may display the following: Fig. 10A 2100, for example, where actuator 2106 is shown indicating that the lighting load is on, and actuator 2102 is at a relative position along control line 2108c indicating 70% intensity, and the value of indicator 2109 shows a value of 70%. Similarly, assuming the lighting load is off, the control application may display a value such as Fig. 10C The control interface 2100 shown, for example, wherein the actuator 2106 is shown indicating that the lighting load is off, and the actuator 2102 is at a position 2108b indicating 0% intensity / lighting load off, and the value of the indicator 2109 shows a value of 0%. Referring to the indicator 2109, initially the value may be displayed in one intensity and / or color, such as Fig. 10A and Fig. 10C For example, once (and / or when) the user selects any of actuators 2102, 2104a, 2104b, and / or 2106, the control application may increase the intensity (or change the color) of indicator 2109 with increasing intensity, as shown. Fig. 10B At a defined time after the user stops changing the dimming state and / or on / off state of the lighting load (or when the user stops actuating any of the actuators), the control application may return the indicator 2109 to Fig. 10A The reduced intensity (and / or restoration of color back to the original color) shown. It will be appreciated that other examples are possible.

[0143] Generally speaking, if the lighting load is Fig. 10A 2106 to turn off the lighting load, the control application may display a Fig. 10C 2100, wherein actuator 2106 is displayed to show that the lighting load is off, and actuator 2102 automatically moves to position 2108b, and indicator 2109 is set to 0% to show the off state. Similarly, if the lighting load is Fig. 10C 2106 to turn on the lighting load, the control application may display a Fig. 10A 21. The control interface 2100 shown in FIG. 21 shows an actuator 2106 that is shown to show that the lighting load is turned on, and the actuator 2102 automatically moves along the control line 2108c to a relative position that shows the current intensity of the lighting load, and the indicator 2109 shows the intensity value (here, for example, the system controller and / or the control application can maintain the last set dimming level and / or the preferred dimming level, and can automatically set the dimming level of the lighting load to that value when the lighting load is turned on). Similarly, if the lighting load is turned on as shown in FIG. Fig. 10A 2106 or 2108b to turn off the lighting load (i.e., to 0%), the control application may display a Fig. 10C 2100, wherein actuator 2106 is shown to indicate that the lighting load is off, and actuator 2102 is shown in position 2108b, and the value of indicator 2109 is set to 0% to indicate the off state. Similarly, if the lighting load is Fig. 10C If the lighting load is shown in the off state, and the user actuates actuator 2106 or 2108a to turn on the lighting load (i.e., increase the intensity), the control application may display a Fig. 10A Control interface 2100 is shown with actuator 2106 shown to show the lighting load is on, and actuator 2102 moves along control line 2108c to a user selected intensity position, and the value of indicator 2109 shows the current intensity value. It will be appreciated that other examples are possible.

[0144] In general, based on detecting a user's selection / movement of actuator 2102 and / or actuators 2104a and 2104b (such as raising or lowering the intensity of a lighting load, turning off a lighting load, etc.), and / or detecting a user's selection of actuator 2106 (such as turning a lighting load on and off), the control application may communicate one or more messages to the system controller 250a, for example, to instruct the controller to reconfigure the lighting control device / one or more lighting loads based on the user's instructions. Again, if the user turns a lighting load off or on, this update may be reflected in icon 622 (e.g., decreasing / increasing a number), etc. The user may exit control interface 2100, for example, by selecting icon 2101. Other examples are also possible.

[0145] According to another example, the lighting control device can control a lighting load (or multiple lighting loads), wherein the lighting load may include multiple multi-color LEDs (light emitting diodes), but it will be appreciated that other types of lighting loads configured to emit colors of various color temperatures may be used. In other words, the lighting load may include, for example, multiple LEDs emitting different colors in a single package, and may be configured such that the chromaticity outputs of the LEDs are mixed to produce light having different chromaticity coordinates (i.e., color points) within the color gamut formed by the various LEDs constituting the lighting load. As an example, the lighting load may include one or more red LEDs, one or more green LEDs, one or more blue LEDs, and one or more white or substantially white LEDs (such as yellow and / or mint green LEDs), which may be collectively referred to herein as RGBW lighting loads. Although the RGBW lighting load is described herein as a combination of four LEDs of certain colors, this is for exemplary purposes, and other combinations of LEDs (e.g., more or fewer LEDs and / or LEDs of different colors) may be used. Similarly, although the RGBW lighting load is described herein as having one or more white LEDs, other color LEDs, such as yellow or mint green LEDs, may also be used instead. Again, RGBW LED lighting loads will be used herein for descriptive purposes only, and other types of lighting loads configured to produce light of different color temperatures may be used.

[0146] The lighting control device and such corresponding lighting loads may be configured to generate white light or near-white light (e.g., light that generates different chromaticity coordinates distributed along a black body locus or curve) of different brightness / intensity within a range of correlated color temperatures (CCT) ranging from, for example, "warm white" (e.g., approximately 2600K to 3700K) to "neutral white" (e.g., 3700K to 5000K) to "cool white" (e.g., 5000K to 8300K). As another example, such lighting control devices and their corresponding lighting loads may also be configured to generate any color of different brightness / intensity within the color gamut formed by the various LEDs that make up the lighting load.

[0147] According to yet another example described herein, such a lighting control device and its corresponding lighting load may be configured in one of two states or modes, including a non-fresh activation state / mode and a fresh activation state / mode (e.g., where the system may automatically select a certain fresh activation level for the user). The chromaticity coordinates of the mixed color output of the lighting load may be the same (or approximately the same) between the two modes (e.g., when in the non-fresh activation mode versus when in the fresh activation mode). However, the intensity of the various LEDs (and therefore the intensity of the wavelengths generated by the LEDs) may vary between the two modes, such that, in the fresh activation mode, for example, the intensity of one or more white light LEDs may be reduced (e.g., such as reduced to 0%) compared to the non-fresh activation mode, wherein the intensity of the remaining red, green, and / or blue LEDs is adjusted to maintain the same color output (or approximately the same color output) between the two modes. Similarly, the non-fresh activation mode may increase the intensity of the white light LEDs (where the intensity of the remaining red, green, and / or blue LEDs is adjusted to maintain the same color output (or approximately the same color output) as when in the fresh activation mode).

[0148] Thus, as described herein, the freshness activation mode can, for example, increase the intensity of one or more wavelengths generated by red, green, and / or blue LEDs, thereby making certain objects in the space appear more "vivid". In other words, as described herein, the freshness activation mode can tune the individual colors of light that make up a given color. When adjusting the freshness activation, the color of the light (e.g., chromaticity coordinates or CCT values) can remain unchanged or substantially unchanged. However, adjusting the freshness activation can adjust the contribution of the individual LEDs that make up a given light output of a given color. Therefore, as the freshness activation increases (freshness activation mode), the light reflected back from objects in the space may be more vivid, and similarly, as the freshness activation decreases (non-freshness activation mode), the light may be less vivid. In addition, adjusting the freshness activation can adjust the spectral power distribution (SPD) of the light. For example, as the freshness activation increases, the SPD curve (e.g., the relationship between relative intensity and wavelength) of the emitted light may become clearer and / or may cause the individual colors on the object to appear more vivid when the light is reflected back from the object. Thus, according to one example as described herein, the difference between the fresh activation mode and the non-fresh activation mode may be the intensity setting of one or more white light LEDs / the amount of contribution of one or more white light LEDs to the mixed color output of the lighting load, wherein the contribution of one or more white light LEDs in the fresh activation mode is less than that in the non-fresh activation mode (as another example, if, for example, a mint green light LED is used instead of a white light LED, the intensity setting of one or more mint green light LEDs / the amount of contribution of one or more mint green light LEDs to the mixed color output of the lighting load may be less in the fresh activation mode than in the non-fresh activation mode). It will be appreciated that other examples are also possible. One example of a lighting control device and a corresponding lighting load as described above is a luminaire or lamp provided by Lutron Ketra. Another example of such a lighting control device and a corresponding lighting load is described as a lighting device 38 of U.S. Patent Application Publication No. 2018 / 0077770, the entire contents of which are incorporated herein by reference. It will be appreciated that other exemplary lighting control devices and corresponding lighting loads are also possible.

[0149] As referred to herein, the freshness activation mode may be referred to as a high freshness activation mode or a freshness activation "on" setting, and the non-freshness activation mode may be referred to as a low freshness activation mode or a freshness activation "off" setting (which may be a "normal" setting).

[0150] Now, assuming that, for example, the “Master bedroom main reading lamp” table lamp icon in interface 702 corresponds to a lighting control device, the lighting control device controls the RGBW lighting load as described above after the control application detects / determines that the user has selected the “Master bedroom main reading lamp” table lamp icon from interface 702, then the control application may display Fig.11A21. The exemplary control interface 2110 shown. It will be recognized again that the control interface 2110 is an example and other control interfaces are possible. It will also be recognized that the control interface 2110 can be displayed to the user in response to other actions made by the user via other interfaces and / or in response to other determinations made by the control application and / or the system controller. The control application can determine that the "Master Bedroom Master Reading Light" table lamp is configured as a dimmable RGBW LED lighting load based on information provided by the system controller (e.g., from a type indicator, etc.), and based on this determination, the control interface 2110 can be displayed. As an example, as described above, the system controller can provide information about each lighting control device to the control application. For RGBW control devices / lighting loads, this information may include its current status / state and / or configuration. For example, for RGBW lighting control devices / one or more lighting loads, the information may include whether one or more lighting loads are in an on state or an off state, and if in an on state, whether it is in a dimmed state and possibly also a dimming level; what color point and / or CCT value the load is set or configured to; whether the control device is in a fresh activation mode, etc. Control interface 2110 can be similar to control interface 2100 and can include actuator 2112 (e.g., which can be referred to herein as a dimming actuator) (and control line 2118c having ends 2118a and 2118b), and can also include actuators 2114a and 2114b, which operate similarly to actuator 2102 and actuators 2104a and 2104b, respectively, and enable a user to control the intensity / brightness / dimming state of the lighting load (i.e., change the intensity / brightness of the color produced by the lighting load) as described above.

[0151] The control interface 2110 may also include an actuator 2116 that, similar to the actuator 2106, may be selected by the user to turn the lighting control device on and off (and thus turn one or more corresponding lighting loads on and off). Again, the control application may display the appearance of the actuator 2116 differently based on the on / off state of the lighting load, where Fig.11A Actuator 2116 is shown in a state indicating that the lighting load is on, and Fig. 11C The actuator 2116 is shown in a state indicating that the lighting load is off. It will be appreciated that other examples are possible. According to another aspect of this example, when the lighting load is Fig.11AWhen shown in the on state, the actuator 2116 may also include an indicator 2117 (e.g., which may be referred to herein as a color indicator). In this example, the indicator 2117 is shown as a circle surrounding the actuator 2116. Nevertheless, it will be appreciated that other indicators may be used, including indicators of different geometric shapes, such as a square or triangle surrounding the actuator 2116, or indicators that are adjacent to the actuator 2116 rather than surrounding the actuator 2116, or indicators that are in different locations within the control interface 2110. The control application may display the indicator 2117 in any of a variety of different colors, and in particular, the color of the indicator 2117 may be displayed to match (or substantially match) or represent the color currently being produced by the lighting load. In this manner, an indication is provided to the user as to the current color setting of the lighting load. As shown in FIG. Fig. 11C As shown, when the lighting load is off, the control application may not display the indicator 2117. Furthermore, when the lighting load is moved between the on state and the off state, such as by actuation of the actuator 2116 or movement of the actuator 2112 to and from the position 2118b (directly or through the actuators 2114a and 2114b), the control application may change the appearance of the actuator 2116 (between the on state / off state) and display or not display the indicator 2117. It will be appreciated that, in lieu of and / or in addition to displaying the "actual" color produced by the lighting load via the indicator 2117, the control application may also display, for example, chromaticity coordinates (such as x and y coordinates) or CCT values ​​(where applicable) of the color produced by the lighting load in the control interface 2110. It will be appreciated that other examples are possible.

[0152] Referring to indicator 2119 (which is similar to indicator 2109) and as described above, initially, the value of the indicator may be displayed at one intensity, such as Fig.11A and Fig. 11C Once the user selects any of actuators 2112, 2114a, 2114b, and / or 2116, the control application may increase the intensity of indicator 2119, such as Fig. 11B At a defined time after the user stops changing the dimming state and / or on / off state of the lighting load, the control application may cause the indicator 2119 to return to the reduced intensity.

[0153] As discussed similarly with reference to interface 2100, based on detecting a user's selection / movement of actuator 2112 and / or actuators 2114a and 2114b (such as raising or lowering the intensity of a lighting load, turning off a lighting load, etc.), and / or detecting a user's selection of actuator 2116 (such as turning a lighting load on and off), the control application may communicate one or more messages to system controller 250a, e.g., to instruct the controller to reconfigure the lighting control device / one or more lighting loads based on the user's instructions. Again, if the user turns a lighting load off or on, this update may be reflected in icon 622 (e.g., decreasing / increasing a number), etc. The user may exit control interface 2110, e.g., by selecting icon 2101. Other examples are also possible.

[0154] According to another aspect of control interface 2110, the interface may include a "Warm / Cool" actuator 2120, a "Vivid" actuator 2122, and a "Full Color" actuator 2124 (it will be appreciated that labels other than "Warm / Cool," "Vivid," and "Full Color" may be used). Each of actuators 2120, 2122, and 2124 may be selected by a user.

[0155] Starting with the "fresh activation" actuator 2122, upon detecting a user selection of this actuator, the control application may communicate one or more messages to the system controller 250a, for example to instruct the system controller to configure the lighting control device / lighting load to enter a fresh activation mode (e.g., turn the fresh activation to an "on" setting or "high" mode). As described above, the fresh activation mode may not change (or substantially change) the color point / chromaticity coordinates of the color produced by the lighting load, but may change the contribution / intensity of each RGBW LED in generating colored light, which may include, for example, reducing the intensity / contribution of one or more white light LEDs (e.g., setting the intensity of the white light LEDs to 0%) to make certain objects in the space more vivid. It will be recognized that this is an example and that fresh activation may be implemented in other ways. The one or more messages communicated by the control application to the system controller may include a command to enter a fresh activation mode, may include a command with a specified intensity setting for each of the individual RGBW LEDs, etc., but other examples are also possible. In general, when entering the freshness activation mode, the degree to which the intensity of each RGBW LED changes can be a predefined amount and, in addition, can depend on the color point / chromaticity coordinates of the color currently produced by the lighting load. For example, the closer the color of the light produced by the lighting load is to the black body curve (i.e., when the lighting load produces white light), the stronger the ability to put the lighting load into the freshness activation mode (compared to when the color of the light is further away from the black body curve).

[0156] In response to detecting selection of the "fresh activation" actuator 2122, the control application may display the appearance of the actuator 2122 differently (e.g., change the color or contrast of the actuator) based on whether the lighting control device is in or not in fresh activation mode. Fig.11A and Fig.11D An example of using reverse contrast to show the state of the fresh activation mode is shown, where Fig.11A shows that the freshness mode is deactivated (low freshness mode / off), and Fig.11D The freshness activation mode is shown to be activated (high freshness activation / on). It will be appreciated that other examples are possible. When the freshness activation mode is activated, upon detecting that the user has further selected actuator 2122, the control application may communicate one or more messages to the system controller 250a to instruct the controller to configure the lighting control device / lighting load to deactivate the freshness activation mode (e.g., setting the freshness activation to an off setting or low mode), thereby maintaining the color output of the lighting load, but compared to when the freshness activation mode is activated, for example, increasing the contribution of one or more white light LEDs (e.g., to a value other than 0%). This state may be referred to herein as a "normal" setting. Furthermore, for example, after the control application initially detects / determines that the user has selected icon 706 labeled "Master Bedroom Master Reading Light" from interface 702, the control application may initially display actuator 2122 as being activated or not activated in freshness activation mode, depending on the current state of the lighting control device reported by the system controller. In addition, even when the lighting control device is in the on state and in freshness activation mode, where actuator 2116 and actuator 2122 are as shown in FIG. Fig.11D As shown, after the lighting load is turned off, the control application can also display the actuator 2122 as being turned off in the fresh activation mode, such as Fig. 11C It will be appreciated that other examples are possible.

[0157] Reference is now made to the "warm / cool" actuator 2120 and the "full color" actuator 2124. The "warm / cool" actuator 2120 may allow a user to control a lighting control device such that the lighting load generates light at a user-selected color point along a black body curve (e.g., white light or near white light). The "full color" actuator 2124 may allow a user to control a lighting control device such that the lighting load generates light at a user-selected color point of any of a plurality of colors that may be within the color gamut formed by, for example, the various RGBW LEDs that make up the lighting load.

[0158] Starting with the "Warm / Cool" actuator 2120, upon detecting that the user has selected an actuator (such as from interface 2110 or from a Figures 11J to 11N After the interface 2140), the control application can display the following Fig.11E21. The control interface 2130 shown, wherein the "warm / cool" actuator 2120 is now shown as activated (here, reverse contrast is used to show the "warm / cool" actuator 2120 as activated, but other examples are possible). The control interface 2130 may continue to include actuators 2112, 2114a, and 2114b (and indicator 2119), which allow the user to control the intensity of the lighting load and also provide the user with the current dimming state of the lighting load. The control interface 2130 may also continue to include actuator 2116, which enables the user to turn the lighting control device / lighting load on and off. The control interface 2130 may also continue to include indicator 2117 to provide the user with an indication of the current color produced / presented by the lighting load. According to this example, the control interface 2130 may also include a color palette 2135, which shows a range of colors ranging from cool colors at end 2135a of the palette to warm colors at end 2135b. These colors may correspond to colors distributed along the black body curve. Specifically, the color palette 2135 may show colors along a range of correlated color temperatures (CCTs) ranging from "warm white" at 2135b (e.g., approximately 2600K to 3700K) to "neutral white" (e.g., 3700K to 5000K) to "cool white" at 2135a (e.g., 5000K to 8300K). As an example, the range may be from 1400K to 7000K, but other examples are possible.

[0159] An actuator 2132 may be superimposed on the color palette 2135, the actuator being movable / slidable along a control line 2135c (e.g., vertically movable here), and in particular, movable / slidable along the color palette 2135 between different CCTs along the black body curve. Thus, the actuator 2132 may allow a user to configure the lighting control device so that the lighting load generates colored light at a color point along the black body curve. Assuming that when the user selects the actuator 2120, the lighting load generates light at a color point along the black body curve, the control application may display the position of the actuator 2132 as shown in FIG. Fig.11E2135c / color palette 2135 to indicate the color produced by the lighting load. Similarly, indicator 2117 may also display the corresponding color. Alternatively, if the lighting load is not configured to produce light at a color point along the blackbody curve (or outside the range of color palette 2135) when the user selects actuator 2120 (or, for example, if the lighting load is off), the control application may not display actuator 2132. The control application may continue to display indicator 2117 corresponding to the color produced by the lighting load (assuming the lighting load is on). As another example, the control application may not initially display actuator 2132 after actuator 2120 is selected, regardless of the lighting load's settings.

[0160] Assume that after the user actuates actuator 2120 from control interface 2110, the control application initially displays the following Fig.11E 2130, for example, in which actuator 2132 is displayed, and assuming that the user then selects actuator 2132 / moves actuator 2132 along control line 2135c (such as via a mouse or via touch) to set the lighting load to a new CCT along the blackbody curve, the control application may then proceed as follows: Fig.11F As shown, indicator 2136 is displayed along with the actuator. As another example, assuming that actuator 2132 is not initially shown when the user selects actuator 2120, user selection of palette 2135 (e.g., via a mouse or touch) may cause actuator 2132 and indicator 2136 to appear at a location along line 2135c relative to where the user touches palette 2135 and / or relative to the CCT currently provided by the lighting load. It will be appreciated that other examples are possible. Indicator 2136 may display a numerical value corresponding to the CCT value currently set to actuator 2132 (6500K in this example). As the user moves actuator 2132 along control line 2135c, the control application may dynamically update indicator 2136 to correspond to the setting of the actuator. Additionally and as shown Fig.11F As shown, when the user moves the actuator 2132 along the control line 2135c, the control application can dynamically update the indicator 2117 to correspond to the color currently set by the actuator 2132. According to another example and as shown in FIG. Fig.11F As shown, the control application can also increase the size of the indicator 2117. In this example, the indicator 2117 is shown as a circle, for example, Fig.11E compared to, Fig.11F2136 from the control interface and return indicator 2117 to a smaller size / thinner line width, such as 2140. Fig.11G As shown in the example of . It will be appreciated that the indicator 2136 can include different values ​​or be different values, such as the chromaticity coordinates (such as x and y coordinates) of the color produced by the lighting load. Similarly, instead of increasing the size of the indicator 2117 as the actuator 2132 is moved to display the color to the user, other mechanisms can be used to display the color to the user, such as by rendering the actuator / icon 2116 the color when the actuator is activated.

[0161] According to yet another example, assuming that the lighting load is off when the user selects the actuator 2120 so that the control application displays the control interface 2130, the user's selection of the color palette 2135 (e.g., via a mouse or touch) may cause the lighting load to turn on (such as to full intensity, to the intensity previously set by the lighting load, or to the user's preferred intensity level, etc.), and wherein the appearance of the actuator 2116 changes to an on state, the indicator 2117 is displayed, and the actuator 2112 is displayed at the current intensity level. Similarly, the actuator 2132 and / or the indicator 2136 may appear at a position along the line 2135c relative to the position where the user touches the color palette 2135 and / or at a position relative to the CCT previously set by the lighting load, or at a position relative to the user's preferred CCT value, but other examples are possible, and wherein the lighting load is controlled to this color (again, the indicator 2117 also indicates the color). Thereafter, the user may move the actuator 2132 as described above.

[0162] As similarly discussed above, based on detecting selection / movement of actuator 2132, the control application may, for example, communicate one or more messages to the system controller 250a instructing the controller to reconfigure the lighting control device / one or more lighting loads based on the user's instructions.

[0163] like Fig.11H As shown, when the lighting load is set to a color point along the blackbody curve, the user can also actuate any of actuators 2112, 2114a and / or 2114b from the control interface 2130 to control the dimming state / intensity of the lighting load. Again, when this occurs, the control application can increase the intensity of indicator 2119, such as Fig.11H Similarly, Fig.11I As shown, when the lighting load is set to a color point along the blackbody curve, the user can also activate the "fresh activation" actuator 2122 from the control interface 2130 to configure the lighting control device / lighting load to enter the fresh activation mode. As shown above, the fresh activation mode may not change (or substantially change) the color point / chromaticity coordinates / CCT value of the color produced by the lighting load, but may change the contribution of each RGBW LED in generating colored light, which can include, for example, reducing the intensity / contribution of one or more white light LEDs to make certain objects in the space more vivid. In response to detecting the selection of the "fresh activation" actuator 2122, the control application can display the appearance of the actuator 2122 to show that it is activated, such as Fig.11I As shown, and one or more messages are communicated to the system controller 250a, for example to instruct the system controller to configure the lighting control device / lighting load to enter the fresh activation mode. When the "fresh activation" actuator 2122 is activated and the user modifies the color and / or intensity of the lighting load via the control interface 2130, the color presented by the lighting load can continue to be in the "fresh" state / fresh activation mode. Similarly, the user can deactivate the fresh activation mode from the control interface 2130, thereby returning to the normal settings (thereby maintaining the color output of the lighting load, but, for example, increasing the contribution of one or more white light LEDs). Finally, assuming that the user turns off the lighting load as described herein (such as through any of actuators 2116, 2112, 2114a and / or 2114b) when the control interface 2130 is displayed, the control application can automatically display the following. Fig. 11C Control interface 2110 is shown. It will be appreciated that other examples are possible. It will also be appreciated that, for example, actuator 2124 can be activated from control interface 2130, thereby causing the control application to display control interface 2140, as discussed below.

[0164] Turning now to the "full color" actuator 2124, upon detecting that the user has selected the actuator (such as from interface 2110 or interface 2130), the control application may display a display such as Fig.11J2140 is shown with the "full color" actuator 2124 now shown as being activated (here, reverse contrast is used to show that the full color actuator 2124 is activated, but other examples are possible). The control interface 2140 may continue to include actuators 2112, 2114a, and 2114b (and indicator 2119) that allow a user to control the intensity of the lighting load and also provide the user with the current dimming state of the lighting load. The control interface 2140 may also continue to include actuator 2116 that enables the user to turn the lighting control device / lighting load on and off. The control interface 2140 may also continue to include indicator 2117 to provide the user with an indication of the current color produced / presented by the lighting load. According to this example, the control interface 2140 may also include a color palette 2145 that shows a variety of colors within the color gamut formed by, for example, the various RGBW LEDs that make up the lighting load.

[0165] like Figure 11K As shown, an actuator 2142 can be superimposed on a color palette 2145, and the actuator can be moved / slid by the user to any of a plurality of positions / colors within the color palette 2145. The control application can display two vertical control lines 2144a and 2144b that intersect at the center 2144c of the actuator 2142 together with the actuator 2142. When the user moves the actuator 2142 within the color palette 2145, the control application can move the control lines 2144a and 2144b and the intersection point with the actuator 2142. These control lines can also assist the user in moving the actuator 2142 horizontally or vertically. Thus, the actuator 2132 can allow the user to configure the lighting control device so that the lighting load produces colored light at a color point that is within the color gamut formed by, for example, the various RGBW LEDs that constitute the lighting load. After, for example, a user actuates actuator 2124, such as from control interface 2110 or 2130, the control application may initially display control interface 2140 without actuator 2142 and without control lines 2144a and 2144b, such as Fig.11J 2144a and 2144b at opposite points within the color palette 2145 to indicate the color produced by the lighting load. Again, the indicator 2117 may also display the corresponding color.

[0166] Assume that after, for example, a user actuates actuator 2124 from control interface 2110 or 2130, the control application initially displays the following: Fig.11J2140, and when the user touches or activates the mouse on the palette 2145, for example, the lighting load is producing a blue background, for example, then the control application can display the actuator 2142 and control lines 2144a and 2144b at a point relative to the activation point. Figure 11K As shown, the control application can move the actuator 2142 and the control lines 2144a and 2144b according to the user action (for example, assuming that the user moves the actuator 2142 toward the orange base color). When the user moves the actuator 2142 on the color palette 2145 to set the lighting load to a new color point within the color palette 2145, the control application can move the indicator ( Figure 11K 2145) is displayed with the actuator. The indicator may display a numerical value corresponding to, for example, the chromaticity coordinates (such as x and y coordinates) of the color point to which the actuator is set, although other values ​​may be used. As the user moves the actuator 2142 on the color palette 2145, the control application may dynamically update this indicator to correspond to the setting of the actuator. Additionally and as Figure 11K As shown, when the user moves the actuator 2142 on the color palette 2145, the control application can dynamically update the indicator 2117 to correspond to the color currently set by the actuator 2142. According to another example and as shown in Figure 11K As shown, the control application can also increase the size of the indicator 2117 (in this example, the indicator 2117 is shown as a circle, for example, with Fig.11J compared to, Figure 11K In this way, the control application can provide an additional mechanism to show the user the color to which the lighting load is set. According to yet another example, after which the user stops actuating the actuator 2142 for the set duration and / or when the user no longer selects the actuator, the control application can return the indicator 2117 to a smaller size / thinner line width, such as Fig.11L , for example, thereby continuing to show the actuator 2142 and control lines 2144a and 2144b at the new color point. It will be appreciated that instead of increasing the size of the indicator 2117 as the actuator 2142 is moved in order to display the color to the user, other mechanisms can be used to display the color to the user, such as by rendering the actuator / icon 2116 the color when the actuator is activated.

[0167] According to yet another example, assuming that the lighting load is off when the user selects actuator 2124 to cause the control application to display control interface 2140, the user's selection of color palette 2145 (e.g., via mouse or touch) may cause the lighting load to turn on (such as to full intensity, to the intensity previously set by the lighting load, or to the user's preferred intensity level, etc.), and wherein the appearance of actuator 2116 changes to an on state, indicator 2117 is displayed, and actuator 2112 is displayed at the current intensity level. Similarly, actuator 2142 and control lines 2144a and 2144b may appear at a position relative to the position where the user touches color palette 2145 and / or at a position relative to the color previously set by the lighting load, or at a position relative to the user's preferred color value, but other examples are possible, and wherein the lighting load is controlled to this color (again, indicator 2117 also indicates the color). Thereafter, the user may move actuator 2142 as described above.

[0168] As similarly discussed above, based on detecting selection / movement of actuator 2142, the control application may communicate one or more messages to the system controller 250a, for example to instruct the controller to reconfigure the lighting control device / one or more lighting loads based on the user's instructions.

[0169] like Fig.11M As shown, when the lighting load is set to a certain color point using the control interface 2140, the user can also actuate any one of the actuators 2112, 2114a and / or 2114b from the control interface 2140 to control the dimming state / intensity of the lighting load. Furthermore, when this happens, Fig.11M As shown, the control application can increase the intensity of indicator 2119. Similarly, as Fig.11N As shown, when the lighting load is set to a certain color point using the control interface 2140, the user can also actuate the "fresh activation" actuator 2122 from the control interface 2140 to configure the lighting control device / lighting load to enter the fresh activation mode. As shown above, the fresh activation mode may not change (or substantially change) the color point / chromaticity coordinates of the color produced by the lighting load, but may change the contribution of each RGBW LED in generating colored light, which can include, for example, reducing the intensity / contribution of one or more white light LEDs to make certain objects in the space more vivid. In response to detecting the selection of the fresh activation actuator 2122, the control application can display the appearance of the actuator 2122 to show that it is activated, such as Fig.11NAs shown, and one or more messages are communicated to the system controller 250a, for example to instruct the system controller to configure the lighting control device / lighting load to enter the fresh activation mode. When the "fresh activation" actuator 2122 is activated and the user modifies the color and / or intensity of the lighting load via the control interface 2140, the color presented by the lighting load can continue to be in the "fresh" state / fresh activation mode. Similarly, the user can deactivate the fresh activation mode from the control interface 2140, thereby returning to the normal settings (thereby maintaining the color output of the lighting load, but increasing the contribution of one or more white light LEDs compared to when the fresh activation mode is activated). Finally, assuming that the user turns off the lighting load as described herein (for example, through any of actuators 2116, 2112, 2114a and / or 2114b) when the control interface 2140 is displayed, the control application can automatically display the following. Fig. 11C Control interface 2110 is shown. It will be appreciated that other examples are possible. It will also be appreciated that actuator 2120 can be activated from control interface 2140, thereby causing a control application to display control interface 2130, for example.

[0170] According to another example of freshness activation control via a "freshness activation" actuator 2122 and a color palette 2145 that allows a user to configure the lighting load to any of a plurality of colors within the palette, the freshness activation control may be limited to colors within a predefined range of colors within the palette. For example, with reference to the color palette 2245, the freshness activation control may be limited to a predefined set of colors (i.e., white) on the right side of the palette. The predefined colors may be the 10% or 20% colors on the right side of the palette. When the user selects a color outside of this predefined set of colors in the palette, the "freshness activation" actuator 2122 and therefore the freshness activation control may be disabled because it is not possible to present these colors in a variety of ways using, for example, RGB and white light LEDs of different intensities. Assuming that the lighting load includes, for example, additional LEDs of other colors, a wider range of color palettes 2245 may allow actuation of the "freshness activation" actuator 2122.

[0171] It will be appreciated that, for example, if the lighting control device / lighting load is in fresh mode when the control application displays any of the control interfaces 2110, 2130, or 2140, then the "fresh" actuator 2122 may be shown as activated.

[0172] Referring now to another example regarding the "fresh activation" actuator 2122, upon detecting that a user has selected this actuator, the control application may display an interface (not shown) to the user that may include, for example, three actuators labeled, for example, "high," "low," and "cancel." The user's selection of "cancel" may cause the control application to close the interface and return the user to the control interface from which the "fresh activation" actuator 2122 was selected. Upon detecting that the user has selected the "high" actuator, the control application may communicate one or more messages to the system controller 250a, for example, to instruct the system controller to configure the lighting control device / lighting load to enter a fresh activation mode (or a "high" fresh activation mode or an "on" setting). The fresh activation mode according to this example may include, for example, setting the lighting load to produce 3000K light (although other color temperatures may also be used) and setting the intensity of the lighting load to 100% (although other intensities may also be used). In this mode, generating 3000K light can include, for example, using one or more red, green, and / or blue LEDs to generate color, and, for example, reducing the intensity / contribution of one or more white LEDs (compared to when the "low" actuator is selected) (e.g., setting the intensity of the white LEDs to 0%), thereby making certain objects in the space more vivid. After selecting the "high" actuator, the control application can again display the control interface from which the "vivid activation" actuator 2122 was selected, wherein the actuator 2116 is set to show that the lighting load is "on", the indicator 2117 is set to a color corresponding to 3000K, and the "vivid activation" actuator 2122 is set to show that the vivid activation mode is activated (e.g., as shown in FIG. 21 ). Fig.11D 2140). If the "fresh activation" actuator 2122 is selected from the control interface 2130, the control application may show the actuator 2132 at a position corresponding to 3000K along the control line 2135c / color palette 2135. If the "fresh activation" actuator 2122 is selected from the control interface 2140, the control application may show the actuator 2142 and the control lines 2144a and 2144b at a position corresponding to 3000K in the color palette 2145. Assuming the user then changes the color produced by the lighting load via the control interface 2130 or 2140, the color produced by the lighting load may still be produced in the "high" fresh activation mode, i.e., with, for example, a reduced intensity / contribution of one or more white light LEDs (compared to the "low" fresh activation mode).

[0173] Alternatively, upon detecting that the user has selected the "low" actuator, the control application may communicate one or more messages to the system controller 250a, e.g., to instruct the system controller to configure the lighting control device / lighting load to enter a non-fresh activation mode (or a "low" fresh activation mode, or an "off" setting, or a normal setting). The non-fresh activation mode according to this example may include, for example, setting the lighting load to produce 3000K light (i.e., the same color temperature as the "high" mode, although other color temperatures may also be used) and setting the intensity of the lighting load to 100% (i.e., the same intensity as the "high" mode, although other intensities may also be used). In this mode, producing the 3000K light may include, for example, using one or more red, green, and / or blue LEDs to produce color, and, for example, using an increased intensity / contribution of one or more white LEDs, as compared to the "high" fresh activation mode, thereby making certain objects in the space less vivid (as compared to the high fresh activation mode). After selecting the "Low" actuator, the control application may again display the control interface from which the "Fresh Activation" actuator 2122 was selected, wherein the actuator 2116 is set to show that the lighting load is "On", the indicator 2117 is set to a color corresponding to 3000K, and the "Fresh Activation" actuator 2122 is set to show that the fresh activation mode is deactivated (e.g., as shown in FIG. Fig.11A 2140 ). If the "fresh activation" actuator 2122 is selected from the control interface 2130, the control application may show the actuator 2132 at a position corresponding to 3000K along the control line 2135c / color palette 2135. If the "fresh activation" actuator 2122 is selected from the control interface 2140, the control application may show the actuator 2142 and the control lines 2144a and 2144b at a position corresponding to 3000K in the color palette 2145. Assuming the user then changes the color produced by the lighting load via the control interface 2130 or 2140, the color produced by the lighting load may still be produced in the "low" fresh activation mode, i.e., with, for example, an increased intensity / contribution of one or more white light LEDs (compared to the "high" fresh activation mode). It will be appreciated that other variations are possible.

[0174] Reference now Fig.11O, another exemplary control interface 2150 is shown. For example, control interface 2150 can be similar to control interfaces 2110, 2130, and 2140, and can operate similarly to these control interfaces. For example, control interface 2150 can include actuator 2116 for controlling / indicating the on / off state of a lighting control device / lighting load as described herein, and can include indicator 2117 for indicating the color that the lighting load is currently configured to produce as described herein. Control interface 2150 can also include actuators 2112, 2114a, and 2114b for controlling the intensity level of the lighting load, for example, as described herein. Control interface 2150 can also include a "warm / cool" actuator 2120 and a "full color" actuator 2124 as described herein. As an example, actuation of the "warm / cool" actuator 2120 may cause the control application to display the color palette 2135 in the control interface 2150 (e.g., along with the actuators 2112, 2114a, and 2114b). Fig.11O 2140 ). For example, as described herein, user actuation of actuator 2132 may allow the user to configure the lighting load to produce a color along the blackbody curve, where indicator 2117 indicates the color, as described herein. Similarly, actuation of “full color” actuator 2124 may cause the control application to display, for example, color palette 2145 in control interface 2150 (similar to control interface 2140 ) along with actuators 2112 , 2114 a , and 2114 b . For example, as described herein, user actuation of actuator 2142 of color palette 2145 may allow the user to configure the lighting load to produce any one of a plurality of colors within a color gamut, where indicator 2117 indicates the color, as described herein.

[0175] According to another aspect of this example, the control interface 2150 may include a "more" actuator 2151 (in Fig.11O When palette 2145 is displayed in control interface 2150, a "more" actuator 2151 may also be shown. Upon detecting that actuator 2151 has been selected, the control application may expand control interface 2150 to include an "auto freshness" actuator 2152, such as Figure 11P In this example, the control interface 2150 scrolls up with the "auto fresh activation" actuator 2152 displayed, but other examples are possible. Similar actions may occur when the control application is displaying the palette 2145 and the "more" actuator 2151 is actuated.

[0176] The “auto freshness activation” actuator 2152 (also referred to herein as an automatic actuator) can be enabled and disabled by a user to enable / disable (e.g., turn on / off) a feature that can be referred to as an “auto freshness activation” feature, as described herein. Figure 11P In this example of , the "auto freshness activation" actuator 2152 is shown as being actuated / enabled, which can be a default state. According to this example, when the "auto freshness activation" actuator 2152 is enabled (i.e., turned on), the control application can (e.g., by communicating one or more messages to the system controller 250a) automatically configure the color rendering index (CRI) value of the lighting control device / lighting load at the color that the lighting control device / lighting load is configured to produce. For example, given a certain color point (e.g., whether selected via the color palette 2135 or the color palette 2145), enabling the "auto freshness activation" actuator 2152 can automatically configure the lighting load to increase the CRI value of the light produced by the lighting load at that color to be greater than or equal to a CRI threshold, which can be greater than or equal to 90.

[0177] Specifically, the light output of the lighting load can be measured by a color rendering index (CRI) value. The CRI value can be a measurement of the ability of the lighting load to reveal the actual color of an object compared to an ideal light source (e.g., natural light). A higher CRI value may be a desired characteristic of the user. For example, a lighting load with a higher CRI value can provide light so that objects in the space reflect light of natural colors. Assuming that the lighting load is, for example, an RGBW LED lighting load as described herein, each of the corresponding LEDs included in the RGBW lighting load can be defined by a certain CRI value. In addition, for example, the RGBW lighting load itself can be defined by a CRI value (e.g., a CRI value indicating a summary or average CRI of each of the corresponding LEDs included in the lighting load). The CRI value can be in the range of 0 to 100 (including 0 and 100). For example, the lowest possible CRI value can be 0, and the highest possible CRI value can be 100. Not all lighting loads can be configured for all CRI values ​​of a given generated color. The control application can be used to configure the CRI value of one or more lighting loads at a given color. CRI values ​​greater than or equal to a threshold value (e.g., a CRI value of 90) may be desirable and may be referred to herein as "optimal," "optimized," or "maximized." That is, other ranges (e.g., smaller and / or larger ranges) may also be considered "optimal," "optimized," or "maximized." Thus, as described herein, a control application may increase or attempt to increase the CRI value of a lighting load at a given selected color to a value greater than or equal to a threshold CRI value. For example, the threshold CRI value may be 90. However, it will be appreciated that the threshold CRI value may be other values. For example, the CRI threshold may be a value that may be considered a desired threshold that the system may attempt to achieve given certain characteristics of a load control system and / or lighting control device (e.g., the quality of the LEDs used in the lighting load). As described herein, optimizing a CRI value toward a threshold CRI value or optimizing a CRI value to be above a threshold CRI value may be referred to as optimizing a CRI value.

[0178] Thus, again, when the “auto fresh activation” actuator 2152 is enabled, the control application may automatically configure the lighting load (based on determining that the actuator is enabled and, for example, by communicating one or more messages to the system controller 250a) such that the CRI value of the light output of the lighting load at a given selected color is greater than or equal to a CRI threshold value (e.g., greater than or equal to 90) (which may be referred to herein as optimizing the CRI value toward the CRI threshold value or optimizing the CRI value to be greater than the CRI threshold value). In some cases (e.g., for a certain color point or CCT), the CRI value may not be able to become a value greater than or equal to the CRI threshold value. In those cases, enabling the “auto fresh activation” actuator 2152 may cause the lighting control device to increase the CRI value of the light output of the lighting load toward the CRI threshold value (e.g., as close as possible). As similarly described herein, when the “auto freshness” actuator 2152 is enabled, as determined by the control application, when a user selects a color via the color palettes 2135 and / or 2145, the control application, system controller and / or lighting control device can cause the CRI value of the light output of the lighting load to be optimized as the user makes changes (e.g., to achieve a CRI value greater than or equal to 90).

[0179] According to another aspect of this example, Figure 11Q As shown, the user can disable the "auto fresh activation" actuator 2152. Upon detecting / determining that the user has disabled the actuator 2152, the control application can further expand the control interface 2150 to display an actuator 2153 (e.g., which can be referred to herein as a fresh activation actuator) that can move / slide along a control line 2156 (e.g., can move vertically), an increase actuator 2154a, and a decrease actuator 2154b.

[0180] As described, the actuator 2153 can be movable / slidable along the control line 2156 (e.g., vertically movable, but it will be appreciated that the actuator 2153 can alternatively be horizontally movable, for example), and can allow a user to increase the relative freshness / freshness level of light output by the lighting load (e.g., by moving the actuator vertically upward toward position 2155a) or decrease the freshness / freshness level of light output by the lighting load (e.g., by moving the actuator vertically downward toward position 2155b). As similarly described herein, altering the freshness of a given lighting load can keep the color of light produced by the lighting load the same or substantially the same, but can alter the contributions of the individual LEDs that make up the light to make an object more or less fresh. The actuator 2153 can allow a user to control the freshness / freshness level of the lighting load from a relative maximum level (position 2155a), such as 100%, to a minimum level (position 2155b), such as 0%. Thus, as the actuator 2153 moves toward position 2155a, the object can become increasingly more vivid, and similarly, as the actuator 2153 moves toward position 2153b, the object can become increasingly less vivid. The control application can display the position of the actuator 2153 along the control line 2156 to represent the current relative activation level of the lighting load. The control application can also display an indicator 2157 with the actuator 2153 that numerically represents the current activation level of the lighting load, shown here as a numerical percentage value of 50%, although other exemplary numerical representations can also be used. The control application can also dynamically change the value of the indicator 2157 as the user moves the actuator 2153 vertically up and down. Also as shown in FIG. Figure 11Q As shown, the portion of the control wire 2156 located below the actuator 2153 can be shown with a different intensity or line thickness (here, greater intensity / line thickness) compared to the portion of the control wire 2156 located above the actuator 2153.

[0181] Similar to actuator 2153, increase actuator 2154a and decrease actuator 2154b can also enable a user to increase and decrease the freshness activation of the lighting load, respectively. As an example, each of actuators 2154a and 2154b can be selected with a single action (e.g., by clicking and releasing a mouse button, or by touching and releasing a display screen of network device 680). Here, each individual actuation of increase actuator 2154a can increase the freshness activation of the lighting load by a defined amount (e.g., 1%), and similarly, each individual actuation of decrease actuator 2154b can decrease the freshness activation of the lighting load by a defined amount (e.g., 1%). The defined amount can be user-definable. As another example, each of actuators 2154a and 2154b can be selected for an extended duration (e.g., by pressing and extending the release of a mouse button, or by extending the touch of the display screen of network device 680). Here, for example, the actuation can increase / decrease the freshness activation level until the mouse button is released or the touch to the screen is removed. According to one example, when the user selects to increase actuator 2154a or decrease actuator 2154b, the control application may also automatically move actuator 2153 in an upward or downward direction, respectively, and accordingly update the value of indicator 2157. After disabling the "fresh activation actuator" 2152, the control application may position actuator 2153 along control line 2156 to represent the current fresh activation level of the lighting load, and may accordingly configure the value of indicator 2157. It will be appreciated that as the user changes the fresh activation level, the CRI value of the lighting load may move below the CRI threshold.

[0182] According to one example, when the "fresh activation actuator" 2152 is disabled, the actuators 2153, 2154a, and 2154b can be enabled only when the control interface 2150 is displaying the color palette 2135. For example, when the control interface is displaying the color palette 2145, the fresh activation control via the actuators 2153, 2154a, and 2154b can be disabled. Alternatively, when the control interface is displaying the color palette 2145, the fresh activation control via the actuators 2153, 2154a, and 2154b can be limited to colors within a predetermined range of the color gamut. For example, with reference to the color palette 2145, the fresh activation control can be limited to a predefined set of colors on the right side of the palette (i.e., white). The predefined colors can be 10% or 20% of the colors on the right side of the palette. When the user selects a color outside of this predefined color set in the color palette, the actuators 2153, 2154a, and 2154b and thus the freshness activation control may be disabled, since it is not possible to render these colors in multiple ways using, for example, RGB and white light LEDs of different intensities. A wider range of color palettes 2245 may allow freshness activation control via the actuators 2153, 2154a, and 2154b, assuming that the lighting load includes, for example, additional LEDs of other colors.

[0183] Again, as similarly described herein, for example, when a user changes the color of the lighting load via the color palette 2135 and / or the color palette 2145 (or a portion thereof), the control application may cause the lighting load (e.g., via a message communicated to the system controller 250a) to produce a certain freshness activation level of light based on the setting of the actuator 2153. Similarly, assuming that the "freshness activation actuator" 2152 is disabled, and for example, after the control application detects that the "freshness activation actuator" 2152 is enabled, the user selects a desired freshness activation level (at the selected color) via the actuator 2153 (thereby causing the lighting load to present light of that color and freshness activation level), the control application may communicate one or more messages to the system controller 250a, for example, to cause the lighting control device / lighting load to change the light output of the lighting load so that the CRI value of the light output / lighting load is greater than or equal to the CRI threshold value. Other examples are also possible.

[0184] will realize that FIG. 10A to FIG. 10C and FIG. 11A to FIG. 11Q The exemplary control interface shown can be activated from other graphical user interfaces, including, for example, other graphical user interfaces described herein, including, for example, activating a control interface from an icon representing a lighting control device that is currently in an off state (as compared to selecting an icon from interface 702 showing a control device that is currently in an on state).

[0185] return Figure 6COnce the user has completed interface 702, the user may select icon 714 (a "done" icon, but an icon may also be used). After detecting / determining that the user has selected icon 714, the control application may again display interface 610 to the user, such as Fig. 6A shown.

[0186] Now go to Fig. 6A , as shown, this icon can be a shade device icon that indicates to the user the number of shade devices within the load control system 210a whose corresponding shades are currently opened / retracted (where open / retracted can be any shade state other than a fully closed position) (it will be recognized that while the shade icon 614 is discussed herein as being associated with shades, it can also be associated with, for example, drapes, curtains, or blinds, as well as other types of window coverings. Alternatively, section 620 can include other icons for such devices.) Similar to a lighting control device, a given shade device can control more than one shade (for example, if multiple shades covering several different windows are coupled together into one shade) and can control those shades in unison (or can potentially be configured to control those shades to different states separately). According to one example, a control application can treat a given shade device and its corresponding shade as one device. In this example, if multiple shades controlled by a shade device are in an open / retracted state, the control application may count this as one (1) with respect to the number associated with icon 624, regardless of the number of shades actually controlled by the device. Nevertheless, it will be appreciated that the number associated with icon 614 may represent the actual number of shades controlled by each lighting control device. Here, the control application may view each shade controlled by a given shade device separately. In this example, the number associated with icon 624 may represent each shade. Thus, if two shades controlled by a shade device are in an open / retracted state, the control application may count this as two (2) with respect to icon 624. For descriptive purposes, the control application is described herein from the perspective of the shade device, where the shade device and its corresponding shade are considered a single unit. The control application may determine the number of shades currently open / retracted based on information obtained from the system controller 250a. In this example, the control application has determined based on information received from the system controller 250a that three shade devices have the corresponding shades currently opened / retracted (where open / retracted may include the shades being in a partially opened / retracted state). Again, for example, the control application and / or the system controller may perform a count to determine this number. Fig. 6AAs shown, the control application can indicate this determination to the user through the displayed number "3" associated with icon 624, but again, the control application can display the number in other ways. In addition to displaying the number of shade devices whose shades are determined to be currently open / retracted, as similarly discussed with respect to lighting control device icon 622, the control application can also actively update the count displayed by icon 624 based on, for example, the system controller 250a actively monitoring the status of the shades in the user's environment (e.g., due to users in the environment raising and lowering the shades) and reporting this information to the control application, for example asynchronously and / or due to the control application requesting the status of the control device / shade from the system controller 250a. In this way, icon 624 can allow the user to quickly and easily determine from network device 680 whether any shades are open / retracted in the user's environment. If it is determined that no shades are currently open / retracted, the control application can use icon 624 to display a value of "0", can use the icon to not display any value, can not display the icon at all (thereby indicating that no shades are open / retracted, etc.). Other variations are also possible. For example, the control application may display an icon when any shade is open / retracted, and not display an icon when all shades are down / closed, rather than displaying the number with icon 624. As yet another example, icon 624 may indicate the number of shades currently down / closed.

[0187] Icon 624 can also be selected by the user. After detecting / determining that the user has selected icon 624, the control application can display graphical user interface 720 to the user via network device 680, such as Fig. 6F As shown. The interface 720 can continue to display to the user the icons 624 and the number of window shade devices whose window shades are determined to be currently open / retracted. The interface 720 can also include an "all open" icon 724 (although other text and / or icons can also be used) and / or can also include an "all closed" icon 726 (although other text and / or icons can also be used), both of which can be selected by the user. The interface 720 can also include a corresponding icon 716 for each window shade device with a corresponding controlled window shade that is currently open / retracted (again, according to this example, the control application can be configured to treat the window shade device and its one or more corresponding window shades as a unit, thereby uniformly representing the unit as an icon. As an alternative, each window shade controlled by the window shade device can be represented by an icon in the interface 720 or some combination thereof.) Each of these icons 716 can also be selected by the user. In this example, three icons 716 are shown in association with the value "3" as shown by the icon 624. According to yet another example and / or alternative example, and as shown in Fig. 6FAs shown, the interface 720 may also include a corresponding icon 718 (three are shown here) for each shade device in the load control system whose corresponding one or more controlled shades are currently closed / lowered. Each of these icons 718 may also be selected by the user. The control application may provide the user with a visual indication of the status of all shades in the load control system. Assuming the control application is configured as follows Fig. 6F If the control application performs the operations shown (i.e., displays icons 716 and 718), the control application may use one or more visual tools / indicators to display corresponding icons 716 and 718 to indicate which shade devices of the load control system have open shades and which shade devices have closed shades. As an example, the control application may change the appearance of the icons for open shades and closed shades, such as in Fig. 6F In an example of using different colors and / or contrast between icons. As another and / or additional example, the control application can use different icons for open window shades versus closed window shades. In one example, an icon representing an open window shade can have an icon showing a partially open window shade, while an icon representing a closed window shade can have an icon showing a closed window shade. Other examples are also possible.

[0188] Similar to Figure 6C The control application may also use a location indicator and / or a type indicator to display an indication of the location and / or function of the corresponding shade device / shade in the user environment with each icon 716 and 718 (in this example, text information such as "kitchen left shade", "kitchen center shade", "kitchen right shade", "living room left shade", "living room center shade", and "living room right shade" is used, but other mechanisms are also possible, such as separating icons by location, similar to Fig. 6A section 660).

[0189] Similar to Figure 6CFor example, if a user in a kitchen moves the "kitchen left shades" from an open state / position to a closed state / position, the control application may receive an indication of this change from the system controller 250a (e.g., automatically or in response to a query by the control application) and change the corresponding icon in the display 720 to have an icon appearance as represented by icon 718. In addition, the control application may decrease the count associated with icon 624. Similarly, if a user in a kitchen moves the "living room left shades" from a closed state / position to an open state / position, the control application may receive an indication of this change from the system controller 250a and change the corresponding icon in the display 720 to have an icon appearance as represented by icon 716. In addition, the control application may increase the count associated with icon 624.

[0190] Turning now to icon 724 of user interface 720, which may allow a user to open all window shades within the load control system 210a. Upon detecting / determining that the user has selected icon 724, the control application may communicate one or more messages to the system controller 250a, instructing the system controller to open all window shades. Once completed, the system controller 250a may provide a response to the control application (e.g., automatically or in response to a query by the control application) indicating that the window shades are now open. According to one example, "opening" all window shades may cause the system controller to control each window shade to its respective fully open state. According to another example, the system controller may, for example, store for each window shade a defined position (e.g., a user-defined position) to which the window shade should be moved in response to an "all open" request. Other variations are also possible. In response, the control application may display a message such as "Open All". Figure 6G Specifically, the control application can change the value associated with icon 624 to indicate the new number of shade devices with open corresponding shades (6 in this example), and can change the appearance of icons 716 / 718 as needed to indicate open shades (in Figure 6G In the example of FIG. 7 , all window shade icons 716 / 718 are shown as open window shades.) Note that in Figure 6G, since all the window shades are open, icon 724 may be deactivated by the control application (wherein deactivation may include rendering icon 724 unselectable by the user and / or changing the appearance of icon 724 (such as by changing its color or contrast compared to other icons), removing the icon from interface 720, etc.). If a window shade is subsequently closed (such as by a user in user environment 202a), the control application may also activate / reactivate icon 724 (wherein activating the icon may include rendering the icon selectable by the user and / or changing the appearance of icon 724 (such as by changing its color or contrast compared to other icons), displaying the icon in interface 720, etc.), in addition to, for example, decreasing the number associated with icon 624 by "1" and correspondingly changing one of the icons in interface 720 to show the closed window shade. As for icon 726, it may allow the user to close all window shades within load control system 210a. Upon detecting / determining that the user has selected icon 726, the control application may communicate one or more messages to system controller 250a, thereby instructing the system controller to close all window shades. Once completed, the system controller 250a may provide a response to the control application (e.g., automatically or in response to a query by the control application) indicating that all shades are now closed. In response, the control application may display a Figure 6H Specifically, the control application can, for example, change the value associated with icon 624 to "0", or display no value at all as shown here, and can change the appearance of icon 716 / 718 as needed to indicate a closed shade (in Figure 6H , all window shade icons 716 / 718 are shown as closed window shades). It should be noted that since all window shades are already closed, icon 726 may be deactivated by the control application. If a window shade is subsequently opened (such as by a user in user environment 202a), the control application may activate / reactivate icon 726 in addition to, for example, increasing the number associated with icon 624 to "1" and correspondingly changing one of the icons in interface 720 to show an open window shade. It will be appreciated that when interface 720 is initially displayed when the user selects icon 624 from interface 610, the control application may activate / deactivate icons 724 and 726 based on the open / closed state of the window shades in load control system 210a.

[0191] As an alternative to selecting icons 724 and / or 726, the user may select any of icons 716 / 718 to respectively control the shade device and thus the shades. Upon detecting / determining that the user has selected a given one of icons 716 / 718, the control application may display to the user an interface for controlling the corresponding shade device and thus one or more shades. For example, assuming that the control application detects / determines that the user has selected icon 716 labeled "kitchen left shade" in interface 720, the control application may display Fig.6I 728 is shown (in this example, if more than one shade is controlled by the control device, the shades can be controlled to a common state). For example, the control interface 728 can be shown separately or superimposed on the interface 720. It will be appreciated that the control interface 728 is an example and other controls are possible. Here, the control interface 728 is shown as having a vertically movable / slidable actuator 730 that can be actuated by the user (again, the control application can determine the appropriate control interface to display to the user based on information provided by the system controller (e.g., from the type indicator) to control the selected device based on the capabilities of the device). As in this example, the control application can display the actuator 730 to provide the user with an indication of the corresponding shade position (i.e., for example, the actuator is approximately halfway along its possible path to indicate that one or more shades are partially closed / lowered). Based on detecting that the user moves the actuator 730 (such as raising or lowering the shade, etc.), the control application can communicate one or more messages to the system controller 250a to instruct the system controller to reconfigure the "kitchen left shade" based on the user's instructions. If the user closes one or more shades, this update may be reflected in icon 624 (e.g., the displayed value decreases) and in interface 720 (e.g., the appearance of the icon), as similarly discussed above. Similarly, if one or more shades were initially closed and are now opened via actuator 730, this update may be reflected in icon 624 (e.g., the displayed value increases) and in interface 720 (e.g., the appearance of the icon), as similarly discussed above. Fig.6I As shown, the control interface 728 may also include a selectable "Edit" icon 732, which, when selected, may cause the control application to display a user interface that will allow the user to reconfigure the parameters associated with the kitchen left shade. The user may exit the control interface 728 by touching an area of ​​the display screen of the network device 680 outside of the interface 728. Other examples are also possible.

[0192] Furthermore, Fig. 6FThe user interface 720 of is an example. As another example, upon detecting that the user has selected the icon 624, the control application may only display the corresponding icon 716 for each shade device with a corresponding shade currently opened / retracted in the graphical interface 720, and may only include an "all closed" icon 726 to close the shades that are opened separately (i.e., the interface 720 may not include an icon 718 representing the shades that are currently closed and / or a control icon 724). As another example, as shown above, the shade icon 624 may alternatively show the number of shades that are currently closed / lowered. In this example, upon detecting that the user has selected the icon 624, the control application may only display the corresponding icon 718 for each shade device with a corresponding shade that is currently closed / lowered in the graphical interface 720, and may only include an "all open" icon 724 to open the shades that are closed separately (i.e., the interface 720 may not include an icon 716 representing the shades that are currently opened and / or a control icon 726). Other examples are also possible. For example, the interface 720 may be as shown. Fig. 6F , where icon 624 shows the number of open shades, and both icons 716 and 718 exist to show the status of all shades. However, interface 720 may not include an “all open” icon 724 and / or an “all closed” icon 726.

[0193] return Fig. 6F Once the user has completed interface 720, the user may select icon 722 (a "done" icon, but an icon may also be used). Upon detecting / determining that the user has selected icon 722, the control application may again display interface 610 to the user, such as Fig. 6A shown.

[0194] Now go to Fig. 6A , as shown, this icon can be a thermostat device icon that indicates to the user the current temperature in the user environment 202a. Specifically, the load control system 210a may include one or more thermostat devices that control a corresponding HVAC system. The control application can determine the current temperature in the user environment 202a based on the interaction of the system controller 250a with the one or more thermostat devices using information obtained from the system controller. Based on the one or more current temperatures obtained from the system controller, the control application can determine a representative temperature reading for the user environment and display this reading to the user by displaying this reading (72 degrees in this example) and associating this reading with the icon 626, as shown. Fig. 6AAs shown. As an example, when the load control system includes a single HVAC system, the current temperature indicated by the control application via icon 626 can be the current temperature as measured by the corresponding thermostat device. When the load control system includes two or more HVAC systems, the current temperature indicated by the control application via icon 626 can be the current temperature indicated by one of the thermostat devices, and the control application's selection of which thermostat device to use can be based on information received from the system controller about which thermostat device to use and / or information associated with the corresponding thermostat device. For example, assuming that the user environment has a downstairs and upstairs HVAC system, the control application may always use the current temperature indicated by the downstairs thermostat, may use the current temperature indicated by the downstairs thermostat during the day (e.g., where "daytime" may be provided by the system controller, such as 6AM to 8PM), and use the current temperature indicated by the upstairs thermostat at night (e.g., where "nighttime" may be provided by the system controller, such as 8PM to 6AM), etc. Other variations are also possible, including the control application allowing the user to select which of the thermostat devices to use and when to use them (see Figure 6K 626 ). As another example, the control application may use an average of the respective current temperatures measured by the respective thermostat devices of each HVAC system (e.g., as determined by the control application and / or system controller). It will be appreciated that when multiple HVAC systems are present, other mechanisms and / or mathematical formulas may be used to determine the temperature associated with icon 626. As another example (not shown in the figure), in addition to associating / displaying the current temperature with icon 626, the control application may also display an indication of the current heating and / or cooling set point temperature to which the thermostat device is set. When multiple thermostat devices / HVAC systems are present, the control application may determine which set point temperature(s) to use in a manner similar to the current temperature. It will be appreciated that the temperature value provided by icon 626 may be in Fahrenheit or Celsius and may be configurable by the user.

[0195] For purposes of illustration only, it will be assumed that the load control system 250a includes two HVAC systems (an upstairs and a downstairs system), each having a corresponding thermostat device, and that the control application displays the current temperature reading of the downstairs system using icon 626. In addition to displaying the current temperature, as with the lighting device icon 622, the control application can also actively update the current temperature displayed by icon 626 based on, for example, the system controller 250a actively monitoring the current temperature measured by the downstairs thermostat and reporting this information to the control application asynchronously and / or as a result of the control application requesting the status of the downstairs thermostat device from the system controller 250a. In this manner, icon 626 can allow a user to quickly and easily determine the current temperature in the user environment 202a from the network device 680.

[0196] Icon 626 can also be selected by the user. After detecting / determining that the user has selected icon 626, the control application can display the following to the user via network device 680: Figure 6J 740. The interface 740 may continue to display the icon 626 and the current temperature reading to the user. The interface 740 may also include an "all raise" icon 744 (although other text and / or icons may also be used) and / or may also include an "all lower" icon 746 (although other text and / or icons may also be used), both of which may be selected by the user and may allow the user to control the thermostat devices of the load control system simultaneously / together, as discussed below. The interface 740 may also include corresponding information sections (also referred to herein as panes) for each thermostat device in the load control system. In this example, where the load control system 210a includes two thermostat devices, each device may have corresponding information sections or panes 760 and 762 that provide corresponding status information and controls for each thermostat device / HVAC system. If the load control system has more than two thermostat devices / HVAC systems, the control application can be configured to make the information sections 760 and 762 scrollable by the user (such as vertically scrollable) to display additional information sections or panes, one section or pane for each system. In one aspect, the information sections 760 and 762 allow the user to control the corresponding thermostat devices separately. Figure 6JAs further shown, the control application can use the location indicator and / or type indicator associated with each thermostat device to display an indication of the location of the corresponding device in the user environment in conjunction with each thermostat device in information sections or panes 760 and 762 (in this example, using text information such as "downstairs thermostat" and "upstairs thermostat", but other mechanisms are possible). In general, the control application's use of text information can allow the user to more easily determine the actual thermostat device / HVAC system in the user environment that the information in sections 760 / 762 refers to.

[0197] Taking the information section or pane 760 as an example, the control application can display the current temperature reading 750 (here 72 degrees) determined by the corresponding thermostat device for the thermostat / HVAC system. Furthermore, when the corresponding thermostat device determines a change in the current temperature reading in the user's environment and the system controller 250a reports this change to the control application (e.g., automatically or in response to a query by the control application), the control application can actively update the current temperature reading 750 displayed to the user. The control application can also display one or more set point temperatures 756 (here 70 degrees) to which the corresponding thermostat device is configured to control its corresponding HVAC system. Assuming that the HVAC system has four modes, including heating mode, cooling mode, automatic mode, and off mode, no set point temperature, one or more set point temperatures 756 may be displayed. For example, if the thermostat is set to off, no set point temperature may be displayed. If the thermostat is set to heating mode or cooling mode, one set point temperature 756 representing the temperature to which the HVAC system is set to heat or cool, respectively, can be shown. If the thermostat is set to automatic mode, two set point temperatures may be shown, representing the temperature to which the HVAC system is set to heat and the temperature to which it is set to cool. The user may also be provided with an indication of which of the two temperatures is the temperature to which it is heated and which is the temperature to which it is cooled. The information section 760 may also include selectable icon controls 752 (two pairs if two set point temperatures are shown) that allow the user to adjust one or more set point temperatures 756 of the thermostat device. In this example, the "+" and "-" controls are used to increase and decrease the set point temperature 756, respectively. It will be appreciated that other control types may be used. Each actuation of the "+" control by the user may increase the set point temperature 756 by a predetermined number of degrees (such as one degree). Similarly, each actuation of the "-" control by the user may decrease the set point temperature 756 by a predetermined number of degrees (such as one degree). Upon detecting / determining that the user has selected one of the corresponding "+" and "-" controls of the icon 752, the control application may communicate one or more messages to the system controller 250a, thereby instructing the system controller to adjust the set point temperature of the thermostat device. Changes in one or more set point temperatures may also be reflected in one or more set point temperatures 756 of interface 740 .

[0198] For example, the information section 760 may also include a selectable "carrot" 758. Upon detecting / determining that the user has selected the carrot 758, the control application may expand the information section 760 to display additional controls / information to the user, such as Figure 6K764 (again, the controls displayed by the control application may be based on the capabilities / functionality of the thermostat device as determined from information provided by the system controller). According to this example, the user interface 764 may include three control sections that may allow the user to further control the downstairs thermostat / HVAC system. These control sections may include a mode control 766 that may allow the user to select, for example, any of the heating mode, cooling mode, automatic mode, and off mode of the HVAC system as described above. The control application may display the current mode of the HVAC system (here, cooling) as determined from the system controller with the mode control 766. The control section may also include a fan control 768 that may allow the user to turn the HVAC fan on and off. The control application may display the current fan setting of the HVAC system (here, on) as determined from the system controller with the fan control 768. Assuming that the thermostat device / HVAC system is programmable, the control section may also include a schedule control 770 that may allow the user to turn a schedule on and off. The control application may display the current schedule status (here, on) as determined from the system controller with a schedule control 770. Upon detecting / determining that a user has selected any of these controls (e.g., by touching the word "heat" or "auto" or "off", etc.), the control application may communicate one or more messages to the system controller 250a, thereby instructing the system controller to adjust / reconfigure the thermostat device. The user interface 764 may also include a selectable "edit" icon 756, which, when selected, may cause the control application to display a user interface that will allow the user to reconfigure the schedule of the thermostat device. For example, where the control application communicates this information to the system controller 250a, the user may be able to adjust on / off times, heating and cooling set point temperatures, etc.

[0199] Go to again Figure 6JAs well as an "all raise" icon 744 and an "all lower" icon 746, these controls can allow the user to simultaneously / together raise and lower one or more set point temperatures 756 of the corresponding thermostat devices of the load control system. It will be appreciated that other control types can be used. Each actuation of the icon 744 by the user can increase one or more corresponding set point temperatures 756 of each thermostat device (which can be different for each thermostat) by a predetermined degree (such as one degree). Similarly, each actuation of the icon 746 by the user can reduce one or more corresponding set point temperatures 756 of each thermostat device by a predetermined degree (such as one degree). For example, if the HVAC system is set to automatic mode, two set point temperatures of the system may move simultaneously. For example, assume that the set point temperature of the downstairs thermostat device / HVAC system (represented by section or pane 760) is 70 degrees, and the set point temperature of the upstairs thermostat device / HVAC system (represented by section or pane 762) is 74 degrees. Actuation of icon 744 by the user may increase the set point temperature of the downstairs thermostat device / HVAC system to 71 degrees, and may increase the set point temperature of the upstairs thermostat device / HVAC system to 75 degrees (assuming that each actuation of icon 744 changes the temperature by one degree). Similarly, again assuming that the set point temperature of the downstairs thermostat device / HVAC system is 70 degrees and the set point temperature of the upstairs thermostat device / HVAC system is 74 degrees, actuation of icon 746 by the user may decrease the set point temperature of the downstairs thermostat device / HVAC system to 69 degrees, and may decrease the set point temperature of the upstairs thermostat device / HVAC system to 73 degrees (assuming that each actuation of icon 746 changes the temperature by one degree). Upon detecting / determining that the user has selected one of the respective icons 744 and 746, the control application may communicate one or more messages to the system controller 250a, thereby instructing the system controller to adjust the set point temperatures of the thermostat devices. The changes in the set point temperatures may be reflected in one or more set point temperatures 756 of each device.

[0200] Further references Figure 6J, if a given user environment includes different types of temperature devices, the appearance of segments 760 and 762 may be different for each temperature device. Again, the control application may make this determination based on, for example, information received from a system controller and / or based on information stored at a network device. According to another aspect of the control application, when the load control system 250a includes multiple HVAC systems, as described above, the temperature associated with icon 626 may correspond to one of the systems. According to one example, the control application may use the temperature associated with the first or top thermostat device / HVAC system, as shown in interface 740 (here, the thermostat device / HVAC system represented by segment 760). According to another aspect of the control application, the user may change the order of segments 760 and 762 displayed in interface 740 (e.g., the user may touch a given segment for at least a defined period of time. Upon detecting the touch, the control application may, for example, activate the segment and allow the user to drag the segment up or down, thereby changing the order). After changing the order, the control application may now cause the temperature associated with icon 626 to track the new top segment. It will be appreciated that the order in which the segments 760 and 762 should be displayed and which of the segments the icon 626 should track can be stored at the network device and / or system controller. It will also be appreciated that other variations are possible, including, for example, the last of the temperature tracking segments 760 and 762 associated with the icon 626.

[0201] Once the user has completed interface 740, the user may select icon 742 (a "done" icon, but an icon may also be used). Upon detecting / determining that the user has selected icon 742, the control application may again display interface 610 to the user, such as Fig. 6A shown.

[0202] As shown in the figure, Fig. 6A Section 620 of user interface 610 may also include other icons, such as Figure 6L776, which can indicate to the user the status of the fan devices within the load control system 210a, such as the number of fans currently turned on. Similar to a lighting control device, a given fan device can control more than one fan and can control these fans in unison. According to one example, the control application can treat a given fan device and its corresponding fans as one device. In this example, as long as one fan controlled by the fan device is in the on state, the control application can count this as one (1) with respect to the number associated with icon 776, regardless of the number of fans actually controlled by the device. Nevertheless, it will be appreciated that the number associated with icon 776 can represent the actual number of fans controlled by each fan device. Here, the control application can view each fan controlled by a given fan device separately. In this example, the number associated with icon 776 can represent each fan. Therefore, if two fans controlled by the fan device are in the on state, the control application can count this as two (2) with respect to icon 776. For descriptive purposes, the control application is described herein from the perspective of the fan device, where the fan device and its corresponding fans are treated as a single unit. The control application may determine the number of fans that are currently turned on based on information obtained from the system controller 250a. Again, for example, the control application and / or the system controller may perform a count to determine this number. In this example, the control application has determined based on information received from the system controller 250a that two fan arrangements have respective fans that are currently turned on (where turned on may include the fans being at any speed and not off). Figure 6LAs shown, the control application can indicate this determination to the user by displaying the number "2" associated with icon 776. In addition to displaying the number of fan devices whose corresponding fans are determined to be currently turned on, similar to lighting control device icon 622, the control application can also actively update the number displayed with fan icon 776 based on, for example, system controller 250a actively monitoring the status of fans in the user environment (e.g., due to users in the environment adjusting fans) and asynchronously and / or, for example, due to the control application requesting the status of fans and / or control devices in general from system controller 250a and reporting this information to the control application. In this way, fan icon 624 allows the user to quickly and easily determine from network device 680 whether there are any fans turned on in the user environment. If no fans are determined to be currently turned on, the control application can use icon 776 to display a value of "0", can use the icon to display no value, or can not display the icon at all (thereby indicating that no fans are turned on, etc.). Other variations are also possible. For example, instead of displaying a number with icon 776, the control application can display an icon when any fan is turned on, and can display no icon when all fans are turned off. As yet another example, icon 776 may indicate the number of fan units whose corresponding fans are all in an off state.

[0203] Icon 776 can also be selected by the user. After detecting / determining that the user has selected icon 776 from user interface 620, the control application can display the following to the user via network device 680: Figure 6M 772 is shown. Interface 772 may continue to display to the user icons 776 and the number of fan devices whose fans are currently determined to be on. Interface 772 may also include a "turn off all fans" icon 778 that can be selected by the user (although other text and / or icons may also be used). Interface 772 may also include a corresponding icon 780 for each fan device that has a corresponding fan that is determined to be on (again, according to this example, the control application may be configured to treat the fan device and its one or more corresponding fans as a unit, and represent the unit uniformly as an icon. As an alternative, each fan controlled by the fan device may be represented by an icon in interface 702 or some combination thereof). Each of these icons may also be selected by the user. In this example, two icons 780 are shown in conjunction with the value "2" shown with icon 776. The control application may use a location and / or type indicator associated with each fan device to display an indication of the location of the corresponding fan device / fan in the user's environment in conjunction with each icon (in this example, text information such as "downstairs bathroom fan" and "master bedroom fan" is used, but other mechanisms are also possible, such as separating icons by location, similar to Fig. 6A, but only icons for devices that are currently turned on are displayed). Similar to interface 702, the control application can actively update the icon 780 displayed to the user when fans in the user environment change state from on to off and from off to on. For example, when a fan controlled by a fan device is turned on, for example, by a user in the user environment, the control application can receive an indication of this change from the system controller 250a (e.g., automatically or in response to a query by the control application) and display an additional icon 780 associated with the fan device of the fan to the user in interface 772, and also increase the value shown by icon 776 by "1". Similarly, when a fan controlled by a fan device is turned off, the control application can receive an indication of this change from the system controller 250a and, when all fans controlled by the fan device are turned off, remove the icon 780 associated with the fan device from the interface 772 or change the appearance of the icon (e.g., changing its color or contrast compared to other icons), as similarly discussed above. Other variations are also possible. For example, the control application can be similar to FIG. 6F to FIG. 6H Interface 772 is configured with interface 720 of FIG. 1 and shows all fan devices (both on and off) in the load control system, including the status of each fan device, as similarly described for the window shades, and also allows the user to control the fan devices, as described for the window shades. FIG. 6F to FIG. 6H. Turning now to icon 778, as shown, this icon can be selected by the user and can allow the user to turn off all fan devices, and thereby turn off the fans currently turned on in the load control system 210a. Upon detecting / determining that the user has selected the icon, the control application can communicate one or more messages to the system controller 250a, thereby instructing the system controller to turn off all fans. Once completed, the system controller 250a can provide a response to the control application (e.g., automatically or in response to a query), thereby indicating that the fan devices are now turned off. In response, the control application can, for example, change the number associated with icon 776 to "0" (or, for example, not show any value), and, for example, remove icon 780 from interface 772 or change the appearance of icon 780. Since all fan devices / fans are turned off, the control application can also deactivate icon 778 (wherein deactivation can include making the icon unselectable by the user and / or changing the appearance of icon 778 (such as by changing its color or contrast compared to other icons), removing the icon from interface 772, etc.). Once a fan unit is returned to the on state (such as by a user in user environment 202a turning on a fan), in addition to, for example, increasing the number associated with icon 776 to "1" and displaying an icon 780 representing the fan unit in interface 772, the control application may also activate / reactivate icon 778 (where activating an icon may include making the icon selectable by the user and / or changing the appearance of icon 778 (such as by changing its color or contrast compared to other icons), displaying the icon in interface 772, etc.). It will be appreciated that other examples are possible, such as interface 772 also / alternatively including a "turn on all fans" icon, which, when selected, may cause the control application to communicate one or more messages to the system controller to turn all fans in the user environment to the on state (or turn a set of preprogrammed fans to the on state). Again, such an action by the user may cause the control application to increase the number associated with icon 622 and display a corresponding icon 780 accordingly. Other examples are possible.

[0204] As an alternative to selecting icon 778, icon 780 may also be selected by the user and allow the user to individually control the fan device, and therefore control one or more fans associated with the icon. (It will be appreciated that if the control application is configured to show icon 780 in a manner indicating that the corresponding fan device is off, the icon may continue to be selected by the user to control the device.) Upon detecting / determining that the user has selected a given icon in icons 780, the control application may display to the user an interface for controlling the corresponding fan device / one or more fans.

[0205] For example, assuming the control application detects / determines that the user has selected icon 780 labeled "Master Bathroom Fan" in interface 772 (in this example, the fan device can control a corresponding fan), the control application can display the following: Figure 6N 782 is shown. For example, control interface 782 may be shown alone or superimposed on interface 772. It will be appreciated that control interface 782 is an example and that other controls are possible. The "master bathroom fan" may be a multi-speed fan, and therefore, the control application (such as determining from its type indicator that the fan is a multi-speed fan) may display control interface 782, as shown here, where multiple fan speed actuators 784 may be actuated by the user (i.e., the control application may determine the appropriate control interface to display to the user based on information provided by the system controller (e.g., from the type indicator) to control the selected fan device / fan based on the capabilities of the fan device / fan). The control application may display actuators 784 to provide the user with an initial indication of the current fan speed of the fan controlled by the fan device (e.g., highlighting the low speed actuator in this example). Based on detecting that the user has selected one of actuators 784, the control application may communicate one or more messages to the system controller 250a to instruct the system controller to reconfigure the fan device based on the user's instructions. If the user turns off the fan device / fan, for example, as discussed above, this update can be reflected in icon 776 (e.g., by reducing the count by 1) and in interface 772 by removing or changing the appearance of icon 780 corresponding to "Master Bathroom Fan." Figure 6N As shown, the control interface 782 may also include an optional "Edit" icon 784, which, when selected, may cause the control application to display a user interface that may allow the user to reconfigure the parameters associated with the corresponding fan device / fan. The user may exit the control interface 782 by touching an area of ​​the display screen of the network device 680 outside of the interface 782. Other examples are also possible.

[0206] return Figure 6M Once the user has completed interface 772, the user may select icon 774 (a "done" icon, but other icons may also be used). Upon detecting / determining that the user has selected icon 774, the control application may again display interface 610 to the user, such as Fig. 6A shown.

[0207] As indicated above, section 620 may show additional status information in addition to the status information discussed herein. For example, the control application may include one or more icons in section 620 to indicate alarms and / or system notifications, such as an indication of low battery / number of low batteries in the load control system (e.g., assuming one or more control devices have batteries), an indication that an alarm is sounding in the user environment 202a (e.g., a smoke alarm, a carbon monoxide detector alarm, a house security alarm), an indication of a communication error (e.g., a system controller user is unable to communicate with one or more control devices), etc. Any such icon may be selected by the user, thereby, for example, causing the control application to display an interface to the user that will provide additional information and / or system controls. Assuming that the load control system includes, for example, an occupancy sensor, the control application may include an icon in section 620 that provides an indication of occupancy status in the user environment 202a. Such icons may simply provide an indication of occupancy / unoccupancy and / or may provide an indication of the number of people present in the user environment 202a. For example, assuming that various rooms have occupancy sensors, selection of such occupancy icons may cause the control application to display to the user an interface that provides additional information such as which rooms in the user environment are occupied and / or unoccupied. It will be appreciated that the control application may determine occupancy in other ways, such as by detecting changes in the status of control devices such as lights, fans, shades, etc. from the user actuating controls within the user environment, tracking the opening / closing of doors through sensors, etc. As another example, the scenes maintained by the system controller may include "vacation mode", "away mode" (which may be a scene for the day when the occupants leave the home), "home mode" (which may be a scene for the day when the occupants have returned home), and other scenes, etc. Accordingly, the control application may include one or more icons in section 620 that provide an indication of which mode / scene is currently active in the environment. Selecting one or more such icons may cause the control application to display to the user an interface that allows, for example, the user to change modes / scenes. Again, other examples are possible.

[0208] Now go to Fig.6OAs well as sections 640 and 660, upon determining / detecting that the user has selected the devices tab 642 (or as a default configuration), the control application may provide an indication of tab activity (e.g., as indicated by underline 643, although other means such as reverse highlighting may also be used) and may display icons within the information section 660, wherein the icons may represent one or more of the control devices of the load control system 210a. According to one example, all control devices may be displayed in section 660. According to another example, certain control devices such as thermostat devices or handheld / remote control keypads that are configured to, for example, only turn on / off one or more lighting loads and / or control dimming levels of lighting loads may not be displayed in this section. According to another example, the control application may be user configurable, allowing the user to decide whether such control devices are shown in section 660. As indicated above, upon starting the control application, it may default to the devices tab 642.

[0209] According to one example, when the device tab 642 is active, the control application may subdivide the section 660 into one or more panes (three panes are shown here: 802, 804, and 806). Each pane may represent a location within the user environment 202a. The control application may determine the location based on information received from the system controller 250a, such as location indicators associated with various control devices. The control application may provide an indication with each pane as to the location it represents. Here, text labels are used, but other mechanisms may also be used. Fig.6OIn the example of , the control application may mark pane 802 as "kitchen", pane 804 as "living room", and pane 806 as "master bedroom". Within each pane 802, 804, and 806, when the control device and / or one or more loads controlled by it are located in the corresponding position represented by the pane, the control application may also display a corresponding icon (such as icons 810a to 810d) for the control device. As shown, different icons may be used for different types of control devices. According to one example, icons for certain control devices may appear in multiple panes 802, 804, and / or 806. As an example, if the determination of whether to display an icon for a given control device in a pane is based on the location of the control device, the icon may appear in a pane corresponding to the location. Ho...

Claims

1. A device comprising: Display screen; Communication circuits; at least one processor; as well as at least one memory device communicatively coupled to the at least one processor and having stored thereon software instructions that, when executed by the at least one processor, instruct the at least one processor to: displaying a graphical user interface on the display screen, the graphical user interface comprising a first color control interface, the first color control interface comprising a first color palette, the first color palette enabling control of the lighting load within a first plurality of colors in response to selection of a color on the first color palette; detecting a selected color on the first color palette; in response to detecting the selected color on the first color palette, communicating a first message via the communication circuit to a lighting control device, the lighting control device being configured to perform the controlling of the lighting load within the first plurality of colors by controlling the lighting load to the selected color on the first color palette; displaying a second color control interface on the graphical user interface, the second color control interface comprising a second color palette, the second color palette enabling control of the lighting load within a second plurality of colors in response to selection of a color on the second color palette; detecting a selected color on the second color palette; and In response to detecting the selected color on the second color palette, a second message is communicated to the lighting control device via the communication circuit, and the lighting control device is configured to perform the control of the lighting load within the second plurality of colors by controlling the lighting load to the selected color on the second color palette.

2. The apparatus of claim 1 , wherein the lighting load comprises a plurality of light emitting diodes (LEDs), the LEDs comprising white light LEDs or substantially white light LEDs; and wherein the instructions, when executed by the at least one processor, further instruct the at least one processor to: Display fresh activation actuator; detecting actuation of the fresh activation actuator; and In response to detecting the actuation of the freshness activation actuator, a third message is communicated to the lighting control device via the communication circuit to control the lighting load to reduce the intensity of the white light LED or the substantially white light LED while continuing to produce the selected color on the first color palette or the second color palette that the lighting load is configured to produce.

3. The apparatus of claim 2, wherein the instructions, when executed by the at least one processor, further instruct the at least one processor to: After detecting the actuation of the fresh activation actuator, detecting further actuation of the fresh activation actuator; and In response to detecting the further actuation of the freshness activation actuator, a fourth message is communicated to the lighting control device via the communication circuit to control the lighting load to increase the intensity of the white light LED or the substantially white light LED while continuing to produce the selected color on the first color palette or the second color palette that the lighting load is configured to produce.

4. The device of claim 1 , wherein the first color palette enables selection of a color along a blackbody curve, wherein the first plurality of colors includes colors on the blackbody curve, and wherein the first message is configured to control the lighting load to produce white light or near-white light at the selected color within the plurality of colors along the blackbody curve.

5. A device comprising: Display screen; Communication circuits; at least one processor; as well as at least one memory device communicatively coupled to the at least one processor and having stored thereon software instructions that, when executed by the at least one processor, instruct the at least one processor to: receiving, via the communication circuit, information communicated by a controller from a communication network, wherein the controller is configured to communicate with a lighting control device, wherein the lighting control device is configured to control a lighting load, wherein the lighting load is configured to produce light of any one of a plurality of different colors, and wherein the information includes an indication of the color that the lighting load is configured to produce; displaying a graphical user interface on the display screen, the graphical user interface comprising an on-off actuator for turning the lighting load on and off; A color indicator is displayed in the graphical user interface along with the on-off actuator, the color indicator indicating the color that the lighting load is configured to produce. detecting actuation of the on-off actuator to turn off the lighting load; and In response to detecting the actuation of the on-off actuator to turn off the lighting load, removing the color indicator from the graphical user interface.

6. A device comprising: Display screen; Communication circuits; at least one processor; as well as at least one memory device communicatively coupled to the at least one processor and having stored thereon software instructions that, when executed by the at least one processor, instruct the at least one processor to: displaying a graphical user interface on the display screen, the graphical user interface including a pane for controlling a lighting load via a lighting control capable of responding to a sensor, wherein the pane includes a selectable actuator capable of configuring the lighting control to respond or not respond to a signal received from the sensor; receiving actuation of the actuator; and In response to the actuation of the actuator, a message is sent to the lighting control device to cause the lighting control device to respond or not respond to the signal from the sensor.

7. A device comprising: Display screen; at least one processor; as well as at least one memory device communicatively coupled to the at least one processor and having stored thereon software instructions that, when executed by the at least one processor, instruct the at least one processor to: displaying a graphical user interface on the display screen, the graphical user interface comprising a first actuator, a second actuator, and a color indicator, the first actuator being configured to cause the graphical user interface to display a first color control interface, the first color control interface being configured to enable control of light generated by the lighting load within a first plurality of colors, the second actuator being configured to cause the graphical user interface to display a second color control interface, the second color control interface being configured to enable control of light generated by the lighting load within a second plurality of colors, and the color indicator indicating a color that the lighting load is currently configured to generate; receiving a selection on a first color control interface; displaying a color from the first plurality of colors on the color indicator in response to a selection on the first color control interface; receiving a selection of a second actuator, the selection configured to cause the graphical user interface to display a second color control interface; as well as A second color control interface is displayed with a color indicator configured to continue to display a color from the first plurality of colors being generated by the lighting load in response to a selection on the first color control interface while the second color control interface is displayed to allow selection of a color from the second plurality of colors.

8. A non-transitory tangible computer-readable medium having stored thereon instructions that, when executed by at least one processor, instruct the at least one processor to: displaying a graphical user interface on the display screen, the graphical user interface comprising a first actuator, a second actuator, and a color indicator, the first actuator being configured to cause the graphical user interface to display a first color control interface, the first color control interface being configured to enable control of light generated by the lighting load within a first plurality of colors, the second actuator being configured to cause the graphical user interface to display a second color control interface, the second color control interface being configured to enable control of light generated by the lighting load within a second plurality of colors, and the color indicator indicating a color that the lighting load is currently configured to generate; receiving a selection on a first color control interface; displaying a color from the first plurality of colors on the color indicator in response to a selection on the first color control interface; receiving a selection of a second actuator, the selection configured to cause the graphical user interface to display a second color control interface; and A second color control interface is displayed with a color indicator configured to continue to display a color from the first plurality of colors being generated by the lighting load in response to a selection on the first color control interface while the second color control interface is displayed to allow selection of a color from the second plurality of colors.

9. A method comprising: displaying, by at least one processor, a graphical user interface, the graphical user interface comprising a first actuator, a second actuator, and a color indicator, the first actuator being configured to cause the graphical user interface to display a first color control interface, the first color control interface being configured to enable control of light generated by the lighting load within a first plurality of colors, the second actuator being configured to cause the graphical user interface to display a second color control interface, the second color control interface being configured to enable control of light generated by the lighting load within a second plurality of colors, the color indicator indicating a color that the lighting load is currently configured to generate; receiving, by the at least one processor, a selection on a first color control interface; displaying, by the at least one processor, a color from the first plurality of colors on a color indicator in response to a selection on the first color control interface; receiving, by the at least one processor, a selection of a second actuator, the selection configured to cause the graphical user interface to display a second color control interface; as well as A second color control interface is displayed by the at least one processor along with a color indicator, wherein the color indicator is configured to continue to display a color from the first plurality of colors being generated by the lighting load in response to a selection on the first color control interface while the second color control interface is displayed to allow selection of a color within the second plurality of colors.

10. A load control system, comprising: a lighting control device, wherein the lighting control device is configured to control a lighting load, and wherein the lighting load is configured to generate light of any of a plurality of different colors; as well as Equipment, including: Display screen; at least one processor; and at least one memory device communicatively coupled to the at least one processor and having stored thereon software instructions that, when executed by the at least one processor, instruct the at least one processor to: displaying a graphical user interface on the display screen, the graphical user interface comprising a first actuator, a second actuator, and a color indicator, the first actuator being configured to cause the graphical user interface to display a first color control interface, the first color control interface being configured to enable control of light generated by the lighting load within a first plurality of colors, the second actuator being configured to cause the graphical user interface to display a second color control interface, the second color control interface being configured to enable control of light generated by the lighting load within a second plurality of colors, and the color indicator indicating a color that the lighting load is currently configured to generate; receiving a selection on a first color control interface; displaying a color from the first plurality of colors on the color indicator in response to a selection on the first color control interface; receiving a selection of a second actuator, the selection configured to cause the graphical user interface to display a second color control interface; and A second color control interface is displayed with a color indicator configured to continue to display a color from the first plurality of colors being generated by the lighting load in response to a selection on the first color control interface while the second color control interface is displayed to allow selection of a color from the second plurality of colors.