Patent ID: 12215881

While the disclosure is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit the disclosure to the particular embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.

DESCRIPTION

For the following defined terms, these definitions shall be applied, unless a different definition is given in the claims or elsewhere in this specification.

All numeric values are herein assumed to be modified by the term “about,” whether or not explicitly indicated. The term “about” generally refers to a range of numbers that one of skill in the art would consider equivalent to the recited value (i.e., having the same function or result). In many instances, the terms “about” may include numbers that are rounded to the nearest significant figure.

The recitation of numerical ranges by endpoints includes all numbers within that range (e.g. 1 to 5 includes 1, 1.5, 2, 2.75, 3, 3.80, 4, and 5).

As used in this specification and the appended claims, the singular forms “a”, “an”, and “the” include plural referents unless the content clearly dictates otherwise. As used in this specification and the appended claims, the term “or” is generally employed in its sense including “and/or” unless the content clearly dictates otherwise.

It is noted that references in the specification to “an embodiment”, “some embodiments”, “other embodiments”, etc., indicate that the embodiment described may include one or more particular features, structures, and/or characteristics. However, such recitations do not necessarily mean that all embodiments include the particular features, structures, and/or characteristics. Additionally, when particular features, structures, and/or characteristics are described in connection with one embodiment, it should be understood that such features, structures, and/or characteristics may also be used connection with other embodiments whether or not explicitly described unless clearly stated to the contrary.

The following description should be read with reference to the drawings in which similar structures in different drawings are numbered the same. The drawings, which are not necessarily to scale, depict illustrative embodiments and are not intended to limit the scope of the disclosure. Although examples of construction, dimensions, and materials may be illustrated for the various elements, those skilled in the art will recognize that many of the examples provided have suitable alternatives that may be utilized.

FIG.1is a schematic block diagram showing features of an illustrative HVAC unit100that may thermostatically control a temperature of a space50. The HVAC unit100is shown inFIG.1as often referred to as a mini-split HVAC unit, but it is contemplated that the disclosure is not limited to such HVAC units. For example, it is contemplated that the HVAC unit100may be a window air conditioning unit, a central air conditioning unit, a forced-air central heating unit, or any other suitable HVAC unit. Moreover, it is contemplated that various embodiments and examples described herein may be extended to other building automation systems and/or units including, but not limited to, security system units, lighting system units, etc.

The illustrative HVAC unit100ofFIG.1includes an indoor unit102that may be configured to draw in return air104and supply temperature regulated air106to the space50. The indoor unit102may be configured to handle air104and106with or without a network of ductwork installed within and/or around the space50.

The indoor unit102of the HVAC unit100may be connected to an outdoor unit108, sometimes through a hole in an external wall of the building. In some cases, lines110carrying a working fluid may be transferred between the indoor unit102and the outdoor unit108. Outdoor unit108may be exposed to an outdoor space, although this is not necessary in all instances. In some cases, outdoor unit108may be mechanically connected to the indoor unit102. The outdoor unit108may extend through a hole in an external wall of the building to access the outdoor space. Alternatively, the outdoor unit108may be located remote from the indoor unit102and may be operatively connected by lines110carrying a working fluid and/or by one or more ducts. In some cases, the HVAC unit100may have a cooling mode and/or a heating mode for controlling the temperature of air inside of the building In some instances, such as when the HVAC unit is a mini-split HVAC system, the HVAC unit100may be mounted high in a room, toward the ceiling.

In some cases, the HVAC unit100may be in communication with a wireless controller112, which may be located remotely from the HVAC unit100. When so provided, the wireless controller112may be configured to communicate wirelessly with an onboard controller122of the HVAC unit100, and the onboard controller122may be configured to accept input signals, such as infra-red (IR) signals (IR codes), from the remotely located wireless controller112. In some instances, the wireless controller112may communicate with the onboard controller122of the HVAC unit100any suitable communication path, such as via a wired (Ethernet, USB, RS-232, etc.) and/or a wireless (Wifi, Bluetooth, Zigbee, etc.) communication link. Communication between the wireless controller112and the onboard controller122of the HVAC unit100may be unidirectional (e.g. from the wireless controller112to HVAC unit100) or bidirectional, as desired.

In some cases, the HVAC unit100may include an IR receiver that is configured to receive IR signals from the wireless controller112, and then pass those IR signals to the onboard controller122. Such IR signal may represent commands that are sent to the HVAC unit100from the wireless controller112, such as to change a setpoint temperature, change a mode (heat, cool) of the HVAC unit100, etc.

In some cases, the wireless controller112may store various IR protocols, along with a correspondence between the various IR protocols and different makes/models of HVAC units. When so provided, the user may use the wireless controller112to select a particular make/model that corresponds to their HVAC unit, and the wireless controller112may then look up and use the IR protocol that corresponds to the selected make/model when subsequently communicating with the user's HVAC unit100. In this way, the wireless controller112may be considered a universal wireless controller112that can communicate with a variety of makes/models of HVAC units, without having to access a remote database such as a remote IR protocol database in the cloud. This may be particularly useful when the wireless controller112does not currently have access to the cloud.

It is contemplated that the onboard controller122may be configured to control at least parts of the HVAC unit100, as described further herein. In some cases, the HVAC unit100may also include a local temperature sensor124. The onboard controller122may reference the temperature sensed by the local temperature sensor124and control whether the HVAC unit100is in a cooling mode, a heating mode, and/or whether the HVAC unit100is currently activated or not. More particularly, the onboard controller122may thermostatically control the temperature in the space50based on the temperature sensed by the local temperature sensor124and a programmable setpoint.

When the temperature sensor124of the HVAC unit100is housed in or around the indoor unit102, such as in some mini-split HVAC systems, the sensed temperature may not represent the temperature that is experienced by the user in the space50, especially when the mini-split HVAC system is mounted high in a room where the temperature of the air is generally warmer. In some cases, and as further detailed herein, the wireless controller112may include its own temperature sensor126, and the wireless controller112may use the temperature sensed its own temperature sensor126to adjust or alter the programmable temperature setpoint of the HVAC unit100in order to deliver improved comfort to the user.

FIG.2is a schematic block diagram of an illustrative wireless controller200, which may be the same or similar to the wireless controller200ofFIG.1. The wireless controller200may include a controller212(e.g., microcontroller, microprocessor, etc.) operatively coupled to a memory202, a user interface214, transmitter208(sometimes a transceiver), a temperature sensor210, a humidity sensor218, and an I/O port216. The temperature sensor(s) (e.g., temperature sensor210), humidity sensor(s) (e.g., humidity sensor218), and/or occupancy sensor(s) may be located in the housing of the wireless controller200and/or located remotely from the wireless controller200.

The transmitter208may be configured to communicate using one or more wireless communication protocols, such as cellular communication, ZigBee, REDLINK™ Bluetooth, Wi-Fi, IrDA, infra-red (IR), dedicated short range communication (DSRC), EnOcean, and/or any other suitable common or proprietary wireless protocol, as desired. In some cases, the transmitter208may communicate commands from the wireless controller200to a remotely located HVAC unit224via an IR communication protocol that uses particular IR codes. The HVAC unit100may receive the IR codes from the transmitter208, and when appropriate, execute the received commands. Commands that may be sent to the HVAC unit224from the wireless controller200may include, for example, a command to change a setpoint temperature of the HVAC unit224, change a mode (heat, cool) of the HVAC unit224, etc.

In some instances, the controller212may include a pre-programmed chip, such as a very-large-scale integration (VLSI) chip and/or an application specific integrated circuit (ASIC). In such embodiments, the chip may be pre-programmed with control logic in order to control the operation of the wireless controller200. In some cases, the pre-programmed chip may implement a state machine that performs the desired functions. By using a pre-programmed chip, the controller212may use less power than other programmable circuits (e.g. general purpose programmable microprocessors) while still being able to maintain basic functionality. In other instances, the controller212may include a programmable microprocessor. Such a programmable microprocessor may allow a user to modify the control logic of the wireless controller200even after it is installed in the field (e.g. firmware update), which may allow for greater flexibility of the wireless controller200in the field over using a pre-programmed ASIC.

In some cases, the controller212may cause the wireless controller200to operate in accordance with programmable setpoints. In some cases, the programmable setpoints may correspond to comfort setpoint, such as a temperature setpoint, a humidity setpoint, etc. The programmable setpoints may be modified by a user to suit the user's particular comfort level and/or schedule.

In the example shown inFIG.2, the user interface214is operatively coupled to the controller212, and permits the wireless controller200to display and/or solicit information, such as operational parameters, as well as accept one or more user interactions with the wireless controller200. Through the user interface214, the user may, for example, view and manage the operation of one or more HVAC units (e.g., HVAC unit100, etc.) that service a space, such as a space within a building, house, or structure. In some cases, the user may be able to group one or more HVAC units to form an operating group to establish operating zones within the building, home, or structure. Alternatively, or in addition, the user may be able to set or modify programmable setpoints and/or set or modify an operating schedule for an HVAC unit and/or a group of HVAC units. Different programmable setpoints and/or operating schedules may be selected for different HVAC units and/or groups of HVAC units, if desired. When provided, the ability to view and manage multiple HVAC units servicing a space may facilitate improved management of a building, house, or structure.

In some cases, the user interface214may be a physical user interface that is accessible at the wireless controller200and may include a display204and/or a distinct keypad206. The display204may be any suitable display. In some instances, the display204may include or may be a liquid crystal display (LCD), an OLED, etc., and in some cases a fixed segment display, a dot matrix LCD display, a 7-segment type display, and/or may include one or more LEDs. In some cases, the display204may include a touch screen LCD panel that functions as both the display204and keypad206. The user interface214may be adapted to solicit values for a number of operating parameters, programmable setpoints, and/or to receive such values, but this is not required. In some cases, the user interface214may be provided as a separate unit from the wireless controller200, and may facilitate a user's interactions with the wireless controller200located within the building, house, or structure. For example, the user interface214may be provided as part of a remote device (e.g., remote device222), such as a smart phone, a tablet computer, a laptop computer, or a desktop computer. In some cases, the user interface214may communicate with the wireless controller200via a network such as, for example, a network220(e.g. Internet, Wifi, etc.).

In some cases, the user interface214may be configured with a shortcut button. In some cases, the distinct keypad206may include the shortcut button. In other cases, the display204may be a touch screen display and may be programmed to include the shortcut button. In cases where the user interface214is provided by a remote device222, the remote device222may provide the shortcut button. When a shortcut button is provided, the wireless controller200may assign a function or a sequence of functions to the shortcut button. When so provided, a user may simply actuate the shortcut button from the keypad206, and in response the controller212may execute the assigned function(s).

The assigned functions may be functions that are otherwise available in the menu structure of the controller212, but the shortcut button may make the assigned function(s) more readily accessible to the user. In some cases, the controller212may present one or more menu screens that allow the user to select one or more functions from a plurality of available functions. The selected function(s) may then be assigned to the shortcut button. In some cases, the controller212may allow a user to select two or more functions, as well as an order of execution of the two or more functions. Once one or more functions are assigned, the user may use the keypad206to activate the shortcut button, and the wireless controller200may transmit command signals to an HVAC unit (e.g., HVAC unit100) to carry out the one or more function(s) assigned to the shortcut button. In some cases, two or more different shortcut buttons may be provided, where the user may assign different function or function combinations to each of the shortcut buttons.

The memory202of the wireless remote200may be operatively coupled to the controller212and may be used to store any desired information, such as the aforementioned control algorithm, setpoints, IR codes, an IR database, schedule times, zones and groupings of HVAC units, shortcut button functional assignments, and the like. The memory202may be any suitable type of storage device including, but not limited to, RAM, ROM, EPROM, flash memory (e.g., NAND flash memory), an external SPI flash memory, a hard drive, and/or the like. In some cases, the memory202may include two or more types of memory. For example, the memory202may include a RAM, a ROM and a flash memory module. During operation, the controller212may store information within the memory202, and may subsequently retrieve the stored information from the memory202.

In certain embodiments, the HVAC unit224or an onboard controller of the HVAC unit224may include an IR receiver, and the transmitter208may communicate with the HVAC unit through IR signals. In some cases, the memory202of the wireless controller200may include a NAND flash memory that stores an IR database. In some cases, the IR database may include a lookup table that identifies a plurality of HVAC units and corresponding IR protocols. For example, some HVAC units may use a first IR protocol that has a first set of IR codes, and some HVAC units may use a second IR protocol that has a second set of IR codes. The NAND flash memory may store IR protocols, including the corresponding IR codes, for many different HVAC units that are available on the market. This may allow the wireless remote200to communicate with many different HVAC unit once deployed in the field. During setup, the wireless controller200may receive a selection of a particular HVAC unit224(e.g. brand/model) from a user via the user interface214. The controller212may then identify the particular HVAC unit224in the IR database lookup table and identify the IR protocol that corresponds to the user's HVAC unit224. The wireless remote200may then subsequently communicate with the HVAC unit224using the identified IR protocol.

While IR communication is used as one example, it is contemplated that the wireless controller200may communicate with the HVAC unit224using any suitable communication modality. For example, it is contemplated that the transmitter208may transmit signals to the onboard controller of the HVAC unit224using any suitable wireless and/or wired communication protocol. In some cases, the transmitter208may use an ad-hoc wireless network. In other cases, the transmitter208may utilize a wireless mesh network and more particularly, a ZigBee wireless or other mesh network. If the transmitter208does utilize a mesh network, the onboard controller may serve as the end node(s). In some cases, the transmitter208may utilize one or more wireless communication protocols including, but not limited to, cellular communication, ZigBee, REDLINK™, Bluetooth, Wi-Fi, IrDA, infra-red (IR), dedicated short range communication (DSRC), EnOcean, and/or any other suitable common or proprietary wireless protocol, as desired.

Once the wireless controller200has established communication the HVAC unit224, the wireless controller200may send instructions via IR (or other) commands to the HVAC unit224. For example, as discussed herein, in some cases, the wireless controller200may be programmed with a control algorithm that uses programmable setpoints, such as setpoints temperatures and humidity setpoints, to help control the operation of the HVAC unit224. Accordingly, the wireless controller200may receive the programmed setpoints (e.g., the setpoint temperature) and/or setpoint schedule from a user via the user interface214. The controller212may then instruct the transmitter208to send IR (or other) command signals in accordance with the identified IR protocol to the HVAC unit224that instruct the HVAC unit224to set the temperature in the space at the desired setpoint temperature.

In some cases, the HVAC unit224may include its own temperature sensor for determining the temperature in the space. The HVAC unit224may be configured to thermostatically control the temperature in a space based on the temperature sensed by its own temperature sensor. For some mini-split HVAC systems that are mounted high in a room and toward the ceiling, the temperature sensed by the temperature sensor of the HVAC unit224may not accurately reflect the temperature experienced by the user. Typically, it will measure a temperature that is warmer than what the user is experiencing, and thus the user may feel cold.

The temperature sensed by the temperature sensor210of the wireless controller200may be more representative of the temperature experienced by the user. Therefore, the control algorithm of the wireless controller may cause the wireless controller200to send IR command signals to the HVAC unit224to adjust the temperature setpoint used by the HVAC unit224so that the HVAC unit224thermostatically controls the temperature in the space, using its own temperature sensor, such that the temperature experienced by the user is more in line with the desired temperature setpoint.

In some instances, the I/O port216of the wireless controller200may permit the wireless controller200to communicate over one or more additional wired or wireless networks that may accommodate remote access and/or control of the wireless controller200via a remote device222such as, for example, a smart phone, tablet computer, laptop computer, personal computer, PDA, and/or the like. In some cases, the remote device222may provide a primary and/or a secondary user interface for the user to interact with the wireless controller200. In some cases, the wireless controller200may utilize a wireless protocol to communicate with the remote device222over a network220. In some cases, the network220may be a may be a Local Area Network (LAN) such as a Wi-Fi network or a Wide Area Network (WAN) such as the Internet. These are just some examples.

In some cases, the remote device222may execute an application program that facilitates communication and control of the wireless controller200. The application program may be provided by and downloaded from an external web service (e.g. Apple Inc.'s ITUNES®, Google Inc.'s Google Play, a proprietary server, etc.) for this purpose, but this is not required. In one example, the application program may cause the remote device222to receive and store data, such as programmable setpoints, operational parameters, operating schedules, etc. received from the wireless controller200. The application program may translate the data received from the wireless controller200and display the data to the user via the user interface of the remote device222. Additionally, the application program may be capable of accepting an input from a user through the user interface of the remote device222and transmitting accepted input to the wireless controller200. For example, if the user inputs include setpoint temperature changes, humidity setpoint changes, schedule changes, and/or other changes, the application program may transmit these changes to the remote device222.

FIG.3is a perspective view of an illustrative wireless controller300that may be an example of the wireless controller200ofFIG.2. The wireless controller300may send commands (e.g. IR codes) to set, for example, programmable setpoints, operating mode changes and/or other parameters to an HVAC unit. In the example shown, the wireless controller300may include a housing302and an optional stand304or other standing feature to aid in placing the wireless controller300on a surface, such as on the surface of a table, desk, counter, etc. Additionally and/or alternatively, in some cases, the wireless controller300may have a mounting feature to aid in mounting the wireless controller300to a wall or ceiling of a room in a building, house, or structure. If battery powered, the housing302may include a battery compartment for holding a battery or battery pack (not explicitly shown). The housing302may have any shape or size suitable for housing the internal electronics of the wireless controller300.

The wireless controller300may include a user interface306. In some cases, the user interface306may include a display308. In some cases, the display308may include or may be an LCD, an OLED, etc., and in some cases a fixed segment display, a dot matrix LCD display, a 7-segment type display, and/or may include one or more LEDs. In the example shown, the display308is a touch screen LCD panel that functions as both the display308and a keypad. In other cases, the user interface may have a physically distinct keypad. In addition, the housing302may include an opening or window310to aid in communicating with an HVAC unit. The opening or window310may extend at least partially around an outer perimeter of the housing302. In some cases, the window or opening310may be located along the top of the wireless controller300. In some cases, the window310may be transparent or semi-transparent to the Infrared (IR), and an IR transmitter and/or receiver may be positioned just behind the window310. The housing302may include a larger opening or window310than shown, or multiple windows310, if desired.

FIG.4is a schematic view of an exemplary building automation system400that may facilitate remote access and/or control using a wireless controller402, and that may be used to coordinate and control the HVAC unit100fromFIG.1. While an HVAC unit100is used as an example, it is contemplated that the wireless controller402may be used to facilitate remote access and/or control over other building automation systems, such as a security system or a lighting system.

As stated herein, the HVAC unit100may be a mini-split HVAC unit, however, this is not necessary. A front-view of the wireless controller402is shown inFIG.4. As can be seen, the wireless controller402looks similar to the wireless controller300ofFIG.3. The configuration of the components and the operation of the wireless controller402may be similar to the wireless controller200ofFIG.2. As such, in the example ofFIG.4, the wireless controller402may include a controller404(e.g., microprocessor, microcontroller, etc.), a memory406(e.g., a non-volatile memory, a flash memory, a NAND flash memory, etc.), a transmitter408(e.g., an IR transmitter, RF transmitter, Bluetooth transmitter, etc.) a user interface410(e.g., a display and in some cases a keypad), and a temperature sensor412.

According to various embodiments, the wireless controller402may be configured to set a programmable setpoint of the HVAC unit100. The HVAC unit100may then thermostatically control the temperature in a space based at least in part on: (1) the temperature sensed by the temperature sensor416of the HVAC unit100; and (2) the programmable setpoint received from the wireless controller402.

To configure communication between the wireless controller402and the HVAC unit100, the wireless controller402may allow a user to set an appropriate IR protocol to use during the communication. For instances, as shown inFIG.5A, the wireless controller402may include a user interface410with a display420, and may display a main menu button422on the display420or may include a mechanical main menu button422adjacent to the display. As shown inFIG.5B, after a user selects the main menu button422, the controller404of the wireless controller402may use the display420to present a main menu screen500to the user, including a set of options502. As can be seen, the set of options502may include a setup option504, a schedule option506, a shortcut button setup option508, etc. This is just one example of a suitable main menu screen500.

In some examples, to establish communication between the wireless controller402and HVAC unit100, the user may select the setup option504. After the setup option504is selected, and turning toFIG.5C, the controller404may present a brand screen510to the user, including a set of HVAC brands512. As can be seen, the set of HVAC brands512may include Brand1, Brand2, Brand3, Brand4, Brand5, Brand6, Brand7, Brand8, etc. In this case, the HVAC unit100that is in the user's space may be of Brand1. As such, the user may select Brand1from the set of HVAC brands512. Turning toFIG.5D, the controller404may then use the display420to present a set of models516of HVAC units made by Brand1on a models screen514. As can be seen, the set of Brand1models516may include Model1, Model2, Model3, Model4, Model5, Model6, Model7, Model8, etc. This is just one example.

Continuing with the example, the HVAC unit100that is in the user's space may be of Model1. As such, the user may select Model1from the set of Brand1models516. According to certain embodiments, once the user selects the appropriate model from the set of Brand1models516, the controller404may access the memory406(seeFIG.4). As stated above, in some cases, the memory406may include a non-volatile memory, such as a NAND flash memory. Turning toFIG.5E, in this example, the memory406may store an IR database518. As shown, the IR database518may include a two-level table structure, which may help improve query performance into the IR database518. In some cases, the IR database518may include a lookup table header520and flash pages522. In some cases, the lookup table header may include or contain a plurality of building automation systems, such as HVAC units, security systems, lighting systems, etc. In some cases, the building automation systems may be categorize according to a brand (e.g., a brand name) and a model (e.g., model number). In some cases, the flash pages522may include or contain a plurality of IR protocols that correspond to (i.e., are used to communicate with) the plurality of building automation systems included in the lookup table. In some cases, each flash page from the flash pages522may contain one IR protocol and the corresponding IR codes, however, this is not necessary. In some cases, the lookup table header520may contain an index or address for the flash page(s) that corresponds to each brand/model combination.

During use, the controller404may match the selected Brand from the set of HVAC brands512and the selected Model from the set of models516with the corresponding Brand/Model entry in the lookup table header520. The pointer or address524stored at that Brand/Model entry in the lookup table header520may point to the flash page522that contains the IR protocol and IR codes for that Brand/Model entry.

In some cases, the controller404may store the indication of correspondence between the HVAC unit100and the corresponding IR protocol in the memory406. In some cases, this correspondence may be stored in a different part of the memory406than the non-volatile portion (i.e. the NAND flash memory) that stores the IR protocols, such as in a separate non-volatile portion or a cache memory portion, but this is not required. In certain embodiments, for the wireless controller402to send IR command signals to the HVAC unit100, the controller404may access the memory406, identify the indication of correspondence, use the indication of correspondence to identify the IR protocol and IR codes to use, and instruct the transmitter408to send IR command signals to the IR receiver418of the HVAC unit100in accordance with the identified IR protocol and IR codes.

FIG.6is a flow diagram of an illustrative method600for programming a wireless controller to communicate with a selected HVAC unit. In some cases, the HVAC unit may be a mini-split HVAC unit. While an HVAC unit is used as an example, it is contemplated that the method may be used to communicate with a security system, lighting system, and/or any other suitable building automation system.

The method600may begin at step602where the wireless controller may receive a selection of a particular mini-split HVAC unit. The wireless controller may store the selection of the particular mini-split HVAC unit in memory. In some examples, the selection of the particular mini-split HVAC unit may be made by receiving a selection of a brand of the mini-split HVAC unit and receiving a selection of a model of the mini-split HVAC unit.

In some examples, a non-volatile memory may store an IR database. In some examples, the IR database may include a two-level table structure that includes a lookup table header and flash pages. In some examples, the lookup table header may include or contain a plurality of mini-split HVAC units categorized according to a brand and/or a model. In some examples, the flash pages may include or contain a plurality of IR protocols that correspond to the plurality of mini-split HVAC units in the lookup table header. In some cases, each flash page may contain one IR protocol and the corresponding IR codes, however, this is not necessary. In some cases, the lookup table header may contain an index or address for the flash page(s) that corresponds to each brand/model combination of the plurality of mini-split HVAC units. At step604, the wireless controller may store an indication of the correspondence between the selected mini-split HVAC unit and the corresponding IR protocol in the non-volatile memory or a separate volatile or non-volatile memory.

At step606, the wireless controller may access the non-volatile memory, and as step608, the wireless controller may identify the IR protocol for use in communicating with the particular mini-split HVAC unit selected by the user. At step610, the wireless controller may transmit IR commands (e.g. IR codes) to the particular mini-split HVAC unit in accordance with the identified IR protocol. In some examples, the wireless controller may transmit IR commands to set a programmable setpoint of the mini-split HVAC unit to a commanded setpoint temperature. In some examples, the commanded setpoint temperature may be based on a desired setpoint temperature set by a user and the temperature sensed by a temperature sensor of the wireless controller. At step612, the wireless controller may determine if the transmission was successful. If the transmission was not successful, the wireless controller may return to step610and retry the transmission. If the transmission was successful, the method600may end.

Referring back toFIG.4, once communication is established between the wireless controller402and the HVAC unit100, the wireless controller402may send commands to set a programmable setpoint of the HVAC unit100, and the HVAC unit100may then thermostatically control the temperature in the space based at least in part on: (1) the temperature sensed by a temperature sensor416of the HVAC unit100; and (2) the set programmable setpoint. According to various embodiments, the wireless controller402may be programmed with a control algorithm that uses programmable setpoints, such as setpoint temperatures, to control and/or influence the operation of the HVAC unit100. In some cases, the wireless controller402may receive a desired setpoint temperature from a user via the user interface410of the wireless controller402. In the example shown inFIG.7A, the user may use increment/decrement buttons422of the user interface410to enter and/or change the desired setpoint temperature. As can be seen, the setpoint temperature is set to 72° F. inFIG.7A. Referring back toFIG.4, the controller404may then instruct the transmitter408to send appropriate IR command signals to the IR receiver418of the HVAC unit100to set the programmable setpoint of the HVAC unit100to the desired temperature setpoint. In this example, the IR command signals may instruct the HVAC unit100to set the temperature in the space at 72° F.

FIG.7Bdepicts an exemplary graph of the operation of the building automation system400in a heating mode after receiving the 72° F. setpoint temperature from the wireless controller402.FIG.7Bshows a Wireless Controller Sensed (WCS) temperature700sensed by the temperature sensor412of the wireless controller402, an HVAC Unit Sensed (HUS) temperature702sensed by the temperature sensor416of the HVAC unit100, and a desired setpoint temperature704. In the example shown, the control algorithm of the controller404of the wireless controller402may sample the WCS temperature700every 10 minutes. In other cases, this sampling period may be every 2 minutes, 5 minutes, 10, minutes, 20 minutes, 30 minutes, hour, 2 hours, 5 hours, 2 days, or any other suitable sample period. In some cases, this sample period may be dynamic, and may be based on, for example, the rate of change of the Wireless Controller Sensed. In any event, an offset temperature706may be calculated at each sampling period by finding a difference between the desired setpoint temperature704and the WCS temperature700. A change in the offset temperature may also be calculated at each sampling period by finding a difference in the offset temperature706of the current sampling period from the offset temperature706of the previous sampling period.

In the example shown inFIG.7B, the WCS temperature700is initially at 69° F., the HUS temperature702is initially at 70° F. (e.g. because the HVAC Unit100is mounted near the ceiling), and the offset temperature is 3° F. In some cases, the HVAC Unit100may communicate the HUS temperature702to the wireless controller402. However, in other cases, the wireless controller402may not know the HUS temperature702, and as will be discussed below, the wireless controller402may determine a measure of the HUS temperature702using the WCS temperature700, the desired setpoint temperature704, and the offset temperature706.

Continuing with the example ofFIG.7B, after 10 minutes with the HVAC unit100in the heating mode, the WCS temperature700has increased to 69.7° F., making the offset temperature7062.3° F., and the change in the offset temperature7080.7° F. After another ten minutes with the HVAC unit100in the heating mode, the WCS temperature700sensed by the wireless controller402has increased to 70.5° F., making the offset temperature7061.5° F., and the change in the offset temperature7080.8° F. After another ten minutes with the HVAC unit100in the heating mode, the WCS temperature700has increased to 70.9° F., making the offset temperature7061.1° F., and the change in the offset temperature7080.4° F. After yet another ten minutes with the HVAC unit100in the heating mode, the WCS temperature700has increased to 71° F., making the offset temperature7061.0° F., and the change in the offset temperature7080.1° F. After another ten minutes with the HVAC unit100in the heating mode, the WCS temperature is still at 71° F., making the offset temperature7061.0° F., and the change in the offset temperature7080.0° F. As can be seen, the WCS temperature700has stabilized at 71° F.

In various embodiments, the control algorithm may provide instructions for the controller404of the wireless controller402to wait until the WCS temperature700has stabilized to determine whether additional commands need to be sent to adjust the temperature setpoint of the HVAC Unit100. In some cases, stabilization may be determined based on the change in the offset temperature708. For example, if the offset temperature706has not changed or has changed very little over a given time interval, it may be understood that the thermostatic control of the HVAC unit100is now cycling on and off to maintain the space temperature as measured by the HVAC unit100(e.g. the HUS temperature702), which in this example shown is different from the WCS temperature700. As such, the WCS temperature700(the temperature at the wireless controller) is not likely to change much further in response to the 72° F. setpoint temperature command that was sent to the HVAC unit100.

As noted above, stabilization may be determined based on the change in the offset temperature708. For instance, in the present case, the controller404may wait to receive two consecutive sample periods where the change in offset temperature708has a value that is less than or equal to a 0.05° F. threshold to determine that the WCS temperature700has stabilized. In other cases, the controller404may use a longer time interval (e.g., three, four, five, etc. consecutive sample periods) or a shorter interval (e.g., one sampling period of the change in offset temperature708having a 0.0° F. of less value) to determine whether the WCS temperature700has stabilized. In some cases, the controller404may use a larger change of rate threshold (e.g., 0.1° F., 0.15° F., 0.2° F., 0.3° F., etc.) or a smaller change of rate threshold (e.g., 0.04° F., 0.03° F., 0.02° F., 0.01° F., etc.), as desired. In some cases, the change of rate threshold may be dynamic, and may be dependent on, for example, the season, heating or cooling mode of the HVAC unit100, and/or any other suitable parameter.

Once the controller404determines that the WCS temperature700has stabilized, the controller404may use the offset temperature706between the desired temperature setpoint704and the WCS temperature700to determine whether additional commands need to be sent to the HVAC unit100. For example, in some cases, the control algorithm of the wireless controller402may use a threshold comfort offset to the controller404. In some cases, if the offset temperature706is greater than or equal to the threshold comfort offset, then the controller404may determine an updated control setpoint temperature710. The updated control setpoint temperature may be based on the offset temperature706and the previous setpoint temperature704(i.e., 72° F.). For instance, in the current example, the threshold comfort offset may be ±0.5° F. Accordingly, if the offset temperature706is within ±0.5° F. of 72° F., then the wireless controller402may allow the HVAC unit100to continue its operation of maintaining the current temperature in the space. However, as in the example shown, the offset temperature is 1.0° F., which is greater than the threshold comfort offset of ±0.5° F. As such, the wireless controller402may determine that the HUS temperature702is currently at 72° F. (i.e., the temperature sensor416of the HVAC unit100is sensing a temperature of 72° F. in the space, and the temperature sensor412of the wireless controller402is sensing a temperature of 71° F. in the space). The controller404may determine an updated control setpoint temperature710by adding the stabilized offset temperature706(i.e., 1.0° F.) to the current setpoint temperature704(i.e., 72° F.). The controller404may then instruct the transmitter408of the wireless controller402to send IR command signals to the IR receiver418of the HVAC unit100(in accordance with the appropriate IR protocol) to change the setpoint temperature704of the HVAC unit100to the updated control setpoint temperature710(i.e., 73° F.).

In some cases, even though the wireless controller402has sent IR command signals to the HVAC unit100to update the setpoint temperature, the controller404may not display the updated control setpoint temperature on the display420of the user interface410of the wireless controller402. Rather, the controller404may continue to display the initial setpoint temperature or the desired setpoint temperature (i.e., 72° F.) on the display420. However, in other embodiments, the controller404may use the display420to indicate that it has updated the setpoint temperature.

Continuing with the example ofFIG.7B, the IR command signals may force the HVAC unit100to adjust its operation from maintaining the current temperature in the space to increasing the temperature in the space to the new updated control setpoint temperature710(i.e., 73° F.). After ten minutes, the controller404may sample the WCS temperature700and find that the WCS temperature has increased to 71.2° F., making the offset temperature7060.8° F., and the change in the offset temperature7080.2° F. After another ten minutes, the WCS temperature700has increased to 71.75° F., making the offset temperature7060.25° F., and the change in the offset temperature7080.55° F. After another ten minutes, the WCS temperature700has increased to 72° F., making the offset temperature7060.0° F., and the change in the offset temperature7080.25° F. In some cases, once the HUS temperature reaches the setpoint temperature, whether it is the desired setpoint temperature or the updated control setpoint temperature, the HVAC unit100cycle on and off to maintain the HUS temperature at the updated control setpoint temperature710of 73° F.

FIG.7Cdepicts another exemplary graph of the operation of the building automation system400in a cooling mode after receiving a 72° F. setpoint temperature from the wireless controller402. In this example, the control algorithm of the wireless controller402may provide instructions to sample the WCS temperature700every 30 minutes (or any other suitable sample period). As shown, the WCS temperature700is initially at 75° F., the HUS temperature702is initially at 76° F., and the offset temperature is −3.0° F. After 30 minutes, the WCS temperature700has decreased to 73° F., making the offset temperature706−1.0° F., and the change in the offset temperature7082.0° F. After another 30 minutes, the WCS temperature700has now decreased to 71° F., making the offset temperature7061.0° F., and the change in the offset temperature7082.0° F. After another 30 minutes, the WCS temperature700remains at 71° F., keeping the offset temperature7061.0° F., and the change in the offset temperature7080.0° F.

In this example, the controller404may wait one sample period to determine if the change in offset temperature708has a value that is either less than or equal to a 0.05° F. change rate threshold (or other change rate threshold) to determine that the WCS temperature700has stabilized. Accordingly, since the change in offset temperature708is less than the change rate threshold at the current sampling period, the controller404may determine that HVAC unit100is not cycling on and off to maintain the temperature in the space and therefore, the WCS temperature700is unlikely to change further in response to the transmitted 72° F. setpoint temperature. Once the controller404determines that the WCS temperature700has stabilized, the controller404may determine if the offset temperature is greater than or equal to a ±0.5° F. threshold offset (or any other suitable threshold offset). Since the offset temperature is 1.0° F., the wireless controller402may determine that the HUS temperature702is currently at 72° F. In response, the controller404may instruct the transmitter408to send IR command signals to the IR receiver418of the HVAC unit100in accordance with the appropriate IR protocol to change the setpoint temperature704of the HVAC unit100to an updated control setpoint temperature710(i.e., 73° F.). In some cases, the IR command signals may force the HVAC unit100to adjust its operation from maintaining the current temperature in the space to increasing the temperature in the space to the new updated control setpoint temperature710(i.e., 73° F.).

After 30 minutes, the controller404may sample the WCS temperature700once again and find that the WCS temperature has increased to 72° F., making the offset temperature7060.0° F., and the change in the offset temperature7081.0° F. Once the HUS temperature702reaches the current setpoint temperature of the HVAC unit100, the HVAC unit101may cycle on and off to maintain that temperature. This will maintain the desired WCS temperature at the wireless controller402.

According to certain embodiments, the control algorithm may be stored in the memory406. In some cases, the control algorithm may reference a schedule, and the controller404may instruct the transmitter408to send IR command signals to the IR receiver418of the HVAC unit100to set desired setpoint temperatures at designated times. In various cases, when there is an initially determined offset temperature (e.g., the offset temperature706) between the setpoint temperature704and the stabilized WCS temperature700, the desired setpoint temperatures may be calculated by adding the offset temperature706to the desired setpoint temperatures from the schedule at each corresponding time. As such, the wireless controller402may automatically set a setpoint temperature (e.g., the setpoint temperature704) to an appropriate updated control setpoint temperature (e.g., the updated control setpoint temperature710) for a given space without having to reevaluate the offset temperature between the setpoint temperature and the stabilized controller temperature during each schedule time period. Instead, it is contemplated that once a stabilized offset temperature706is determined, that same stabilized offset temperature706may be used for a significant length of time. In some cases, the stabilized offset temperature706may only be updated every week, month, upon a change in season, or at any other interval or upon request by the user.

FIG.8shows an illustrative method800for a wireless controller402to remotely control a mini-split HVAC unit100configured to receive commands to set a programmable setpoint of the mini-split HVAC unit100such that the mini-split HVAC unit100may thermostatically control the temperature in a space based at least in part on the temperature sensed by a local temperature sensor416of the mini-split HVAC unit100and the programmable setpoint. The illustrative method800begins at step802, where the wireless controller402may send a command from a remote location to set the programmable setpoint of the mini-split HVAC unit100to a desired setpoint temperature. In some examples, the wireless controller402may receive the desired setpoint temperature from a user via a user interface of the wireless controller402. The wireless controller402may send a command to the mini-split HVAC unit100using IR signals, in accordance with an appropriate IR protocol, to set the temperature setpoint of the HVAC unit100to the desired setpoint temperature.

At step804, the wireless controller402may sense the temperature from the remote location. In some examples, the wireless controller402may sense the temperature at specific time intervals (e.g., every 10 minutes, every 20 minutes, every 30 minutes, every hour, etc.). After waiting and sensing the temperature at a time interval, at step806, the wireless controller402may determine whether the temperature sensed has stabilized. In some examples, stabilization may be determined based on the change in the sensed temperature over the specified time interval. For instance, if the sensed temperature has not changed or has changed very little over the specified time interval, it may be understood that the mini-split HVAC unit100is now cycling on and off to maintain the temperature in the space, and therefore the temperature sensed by the wireless controller402is unlikely to change significantly going forward. If the sensed temperature has not stabilized, the wireless controller402may wait till the next time interval and sense the temperature again at step804. This may continue until the sensed temperature has stabilized.

Once the sensed temperature has stabilized, at step808, the wireless controller402may determine a stabilized offset temperature by finding the difference between the desired setpoint temperature and the stabilized temperature. At step810, the wireless controller402may determine whether the difference between the desired setpoint temperature and the stabilized temperature is greater than or equal to a specified threshold. If the difference is less than the specified threshold, the wireless controller may allow the mini-split HVAC unit100to continue its operation without adjusting its temperature setpoint, and method800may end. If the difference is greater than or equal to the specified threshold, at step812, the wireless controller402may send a command to the mini-split HVAC unit100to set the programmable setpoint to an updated control setpoint temperature. In some examples, the wireless controller may determine the updated control setpoint temperature by adding the stabilized offset temperature to the desired setpoint temperature. In some examples, the wireless controller402may send a command to the mini-split HVAC unit100using IR signals, in accordance with an appropriate IR protocol, that changes the temperature setpoint of the HVAC unit100to the updated control setpoint temperature. Once the command has been sent, the wireless controller402may wait till the next time interval and sense the temperature again at step804. The wireless controller402may then proceed with method800in a similar fashion until the sensed temperature is at the desired setpoint temperature or the difference between the desired set pint temperature and the stabilized temperature is within a specified threshold.

According to various embodiments, the user interface410of the wireless controller402may be configured with a shortcut button. In some cases, the shortcut button may be a physical button (e.g., an electromechanical button) spaced from the display and potentially grouped with other physical buttons, such as on a keypad, for example. In other cases, such as when the display420is a touchscreen, the shortcut button may be on the display. In some cases, the shortcut button may be created and/or updated by the controller404by assigning a function or a plurality of functions to the shortcut button. For example, and referring back toFIG.5A, the user may select the main menu button422. As shown inFIG.5B, after the user selects the main menu button422, the controller404may use the display420to present the main menu screen500to the user, including a set of options502. As can be seen, the set of options502may include the setup option504, the schedule option506, the shortcut button setup option508, etc. In some examples, to create and/or update the shortcut button, the user may select the shortcut button setup option508.

Turning toFIG.9A, and in the example shown, after the shortcut button setup option508is selected, the controller404may use the display420to present a shortcut button menu screen900that includes a create a new shortcut button option902, an update existing shortcut button option904, and a remove existing shortcut button option906. This is just one example of the shortcut button menu screen900and the various options that may be presented on the shortcut button menu screen900. In this case, the user may select create a new shortcut button option902. The controller404may then use the display420to present a shortcut button definition options screen910, as shown inFIG.9B. In some cases, the shortcut button definition option screens910may include a schedule settings option912, a network settings option914, a display settings option916, an auto changeover (ACO) settings option918, an adaptive intelligent recovery (AIR) settings option920, a date/time settings option922, a temperature settings option924, an equipment status option926, and a device information option928. This is just one example of the shortcut button definition options screen910and the various options that may be presented on the shortcut button menu screen900. In the example shown, the user selects the schedule settings option912.

Turning toFIG.9C, the controller404may then use the display420to present a schedule settings functions screen930. In some cases, the schedule settings functions screen930may include an hour scheduling option, an eight hour scheduling option, a day scheduling option, a week scheduling option, a month scheduling option, a year scheduling option, a weekdays scheduling option, a weekends scheduling option, and a custom scheduling option. This is just one example of the schedule settings functions screen930and the various schedule functions that may be presented on the schedule settings functions screen930. In this case, the user selects the weekdays scheduling option.

Turning toFIG.9D, the controller404may then use the display420to present a weekday settings screen932. In some cases, the weekday settings screen932may include a temperature settings portion934and a time settings portion936. In some cases, the user may use increment/decrement temperature arrows938to increase or decrease a setpoint temperature940. In some cases, the user may also use increment/decrement time arrows942A and942B to change a time interval944for which the setpoint temperature940is set. In this example, the user may work during the weekdays. Accordingly, the user may not be home between the hours of 8:00 AM and 5:00 PM during weekdays. As such, the user may set the setpoint temperature940to 65° F. between the hours of 8:00 AM and 5:00 PM on the weekdays. In some cases, the weekday settings screen932may also include a back option for moving back to the previous screen (in this case, the schedule settings functions screen930ofFIG.9C), a next option for moving to the next screen, and a submit option for submitting the setpoint temperature940for the time interval944. This is just one example of the weekday settings screen932and the various features that may be presented on the weekday settings screen932. In this case, the user may select the next option.

Turning toFIG.9E, the controller404may then use the display420to present a second weekday settings screen946. Similar to the weekday settings screen932, the weekday settings screen946may also include the increment/decrement temperature arrows938to increase or decrease the setpoint temperature940and the increment/decrement time arrows942A and942B to change the time interval944for which the setpoint temperature940is set. In this example, the user may be home and awake on the weekdays between the hours of 5:00 PM and 10:00 PM. As such, the user may turn the setpoint temperature940up to 70° F. between the hours of 5:00 PM and 10:00 PM. In this case, the user may then select the next option.

Turning toFIG.9F, the controller404may then use the display420to present a third weekday settings screen948. Similar to the weekday settings screens932and946, the weekday settings screen948may also include the increment/decrement temperature arrows938to increase or decrease the setpoint temperature940and the increment/decrement time arrows942A and942B to change the time interval944for which the setpoint temperature940is set. In this example, the user may be home and asleep on the weekdays between the hours of 10:00 PM and 8:00 AM. As such, the user may turn the setpoint temperature940down to 67° F. between the hours of 10:00 PM and 8:00 AM. In this case, the user may then select the submit option.

Turning toFIG.9G, the controller404may then use the display420to present a shortcut button label screen950. In some cases, the shortcut button label screen950may include an alphabet keypad952that the user can use to label the shortcut button. In some cases, the alphabet keypad942may include a numeric button option954that the user can select to bring up a numerical keypad (not shown). This is just one example of the shortcut button label screen950and the various features that may be presented on the shortcut button label screen950. In this case, once the user has selected a label for the shortcut button, the user may select the submit option and the controller404may assign the weekdays scheduling option functions and the label to the shortcut button.

Turning toFIG.9H, the controller404may then use the display420to present a shortcut button956on the user interface410. As shown, in this example, the user has labeled the shortcut button956“WEEKDAY SETTINGS”. In this case the label “WEEKDAY SETTINGS” appears on the shortcut button956. In other embodiments, the label may appear by or adjacent the shortcut button956. For example, in some cases, the shortcut button956may be an electromechanical button spaced from the display420and positioned immediately adjacent to the display420. The label may appear on the display420adjacent to the electromechanical shortcut button (e.g. soft key). In addition, in some cases, as shown by arrows958A-958C, the controller404may be configured to allow the user to move the shortcut button956to different locations on the display420, if desired.

According to various embodiments, when the shortcut button956is subsequently activated, the controller404may instruct the transmitter408to send IR command signals to the IR receiver418of the HVAC unit100to set the desired setpoint temperatures at the designated times based on the assigned weekdays scheduling option functions. Furthermore, in this case, the controller404may automatically set the setpoint temperatures of 65° F., 70° F., and 67° F. to their updated control setpoint temperatures of 66° F., 71° F., and 68° F. As such, the transmitter may send IR command signals, in accordance with an appropriate IR protocol, to the IR receiver418of the HVAC unit100to set the setpoint temperatures at 66° F. between the hours of 8:00 AM and 5:00 PM, 71° F. between the hours of 5:00 PM and 10:00 PM, and 68° F. between the hours of 10:00 PM and 8:00 AM.

In some cases, the user may once again select the main menu button422. As shown inFIG.5B, after the user selects the main menu button422, the controller404may once again use the display420to present the main menu screen500. The user may then select the shortcut button setup option508. Referring tack toFIG.9A, after the shortcut button setup option508is selected, the controller404may once again use the display420to present a shortcut button menu screen900and the user may select the create a new shortcut button option902. Turning toFIG.9B, the controller404may then use the display420to present a shortcut button definition options screen910and the user may select the device information option928.

Turning toFIG.9I, the controller404may then use the display420to present a device information functions screen960. In some cases, the device information functions screen960may include current schedules information964, current network settings information966, current display settings information968, and current temperature settings970. In some cases, the device information functions screen960may also include a priority table962that may be used to specify an order at which the selected functions are presented on the display420. As shown by arrows972A-972D, the controller404may be configured to allow the user to move the functions964-970into the priority table962. This is just one example of the device information functions screen960and the various device information functions that may be presented on the device information functions screen960.

Turning toFIG.9J, the current display settings information968has been placed in the first cell of the priority table962, the current schedules information964has been placed in the second cell of the priority table962, the current temperature settings970has been placed in the third cell of the priority table962, and the current display settings information968has been placed in the fourth cell of the priority table962. This is just one example of how the device information functions964-970may be prioritized. In other cases, there may not be a priority table and the controller404may be configured to prioritize functions in a different manner. In this case, the user may then select the submit option. Turning back toFIG.9G, the controller404may once again use the display420to present a shortcut button label screen950. Once the user has selected a label for the shortcut button, the user may select the submit option and the controller404may assign the device information functions and the label to the shortcut button.

Turning toFIG.9K, the controller404may then use the display420to present a shortcut button974on the user interface410. As shown, in this example, the user has labeled the shortcut button974“WIRELESS CONTROLLER STATUS”. In this case the label “WIRELESS CONTROLLER STATUS” appears on the shortcut button974. In addition, in some cases, as shown by arrows976A-976B, the controller404may be configured to allow the user to move the shortcut button976to different locations on the display420. This is just one example of how the controller404may use the display420to present the shortcut buttons956and974. In other embodiments, the shortcut buttons956and974may be presented in a different manner.

According to various embodiments, when the shortcut button974is subsequently activated, the controller404may use the display420to present the device information functions964-970based on the order specified by the priority table962(i.e., the cell of the priority table962that each of the device information functions964-970occupies). In this case, the current display settings information968may be displayed first, the current schedules information964may be displayed second, the current temperature settings information970may be displayed third, and the current display settings information968may be displayed fourth. Similarly, other functions that the controller404may control, such as operating functions of the HVAC unit100may be assigned an order or sequence of operation and the controller404may instruct the transmitter408to send IR command signals to the IR receiver418of the HVAC unit100to carry out the functions assigned to the shortcut button (e.g., shortcut buttons956and974) according to the specified order.

FIG.10shows an illustrative method1000for operating a wireless controller402configured to send commands to a mini-split HVAC unit100that includes an IR receiver, and the mini-split HVAC unit100may be configured to thermostatically control the temperature in a space based at least in part on the temperature sensed by a temperature sensor associated with the mini-split HVAC unit100in conjunction with a programmable setpoint. The method1000may begin at step1002, where the wireless controller402may receive a selection of a shortcut button definition option. In some examples, the shortcut button may be a physical button (e.g., an electromechanical button) on a user interface of the wireless controller and the wireless controller receives selection of the shortcut button definition option by activation of the shortcut button. In some examples, a touchscreen display may be included on the user interface and the shortcut button may be created and/or updated and the wireless controller receives selection of the shortcut button definition option from an options menu presented by the display.

At step1004, and after receiving selection of the shortcut button definition option, the wireless controller402may use the display to present menu screens that allow a user to select functions from predefined functions that can be assigned to the shortcut button. In some examples, the menu screens presented may also allow the user to specify an order of sequence that the selected functions should be executed. At step1006, the wireless controller402may receive a selection of functions to assign to the shortcut button. At step1008, the wireless controller402may determine whether the user would like to select more functions to assign to the shortcut button. In some examples, the wireless controller402may use the display to present a select more functions option or a next option to allow the user to select more functions, if desired. In some examples, the wireless controller402may use the display to present a submit option or a finished option to indicate that the user is done selecting functions.

If the wireless controller402determines that the user would like to select more functions to assign to the shortcut button, at step1004, the wireless controller402may use the display to present more functions. If the wireless controller402determines that the user is done selecting functions, at step1010, the wireless controller402may assign the selected functions to the shortcut button. The shortcut button is then active.

At step1012, when the shortcut button is subsequently activated by a user, the wireless controller402may send or transmit commands to the mini-split HVAC unit100, and in response the mini-split HVAC unit100may carry out the selected and assigned functions. In some examples, the mini-split HVAC unit100may also carry out the selected and signed functions in an order or sequence specified by the user.

Method examples described herein can be machine or computer-implemented at least in part. Some examples can include a computer-readable medium or machine-readable medium encoded with instructions operable to configure an electronic device to perform methods as described in the above examples. An implementation of such methods can include code, such as microcode, assembly language code, a higher-level language code, or the like. Such code can include computer readable instructions for performing various methods. The code may form portions of computer program products. Further, in an example, the code can be tangibly stored on one or more volatile, non-transitory, or non-volatile tangible computer-readable media, such as during execution or at other times. Examples of these tangible computer-readable media can include, but are not limited to, hard disks, removable magnetic or optical disks, magnetic cassettes, memory cards or sticks, random access memories (RAMs), read only memories (ROMs), and the like.

The above description is intended to be illustrative, and not restrictive. For example, the above-described examples (or one or more aspects thereof) may be used in combination with each other. Also, in the above Description, various features may be grouped together to streamline the disclosure. This should not be interpreted as intending that an unclaimed disclosed feature is essential to any claim. Rather, inventive subject matter may lie in less than all features of a particular disclosed embodiment. Thus, the following claims are hereby incorporated into the Description as examples or embodiments, with each claim standing on its own as a separate embodiment, and it is contemplated that such embodiments can be combined with each other in various combinations or permutations.