HK40090689A - Transmission of aggregated sensor data - Google Patents

Description

Transmission of aggregated sensor data

Cross-references to related applications

This application claims priority to U.S. Provisional Patent Application No. 63/081,649, filed September 22, 2020, entitled “Transmission of Control Data on Wireless Network Communication Links,” the entire disclosure of which is hereby incorporated by reference.

Background Technology

For example, user environments such as residential or office buildings can be configured using various types of load control systems. Lighting control systems can be used to control lighting loads in a user environment. Electric window covering control systems can be used to control natural light supplied to a user environment. Heating, ventilation, and air conditioning (HVAC) systems can be used to control temperature in a user environment. Each load control system can include various control devices, including control source devices and control target devices. The control target device can receive messages from one or more control source devices for controlling electrical loads, the messages including load control commands. The control target device may be able to directly control the electrical load. The control source device may be able to indirectly control the electrical load through the control target device. Examples of control target devices may include lighting control devices (e.g., dimmer switches, electronic switches, ballasts, or light-emitting diode (LED) drivers), electric window coverings, temperature control devices (e.g., thermostats), AC plug-in load control devices, etc. Examples of control source devices may include remote control devices, occupancy sensors, daylight sensors, temperature sensors, etc.

Summary of the Invention

Devices such as wired or wireless system controllers can be configured to communicate with multiple input devices and process messages received from said multiple input devices for transmission over a wireless communication link. For example, the multiple input devices may be sensors configured to transmit measurements from sensor data over a first communication link (e.g., a wired or wireless communication link). The sensor data may be received by the wireless system controller and can be configured for transmission over a second communication link (e.g., a wireless communication link). The first and second communication links may use different communication protocols. The wireless system controller may receive sensor data over the first communication link and format the sensor data for transmission over the second communication link.

The wireless system controller can transmit sensor data received from multiple sensor devices on the second communication link after the time interval expires, to avoid more frequent transmissions on the second communication link that could otherwise interfere with other communications. Sensor data from multiple sensors can be aggregated for transmission on the second communication link to avoid additional communication and potential interference.

Each of the sensors can be configured to transmit a message including sensor data measured at the respective sensor on a first communication link according to a transmission criterion satisfied at the respective sensor. In response to receiving a message including sensor data from the respective sensor, the wireless system controller can determine a transmission count for the respective sensor. For example, the transmission count of the respective sensor from which the message is received can be based on a transmission criterion that triggers the sensor to transmit the message. Each of the plurality of sensors communicating with the wireless system controller can be associated with a corresponding transmission count for performing a transmission on a second communication link. For example, the transmission count can indicate the number of corresponding transmissions for transmitting a message, including sensor data measured at each of the plurality of sensors, on the second communication link. After receiving the message and determining the corresponding transmission count for the sensor, the wireless system controller can store the received sensor data measured at the respective sensor device for transmission on the second communication link.

As described herein, a wireless system controller can process messages received from multiple sensors based on its state. For example, the wireless system controller's state can be one of a heartbeat state, a backoff state, or a fast state. Therefore, the wireless system controller can identify its current state and then process messages received from multiple sensors based on that current state. For example, when in the heartbeat state, the wireless system controller can determine that at least one of the multiple sensors is marked for transmission (e.g., based on the corresponding transmission count of each of the multiple input devices) and transmit a message including sensor data from each of the at least one sensor marked for transmission. Alternatively, the wireless system controller can determine that one or more sensors are marked for heartbeat transmission after an interval period has expired, and then transmit a message including sensor data from each of the multiple sensors. When the wireless system controller is in the backoff state, it can determine whether a message including sensor data has been received during the interval period. If no message including sensor data has been received during the interval period, the wireless system controller can transition to the heartbeat state. When the wireless system controller is in a fast state, it can determine when the interval period expires that at least one input device has been marked for transmission (e.g., based on the corresponding transmission count of each of the plurality of input devices), and transmit a message including sensor data for each of the at least one input device marked for transmission on a second communication link.

Attached Figure Description

Figure 1 is a simplified diagram of an exemplary load control system for controlling one or more electrical loads.

Figures 2A and 2B are state machine diagrams associated with an exemplary program that can be executed by control circuitry to transition between different states in order to transmit messages on one or more communication links.

Figure 3A is a flowchart illustrating an exemplary procedure for aggregating sensor data for transmission over a communication link.

Figure 3B is a flowchart illustrating an exemplary procedure for transmitting sensor data over a communication link.

Figure 4 is a flowchart of an exemplary procedure that can be executed in response to receiving a message from one or more sensors.

Figure 5 is a flowchart of an exemplary program that can be executed in response to the expiration of an interval timer.

Figure 6A is a message timing diagram illustrating exemplary messages transmitted between devices in a network.

Figure 6B is another message timing diagram illustrating exemplary messages transmitted between devices in a network.

Figure 6C is another message timing diagram illustrating exemplary messages transmitted between devices in a network.

Figure 7 is a simplified block diagram of an exemplary device.

Figure 8 is a simplified block diagram of an exemplary load control device.

Detailed Implementation

A better understanding of the foregoing invention and its specific embodiments will be achieved when read in conjunction with the accompanying drawings. Examples are illustrated in the drawings, with several views running throughout the drawings, and similar numbers denote similar parts. However, the drawings and description herein are not intended to be limiting.

Figure 1 is a simplified diagram of an exemplary load control system for controlling the amount of power delivered from an alternating current (AC) power source (not shown) to one or more electrical loads. The load control system 100 may include multiple control devices. These control devices may include multiple control source devices and multiple control target devices. For example, the control source devices may include input devices operable to transmit messages in response to user input, occupancy/vacancy status, measured changes in light intensity, and/or other input information. The control target devices may include, for example, load control devices operable to receive messages and/or control corresponding electrical loads in response to received messages. A single control device of the load control system 100 may function as both a control source device and a control target device.

The load control system 100 may include a wired system controller 110 (e.g., a system controller or load controller) operable to transmit messages to and/or receive messages from a control device on wired communication links (such as wired serial communication link 104) and wireless communication links (such as wireless input device communication link 106). The wireless input device communication link 106 may be a wireless communication link on which RF signals are transmitted from input devices in the load control system 100. The wireless input device communication link 106 may be a unidirectional wireless communication link.

As shown in Figure 1, the wired system controller 110 can be coupled to one or more control source devices and control target devices (e.g., which may include wired or wireless control devices) via a wired serial communication link 104 and/or a wireless input device communication link 106. For example, some wired control devices of the load control system 100 can use the wired serial communication link 104 to transmit messages to the wired system controller 110. Similarly, and as further described herein, some wireless control devices of the load control system 100 can transmit messages directly to the system controller 110 via the wireless input device communication link 106, or transmit messages to the system controller via the wired serial communication link 104 via a wireless adapter 158. The wireless adapter device 158 is coupled to both the wired serial communication link 104 and the wireless input device communication link 106, and is therefore able to receive RF signals via the wireless input device communication link 106 and transmit messages received via RF signals to the wired system controller 110 via the wired serial communication link 104. For example, the wireless adapter device 158 can retransmit messages received from the wireless controller over the wired serial communication link 104. Although shown as separate devices, the wireless system controller 111 and the wired system controller 110 may be part of the same device or include the functionality of the same device.

Wired system controller 110 can be configured to receive messages from a control source device and can transmit messages to a control target device in response to, for example, messages received from the control source device. Load control system 100 may include one or more load control devices that can be controlled in response to messages received from an input device. For example, load control system 100 may include a light-emitting diode (LED) driver 130 for controlling or driving a corresponding electrical load, such as an LED light source 132 (e.g., an LED light engine) and/or lighting fixtures 170, 172. LED driver 130 may be remotely located in a lighting fixture, for example, the corresponding LED light source 132. LED driver 130 may be configured to receive messages from wired system controller 110 via a wired serial communication link 104. LED driver 130 may be configured to control the corresponding LED light source 132 in response to received messages. LED driver 130 may include internal RF communication circuitry or be coupled to external RF communication circuitry (e.g., mounted externally to the lighting fixture, such as mounted on a ceiling) for transmitting and/or receiving messages using wireless input device communication link 106. The load control system 100 may also include other types of lighting control devices, such as electronic dimming ballasts for driving fluorescent lamps.

The load control device in the load control system 100 may include multiple daylight control devices, such as motorized window coverings, like motorized roller blinds 140. The load control system 100 may utilize multiple daylight control devices to control, for example, the amount of daylight entering a building in which the load control system 100 is installed. Each motorized roller blind 140 may include an electronic drive unit (EDU) 142. The electronic drive unit (EDU) 142 may be located inside the roller tube of the motorized roller blind. The electronic drive unit 142 is operable to communicate with the system controller 110 and/or other devices via wired and/or wireless communication links. The electronic drive unit 142 may be coupled to a wired serial communication link 104, for example, to transmit and receive messages. The electronic drive unit 142 may be configured to adjust the position of the window covering fabric in response to messages received from the wired system controller 110 via the wired serial communication link 104. Each electronic drive unit 142 may include internal RF communication circuitry or be coupled to external RF communication circuitry (e.g., located outside the roller tube), for example, to transmit and/or receive messages on a wireless input device communication link 106. The load control system 100 may include other types of daylight control devices, such as, for example, honeycomb blinds, canopies, Roman blinds, Venetian blinds, Persian blinds, pleated blinds, tension roller blind systems, electrochromic or smart windows, or other suitable daylight control devices.

The load control system 100 may include one or more other types of load control devices, such as, for example, a screw-in floodlight including a dimmer circuit and an incandescent or halogen lamp; a screw-in floodlight including a ballast and a compact fluorescent lamp; a screw-in floodlight including an LED driver and an LED light source; an electronic switch, a controllable circuit breaker, or other switching device for turning electrical appliances on and off; a plug-in load control device, a controllable electrical outlet, or a controllable power board for controlling one or more plug-in loads; a motor control unit for controlling motor loads, such as a ceiling fan or exhaust fan; and a drive unit for controlling electric window covers or a projection screen. Electric internal or external blinds; thermostats for heating and/or cooling systems; temperature control devices for controlling setpoint temperatures in HVAC systems; air conditioners; compressors; electric wall panel heater controllers; controllable dampers; variable air volume controllers; fresh air intake controllers; ventilation controllers; hydraulic valves for radiators and radiant heating systems; humidity control units; humidifiers; dehumidifiers; water heaters; boiler controllers; pool pumps; refrigerators; freezers; television or computer monitors; cameras; audio systems or amplifiers; elevators; power supplies; generators; chargers, such as electric vehicle chargers; and/or alternative energy controllers.

The load control system 100 may include one or more input devices, such as a wired keypad device 150, a wired daylight sensor 166, a battery-powered remote control device 152, a wireless occupancy sensor 154, and/or a wireless daylight sensor 156. The wired keypad device 150 may be configured to transmit messages to the system controller 110 via a wired serial communication link 104 in response to actuation of one or more buttons on the wired keypad device. For example, the wired keypad device 150 may be configured to transmit messages to the system controller 110 via a wired serial communication link 104 in response to actuation of one or more buttons on the wired keypad device 150. The messages may include an indication that a button has been pressed on the wired keypad device 150. The wired keypad device 150 may be adapted to be wall-mounted in a standard electrical box.

The wired daylight sensor 166 can be configured to measure (e.g., periodically measure) signals (e.g., photosensor or photodiode current). For example, the signal can be used to determine a value (e.g., sensor data) indicating the light intensity in the space where the wired daylight sensor 166 is mounted. The wired daylight sensor 166 can similarly be configured to transmit messages to the wired system controller 110 via a wired serial communication link 104. For example, the wired daylight sensor 166 can be configured to couple to a sensor interface 168. The wired daylight sensor 166 can periodically transmit messages (e.g., which may include the signal of the corresponding measurement) to the sensor interface 168 in response to periodic measurements. The sensor interface 168 can be configured to transmit messages to the system controller 110 via the wired serial communication link 104 in response to messages received from the wired daylight sensor 166. For example, the sensor interface 168 can periodically retransmit messages received from a wireless control device over the wired serial communication link 104. Additionally, sensor interface 168 can be configured to convert the signal measured by wired daylight sensor 166 into an appropriate value indicating the light intensity in the space (e.g., a daylight value, such as foot-candle or another daylight value). Sensor interface 168 can also transmit said value to system controller 110 via wired serial communication link 104. For example, said value can be used to control the intensity of one or more electrical loads (e.g., LED light source 132).

The battery-powered remote control 152, wireless occupancy sensor 154, and/or wireless daylight sensor 156 can be wireless control devices. For example, the battery-powered remote control 152, wireless occupancy sensor 154, and/or wireless daylight sensor 156 may include an RF transmitter (e.g., a unidirectional RF transmitter) configured to transmit messages to the wired system controller 110 directly or indirectly over a wired serial communication link 104 via the wireless input device communication link 106 to the wireless adapter 158. The wired system controller 110 may be configured to transmit one or more messages to a load control device (e.g., an LED driver 130 and/or an electric roller blind 140) in response to messages received from input devices (e.g., a wired keypad device 150, a battery-powered remote control 152, a wireless occupancy sensor 154, a wired daylight sensor 166, and/or a wireless daylight sensor 156).

The battery-powered remote control 152 can be configured to transmit messages to the wired system controller 110 in response to actuation of one or more buttons on the battery-powered remote control for controlling electrical loads in the load control system 100. The battery-powered remote control 152 can be configured to transmit messages to the wired system controller 110 directly via a wireless input device communication link 106 or indirectly via a wired serial communication link 104, either directly or indirectly by transmitting messages to a wireless adapter 158 via the wireless input device communication link 106. The messages may include indications of buttons pressed on the remote control 152.

The wireless occupancy sensor 154 can be configured to transmit messages to the system controller 110. The wireless occupancy sensor 154 can also be configured to transmit messages to the wired system controller 110 in response to sensing an occupancy/vacancy status for controlling electrical loads in the load control system 100. The wireless occupancy sensor 154 can be configured to transmit messages to the wired system controller 110 directly via the wireless input device communication link 106 or indirectly via the wireless adapter 158 on the wired serial communication link 104. The wireless occupancy sensor 154 can transmit messages including an occupancy or vacancy status identified by the occupancy sensor 154. Examples of RF load control systems with wireless occupancy and idle sensors are described in more detail in the following patents: U.S. Patent No. 8,009,042, entitled “RADIO-FREQUENCY LIGHTING CONTROLSYSTEM WI TH OCCUPANCY SENSING,” published August 30, 2011; U.S. Patent No. 8,199,010, entitled “METHOD AND APPARATUS FORCONFIGURING A WIRELES S SENSOR,” published June 12, 2012; and U.S. Patent No. 8,228,184, entitled “BATTERY-POWERED OCCUPANCY SENSOR,” published July 24, 2012, the entire disclosure of which is hereby incorporated by reference.

The wireless daylight sensor 156 can be configured to measure (e.g., periodically measure) signals (e.g., photosensor or photodiode current), as described herein, which can be used to determine sensor data (e.g., a value indicating the light intensity in the space where the wireless daylight sensor 156 is mounted). The wireless daylight sensor 156 can be configured to transmit a message including the periodically measured signal to the wired system controller 110 for controlling one or more electrical loads in the load control system 100 in response to the light intensity in the space. The wireless daylight sensor 156 can be configured to transmit messages to the wired system controller 110 directly via the wireless input device communication link 106 or indirectly via the wireless adapter 158 over a wired serial communication link 104.

The input device in the load control system can determine whether to transmit a message including a measurement signal based on a certain transmission standard, for example, to conserve battery power and/or resources on the wireless input device communication link 106. In one example, a sensor device can perform measurements and determine whether to transmit a message on the wireless input device communication link 106 based on a certain transmission standard. For example, a wireless sunlight sensor 156 can perform periodic measurements and determine whether to transmit the measurement in a message based on a transmission standard stored at the wireless sunlight sensor 156. According to the transmission standard, the wireless sunlight sensor 156 can determine to transmit a message including a measurement signal when the measurement has changed by at least a threshold amount. The wireless sunlight sensor 156 can also determine not to transmit a message including a measurement signal when the rate of change of the measurement signal is too high (e.g., greater than a threshold) (which could indicate that clouds are passing over the sun from time to time). Examples of RF load control systems with daylight sensors are described in more detail in commonly assigned U.S. Patent No. 8,410,706, entitled “METHOD OF CALIBRATING A DAYLIGHT SENSOR,” published April 2, 2013, and U.S. Patent No. 8,451,116, entitled “WIRELESS BATTERY POWERED DAYLIGHT SENSOR,” published May 28, 2013, the entire disclosure of which is hereby incorporated by reference.

As described herein, the wireless daylight sensor 156 (e.g., or other wireless input device) can be configured to transmit messages including sensor data (e.g., for controlling the intensity of one or more electrical loads) according to a certain transmission standard. For example, at certain times of the day (e.g., around noon and/or in the evening), the changes in sensor data measurements during this period may be small or negligible and may not reach a threshold level that triggers a change in electrical load control. At certain times of the day, transmitting a message after each measurement may overload the wireless input device communication link 106 (e.g., causing increased message processing at the devices in the load control system 100 and/or interference due to the inability to receive RF signals on the wireless input device communication link 106 due to increased message transmission) and/or deplete the battery, with little to no effect on the electrical load. However, at other times of the day, the changes in sensor data measurements may be perceptible and may reach or exceed a threshold level that triggers a change in electrical load control.

To balance message transmission, the wireless sunlight sensor 156 can transmit messages in response to predefined transmission criteria. For example, the wireless sunlight sensor 156 can be configured to perform measurements and determine whether to transmit each measurement in response to the transmission criteria. In another example, the wireless sunlight sensor 156 can accumulate samples of sunlight levels measured over a predefined period of 15 seconds (e.g., 10 samples every 1.5 seconds). The wireless sunlight sensor 156 can then analyze the samples of sensor data accumulated during that period and determine whether the transmission criteria are met to trigger the transmission of sensor data in one or more messages.

Different emission standards can define different thresholds for transmitting messages in response to sensor data measured at a sensor device such as daylight sensor 156. For example, a specification standard can be defined for transmitting messages from the sensor device during normal operation when the specification standard is met. When a large measurement change is detected, a sensor device such as daylight sensor 156 can respond more quickly to the measurement change to perform control in a load control environment.

In one example, the wireless daylight sensor 156 can be configured with a specification criterion to enable message transmission during normal operation when the specification criterion is met. The specification criterion can be used to define a stable period in which sensor data (e.g., daylight values such as foot-candles or other daylight values measured or calculated by a photoelectric sensor current, temperature values, color temperature values, etc.) are relatively stable, and to allow sensor data transmission when a threshold change in the sensor data is identified within the stable period. The specification criterion can prevent message transmission when the sensor data is relatively stable and allow transmission when a threshold change in the sensor data is detected. A specification criterion can be met when both the stability criterion identifying the stable period of sensor data and the change criterion identifying the threshold change are met. A stability criterion can be met when the lowest sensor data measured within a predefined period and the highest sensor data measured within a predefined period are within each other's predefined ranges. For example, a stability criterion can be met when the lowest and highest sensor data measured within a predefined period are within 10% of each other or within each other's predefined values. Referring again to the wireless daylight sensor 156, the stability criterion is met when the lowest and highest daylight levels measured within a predefined time period are within 10% of each other or within two feet of each other.

A change criterion is met when the current measurement in the sensor data has changed by more than or equal to one or more predefined thresholds relative to previously reported sensor data. For example, the wireless daylight sensor 156 can determine that a change criterion is met when the current measurement of daylight level has changed by more than or equal to 15% and/or more than or equal to two foot-candles relative to previously reported sensor data. If the specification criteria are met (e.g., the change criterion is met, or both the stability criterion and the change criterion are met), the wireless daylight sensor 156 can transmit the sensor data of the current measurement because a threshold change has been detected since the stable period.

The wireless daylight sensor 156 can also be configured with a fast response criterion for transmitting a message, for example, when a relatively rapid change in measured sensor data is detected (e.g., a rapid change in daylight level). The fast response criterion may include one or more thresholds indicating a change in threshold amount greater than a specified criterion. If a rapid change in sensor data (e.g., daylight values such as foot-candles or other daylight values, temperature values, color temperature values, etc.) is detected between consecutive measurements, the wireless daylight sensor 156 may trigger the transmission of a message indicating the rapid change in sensor data. For example, the wireless daylight sensor 156 may determine whether a predefined number of consecutive measurements of daylight level (e.g., two consecutive measurements) meet the fast response criterion. The fast response criterion may be met when the most recently measured sensor data is below a predefined threshold (e.g., 5 foot-candles) and/or the difference between previously transmitted sensor data and the most recently measured sensor data is greater than one or more predefined thresholds (e.g., greater than 10 foot-candles and/or greater than 20%). If the fast response criterion is met, the wireless sunlight sensor 156 can transmit the most recently measured sensor data to provide a measurement that triggers the transmission.

If a fast response criterion is met, the wireless sunlight sensor 156 can also transmit a predefined number of subsequently accelerated update messages for the sensor data to be measured within a predefined time period. For example, the wireless sunlight sensor 156 can transmit sensor data subsequently measured at zero seconds (e.g., the time of the transmission event), 6 seconds, 12 seconds, 24 seconds, 36 seconds, 48 seconds, and/or 60 seconds. The transmission time of the update messages can be selected based on the sensor data to reduce oscillations in the electrical load while providing more frequent sensor data updates.

The wireless daylight sensor 156 can also be configured to periodically transmit sensor data in a heartbeat message (e.g., as a supplement to other transmissions or independently of other transmissions). For example, when a heartbeat criterion is met, the wireless daylight sensor 156 may transmit a heartbeat message including sensor data. The heartbeat criterion may define a period of time (e.g., 60 to 68 minutes) for periodically transmitting currently measured sensor data. In the example, the wireless daylight sensor 156 may transmit a heartbeat message including the current daylight level after the defined period of time to inform other devices that sensor data measured after the extended period of time and/or that the sensor is still communicating or operating normally. Examples of transmitting messages including sensor data according to transmission criteria are described in more detail in co-assigned U.S. Patent Application Publication No. 2010/0244709, entitled “Wireless Battery-Powered Daylight Sensor,” published September 30, 2010, the entire disclosure of which is hereby incorporated by reference.

Although the wireless daylight sensor 156 is provided as an example, other types of devices or sensors can be similarly implemented to perform measurements and transmit messages in response to transmission standards. For example, a temperature sensor can measure the temperature of a space and transmit a temperature measurement in response to a transmission standard (e.g., to balance message transmission as sensor data changes with temperature) to control an HVAC system. A color temperature sensor can measure the color temperature of a lighting load and transmit a color temperature measurement in response to a transmission standard (e.g., to balance message transmission as sensor data changes with color temperature) to control the color temperature of the lighting load. These sensors can similarly include specification standards for transmitting messages during normal operation, fast-response standards for transmitting messages in response to relatively large changes in sensor measurements, and/or heartbeat standards for sending heartbeat messages after a period of time.

The load control system 100 may include other types of input devices, such as, for example, temperature sensors, color temperature sensors, humidity sensors, radiometers, cloudy day sensors, shading sensors, pressure sensors, smoke detectors, carbon monoxide detectors, air quality sensors, motion sensors, safety sensors, proximity sensors, appliance sensors, zone sensors, keypads, multi-zone control units, slider control units, powered or solar-powered remote controls, key fobs, cellular phones, smartphones, tablet computers, personal digital assistants, personal computers, laptop computers, clocks, audio-visual controls, safety devices, power monitoring devices (e.g., power meters, energy meters, utility meters, rate meters, etc.), central control transmitters, residential controllers, commercial controllers, industrial controllers, or any combination of input devices.

The operation of the load control system 100 can be programmed and/or configured to be stored at one or more system controllers and/or control devices using a personal computer 164 or other network device. The personal computer 164 can execute graphical user interface (GUI) configuration software to allow users to program how the load control system 100 can operate. The configuration software can generate a load control database that defines the operation of the load control system 100. For example, the load control database may include information about the operating settings of different load control devices of the load control system 100 (e.g., LED driver 130 and/or motorized roller blind 140). The load control database may include information about the association between the load control devices and input devices (e.g., wired keypad device 150, battery-powered remote control device 152, wireless occupancy sensor 154, wired daylight sensor 166 and/or wireless daylight sensor 156), and information about how the load control devices respond to input received from the input devices. The load control database, or portions thereof, may be transmitted via wired and/or wireless communication links to one or more system controllers and/or control devices for storage thereon. Examples of configuration procedures for load control systems are described in more detail in commonly assigned U.S. Patent No. 7,391,297, entitled “HANDHELD PROGRAMMERFOR A LIGHTING CONTROL SYSTEM”, published June 24, 2008; U.S. Patent Application Publication No. 2008/0092075, entitled “METHOD OF BUILDING A DATABASE OF A LIGHTING CONTROL SYSTEM”, published April 17, 2008; and U.S. Patent Application Publication No. 2014/0265568, entitled “COMMISSIONING LOAD CONTROL SYSTEMS”, published September 18, 2014, the entire disclosure of which is hereby incorporated by reference.

Wired system controller 110 can receive messages from input devices to be relayed to load control devices configured to control electrical loads. The wired system controller can be operated to couple to a network, such as a wireless local area network (LAN), via a wired network communication link 160 (e.g., an Ethernet communication link) to access, for example, the Internet. Wired system controller 110 can be connected to switch 162 (or an Ethernet switch) via wired network communication link 160 to allow it to communicate with additional system controllers (such as wireless system controller 111) to control additional electrical loads, such as lighting fixtures 170, 172, that can communicate with the wireless system controller. For example, wired system controller 110 can receive messages from input devices and (e.g., based on association information that associates the input devices with one or more load control devices) determine that the messages will be forwarded to another system controller, such as wireless system controller 110, to be relayed to load control devices, such as lighting fixtures 170, 172, with which the wireless system controller can perform communication.

The wireless system controller 111 can be configured to communicate with the wired system controller 110 via a wired network communication link 160. The wireless system controller 111 can also operate to transmit and receive messages via a wireless network communication link 107. For example, the wireless system controller 111 may be able to communicate with control devices (e.g., lighting devices 170, 172) via the wireless network communication link 107. The wireless network communication link 107 can be used to transmit messages via RF signals. The wireless network communication link 107 may differ from the wired serial communication link 104 and/or the wireless input device communication link 106. For example, the RF wireless network communication link 107 may utilize a different channel and/or a different communication protocol than the wireless input device communication link 106.

As shown in Figure 1, the wireless system controller 111 may be able to communicate via a wireless network communication link 107 with one or more control source devices and/or control target devices (such as lighting devices 170, 172). Lighting devices 170, 172 may include controllable light sources similar to LED light source 132. For example, lighting devices 170, 172 may include lighting control devices, such as LED drivers, capable of controlling the color and/or intensity of the controllable light source (such as LED light source). Lighting devices 170, 172 may be controlled in response to messages including data (e.g., control data and/or sensor data) transmitted by one or more input devices (such as a wired keypad device 150, a battery-powered remote control device 152, an occupancy sensor 154, a wired daylight sensor 156, a wireless daylight sensor 166, a temperature sensor, a color temperature sensor, etc.). These messages, including data for performing control, can be received by the wireless system controller 111, and the wireless system controller 111 can then determine, based on the data, whether to transmit a message (e.g., or the data included in the message) on the wireless network communication link 107 (e.g., for controlling lighting devices 170, 172).

The wireless system controller 111 can receive messages including data (e.g., control data, sensor data, etc.) for performing control over one or more devices (e.g., lighting devices 170, 172) on the wireless network communication link 107. The wireless system controller 111 can determine (e.g., based on associations in a load control database) that the data is associated with a load control device coupled to the wireless network communication link 107 (e.g., it can be used to control the load control device). For example, this determination can be made using association information stored in the load control database. In response to receiving such a message, the wireless system controller 111 can determine whether to transmit the received data on the wireless network communication link 107 based on a transmission standard.

After determining that data will be transmitted on the wireless communication network utilizing RF signal 107, the wireless system controller 111 can be configured to format and/or aggregate the received data for transmission in a message via the wireless network communication link 107. As described herein, the frequency at which the wireless system controller 111 receives messages can vary among the various devices transmitting messages. For example, as described herein, the wired daylight sensor 166 can be configured to periodically transmit messages including sensor data, while the wireless daylight sensor 156 can be configured to transmit messages including sensor data based on a transmission criterion (e.g., when the measured sensor data changes a predefined threshold within a predefined time period). Due to the different frequencies of message transmission, the wireless system controller 111 can periodically receive messages from some devices and periodically receive messages from other devices. As a result, the wireless system controller can be configured to aggregate data received within a predefined time period and periodically transmit the aggregated data on the wireless network communication link 107.

If the wireless system controller 111 forwards messages (e.g., data included in the messages) to devices coupled to the wireless network communication link 107 (e.g., lighting devices 170, 172) at the frequency at which messages are received, other messages transmitted on the wireless network communication link 107 may be unduly interfered with. In the example, the communication protocol of the wireless network communication link 107 may utilize multicast or broadcast messages, which could cause sensor devices (e.g., occupancy sensor 154, daylight sensors 156, 166, temperature sensors, color temperature sensors, etc.) to transmit one or more broadcast or multicast messages on the wireless network communication link 107 each time a measurement is performed. These broadcast or multicast messages can interfere with the wireless network communication link 107 because the additional messages may be transmitted at a relatively high frequency. Therefore, as described herein, the wireless system controller 111 may format the received data transmitted in the messages for transmission via the wireless network communication link 107 to limit the possibility of interference with other messages transmitted via the wireless communication network link 107.

The wireless system controller 111 can be configured to aggregate received messages or data and efficiently distribute and/or transmit these messages to devices coupled to the wireless network communication link 107. For example, the wireless system controller 111 can aggregate messages or data received from each device over a period of time. Regarding the aggregation of messages including data from one or more input devices, the wireless system controller 111 can, for example, be configured to maintain or store received messages or data based on the respective device from which the messages or data are received. For example, after receiving a message including sensor data received from sensor devices (e.g., daylight sensors 156, 166, occupancy sensor 154, etc.), the wireless system controller 111 can be configured to maintain the sensor data received from each of the one or more sensor devices. The wireless system controller 111 can then independently determine whether the sensor data received from the respective sensor device should be transmitted to the device on the wireless network communication link 107. For example, the wireless system controller 111 can process the received sensor data to determine whether it meets the transmission criteria for transmission to the device on the wireless network communication link 107 (e.g., similar to the transmission criteria described herein with respect to the wireless daylight sensor 156 for achieving efficient communication on a wireless communication network). Determining whether to transmit sensor data based on transmission criteria allows the wireless system controller 111 to consider the frequency of changes when receiving messages that include sensor data. The transmission criteria can also allow the wireless system controller 111 to consider whether changes in the sensor data are perceptible (e.g., whether changes in the sensor data reach or exceed a threshold level to trigger changes in electrical load control).

The wireless system controller 111 can be configured to transition between multiple states. For example, the wireless system controller 111 may have computer-executable instructions stored thereon that, when executed by control circuitry, cause the control circuitry to execute a local state machine capable of transitioning between states for transmitting messages. The state machine can be configured to transition between two or more states.

As described herein, the state machine can transition between corresponding states based on transmission criteria. For example, the state machine can transition between corresponding states based on the expiration of an interval timer or based on whether sensor data is received from the corresponding sensor device for transmission to the device on the wireless network communication link 107. Depending on the corresponding state of the state machine executed on the wireless system controller 111, the wireless system controller can aggregate sensor data received from each of the sensor devices within a predefined time period and package the aggregated sensor data received within said time period for transmission to the device (e.g., lighting devices 170, 172) on the wireless network communication link 107 in one or more messages. That is, the wireless system controller 111 can transition between various states in response to sensor data from a given sensor and/or determining that the transmission criteria are met for a given sensor. As a result, the state of the wireless system controller 111 may depend on the received sensor data and/or the transmission criteria may also change over time.

Although some techniques and procedures are described herein as being performed by a wireless system controller, they can also be performed by other devices in a load control system. For example, the techniques and procedures can also be performed, or alternatively, by a wired system controller (e.g., wired system 110 shown in Figure 1). Wireless system controller 111 and wired system controller 110 can be the same device. Similarly, although some examples are described in the context of sensor data or specific sensor data (such as daylight sensor data), these techniques can also be used to receive, package, or transmit sensor data from other types of sensors or other types of data from control devices over a communication link and/or transmit said data to another communication link. Furthermore, the type of communication link (e.g., wired or wireless communication links including different communication protocols) is similarly non-limiting. That is, the techniques described herein can be used to facilitate communication between a first communication link associated with a first protocol, transmission scheme, and/or message format and a second communication link associated with a second protocol, transmission scheme, and/or message format.

Figure 2A is a state machine diagram illustrating the operation of an exemplary program 200 (e.g., a state machine program), which can be executed by control circuitry to transition between different states in order to transmit messages on one or more communication links (such as wireless network communication link 107 shown in Figure 1). For example, program 200 can be executed by the control circuitry of a system controller (such as wireless system controller 111 or wired system controller 110 shown in Figure 1). Although the system controller may be provided as an exemplary device on which program 200 or a portion thereof can be implemented, program 200 or a portion thereof can be executed by the control circuitry of a sensor device that transmits messages or by another device capable of performing wired and/or wireless communications as described herein.

As shown in Figure 2A, the control circuitry can be configured to transition between idle state 204 and transmit state 206. Idle state 204 can be a heartbeat state or another state in which the control circuitry remains idle for a period of time. Although a single transmit state 206 is shown in Figure 2A, one or more transmit states can be implemented to transmit one or more messages in response to a transmit criterion, as described herein (e.g., as shown in Figure 2B). Furthermore, although the different states are being implemented via a state machine as an example, the control circuitry can similarly track or control message transmission via other information or models stored and/or executed by the control circuitry. For example, the control circuitry can set the state of a transmit flag and store it in memory. As described with respect to transmit state 206 and idle state 204 respectively, the transmit flag can be set to enable transmission or indicate an idle period.

Program 200 can begin execution at 202. For example, the control circuitry can execute program 200 at 202 after the system controller is powered on. The control circuitry can default to an idle state 204 after power-on. When the control circuitry enters idle state 204, it can set an interval timer to an idle interval period. In one example, the idle interval period can be a heartbeat interval period (e.g., approximately 60 minutes, as described herein). The idle interval period can be randomized within a predefined range (e.g., approximately 60 to 68 minutes) to allow for offsets in heartbeat transmissions from multiple system controllers. The idle interval period can allow the control circuitry to delay transmissions on the communication link while simultaneously allowing it to enter a transmission state to transmit messages (e.g., heartbeat messages) at periodic intervals to devices (e.g., lighting devices 170, 172) on the communication link.

The control circuitry can enter or transition to transmit state 206 to enable the transmission of one or more messages containing sensor data over the communication link. The control circuitry can enter transmit state 206 when one or more transmit criteria are met. Transmit criteria can be met when an interval timer set by the control circuitry expires or when sensor data from one or more sensor devices that meet predefined criteria are received. For example, the control circuitry can identify that an idle interval period set during idle state 204 has expired.

When the control circuit is in idle state 204 and the idle interval period has elapsed, the control circuit can set a transmission count (e.g., transmission count = 1) for each of the sensor devices that has met the transmission criteria, and can enter or transition to transmission state 206 to perform transmission of a message (e.g., a heartbeat message) including sensor data from each of the sensor devices. A message transmitted after the idle interval period may include previously measured sensor data, recently received measured sensor data, or previously transmitted measured sensor data transmitted in a message for each of the sensor devices before the idle interval period. The interval timer can be set to null or zero when entering transmission state 206 so that the control circuit transmits a message upon entering transmission state 206, since the control circuit may have delayed transmission for a period of time. In another example, the control circuit can set the interval timer to a predefined time period (e.g., approximately 6 seconds) and transmit a message on the wireless network communication link when the interval timer expires.

After transmitting a message in transmit state 206, the control circuit can decrement the transmission count for each sensor transmitting sensor data and set an interval timer for a predefined time period after message transmission. For example, the control circuit can decrement the transmission count for each sensor by one and set the interval timer for a predefined time period or transmission delay time (e.g., approximately 6 seconds). At 210, the control circuit can wait for the predefined time period or transmission delay time after message transmission. When the interval timer expires while the control circuit is in transmit state 206, the control circuit can determine whether any sensor device has measured the sensor data to be transmitted (e.g., a transmission count greater than zero). If no other sensor device has measured sensor data to be transmitted and no other transmission criteria are met while the control circuit is in transmit state 206, the control circuit can return to idle state 204 at 212. The control circuit can set the interval timer for an idle interval period (e.g., a heartbeat interval period) and start the interval timer when the control circuit enters idle state 204.

Other transmission criteria can be identified for causing the control circuitry to increment the transmit count of a given sensor device and transition to or maintain transmit state 206 to enable transmission on the communication link. These other transmission criteria may be based on measurement sensor data received at the control circuitry from one or more sensor devices. As described herein, transmission criteria may take into account the frequency of changes when the control circuitry can receive messages including sensor data and/or whether changes in the sensor data are perceptible (e.g., whether changes in the sensor data reach or exceed a threshold change level to trigger control changes of devices coupled to the wireless network communication link).

The transmission criteria may include specification criteria that can be identified to trigger control circuitry to increment the transmission count of a given sensor and transmit a message in transmission state 206. The specification criteria may identify the amount of threshold change in the measured sensor data received from the sensor device. The specification criteria may be used to define a stable time period in which the sensor data in the message received from the sensor device is relatively stable compared to other time periods where the sensor data changes more rapidly. When a threshold change in the sensor data is detected during a stable time period, the specification criteria may allow the control circuitry to continue aggregating the sensor data from the sensor device and transmitting the sensor data over the wireless communication link. In the example, when the received sensor data indicates that both the stability criterion and the change criterion are met for that sensor, the control circuitry may determine that the specification criteria for performing the transmission are met, as described herein. A stability criterion may be met at the control circuitry when the lowest sensor data received by the control circuitry from the sensor device within a predefined time period and the highest sensor data received by the control circuitry from the sensor device within a predefined time period are within each other's predefined ranges to indicate a certain level of stability of the sensor data over a period of time. For example, a stability criterion is met when the lowest and highest sensor data measured within a predefined time period are within 10% of each other or within each other's predefined values. Taking a wireless sunlight sensor as an example, a stability criterion is met when the lowest and highest sunlight levels received from the sensor within a predefined time period are within 10% of each other or within two feet of each other.

When sensor data is within a stable period indicated by a stability criterion, the control circuitry can continue to aggregate the sensor data and prevent the transmission of sensor data until a change criterion is met. The control circuitry can continue to reset the interval timer to a predefined time period in which the stability criterion is maintained within a predefined range. As the stability criterion continues to indicate that the sensor data is within a stable period, the control circuitry can determine whether a change criterion used to trigger transmission is met. In another example, the control circuitry can rely on the change criterion as a threshold change amount for a specification standard. The change criterion can identify when a threshold change amount of sensor data is exceeded and allow the transmission of sensor data to provide an update on the identified change. A change criterion can be met at the control circuitry when the sensor data recently received from the sensor device differs from previously reported sensor data by more than or equal to one or more predefined thresholds. For example, the control circuitry can determine that a change criterion is met when the current value of the sunlight level received from the sunlight sensor has changed by more than or equal to 15% and/or more than or equal to a total predefined amount (such as two foot candles) relative to previously reported sensor data in a previously transmitted message. Although the change criterion is indicated as the amount of threshold change relative to previously received sensor data, it can also be indicated as the amount of threshold change relative to previously measured or previously transmitted sensor data. The change criterion can also be the rate of threshold change over a period of time.

If a given sensor device meets a specification criterion (e.g., meets a variation criterion, or both a stability criterion and a variation criterion), the control circuit can increment the transmit count of that sensor device by the specification count (e.g., 1) and transition to transmit state 206. The specification count may vary over time. For example, the specification count may initially be set to a first value, which may increase and/or decrease over time. If the specification count varies over time, it can be a function of the specification count over time (e.g., the maximum value of the specification count over time). An interval timer may be set to null or zero when transitioning from an idle state to cause the control circuit to transmit a message upon entering transmit state 206, since the control circuit may have delayed the transmission for a period of time. In another example, the control circuit can set the interval timer to a predefined time period (e.g., approximately 6 seconds) and transmit a message on the wireless network communication link when the interval timer expires. The transmitted message may include an update to measured sensor data or an amount of change in sensor data relative to previously transmitted messages from each sensor device with a transmit count greater than 1.

After transmitting a message in transmit state 206, the control circuit can decrement the transmission count for each sensor device transmitting sensor data and set an interval timer to a transmission interval after message transmission. This transmission interval can be a predefined time period. For example, the control circuit can decrement the transmission count by one and set the interval timer to a predefined time period of the transmission interval. At 210, the control circuit can wait for the predefined time period after message transmission. When the interval timer expires while in transmit state 206, the control circuit can determine if any sensor device has measured the sensor data to be transmitted (e.g., a transmission count greater than zero). If no other sensor device has measured sensor data to be transmitted and no other transmission criteria are met while in transmit state 206, the control circuit can return to idle state 204 at 212. The control circuit can then set the interval timer to an idle interval period and start the interval timer upon entering idle state 204.

Other transmission criteria can be identified to cause the control circuitry to increment the transmit count of a given sensor and transition to or maintain transmit state 206 to enable transmission on the communication link. For example, a transmission criterion could include a fast response criterion, which can be identified to trigger the control circuitry to set a transmit count for a given sensor device and transmit a message in transmit state 206. Compared to sensor data changes detected by a specification criterion, a fast response criterion can be used to detect relatively large or relatively rapid changes in the measured sensor data accumulated from a given sensor, allowing for faster control of the electrical load communicating on the communication link in response to rapid changes in sensor data. A fast response criterion can be satisfied when the most recently measured sensor data is below a predefined threshold and/or the difference between previously transmitted sensor data and the most recently measured sensor data is greater than one or more predefined thresholds. Therefore, satisfying the fast response criterion for a given sensor device allows the control circuitry to set a transmit count for transmitting the measured sensor data from the sensor device while in transmit state 206 and to transmit sensor data in response to relatively rapid changes in sensor data to perform faster control of the electrical load. Although the fast response criterion is described as indicating the amount of threshold change relative to previously received sensor data, it can also be indicated as the amount of threshold change relative to previously measured or previously transmitted sensor data. A fast response criterion can also be the rate of threshold change over a period of time.

The control circuit can determine that a fast response criterion is met when the most recently received sensor data for the corresponding sensor is below a predetermined threshold or when the difference between the sensor data previously transmitted from the control circuit for the sensor device and the most recently received sensor data for the sensor device is greater than one or more predefined thresholds. For example, when the type of sensor device from which sensor data is received is a daylight sensor, the control circuit can determine that a fast response criterion is met when the most recently received sensor data for the daylight sensor is below 5 foot-candles and/or the difference between the previously transmitted sensor data for the daylight sensor and the most recently received sensor data for the sensor device is greater than 10 foot-candles and/or greater than a 20% variation (e.g., increase or decrease).

When a given sensor device meets the fast response criterion, the control circuit can set the transmission count of that sensor device to a fast response count (e.g., 11) to attempt to control the electrical load in response to rapid changes in sensor data through a series of transmissions. As described herein, the transmission count of a given sensor device can indicate the number of times sensor data measured by that sensor device is to be transmitted over the communication link. The fast response count can be, for example, a predefined count stored in memory and can indicate the number of subsequent sensor data values to be transmitted by that sensor over the wireless network communication link. If the control circuit is not already in transmission state 206, it can transition to transmission state 206 to enable the transmission of sensor data from the sensor device over the communication link. If the control circuit is already in transmission state 206 and is performing a transmission for another sensor device, it can remain in transmission state 206 and continue transmitting messages over the communication link. The messages can include sensor data for each sensor with a transmission count greater than zero.

After each transmission in transmit state 206, the control circuit can wait at 210 for a predefined transmission interval. When the interval timer expires while in transmit state 206, the control circuit can determine if any sensor device has measured the sensor data to be transmitted (e.g., a transmission count greater than zero). If any sensor device still has the sensor data to be transmitted (e.g., a transmission count greater than zero), the control circuit can remain in transmit state 206 and continue transmitting messages for those sensor devices. If no other sensor device has the measured sensor data to be transmitted and no other transmission criteria are met while in transmit state 206, the control circuit can return to idle state 204 at 212. The control circuit can set the interval timer to an idle interval period and start the interval timer upon entering idle state 204.

Although Figure 2A illustrates a program 200 that can be executed according to a state machine having two states, the control circuitry can implement a state machine with more than two states to enable transmission on a communication link. For example, Figure 2B is a state machine diagram illustrating an exemplary program 250 (e.g., a state machine program) that can be executed by the control circuitry according to the state machine to transition between three states in order to transmit messages on a communication link (such as the wireless network communication link 107 shown in Figure 1). Program 250 can be executed by the control circuitry of a system controller (such as the wireless system controller 111 or the wired system controller 110 shown in Figure 1). Although the system controller can be provided as an exemplary device on which program 250 or a portion thereof can be implemented, program 250 or a portion thereof can be executed by the control circuitry of a sensor device for transmitting messages or by another device capable of performing wireless and/or wired communication as described herein.

As shown in Figure 2B, the control circuit can be configured to transition between heartbeat state 254, fast state 256, and backoff state 258. Program 250 can begin execution at 252. For example, the control circuit can begin executing program 250 at 252 after the system controller is powered on. The control circuit can default to heartbeat state 204 after power-on. When the control circuit enters heartbeat state 204, the control circuit can set an interval timer to a heartbeat interval period (e.g., approximately 60 minutes or randomized between approximately 60 minutes and approximately 68 minutes, as described herein).

When in heartbeat state 254, the control circuitry can monitor the interval timer and sensor data received from each of the sensor devices to identify the transmission criteria. As described herein, the transmission criteria can be met when the interval timer expires. After the heartbeat interval period expires, the control circuitry can detect that the transmission criteria have been met for one or more sensor devices. Upon the expiration of the heartbeat interval period, the control circuitry can increment the transmission count (e.g., transmission count = 1) for each sensor device that has met the transmission criteria and can transmit a heartbeat message.

After transmitting a heartbeat message, the control circuit can decrement the transmission count for each sensor device (e.g., for each sensor device that transmitted a heartbeat message) and transition to a backoff state 258 at 262. The backoff state allows the control circuit to wait for a predefined transmission interval (e.g., approximately 6 seconds) before transmitting another message or transitioning to another state after transmission. The control circuit can set an interval timer to the predefined transmission interval and start the interval timer upon entering backoff state 258. The backoff state allows the control circuit to wait for a predefined period after each message transmission. If, while in backoff state 258, no other sensor device has sensor data to transmit when the interval timer expires and other transmission criteria are not met for the sensor device, the control circuit can transition to a heartbeat state 254 at 268. Upon entering heartbeat state 254, the control circuit can set an interval timer to the heartbeat interval period and start the interval timer for another potential heartbeat message transmission for each of the sensor devices.

As described herein, the control circuitry can similarly monitor received sensor data, which is accumulated to indicate whether a specification standard or a fast response standard is met. If the measured sensor data based on a given sensor device meets the specification standard, the transmission count of that sensor device can be incremented. The control circuitry can transmit a message containing the measured sensor data of that sensor and decrement the sensor count of that sensor device after transmission. After transmitting the message, the control circuitry can set an interval timer to a predefined period of time for the transmission interval and start the interval timer when entering backoff state 258.

The control circuitry can also monitor received sensor data, which is accumulated to identify whether a fast response criterion is met. If the measured sensor data based on a given sensor device meets the fast response criterion, the transmit count of that sensor device can be set to a fast response count (e.g., 11). Upon detecting that the fast response criterion is met for a given sensor device, the control circuitry can transition to a fast state 256 at 260. The control circuitry can transmit a message for each sensor device that has a transmit count greater than 1 in fast state 256. After each transmission, the control circuitry can decrement the transmit count for each sensor device for which sensor data has been transmitted and transition to a backoff state 258 at 264. Alternatively, the state machine can remain in fast state 256 until the transmit count for each sensor device is less than 1. In such an implementation, after the transmit count for each sensor device is less than 1, the state machine can transition to backoff state 258 at 264.

After each transmission in backoff state 258 or fast state 256, the control circuitry can wait for a predefined period of the transmission interval. If, in backoff state 258, additional sensor devices have a remaining transmission count and/or otherwise meet the fast response criteria after the fast response criteria are identified, the control circuitry can return to the fast state at 266. After a transmission message, the control circuitry can set the interval timer to the predefined period of the transmission interval and start the interval timer when entering backoff state 258.

Figures 3A and 3B illustrate exemplary programs 300 and 320 for aggregating sensor data for transmission over a communication link and for transmitting sensor data over a communication link, respectively. Programs 300 and 320 can be executed by a system controller (e.g., wired system controller 110 and/or wireless system controller 111 of Figure 1). Although programs 300 and 320 can be described as being executed by a system controller, another control device in a load control system (e.g., a lighting control device, a sensor device, or another control device) can execute programs 300 and 320 or one or more portions thereof. Programs 300 and 320 can be stored in a memory as a computer-readable or machine-readable storage medium and can be executed by control circuitry of one or more devices for executing the program. Programs 300 and 320 can be executed in parallel to allow program 300 to aggregate sensor data while program 320 transmits sensor data.

As shown in Figure 3A, program 300 may begin at 302. For example, the control circuitry of the system controller may begin executing program 300 upon receiving measurement sensor data in a message or upon the expiration of an interval timer. As described herein, the sensor data may be transmitted (e.g., initially transmitted) by sensor devices (e.g., wired daylight sensor 166 and/or wireless daylight sensor 156) and may be used to control one or more electrical devices (e.g., lighting devices 170, 172) over a wireless network communication link. At 304, the control circuitry may determine whether sensor data has been received. When sensor data is received at 304, the control circuitry may store the received sensor data in memory at 306. Sensor data may be received from different sensor devices at 304 and stored in memory at 306 along with a unique identifier of the sensor device from which sensor data has been received. The control circuitry may continue to aggregate sensor data from different sensors for transmission in response to meeting transmission criteria.

At 308, the control circuitry can determine whether a transmission criterion has been met for at least one sensor device. The transmission criterion may include the expiration of an interval timer (e.g., the expiration of an idle or heartbeat interval). The transmission criterion may include specification criteria and/or fast response criteria, as described herein. When it is determined that a transmission criterion has not been met for at least one sensor device, procedure 300 may return to 304 and the control circuitry may continue to monitor sensor data or the expiration of the interval timer to determine whether the transmission criterion has been met.

In response to the emission criterion being met at 308, the control circuitry can update the emission count of the sensor device that met the emission criterion at 310. The control circuitry can aggregate sensor data and/or update the sensor emission count in any state. For example, in a two-state machine, the control circuitry can aggregate and/or update the sensor emission count when in an idle or emission state. In a three-state machine, the control circuitry can aggregate and/or update the sensor emission count when in a heartbeat state, a fast response state, and/or a backoff state. In response to the expiration of an idle interval or heartbeat interval, the control circuitry can update the emission count (e.g., increment to 1) for each sensor device whose idle or heartbeat interval has expired and store the updated emission count in memory. In response to the expiration of an idle or heartbeat interval or an indication that the received sensor data has met the specification criterion, the emission count can be incremented by the same amount or a different amount. In response to determining that the fast response criterion has been met, the control circuitry can update the emission count (e.g., increment by 11) for each sensor device that has met the fast response criterion and store the updated emission count in memory. Instead of increasing the transmit count in response to specification criteria or the expiration of idle or heartbeat intervals, a much larger increase can be made in response to fast response criteria. This allows for the transmission of a series of messages, including updates to sensor data for a given sensor device, when fast response criteria are met, enabling faster control of electrical loads.

When a transmission criterion is met, the control circuitry can continue to update the transmission count for each of the sensor devices. Additionally, the control circuitry can transmit a message including sensor data for each of the sensor devices whose transmission count is higher than a threshold (e.g., greater than one). Figure 3B illustrates an exemplary procedure 320 for transmitting stored sensor data over a communication link for sensor devices with transmission counts higher than the threshold. As shown in Figure 3B, procedure 320 can begin at 321. For example, procedure 320 can begin at 321 after the sensor's transmission count has been updated. At 322, the control circuitry of the system controller can identify whether one or more sensor devices have a transmission count greater than the threshold (e.g., zero). When one or more sensors are identified as having a transmission count greater than zero, the control circuitry can transmit sensor data for each of the sensor devices with a transmission count greater than zero at 324. For example, the control circuitry can generate a message including the currently stored measurement sensor value for each of the sensor devices with a transmission count greater than zero. This message can allow the aggregation of measurement sensor data received by the control circuitry for transmission in a single message. As described herein, the control circuitry can receive sensor data from multiple sensors (e.g., up to 30 sensors) and aggregate the sensor data into a message. At 324, the control circuitry can transmit a message for controlling one or more electrical loads. After transmitting the message at 324, the control circuitry can decrement the sensor count of each of the sensor devices that transmitted sensor data at 326 and store the updated sensor count in memory. After transmission, the control circuitry can wait at 328 for a predefined time period (e.g., a transmission interval of approximately 6 seconds) and then transmit another message or set an interval timer (e.g., set to a heartbeat interval time period).

If the emission count of an additional sensor device is greater than zero, the control circuit can identify those sensor devices at 322 after a predefined time period expires and generate another message for emission. For example, when a fast response criterion is met for a sensor device, the emission count of the sensor device can be set to a predefined value greater than one to allow a series of messages to be emitted. The control circuit can generate each message using sensor data already stored for the sensor device at 306 in procedure 300 of Figure 3A. Since the fast response criterion can detect relatively rapid changes in the measured sensor data, the stored sensor data 306 can vary in the series of messages generated and emitted at 324. This allows electrical loads to be controlled in response to these changes in sensor data in the series of messages. During a predefined time period 328, the emission count for a given sensor device can be changed to allow additional sensor data to be emitted at 324. If no additional emission count for any sensor is greater than a threshold (e.g., zero), procedure 320 can end.

When a state machine is implemented at the system controller, the system controller's control circuitry can use different states to execute one or more portions of programs 300 and 320. For example, based on a state machine with an idle state and a transmit state, when one or more sensor devices are identified as having a transmit count greater than zero, the control circuitry can enter or remain in the transmit state at point 322 of program 320. When no sensor device is identified as having a transmit count greater than zero, the control circuitry can return to the idle state to wait for the idle interval to expire or to identify other transmit criteria in the received sensor data. In the transmit or idle state, the control circuitry can receive sensor data at point 304 and store sensor data at point 306. When a transmit criterion is met at point 308, the control circuitry can transition from the idle state to the transmit state or remain in the transmit state to execute the transmission of one or more messages on the communication link.

In another example, the state machine can have a heartbeat state, a fast state, or a backoff state. In any of these states, the control circuitry can receive sensor data at 304 and store the sensor data at 306. The control circuitry can enter the fast state when a fast response criterion is met at 308 and/or when a sensor device is identified at 322 as having a transmit count higher than a threshold (e.g., greater than 1). When no sensor device has a transmit count greater than zero, the control circuitry can enter the heartbeat state and can transmit a heartbeat message if the heartbeat interval expires. After each transmit, the control circuitry can transition to the backoff state to wait for a predefined period of time for each transmit interval.

Figures 4 through 6C illustrate examples associated with a system controller (e.g., a wireless system controller, such as wireless system controller 111 in Figure 1), which receives data from one or more sensors, transitions between various states based on the received sensor data, and/or packages the sensor data via a wireless network communication link (e.g., wireless network communication link 107 in Figure 1) and periodically transmits the sensor data to a device based on its corresponding state. Figure 4 illustrates an exemplary program 400 that can be executed by a system controller (e.g., wired system controller 110 and/or wireless system controller 111 in Figure 1). Although program 400 may be described as being executed by a system controller, another control device in the load control system (e.g., a lighting control device, a sensor device, or another control device) may execute program 400 or one or more portions thereof. Furthermore, although program 400 may be described as being executed by a single device, program 400 or portions thereof may be distributed across multiple devices (e.g., multiple system controllers, system controllers and control devices, multiple control devices, or other devices in the load control system). Program 400 may be stored in a memory as a computer-readable or machine-readable storage medium, and may be executed by the control circuitry of a system controller or one or more other devices for executing the program.

As shown in Figure 4, program 400 may begin at 401 in response to the system controller's control circuitry receiving a message including sensor data. As described herein, the sensor data may be transmitted (e.g., initially transmitted) by sensor devices (e.g., wired daylight sensor 166 and/or wireless daylight sensor 156) and may be used to control one or more electrical devices (e.g., lighting devices 170, 172) over a wireless network communication link. The control circuitry may determine whether to transmit sensor data over the wireless network communication link based on transmission criteria. For example, the control circuitry may determine whether to meet a fast response criterion or a specification criterion to enable different types of transmission over the wireless network communication link.

As described herein, the transmission criteria can be predefined criteria that consider the frequency of changes in the control circuitry when it can receive messages including sensor data and/or whether the changes in sensor data are perceptible (e.g., whether the changes in sensor data reach or exceed a threshold level to trigger control changes of devices coupled to the wireless network communication link). Therefore, the control circuitry can determine at 402 whether a fast response criterion is met. For example, the control circuitry can determine that a fast response criterion is met when the most recently received sensor data for the corresponding sensor is below a predefined threshold/or when the difference between previously transmitted sensor data and the most recently received sensor data for that sensor device is greater than one or more predefined thresholds. For example, when the type of sensor device from which messages are received is a daylight sensor, the control circuitry can determine that a fast response criterion is met when the most recently received sensor data for the daylight sensor is below 5 foot-candles and the difference between previously transmitted sensor data for the daylight sensor and/or the most recently received sensor data for the sensor is greater than 10 foot-candles and/or greater than a 20% change (e.g., an increase or decrease).

As described herein, when the fast response criterion is met, the control circuitry can determine to transmit received sensor data on the wireless network communication link. Additionally, the control circuitry can determine to transmit multiple subsequent sensor data values for the sensor device. Therefore, if the control circuitry determines that the fast response criterion is met, at 408, the control circuitry can set the transmission count of the sensor device to a fast response count (e.g., 11) and store the transmission count in memory. As described herein, the transmission count of the corresponding sensor device can indicate the number of times sensor data to be transmitted on the wireless network communication link, as measured by the sensor device. The fast response count can be, for example, a predefined count stored in memory at the system controller, and can indicate the number of subsequent sensor data values to be transmitted by the sensor on the wireless network communication link.

Similarly, when in a heartbeat state, the control circuitry can determine at point 404 whether a specification criterion is met. For example, a specification criterion can be defined at the control circuitry to transmit messages differently on the wireless network communication link. The specification criterion can include a threshold change in sensor data that is less than a threshold change in a fast response criterion. The specification criterion can be used to define a stable time period during which the sensor data in messages received from the sensor is relatively stable. The specification criterion can prevent message transmission on the wireless network communication link when the sensor data is relatively stable and allow transmission when a threshold change in the sensor data is detected.

In the example, when received sensor data indicates that the sensor device meets a variation criterion or both a stability criterion and a variation criterion, the control circuitry can determine that a specification criterion is met, as described herein. The stability criterion can identify a period of stable sensor data received from the sensor device at the system controller, and prevent the transmission of sensor data when the data does not indicate a stable period. The variation criterion can identify when a threshold variation in the sensor data received from the sensor device at the system controller is exceeded, and allow the transmission of sensor data when the threshold variation is exceeded.

A stability criterion is met at the system controller when the lowest sensor data received by the control circuit from a given sensor device within a predefined time period and the highest sensor data received by the control circuit from the given sensor device within the same predefined time period are within each other's predefined ranges. For example, a stability criterion is met when the lowest and highest sensor data measured within a predefined time period are within 10% of each other or within each other's predefined values. Again, taking a wireless sunlight sensor as an example, a stability criterion is met when the lowest and highest sunlight levels received from the sunlight sensor within a predefined time period are within 10% of each other or within two foot-candles of each other.

A change criterion can be met at the system controller when the sensor data recently received from the sensor device and/or the change in sensor data differs from previously reported sensor data by one or more predefined thresholds. For example, the control circuitry can determine that a change criterion is met when the current value of the sunlight level received from the sunlight sensor has changed by more than or equal to 15% and/or more than or equal to a predefined amount (such as two foot candles) relative to previously reported sensor data.

If a specification criterion is met (e.g., a variation criterion is met, or both a stability criterion and a variation criterion are met), the control circuit can set the transmit count of the sensor device to a specification count (e.g., 1) at 406. The specification count may vary over time. For example, the specification count may initially be set to a first value, which may increase and/or decrease over time. If the specification count varies over time, it can be a function of the specification count over time (e.g., the maximum value of the specification count over time). As further described herein, a transmit count greater than zero for a given sensor device may cause the control circuit to transmit sensor data received from that sensor device to the control device over a wireless network communication link (e.g., marking the sensor data as transmitted over the wireless network communication link). At 410, the control circuit can store the sensor data received from the sensor device in memory. As described herein, the control circuit can maintain whether sensor data received from one or more sensor devices communicating with the system controller and/or sensor data of the respective sensor devices has been transmitted over the wireless network communication link. Additionally, the maintained sensor data can be used to determine whether a transmission criterion is met for the respective sensor device.

As described herein, the control circuitry can receive sensor data from multiple sensor devices (e.g., up to approximately 30 sensor devices). And at 412, the control circuitry can determine whether any of the sensor devices transmitting sensor data to the system controller has a transmission count greater than zero (e.g., whether sensor data from any sensor device is marked as transmitted on a wireless network communication link). If the control circuitry determines that no sensor device has a transmission count greater than zero (e.g., sensor data is not marked as transmitted on a wireless network communication link), then procedure 400 can end at 427. However, if the control circuitry determines that a sensor device has a transmission count greater than zero (e.g., sensor data from one or more sensor devices is marked as transmitted on a wireless network communication link), then the control circuitry can determine whether to immediately transmit the received sensor data or wait for a predefined interval before transmission. For example, if the control circuitry determines at 414 that it is in a heartbeat state, then the control circuitry can transmit a message at 418 including the received sensor data, with the sensor device transmission count greater than zero, without waiting for a predefined interval before transmission. The control circuit can transmit messages while in a heartbeat state because it has waited for a period of time before entering the heartbeat state. Therefore, the possibility of interference is lower when the control circuit is allowed to transmit messages via RF signals. At 418, the control circuit can also decrement the transmission count of the sensor device to which the transmitted sensor data is targeted.

At 422, the control circuitry can determine if any sensor's transmit count is greater than zero (e.g., sensor data from one or more sensor devices is marked for transmission on a wireless network communication link). If the sensor's transmit count is not greater than zero, the control circuitry can transition to a backoff state at 424. After transmitting sensor data at 418 and because no additional sensor device's transmit count is greater than zero, the control circuitry can transition to a backoff state at 424. The backoff state allows for receiving and/or aggregating additional messages from sensor devices for subsequent transmission during the fast state and before transitioning to the heartbeat state. If the implemented state machine is a two-state machine with an idle state and a transmit state, or does not have a backoff state, the control circuitry can wait for a predefined period of time for the transmit interval after transmitting in the transmit state.

However, if the sensor device's transmit count is indeed greater than zero (e.g., the sensor is still marked as transmitting), the control circuit can transition to a fast state at 426, allowing the control circuit to consider and transmit sensor data that the control circuit has determined will subsequently be transmitted from the sensor device (e.g., because the sensor device meets the fast response criterion). Similarly, if the implemented state machine is a two-state machine with an idle state and a transmit state, or does not have a fast state, the control circuit can remain in the transmit state to perform subsequent transmissions including sensor data from the sensor device (e.g., because the sensor device meets the fast response criterion).

If the control circuit is not in a heartbeat state at 414, it can determine at 416 whether it is in a backoff state. If the control circuit is in a backoff state at 416, it can transition to a fast state at 420, and program 400 can terminate at 427. The control circuit can transition to a fast state at 420 to allow the transmission of sensor data received and/or aggregated while the control circuit is in a backoff state. The control circuit can operate in the fast state as described herein. Similarly, if the state machine being implemented is a two-state machine with an idle state and a transmit state, or without a fast state, and the control circuit determines at 412 that the transmit count of the sensor device is greater than zero, the control circuit can remain in the transmit state to transmit sensor data received and/or aggregated therein.

Figure 5 illustrates an exemplary program 500 that can be executed by a system controller (e.g., wired system controller 110 and/or wireless system controller 111 in Figure 1). Although program 500 may be described as being executed by a wireless system controller, another control device in the load control system (e.g., a lighting control device, a sensor device, or another control device) may execute program 500 or one or more portions thereof. Furthermore, although program 500 may be described as being executed by a single device, program 500 or portions thereof may be distributed across multiple devices (e.g., multiple system controllers, system controllers and control devices, multiple control devices, or other devices in the load control system). Program 500 may be stored in a memory as a computer-readable or machine-readable storage medium, and may be executed by the control circuitry of the system controller or one or more other devices for executing the program.

As shown in Figure 5, program 500 can begin at 501 in response to the expiration of an interval timer. The interval timer can be implemented to separate transmissions on a second communication link (e.g., a wireless communication link utilizing RF signal 107 in Figure 1), at least by means of the interval timer. The implementation of the interval timer can allow the control circuitry to aggregate sensor data from multiple sensors for transmission in the same message on the wireless network communication link. Additionally, the implementation of the interval timer can allow the system controller to transmit sensor data received from sensors to devices communicating on the wireless network communication link. The interval timer can be set to an idle interval period or a heartbeat interval period. The interval timer can be set to a transmission interval. For example, the interval timer can expire periodically (e.g., approximately every 6 seconds), and the control circuitry can transmit the sensor data aggregated within the interval timer period. The operation of the control circuitry when the interval expires at 501 can be changed based on the state of the control circuitry at the time of expiration.

At 502, the control circuit can determine whether it is in a heartbeat state when the interval timer expires. If the control circuit is in a heartbeat state when the interval timer expires, the control circuit can determine at 504 whether the heartbeat interval period has expired. As described herein, the heartbeat interval may include the period during which sensor data of each of the sensor devices communicating with the system controller will be transmitted (e.g., approximately 60 minutes). Additionally, the heartbeat interval period ensures that sensor data of each of the sensor devices communicating with the system controller is transmitted at least once during a given heartbeat interval (e.g., this helps keep the sensor data of each of the sensor devices synchronized with the control device on the wireless communication network). If the control circuit determines that the heartbeat interval has expired, at 506, the control circuit can transmit sensor data on the wireless network communication link for each (e.g., all) of the sensor devices from which it receives sensor data. This allows the sensor data to be synchronized with the control device on the wireless network communication link for each of the sensor devices. For example, in some cases, sensor data from a given sensor device may become out of sync or outdated for a control device on a wireless communication link (e.g., if the control device is powered on/off and/or misses a previous transmission including the sensor data from that sensor device). In these types of scenarios, a heartbeat transmission can allow the sensor data of the sensor device to be synchronized with the control device on the wireless communication link (e.g., enabling the control device to know the current sensor data of the sensor device). After transmitting sensor data at 506 for each of the sensor devices receiving sensor data from the wireless communication network link, the control circuit can transition to a backoff state at 508. If the control circuit determines that the heartbeat interval has not yet expired, the procedure 500 can exit at 521.

At 510, the control circuit can determine whether it is in a fast state when the interval timer expires. As described herein, if the control circuit is in a fast state when the interval timer expires, the control circuit can initiate a transmission on the wireless network communication link at 512, the transmission including aggregated sensor data from sensor devices with a transmission count greater than zero (e.g., sensor devices with a transmission count greater than zero). Additionally, at 512, the control circuit can decrement the transmission count of sensor devices for which it has already transmitted sensor data on the wireless network communication link. At 514, the control circuit can determine whether any of the sensor devices that transmitted sensor data to the control circuit has a transmission count greater than zero (e.g., whether sensor data from any sensor device is marked as transmitted on the wireless network communication link). If the control circuit determines that the transmission counters of one or more sensor devices are greater than zero (e.g., sensor data from a sensor device is marked as transmitted on the wireless network communication link), then program 500 can exit at 521. However, if the control circuit determines that no sensor transmit count is greater than zero (e.g., sensor data is not marked as being transmitted on a wireless network communication link), the control circuit can transition to a backoff state at 516, and procedure 500 can terminate at 521. After transmitting sensor data at 512 and because no additional sensor device transmits a count greater than zero, the control circuit can transition to a backoff state at 516. The backoff state allows receiving and/or aggregating sensor data from sensor devices for subsequent transmission during the fast state and before transitioning to the heartbeat state.

At 518, the control circuit can determine whether it is in a backoff state when the interval timer expires. If the control circuit is in a backoff state when the interval timer expires, the control circuit can transition to a heartbeat state at 520 and program 500 can terminate at 521. The control circuit can remain in the heartbeat state until subsequently received messages include sensor data for transmission over the wireless network communication link.

Figures 6A to 6C are timing diagrams illustrating exemplary messages communicated between input devices 601, 602 and system controller 603 (e.g., the wireless system controller 111 shown in Figure 1). Although the timing diagrams of Figures 6A to 6C illustrate an example of a state machine with three states, state machines with different numbers of states can also be implemented. For example, a state machine with two states can be implemented as described herein and shown in Figure 2A. Input devices 601, 602 can be sensor devices, such as daylight sensors 156, 166, temperature sensors, color temperature sensors, or other types of sensors. Input devices 601, 602 can be on a first communication link (e.g., wired serial communication link 104 and/or wireless input device communication link 106, as shown in Figure 1). System controller 603 can be configured as an intermediary between the input devices on the first communication link and control devices on a wireless network communication link (e.g., wireless network communication link 107, as shown in Figure 1). The system controller 603 can be configured to transmit messages, including sensor data received from input devices 601, 602, to control devices (e.g., lighting devices 170, 172 in FIG. 1) over a wireless network communication link (e.g., for controlling corresponding electrical loads, such as the lighting loads of lighting devices 170, 172).

To transmit messages from input devices 601 and 602 over a wireless network communication link, the wireless system controller 603 can operate in one of several states. As described herein, these states may include a heartbeat state, a backoff state, and/or a fast state. As shown in Figures 6A to 6C, the system controller 603 can transition between these states based on sensor data included in messages from input devices 601 and 602. Similarly, input devices 601 and 602 can be sensors and, as described herein, can be configured to transmit messages including sensor data according to the system controller 603. In response to receiving sensor data from input devices 601 and 602, the system controller 603 can determine whether to transmit the sensor data over the wireless network communication link based on whether a message received from one of the input devices 601 and 602 has met a transmission criterion. The system controller 603 can also transition between these states based on corresponding transmission criteria met at one or more input devices 601 and 602. Additionally, the system controller 603 can periodically (e.g., based on the expiration of an interval timer) transmit sensor data received from input devices 601, 602 to one or more devices over a wireless network communication link.

Referring first to Figure 6A, an example is shown where input devices 601 and 602 transmit messages including sensor data to system controller 603, and system controller 603 determines whether to transmit sensor data on the wireless network communication link based on compliance with specification criteria. At 604, system controller 603 may be in a heartbeat state. At 606, system controller 603 can receive messages including sensor data (e.g., measurement of 63) from input device 601. In response to receiving a message from input device 601, system controller 603 can determine whether to transmit the sensor data received at 606 on the wireless network communication link based on the determination that the sensor data received from input device 601 meets specification criteria. Additionally, system controller 603 can set the transmission count of input device 601 to the specification message count (e.g., 1). Because sensor data is received when system controller 603 is in a heartbeat state, system controller 603 can transmit (e.g., immediately at 606) a message including sensor data (e.g., measurement of 63) on the wireless network communication link and decrement the transmission count of input device 601 to zero. Since the transmit count of input device 601 is set to zero, system controller 603 can transition its state to a backoff state at 606. For example, system controller 603 can transition to a backoff state because neither input device 601 nor input device 602 has a transmit count greater than zero after transmitting at 606. The interval timer can also expire at 606 (e.g., a few seconds later than 604), and wireless system controller 603 can also forward or transmit sensor data to one or more control devices on the wireless network communication link at 606.

As shown in Figure 6A, the message transmitted at 606 on the wireless network communication link may include sensor data from an input device tagged for transmission. As described herein, system controller 603 may identify an input device tagged for transmission based on a transmission count greater than zero for the corresponding input device. For example, at 606, system controller 603 may transmit a message including sensor data from input device 601, but not sensor data from input device 602 (e.g., because the transmission count of input device 601 is one, while the transmission count of input device 602 is zero). After transmitting sensor data to the control device on the wireless network communication link at 606, system controller 603 may decrement the transmission count of the corresponding input device for which it transmitted sensor data (e.g., the transmission counts of input devices 601 and 602 may both be zero). Although the diagram in Figure 6A shows that both the sensor data for input device 601 and the message transmitted by system controller 603 appear at 606, it should be understood that the sensor data is first transmitted by input device 601 and shortly thereafter (e.g., after one or more clock cycles of the control circuitry of system controller 603), the message is transmitted by system controller 603.

At 608, system controller 603 can receive a message from input device 602 including sensor data (e.g., measurement of 37). In response to the sensor data received at 608, system controller 603 can determine whether to transmit the received sensor data over the wireless network communication link based on whether the input device 602 meets specification criteria. In response to receiving the message, system controller 603 can also set the transmission count of input device 602 to one (e.g., mark input device 601 for transmission) and transition to a fast state at 608 (e.g., as described herein with reference to FIG. 2). System controller 603 can transition to the fast state for transmitting sensor data received from input device 602 after the time interval expires. At 610, the interval timer can expire again (e.g., 6 seconds later than 606 when system controller 603 last transmitted a message), and system controller 603 can transmit the sensor data (e.g., measurement of 37) of input device 602 to the control device over the wireless network communication link.

As shown in Figure 6A, the message transmitted at 610 may include sensor data from an input device (e.g., input device 602) tagged for transmission, and as described herein, the transmission may be based on a transmission count greater than zero for the corresponding input device. However, after transmitting the message at 610, the wireless system controller 603 may decrement the transmission count of input device 602, and the transmission counts of both input devices may become zero. As described herein, this may cause the system controller 603 to transition into a backoff state for a period of time. At 612, the interval timer may expire again, and since the system controller 603 was already in a backoff state when the interval timer expired, the wireless system controller 603 may transition into a heartbeat state until a subsequent message is received.

As described herein, the example shown in Figure 6A can also be implemented using a state machine with a different number of states (e.g., two states). For example, the state machine could remain in a single state, such as the launch state 206 described in Figure 2A, instead of transitioning between the backoff state and the fast state at 608 and 610.

Referring now to Figure 6B, an example is shown in which input devices 601, 602 transmit messages including sensor data to system controller 603, and system controller 603 determines whether to transmit sensor data on the wireless network communication link based on meeting a fast response criterion. At 620, system controller 603 may be in a heartbeat state. At 622, system controller 603 may receive messages including sensor data (e.g., measurements of 50) from input device 601. In response to receiving a message from input device 601, system controller 603 may determine whether to transmit sensor data on the wireless network communication link based on meeting a fast response criterion. Additionally, system controller 603 may set the transmission count of input device 601 to a fast response count (e.g., 11) and transition to a fast state, as described herein. An interval timer may expire at 622 (e.g., 6 seconds later than 620), and wireless system controller 603 may also forward or transmit sensor data to one or more control devices on the wireless network communication link at 622. As shown in Figure 6B, the message may include sensor data tagged as an input device for transmission (e.g., input device 601, because its transmission count is greater than zero). After the sensor data is transmitted to the device on the wireless network communication link, the system controller 603 may decrement the transmission count of the corresponding input device for which it transmitted the sensor data. For example, the transmission count of input device 601 may be decremented to ten, while the transmission count of input device 602 may remain at zero.

When the fast response criterion is met, system controller 603 can determine to transmit an additional message including subsequently measured sensor data. At 624, system controller 603 can receive subsequently measured sensor data (e.g., measurement of 51) from input device 601. Similarly, receiving the message at 624 can coincide with the expiration of an interval timer, causing wireless system controller 603 to transmit sensor data and decrement the transmission count of input device 601. At 626, system controller 603 can receive a message including sensor data (e.g., measurement of 50) from input device 602. Again, system controller 603 can determine to transmit sensor data on the wireless network communication link based on the fast response criterion being met. Therefore, system controller 603 can set the transmission count of input device 602 to the fast response count (e.g., 11). At 628, the interval timer may expire and system controller 603 can transmit sensor data marked for transmission. As shown in Figure 6B, for example, input devices 601 and 602 can be marked for transmitting (e.g., the transmission counts of input devices 601 and 602 are both greater than zero), and system controller 603 can transmit the corresponding sensor data to the control device over a wireless network communication link.

As shown in Figure 6B, the system controller can continue to receive messages including sensor data from input devices 601 and 602. For example, system controller 603 can receive messages including sensor data from input device 601 at 628 (e.g., measurement of 50), 636 (e.g., measurement of 49), 642 (e.g., measurement of 49), 648 (e.g., measurement of 50), and 654 (e.g., measurement of 50). System controller 603 can receive messages including sensor data from input device 602 at 630 (e.g., measurement of 50), 634 (e.g., measurement of 49), 640 (e.g., measurement of 50), 646 (e.g., measurement of 51), 652 (e.g., measurement of 51), and 658 (e.g., measurement of 50). Similarly, system controller 603 can continue transmitting sensor data to the control device over the wireless network communication link when the interval timer expires periodically at 632, 636, 638, 642, 644, 648, 650, 654, 656, and 660. Furthermore, as described herein, for example with respect to FIG6A, although both the sensor data for input device 601 and the message including said sensor data transmitted by system controller 603 appear at 636, it should be understood that the sensor data is first transmitted by input device 601, and the message is transmitted by system controller 603 shortly thereafter. A similar situation occurs at 642 and 654. System controller 603 can also decrement the corresponding transmission counts of input devices 601 and 602 as sensor data is transmitted until the corresponding transmission count is no longer greater than zero. For example, the transmit count of input device 601 can be decremented to zero after system controller 603 transmits a message at 654, and the transmit count of input device 602 can be decremented to zero after system controller 603 transmits a message at 660. Further as shown in Figure 6B, after transmitting a message at 660, the transmit counts of input devices 601 and 602 can be zero, and as a result, wireless system controller 603 can also transition to a backoff state. When system controller 603 is in the backoff state, an internal timer can expire at 662 because system controller 603 failed to receive any messages in the backoff state, which may cause system controller 603 to transition to a heartbeat state, as described herein.

As shown in Figure 6B, the system controller 603 can enter a fast state for transmitting sensor data received from input devices 601 and 602 and maintain this fast state until the transmission counts of input devices 601 and 602 reach zero. Sensor data received from each input device within the same interval can be aggregated for transmission in a single message over the wireless network communication link.

As described herein, the example shown in Figure 6B can also be implemented using a state machine with a different number of states (e.g., two states). For example, the state machine could remain in a single state, such as the launch state 206 described in Figure 2A, instead of transitioning from the fast state to the backoff state at 660.

Referring now to Figure 6C, an example is shown where system controller 603 can determine to transmit sensor data from input device 601 based on meeting specification criteria, and where system controller 603 determines to transmit sensor data from input device 602 based on meeting fast response criteria. At 670, system controller 603 can be in a heartbeat state. At 671, system controller 603 can receive a message from input device 601 including sensor data (e.g., a measurement of 50). In response to receiving a message from input device 601, system controller 603 can determine to transmit sensor data on the wireless network communication link based on meeting specification criteria. Therefore, system controller 603 can set the transmission count of input device 601 to a specification count (e.g., 1) and transition to a fast state for transmission, as described herein. Receiving a message at 671 can also coincide with the expiration of an interval timer (e.g., 6 seconds later than 670), and wireless system controller 603 can also transmit sensor data to one or more control devices on the wireless network communication link at 671. As shown in Figure 6C, the message may include sensor data tagged as an input device for transmission (e.g., input device 601, because its transmission count is greater than zero). After transmitting the sensor data to the control device on the wireless network communication link, the system controller 603 may decrement the transmission count of the corresponding input device for which it transmitted the sensor data (e.g., the transmission counts of input devices 601 and 602 may now be zero). At 671, since input devices 601 and 602 both have zero transmission counts (e.g., as shown in Figure 3), the system controller 603 may transition to a backoff state for an interval.

At 673, the system controller 603 can receive a message from the input device 302 including sensor data (e.g., measurements of 50). In response to receiving the message from the input device 602, the wireless system controller 603 can determine whether to transmit the sensor data from the input device 602 on the wireless network communication link based on meeting a fast response criterion. Therefore, the system controller 603 can set the transmission count of the input device 602 to a fast response count (e.g., 11). At 674, the interval timer can expire again, and the system controller 603 can also transmit the sensor data received from the input device 602 to the control device on the wireless network communication link.

As shown in Figure 6C, the system controller 603 can continue to receive messages including sensor data from the input device 602. For example, the system controller 603 can receive subsequent messages including sensor data from the input device 602 at 675 (e.g., measurement of 50), 678 (e.g., measurement of 49), 682 (e.g., measurement of 50), 685 (e.g., measurement of 51), 691 (e.g., measurement of 51), and 695 (e.g., measurement of 50). At 677, 679, 680, 683, 684, 688, 690, 692, 694, and 696, the system controller 603 can continue to transmit the sensor data received from the input device 602 on the wireless network communication link. The system controller 603 can also decrement the transmission count of the input device 602 as sensor data is transmitted. For example, after the system controller 603 transmits a message including sensor data at 696, the transmission count of the input device 602 can be decremented to zero.

As further shown in Figure 6C, the system controller 603 can also receive messages including sensor data from the input device 601 at 676, 686, and 692. Similarly, the system controller 603 can determine the sensor data transmitted and received on the wireless network communication link based on satisfying specification criteria. For example, in response to receiving each of these messages from the input device 601, the system controller 603 can set the transmission count of the input device 601 to a specification count (e.g., 1). The system controller 603 can aggregate the sensor data received from the input device 601 with the sensor data transmitted by the input device 602 in the next message. The system controller 603 can decrement the transmission count of the input device 601 as it transmits sensor data to the control device on the wireless network communication link. For example, the transmission count of the input device 601 can be set to a specification count (e.g., 1) at 676 and then decremented (e.g., decremented to zero) after the received sensor data is transmitted at 677. The transmit count of input device 601 can be similarly set to a normal count at 686 and 692 respectively, and then decremented after transmits at 688 and 692.

After transmitting sensor data from input device 601 at point 696, the transmission counts of input devices 601 and 602 can both be zero, and system controller 603 can transition to a backoff state. When the interval timer expires again at point 698, system controller 603 can transition to a heartbeat state.

As described herein, the example shown in Figure 6C can also be implemented using a state machine with a different number of states (e.g., two states). For example, the state machine could remain in a single state, such as the launch state 206 described in Figure 2A, instead of transitioning between the backoff state and the fast state at 673 and 696.

Figure 7 is a block diagram illustrating an example of a device 700 capable of handling and/or communicating in a load control system (such as the load control system 100 of Figure 1). In the example, device 700 may be a control device capable of transmitting or receiving messages. The control device may be in an input device (such as a wired keypad device 150, a wired daylight sensor 166, a battery-powered remote control device 152, a wireless occupancy sensor 154 and/or a wireless daylight sensor 156) or in another input device capable of transmitting messages to a load control device or other device in the load control system 100. Device 130 may be a computing device, such as a personal computer 164, a wired system controller 110, a wireless system controller 111, or another computing device in the load control system 100. The system controller may be a gateway system controller, a target system controller, a remote system controller, and/or a combination thereof.

Device 700 may include control circuitry 701 for controlling the functionality of device 700. Control circuitry 701 may include one or more general-purpose processors, special-purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, programmable logic devices (PLDs), application-specific integrated circuits (ASICs), etc. Control circuitry 701 may perform signal encoding, data processing, image processing, power control, input/output processing, or any other functionality that enables device 700 to perform as described herein as a device for a load control system (e.g., load control system 100).

Control circuitry 701 may be communicatively coupled to memory 702 to store information in memory 702 and/or retrieve information from said memory. Memory 702 may include a computer-readable or machine-readable storage medium storing computer-executable instructions to be executed as described herein. When device 700 is a system controller, sensor device, or another device configured to transmit messages as described herein, the computer-executable instructions may include one or more portions of programs 300, 320, 400, and/or 500 to be executed as described herein. Memory 702 may maintain the state of sensor data received by control circuitry 701 and/or the state of a state machine executed on device 700. Control circuitry 701 may access instructions from memory 702 for execution to cause control circuitry 701 to operate as described herein, or to operate one or more devices as described herein. Memory 702 may include non-removable memory and/or removable memory. Non-removable memory may include random access memory (RAM), read-only memory (ROM), hard disk, or any other type of non-removable memory storage device. The removable storage device may include a Subscriber Identity Module (SIM) card, Memory Stick, Memory Card, or any other type of removable storage device. Storage 702 may be implemented as an external integrated circuit (IC) or as internal circuitry of control circuitry 701.

Device 700 may include one or more communication circuits 704 that communicate with control circuitry 701 to send and/or receive information as described herein. Communication circuitry 704 may perform wireless and/or wired communication. Communication circuitry 704 may include wired communication circuitry capable of communication over a wired communication link. The wired communication link may include an Ethernet communication link, an RS-485 serial communication link, a 0-10 volt analog link, a pulse width modulation (PWM) control link, a Digital Addressable Lighting Interface (DALI) digital communication link, and/or another type of wired communication link. Communication circuitry 704 may be configured to communicate via a power line (e.g., a power line from which device 130 receives power) using power line carrier (PLC) communication technology. Communication circuitry 704 may include wireless communication circuitry including one or more RF or infrared (IR) transmitters, receivers, transceivers, or other communication circuitry capable of performing wireless communication.

Although a single communication circuit 704 may be shown, multiple communication circuits may be implemented in device 700. Device 700 may include communication circuits configured to communicate via one or more wired and/or wireless communication networks and/or protocols, and at least one other communication circuit configured to communicate via one or more other wired and/or wireless communication networks and/or protocols. For example, a first communication circuit may be configured to communicate via a wired or wireless communication link, while another communication circuit may be able to communicate on another wired or wireless communication link. The first communication circuit may be configured to communicate via a first wireless communication link (e.g., a wireless network communication link) using a first wireless protocol (e.g., a wireless network communication protocol, such as CLEAR CONNECT (e.g., CLEARCONNECT A and/or CLEAR CONNECT X) and/or THREAD protocol), and a second communication circuit may be configured to communicate via a second wireless communication link (e.g., a short-range or direct wireless communication link) using a second wireless protocol (e.g., a short-range wireless communication protocol, such as BLUETOOTH and/or BLUETOOTH LOW ENERGY (BLE) protocol). In another example, the first communication circuit may be configured to communicate via a first wireless communication link (e.g., a wireless network communication protocol, such as CLEAR CONNECT (e.g., CLEAR CONNECT A and/or CLEAR CONNECT X) and/or THREAD protocol) using a first wireless protocol, and the second communication circuit may be configured to communicate via a wired communication link.

One of the communication circuits 704 may include a beacon transmitting and/or receiving circuit capable of transmitting and/or receiving beacon messages via short-range RF signals. Control circuit 701 may communicate with the beacon transmitting circuit (e.g., a short-range communication circuit) to transmit beacon messages. For example, the beacon transmitting circuit may transmit beacon messages via RF communication signals. The beacon transmitting circuit may be a unidirectional communication circuit (e.g., the beacon transmitting circuit is configured to transmit beacon messages) or a bidirectional communication circuit capable of receiving information on the same network and/or protocol on which the beacon messages are transmitted (e.g., the beacon transmitting circuit is configured to both transmit and receive beacon messages). Information received at the beacon transmitting circuit may be provided to control circuit 701.

Control circuitry 701 can communicate with one or more input circuits 705 from which input can be received. Input circuitry 704 can be included in a user interface for receiving input from a user. For example, input circuitry 704 may include an actuator (e.g., a momentary switch actuated by one or more physical buttons) that can be actuated by a user to convey user input or selection to control circuitry 701. In response to actuation of the actuator, control circuitry 701 can enter an associated mode, transmitting associated messages from device 700 via communication circuitry 704, and/or receiving other information (e.g., control instructions for performing control on electrical loads). In response to actuation of the actuator, control can be performed by transmitting control instructions instructing actuation on the user interface and/or control instructions generated in response to said actuation. Actuators may include touch-sensitive surfaces, such as capacitive touch surfaces, resistive touch surfaces, inductive touch surfaces, surface acoustic wave (SAW) touch surfaces, infrared touch surfaces, acoustic pulse touch surfaces, or another touch-sensitive surface configured to receive input such as point-driven or gesture-based input from a user (e.g., touch actuation/input). The control circuit 701 of the device 700 can enter an association mode in response to actuation or input from the user on the touch-sensitive surface, transmit association messages, transmit control commands, or perform other functions.

Input circuitry 703 may include sensing circuitry (e.g., a sensor). Sensing circuitry may be occupancy sensing circuitry, temperature sensing circuitry, color (e.g., color temperature) sensing circuitry, visible light sensing circuitry (e.g., a camera), sunlight sensing circuitry, or ambient light sensing circuitry, or another sensing circuitry for receiving input (e.g., environmental characteristics in the environment of sensing device 700). Control circuitry 701 may receive information from one or more input circuits 703 and process said information to perform the functions described herein.

The control circuit 701 can communicate with one or more output sources 705. The output source 705 may include one or more light sources (e.g., LEDs) for providing indications (e.g., feedback) to a user. The output source 705 may include a display (e.g., a visible display) for providing information (e.g., feedback) to a user. The control circuit 701 and/or the display may generate a software-generated graphical user interface (GUI) for display on the device 700 (e.g., on a display of the device 700).

The user interface of device 700 can combine features of input circuitry 703 and output source 705. For example, the user interface may have buttons that actuate the actuator of input circuitry 703 and may have indicators (e.g., visibility indicators) that can be illuminated by a light source from output source 705. In another example, the display and control circuitry 701 may be in bidirectional communication, as the display can show information to the user and includes a touchscreen capable of receiving information from the user. Information received via the touchscreen may be provided as information to control circuitry 701 for performing functions or control.

Each of the hardware circuits within device 700 may be powered by power supply 706. For example, power supply 706 may include a power source configured to receive power from an alternating current (AC) power source or a direct current (DC) power source. Additionally, power supply 706 may include one or more batteries. Power supply 706 may generate a supply voltage _VCC to power the hardware within device 700.

Figure 8 is a block diagram illustrating an exemplary load control device 800. The load control device 800 may be a lighting control device (e.g., a light-emitting diode (LED) driver 130 for controlling or driving a corresponding electrical load such as an LED light source 132 and/or lighting fixtures 170, 172) or a daylight control device such as an electric window cover (e.g., an electric roller blind 140), a plug-in load control device, a temperature control device, a dimmer switch, an electronic switch, an electronic ballast for a lamp, and/or another load control device.

The load control device 800 may include control circuitry 801 for controlling the functionality of the load control device 800. Control circuitry 801 may include one or more general-purpose processors, special-purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, programmable logic devices (PLDs), application-specific integrated circuits (ASICs), etc. Control circuitry 801 may perform signal encoding, data processing, image processing, power control, input/output processing, or any other functionality that enables the load control device 800 to perform as described herein as a device for a load control system (e.g., load control system 100).

The load control device 800 may include a load control circuit 805, which may be electrically coupled in series between a power source 807 (e.g., an AC power source and/or a DC power source) and an electrical load 808. The control circuit 801 may be configured to control the load control circuit 805 to control the electrical load 808, for example, in response to a received instruction or message (such as a message including, for example, sensor data). The electrical load 808 may include a lighting load, a motor load (e.g., for a ceiling fan and/or exhaust fan), an electric motor for controlling appliances on electric windows, components of a heating, ventilation, and cooling (HVAC) system, a speaker, or any other type of electrical load.

Control circuitry 801 may be communicatively coupled to memory 802 to store information in memory 802 and/or retrieve information from said memory. Memory 802 may include a computer-readable or machine-readable storage medium that maintains a device dataset of associated device identifiers, network information, and/or computer-executable instructions for execution as described herein. For example, memory 802 may include computer-executable or machine-readable instructions capable of controlling electrical load 808 in response to sensor data received at control circuitry as described herein. Control circuitry 801 may access instructions from memory 802 for execution to cause control circuitry 801 to operate as described herein, or to operate one or more devices as described herein. Memory 802 may include non-removable memory and/or removable memory. Non-removable memory may include random access memory (RAM), read-only memory (ROM), hard disk, or any other type of non-removable memory storage device. Removable memory may include a subscriber identity module (SIM) card, memory stick, memory card, or any other type of removable memory. The memory 802 can be implemented as an external integrated circuit (IC) or as an internal circuit of the control circuit 801.

The load control device 800 may include one or more communication circuits 804 that communicate with the control circuit 801 to send and/or receive information as described herein. The communication circuits 804 may perform wireless and/or wired communication. The communication circuits 804 may be wired communication circuits capable of communication over a wired communication link. The wired communication link may include an Ethernet communication link, an RS-485 serial communication link, a 0-10 volt analog link, a pulse width modulation (PWM) control link, a Digital Addressable Lighting Interface (DALI) digital communication link, and/or another type of wired communication link. The communication circuits 804 may be configured to communicate via a power line (e.g., a power line from which the load control device 800 receives power) using power line carrier (PLC) communication technology. The communication circuits 804 may be wireless communication circuits including one or more RF or IR transmitters, receivers, transceivers, or other communication circuits capable of performing wireless communication.

Although a single communication circuit 804 may be shown, multiple communication circuits may be implemented in the load control device 800. The load control device 800 may include communication circuits configured to communicate via one or more wired and/or wireless communication networks and/or protocols, and at least one other communication circuit configured to communicate via one or more other wired and/or wireless communication networks and/or protocols. For example, a first communication circuit may be configured to communicate via a wired or wireless communication link, while another communication circuit may be able to communicate on another wired or wireless communication link. The first communication circuit may be configured to communicate via a first wireless communication link (e.g., a wireless network communication link) using a first wireless protocol (e.g., a wireless network communication protocol, such as CLEARCONNECT (e.g., CLEAR CONNECT A and/or CLEAR CONNECT X) and/or THREAD protocol), and a second communication circuit may be configured to communicate via a second wireless communication link (e.g., a short-range or direct wireless communication link) using a second wireless protocol (e.g., a short-range wireless communication protocol, such as BLUETOOTH and/or BLUETOOTH LOW ENERGY (BLE) protocol).

One of the communication circuits 804 may include beacon transmitting and/or receiving circuitry capable of transmitting and/or receiving beacon messages via short-range RF signals. Control circuitry 801 may communicate with the beacon transmitting circuitry (e.g., a short-range communication circuit) to transmit beacon messages. For example, the beacon transmitting circuitry may transmit beacon messages via RF communication signals. The beacon transmitting circuitry may be a unidirectional communication circuitry (e.g., the beacon transmitting circuitry is configured to transmit beacon messages) or a bidirectional communication circuitry capable of receiving information on the same network and/or protocol on which the beacon messages are transmitted (e.g., the beacon transmitting circuitry is configured to both transmit and receive beacon messages). Information received at the beacon transmitting circuitry may be provided to control circuitry 801.

Control circuitry 801 can communicate with one or more input circuits 806 from which input can be received. Input circuitry 806 can be included in a user interface for receiving input from a user. For example, input circuitry 806 may include an actuator (e.g., a momentary switch actuated by one or more physical buttons) that can be actuated by a user to transmit user input or selection to control circuitry 801. In response to actuation of the actuator, control circuitry 801 can enter an associated mode, transmitting associated messages from load control device 800 via communication circuitry 804, and/or receiving other information. In response to actuation of the actuator, control can be performed by controlling load control circuitry 805 to control electrical load 800 and/or by transmitting control commands indicative of actuation on the user interface and/or by control commands generated in response to said actuation. The actuator may include a touch-sensitive surface, such as a capacitive touch surface, a resistive touch surface, an inductive touch surface, a surface acoustic wave (SAW) touch surface, an infrared touch surface, an acoustic pulse touch surface, or another touch-sensitive surface configured to receive input such as point actuation or gesture from a user (e.g., touch actuation/input). The control circuitry 801 of the load control device 800 may enter an associated mode in response to actuation or input from a user on the touch-sensitive surface, transmit an associated message, control the load control circuitry 805, transmit control commands, or perform other functionalities.

Input circuitry 806 may include sensing circuitry (e.g., a sensor). Sensing circuitry may be occupancy sensing circuitry, temperature sensing circuitry, color (e.g., color temperature) sensing circuitry, visible light sensing circuitry (e.g., a camera), sunlight sensing circuitry, or ambient light sensing circuitry, or another sensing circuitry for receiving input (e.g., sensing environmental characteristics in the environment of the load control device 800). Control circuitry 801 may receive information from one or more input circuits 806 and process said information to perform the functions described herein.

The control circuit 801 can illuminate the light source 803 (e.g., an LED) to provide feedback to the user. The control circuit 801 can be operated to illuminate the light source 803 of different colors. The light source 803 can illuminate one or more indicators (e.g., visibility indicators) of, for example, the load control device 800.

Although features and elements are described herein in specific combinations, each feature or element may be used alone or in various combinations with other features and elements. The methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), removable magnetic disks, and optical media such as CD-ROM disks and digital versatile disks (DVDs).

Claims (45)

1. An apparatus configured to process messages from a plurality of input devices, each of the messages including sensor data measured by a corresponding input device among the plurality of input devices, the apparatus comprising: A first communication circuit, configured to communicate via a first communication link; A second communication circuit, configured to communicate via a second communication link; and Control circuit, the control circuit being configured to: Receive a message including sensor data from the plurality of input devices via the first communication circuit on the first communication link, wherein the message includes sensor data measured at a first input device among the plurality of input devices, and wherein the message includes sensor data measured at a second input device among the plurality of input devices; Aggregate the sensor data from the first input device and the sensor data from the second input device; In response to detecting a threshold change in the sensor data from the first input device and the second input device, a message is transmitted via the second communication circuit on the second communication link, the message including aggregated sensor data from the first input device and the second input device; and In response to detecting a threshold change in the sensor data from the first input device but not a threshold change in the sensor data from the second input device, a message is transmitted via the second communication circuit on the second communication link, the message including the sensor data from the first input device but not the sensor data from the second input device. 2. The apparatus of claim 1, wherein the threshold change is a first threshold change of the sensor data, and wherein the control circuit is configured to: In response to detecting a second threshold change in the sensor data from the first input device, a plurality of messages are transmitted via the second communication circuit on the second communication link, wherein the plurality of messages include at least one message that includes the aggregated sensor data from the first input device and the second input device, and wherein the second threshold change is greater than the first threshold change. 3. The apparatus of claim 2, wherein the control circuit is configured to continuously transmit the plurality of messages at a transmission interval time period after each message transmission. 4. The apparatus of claim 2, wherein the first threshold change and the second threshold change each include different threshold changes between the sensor data and previously measured sensor data, previously received sensor data, and previously transmitted sensor data. 5. The apparatus of claim 2, wherein the first threshold change and the second threshold change each comprise different threshold change rates over a period of time. 6. The apparatus of claim 2, wherein the control circuit is further configured to: The first emission count of the first input device is determined based on the change in the first threshold; and The second emission count of the second input device is determined based on the change in the second threshold. 7. The apparatus of claim 6, wherein the control circuit is further configured to: After the heartbeat interval period expires, it is determined that at least one of the first input device or the second input device is marked as having emitted a heartbeat; and A message is transmitted on the second communication link via the second communication circuit, the message including the aggregated sensor data of the first input device and the second input device. 8. The apparatus of claim 2, wherein the control circuit is further configured to: In response to detecting a change in the first threshold, a first emission count is set for the first input device; and In response to detecting a change in the second threshold, a second emission count is set for the second input device, wherein the second emission count is greater than the first emission count. 9. The apparatus of claim 8, wherein the control circuit is further configured to: In response to detecting a first threshold change in the sensor data from the second input device, the first emission count is set for the second input device; and In response to detecting a second threshold change in the sensor data from the second input device, the second emission count is set for the second input device. 10. The apparatus of claim 9, wherein the control circuit is further configured to: Determining that both the first input device and the second input device have emission counts greater than a threshold; and A message is transmitted on the second communication link via the second communication circuit, the message including the aggregated sensor data from the first input device and the second input device. 11. The apparatus of claim 10, wherein the control circuit is further configured to: It is determined that the second input device has an emission count greater than the threshold; Determine that the first input device no longer has an emission count greater than the threshold; and A message is transmitted on the second communication link via the second communication circuit, the message including the sensor data from the second input device. 12. The apparatus of claim 11, wherein the control circuit is configured to enter a transmit state to transmit the message on the second communication link, and wherein the control circuit is further configured to: Determine that each of the plurality of input devices does not have an emission count greater than the threshold; Entering an idle state; and Set the interval timer to an idle interval period to remain in the idle state. 13. The apparatus of claim 1, wherein the control circuit is further configured to: The state of the device is identified, wherein the identified state is one of a heartbeat state, a rapid state, or a retreat state; and The received message is processed according to the status of the identifier. 14. The apparatus of claim 13, wherein the state of the identifier is the retreat state, and wherein the control circuit is further configured to: Determine whether a message including sensor data was received during the interval period; and The heartbeat state is transitioned in response to determining that no message including the sensor data has been received during the interval period. 15. The apparatus of claim 13, wherein the threshold change is a first threshold change, wherein the identified state is the fast state, and wherein the control circuitry is further configured to: The system enters the fast state in response to the detection of a second threshold change in order to control the electrical load in response to the second threshold change. When the interval period expires, it is determined that the first input device is marked for transmission based on the transmission count of the first input device; and A message is transmitted on the second communication link via the second communication circuit, the message including sensor data from the first input device. 16. A method for processing messages from a plurality of input devices, each of the messages comprising sensor data measured by a corresponding input device among the plurality of input devices, the method comprising: Receive a message including sensor data from the plurality of input devices on a first communication link, wherein the message includes sensor data measured at a first input device among the plurality of input devices, and wherein the message includes sensor data measured at a second input device among the plurality of input devices; Aggregate the sensor data from the first input device and the sensor data from the second input device; In response to detecting a threshold change in the sensor data from the first input device and the second input device, a message is transmitted on the second communication link, the message including aggregated sensor data from the first input device and the second input device; and In response to detecting a threshold change in the sensor data from the first input device but not a threshold change in the sensor data from the second input device, a message is transmitted on the second communication link, the message including the sensor data from the first input device but not the sensor data from the second input device. 17. The method of claim 16, wherein the threshold change is a first threshold change of the sensor data, the method further comprising: In response to detecting a second threshold change in the sensor data from the first input device, a plurality of messages are transmitted on the second communication link, wherein the plurality of messages include at least one message that includes the aggregated sensor data from the first input device and the second input device, and wherein the second threshold change is greater than the first threshold change. 18. The method of claim 17, further comprising: The multiple messages are continuously transmitted at transmission intervals after each message transmission. 19. The method of claim 17, wherein the first threshold change and the second threshold change each comprise different threshold changes of the sensor data compared to previously measured sensor data, previously received sensor data, and previously transmitted sensor data. 20. The method of claim 17, wherein the first threshold change and the second threshold change each comprise different threshold change rates over a period of time. 21. The method of claim 17, further comprising: The first emission count of the first input device is determined based on the change in the first threshold; and The second emission count of the second input device is determined based on the change in the second threshold. 22. The method of claim 21, further comprising: After the heartbeat interval period expires, it is determined that at least one of the first input device or the second input device is marked as having emitted a heartbeat; and A message is transmitted on the second communication link, the message including the aggregated sensor data of the first input device and the second input device. 23. The method of claim 17, further comprising: In response to detecting a change in the first threshold, a first emission count is set for the first input device; and In response to detecting a change in the second threshold, a second emission count is set for the second input device, wherein the second emission count is greater than the first emission count. 24. The method of claim 23, further comprising: In response to detecting a first threshold change in the sensor data from the second input device, the first emission count is set for the second input device; and In response to detecting a second threshold change in the sensor data from the second input device, the second emission count is set for the second input device. 25. The method of claim 24, further comprising: Determining that both the first input device and the second input device have emission counts greater than a threshold; and A message is transmitted on the second communication link, the message including the aggregated sensor data from the first input device and the second input device. 26. The method of claim 25, further comprising: It is determined that the second input device has an emission count greater than the threshold; Determine that the first input device no longer has an emission count greater than the threshold; and A message is transmitted on the second communication link, the message including the sensor data from the second input device. 27. The method of claim 26, further comprising: Enter transmit state to transmit the message on the second communication link: Determine that each of the plurality of input devices does not have an emission count greater than the threshold; Entering an idle state; and Set the interval timer to an idle interval period to remain in the idle state. 28. The method of claim 16, further comprising: The state of the device is identified, wherein the identified state is one of a heartbeat state, a rapid state, or a retreat state; and The received message is processed according to the status of the identifier. 29. The method of claim 28, wherein the state of the identifier is the retreat state, the method further comprising: Determine whether a message including sensor data was received during the interval period; and The heartbeat state is transitioned in response to determining that no message including the sensor data has been received during the interval period. 30. The method of claim 28, wherein the threshold change is a first threshold change, wherein the identified state is the fast state, and the method further comprises: The system enters the fast state in response to the detection of a second threshold change in order to control the electrical load in response to the second threshold change. When the interval period expires, it is determined that the first input device is marked for transmission based on the transmission count of the first input device; and A message is transmitted on the second communication link, the message including sensor data from the first input device. 31. A computer-readable storage medium having computer-executable instructions stored thereon, the computer-executable instructions causing the control circuit, when executed by the control circuit, to: Receives a message including sensor data from multiple input devices via a first communication circuit on a first communication link, wherein the message includes sensor data measured at a first input device among the multiple input devices, and wherein the message includes sensor data measured at a second input device among the multiple input devices; Aggregate the sensor data from the first input device and the sensor data from the second input device; In response to detecting a threshold change in the sensor data from the first input device and the second input device, a message is transmitted via a second communication circuit on the second communication link, the message including aggregated sensor data from the first input device and the second input device; and In response to detecting a threshold change in the sensor data from the first input device but not a threshold change in the sensor data from the second input device, a message is transmitted via the second communication circuit on the second communication link, the message including the sensor data from the first input device but not the sensor data from the second input device. 32. The computer-readable storage medium of claim 31, wherein the threshold change is a first threshold change of the sensor data, and wherein the computer-readable storage medium is further configured to cause the control circuitry to: In response to detecting a second threshold change in the sensor data from the first input device, a plurality of messages are transmitted via the second communication circuit on the second communication link, wherein the plurality of messages include at least one message that includes the aggregated sensor data from the first input device and the second input device, and wherein the second threshold change is greater than the first threshold change. 33. The computer-readable storage medium of claim 32, wherein the computer-readable storage medium is further configured to cause the control circuitry to continuously transmit the plurality of messages at transmission intervals after each message transmission. 34. The computer-readable storage medium of claim 32, wherein the first threshold change and the second threshold change each comprise different threshold changes of the sensor data compared to previously measured sensor data, previously received sensor data, and previously transmitted sensor data. 35. The computer-readable storage medium of claim 32, wherein the first threshold change and the second threshold change each comprise different threshold change rates over a period of time. 36. The computer-readable storage medium of claim 32, wherein the computer-readable storage medium is further configured to cause the control circuitry to: The first emission count of the first input device is determined based on the change in the first threshold; and The second emission count of the second input device is determined based on the change in the second threshold. 37. The computer-readable storage medium of claim 36, wherein the computer-readable storage medium is further configured to cause the control circuitry to: After the heartbeat interval period expires, it is determined that at least one of the first input device or the second input device is marked as having emitted a heartbeat; and A message is transmitted on the second communication link via the second communication circuit, the message including the aggregated sensor data of the first input device and the second input device. 38. The computer-readable storage medium of claim 32, wherein the computer-readable storage medium is further configured to cause the control circuitry to: In response to detecting a change in the first threshold, a first emission count is set for the first input device; and In response to detecting a change in the second threshold, a second emission count is set for the second input device, wherein the second emission count is greater than the first emission count. 39. The computer-readable storage medium of claim 38, wherein the computer-readable storage medium is further configured to cause the control circuitry to: In response to detecting a first threshold change in the sensor data from the second input device, the first emission count is set for the second input device; and In response to detecting a second threshold change in the sensor data from the second input device, the second emission count is set for the second input device. 40. The computer-readable storage medium of claim 39, wherein the computer-readable storage medium is further configured to cause the control circuitry to: Determining that both the first input device and the second input device have emission counts greater than a threshold; and A message is transmitted on the second communication link via the second communication circuit, the message including the aggregated sensor data from the first input device and the second input device. 41. The computer-readable storage medium of claim 40, wherein the computer-readable storage medium is further configured to cause the control circuitry to: It is determined that the second input device has an emission count greater than the threshold; Determining that the first input device no longer has an emission count greater than the threshold; and A message is transmitted on the second communication link via the second communication circuit, the message including the sensor data from the second input device. 42. The computer-readable storage medium of claim 41, wherein the computer-readable storage medium is further configured to cause the control circuitry to enter a transmit state to transmit the message on the second communication link, and wherein the computer-readable storage medium is further configured to cause the control circuitry to: Determine that each of the plurality of input devices does not have an emission count greater than the threshold; Entering an idle state; and Set the interval timer to an idle interval period to remain in the idle state. 43. The computer-readable storage medium of claim 31, wherein the computer-readable storage medium is further configured to cause the control circuitry to: The state of the device is identified, wherein the identified state is one of a heartbeat state, a rapid state, or a retreat state; and The received message is processed according to the status of the identifier. 44. The computer-readable storage medium of claim 43, wherein the state of the identifier is the backoff state, and wherein the computer-readable storage medium is further configured to cause the control circuitry to: Determine whether a message including sensor data was received during the interval period; and The heartbeat state is transitioned in response to determining that no message including the sensor data has been received during the interval period. 45. The computer-readable storage medium of claim 43, wherein the threshold change is a first threshold change, wherein the identified state is the fast state, and wherein the computer-readable storage medium is further configured to cause the control circuitry to: The system enters the fast state in response to the detection of a second threshold change in order to control the electrical load in response to the second threshold change. When the interval period expires, it is determined that the first input device is marked for transmission based on the transmission count of the first input device; and A message is transmitted via the second communication circuit on the second communication link, the message including sensor data from the first input device.