Patent ID: 12196585

In accordance with common practice, the various features illustrated in the drawings may not be drawn to scale. Accordingly, the dimensions of the various features may be arbitrarily expanded or reduced for clarity. In addition, some of the drawings may be simplified for clarity. Thus, the drawings may not depict all of the components of a given apparatus (i.e., a device) or method. Finally, like reference numerals may be used to denote like features throughout the specification and figures.

DETAILED DESCRIPTION

Various aspects of the present disclosure are described below. It should be apparent that the teachings herein may be embodied in a wide variety of forms and that any specific mechanism, function, or both disclosed herein is merely representative. Based on the teachings herein, one skilled in the art should appreciate that an aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways, even if not specifically illustrated in the figures. For example, an apparatus may be implemented, or a method may be practiced, using any number of the aspects set forth herein whether disclosed in connection with a method or an apparatus. Further, the disclosed apparatuses and methods may be practiced using mechanisms or functionality known to one of skill in the art at the time this application was filed, although not specifically disclosed within the application.

In addition, such an apparatus may be implemented, or such a method may be practiced, using mechanisms or functionality disclosed elsewhere in the application and/or using mechanisms and functionality known to one of skill in the art at the time of filing this application and which is not set forth herein.

The word “exemplary” is used exclusively herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

The phrases “connected to,” “coupled to,” and “in communication with” refer to any form of interaction between two or more entities, including mechanical, electrical, magnetic, electromagnetic, fluid, and thermal interaction. Two components may be functionally coupled to each other even though they are not in direct contact with each other. The term “abutting” refers to items that are in direct physical contact with each other, although the items may not necessarily be attached together. The phrase “fluid communication” refers to two features that are connected such that a fluid within one feature is able to pass into the other feature.

Referring toFIG.1, a schematic block diagram illustrates one embodiment of a system100for measuring water consumption and performing other functions. The system100may be used for the benefit of one or more users110, which may include a first user112, a second user114, a third user116, and a fourth user118, as shown inFIG.1. (The number of users110who may employ or use the system100may be varied within the scope of the disclosed subject matter. The four users112,114,116,118identified inFIG.1are provided only as an example of one potential implementation.) Each of the users110may use one of a variety of computing devices120, which may include any of a wide variety of devices that carry out computational steps, including but not limited to a desktop computer122used by the first user112, a pulse detecting device124coupled or positioned adjacent to a water meter310(illustrated inFIG.3) used by the second user114, a smartphone126used by the third user116, a multi-zone irrigation flow controller128used by the fourth user118, and the like. The systems and methods presented herein may be carried out on any type of computing device120and may be used by a single user110or multiple different users110.

The computing devices120may optionally be connected to each other and/or other resources. Such connections may be wired or wireless, and may be implemented through the use of any known wired or wireless communication standard, including but not limited to Ethernet, 802.11a, 802.11b, 802.11g, and 802.11n, universal serial bus (USB), Bluetooth, cellular, near-field communications (NFC), Bluetooth Smart, ZigBee, Z-Wave, and the like. InFIG.1, by way of example, wired communications are shown with solid lines and wireless communications are shown with dashed lines.

Communications between the various elements ofFIG.1may be routed and/or otherwise facilitated through the use of routers130. The routers130may be of any type known in the art, and may be designed for wired and/or wireless communications through any known communications standard including, but not limited to, those listed above. The routers130may include, for example, a first router132that facilitates communications to and/or from the desktop computer122, a second router134that facilitates communications to and/or from the pulse detecting device124, a third router136that facilitates communications to and/or from the smartphone126, and a fourth router138that facilitates communications to and/or from the multi-zone irrigation flow controller128. Alternatively, a single router (e.g., the first router132) could process the communications.

The routers130may facilitate communications between the computing devices120and one or more networks140, which may include any type of network, including, but not limited to, local area networks (such as a local area network142) and/or wide area networks (such as a wide area network144) or a combination of local and wide area networks140. In one example, the local area network142may be a network140that services an entity such as a business, non-profit entity, government organization, or the like. The wide area network144may provide communications for multiple entities and/or individuals, and in some embodiments, may comprise the Internet. The local area network142may communicate with the wide area network144. If desired, one or more routers130or other devices may be used to facilitate such communication.

The networks140may store information on servers150or other information storage devices. As shown, a first server152may be connected to the local area network142, and may thus communicate with devices120connected to the local area network142, such as the desktop computer122and the pulse detecting device124. A second server154may be connected to the wide area network144and may thus communicate with devices120connected to the wide area network144, such as the smartphone126and the multi-zone irrigation flow controller128. If desired, the second server154may be a web server that provides web pages, web-connected services, executable code designed to operate over the Internet, and/or other functionality that facilitates the provision of information and/or services over the wide area network144.

Referring toFIG.2A, a schematic block diagram illustrates one embodiment of a computing device128(which comprises one example of the computing devices120illustrated inFIG.1) that enables implementation of embodiments of the present disclosure in a standalone computing environment. The computing device128may be, for example, the multi-zone irrigation flow controller128ofFIG.1. Alternatively, the computing device may comprise a single-zone irrigation flow controller (shown inFIG.3).

As shown, the multi-zone irrigation flow controller128may include a processor210that is designed to execute instructions. The processor210may be of any of a wide variety of types, including microprocessors with x86-based architecture or other architecture known in the art, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGA's), and the like. The processor210may optionally include multiple processing elements, or “cores.” The processor210may include a cache that provides temporary storage of data incident to the operation of the processor210.

The multi-zone irrigation flow controller128may further include memory220, which may be volatile memory (such as random access memory (RAM)). The memory220may include one or more memory modules. The memory220may include executable instructions, data referenced by such executable instructions, and/or any other data that may beneficially be made readily accessible to the processor210.

The multi-zone irrigation flow controller128may further include a data store230, which may comprise non-volatile or volatile memory (such as a hard drive, flash memory, and/or the like). The data store230may include one or more data storage elements. The data store230may store executable code (such as an operating system and/or various programs) to be run on the multi-zone irrigation flow controller128, which may also be referred to herein as “multi-zone irrigation flow controller(s),” “irrigation flow controller(s),” and/or “flow controller(s).” The data store230may further store data to be used by such programs. For the systems and methods of the present disclosure, the data store230may store, for example, irrigation water flow data232, water meter flow data234, irrigation water consumption data236and non-irrigation water consumption data238.

The irrigation water flow data232may include data regarding irrigation activities managed, for example, by the multi-zone irrigation flow controller128ofFIG.1, by a hose-attached irrigation flow controller (sometimes referred to as a “hose tap timer”), or by any other type of irrigation flow controller. The irrigation water flow data232may include all of the data needed to determine the amount of water used for irrigation, which may include, but need not be limited to, irrigation start times, irrigation stop times, irrigation durations, flow rates, total irrigation water flow over a period of time, water pressure information, irrigation pipe sizes, sprinkler head information, and/or the like. The irrigation water flow data232may include zone-specific information pertaining to individual irrigation zones and/or global information pertaining to all zones controlled by the multi-zone irrigation flow controller128. The irrigation water flow data232may be specific to the irrigation activities carried out in association with or on a water-monitored property. The water-monitored property may or may not include a structure (not shown), such as a home, a commercial building, an industrial facility, and/or the like. As indicated previously, the irrigation water flow data232may include start and stop times for individual watering zones or a start and stop time for an entire group of watering zones. (Watering zones may also be referred to as watering stations.) The start and stop times may include the specific time, day, and/or date.

The water meter flow data234may include data regarding water flow monitored, for example, by the pulse detecting device124ofFIG.1. The water meter flow data234may also have timestamps indicating the time the pulse was generated or received or an estimate thereof. The pulse detecting device124may be integral, or coupled to, or adjacent to a water meter310(illustrated inFIG.3) that meters water flow to the water-monitored property. The water meter flow data234may include all of the water used on or in connection with a water-monitored property (which may include or be associated with a structure), and may therefore include water for irrigation and non-irrigation purposes. The water meter flow data234may include, but need not be limited to, water consumption start times, stop times, and/or durations, water flow rates, and/or the like.

The irrigation water consumption data236may include data regarding irrigation water used in connection with a water-monitored property. The irrigation water may comprise, for example, water used for irrigating or watering any type of plant (e.g., grass, shrubbery, flowers, crops, gardens or trees), whether positioned inside or outside of a climate-controlled structure. The non-irrigation water consumption data238, in various embodiments, relates to all water consumption aside from irrigation water, such as water used for cooking, bathing, and drinking (for both human and animal consumption). The irrigation water consumption data236may be ascertained by multiplying the total number of pulses received during the period of irrigation according to the irrigation water flow data232by the amount of water associated with each pulse, for example, during a period or periods of irrigation. In some embodiments, the non-irrigation water consumption data238may be obtained by subtracting the total water consumed according to the irrigation water flow data232from the water amount consumed according to the water meter flow data234. The total amount of water consumed may be ascertained by multiplying the total number of pulses received during the pertinent period by the amount of water associated with each pulse. In one embodiment, irrigation water flow data232may be calculated based on an estimated flow rate for an irrigation valve (e.g., 15 gallons per minute) multiplied by the number of minutes that the irrigation valve is open (i.e., the period of time that the zone of the water-monitored property is being irrigated). (Each zone of the water monitored property may receive irrigation water through a single irrigation valve period) The estimated flow rate for an irrigation zone may be calculated, for example, using a flow meter for a particular zone or for the water-monitored property (during a period when other water usage is negligible or absent) or may be estimated as described below in connection with, for example,FIG.8.

In various embodiments, the non-irrigation water consumption data238may be ascertained by multiplying the total number of pulses received during non-irrigation periods by the amount of water represented by each pulse. The irrigation water consumption data236may then be ascertained by subtracting the amount of water associated with the non-irrigation water consumption data238from the total water consumed according to the water meter flow data234during a period of time involving both a period of irrigation and a period of non-irrigation. The foregoing procedure may be based on the presumption that the non-irrigation water consumed during a period of irrigation is sufficiently small to be considered negligible. This presumption is valid in a wide range of use-case scenarios. In various alternative embodiments, the irrigation water flow data232for a particular period may be subtracted from the water meter flow data234to ascertain non-irrigation water consumption data238. Again, the irrigation water flow data232may be calculated using various mechanisms or techniques, as explained previously.

The multi-zone irrigation flow controller128may further include one or more wired transmitter/receivers240, which may facilitate wired communications between the multi-zone irrigation flow controller128and any other device (such as other computing devices120, the servers150, and/or the routers130ofFIG.1). The wired transmitter/receivers240may communicate via any known wired protocol, including, but not limited to, any of the wired protocols described in connection withFIG.1. In some embodiments, the wired transmitter/receivers240may include Ethernet adapters, universal serial bus (USB) adapters, and/or the like.

The multi-zone irrigation flow controller128may further include one or more wireless transmitter/receivers250, which may facilitate wireless communications between the multi-zone irrigation flow controller128and any other device (such as the other computing devices120, the servers150, and/or the routers130ofFIG.1). The wireless transmitter/receivers250may communicate via any known wireless protocol, including, but not limited to, any of the wireless protocols referenced in connection withFIG.1. In some embodiments, the wireless transmitter/receivers250may include Wi-Fi adapters, ZigBee adapters, Z-Wave adapters, Bluetooth adapters, cellular adapters, and/or the like.

The multi-zone irrigation flow controller128may further include one or more user inputs260that receive input from a user such as the fourth user118ofFIG.1. The user inputs260may be integrated into the multi-zone irrigation flow controller128, or may be separate from the multi-zone irrigation flow controller128and connected to it by a wired or wireless connection, which may operate via the wired transmitter/receivers240and/or the wireless transmitter/receivers250. The user inputs260may include elements such as touch screens, buttons, keyboards, mice, track balls, track pads, styli, digitizers, digital cameras, microphones, and/or other user input devices known in the art.

The multi-zone irrigation flow controller128may further include one or more user outputs270that provide output to a user, such as the fourth user118ofFIG.1. The user outputs270may be integrated into the multi-zone irrigation flow controller128, or may be separate from the multi-zone irrigation flow controller128and connected to it by a wired or wireless connection, which may operate via the wired transmitter/receivers240and/or the wireless transmitter/receivers250. The user outputs270may include elements such as a display screen, speaker, vibration device, LED or other lights, and/or other output devices known in the art. In some embodiments, one or more of the user inputs260may be combined with one or more of the user outputs270, as may be the case with a touch screen.

The multi-zone irrigation flow controller128may include various other components not shown or described herein. Those of skill in the art will recognize, with the aid of the present disclosure, that any such components may be used to carry out embodiments of the present disclosure, in addition to or in the alternative to the components shown and described in connection withFIG.2A.

The multi-zone irrigation flow controller128may be capable of carrying out embodiments of the present disclosure in a standalone computing environment (i.e., without relying on communication with or through other devices such as the other computing devices120or the servers150). Other embodiments of the present disclosure may be utilized in different computing environments. One example of a client/server environment is shown and described in connection withFIG.2B.

Referring toFIG.2B, a schematic block diagram illustrates embodiments of a computing device (in the form of the smartphone126ofFIG.1), and a server (in the form of the first server152ofFIG.1), which may cooperate to enable practice of embodiments of the present disclosure with client/server architecture. As shown, the smartphone126may function as a “dumb terminal,” that is, it is made to function in conjunction with the first server152.

Thus, the smartphone126may have and/or use only the hardware needed to interface with a user (such as the first user112ofFIG.1) and communicate with the first server152. Thus, the smartphone126may include one or more user inputs260, one or more user outputs270, one or more wired transmitter/receivers240, and/or one or more wireless transmitter/receivers250. These components may be as described above in connection withFIG.2A.

Computing functions (apart from those incident to receiving input from the user110and delivering output to the user110) may be carried out, in various embodiments, by the first server152. Thus, the processor210, memory220, data store230, wired transmitter/receivers240and wireless transmitter/receivers250may be housed in the first server152.

In various embodiments, the smartphone126may receive input from the user110via the user inputs260. The user input may be delivered to the first server152via the wired transmitter/receivers240and/or wireless transmitter/receivers250. This user input may be further conveyed by any intervening devices, such as the first router132and any other devices in the local area network142that are needed to convey the user input from the first router132to the first server152.

The first server152may conduct any processing steps needed in response to receipt of the user input. Then, the first server152may transmit user output to the user110via the wired transmitter/receivers240, and/or wireless transmitter/receivers250. This user output may be further conveyed by any intervening devices, such as the first router132and any other devices in the local area network142that are needed to convey the user output from the first server152to the first router132. The user output may then be provided to the user110via the user outputs270on the smartphone126.

Referring toFIG.3, a schematic block diagram illustrates one embodiment of a system300for measuring water flow. The system300represents one example of operation of the present disclosure in a standalone computing environment, as exemplified byFIG.2A.

As shown, the pulse detecting device124may be connected to a water meter310. Alternatively, the pulse detecting device124may merely be adjacent to or in close proximity to the water meter310. The water meter310may be a municipal water meter of any known type and may measure the water consumed at a water-monitored property (including irrigation and non-irrigation water consumption). The pulse detecting device124may deliver the water meter flow data234to the multi-zone irrigation flow controller128. The water meter flow data234may be transmitted wirelessly and/or over a wired connection, as described previously.

The multi-zone irrigation flow controller128may generate the irrigation water flow data232and perform the necessary calculations on the irrigation water flow data232and the water meter flow data234to obtain the irrigation water consumption data236. The multi-zone irrigation flow controller128may have a display screen371that displays the irrigation water consumption data236, non-irrigation water consumption data238, and/or other data, such as the irrigation water flow data232and/or the water meter flow data234, for the user.

If desired, the multi-zone irrigation flow controller128may provide categorized and quantified water use data (such as irrigation water consumption data236and non-irrigation water consumption data238) for the user110. This may make it easy for the user110to determine how much water the water-monitored property (for example, his or her home) is consuming for various activities. This information may optionally be displayed graphically, with breakdowns for different water consumption activities, different dates and/or times of day, different water flow rates, and/or the like.

The pulse detecting device124may additionally or alternatively provide the water meter flow data234to a hose-attached irrigation flow controller330, which may be connected to a hose and/or hose bib to control irrigation in a single zone. The hose-attached irrigation flow controller330may generate irrigation water flow data232in a manner similar to that of the multi-zone irrigation flow controller128. If desired, the hose-attached irrigation flow controller330may receive the water meter flow data234and perform the necessary calculations on the irrigation water flow data232and the water meter flow data234to obtain the irrigation water consumption data236and non-irrigation water consumption data238.

The hose-attached irrigation flow controller330and multi-zone irrigation flow controller128illustrated inFIG.3comprise non-limiting examples and serve only to illustrate the type of device or devices that may be used to perform the functions identified herein.

Referring toFIG.4, a schematic block diagram illustrates one embodiment of a system400for measuring water consumption and performing other functions. The system400represents one example of operation in a client/server computing environment, as also exemplified inFIG.2B. As shown, the pulse detecting device124may deliver the water meter flow data234to a router, such as the first router132ofFIG.1. Similarly, the multi-zone irrigation flow controller128may also deliver the irrigation water flow data232to the first router132.

Further, the system400may include one or more additional irrigation flow controllers. For example, the system400may also include a hose-attached irrigation flow controller410, which may be attached to a hose bib and/or hose to control irrigation of one zone via the hose. The hose-attached irrigation flow controller410may also transmit irrigation water flow data232to the first router132. (In various embodiments, the multi-zone irrigation flow controller128and/or hose-attached irrigation flow controller410may each comprise a pulse detecting device124to detect pulses generated by the water meter310.)

From the router132, the irrigation water flow data232and the water meter flow data234may be conveyed to the second server154over the wide area network144, which may be the Internet. The second server154may be housed in any suitable facility. In various embodiments, the second server154may be controlled by the manufacturer of components of the irrigation system used for irrigation of the water-monitored property. Thus, in some embodiments, the second server154may be controlled by the manufacturer of the multi-zone irrigation flow controller128, the hose-attached irrigation flow controller410, the pulse detecting device124, and/or a wireless irrigation system monitor420, which will be described subsequently.

The second server154may then perform the necessary calculations to obtain the irrigation water consumption data236and/or the non-irrigation water consumption data238, which may be transmitted back to the first router132via the wide area network144.

The irrigation water consumption data236may be conveyed to any of a variety of computing devices by the first router132. These computing devices may include, but need not be limited to, a desktop computer122and a smartphone126(examples of which are shown inFIG.1). Additionally or alternatively, these computing devices may include the wireless irrigation system monitor420, which may be a dedicated device and/or software that can be used to monitor and/or control the operation of the irrigation flow controller128and/or other irrigation system components. The wireless irrigation system monitor420may optionally be stored in or near the water-monitored property so that the user110of the monitor420can easily view his or her water consumption (including, for example, the irrigation water flow data232and the irrigation water consumption data236) and make any necessary adjustments to the operation of the irrigation system based on this information.

Adjustments made via the wireless irrigation system monitor420may be transmitted as commands430to the first router132, and thence to the multi-zone irrigation flow controller128and/or the hose-attached irrigation flow controller410, as applicable. The multi-zone irrigation flow controller128and/or the hose-attached irrigation flow controller410may then make the adjustments needed to carry out the commands430.

The various arrows inFIG.4, although shown in solid lines, may represent wired and/or wireless data transmission. According to some embodiments, the first router132may have a wired connection to the wide area network144, and wireless connections to the other components of the system400, aside from the second server154. These wireless connections may include one or more of the wireless protocols mentioned previously. According to some embodiments, the first router132may communicate with other components of the system400via Wi-Fi. According to other embodiments, the first router132may communicate with other components of the system400via ZigBee, Z-wave and/or the like.

Referring toFIG.5, a flowchart illustrates one embodiment of a method500for measuring water consumption. The method500may be practiced with, for example, the system300ofFIG.3, the system400ofFIG.4, or any other system within the scope of the present disclosure. Similarly, the system300or the system400may operate via the method500illustrated inFIG.5, or via other methods within the scope of the present disclosure.

As shown, the method500may start510with step520in which the irrigation water flow data232is received by the processor210, for example, the processor210of the multi-zone irrigation flow controller128ofFIG.2Aand/or the processor210of the first server152ofFIG.1. The irrigation water flow data232may be received from an irrigation flow controller, such as the multi-zone irrigation flow controller128and/or the hose-attached irrigation flow controller410, as described previously.

In step530, the water meter flow data234may be received by the processor210. The water meter flow data234may be received from a pulse detecting device124, as described previously.

In step540, the irrigation water flow data232may be analyzed with reference to the water meter flow data234by the processor210. This analysis may entail, for example, determining the number of pulses generated or received within an irrigation watering period or non-irrigation watering period or subtracting the total water consumed during non-irrigation periods based on the non-irrigation water consumption data238from the total water consumption based on the water meter flow data234.

In step550, the irrigation water consumption data236may be obtained. The irrigation water consumption data236may be obtained as a direct result of the analysis of the step540. Alternatively, the irrigation water consumption data236may be obtained via performance of one or more additional steps based on the results of the analysis performed in the step540. For example, the step540may entail comparisons of start times, stop times, and/or durations with the timing of pulses received. Additional mathematical steps may be needed to convert the resulting analysis results into the irrigation water consumption data236.

In step560, the irrigation water consumption data236may be displayed for the user110. As mentioned previously, this may be done on any of a variety of computing devices, including, but not limited to, the desktop computer122, the smartphone126, the irrigation flow controller128, the hose-attached irrigation flow controller410, and/or the wireless irrigation system monitor420. This step may entail displaying any of a wide variety of information, which may include textual and/or graphical forms, and may include a series of graphs (e.g., pie charts or bar graphs) or numerical values broken down by one or more periods of time or the type of water consumption (e.g., irrigation versus non-irrigation watering).

In addition, non-irrigation water consumption data238may be calculated in step570. The non-irrigation water consumption data238may be calculated, for example, by subtracting irrigation water consumed according to the irrigation water consumption data236for a period from the total water consumed according to the water meter flow data234for the period, or by multiplying the number of pulses received during non-irrigation periods by the amount of water associated with each pulse.

Thereafter, the non-irrigation water consumption data238may be displayed in step580on one or more of various devices described above and the method500may terminate590.

Any methods disclosed herein comprise one or more steps or actions for performing the described method. The method steps and/or actions may be interchanged with one another. In other words, unless a specific order of steps or actions is required for proper operation of the embodiment, the order and/or use of specific steps and/or actions may be modified or various steps may be combined within the scope of the present disclosure.

FIG.6illustrates one embodiment of a system600for measuring water consumption and performing other functions. The system600may include a series of irrigation valves690a-c, a multi-zone irrigation flow controller628, a computer network640, a weather station695, a first server652and an end-user device626.

Each of the irrigation valves690a-cmay include an optional meter691a-c. Each meter691a-cmay monitor the amount of water flowing through each of the valves690a-c. Water meter flow data234may be related to the amount of water flowing through each of the valves690a-cand may be transmitted wirelessly or via a wired connection to the multi-zone irrigation flow controller628. The water meter flow data234may be in the form of an electronic signal that uniquely identifies each valve690a-cto which the water meter flow data234pertains in order to distinguish the water meter flow data234related to each of the valves690a-c. The meters691a-cmay be positioned in alternative locations throughout the system600. For example, a single meter691a-ccould pertain to multiple valves690a-cor all of the valves690a-c. In various embodiments, one or more of the valves690a-ccould comprise the hose-attached irrigation flow controller330,410shown inFIGS.3and4.

The number of irrigation valves690a-cand meters691a-cshown inFIG.6is merely illustrative. Accordingly, the number of irrigation valves690a-cand meters691a-cmay be varied within the scope of the disclosed subject matter or, in certain embodiments, may be entirely omitted from the system600.

The multi-zone irrigation flow controller628may include similar components and functionality included in the multi-zone irrigation flow controller128shown inFIG.2A. Components which are common to both the flow controller628ofFIG.6and the flow controller128ofFIG.2Ainclude the same reference numerals and perform generally the same function and, accordingly, will not be described again. Components shown inFIG.6that are analogous to the components shown inFIG.2Ainclude similar numbering (i.e., the last 2 digits of the number are the same, while the first digit is different).

The multi-zone irrigation flow controller628may further include irrigation water consumption data636comprising zone data637. The zone data637indicates the amount of water consumed by each valve690a-c(i.e., consumed by each zone or station of the system600). The zone data637may be calculated, for example, by determining the end and start time for each valve690a-cand, based on the general water consumption data, identifying the amount of water consumed during those periods, such as by using the pulse detecting device124illustrated inFIG.3. In other embodiments, the valves690a-c(using the meters691a-c) may transmit the data232related to each valve690a-cto the flow controller628in order to calculate the zone data637.

The flow controller628may further comprise historical data641. The historical data641may comprise dates and times associated with irrigation water flow data232, water meter flow data234, irrigation water consumption data636, and non-irrigation water consumption data238. The historical data641may be used for various purposes. For example, the historical data641may be used by the leak detection component674to determine when a leak notification should be generated by comparing historical data641to current data636,637. A significant jump in the current data636,637relative to the historical data641could trigger a leak notification. The leak notification may be transmitted to an end-user device626for viewing by one or more users110(shown inFIG.1) in various ways, such as on the end-user device626, described in more detail subsequently.

Also, using the historical data641related to the zone data637, the leak detection component674may generate a leak notification associated with a particular zone or valve690a-c. A comparison could be made between the historical data641for a particular zone and the current data for that zone within corresponding periods of time (e.g., the same day or set of days one year ago). In various embodiments, a threshold value may be used to determine whether a leak notification for a particular zone or valve690a-cwill be generated. For example, one threshold value could be based on a percentage change in the flow volume, while another threshold value could be based on a change in a certain number of gallons or liters used over a particular period of time. In various embodiments, as another example, a 20% increase in flow over a prior period of time could trigger the generation of a leak notification. The leak detection component674could also take into consideration a change in the time that a valve690a-cremains open in order to determine whether a leak notification should be generated. For example, a high flow rate for a period of time when the valves690a-cshould be closed could also form a basis for generating a leak notification.

In addition, the historical data641may be used to determine when a sprinkler system may have been inadvertently turned off (e.g., the user110turned off the sprinkler system for a yard party and forgot to turn the sprinkler system on again). This determination may be made in conjunction with, for example, temperature and/or precipitation data643,645(e.g., the temperature has exceeded 90° for three consecutive days with no rain in the area of interest and no irrigation cycle has been initiated within that period). When such a determination is made, a corresponding notification may be sent to a device for review by the user110.

The multi-zone irrigation flow controller628could also be coupled to a computer network640, such as the Internet and/or a local area network. The computer network640may enable the flow controller628to receive weather data, including temperature data643and precipitation data645, from the weather station695. The received temperature data643and/or precipitation data645may be stored in the data store630. The flow controller628may include a temperature sensor672and may also be coupled to a precipitation sensor or moisture sensor646. The temperature data643may thus be calculated and received from the temperature sensor672rather than, or in addition to, receiving the temperature data643through the computer network640. Also, the precipitation data645(or related moisture data) may be obtained from the precipitation or moisture sensor646rather than, or in addition to, receiving the precipitation data645through the computer network640. The temperature data643and precipitation data645may be utilized to adjust the time period during which each of the valves690a-cremains in an open state. For example, if the temperature data643indicates that the conditions are generally cooler than an analogous period, the period of time in which each of the valves690a-cis open may be decreased to avoid wasting water using one or more of the commands430(shown inFIG.4). The weather station695could pertain to a particular user110, area, residence, or business or could be utilized by a number of users110. The weather station695may further comprise a data storage facility for storing temperature data643and/or precipitation data645(or other types of weather data, such as wind data or barometric pressure data) for a variety of different physical locations and thus may comprise a server of some kind.

The multi-zone irrigation flow controller628may also receive data (e.g., pulses) from the pulse detecting device124(illustrated inFIG.4) to ascertain, for example, water meter flow data234for use in computing irrigation water consumption data236and/or non-irrigation water consumption data238.

The computer network640may also enable the flow controller628to communicate with a first server652and an end-user device626. With reference to all of the Figures of this application, each of the components illustrated in the flow controllers128,628,728may be embodied or implemented within the first server152,652,752and/or the end-user device626. In various embodiments, the end-user device626is directly coupled through a wired or wireless connection to the first server152,652rather than communicating with the first server152,652through the networks140,640. The end-user device626may comprise, for example, a tablet, laptop, smartphone, notebook or desktop computer, including the associated software. The first server152,652may comprise hardware and software (e.g., an operating system, volatile and non-volatile storage devices, a processor, and/or communication hardware).

In view of the foregoing, systems and methods for measuring water consumption for irrigation and non-irrigation purposes are disclosed within this application. A pulse generating device may interact with a water meter310and generate a pulse based on the amount of water passing through the water meter310. For example, the pulse generating device may generate a pulse for each tenth of a gallon of water passing through the water meter310. The pulse may be transmitted via a wired or wireless connection to one or more pulse detecting devices124.

FIG.7illustrates one embodiment of a system700for measuring water consumption pertinent to a water-monitored property and for performing other functions. The system700may include one or more irrigation valves790a-c, a multi-zone irrigation flow controller728, a computer network740, a weather station795, a first server752and an end-user device726.

Each of the irrigation valves790a-cmay be associated with an optional meter791a-c. Each meter791a-cmay monitor the amount of water flowing through each of the valves790a-c. Water meter flow data234may be related to the amount of water flowing through each of the valves790a-cand may be transmitted wirelessly or via a wired connection to the multi-zone irrigation flow controller728. The water meter flow data234may be in the form of an electronic signal that uniquely identifies each valve790a-cto which the water meter flow data234pertains in order to distinguish the water meter flow data234related to each of the valves790a-c. The meters791a-cmay be positioned in alternative locations throughout the system700. For example, a single meter791a-ccould pertain to multiple valves790a-cor all of the valves790a-c. In various embodiments, one or more of the valves790a-ccould comprise the hose-attached irrigation flow controller330,410shown inFIGS.3and4.

The number of irrigation valves790a-cand meters791a-cshown inFIG.7is merely illustrative. Accordingly, the number of irrigation valves790a-cand meters791a-cmay be varied within the scope of the disclosed subject matter or, in certain embodiments, may be entirely omitted from the system700.

The multi-zone irrigation flow controller728may include similar components and functionality included in the multi-zone irrigation flow controllers128,628shown inFIGS.2A and6. Components which are common to the flow controller728and both of the flow controllers128,628ofFIGS.2A and6include the same reference numerals and perform generally the same function and, accordingly, will not be described again. Components shown inFIG.7that may be analogous to the components shown inFIG.2AandFIG.6include similar numbering (i.e., the last 2 digits of the number are the same, while the first digit is different).

The multi-zone irrigation flow controller728ofFIG.7may further include an identification module781, a calibration module782, a timestamp module783, a data module784, a computational module785, a flow estimation module786, a detection module787, a display screen771, a temperature sensor772, an irrigation valve controller774, and an irrigation valve interface776. The data store730of the multi-zone irrigation flow controller728may also include historical data741, weather data743, watering schedule data731, calibration schedule data732, actual water usage data733, computed flow rate data734, and irrigation water consumption data736comprising zone data737and estimated water usage data739.

The zone data737, or station data, may indicate the amount of water consumed by each valve790a-c(i.e., consumed by each zone or station of the system700). In some embodiments, the valves790a-c(using the meters791a-c) may transmit the data related to each valve790a-cto the flow controller728in order to calculate the zone data737. In other embodiments, the zone data737may be calculated, for example, by determining the end and start time for each valve790a-cand computing an estimated amount of water consumed during those periods by multiplying the total time a valve790a-cis operated by a computed flow rate (as explained below) for that valve790a-c.

The irrigation valve interface776may be configured to place the multi-zone irrigation flow controller728in electronic communication with the one or more irrigation valves790a-c. In various embodiments, each of the one or more irrigation valves790a-cmay be associated with watering a particular zone or station of the water-monitored property. In these and other embodiments, the irrigation valve controller774may be configured to transmit electrical signals to the one or more irrigation valves790a-cvia the irrigation valve interface776to systematically open and close the one or more irrigation valves790a-cin accordance with the watering schedule data731and/or the calibration schedule data732.

In various embodiments, the multi-zone irrigation flow controller728may be configured to estimate irrigation water consumption for each zone of the water-monitored property based on computed flow rates associated with each zone and a total operational time for each valve790a-cin a given zone over a selected time period of interest. In particular, the multi-zone irrigation flow controller728may be configured to perform a calibration process (as explained below) to ascertain computed flow rates for each valve790a-c, which may then be used to find the estimated water usage for each valve790a-cover time.

The identification module781may be configured to identify one or more time periods when water consumption is not likely to occur or is likely minimal within the water-monitored property. In particular, the identification module781may receive a first actual water usage data representative of actual water usage for the water-monitored property over an initial period of time. For example, the first actual water usage data may comprise actual water usage data for the water-monitored property that has occurred over a past time period such as a day, a week, a month, etc. In various embodiments, the identification module781may receive the first actual water usage data directly from the meters791a-cassociated with the valves790a-c, as previously described.

In other embodiments, the identification module781may indirectly receive the first actual water usage data from a water utility entity. The water utility entity may be, for example, a municipality that measures the water consumption of the water-monitored property and charges the owner of the water-monitored property for corresponding water consumption. The water utility entity may utilize a smart meter (not shown) to electronically collect water meter flow data234for the water-monitored property. The smart meter may measure water flow and generate water meter flow data234in discrete time period increments. For example, the smart meter may be configured to measure total water flow over incremental time periods such as every minute, every five minutes, five minutes, every fifteen minutes, every hour, etc. Each incremental time period may be associated with a timestamp that identifies when the water consumption occurred. The smart meter may electronically send incremental water meter flow data234to the water utility entity in a variety of ways, as will be discussed in more detail below, and the water utility entity may also send incremental water meter flow data234to the identification module781.

The identification module781may receive the first actual water usage data from the water utility entity and analyze the first actual water usage data to identify one or more time periods within the first actual water usage data when little or no water consumption occurred for the water-monitored property. Based on the first actual water usage data, the identification module781may determine or identify similar time periods in the future in which water usage is unlikely or is likely minimal within the water-monitored property (i.e., little or no water usage occurs from midnight until 6:00 AM at a particular water-monitored property). Accordingly, the identification module781may create calibration schedule data732for the one or more valves790a-cto conduct calibrations in the future, based on the one or more identified time periods.

In certain situations, such as industrial settings, water may be used continually. Accordingly, the identification module781may not be able to identify a period of time when water usage is unlikely and the identification module may thus identify periods of time when water usage is likely minimal. For example, while water usage may be continual in such a setting, the water usage may be minimized Sunday mornings from 1:00 AM to 5:00 AM each week. The identification module781would thus identify this time period for calibration to be conducted. Also, it should be noted that the identification module781, in various embodiments, may utilize first actual water usage data over an extended period of time in order to identify, for example, daily, weekly or monthly periods of unlikely or minimal water usage. In many cases, periods of minimal or no water usage may be quickly identified by the identification module, such as in most residential use case scenarios.

By way of example only, a water utility entity may collect water meter flow data234for a water-monitored property in fifteen-minute increments. The water utility entity may then send a set of incremental water meter flow data234to the multi-zone irrigation flow controller728for analysis (potentially in response to a request from the multi-zone irrigation flow controller728). This set of incremental water meter flow data234may represent the first actual water usage data that occurred within the water-monitored property over a period of time in the past (e.g., over a week). The identification module781may analyze the first actual water usage data and identify one or more time periods within the first actual water usage data when little or no actual water usage occurred within the water-monitored property (for example, between 1:00 AM and 4:00 AM in the morning). The identification module781may schedule one or more calibration times between 1:00 AM and 4:00 AM in the future when water usage is expected to be low or non-existent. The identification module781may further schedule calibration times for each valve790a-cwithin individual fifteen minute increment periods between the identified 1:00 AM and 4:00 AM time period. Accordingly, the calibration schedule data732may include data that identifies each valve790a-cfor activation during an individual calibration time period, along with a start time and a stop time for each valve790a-c. The identification module781may further schedule calibration time periods for each valve790a-cthat are sufficiently long enough to negate the effects of latency on flow rates due to slow valve “turn-on” and “turn-off” times. For example, the identification module781may schedule each valve790a-cto come on and run for about three minutes or more in order to increase the accuracy of computed flow rates during calibration time periods by negating the effects of slow valve “turn-on” and “turn-off” times on computed flow rates during calibration time periods. Thus, it may be assumed that all of the water flow measured during a calibration time period may be attributable to the individual valve790a-cthat is activated during a given calibration time period.

In various embodiments, the calibration module782may be configured to open and close each of the one or more irrigation valves790a-cin accordance with the calibration schedule data732during a first period of time within the one or more time periods when water consumption is not likely to occur or is likely minimal within the water-monitored property. The timestamp module783may also be configured to identify a calibration valve open time and a calibration valve close time for each of the one or more irrigation valves790a-cin accordance with the calibration schedule data732during the first period of time. Moreover, a data module784may be configured to receive actual water usage data that occurred between the calibration valve open time and the calibration valve close time for each of the one or more irrigation valves790a-cduring the first period of time. The calibration valve open time and the calibration valve close time may differ from an operation valve open time and an operation valve close time because the calibration valve open and close times occur during calibration processes, whereas the operation valve open and close times occur during normal irrigation processes of the multi-zone irrigation flow controller728. A computational module785may be configured to calculate a first computed flow rate for each of the one or more irrigation valves790a-cbased on the calibration valve open time, the calibration valve close time, and the actual water usage data733that occurred between the calibration valve open time and the calibration valve close time during the first period of time. For example, if the time period between the calibration valve open time and the calibration valve close time is three minutes and the actual water usage that occurred during this time period may be 17.8 gallons. Accordingly, the first computed flow rate may be 17.8 gallons divided by 3 minutes, which equals 5.93 gallons per minute.

In this manner, each of the valves790a-cmay be characterized by their individual first computed flow rates, which may be expressed in units of volume per unit of time, such as gallons per minute, liters per minute, or the like. Once the first computed flow rate for each valve790a-cis known, the estimated irrigation water consumption for each valve790a-cmay be continuously computed by the flow estimation module786. The flow estimation module786may be configured to estimate irrigation water consumption and provide estimated water usage data739for at least one particular zone or valve790a-cof the water-monitored property based on the first computed flow rate for each of the one or more irrigation valves790a-cfor the particular zone and a total operational time for each of the one or more irrigation valves790a-cassociated with watering the particular zone over a selected time period of interest. For example, if the total operational time of a valve over a given time period of interest is 23 minutes and the first computed flow rate for the valve is 7.4 gallons per minute, then the water consumption for the valve over the time period of interest is (23 minutes) x (7.4 gallons/minute)=170.2 gallons.

In various embodiments, the first computed flow rate for each valve790a-cmay be periodically updated or checked against a second computed flow rate for each valve790a-cto ensure accuracy of computed flow rates for each valve790a-c. In this embodiment, the calibration module782may be configured to open and close each of the one or more irrigation valves790a-cin accordance with the calibration schedule data732during a second period of time within the one or more time periods when water consumption is not likely to occur or is likely minimal within the water-monitored property. The timestamp module783may also be configured to identify a calibration valve open time and a calibration valve close time for each of the one or more irrigation valves790a-cin accordance with the calibration schedule data732during the second period of time. The data module784may also be configured to receive actual water usage data733that occurred between the calibration valve open time and the calibration valve close time for each of the one or more irrigation valves790a-cduring the second period of time. The computational module785may further be configured to calculate a second computed flow rate for each of the one or more irrigation valves790a-cbased on the calibration valve open time, the calibration valve close time, and the actual water usage data733that occurred between the calibration valve open time and the calibration valve close time during the second period of time, similar to the process discussed above.

Once the second computed flow rate for each valve790a-cis known, the calibration module782may be configured to compare the first computed flow rate to the second computed flow rate for each valve790a-cand average the first computed flow rate with the second computed flow rate if the second computed flow rate is within a first percentage difference of the first computed flow rate. By way of example only, if the second computed flow rate is within 5% of the first computed flow rate, then the first computed flow rate may be averaged with the second computed flow rate. However, if the second computed flow rate is within a second percentage difference of the first computed flow rate (e.g., greater than 5%), then the calibration module782may be configured to conduct further calibrations to try and determine which computed flow rate is more likely to be accurate and/or which computed flow rate was affected by an anomaly that occurred during one of the two calibration sessions. For example, if a sprinkler head broke between the first and second set of calibrations the computed flow rates would likely be quite different.

The resolution of the actual water usage data733may affect the timing at which the calibration module782will initiate the calibration process for each zone. For example, if actual water usage data733may only be obtained in hour increments, the calibration module782will initiate the calibration process for each zone at least one hour apart to ensure that the actual water usage data733gathered pertains only to one particular zone during the calibration process.

The display screen771of the multi-zone flow controller728may be configured to display at least one of the estimated water usage data739in real time, the estimated water usage data739over a selected time period of interest, and/or a comparison between a first estimated water usage data over a first selected time period of interest and a second estimated water usage data over a second selected time period of interest.FIGS.9A-11Billustrate various embodiments of a display screen771a-fthat may be used with any of the multi-zone irrigation flow controllers128,628,728of the present disclosure. The embodiments illustrated in these figures are merely exemplary and are not exhaustive of the potential configurations for such a screen771.FIG.9Ashows the sample display screen771adisplaying a message1011aat the bottom of the display screen771aindicating that the next watering event will occur today and will consume about 800 gallons of water at a cost of about $4.16. The “Water Now” button973may initiate watering immediately, for example, by progressing through all of the watering zones from the lowest numbered zone to the highest numbered zone. The “Budget” button975may allow the user110to adjust the water time of a zone, as shown inFIG.9B.FIG.9Bshows the sample display screen771bdisplaying a message1011bat the bottom of the display screen771bindicating that zone1has been adjusted to increase the watering time to 20 minutes, which will increase water consumption by 58 gallons for a total water usage in zone1of 120 gallons for each iteration of watering for zone1at a cost of $0.62.FIGS.10A and10Bcomprise display screens771c-dillustrating a comparison of water usage in a given month between different years (e.g., July 2016 water usage vs. July 2015 water usage) in the messages1011c-d.FIGS.11A and11Bcomprise display screens771e-fillustrating a comparison of water usage between different years (e.g., water usage for 2016 vs. water usage for 2015) within the messages1011e-f. The user110may toggle through the information displayed on the bottom of the screen by pressing the left and right arrow keys1177a-bon the bottom of the display screen771e-fto view various data, such as the monthly water consumption to date (and for past months), the yearly water consumption to date (and for past years), the cost for water consumption during different time periods, as well as other data described herein.

FIG.12illustrates one embodiment of water usage report1200that may be generated with data produced by embodiments of the present disclosure. The water usage report shown inFIG.12may display data related to various items of interest including, but not limited to: daily water usage1202over a month due to indoor usage1208acompare to outdoor usage1208b(largely irrigation usage), monthly water usage1204, annual water usage1206, percentage increases/decreases in water usage1210a-b, time period comparisons1212a-c, cost in gallons information1214a-c, anomaly detection/notifications1216, and weather data1218including temperature data1220, precipitation data1222, and the like. The water usage report shown inFIG.12may be displayed on any of the computing devices120or end-user devices626,726disclosed herein and/or may be generated by the water utility entity and sent directly to the user110in electronic and/or paper format.

It will be understood that the illustrative display screen shots shown inFIGS.9A-11Band the illustrative water usage report shown inFIG.12are intended to be non-limiting examples and any number or variation of different display screens, display messages, and water usage reports are contemplated herein in the present disclosure.

Continuing once again with reference toFIG.7, as mentioned previously, the historical data741may comprise dates and times associated with irrigation water flow data232, water meter flow data234, irrigation water consumption data736, and non-irrigation water consumption data238. The historical data741may be used for various purposes. For example, as indicated above, the historical data741may be used by the detection module787to determine when an anomaly has occurred, such as a leak, an excessive flow condition, an under-flow condition, a no-flow condition and the like. The anomaly could be due to a broken pipe, either upstream or downstream of a valve. A broken pipe upstream of the valve790a-cmay manifest by high water usage both during and outside of operation of the sprinkler system. A broken pipe or a broken sprinkler head downstream of the valve790a-cmay be manifest by higher water usage during operation of that particular valve790a-c. The detection module787may be configured to detect at least one water consumption anomaly based on a comparison between the estimated water usage data739and the actual water usage data733over a period of interest. The detection module may be further configured to generate a notification based on a specified threshold discrepancy between the estimated water usage data739and the actual water usage data733over the period of interest. (The threshold discrepancy may be specified, for example, by an end-user, a manufacturer or through an algorithm.) The detection module787may determine whether a notification related to a detected anomaly should be generated by comparing historical data741to current data736. A significant jump or decline in the current data736relative to the historical data741could trigger various notifications depending on the nature of the anomaly detected. The appropriate anomaly notification may be transmitted to an end-user device726for viewing by one or more users110in various ways, such as on the end-user device726, or via the display screen771of the multi-zone flow controller728.

Furthermore, the detection module787may generate notifications associated with a particular zone or valve790a-cbased on historical data741related to the zone data737. A comparison could be made between the historical data741for a particular zone and the current data736and may be performed based on a certain period of time or on a certain instance in time. In various embodiments, a threshold value may be used to determine whether a leak notification for a particular zone or valve790a-cwill be generated. For example, one threshold value could be based on a percentage change in the flow volume, while another threshold value could be based on a change in a certain number of gallons or liters over a particular period of time. In various embodiments, as another example, a 20% increase in flow over a prior period of time could trigger the generation of a leak notification. The detection module787could also take into consideration a change in the time that a valve790a-cremains open in order to determine whether a notification should be generated. For example, a high flow rate for a period of time when the valves790a-cshould be closed could also form a basis for generating a notification.

FIGS.13A-13Cillustrate various embodiments of water usage notifications1355a-cthat may be generated by the detection module787.FIG.13Ashows a notification1355aindicating that a leak may have occurred between the water meter310and the valves790a-c.FIG.13Bshows a notification1355bindicating that a leak may exist in a particular water zone andFIG.13Cshows a notification1355cindicating that the user110may have forgotten to turn on the sprinkler system. It will be understood that the foregoing exemplary notifications shown inFIGS.13A-Care non-limiting and any number or variation of different notifications are contemplated within the scope of this disclosure.

Continuing once again withFIG.7, the multi-zone irrigation flow controller728may also be coupled to a computer network740, such as the Internet and/or a local area network. The computer network740may enable the multi-zone irrigation flow controller728to receive weather data743, such as temperature data, precipitation data, wind data, and the like from the weather station795. The received weather data743may be stored in the data store730. The multi-zone irrigation flow controller728may also include a temperature sensor772and the temperature data may also be calculated and received from the temperature sensor772rather than, or in addition to, receiving the temperature data through the computer network740. The weather data743may be utilized to adjust the time period during which each of the valves790a-cremains in an open state. For example, if the temperature data indicates that the conditions are generally cooler than an analogous period, or if precipitation is detected, then the period of time in which each of the valves790a-cis open may be decreased to avoid wasting water using one or more of the commands430(shown inFIG.4). Wind data reflecting higher than normal winds may cause an increase in watering times for each zone as additional evaporation or transpiration may occur or if wind occurs during watering, some water may be carried by the wind off of the water-monitored property before reaching the desired plants. The weather station795could pertain to a particular user110area, residence, or business or could be utilized by a number of users110. The weather station795may further comprise a data storage facility for storing weather data743for a variety of different physical locations and thus may comprise a server of some kind.

The multi-zone irrigation flow controller728may also receive data (e.g., pulses) from the pulse detecting device124(illustrated inFIG.4) to ascertain, for example, water meter flow data234for use in computing irrigation water consumption data236and non-irrigation water consumption data238.

The computer network740may also enable the multi-zone flow controller728to communicate with a first server752and an end-user device726. With reference to all of the Figures of this application, each of the components illustrated in the multi-zone irrigation flow controllers128,628,728may be embodied or implemented within the first server152,652,752and/or the computing device(s)120or end-user device(s)626,726. In various embodiments, the end-user device626,726is directly coupled through a wired or wireless connection to the first server152,652,752rather than communicating with the first server152,652,752through the network140,640,740. The end-user device626,726may comprise, for example, a tablet, laptop, notebook, smartphone or desktop computer, including the associated software. The first server152,652,752may comprise hardware and software (e.g., an operating system, volatile and non-volatile storage devices, a processor, and/or communication hardware).

FIG.8comprises a flowchart illustrating one embodiment of a method800for obtaining irrigation water consumption data736pertinent to a water-monitored property. The method800may be practiced with the system300ofFIG.3, the system400ofFIG.4, the system600ofFIG.6, the system700ofFIG.7, or any other system within the scope of the present disclosure. Similarly, the system300, the system400, the system600, and/or the system700, may operate via the method800, or via other methods within the scope of the present disclosure.

As shown, the method800may start with step810in which the first actual water usage data is received by the processor210(e.g., the processor210of the multi-zone irrigation flow controller128ofFIG.2A, the processor210of the first server152ofFIG.2B, the processor210of the multi-zone irrigation flow controller628ofFIG.6, the processor210of the multi-zone irrigation flow controller728ofFIG.7, and/or the processor of end-user devices626,726). The first actual water usage data may be received from a water utility entity or from one or more water meters310, as previously described.

In step815, one or more time periods in the first actual water usage data may be identified by the processor210when water consumption is not likely to occur or is likely minimal within the water-monitored property, as previously described.

In step820, each of the one or more irrigation valves may be opened and closed in accordance with the calibration schedule data by the processor210. The calibration schedule data may correspond to a first period of time within the one or more time periods when water consumption is not likely to occur or is likely minimal within the water-monitored property.

In step825, the calibration valve open time and the calibration valve close time for each of the one or more irrigation valves may be identified by the processor210in accordance with the calibration schedule data for the first period of time.

In step830, the second actual water usage data that occurred between the calibration valve open time and the calibration valve close time for each of the one or more irrigation valves during the first period of time may be received by the processor210. The second actual water usage data may be received from a water utility entity or from one or more water meters, as previously described.

In step835, the first computed flow rate for each of the one or more irrigation valves may be calculated by the processor210based on the calibration valve open time, the calibration valve close time, and the second actual water usage data that occurred between the calibration valve open time and the calibration valve close time during the first period of time. This calculation may entail, for example, dividing the second actual water usage by the amount of time between the calibration valve open time and the calibration valve close time.

In step840, irrigation water consumption may be estimated by the processor210by providing estimated water usage data for at least one particular zone of the water-monitored property based on the first computed flow rate for each of the one or more irrigation valves associated with watering the particular zone and a total operational time for each of the one or more irrigation valves associated with watering the particular zone over a selected time period of interest.

In step845, at least one water consumption anomaly may be detected by the processor210based on a comparison between the estimated water usage data and a third actual water usage data over the selected time period of interest, as previously described.

In step850, a notification may be generated by the processor210based on a specified threshold discrepancy between the estimated water usage data and the third actual water usage data over the selected time period of interest.

In step855, the estimated water usage data739may be displayed for review by a user110, for example, on one or more of the end-user devices726. The estimated water usage data739may be displayed in various ways. By way of example, the estimated water usage data739is included in each of the sample water usage notifications1355a-cinFIGS.13A-Cas the “Expected Usage.”

In step860, a second computed flow rate may be calculated by the processor210for each of the one or more irrigation valves. The second computed flow rate may be obtained in a similar manner to the first computed flow rate described above in steps820-835. The second computed flow rate may be based on a calibration valve open time, a calibration valve close time, and a fourth actual water usage data that occurred between the calibration valve open time and the calibration valve close time during a second period of time. This calculation may entail, for example, dividing the fourth actual water usage by the amount of time between the calibration valve open time and the calibration valve close time.

In step865, the first computed flow rate may be compared to the second computed flow rate by the processor210and the first computed flow rate may be averaged with the second computed flow rate if the second computed flow rate is within a first percentage difference of the first computed flow rate.

In step870, further calibration may be conducted if the second computed flow rate is outside of a second percentage difference of the first computed flow rate in order to determine which of the first and second flow rates is more accurate.

The method steps and/or actions of the method800above may be interchanged with one another and one or more method steps and/or actions of method800may not be performed by every embodiment disclosed herein.

FIG.14illustrates one embodiment of a system1400for measuring HVAC (“Heating, Ventilation, and Air Conditioning”) energy consumption and performing other functions. The system1400may include a gas valve1490(for natural gas), an AC unit switch1492, an HVAC controller1428, a computer network1440, a weather station1495, a first server1452and an end-user device1426.

The gas valve1490may be associated with a gas meter1491that may monitor the amount of gas flowing through the gas valve1490. The AC unit switch1492may be associated with an electricity meter1493that may monitor the amount of electricity consumed by an AC unit (not shown) associated with the AC unit switch1492. Energy meter flow data1434may include gas meter1491flow data and electricity meter1493flow data, which may be transmitted wirelessly or via a wired connection to the HVAC controller1428. The energy meter flow data1434may be in the form of an electronic signal that uniquely identifies the meter to which the energy meter flow data1434pertains in order to distinguish the gas meter1491flow data from the electricity meter1493flow data.

Although the embodiment shown inFIG.14illustrates a single gas valve1490and a single AC unit switch1492, it will be understood that other embodiments are contemplated that include one or more gas valves1490, gas meters1491, AC unit switches1492, and/or electricity meters1493which may be varied within the scope of the disclosed subject matter or, in certain embodiments, may be entirely omitted from the system1400.

The HVAC controller1428may include similar components and functionality included in the multi-zone irrigation flow controllers128,628,728shown inFIGS.2A,6, and7. Components which are common to the HVAC controller1428and the multi-zone irrigation flow controllers128,628,728may include the same reference numerals and perform generally the same function and, accordingly, will not be described again. Components shown inFIG.14that may be analogous to the components shown inFIGS.2A,6, and7may include similar numbering (i.e., the last 2 digits of the number may be the same, while the first two digits may be different).

The HVAC controller1428ofFIG.14may include an identification module1481, a calibration module1482, a timestamp module1483, a data module1484, a computational module1485, a flow estimation module1486, a detection module1487, a display screen1471, a temperature sensor1472, a valve and switch controller1474, and a gas valve/AC unit switch interface1476. The data store1430of the HVAC controller1428may also include energy flow data1435, historical data1441, weather data1443, thermostat schedule data1431, calibration schedule data1432, actual energy usage data1433, computed flow rate data1442, non-HVAC energy consumption data1438, and HVAC energy consumption data1436comprising energy type data1437and estimated energy usage data1439.

The energy flow data1435may comprise gas valve1490and AC unit switch1492open and close times. The thermostat schedule data1431may include desired temperature settings for different times of the day and/or different days of the week for a given energy-monitored property, such as a house or building (not shown). The energy type data1437may include data related to the type of energy consumed (e.g., gas, electricity, and the like). The estimated energy usage data1439may indicate the amount of energy consumed by each gas valve1490and/or each AC unit switch1492. In some embodiments, the meters1491,1493may directly transmit the energy meter flow data1434, the energy type data1437, and/or the estimated energy usage data1439for the gas valve1490and/or the AC unit switch1492to the HVAC controller1428. In other embodiments, the energy meter flow data1434, the energy type data1437, and/or the estimated energy usage data1439may be sent to the HVAC controller1428by one or more energy utility entities (not shown). In other embodiments, the estimated energy usage data1439may be calculated, for example, by determining the open and close times for the gas valve1490and the AC unit switch1492and computing an estimated amount of energy consumed during those periods by multiplying the total time the gas valve1490and the AC unit switch1492are open (“on” or “operated”) by a computed flow rate, as will be described in more detail below.

The gas valve/AC unit switch interface1476may be configured to place the HVAC controller1428in electronic communication with the gas valve1490and the AC unit switch1492. In various embodiments, the gas valve1490and the AC unit switch1492may be associated with heating and cooling the energy-monitored property, respectively. In these and other embodiments, the valve and switch controller1474may be configured to transmit electrical signals to the gas valve1490and the AC unit switch1492via the gas valve/AC unit switch interface1476to systematically open and close the gas valve1490and the AC unit switch1492in accordance with the thermostat schedule data1431and/or the calibration schedule data1432.

In various embodiments, the HVAC controller1428may be configured to estimate energy consumption for the energy-monitored property based on computed flow rates associated with each energy type and a total operational time for the gas valve1490and/or the AC unit switch1492over a selected time period of interest. In particular, the HVAC controller1428may be configured to perform a calibration process to ascertain computed flow rates for the gas valve1490and the AC unit switch1492, which may then be used to find the estimated energy usage for the gas valve1490and the AC unit switch1492individually, or in combination.

The identification module1481may be configured to identify one or more time periods when energy consumption (e.g., gas, electricity, or both) is not likely to occur or is likely minimal within the energy-monitored property. In particular, the identification module1481may receive a first actual energy usage data representative of actual energy usage for the energy-monitored property over an initial period of time. For example, the first actual energy usage data may comprise actual energy usage data for the energy-monitored property that has occurred over a past time period such as a day, a week, a month, etc. In various embodiments, the identification module1481may receive the first actual energy usage data directly from the meters1491,1493, as previously described.

In other embodiments, the identification module1481may indirectly receive the first actual energy usage data from one or more energy utility entities. The one or more energy utility entities may measure energy consumption of the energy-monitored property and/or charge the owner of the energy-monitored property for energy consumption.

FIG.16illustrates a schematic block diagram of one embodiment of a system1600for communicating data related to an HVAC system. The system1600may include an HVAC controller1628, a router1630, one or more computing devices such as a laptop1622and a smartphone1626, a computer network1640, a cell phone tower1660, a server1652, an AC unit1694, an electricity meter1693associated with the AC unit1694, a heating unit1696, a gas meter1691associated with the heating unit1696, and a data collection vehicle1620. The gas meter1691and the electricity meter1693may be smart meters with communication capabilities.

The HVAC controller1628may send electronic commands to the AC unit1694and the heating unit1696and the HVAC controller1628may also be remotely programmed and/or controlled via the laptop1622or the smartphone1626, as previously discussed in other embodiments.

The one or more energy utility entities may utilize the smart meters1691,1693to electronically collect energy meter flow data1434for the energy-monitored property. The smart meters1691,1693may measure energy flow, such as natural gas flow and/or electricity flow and may generate energy meter flow data1434in discrete time period increments. For example, the smart meters1691,1693may be configured to measure total energy flow over incremental time periods, such as every five minutes, every fifteen minutes, every hour, etc. Each incremental time period may be associated with a timestamp that identifies when the energy consumption occurred. The smart meters1691,1693may electronically send the energy meter flow data1434to the one or more energy utility entities in a variety of ways. For example, the smart meters1691,1693may wirelessly transmit energy meter flow data1434to the data collection vehicle1620when the data collection vehicle1620comes into close proximity with the smart meters1691,1693. Alternatively, or in addition thereto, the smart meters1691,1693may wirelessly (or via wired connections) transmit energy meter flow data1434to the router1630, the cell phone tower1660, a wireless transceiver in a nearby telephone pole (not shown), the HVAC controller1628, and/or the one or more computing devices, such as the laptop1622and the smartphone1626. The one or more energy utility entities may also send energy meter flow data1434to the HVAC controller1628via the computer network1640and/or the router1630from the server1652, which may be the server of a municipality, or other gas or electricity monitoring entity.

Continuing, once again, withFIG.14, the identification module1481may receive the first actual energy usage data from the one or more energy utility entities and analyze the first actual energy usage data to identify one or more time periods within the first actual energy usage data when little or no energy consumption occurred within the energy-monitored property. Based on the one or more previously identified time periods, the identification module1481may also be configured to identify analogous time periods in which energy is not likely to be used. Accordingly, the identification module1481may create calibration schedule data1432for the gas valve1490and the AC unit switch1492to conduct calibration processes in the future, based on the one or more identified time periods.

By way of example only, an energy utility entity may collect energy meter flow data1434for an energy-monitored property in incremental time periods of every fifteen minutes. The energy utility entity may then send a set of incremental energy meter flow data1434to the HVAC controller1428for analysis. This set of incremental energy meter flow data1434may represent the first actual energy usage data that occurred within the energy-monitored property over a period of time in the past (e.g., over a time period of a week, as one example). The identification module1481may analyze the first actual energy usage data and identify one or more time periods within the first actual energy usage data when little or no actual energy usage occurred within the energy-monitored property (for example, between 1:00 AM and 4:00 AM in the morning). The identification module1481may then schedule one or more calibration times between 1:00 AM and 4:00 AM in the future when energy usage is expected to be low or non-existent. The identification module1481may further schedule calibration times for the gas valve1490and/or the AC unit switch1492within individual fifteen minute increment periods between the identified 1:00 AM and 4:00 AM time period. Accordingly, the calibration schedule data1432may include data that identifies the gas valve1490and the AC unit switch1492for activation during an individual calibration period time, along with a start time and a stop time for the gas valve1490and the AC unit switch1492. The identification module1481may further schedule calibration time periods for the gas valve1490and/or the AC unit switch1492that are sufficiently long enough to negate any effects due to slow valve “turn-on” and “turn-off” times. For example, the identification module1481may schedule the gas valve1490to come on and run the heating unit1696for about three minutes (or more) to increase the accuracy of the computed flow rate during the calibration time period. Thus, it may be assumed that all of the energy flow measured during a calibration time period may be attributable to the gas valve1490and/or the AC unit switch1492. As a further example, in various embodiments, calibration for a furnace may occur in the early morning hours during the summertime when the furnace is not otherwise likely to be used (and other gas-power devices are also unlikely to be used) and, alternatively, calibration of an air conditioner may take place in the early morning hours during the winter time when the air conditioning unit is unlikely to be used.

In various embodiments, the calibration module1482may be configured to open and close the gas valve1490and/or the AC unit switch1492in accordance with the calibration schedule data1432during a first period of time when energy consumption is not likely to occur or is likely minimal within the energy-monitored property. The timestamp module1483may also be configured to identify a calibration open time and a calibration close time for the gas valve1490and/or the AC unit switch1492in accordance with the calibration schedule data1432during the first period of time. Moreover, a data module1484may be configured to receive actual energy usage data1433that occurred between the calibration open time and the calibration close time for the gas valve1490and/or the AC unit switch1492during the first period of time. The calibration open time and the calibration close time may differ from an operation open time and an operation close time because the calibration open and close times occur during calibration processes, whereas the operation open and close times occur during normal heating and cooling processes. A computational module1485may be configured to calculate a first computed flow rate for the gas valve1490and/or the AC unit switch1492based on the calibration open time, the calibration close time, and the actual energy usage data1433that occurred between the calibration open time and the calibration close time during the first period of time. For example, if the time period between the calibration open time and the calibration close time is three minutes and the actual energy usage that occurred during this time period is 0.3 Ccf, then the first computed flow rate for the gas valve1490may be (0.3 Ccf)÷(3 minutes)=0.1 Ccf per minute. A similar computed flow rate may be calculated for the AC unit switch1492.

In this manner, the gas valve1490and the AC unit switch1492may be characterized by their individual first computed flow rates, which may be expressed in units of volume per time and/or current per time. Once the first computed flow rate for the gas valve1490and the AC unit switch1492are known, the estimated energy consumption for the gas valve1490and the AC unit switch1492may be continuously computed by the flow estimation module1486. The flow estimation module1486may be configured to estimate energy consumption and provide an estimated energy usage data1439for the energy-monitored property based on the first computed flow rate for the gas valve1490and the AC unit switch1492and a total operational time for the gas valve1490and the AC unit switch1492over a selected time period of interest. For example, if the total operational time of the gas valve1490over a given time period of interest is 3.7 hours and the first computed flow rate for the valve is 0.1 Cef per minute, then the energy consumption for the gas valve1490over the time period of interest is (3.7 hours=222 minutes) x (0.1 Ccf/minute)=22.2 Ccf. Likewise, the energy consumption for the AC unit switch1492may be computed in a similar manner.

In various embodiments, the first computed flow rate for the gas valve1490and the AC unit switch1492may be periodically updated or checked against a second computed flow rate for the gas valve1490and the AC unit switch1492to ensure accuracy of the first computed flow rates. In this embodiment, the calibration module1482may be configured to open and close the gas valve1490and the AC unit switch1492in accordance with the calibration schedule data1432during a second period of time when energy consumption is not likely to occur or is likely minimal within the energy-monitored property. The timestamp module1483may also be configured to identify a calibration open time and a calibration close time for the gas valve1490and the AC unit switch1492in accordance with the calibration schedule data1432during the second period of time. The data module1484may also be configured to receive actual energy usage data1433that occurred between the calibration open time and the calibration close time for the gas valve1490and the AC unit switch1492during the second period of time. The computational module1485may further be configured to calculate a second computed flow rate for the gas valve1490and the AC unit switch1492based on the calibration open time, the calibration close time, and the actual energy usage data1433that occurred between the calibration open time and the calibration close time during the second period of time.

Once the second computed flow rate for the gas valve1490and the AC unit switch1492are known, the calibration module1482may be configured to compare the first computed flow rate to the second computed flow rate for the gas valve1490and the AC unit switch1492and average the first computed flow rate with the second computed flow rate if the second computed flow rate is within a first percentage difference of the first computed flow rate. By way of example only, if the second computed flow rate is within 5% of the first computed flow rate, then the first computed flow rate may be averaged with the second computed flow rate. However, if the second computed flow rate is within a second percentage difference of the first computed flow rate (e.g., greater than 5%), then the calibration module1482may be configured to conduct further calibrations to try and determine which computed flow rate is accurate and/or which computed flow rate was affected by an anomaly that occurred during one of the two calibration sessions.

The display screen1471of the HVAC controller1428may be configured to display at least one of the estimated energy usage data1439in real time, the estimated energy usage data1439over a selected time period of interest, and/or a comparison between a first estimated energy usage data over a first selected time period of interest and a second estimated energy usage data over a second selected time period of interest.FIGS.17A-18Billustrate various embodiments of display screens1471a-dthat may be used with the HVAC controller1428of the present disclosure.FIGS.17A and17Bshow an embodiment of a display screen1471a-bdisplaying a message at the bottom of the display screen1471a-billustrating a comparison of electricity energy usage for a given month in different years (e.g., July 2015 electricity energy usage vs. July 2016 electricity energy usage).FIGS.18A and18Bshow an embodiment of a display screen1471c-dillustrating a comparison of electricity energy usage between different years (e.g., electricity energy usage for 2015 vs. electricity energy usage for 2016). The user110may toggle through the information displayed on the bottom of the screen by pressing the left and right arrow keys1877a-bon the bottom of the display to view various data such as the monthly energy consumption to date (and for past months), the yearly energy consumption to date (and for past years), the cost for energy consumption during different time periods, as well as other data described herein.

It will be understood that the foregoing sample display screen shots shown inFIGS.17A-18Bare merely examples and any number or variation of different display screen formats and/or display messages are contemplated herein.

Continuing, once again, withFIG.14, the HVAC controller1428may further comprise historical data1441. The historical data1441may comprise dates and times associated with energy flow data1435, energy meter flow data1434, HVAC energy consumption data1436, and non-HVAC energy consumption data1438. The historical data1441may be used for various purposes. For example, the historical data1441may be used by the detection module1487to determine when an anomaly has occurred, such as an energy leak, an excessive energy flow condition, an energy under-flow condition, an energy no-flow condition, and the like. For example, the anomaly could be due to a broken pipe, either upstream or downstream of the gas valve1490. A broken pipe upstream of the gas valve1490may manifest by high gas usage both during and outside of operation of the gas valve1490. A broken gas pipe downstream of the gas valve1490may be manifest by higher gas usage during operation of the gas valve1490. Furthermore, an anomaly may involve lower gas usage. For example, if a homeowner turns off the heater for some reason and forgets to turn it back on this may create a low gas usage anomaly. Likewise, similar anomalies for electricity consumption are contemplated herein. The detection module1487may be configured to detect at least one energy consumption anomaly based on a comparison between the estimated energy usage data1439and the actual energy usage data1433over a selected time period of interest. The detection module1487may be further configured to generate a notification based on a specified threshold discrepancy between the estimated energy usage data1439and the actual energy usage data1433over the selected time period of interest. The detection module1487may determine whether a notification related to a detected anomaly should be generated by comparing historical data1441to current data. A significant jump or decline in the current data relative to the historical data1441could trigger various notifications depending on the nature of the anomaly detected. The appropriate anomaly notification may be transmitted to an end-user device1426for viewing by one or more users110in various ways, such as via the end-user device1426, or the display screen1471of the HVAC controller1428.

FIGS.19A-20Cillustrate various embodiments of electricity and gas usage notifications1955a-c,2055a-cthat may be generated by the detection module1487.FIG.19Ashows a notification1955aindicating that an electrical short (an electrical leak) may have occurred in the wiring system associated with the air conditioning unit.FIG.19Bshows a notification1955bindicating that high electricity usage was detected during operation of the air conditioning unit only, indicating that the air conditioning unit may require servicing.FIG.19Cshows a notification1955cindicating that a door or a window may have been left open.FIG.20Ashows a notification2055aindicating that a gas leak may have occurred in the gas line or lines.FIG.20Bshows a notification2055bindicating that high gas usage was detected during operation of the heating unit, indicating that the heating unit may require servicing.FIG.20Cshows a notification2055cthat indicates that a door or a window may have been left open. It will be understood that the foregoing example notifications1955a-c,2055a-cshown inFIGS.19A-20Care non-limiting and any number or variation of different notifications are contemplated herein.

Continuing withFIG.14, the HVAC controller1428may also be coupled to a computer network1440, such as the Internet and/or a local area network. The computer network1440may enable the HVAC controller1428to receive weather data1443, such as temperature data, precipitation data, wind data, and the like from the weather station1495. The received weather data1443may be stored in the data store1430. The HVAC controller1428may also include a temperature sensor1472and the temperature data may also be calculated and received from the temperature sensor1472rather than, or in addition to, receiving the temperature data through the computer network1440. The temperature sensor1472, in one embodiment, may comprise an indoor and outdoor sensor with the indoor sensor sensing a temperature within the monitored structure (or within a portion of the monitored structure) and the outdoor sensor sensing the temperature outside the monitored structure. The weather data1443may be utilized to adjust the time period during which the gas valve1490and/or the AC unit switch1492may remain in an open or “on” state. For example, if the temperature data indicates that the conditions are generally cooler than an analogous period, indicating that an anomaly in energy consumption may be due to a temperature difference. The weather station1495could pertain to a particular user110, area, residence, or business or could be utilized by a number of users110. The weather station1495may further comprise a data storage facility for storing weather data1443for a variety of different physical locations and thus may comprise a server of some kind. The weather, such as humidity, may affect the performance and efficiency of a heating unit or an air conditioning unit and how different temperatures are perceived by individuals (e.g., causing the individuals to adjust the HVAC controller1428to a different temperature even though the outside temperatures may not have changed).

In various embodiments, the HVAC controller1428may also receive data (e.g., pulses) from the pulse detecting device124(illustrated inFIG.4) to ascertain, for example, energy meter flow data1434for use in computing HVAC energy consumption data1436and non-HVAC energy consumption data1438.

The computer network1440may also enable the HVAC controller1428to communicate with the first server1452and/or the end-user device1426. Each of the components illustrated in the HVAC controller1428may be embodied or implemented within the first server1452, the computing devices120, and/or the end-user device1426. In various embodiments, the end-user device1426is directly coupled through a wired or wireless connection to the first server1452rather than communicating with the first server1452through the computer network1440. The end-user device1426may comprise, for example, a tablet, laptop, notebook, smartphone, or desktop computer, including associated software. The first server1452may comprise hardware and software (e.g., an operating system, volatile and non-volatile storage devices, a processor, and/or communication hardware).

FIG.15illustrates a flowchart of one embodiment of a method1500for obtaining energy consumption data pertinent to an energy-monitored property. The method1500may be practiced with the system1400ofFIG.14. Similarly, the system1400may operate via the method1500, or via other methods within the scope of the present disclosure.

As shown, the method1500may start with step1510in which the first actual energy usage data is received by the processor210, for example, the processor210of the HVAC controller1428ofFIG.14, the processor210of the first server1452ofFIG.2B, and/or the processor of the end-user device1426or other computing devices described herein. The first actual energy usage data may be received from one or more energy utility entities or from one or more meters, as previously described.

In step1515, one or more time periods in the first actual energy usage data may be identified by the processor210when energy consumption is not likely to occur or is likely minimal within the energy-monitored property.

In step1520, the gas valve1490and/or the AC unit switch1492may be opened and closed in accordance with the calibration schedule data1432by the processor210. The calibration schedule data1432may correspond to a first period of time when energy consumption is not likely to occur or is likely minimal within the energy-monitored property.

In step1525, the calibration open time and the calibration close time for the gas valve1490and the AC unit switch1492may be identified by the processor210in accordance with the calibration schedule data1432for the first period of time.

In step1530, the second actual energy usage data that occurred between the calibration open time and the calibration close time for the gas valve1490and the AC unit switch1492during the first period of time may be received by the processor210. The second actual energy usage data may be received from one or more energy utility entities or from one or more meters, as previously described.

In step1535, the first computed flow rate for the gas valve1490and the AC unit switch1492may be calculated by the processor210based on the calibration open time, the calibration close time, and the second actual energy usage data that occurred between the calibration open time and the calibration close time during the first period of time. This calculation may entail, for example, dividing the second actual energy usage by the amount of time between the calibration open time and the calibration close time for the gas valve1490and the AC unit switch1492.

In step1540, energy consumption may be estimated by the processor210by providing estimated energy usage data1439for the energy-monitored property based on the first computed flow rate for the gas valve1490and the AC unit switch1492and a total operational time for the gas valve1490and the AC unit switch1492over a selected time period of interest.

In step1545, at least one energy consumption anomaly may be detected by the processor210based on a comparison between the estimated energy usage data1439and a third actual energy usage data over the selected time period of interest, as previously described.

In step1550, a notification may be generated by the processor210based on a specified threshold discrepancy between the estimated energy usage data1439and a third actual energy usage data over the selected time period of interest.

In step1555, the estimated energy usage data1439may be displayed for review by a user110on, for example, one or more of various end-user devices1426. The estimated energy usage data1439may be displayed in various ways. By way of example, the estimated energy usage data1439is included in each of the sample energy usage notifications1955a-cinFIGS.19A-Cas the “Expected Usage.”

In step1560, a second computed flow rate may be calculated by the processor210for the gas valve1490and the AC unit switch1492. The second computed flow rate may be obtained in a similar manner to the first computed flow rate described above in steps1520-1535. The second computed flow rate may be based on a calibration open time, a calibration close time, and a fourth actual energy usage data that occurred between the calibration open time and the calibration close time during a second period of time. This calculation may entail, for example, dividing the fourth actual energy usage by the amount of time between the calibration open time and the calibration close time.

In step1565, the first computed flow rate may be compared to the second computed flow rate by the processor210and the first computed flow rate may be averaged with the second computed flow rate, if the second computed flow rate is within a first percentage difference of the first computed flow rate.

In step1570, further calibration may be conducted if the second computed flow rate is within a second percentage difference of the first computed flow rate in order to determine which of the first and second flow rates are accurate, and/or which of the first and second flow rates was affected by an anomaly.

The method steps and/or actions of the method1500above may be interchanged with one another and one or more method steps and/or actions of method1500may not be performed by every embodiment disclosed herein.

It is understood that any specific order or hierarchy of steps in any disclosed process is merely illustrative. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

FIG.21illustrates one embodiment of gas usage report2100that may be generated with data produced by embodiments of the present disclosure. The gas usage report2100shown inFIG.21may display data related to various items of interest including, but not limited to: monthly gas usage2104, annual gas usage2106, a comparison2108of annual usage of the identified gas-monitored property relative to the average of other gas-monitors properties in the same area, usage detail2108a-bof October 2014 compared to October 2015 including temperature data2120, anomaly detection/notifications2116and the like. The gas usage report2100shown inFIG.21may be displayed on any of the computing devices120or end-user devices1426disclosed herein and/or may be generated by the gas utility entity and sent directly to the user110in electronic and/or paper format. The report2100shown inFIG.21constitutes only one example of the type of reports that can be utilized generating the systems, mechanisms, and methods disclosed herein. A similar report could be generated for usage of electricity.

Systems and methods disclosed herein could be used in various locations, such as in conjunction with one or more businesses, residences, parks or broader geographical areas.

In addition, it should be noted that determining the flow rate or flow volume with a meter may be implemented in various ways. For example, a turbine at least partially disposed in a fluid or gas may be used to determine flow rate or flow volume of the fluid based on the number of rotations of the turbine. Alternatively, a diaphragm for sensing pressure may also be utilized. From the sensed pressure, a flow rate and/or flow volume may be derived based on the density of the fluid. Thus, a generated pulse may be embodied in various ways and may reference pressure, volume, flow rate or other types of data.

Reference throughout this specification to “an embodiment.” “one embodiment” or “various embodiments” has reference to a particular feature, structure, mechanism or characteristic that may be included or used in connection with other features, structures mechanisms or characteristics disclosed herein and known to one of skill in the art at the time this application was filed. Thus, these phrases, or variations thereof, as recited throughout this specification are not necessarily all referring to the same embodiment.

Similarly, it will be appreciated that in the above description of embodiments, various features are sometimes grouped together in a single embodiment, figure, or description for the purpose of streamlining the present disclosure. This method of disclosure, however, is not to be interpreted as reflecting an intention that any claim in this or any application claiming priority to this application require more features than those expressly recited in that claim. Rather, as the following claims reflect, inventive aspects lie in a combination of fewer than all features of any single foregoing disclosed embodiment. Thus, the claims following this Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment. This disclosure includes all permutations of the independent claims with their dependent claims.

Recitation in the claims of the term “first” with respect to a feature or element does not necessarily imply the existence of a second or additional such feature or element. Only elements recited in means-plus-function format are intended to be construed in accordance with 35 U.S.C. § 112 Para. 6. It will be apparent to those having skill in the art that changes may be made to the details of the above-described embodiments without departing from the underlying principles of the present disclosure.

The description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the aspects shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed. For example, data collection vehicle1620ofFIG.16may also be used in connection with the methods described inFIGS.7and8to collect actual water usage data. As an additional example, the ofFIG.14and the method ofFIG.15may also be used in connection with other gas or electrically powered appliances besides a heating unit or air conditioning unit, such as a gas-powered water heater or an electrical water heater. A gas-powered water heater may have anomalies in operation when a leak develops in the water holding tank of the heater (which may require increased operation of the water heater to maintain the water disposed therein at the set temperature). These anomalies may be detected and corresponding notifications may be provided using the methods and systems identified above.

It should also be noted that the first, second, third and fourth periods of time referenced herein, in various embodiments, may be mutually exclusive. In other words, in at least some embodiments, there is no temporal overlap between these periods of time.

It should also be noted, that in various embodiments, once the computed flow rate data734is established for irrigation zone(s) of a particular system, there is no requirement of a network connection at the water meter310, hose-attached irrigation flow controller330,410or multi- or single-zone irrigation flow controller128,628,728in order to calculate estimated water usage data739. Instead, the computed flow rate data734may be utilized to calculate estimated water usage data739(e.g., gallons-per-minute for a particular zone multiplied by the number of minutes that the valve690a-c.790a-cassociated with that zone is open for each zone). One benefit of a permanent connection to a network640,740(or a readily available connection to a network640,740) is more rapid anomaly detection and faster generation of enhanced water reports (i.e., water usage reports based on ongoing actual water usage data733). Without such a network connection, anomaly detection and enhanced reports will not be generated until the pertinent actual water usage data733is received or input into the flow controller330,410,128,628,728, either by manually inputting the data at the flow controller330,410,128,628,728(e.g., using a numeric keypad or keyboard at the controller330,410,128,628,728), inputting the data through a temporary or a sporadically available network connection (e.g., through a Wi-Fi connection made available by a cellular telephone), or through a portable storage device (e.g., a portable USB drive) coupled to the flow controller330,410,128,628,728. It should also be noted that the computed flow rate data734may be calculated based on a user reading of before and after actual water usage data733from a water meter310in connection with a calibration cycle where actual water usage data733is displayed on the water meter310or is otherwise accessible to the user110. Thus, in connection with calibration, the displayed values of the before and after actual water usage data733may be input into the irrigation flow controller330,410,128,628,728by the user110with the controller330,410,128,628,728realizing the appropriate computations of the computed flow rate734based on the time that the pertinent valve(s)690a-c,790a-cwere open and closed for each zone. The foregoing principles also apply to the system1400,1600and methods1500outlined in connection withFIGS.14-21(i.e., estimated energy usage data1439based on the computed flow rate data1442may be calculated without a network connection, as indicated above).

The use of a hose-attached irrigation flow controller330,410presents unusual challenges because the coupled hose-end products are not always static (i.e., the sprinklers attached to the hose-end product may be quickly and easily modified by a user110, if desired). (It should also be noted that calibration should be repeated again when sprinkler heads coupled to a multi- or single-zone irrigation flow controller128,628,728are modified, added, or removed within one or more zones of a system.) Accordingly, the computed flow rate data734may change based on the coupled hose-end products. However, in situations where the hose-end products remain static, the computed flow rate data734would also remain constant in the absence of an anomaly, such as a broken sprinkler or a leak in the hose intermediate the hose-attached irrigation flow controller330,410and the attached hose-end products.