KITCHEN ENVIRONMENT WITH ENHANCED USER EXPERIENCE AND ACCESSORIES

TECHNICAL FIELD

The present disclosure relates generally to several interrelated aspects of a kitchen environment, including sinks, stovetops, refrigerators, dishwashers, microwave, and the like.

BACKGROUND

A kitchen is a room or area within a building designated for the preparation of meals (e.g., food) and other associated activities. As just a few illustrative examples, a kitchen may include: a refrigerator and/or freezer for storage of perishable food ingredients; cabinets for storage of non-perishable food ingredients and/or dishware and glassware; a stovetop, oven, and/or microwave oven for heating foodstuffs for cooking and baking; and a sink for washing and cleaning of food items and dishware.

SUMMARY

The present disclosure is directed to various features that may provide improved functionality for kitchens and associated kitchen systems, particularly with regard to a user experience (“UX”) within a “smart” (e.g., technologically enhanced) kitchen environment. In general, various implementations of the present disclosure includes a sink system including one or more sink basins integrated into a cabinet or housing, and a faucet coupled to the sink. The sink system can include a produce washing station in a second basin. The produce washing station can include water delivery systems including an ozonated mist spray, a waterfall spray, and/or a jet propulsion spray, and can also include a produce basket nested within the basin, and a berry basket nested at varying heights within the produce basket. A sliding basin lid can also be incorporated to seal the basin, and optionally to provide a workstation for cleaning, cutting, or drying.

The sink system according to various implementations can include smart features including sensors and controls systems, which allow various smart features including, but not limited to, audiovisual features for controlling various features of the sink systems, digital tutorials or instruction, a command-center for controlling various features of the total kitchen, customized user audiovisual settings and welcoming features, water usage features, water selection based on biometric data of a user, and the like.

The sink system according to various implementations can also include a beverage or hydration station feature in which water can be customized for a user or for a desired end use of the water by the user. For example, one or more of flavors, vitamins, minerals, carbonation, filtration, instant hot, chilled, coffee, ice, and cocktails can be added to the water and dispensed by the sink system. In an example, if a water type from a specific geographic location is desired for an end use, for example, water from Brooklyn, New York, to make pizza dough, the sink system can customize the additives, such as minerals, to reproduce similar water.

Other optional features of the sink systems are described in detail below. Further, one or more implementations described herein can be combined with one or more implementations described in U.S. Pat. App. Pub. No. 2022/0364343, entitled “Sink System and Components”, incorporated herein by reference in its entirety.

BRIEF DESCRIPTION OF THE DRAWINGS

Subject matter hereof may be more thoroughly understood in consideration of the following detailed description of various examples in connection with the accompanying figures, in which:

FIG. 1-1 is a perspective view of an example smart-kitchen environment, including a first example sink system.

FIG. 1-2 is a top view of the sink system of FIG. 1-1.

FIG. 2 is a front view of an example sink system of the smart-kitchen environment of FIG. 1-1.

FIG. 3-1 is a perspective view of an example sink system, including an example ozonated-mist-delivery system.

FIG. 3-2 is a block diagram illustrating some example components of the mist-delivery system of FIG. 3-1.

FIG. 3-3 is a close-up view of a portion of an example sprayhead of the mist-delivery system of FIG. 3-1.

FIG. 3-4 is a block diagram of an example ozone generator as mounted on a faucet of the sink of FIG. 3-1.

FIG. 4-1 is a perspective view of an example sink system of the smart-kitchen environment of FIG. 1-1, including an example on-demand liquid-conditioning system.

FIG. 4-2 is a block diagram of an example of the liquid-conditioning system of FIG. 4-1.

FIG. 5-1 is a perspective view of an example sink system that includes an example immersive-UX faucet system.

FIG. 5-2 is a block diagram of an example user module of the sink system of FIG. 5-1.

FIG. 6 is a perspective view of an example sink system that includes a sleeve system.

FIG. 7-1 is a perspective view of an example sink system that includes an enhanced-accessibility system.

FIG. 7-2 is a block diagram of an example accessibility trackpad of the sink system of FIG. 7-1.

FIG. 8-1 is a front view of an example sink system, including an automatic-cleaning system.

FIG. 8-2 is a perspective view of an example faucet of the sink system of FIG. 8-1.

FIG. 8-3 is a block diagram of an example controller for the sink system of FIG. 8-1.

FIG. 9-1 is a front view of an example sink system that includes an expanding-spray motion-detection system.

FIG. 9-2 is a side view of the sink system of FIG. 9-1.

FIG. 10-1 is a front view of an example sink system that includes an example “welcome” system and other audiovisual features.

FIG. 10-2 is a block diagram of an example controller for the sink system of FIG. 10-1.

FIG. 10-3 is a flowchart illustrating an example technique for triggering “welcome” events of the sink system of FIG. 10-1.

FIG. 11-1 is a perspective view of an example sink system that includes a beverage system.

FIG. 11-2 is a conceptual block diagram of an example hydration-customization station of the beverage system of FIG. 11-1.

FIG. 11-3 is a flowchart illustrating an example functionality of the hydration station of FIG. 11-2.

FIG. 11-4 is a flowchart illustrating an example operation of the hydration station of FIG. 11-2 to satisfy user preferences regarding artificial flavoring of the water.

FIG. 11-5 is a flowchart illustrating an example operation of the hydration station of FIG. 11-2 to improve a health of the user.

FIG. 11-6 is a flowchart illustrating an example operation of the hydration station of FIG. 11-2 to mimic a flavor of tap water from a particular geographic region.

FIG. 11-7 is a conceptual block diagram illustrating an example on-demand coffee station of the beverage system of FIG. 11-1.

FIG. 11-8 is a conceptual block diagram illustrating an example cocktail station of the beverage system of FIG. 11-1.

FIG. 12 is a block diagram illustrating an example command-center system that may be incorporated within the smart-kitchen environment of FIG. 1-1.

FIG. 13-1 is a front view of an example ozonated-mist-delivery unit that can be included within the smart-kitchen environment of FIG. 1-1.

FIG. 13-2 is a conceptual block diagram of the mist-delivery unit of FIG. 13-1.

FIG. 13-3 is a partial exploded view of the mist-delivery unit of FIG. 13-1.

FIG. 13-4 is a flow diagram illustrating an example technique for selecting or scheduling a cycle for the mist-delivery unit of FIG. 13-1.

FIG. 14 is a perspective view of an example self-cleaning kitchen robot for use in the smart-kitchen environment of FIG. 1-1.

FIG. 15 is a flowchart of an example electronic remodeling service system for the smart-kitchen environment of FIG. 1-1.

FIG. 16 is a top perspective view of an example sink system that includes a seamless drainage catch.

FIG. 17 is a perspective view of an example sink system that includes dual sink modules.

FIG. 18-1 is a cross-sectional view of an example sink system that includes a handsfree, magnetic sink stopper.

FIG. 18-2 is a perspective view of a drain cover of the sink system of FIG. 18-1.

FIG. 18-3 depicts the magnetic sink stopper of FIG. 18-2 in a “sealed” or “energized” state.

FIG. 19-1 is a perspective view of an example sink system that includes a produce-washing system.

FIG. 19-2 is a perspective view of the produce-washing system of FIG. 19-1.

FIG. 19-3 is a perspective view of the produce-washing system of FIG. 19-1, including a basket.

FIG. 19-4 is a perspective view of the produce-washing system and basket of FIG. 19-1.

FIG. 19-5 is a conceptual diagram illustrating different example washing cycles using the washing system of FIG. 19-1.

FIG. 20-1 is a perspective bottom view of an example produce basket with a magnetic impeller.

FIG. 20-2 is a perspective view of the produce basket of FIG. 20-1.

FIG. 20-3 is an overhead view of the produce basket of FIG. 20-1.

FIG. 20-4 is a perspective bottom view of a produce basket with two magnetic impellers.

FIG. 20-5 is a perspective bottom view of a portion of the produce basket of FIG. 20-4.

FIG. 20-6 is a perspective view of a magnetic impeller of the produce basket of FIG. 20-4.

FIG. 20-7 is a perspective view of an example magnetic liquid stirrer having a motorized magnetic rotation mechanism.

FIG. 20-8 is a perspective view of an example magnetic liquid stirrer having a motorless magnetic rotation mechanism.

FIG. 21-1 is a perspective top view of an example sink system including a sliding basin lid.

FIG. 21-2 is a perspective view of the sink system of FIG. 21-1.

FIG. 21-3 is a perspective top view of the sink system of FIG. 21-1.

FIG. 21-4 is a perspective view of the sliding basin lid of FIG. 21-1.

FIG. 21-5 is a perspective cross-sectional bottom view of a portion of the sliding basin lid of FIG. 21-1.

FIG. 21-6 is a perspective side view of a portion of the sliding basin lid of FIG. 21-1.

FIG. 21-7 is a perspective bottom view of the sliding basin lid of FIG. 21-1.

FIG. 21-8 is a side view of the sliding basin lid of FIG. 21-1.

FIG. 22-1 is a perspective view of an example sink system including a water jet.

FIG. 22-2 depicts an example jet for the sink system of FIG. 22-1.

FIG. 22-3 depicts another example jet for the sink system of FIG. 22-1.

FIG. 23-1 is a perspective side view of an example sink system having an apron-front storage compartment.

FIG. 23-2 is a perspective view of the sink system of FIG. 23-1.

FIG. 23-3 is a side view of the storage compartment of FIG. 23-1 in a “closed” position.

FIG. 23-4 is a side view of the storage compartment of FIG. 23-1 in an “open” position.

FIG. 23-5 is a perspective side view of a mounting plate for the storage compartment of FIG. 23-1.

FIG. 23-6 is a perspective top view of a movable joint for the storage compartment of FIG. 23-1.

FIG. 23-7 is a perspective side view of the movable joint of FIG. 23-6.

FIG. 23-8 is a perspective view of the movable joint of FIG. 23-6, including a control rod.

FIG. 23-9 is a perspective view of the storage compartment of FIG. 23-1, including the mounting plates of FIG. 23-5.

FIG. 23-10 is a perspective bottom view of a portion of the storage compartment of FIG. 23-1.

FIG. 23-11 is a transparent side view of the movable joint of the storage compartment of FIG. 23-1.

FIG. 23-12 is a perspective view of the sink system of FIG. 23-1, including the control rod of FIG. 23-8.

FIG. 23-13 is a perspective view of the sink system of FIG. 23-1, including the control rod of FIG. 23-8 and a one-way damper.

FIG. 24 is a front view of an example sink system, including an air-gap concealing apparatus.

FIG. 25 is a front view of an example sink system, including an air-gap stowing mechanism.

FIG. 26 is a perspective view of an example sink system, including an automatic washing system and a solenoid-based drying mechanism.

FIG. 27 is a perspective top view of an example sink system, including an example automatic produce-drying system.

FIG. 28 is a front view of an example sink system, including another example automatic produce-drying system.

FIG. 29 is a conceptual diagram of an example sink system, including a pressure-controlled produce-washing system.

FIG. 30 is a front view of an example sink system, including an automatic basin-fill system.

FIG. 31-1 is a conceptual diagram of an example sink system, including a pesticide monitor.

FIG. 31-2 is a flowchart illustrating an example produce-cleaning cycle using the sink system of FIG. 31-1.

FIG. 32-1 is a perspective view of an example sink system, including an integrated input panel.

FIG. 32-2 is an exploded side view of the input panel of FIG. 32-1.

FIG. 33-1 is a perspective view of the underside of an example of a capacitive sensing input panel.

FIG. 33-2 is an elevational view of the capacitive sensing input panel of FIG. 33-1.

FIG. 33-3 is a top view of a printed circuit board (PCB) according to an example.

FIG. 33-4 is an elevational view of the PCB of FIG. 33-3.

FIG. 33-5 is an elevational view of a combination of the capacitive sensing input panel of FIG. 33-1 and the PCT of FIG. 33-3.

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

DETAILED DESCRIPTION

Before turning to the figures, in general, a “kitchen” is a room or area within a building designated for the preparation of meals (e.g., food) and other associated activities. As just a few illustrative examples, a kitchen may include: a refrigerator and/or freezer for storage of perishable food ingredients; cabinets for storage of non-perishable food ingredients and/or dishware and glassware; a stovetop, oven, and/or microwave oven for heating foodstuffs for cooking and baking; and a sink for washing and cleaning of food items and dishware.

In many cases, a household kitchen may include a sink and a faucet. The sink often includes one or more basins and one or more faucets, where the faucet is manually or digitally controlled using a handle, a sensor and processor assembly, or both. Positioned below the sink are the utility lines for the water connections and drain plumbing. In some examples, an electrical outlet is positioned below the sink, allowing for the installation of a garbage disposal. Because the cabinet space below a sink can be damp, difficult-to-reach, and crowded with utility connections, a user may avoid storing cookware and food below the sink. Instead, the user may decide to store cleaning supplies, tools, and other equipment that would not be safe to store with food.

FIG. 1-1 is a perspective view of a smart-kitchen environment 100 that includes a first example kitchen-sink system 110, and FIG. 1-2 is an overhead view of sink system 110 of FIG. 1-1. In general, kitchen-sink system 110 is an integrated, multi-purpose/multi-functional unit, which may be configured to replace more-traditional kitchen systems having distinct, designated functional units (e.g., including separate sinks, cabinets, dishwashers, etc.). For instance, as shown in FIG. 1-1, sink system 110 is configured to fit into a recessed cabinet space 134 (e.g., indicated by the dashed rectangle bordering the back wall 104 of the recessed space). In some examples, recessed cabinet space 134 may be a “standard” cabinet space, e.g., an open space defining a width of approximately 36 inches, a depth of approximately 24 inches, and a height of approximately 40 inches, although it should be understood that, according to other examples, other configurations of cabinet space 134 may have differing dimensions. In some examples, recessed cabinet space 134 may be surrounded on one or more sides by cabinet(s) 102A, 102B (collectively, “cabinets 102”), and on one or more other sides by wall(s) 104 (e.g., in the corner of two walls). Sink system 110 may be sized to fit any suitable recessed cabinet space 134. For instance, recessed cabinet space 134 may be formed between, or adjacent to, cabinet(s) 102, and sized to receive sink system 110.

In certain configurations, sink system 110 includes electronic components, in which case, sink system 110 may be installed by plugging sink system 110 into an electrical outlet within kitchen environment 100, e.g., using one or more power cords 162 (FIG. 1-2). According to some examples, the electronic accessories provided with sink system 110 may already be installed and configured to be controlled by a wireless controller. For example, sink system 110 may include one or more faucet(s) 150, a spray wand 158 (FIG. 1-2), a side-sprayer, and/or an integrated dishwasher, each receiving a respective supply of water from connected utility lines. A user may use the wireless controller to turn on faucet 150 and/or the side-sprayer. The user may also use the wireless controller to turn off faucet 150 and the side-sprayer, and to turn on the integrated dishwasher. With all of the accessories already installed within integrated sink system 110, the user only has to connect the utility lines and the power cord 162 to provide water and electricity to sink system 110.

In some examples, sink system 110 includes sanitizing features, such as ultraviolet light(s) and/or sanitizing mists. The ultraviolet lights may be in visual communication with each of the drawers, operatively coupled to the power supply, and controllable by the wireless controller. Similarly, the sanitizing mist may spray into a cabinet 138 below the sink to sanitize sponges, towels, clothes, or anything else stored in cabinet 138.

In the example shown in FIG. 1-1, sink system 110 includes a sink module 136 and a lower cabinet module 138. Sink module 136 may be coupled to an upper portion of cabinet module 138, and may be configured to be positioned within recessed cabinet space 134 proximate to a countertop 140 above cabinet(s) 102. Sink module 136 includes a top surface 112 extending about a perimeter of the sink module 136 and includes a backsplash 106 extending upward proximate a rear portion of sink module 136, the backsplash 106 being contiguous with top surface 112. When sink module 136 is installed within recessed cabinet space 134, top surface 112 may be in the same plane as countertop 140 so as to provide a cohesive, seamless appearance. In other examples, top surface 112 may be positioned slightly lower than countertop 140.

In some examples, top surface 112 is adjustable (e.g., via lower cabinet module 138) to be positioned either above or below countertop 140. Similarly, backsplash 106 may be contiguous with an existing backsplash of countertop 140. Sink module 136 may be formed from a corrosion-resistant material, such as stainless steel, aluminum, cast iron or plastic. In some examples, sink module 136 may be formed from sheet metal that may be stamped and bent into the shape of top surface 112 and backsplash 106. Sink system 110 may be installed within, or on top of, a standard-sized lower cabinet module 138, e.g., defining a height of at least 36 inches. In other examples, lower cabinet 138 may include a height less than 36 inches.

As shown in FIG. 1-2, sink module 136 includes a leading edge 114 (e.g., front edge, first edge) and a trailing edge 108 (e.g., rear edge, second edge, etc.) positioned opposite to leading edge 114. Top surface 112 extends between leading edge 114 and trailing edge 108. Backsplash 106 extends orthogonally away from sink module 136 proximate to trailing edge 108. A basin 116 (e.g., a “first” basin 116) extends into sink module 136 between leading edge 114 and trailing edge 108 such that a portion 142 of top surface 112 is positioned between first basin 116 and leading edge 114. First basin 116 includes sidewalls 118, a catch 120, and a drain opening 122. Sidewalls 118 are contiguous with top surface 112 and may be formed from the same material as top surface 112, such as a common sheet of material (e.g., through stamping and bending). Catch 120 may be contiguous with sidewalls 118 and defines drain opening 122. First basin 116 may be configured for receiving a flow of liquid and/or waste and delivering the flow to drain opening 122. In some examples, drain opening 122 may be positioned proximate to a corner of catch 120. In some examples, drain opening 122 is centered in catch 120.

First basin 116 can define any suitable shape, including circular, elliptical, racetrack, obround, rectangular, rounded-corner rectangular, etc. In some examples, first basin 116 extends between a first (or “left”) peripheral edge 148 and a second (or “right”) peripheral edge 124 of sink module 136, such that a “left” narrow portion 152A of top surface 112 may be positioned between first peripheral edge 148 and first basin 116, and a “right” narrow portion 152B of top surface 112 may be positioned between second peripheral edge 124 and first basin 116.

In some examples, but not all examples, sink module 136 may include just one basin (e.g., first basin 116), commonly referred to as a “single basin” sink. First basin 116 may further include a pair of ledges 126A, 126B (collectively, “ledges 126”) extending orthogonally into first basin 116 and configured to support an accessory within or above first basin 116, such as a drying rack 154 and/or a cutting board. Ledges 126 may extend perpendicularly to leading edge 114. In other examples, ledges 126 extend substantially parallel to leading edge 114. A sink rack 154 may be sized to be positioned across first basin 116 and engage with both ledges 126. Ledges 126 may be vertically offset from top surface 112, e.g., positioned lower into first basin 116. In other examples, sink rack 154 may be sized such that a top-facing surface of sink rack 154 may be in the same plane as top surface 112.

In some examples, sink module 136 includes “trimming” features configured to extend outward over the adjacent edges of countertop 140 to provide the appearance of a continuous or “clean” surface or edge. For instance, a perfectly sized recessed cabinet space 134 may be difficult to build or cut, resulting in countertop 140 featuring “rough” edges proximate to recessed cabinet space 134. Accordingly, top surface 112 proximate left peripheral edge 148 and right peripheral edge 124 may extend over countertop 140 when sink system 110 is installed in recessed cabinet space 134 in order to cover the rough or imperfect edges of countertop 140. A bead of caulk or similar sealant may then be interposed between top surface 112 and countertop 140.

In some examples, but not all examples, sink module 136 includes a second basin 128 extending into sink module 136. Second basin 128 may be positioned in confronting relation to first basin 116, and may include similar features as those described above with respect to first basin 116. One example difference between first basin 116 and second basin 128 may be that second basin 128 has a greater depth (e.g., vertical distance between top surface 112 and catch 156). In some examples, a partition 130 extends between first basin 116 and second basin 128 such that first basin 116 and second basin 128 are fluidly isolated from one another. Partition 130 may include one of ledges 126. Second basin 128 may be similar to first basin 116, in that second basin 128 includes sidewalls and/or a drain opening defined by catch 156. For example, second basin 118 may be fluidly coupled to a garbage disposal, making second basin 128 a dedicated food-waste basin.

In some examples, second basin 128 includes a basin lid 132 for covering second basin 128 to prevent foreign objects from falling into second basin 128. In some examples, basin lid 132 forms a watertight seal about second basin 128. Basin lid 132 may be pivotably coupled to sink module 136. In some examples, basin lid 132 may pivot about a pivot axis that extends substantially parallel to trailing edge 108. In other examples, basin lid 132 pivots about a pivot axis that extends substantially perpendicular to trailing edge 108. In yet other examples, basin lid 132 may be slid laterally in and out of engagement with second basin 128. In some examples, first basin 116 includes a basin lid similar to basin lid 132.

In some examples, sink module 136 includes a recessed back portion 160 (e.g., vertically recessed relative to top surface 112) positioned between backsplash 106 and first basin 116 and/or second basin 128. Back portion 160 can define further-recessed depression(s) 144A, 144B (collectively “recesses 144”) configured to retain sink items such as soap bottles, sponges, and the like. Back portion 160 may be generally elongated or rectangular in shape, and may be contiguous with sidewalls 118 such that waste and fluids from recessed surface 160 can easily be wiped into first basin 116 and/or second basin 128 for disposal.

A faucet 150 extends through an opening 146 in back portion 160 between recesses 144A, 144B. Faucet 150 provides a water spray to first basin 116 and second basin 128. Faucet 150 may be a goose-neck-type faucet (as shown in FIGS. 1-1 and 1-2), or any other suitable type of faucet configured for discharging a fluid into first basin 116 and second basin 128.

The present disclosure describes additional “smart” features that may be integrated (or otherwise implemented) within smart-kitchen environment 100 of FIG. 1-1, particularly with respect to enhancing a user experience (“UX”) for a user of kitchen environment 100. For instance, FIG. 2 is a front view of a second example sink system 210 that may be integrated within smart-kitchen environment 100. Sink system 210 may be an example of sink system 110 of FIGS. 1-1 and 1-2, apart from any differences explicitly noted herein.

In the example shown in FIG. 2, sink system 210 includes a sink module 236 (e.g., sink module 136 of FIGS. 1-1 and 1-2) and a lower cabinet module 238 (e.g., lower cabinet 138 of FIG. 1-1). Sink module 236 may be configured to be positioned on top of the cabinet module 238. In other examples, sink module 236 includes a base module that acts as a ground support. Sink module 236 may be configured to receive a material (e.g., water, liquid, waste, food, etc.) from a faucet 250 (e.g., faucet 150 of FIGS. 1-1 and 1-2).

Faucet 250 may be positioned proximate, and on top of, sink module 236. Faucet 250 may be actuated between “on” and “off” positions, such that faucet 250 dispenses fluid(s) (e.g., tap/ozonated/soapy water). Faucet 250 may be manually actuated between the “on” and “off” positions by a handle 240. In other examples, faucet 250 may be actuated or activated between the “on” and “off” positions via a touchless sensor, which may be located at any suitable location of sink system 210.

Additionally or alternatively, faucet 250 may be actuated between the “on” and “off” positions using voice controls. Additionally or alternatively, faucet 250 may be actuated between the “on” and “off” positions via a mobile application (or “app”), which can also include temperature controls for the water being output. Faucet handle 240 may be positioned proximate to the base of faucet 250, wherein faucet handle 240 is rotatable about faucet 250. The user may provide a distal force onto faucet handle 240 to actuate faucet 250 between the “on” and “off” positions. Furthermore, the user may rotate faucet handle 240 to change the temperature of the material being dispensed by faucet 250. By way of example, the user may rotate faucet handle 240 toward backsplash 106 to increase the temperature of the material dispensed by faucet 250.

In accordance with techniques of this disclosure, sink system 210 includes a sensor system 220 having one or more sensors 222A, 222B (collectively, “sensors 222”). Although FIG. 2 shows two sensors 222, sink system 210 can include more sensors or fewer sensors, or different types of sensors, or the sensors 222 may be located at different positions on or within various components of sink system 210 than those shown in FIG. 2.

In a first illustrative example, sensor system 220 includes a total dissolved solids (“TDS”) sensor 222A configured to detect and measure a water quality (e.g., purity, cleanliness) prior to dispensing the water from faucet 250. For instance, TDS sensor 222A may be integrated into faucet 250, or into a holding tank (not shown) beneath sink 236. In other examples, TDS sensor 222A may include a modular “add-on” that can be manufactured and sold separately from, but later retrofitted to, sink system 210A.

In some examples, TDS sensor 222A is configured to measure the water quality on a continuous (or virtually continuous) basis. In other examples, TDS sensor 222A is configured to measure the water quality on an intermittent or discrete basis, or on a user-customizable, scheduled basis. For instance, TDS sensor 222A may be configured to measure and output an indication of the water quality once per day (e.g., either at the beginning of each day, or at the first use of faucet 250 each day), or alternatively, every time faucet 250 is used.

In some examples, sink system 210 is configured to receive, from TDS sensor 222A, sensor data indicating the current water quality, and in response, generate and output an indication of the current water quality to the user. For instance, sink system 210 may generate a visual indication, an audible indication, and/or a tactile indication of the water quality. A visual indication, such as via an electronic display 224 (e.g., a liquid-crystal display (LCD) or the functional equivalent) of sink system 210, may include a numeric indication of the water quality (e.g., a TDS measurement, in parts-per-million (PPM)), a textual, “relative” indication of the water quality (e.g., “low,” “medium,” or “high”), and/or a color-coded “relative” indication of the water quality (e.g., green, yellow, or red). An audible indication may include a numeric indication of the water quality (e.g., a TDS measurement, in PPM) output by a speaker 226 of sink system 210, or a verbal relative indication of the water quality (e.g., “low,” “medium,” or “high”) output by speaker 226 of sink system 210. A tactile indication may include a vibrational signal output by faucet handle 240, such as a particular vibrational pulse pattern, vibrational intensity (e.g., amplitude), vibrational pulse frequency, etc.

In some examples, sink system 210 (e.g., processing circuitry incorporated within sink module 236) may further be configured to determine, based on the measured water quality, whether the water quality is below a predetermined minimum-water-quality threshold. In some such examples, sink system 210 is configured to output a relevant alert or indication, e.g., that a water filter of sink system 210 may need replacement. Additionally or alternatively, in response to identifying a sub-threshold water quality, sink system 210 may be configured to automatically engage or activate a new or additional water filter. In some such examples, sink system 210 can be configured to apply or activate the additional filter for a predetermined duration of time, or indefinitely, e.g., until a subsequent water-quality measurement indicates that the additional filter is no longer necessary, at which point sink system 210 can be configured to automatically remove or disable the water filter.

In a second illustrative example, sensor system 220 includes a water-flow-rate sensor 222B configured to detect and measure an amount of water dispensing from faucet 250. For instance, flow-rate sensor 222B may be integrated into faucet 250, or into a holding tank (not shown) beneath sink 236. In other examples, flow-rate sensor 222B may be a modular “add-on” feature that can be manufactured and sold separately, but later retrofitted to, sink system 210.

In some examples, sink system 210 is configured to measure, via flow-rate sensor 222B, an amount of water dispensed from faucet 250 over a predetermined time period, after which point, the amount of water (e.g., as stored in a digital memory incorporated within sink system 210) resets and begins counting anew. For instance, sink system 210 may be configured to measure and output an indication of the amount of water dispensed from faucet 250 during the current calendar day, during the current calendar week, during the current calendar month, during the current calendar year, or during any user-customizable time period. Additionally or alternatively, sink system 210 may be configured to store an indication of a total amount of water dispensed from faucet 250 since a predetermined historical point in time, e.g., without resetting after a predetermined duration.

In some examples, sink system 210 is configured to retrieve, from memory, an amount of water usage for the current predetermined time period, and compare the amount to a user-configurable water-usage target. For instance, a user of sink system 210 may wish to consciously reduce an amount of personal water usage, in order to conserve resources or to save money. In response, sink system 210 is configured to generate and output an indication of the current water usage to the user. For instance, sink system 210 may generate a visual indication, an audible indication, and/or a tactile indication of the water usage. A visual indication may include a numeric indication (e.g., via display 224) of the water usage (e.g., in gallons), a textual “relative” indication of the water usage (e.g., “low,” “medium,” or “high”), and/or a color-coded “relative” indication of the water usage (e.g., green, yellow, or red). An audible indication may include a numeric indication of the water usage (e.g., in gallons) output by speaker 226 of sink system 210, or a verbal relative indication of the water usage (e.g., “low,” “medium,” or “high”) output by a speaker of sink system 210. A tactile indication may include a vibrational signal output by faucet handle 240, such as a particular vibrational pulse pattern, vibrational intensity (e.g., amplitude), vibrational pulse frequency, etc.

In some examples, sink system 210 may further be configured to determine, based on the measured water usage, whether the water usage is above a predetermined usage threshold. As an illustrative example, sink system 210 can include a lighted faucet (e.g., LEDs that illuminate water dispensed from faucet 250) indicating a current status of daily water consumption. For instance, a green-lit water flow can indicate a “good” amount of water usage, a yellow-lit water flow can indicate that the user is approaching a target daily maximum amount of water usage, and a red-lit water flow can indicate that the user has reached, or has exceeded, the target daily maximum amount of water usage. In some such examples, the LEDs of lighted faucet 250 can additionally be manually activated, e.g., to function as a nightlight, or for directional lighting of difficult-to-see locations surrounding sink system 210.

In some examples, smart-kitchen environment 100 includes a virtual kitchen assistant 246. For instance, in the example shown in FIG. 2, virtual kitchen assistant 246 can include a hologram-based, anthropomorphic avatar configured to interact with the user, similar to how a human assistant might. Virtual kitchen assistant 246 (e.g., a processor-based engine of virtual assistant 246) may be configured to implement one or more artificial-intelligence (“AI”), machine-learning (“ML”), or deep-learning (“DL”) based models to generate relevant interactive content for a user of kitchen environment 100. In some such examples, virtual assistant 246 is configured to output verbal (e.g., audible) assistance via speaker 226.

Additionally or alternatively to a characterized avatar, virtual kitchen assistant 246 can include a computer-operating-system-type virtual environment, e.g., configured to project or display textual “windows” onto various surfaces within kitchen environment 100. These textual windows can display, e.g., kitchen-assisting instructions, such as recipes, tutorials, etc. For instance, cooking recipes and instructions can be projected onto planar surfaces such as a wall, floor, window, refrigerator door, a microwave door, a vent hood, the door of cabinet 238, or any other appropriate planar surface within kitchen environment 100.

In some examples, virtual kitchen assistant 246 can be a projected hologram, e.g., visible to any persons present within kitchen environment 100, and projected by projector (not shown) placed within kitchen environment 100 (such as within a cabinet, below the sink deck, within a wall, floor, or ceiling, located on the faucet, in the sink, etc., and projected through an aperture formed therein). In other examples, virtual kitchen assistant 246 can be, or can include, an augmented-reality (AR) based system, e.g., only visible through an appropriate AR headset (e.g., augmented-reality goggles) worn by a particular user within kitchen environment 100.

FIGS. 3-1 through 3-4 illustrate a third example sink system 310 (e.g., sink system 110 of FIGS. 1-1 and 1-2) that can be implemented within smart-kitchen environment 100 of FIG. 1-1. In particular, sink system 310 of FIGS. 3-1 through 3-4 includes an ozonated-mist-delivery system 300 configured to produce and disperse ozone-sterilized water 301, e.g., for gently-but-thoroughly washing produce prior to consumption (or other cleaning purposes). Mist-delivery system 300 includes one or more sprayheads 302, each configured to deliver ozonated mist 301 in a different spray configuration, as detailed further below. In some examples, such as the perspective view shown in FIG. 3-1, sprayhead(s) 302 can be configured for use with a faucet 350 (e.g., faucet 150 of FIGS. 1-1 and 1-2) of a sink module 336 (e.g., sink module 136 of FIGS. 1-1 and 1-2). In other examples, a distinct (e.g., designated and self-contained) sprayer unit (e.g., side sprayer 158) can include sprayhead 302.

FIG. 3-2 is a conceptual block diagram illustrating some example components of mist-delivery system 300 of FIG. 3-1. As shown in FIG. 3-2, mist-delivery system 300 further includes an ozone generator 308, an injector module 312, and at least one sensor 322 (e.g., sensors 222 of FIG. 2). Faucet 350 can be situated to deliver fluid 301 through sprayhead(s) 302.

Ozone generator 308 can be configured to be mounted on faucet 350 and fluidly coupled to sprayhead 302, such that ozone generator 308 infuses gaseous ozone into the fluid directed by sprayhead 302.

Sensor 322, which can be operably coupled to ozone generator 308, is configured to detect ozone levels in the fluid 301 prior to delivery via sprayhead 302, and output a signal indicating the detected level of ozone in the fluid 301. For instance, sensor 322 can include a capacitive sensor, or any other suitable sensor configured to detect and indicate ozone levels in fluid 301. System 300 further includes control circuitry 346, e.g., integrated within ozone generator 308 and/or sink module 336, configured to monitor the output signal from ozone-level sensor 322 to operate ozone generator 308, e.g., to increase or decrease ozone levels, as appropriate, toward a predetermined or user-configurable “target” ozone level.

FIG. 3-3 is a close-up view of a portion of sprayhead 302 of mist-delivery system 300 of FIG. 3-1. As shown in FIG. 3-3, sprayhead 302 includes a valve 304 (e.g., a fluid-control valve or diverter) having one or more chambers 306. Valve 304 is configured to control a flow of fluid (e.g., water 301) through sprayhead 302. Sprayhead 302 further defines at least one fluid outlet 314 (e.g., an outlet member defining a fluid lumen therein) configured to direct the spray of fluid 301 as it exits sprayhead 302. Sprayhead 302 further includes at least one actuator 316 configured to control operation of valve 304, e.g., to cause valve 304 to switch between different spraying functions. Actuator 316 may be configured as a toggle, a switch, a button, or any other suitable manual-input mechanism. Sprayhead 302 can include one or more guiding features (e.g., studs, pivots, guides, bosses, protrusions, axles, etc.) configured to guide and/or facilitate movement of the actuator 316. Actuation of actuator 316 causes a change in operation (e.g., fluid flowrate, spray pattern, etc.) of sprayhead 302.

As shown in FIGS. 3-2 and 3-3, sprayhead 302 includes a fluid inlet 318 configured to receive a supply of fluid 301 from an adjoining member, such as faucet 350 and/or ozone generator 308, either of which may be operably coupled to sprayhead 302 via a connector 320. Connector 320 can be disposed proximally to fluid inlet 318 to facilitate use of sprayhead 302. For example, connector 320 may define the fluid inlet 318 (or a proximal portion thereof), which is fluidly connected to (e.g., in fluid communication with) valve 304 of sprayhead 302, so as to introduce fluid 301 into valve 304. In some examples, connector 320 is configured to detachably couple, e.g., via screw-threads, to a hose 324 that fluidly couples sprayhead 302 to ozone generator 308, which is detachably mounted and fluidly connected to faucet 350 of sink 336 (FIG. 3-1).

In some examples, hose 324 includes a telescoping-type connector 325 for removably decoupling to spout 326 of faucet 350. In other words, connector 325 enables sprayhead 302 to couple to, and de-couple from, ozone generator 308, and also enables hose 324 to be retracted into, and extracted from, spout 326.

Fluid inlet 318 of sprayhead 302 can function as a chamber (e.g., can define an internal cavity) within sprayhead 302, and can provide a space for ozone generator 308 to release ozonated water 301. In some such examples, sensor 322 can be incorporated within sprayhead 302, and can monitor fluid 301 passing through fluid inlet 318 to determine whether fluid 301 includes a minimum level of ozone, wherein the minimum level can be pre-configured by default, or manually defined by a user. If control circuitry 346 of system 300 determines, based on sensor data from ozone sensor 322, that the minimum level of ozone is present in fluid 301, then ozone generator 308 can be configured to automatically stop operation. However, if system 300 determines that fluid 301 in fluid inlet 318 does not meet threshold ozone levels, control circuitry 346 activates ozone generator 308 to produce additional ozone. Internal mechanics of ozone generator 308 are detailed further below.

Eventually, fluid 301 directed into fluid inlet 318 flows out through one or more fluid outlets 314A, 314B, 314C (collectively, “outlets 314,”) e.g., through inner lumens of outlet members positioned opposite valve 304 from fluid inlet 318). In some examples, fluid 301 flows virtually “uninhibited” through fluid outlet(s) 314, e.g., without stopping in any of chambers 306 of sprayhead 302.

As shown in FIG. 3-3, for a first mist-spray configuration 329 of sprayhead 302, a first fluid outlet 314A is fluidly coupled to a first subset of a plurality of individual fluid nozzles 328 mutually arranged, as an illustrative example, in an annular configuration, so as to direct fluid 301 according to a first spray pattern 329 (e.g., an annular-shaped spray pattern 329) as fluid 301 is dispensed from nozzles 328.

Sprayhead 302 can further include a second fluid outlet 314B configured to provide a second spray configuration that is different than the first spray configuration 329, e.g., with respect to one or more of spray-pattern shape, flowrate, fluid pressure, fluid-pulse frequency, or another parameter of fluid 301. For example, fluid outlet 314B can include at least one nozzle 328 that provides an aerated stream of fluid from sprayhead 302.

Sprayhead 302 can further include a third fluid outlet 314C configured to provide a third spray configuration that is different than the first and second spray functions. For example, fluid outlet 314C can include a third subset of the plurality of nozzles 328 configured to dispense a fine, gentle spray, e.g., configured to clean produce (e.g., fruit) or other delicate objects.

As shown in FIG. 3-3, sprayhead 302 includes an actuator 316 (e.g., button, switch, toggle, etc.). Actuator 316 controls valve 304 to change (e.g., switch) the operation of sprayhead 302 between its two or more spray configurations. According to some examples, actuator 316 includes a button configured to move between a first position (e.g., a non-depressed position) and a second position (e.g., a depressed position). For instance, when the button 316 is in the first position, valve 304 of sprayhead 302 directs the fluid to a first outlet 314A configured to provide a first spray type. When the button 316 is depressed from the first position into the second position, the valve 304 directs the fluid to a second outlet 314B configured to provide a second spray type that is different from the first spray type.

As shown in FIG. 3-3, sprayhead 302 can optionally include a housing 330 (e.g., a casing, etc.) configured retain one or more internal components of sprayhead 302. Housing 330 can include an outer wall having a first portion 332A and a second portion 332B, which collectively define an internal cavity 331 that retains at least a portion of valve 304 therein.

Housing 330 can define a first opening 334A (e.g., proximate fluid inlet 318) disposed at a first end (e.g., an inlet end) of the housing 330 adjacent to the first portion 332A, and a second opening 334B (e.g., fluid outlet(s) 314) disposed at a second end (e.g., an outlet end) of the housing 330 adjacent to the second portion 332B. A portion of sprayhead 302, such as connector 320 and/or valve 304, is configured to extend proximally through the first opening 334A. Similarly, fluid outlet(s) 314 and/or nozzles 328 may be disposed in the second opening 334B. For instance, as shown in FIG. 3-3, fluid outlets 314 are disposed in second opening 334B of housing 330, such that fluid 301 directed from fluid outlets 314 is discharged from second end 332B of housing 330 defining second opening 334B.

FIG. 3-4 is a conceptual block diagram of ozone generator 308 as mounted on faucet 350 of sink 336 (FIG. 3-1) to access a water supply for ozone-purification. Ozone generator 308 is detachably and operably coupled to faucet 350 via connectors 320, 325 such that ozone generator 308 works in conjunction with sprayhead 302 (FIG. 3-3). Ozone generator 308 can include a first electrode 338A, e.g., formed from stainless steel or any other suitable material that is electrically conductive, cost-effective, and resistant to oxidation.

First electrode 338A, which may be ensconced within an outer dielectric (e.g., glass) casing 340, can be disposed inside a first chamber 342 of ozone generator 308, which can be considered the “ozone chamber.” Ozone chamber 342 includes an electrically conducting wall 338B that functions as a grounding electrode, such that first electrode 338A and wall 338B collectively generate an electrical corona to produce ozone gas. The ground electrode 338B can be made of stainless steel. Ozone chamber 342 includes at least a first opening 344 for introduction of oxygen, from which ozone gas can subsequently be produced.

Ozone generator 308 can be powered by a low-voltage power source, such as a conventional wall power outlet coupled to a 110-Volt electrical supply. The low-voltage power source can also be coupled to control circuitry 346, configured to dynamically determine a power amplitude supplied to first electrode 338A and also to monitor the performance of ozone generator 308. Control circuitry 346, via sensor data received from ozone sensor 322, monitors the level of electrical current drawn through ozone generator 308. When the current amplitude exceeds a threshold level, control circuitry 346 automatically disables the operation of ozone generator 308. Control circuitry 346 can also be configured to interrupt operation of ozone generator 308 when the electrical current falls below a threshold level in order to conserve resources.

Ozone generator 308 further includes a venturi 348 configured to introduce ozone generated by ozone generator 308 into non-ozonated water 301A, which is ultimately dispensed as ozonated water 301B by sprayhead 302. Venturi 348, which creates a bottleneck in the stream of water, allows tube 352 to be inserted at the bottleneck, whereupon ozone gas is injected such that the stream of water 301A becomes infused with ozone.

Water 301A is supplied from faucet 350 of sink 336 using a generic conduit component that allows for pumping water through ozone generator 308. Ozone generator 308 then generates ozone, which is then injected into the water stream via venturi 348. Ozonated water 301B then flows into a reaction chamber 354, which, in some examples includes first fluid inlet 318 of sprayhead 302, or in other examples, includes a separate reaction chamber 354 within ozone generator 348.

Reaction chamber 354 is designed such that the generated ozone, after infusion into the stream of water, interacts with any contaminants suspended in the water for a duration of time sufficient to neutralize their toxic effects. For instance, as water 301B flows into reaction chamber 354, it can also pass through an optional diffuser 356 configured to ensure that the ozone gas is more thoroughly diffused into the water stream. After spending at least a threshold amount of time (which can be predetermined or manually selected) within reaction chamber 354, the water can be filtered (357) before flowing into an ozone separator 358. Ozone separator 358 separates any remnant gaseous ozone from the water stream and directs the remnant gaseous ozone to an ozone eliminator module 360 for disposal. The treated water 301B is then pumped from ozone separator 358 to fluid inlet 318 of sprayhead 302 to be dispensed upon user-actuation of actuator 316.

FIGS. 4-1 and 4-2 illustrate a fourth example sink system 410 (e.g., sink system 110 of FIGS. 1-1 and 1-2) that can be implemented within smart-kitchen environment 100 of FIG. 1-1. In particular, sink system 410 of FIGS. 4-1 and 4-2 includes an on-demand liquid-conditioning system 400 configured to modify, on-demand, one or more properties (e.g., temperature, filtration, softening, etc.) of a liquid 401, such as water (e.g., water 301 of FIGS. 3-1 through 3-4). In general, system 400 is designed to increase thermal efficiency, so as to the lower heat loss associated with typical plumbing systems. System 400 also lowers the plumbing requirements for home construction, as well as the design requirements and footprint for the number of waterways required for installed water features and other products.

For instance, liquid-conditioning system 400 includes a main housing unit 402 that includes at least one inlet manifold 404 defining a fluid inlet 406, an internal cavity 408, and an outlet conduit 412. Internal cavity 408 is configured to retain a plurality of water-conditioning units 414, such as heater(s) 418, cooler(s) 438, and/or filter(s)/softener(s) 452, the respective inlets of each of which are connected in a parallel, series, or mixed fluid-flow relationship via inlet manifold 404, and the outlets of each of which are each connected to a separate outlet conduit 416, and which is configured to provide conditioned water 401B to one or more liquid fixtures 450 (e.g., sinks, showers, etc.).

In various examples, housing 402 of water-conditioning system 400 contains one or more water-customization units 414 including, e.g., at least one water heater 418 having a respective liquid inlet 418A and a liquid outlet 418B. In examples having multiple liquid inlets 418A, the inlets may be mutually connected in a parallel fluid-flow relationship to inlet manifold 404 that, in turn, can be fluidly connected to a source 420 of liquid 401A to be heated, e.g., a water line, by an inlet-manifold connector 422. Outlet(s) 418B of heater(s) 418 are connected to one or more liquid-outlet conduit(s) 412. Each outlet conduit 412 can be, for example, connected to a separate fixture 450 for the supply of conditioned (e.g., heated) liquid 401B.

Liquid heater 418 includes one or more electrical-resistance-heating elements 424. The electrical power to the electrical-resistance-heating elements 424 can be configured to pass through a switching unit 426A and, in certain examples, a separate circuit relay 428 (also referred to as “contactor 428”) for each heater 418. Control circuitry 446, which, in certain configurations, can be mounted on the heater 418, regulates the operation of switching unit 426A and hence the current flow to one or more electrical-resistance heaters 424 of heater 418. Circuit relay 428A can be connected to an electrical-power source 430 (e.g., line voltage) via taps 432 in terminal blocks 434.

Controller 446 (e.g., control circuitry 346 of FIG. 3-2) furnishes an output control signal to switching unit 426, which gates power from terminal block 434 for selectively energizing one or more electrical-resistance-heating elements 424 of heater 418. In certain configurations, controller 446 regulates electrical current flow to one or more electrical resistance heating elements 424 in response to a signal produced by a sensor 436A, such as a temperature sensor, a flow sensor, or both. Controller 446 can be configured to prevent energizing an electrical-resistance-heating element 424 of liquid heater 418 until the flow rate of liquid 401 through the liquid inlet 418A exceeds a predetermined flow-rate threshold. Heater 418 can include a temperature sensor 436A, operably disposed in a liquid outlet 418B of heater 418, that provides a signal to controller 446 for regulating electrical-current flow to one or more electrical-resistance-heating elements 424 and maintaining a desired output temperature of liquid 401.

Additionally or alternatively, water-customization system 400 includes one or more coolers 438 each having a liquid inlet 438A and a liquid outlet 438B. Liquid inlets 438A of cooler(s) 438 may be mutually connected in a parallel fluid-flow relationship by inlet manifold 404, which, in turn, can be connected to source 420 of liquid 401A to be cooled, e.g., a water line, by an inlet-manifold connector 442. Liquid outlets 438B of coolers 438 are connected to one or more outlet conduits 412. Each outlet conduit 412 can be connected to, for example, a separate fixture 450 for the cooled supply of conditioned liquid 401B.

Each cooler 438 includes a miniature refrigeration unit 444. The electrical power to miniature refrigeration unit 444 can be configured to pass through a switching unit 426B and, in certain examples, a separate circuit relay 428B (also referred to as “contactor 428B”) for each cooler 438. Controller 446, which, in certain configurations, can be mounted on cooler 438, regulates the operation of switching unit 426B and hence the current flow to one or more miniature refrigeration units 444 of cooler 438. Circuit relays 428B can be connected to a source 430 of electrical power (e.g., line voltage) via taps 432 in terminal blocks 434.

Controller 446 furnishes an output control signal to switching unit 426A, which gates power from terminal block 434 for selectively energizing miniature refrigeration units 444 of cooler 438. In certain configurations, controller 446 regulates electrical current flow to the miniature refrigeration units 444 in response to a signal produced by a sensor 436B, e.g., a temperature sensor, a flow sensor, or both. Controller 446 can prevent energizing of miniature refrigeration units 444 of cooler 438 until the flow rate of liquid 401 through liquid inlet 438A exceeds a predetermined fluid-flowrate threshold. Cooler 438 can include a temperature sensor 436B, operably disposed in liquid outlet 438B of cooler 438, which provides a signal to controller 446 for regulating electrical-current flow to miniature refrigeration units 444 and maintaining a desired temperature of conditioned liquid 401B.

Housing 402 of on-demand water-conditioning system 400 can define an enclosure 408 containing mounting points for electrical components (for example, circuit relays 426, terminal blocks 432, etc.) in addition to heaters 418 and coolers 438. In certain configurations, liquid heaters 418 and coolers 438 are directly mounted, at predetermined angles, to housing 402 via angle brackets.

Heater 418 further includes a heater cartridge 423, which is removably coupleable to housing 402 and can be removed and replaced without disconnecting heater 418 from inlet manifold 404 or outlet conduit 412. Heater cartridge 423 can be releasably secured to housing 402 by removable fasteners such that heater cartridge 423 can be readily released from heater 418 without disturbing the existing mounting of heater 418 and its plumbing connections to inlet manifold 404 or outlet conduit 412.

Similarly, cooler 438 includes a cooler cartridge 440, which is removably coupleable to housing 402 and can be removed and replaced without disconnecting housing 402 from inlet manifold 404 or outlet conduit 412. Cooler cartridge 440 can be releasably secured to housing 402 by removable fasteners such that cooler cartridge 440 can be readily released from cooler 438 without disturbing the existing mounting of cooler 438 and its plumbing connections to inlet manifold 404 or outlet conduit 412.

Housing 402 of on-demand water-conditioning system 400 can further retain filter/conditioner 452 within internal cavity 408. Liquid 401A, such as water, which is intended to be heated or cooled can travel through fluid inlet 406 and pass through filter/conditioner 452. Filter/conditioner 452 can include a removable filtration cartridge 453 configured to capture and remove impurities, such as sediments, from liquid 401A. For instance, cartridge 453 can include mesh material(s) that capture impurities while simultaneously allowing liquid 401A to pass through to other chambers within housing 402. Cartridge 453 may be readily detached from filter/conditioner 452 without affecting the overall structure or disposition of liquid-conditioning system 400.

FIGS. 5-1 and 5-2 illustrate a fifth example sink system 510 (e.g., sink system 110 of FIGS. 1-1 and 1-2) that can be implemented within smart-kitchen environment 100 of FIG. 1-1. In particular, sink system 510 of FIGS. 5-1 and 5-2 includes an immersive faucet system 500 for enabling an immersive user-experience (“UX”) for cooking. System 500 includes a faucet module 550, a plurality of temperature sensors 522, and an interactive user module 506 that incorporates an imaging unit 504 configured to sensing, recording, and displaying different types of imagery.

Immersive faucet system 500 can include a faucet module 550. In some examples, faucet module 550 is configured to be removably mounted to a sink 536, or as an integrated, standalone structure. For instance, although not shown in FIG. 5-1, in other examples, faucet 550 can be ceiling-mounted. Faucet module 550 is configured to dispense liquid 501 (e.g., water, etc.) from a nozzle or sprayhead 502. Faucet module 550 can be actuated by a control lever 540 (e.g., faucet handle 240 of FIG. 2), whereupon, depending on movement of control lever 540, faucet module 550 can be actuated to dispense water 501; specific movement of control lever 540 (e.g., moving control lever 540 up or down instead of right or left) can trigger proximity and capacitive sensors 522, safely disposed at any suitable location along sink system 510, to generate an output signal to be read by control circuitry 546 within interactive user module 506.

In certain examples, faucet module 550 of sink system 510 can be actuated between the “on” and “off” positions by interfacing with a mobile application (“app”) or a remote control, wherein the app or remote control can further provide temperature control over dispensed liquid 501. Control lever 540 can be positioned proximate to the base of the faucet 550, where the control lever 540 can be rotatable about faucet 550. The user can apply force to control lever 540, e.g., in a direction distal to faucet 550, to actuate faucet 550 between the “on” and “off” positions, and anywhere therebetween, to modify dispersed-water pressure, which can vary between a “completely on” pressure/position and a “completely off” pressure/position.

Sink system 510 can include a plurality of sensors 522, which can be positioned within various components of sink system 510. Sensors 522 are configured to generate a signal (or signals) to a communication unit 556 with the interactive user module 506 to operate or actuate various components of sink system 510.

User module 506 can be physically distinct from the rest of sink system 510, and can be configured to mount virtually anywhere on or near sink system 510. A controller 508 of user module 506 can be integrated within user module 506. In other examples, controller 508 can be remote from the physical user module 506. Controller 508 is configured to continually monitor for output signals generated by sensors 522, where receipt of the output signals can cause controller 508 to commence with operation.

Controller 508 can include a wireless communication device 556 (or “control communication 556”), a power supply 530, a processing logic 546, and a memory 512.

Controller 508 can transmit, via the control communication 556, executable instructions to activate an imaging unit 504, which can record images for further manipulation and can display recorded images based on user selections, such as by displaying holographic content.

Power supply 530 is configured to power controller 508. Power supply 530 can include disposable batteries (e.g., alkaline, lithium, zinc-air, etc.) or rechargeable batteries (lithium ion, nickel-cadmium, etc.). Controller 508 can plug into an outlet and receive either AC or DC current. In some configurations, controller 508 is wirelessly powered via inductive charging. For example, controller 508 can be mounted to a wall, behind which a wireless charger (e.g., copper coil, magnetic loop antenna, etc.) is positioned. The wireless charger can then interface with power supply 530, which is configured to wirelessly charge from the wireless charger positioned behind the wall.

Processing logic 546 is configured to send signals to, and receive signals from, control communication 556. Processing logic 546 can be operably coupled to memory 512, where instructions for how to respond to various signals is stored. Memory 512 can be a non-transitory memory that includes programming instructions stored thereon. In certain examples, the instructions are added to memory 512 during manufacturing (i.e., as firmware) and are inaccessible to the end user. For example, memory 512 can store instructions for how user module 506 is to be activated. In some examples, memory 512 can store instructions for activating imaging unit 504, and how to interpret signals generated by sensors 522 (e.g., whether a generated signal detected by controller 508 and communicated by unit 556 should be interpreted by processing logic 546 as including executable instructions for display of holographic content, or whether the executable instructions are for recording the user, etc.).

As shown in FIG. 5-2, user module 506 further includes a trackpad 514 that includes one or more of sensors 522. Trackpad 514 is configured to communicate with controller 508 by generating output signals, where the user can determine modes of operation for user module 506 from a plurality of modes of operation by pressing down on different actuators of the trackpad 514. For example, trackpad 514 can include a plurality of buttons 516, where each button is linked to a separate capacitive sensor 522 which, in turn, generates a separate output signal for detection by controller 508. Each different signal can have different executable instructions encoded therein. For example, a first button 516A can generate an output signal configured to cause imaging unit 504 to activate recording.

Imaging unit 504 can also include a microphone 518 and speaker 520 for voice detection, recording, and playing audible sounds, in conjunction with a display 524 for displaying images, such as recordings or holograms. Recordings recorded by imaging unit 504 can be directly uploaded to the Internet, e.g., while user module 506 is connected to Wi-Fi. Additionally or alternatively, pressing a second button 516B generates a signal that actuates display of prerecorded video images or real-time video images. For instance, imagery triggered by button 516B can depict well-known chefs instructing the user on best policies for cooking, exceptional recipes, motivational speeches, etc. Additionally or alternatively, pressing a third button 516C generates a signal that actuates display of video images in the form of holographic avatars (e.g., avatar 246 of FIG. 2) projected opposite imaging unit 504.

Sensors 522 can include proximity sensors 522A, capacitive touch sensors 522B, and temperature sensors 522C. Temperature sensors 522C can be embedded throughout sink system 510 and can generate output signals based on whether the temperature detected on the surface of the sensors 522C is above, within, or beyond a threshold temperature range, for instance, to warn a user of surfaces that are dangerously hot or cold to the touch. Additionally, temperature sensors 522C can be used to detect temperature of items placed directly on top of them, such as fruits, vegetables, or other produce. Leveraging this feature, temperature sensors 522C and related proximity sensors 522A can generate output signals to generate alerts, warnings, or other messages to indicate to the user that food items placed atop the sensors 522 achieve a temperature indicative of having been fully cooked.

FIG. 6 illustrates a sixth example sink system 610 (e.g., sink system 110 of FIGS. 1-1 and 1-2) that can be implemented within smart-kitchen environment 100 of FIG. 1-1. In particular, sink system 610 of FIG. 6 includes a sleeve system 600 for decorating (and optionally insulating) flexible waterway features, such as exposed portions of faucets 650 and/or hoses 624, with limited-edition sleeve(s) 606. Sleeve 606 includes at least one base tube 602. In some examples, tube 602 can define a cylindrical shape, e.g., closely tailored to typical waterway configurations. Tube 602 can be formed from a flexible, water-resistant material that can mimic the flexibility of, and conform to curvature of, certain waterways intended for adornment, such as plastic or rubber waterways. As a non-limiting example, a waterway feature can include a flexible hose 624, a curved faucet 650, or any other exposed waterway. Tube 602 can also be formed from harder, more rigid materials to provide more structure, such as brass. Tube 602 has an input endpiece 608A, an output endpiece 608B, and a decorative cover sleeve 612 lining the exterior of the base tube 602. Decorative cover sleeve 612 can include any of a plurality of suitable decorative materials, including a woven or silk material for decorative purposes.

Sleeve system 600 is adapted to be fitted on any waterway, particularly flexible waterways. Therefore, base tube 602 is configured to be fastened and unfastened. Tube 602 can be unfasted by removing fasteners, such as screws, along its body, whereupon tube 602 will lay open and enable receipt of a waterway 604 therein. Once tube 602 has been fitted along or over the waterway, tube 602 can be re-fastened using fasteners (e.g., screws, etc.).

Input end 608A is configured to connect to a supply water line that provides a stream of water through the flexible waterway. For example, input end 608A can be proximal to a supply line that fluidly connects to a waterway. As such, input end 608A can define a wider enclosure. Output end 608B, which is configured to be distal to a supply line, can be proximal to where liquid 601 will be dispersed. For example, in a faucet 650, tube 602 may cover a distal spout of the faucet 650, input end 608A would be located proximal to the sink 636, and output end 608B may be positioned proximal to the nozzle where water 601 is ultimately dispensed. A small notch 604 can be formed near input end 608A such that condensation or other liquid retained within sleeve 606 can drain out.

FIGS. 7-1 and 7-2 illustrate a seventh example sink system 710 (e.g., sink system 110 of FIGS. 1-1 and 1-2) that can be implemented within smart-kitchen environment 100 of FIG. 1-1. In particular, sink system 710 of FIGS. 7-1 and 7-2 includes an enhanced-accessibility system 700 enabling a diverse array of users to access and use sink system 710. For instance, accessibility system 700 can include a plurality of sensors, microphones, and other features to enhance accessibility to users of all abilities.

As shown in FIG. 7-1, accessibility system 700 of sink system 710 includes an accessible faucet 750 coupled to a mounting plate 724. Mounting plate 724 is adapted to stand on the rim 706 of a sink 736 or on a countertop 740 (e.g., countertop 140 of FIG. 1-1) surrounding an under-the-counter mounted sink 736. Other examples of system 700 do not include a mounting plate 724, and instead, the bottom of the faucet 750 is mounted directly to the surface 706 adjacent the basin 716 (e.g., basin 116 of FIG. 1-1) the sink 736.

Faucet 750 extends upward from mounting plate 724. In certain examples, faucet 750 has a first end (e.g., a proximal end, from the perspective of the flow-path of water 701) with a generally vertical, tubular base 728 projecting upward from the mounting plate 724 and connecting into a tubular, arched portion 730 that curves upward and outward over the sink basin 716 and then continues curving downward terminating at a second end that has a distal water spout 726 and/or sprayhead 702 from which a stream of water 701 flows when faucet 750 is activated.

Waterspout 726 is actuated by a control lever 742 (e.g., faucet handle 540 of FIG. 5-1) that can be actuated to initiate a stream of water 701 to flow through and disperse from spout 726. Control lever 742 can also be leveraged to dictate the temperature of the water (e.g., if the control lever 742, is turned to the right, hot water disperses from spout 726, and if turned to the left, then cold water disperses from spout 726, etc.). Control lever 742 can be integrally coupled to a braille plate 704 that includes standard Braille lettering to indicate actuation and dictation of temperature based on handling of the control lever 742. Persons skilled in the art shall recognize that sink 736 may have other types of faucets 750 that project upward and forward from a base section 728 to a waterspout 726. Faucet 750 may have a pull-out-style sprayhead 702 attached to a hose 724 (e.g., hose 324) that extends through spout 726.

FIG. 7-2 illustrates an example of accessibility trackpad 714 (e.g., trackpad 514) that may be integrated within base plate 724 and/or other components of sink system 710 of FIG. 7-1. Trackpad 714 includes at least one sensor 722, one or more processors 746, and a memory 712 storing programming instructions configured to be executed by the one or more processors 746.

Accessibility trackpad 714 can include a plurality of sensors 722 configured to be mounted on faucet 750 and control lever 742. Sensors 722 can include capacitive sensors, proximity sensors, optical sensors, or any other sensors configured to detect user interaction with sink system 710. Sensors 722 are configured to detect human touch, particularly whether human touch is detected on braille plate 704. Once a sensor 722 detects significant human touch (that is, identifiable human touch detected for at least a threshold time duration), sensor 722 generates an electrical signal to communicate to a processor unit 746. Processor unit 746 can be remote from accessibility trackpad 714, while having capability to receive communication signals from sensor(s) 722; such examples enable processor unit 746 to function securely away from faucet 750 to avoid water damage. Alternatively, processor unit 746 can be incorporated within accessibility trackpad 714 such that processor unit 746 is out of the way of basin 716 of sink 736 and faucet 750.

Processor 746 can monitor sensor 722 for output communication signals. If processor 746 receives or detects an output signal from sensor 722, then processor 746 commences with operation by executing appropriate instructions saved to memory 712 based on the output signal and based on an operational state of sink system 710 (e.g., whether faucet 750 has been actuated or has not yet been actuated, the orientation of control lever 742, etc.). For example, these instructions can include executable instructions for processor 746 to issue audible commands through a speaker 708 (e.g., speaker 226 of FIG. 2), wherein speaker 708 can be remote from accessibility trackpad 714 while having capability to issue audible noise in a frequency range detectable by a human user. Alternatively, speaker 708 can be incorporated within accessibility trackpad 714 such that speaker 708 is out of the way of basin 716 of sink 736 and faucet 750.

Programming instructions can include audible commands that inform the user whether faucet 750 has been actuated via control lever 742 to dispense water 701 via spout 726 and, if actuated, announce the water temperature, pressure, flowrate, or any other relevant information to enhance accessibility of sink system 710, e.g., for the visually impaired.

FIGS. 8-1 through 8-3 illustrate an eighth example sink system 810 that can be incorporated within kitchen environment 100 of FIG. 1-1. For instance, FIG. 8-1 is a front view of sink system 810, and FIG. 8-2 is a perspective view of faucet 850 of FIG. 8-1. In general, sink system 810 includes a self-cleaning system 800, as detailed further below.

Sink system 810 includes a sink module 836. In some examples, sink module 836 can be integrated with, and removable from, countertop 804; contained within or implemented into a continuous base (e.g., acting as a ground support); or integrated with a standalone structure.

Sink module 836 is configured to receive a fluid (e.g., tap water, ozonated water, soapy water, or another liquid) from faucet 850. Faucet 850 may be positioned proximate to, and on top of, sink module 836. By way of example, faucet 850 may be actuated between an “off” configuration and an “on” configuration in which faucet 850 dispenses the fluid.

Faucet 850 may be actuated between the “on” and “off” configurations by a handle 808. Additionally or alternatively, faucet 850 may be actuated between the “on” and “off” configurations by interfacing with a touchless sensor that may be located at location along sink system 810. Additionally or alternatively, faucet 850 may be actuated between the “on” and “off” configurations using voice recognition and control. Additionally or alternatively, faucet 850 may be actuated between the “on” and “off” configurations by interfacing with an app or remote control that additionally provides water-temperature control. Handle 808 may be positioned proximate base 806 of faucet 850, wherein faucet handle 808 is rotatable relative to faucet 850. The user may apply a force onto handle 808, e.g., in a direction distal to faucet 850, to actuate faucet 850 between the “on” and “off” configurations, and anywhere therebetween, to control fluid pressure from faucet 850.

Additionally or alternatively, the user may apply a rotational force onto handle 808, e.g., in a direction substantially parallel to faucet 850, to change the temperature of the material being dispensed by faucet 850. By way of example, the user may rotate handle 808 proximal to a backsplash 812 or the position behind faucet 850 to increase the temperature of the fluid dispensed by faucet 850.

In some examples, faucet 850 of self-cleaning system 800 may be actuated into a “clean” mode, such that faucet 850 automatically sprays the entirety of sink basin 816. In some examples, faucet 850 may be actuated into the “clean” mode via a handle 814 that is separate from handle 808. Additionally or alternatively, faucet 850 may be actuated into the “clean” mode by interfacing with a touchless sensor located at any suitable location along sink system 810. Additionally or alternatively, faucet 850 may be actuated into the “clean” mode using voice recognition and control. Additionally or alternatively, faucet 850 may be actuated into the “clean” mode by interfacing with an app or remote control that also provides water-temperature control over fluid 801. In some examples, once actuated, spout outlet 820 may rotate relative to faucet 850 about an automatic swivel 830, such that a dispensed cleaning fluid 801 sprays in multiple directions/angles to clean at least a majority of sink basin 816.

Sink system 810 includes one or more sensors 822 positioned within various components of sink system 810. Sensors 822 are configured to provide signal(s) to a communication interface to operate or actuate various components of sink system 810. For instance, sensors 822 may include a touchless sensor system having a sensor range 824 (FIG. 8-2). In some examples, the user may place or wave a portion of their body (e.g., a hand) near the sensor within the sensor range 824 to actuate various components of sink system 810. In some examples, a first sensor housing 826 is disposed within faucet 850, e.g., proximate a top of faucet 850.

In some examples, one or more of sensors 822 (e.g., positioned along sink module 836, faucet 850, or faucet handle 808) are configured to enable additional controls for faucet 850. For instance, faucet 850 may be turned on and off, temperature of water 801 flowing out of faucet 850 may be controlled, and/or the “clean” mode may be activated, via one or more of sensors 822. For instance, faucet 850 includes a fluid outlet 820 (or “spout 820”) that dispenses a flow of fluid 801 (e.g., water) out of faucet 850. As shown in FIG. 8-2, sensor 822D may be conveniently positioned within faucet 850, proximate to spout 820 to provide access to the user. In other examples, sensor 822D is positioned distal to spout 820. Sensor 820 may be configured to sense, within the sensor range (or “field of view”) 824, a hand of the user. For instance, when the user holds or waves their hand through sensor range 824, a signal generated by sensor 822D causes faucet 850 to convert between the “on” and “off” configurations. Additionally or alternatively, sensor 822D may be actuated or activated such to change the temperature of fluid 801 dispensed from spout 820.

In some examples, faucet 850 may be actuated, e.g., by any of a plurality of actuation modules positioned along sink module 836, faucet 850, or faucet handle 808, into an “automatic clean” mode, such that faucet 850 dispenses fluid 801. While in the “automatic clean” mode, faucet 850 dispenses fluid 801 (e.g., tap/ozonated/soapy water) so as to thoroughly spray the internal edges, sides, and base of sink basin 816. In some examples, faucet 850 includes a mechanism (e.g., tubing integrated within faucet 850) that, upon activation of the “automatic clean” mode, outputs an additional substance, such as a cleaning material (e.g., soap). In some examples, the cleaning material and fluid 801 are simultaneously dispensed from faucet 850 to clean sink basin 816.

In some examples, faucet 850 includes a rotary mechanism, such as an automatic swivel adapter or swivel joint 830, coupled to spout 820. Once activated into the “automatic clean” mode, fluid 801 flows through spout 820 in a way that causes spout 820 to rotate about automatic swivel 830. Spout 820 may then follow a preprogrammed procedure to thoroughly spray at least certain portions of sink basin 816.

In some examples, spout 820 swivels side-to-side to provide a continuous spray of fluid 801 from the left side of sink 836 to the right side (or vice versa). Additionally or alternatively, spout 820 swivels forward and backward, which provides a continuous spray of fluid 801 from the front side of sink 836 to the back side (or vice versa). Additionally or alternatively, the base of sink basin 816 also receives a spray of fluid 801 during the rotational movement of automatic swivel 830 (e.g., during forward, backward, and side-to-side rotation).

In some examples, automatic swivel 830 enables a complete 3600 of rotational motion, such that forward, backward, and side-to-side sprays of fluid 801 may be realized in a single cycle of the “automatic clean” mode. Thus, the entirety of sink basin 816 is sprayed with fluid 801 to rinse out leftover food, stains, dirt, dust, etc. In this way, the “automatic clean” mode of cleaning system 800 (particularly the rotary motion of faucet 850 via automatic swivel 830) enables an automatic cleaning or rinsing-out feature for sink system 810. In some examples in which dishes, bowls, glassware, etc., are disposed within sink basin 816, the “automatic clean” mode may be activated to rinse basin 816 as well as the objects residing therein.

In some examples, spout 820 enables a variety of different spray configurations and/or flow functions (e.g., shower, stream, mist, spray, flat, jet, etc.) of fluid 801 for selection by a user. For instance, a button, sensors 822, etc., may be interchangeably positioned and activated such that one or more spray configurations and/or functions of fluid 801 are dispensed via spout 820.

In some examples, a particular spray configuration or function may be preprogrammed as a default setting for the “automatic clean” mode of sink system 810, and may be adjustable (e.g., via a mobile app) according to user preference. For instance, a maximum fluid pressure and/or temperature may be set for the “automatic clean” mode.

In some examples, a user may pre-program a “first” automatic-clean mode, e.g., to address relatively larger messes in sink basin 816. For instance, the “first” automatic-clean mode can include a set of parameters such as a maximum water temperature and a “strong” water spray with a maximum fluid pressure. Additionally or alternatively, the user may preprogram a “second” automatic-clean mode for relatively smaller messes. For instance, the “second” clean mode can be configured to provide sink basin 816 with a “refreshing” rinse with a relatively lower water temperature and a “shower” or “mist” of water 801 with a below-maximum fluid pressure.

In some examples, sink system 810 includes a controller, such as a solenoid assembly 828 (FIG. 8-1). Solenoid assembly 828 may be coupled to other features that enable receipt of sensor signals from at least one of sensors 822. During operation, at least one of sensors 822 within sensor housing 826 sends a signal to solenoid assembly 828 in response to detecting, e.g., a hand of user in the field-of-view 824 of sensor 822D (FIG. 8-2). Solenoid assembly 828 consequently causes material passageways therein to open, allowing hot water, cold water, or a combination thereof, to flow toward spout 820.

In some examples, sink system 810 includes a plurality of solenoid assemblies 828A-828C, each controlled by a respective sensor 822A-822C. For example, a first sensor 822A may be operably coupled to a first solenoid assembly 828A. First solenoid assembly 828A may be configured to open a hot-water pathway when first sensor 822A interfaces with (e.g., detects) a portion of the user's body. In another example, a second sensor 822B may be operably coupled to a second solenoid assembly 828B. Second solenoid assembly 828B may be configured to open a cold-water pathway when second sensor 822B detects a portion of the user's body. In another example, a third sensor 822C may be operably coupled to a third solenoid assembly 828C. Third solenoid assembly 828C may be configured to actuate faucet 850 between the “on” and the “off” configurations when sensor 822C detects the user's body. In other examples, solenoid assemblies 828 may be configured to actuate any suitable component of sink system 810.

FIG. 8-3 illustrates an example controller 840 (e.g., control module, remote control, control interface, etc.) of sink system 810 of FIGS. 8-1 and 8-2. Controller 840 is configured to control (e.g., touchlessly actuate) any or all of faucet 850, sensors 822, and/or the “automatic clean” mode(s) of sink system 810. Controller 840 includes a wireless communication device 842 (or “control communication 842”), a power supply 844, processing logic 846, and a memory 848. In general, controller 840 communicates with solenoid assemblies 828 of sink system 810.

For instance, controller 840 may transmit, via control communication 842, instructions to solenoid assemblies 828 to open/close a fluid pathway and/or activate/deactivate a pre-programmed motion of spout swivel 830. Solenoid assemblies 828 may receive sensor signals and relay the signals to open/close the fluid pathway, activate/deactivate spout swivel 830, and/or enable/disable the “automatic clean” mode of sink system 810.

Power supply 844 powers controller 840. Power supply 844 can include disposable batteries (e.g., alkaline, lithium, zinc-air, etc.) or rechargeable batteries (lithium ion, nickel-cadmium, etc.), or may plug into an outlet to receive either AC or DC current. In some examples, controller 840 is wirelessly powered, e.g., via inductive charging. For example, controller 840 may be mounted to a wall, behind which a wireless charger (e.g., copper coil, magnetic loop antenna, etc.) is positioned. The wireless charger may then interface with power supply 844 to wirelessly charge controller 840.

Processing logic 846 is configured to send signals to, and receive signals from, control communication 842. Processing logic 846 is operably coupled to memory 848, which can store, e.g., instructions for responding to different sensor signals. Memory 848 may be a non-transitory memory that includes programming instructions stored thereon. In some examples, the instructions are added to memory 848 during manufacturing (e.g., as firmware), and are therefore inaccessible to the end user of sink system 810. For example, memory 848 may store instructions to cause solenoid assemblies 828 to open/close hot/cold fluid pathways. In some examples, memory 848 stores instructions to cause spout swivel 830 to move during the automatic-clean mode, e.g., defining pre-programmed spray patterns, fluid pathways, user preferences, spray duration, fluid temperatures, etc. In some examples, memory 848 may be structured such that a user is unable to change how solenoid assemblies 828 respond to receiving instructions from controller 840. In other examples, memory 848 may be structured such that a user is able to change how solenoid assemblies 828 respond to receiving instructions from controller 840.

As described above, sensors 822 are configured to provide signal(s) to controller 840 (FIG. 8-3) to operate or actuate various components of sink system 810. Sensors 822 can include any suitable type of sensor configured to sense activity around faucet 850. For example, sensor(s) 822 can be or can include proximity sensors; facial-landmark sensors/detectors (e.g., to identify a mouth, eyebrows, nose, and/or any facial landmark of a user); motion sensors (e.g., to sense head movement and/or eye movement and/or a particular gesture, such as “yes”/“no” head movements); eye-tracking/eye-gaze sensors; light sensors; touch/tactile sensors; cameras; audio sensors (e.g., a microphone) for voice recognition; etc.

In some examples of sink system 810, sensors 822 can sense operational and/or physical parameters such as water temperature, flow rate, fluid pressure, etc. For instance, sink system 810 can use data from sensors 822 in a facial-recognition algorithm, such that sink system 810 can distinguish between different users.

In some such examples, sink system 810 can provide a customizable user experience (“UX”) for each user that includes personalized temperature settings, commands, flow rates, etc., based on user identification. For instance, as a particular user approaches sink system 810, the system identifies the user and, via controller 840, configures the user's preferred settings, such as automatically turning on faucet 850 with a preferred water temperature, pressure, spray pattern, etc.

In some examples, sink system 810 may identify a minor user (e.g., as pre-programmed by an adult user, or based on certain facial characteristics), and automatically reduce the maximum temperature and/or pressure of water 801. In some examples, controller 840 monitors the usage of sink system 810 for each user and stores the information on the memory 848 for subsequent display and/or analysis.

In some examples, sink system 810 may be configured to recognize certain objects based on sensor data, such as a particular type of container approaching or present within, sink basin 816, and in response, automatically turn on faucet 850.

In some examples, one or more preset buttons 832 (FIG. 8-2) may be integrated into faucet 850, around sink module 836, into backsplash 812, etc., that cause spout 820 to output a predetermined volume of fluid 801 at a predetermined temperature. For instance, a “glass of water” button 832 may cause spout 820 to output 8 oz. of water at the coldest temperature setting.

In some examples, preset button(s) 832 (or other suitable user-input mechanism) may be associated with a particular user of sink system 810. For instance, one preset button may be associated with the settings of a first user, and a second preset button may be associated with the settings of a second user, wherein the settings indicate particular preconfigured water temperatures, water pressures, dispersal durations, fluid quantities, etc.

In some examples, sink 836 includes a microphone 834 positioned within any suitable component of sink system 810. Microphone 834 may be communicatively coupled to controller 840 to receive voice commands for additional control over various functions of sink system 810. For instance, voice commands may include “summons” commands, “request” commands, device-function commands, and/or “skill” commands.

A voice command may include a predetermined syntax or structure to facilitate recognition by sink system 810, such as: ([summons], [device-function command]). Voice commands may additionally or alternatively include “natural” spoken words or phrases. In some examples, preset commands may be uttered by the user that enable preset functionalities of sink system 810. For example, a user may utter “fill baby bottle,” which causes spout 820 of faucet 850 to dispense 8 oz. of fluid 801 at a temperature of 105° Fahrenheit. In other examples, a user may utter “User One,” which causes spout 820 to output fluid 801 according to user-designated settings associated with one of preset buttons 832, as described above. In further examples, “temp. max.” and “temp. min.” may cause faucet 850 to dispense water 801 at a maximum or minimum temperature, respectively. In other examples, a user may utter “on,” “off,” “activate,” “deactivate,” or the like, which, as indicated, may turn faucet 850 on or off.

In some examples, controller 840 can communicatively couple to one or more wireless devices (e.g., smart device, remote control, etc.) to further control components of sink system 810. In some such examples, a mobile application (or “app”) may include a user interface (“UI”) or graphical user interface (“GUI”) on a mobile device, such as a smartphone, tablet, laptop, or “wearable” device. In some such examples, the app can accept user input enabling control over, and customization of, the various features of sink system 810 as described and illustrated herein.

In some examples, the app's UI provides an option for customizing the executions of preset buttons 832. For example, a first user may change their preferences (e.g., water pressure, water temperature, fluid volume, etc.) upon actuation of their associated preset button 832 or in response to voice-activation for those particular setting(s). In some examples, the UI is configured to customize temperature settings for faucet 850 such that a user can adjust the temperature of dispensed water 801 by manually increasing or decreasing a displayed number value, dragging/moving a slider bar (whether horizontally or vertically), or any other similar digital user-input mechanism.

FIGS. 9-1 and 9-2 illustrate a ninth example sink system 910 that can be incorporated within kitchen environment 100 of FIG. 1-1. In particular, FIG. 9-1 is a front view of sink system 910, and FIG. 9-2 is a side view of sink 936 of sink system 910. Sink system 910 is an example of sink system 810 of FIGS. 8-1 and 8-2 (e.g., having automatic-cleaning functionality), apart from any differences explicitly noted herein.

Sink system 910 includes an expanding-spray system 900. Expanding-spray system 900 includes one or more sensors 922A-922C (collectively, “sensors 922”), which may be positioned within sensor housings at various locations within components of sink system 910. By way of example, expanding-spray system 900 may include a “touchless” sensor system defining a sensor range (or “field of view”) 926, wherein the range 926 of the one or more sensors 922 cover the entirety, or at least the majority, of basin 916 of sink module 936. In the example illustrated in FIG. 9-2, first sensor 922A is disposed within faucet 950, e.g., proximate to the base of faucet 950. Additional or alternative sensors 922B, 922C may be positioned elsewhere around sink module 936.

In some examples, expanding-spray system 900 may use sensors 922 to detect and differentiate user gestures across all three spatial dimensions (e.g., “3-D”). For instance, sensors 922 may include optical sensors configured to detect an object's height within their fields-of-view 926, as well as any movement of the object and/or the speed thereof. As described herein, the object may include a user's hand(s) while making or performing a particular gesture. A controller (e.g., controller 840 of FIG. 8-3) of system 900 can distinguish between data from different sensors 922 to determine movement and/or speed of the hand gesture.

In an illustrative example of expanding-spray system 900, after turning on faucet 950, a user may position their hands together and then “expand” them apart (e.g., while remaining within view 926 of sensors 922). In response, expanding-spray system 900 proportionally expands a spray-width of water 901 dispensed from faucet 950. In some such examples, water 901 dispensed from faucet 950 can also transition from a “jet” stream (or “regular” stream) into a “shower” stream or “mist” spray.

Additionally or alternatively, the user can move both hands together while within view 926 of sensors 922. In response, system 910 proportionally condenses the spray width of water 901. In some such examples, water 901 dispensed from faucet 950 may transition back from a “shower” stream or “mist” spray into a “jet” stream (or “regular” stream). Thus, while within sensor range 926, a user may exercise personalized gestural control over the width and/or pressure of water 901 dispensed from faucet 950.

In some examples, the user may execute additional or alternative gestures to change the output from faucet 950, including turning the water flow on or off, changing the flow rate of the water, adjusting the temperature, changing the dispensed water 901 between filtered water and unfiltered water, metering a present amount of water, and selecting a discrete fill volume. For instance, an “up” or “upward” gesture may turn the water flow on, and a “down” or “downward” gesture down may turn the water flow off. In other examples, an “up” or “upward” gesture may increase water temperature, and a “down” or “downward” gesture may decrease water temperature. In some examples, a “forward” gesture may increase the flow rate, and a “backward” gesture back may decrease the flow rate. Other gestures and associated functions of sink system 910 are contemplated.

FIG. 10-1 is a perspective overhead/front view of a tenth example sink system 1010 that may be incorporated within smart-kitchen environment 100 of FIG. 1-1. Sink system 1010 may be an example of sink system 810 of FIG. 8-1 (e.g., having automatic-cleaning functionality), sink system 910 of FIG. 9-1 (e.g., having expanding-spray functionality), or any other sink systems described herein, apart from any differences explicitly noted. In particular, sink system 1010 includes a “welcome” system 1000, as detailed further below.

Sink system 1010 includes a sink module 1036. In some examples, sink module 1036 may be integrated with, and removable from, countertop 1004, which may contain or may be implemented into a continuous base (e.g., acting as a ground support) or integrated with its own standalone structure. Sink module 1036 may be configured to receive a fluid (e.g., water, liquid, etc.) from a faucet 1050. Faucet 1050 may be positioned proximate to (e.g., over) basin 1016 of sink module 1036. Faucet 1050 may be actuated between an “off” configuration and an “on” in which faucet 1050 dispenses fluid. Faucet 1050 may be actuated between the “on” and “off” configurations via a handle or knobs 1008.

In some examples, faucet 1050 may be actuated between the “on” and “off” configurations by interfacing with a touchless sensor disposed at suitable location along sink system 1010. Additionally or alternatively, faucet 1050 may be actuated between the “on” and “off” configurations using voice recognition and control. Additionally or alternatively, faucet 1050 may be actuated between the “on” and “off” configurations by interfacing with a mobile application (“app”) or remote control that further provides water-temperature control (or other features described herein). Knobs 1008 may be positioned proximate to the base of faucet 1050, and are rotatable to control either a “hot” material flow or a “cold” water flow from faucet 1050.

In some examples, sink system 1010 includes a motion sensor 1022, e.g., integrated into a front wall of sink module 1036. Sensor 1022 may define a range or field-of-view directed outward from sink module 1036 in order to detect a user approaching or leaving sink system 1010. Although FIG. 10-1 illustrates a single sensor 1022 incorporated at the front of sink 1036, in other examples, a different number of sensors may be positioned at different locations around sink system 1010, such as on top of the front of sink 1036, at the base of sink system 1010, on or above backsplash 1012, along countertop 1004, on the wall behind faucet 1050, etc. Although not explicitly described, numerous other sensors and sensor locations are possible and contemplated, such that, as a user approaches sink system 1010, the sensors send signals for processing. In response, welcome system 1000 triggers a “welcome” event, as detailed further below.

Sensor 1022 outputs sensor signal(s) indicating the incoming presence (or the absence) of users approaching sink system 1010 and, optionally, transmitting the signals to a controller 1040 (e.g., controller 840 of FIG. 8-3) to trigger “welcome” event(s). In some examples, controller 1040 may include, or may be coupled to, a microphone 1034 (e.g., microphone 834 of FIG. 8-2), one or more speakers 1026 (e.g., speaker 226 of FIG. 2), one or more screen-type displays 1024 (e.g., display 224 or display 524, such as a light-emitting diode (LED) television display, a touchscreen device, etc.), and one or more light features 1002 (e.g., a plurality of LEDs, lightbulbs/light fixtures, etc.).

In some examples, light features 1002 are integrated within sink system 1010. Although light features 1002 are illustrated as being mounted to the backsplash 1012 and the base of the sink system 1010, additional/alternative light features and respective locations are contemplated. For instance, light features 1002 may be positioned at the base of sink system 1010, within basin 1016 of sink module 1036, along the countertop 1004, etc.

FIG. 10-2 is a conceptual block diagram of controller 1040 (e.g., control module, remote control, control interface) of welcome system 1000 of FIG. 10-1. Controller 1040 may be a stand-alone device or may be integrated within one of the devices of sink system 1010, for example, within display 1024. Controller 1040 is configured to wirelessly/touchlessly control faucet 1050, sensor(s) 1022, and, in particular, the triggering and execution of “welcome” events of system 1000, as described herein. As shown in FIG. 10-2, controller 1040 includes a wireless communication module 1042 (or “control communication 1042,” e.g., control communication 842 of FIG. 8-3), a power supply 1044 (e.g., power supply 844 of FIG. 8-3), processing logic 1046 (e.g., logic 846 of FIG. 8-3), and a memory 1048 (e.g., memory 848 of FIG. 8-3).

In general, controller 1040 communicates with components of sink system 1010, such as microphone 1034, speaker(s) 1026, display(s) 1024, and/or light features 1002. For instance, for execution of a “welcome” event of system 1000, controller 1040 may transmit, via control communication 1042, instructions to open or close a fluid pathway of sink 1036, and activate/deactivate speakers 1026 and/or display 1024. That is, in response to sensor(s) 1022 detecting an approaching user, system 1000 triggers a “welcome” event by activating one or more components of sink system 1010.

Power supply 1044 powers controller 1040. Power supply 1044 may include disposable batteries (e.g., alkaline, lithium, zinc-air, etc.) or rechargeable batteries (lithium ion, nickel-cadmium, etc.). Controller 1040 may plug into an outlet and receive either AC or DC current. In some examples, controller 1040 may be wirelessly powered via inductive charging. For example, controller 1040 may be mounted to a wall, behind which a wireless charger (e.g., copper coil, magnetic loop antenna, etc.) is positioned. The wireless charger behind the wall may interface with power supply 1044 to charge controller 1040.

Processing logic 1046 may be configured to send and receive signals via control communication 1042. Processing logic 1046 may be operably coupled to memory 1048, which stores programming instructions for, e.g., how to respond to various sensor signals. Memory 1048 may be a non-transitory memory that includes programming instructions stored thereon. In some examples, the instructions are added to memory 1048 during manufacturing (e.g., as firmware), and are therefore inaccessible to the intended end user of sink system 1010 and welcome system 1000. For example, memory 1048 may store instructions governing any or all of: how speakers 1026 output sound, what content is to be displayed on display 1024, and the illumination of light features 1002 during execution of “welcome” events of system 1000. As one particular example, memory 1048 can store instructions for determining the audio volume of speakers 1026 during a “welcome” event.

FIG. 10-3 is a flowchart 1060 illustrating an example operation of “welcome” system 1000 of sink system 1010 of FIGS. 10-1 and 10-2. At step 1062, welcome system 1000 is in a default “idle” state, awaiting a user. At step 1064, a user approaches sink system 1010, triggering motion sensor(s) 1022 to automatically send signal(s) to controller 1040 indicating the presence or incoming presence of the user. In response, at step 1066, system 1000 triggers a “welcome” event by actuating a predetermined configuration of audiovisual experiences to greet the user. At step 1068 (by which time the user may or may not have departed from the vicinity of sink system 1010), system 1000 completes the “welcome” event and returns to the default “idle” state (step 1062).

As described herein, a “welcome” event of system 1000 is an occurrence in which one or more of the components of sink system 1010 are activated and/or deactivated (as appropriate), in response to a user approaching sink system 1010.

In some examples, light features 1002 of sink system 1010, such as lightbulbs, LEDs, provide at least partial illumination of sink system 1010 during a “welcome” event. In some examples, light features 1002 are selectively activated and deactivated during execution of “welcome” events. Selective activation may be based on the presence of the user and may be preprogramed for execution by controller 1040. For instance, depending on a time of day, controller 1040 may be pre-programmed to activate one or more light features 1002. In some examples, controller 1040 is pre-programmed to automatically activate light features 1002 at the base of sink system 1010 to provide a “welcoming” light, e.g., to illuminate a walkway for the user (e.g., as a nightlight in the evenings, or during a lack of adequate light in the vicinity of sink system 1010).

In some examples, the controller 1040 is pre-programmed to automatically activate light features 1002 near faucet 1050 in anticipation of use. In some examples, controller 1040 may be pre-programmed to automatically activate and deactivate light features 1002 according to “flashing” patterns, e.g., either multiple/all lights 1002 simultaneously, or alternating between individual lights 1002. These “flashing” patterns may be associated with other features, including synchronizing actuation of light features 1002 with sounds emitted by speakers 1026 and/or imagery depicted on display 1024, as detailed further below.

In some examples, light features 1002 include “dimming” functionality, such that, upon triggering a “welcome” event, a less-than-maximum illumination may be executed. Although not explicitly described herein, numerous other light features and associated activations are possible and contemplated.

In some examples, sink system 1010 includes one or more display(s) 1024 (FIG. 10-1).

In some such examples, display 1024 may be selectively activated during “welcome” events of welcome system 1000. In some examples, controller 1040 may be pre-programmed to automatically activate and deactivate display 1024 based on pre-selected user preferences.

In some examples, one or more speakers 1026 may be incorporated into sink system 1010. In some such examples, speakers 1026 may be selectively activated and deactivated during execution of “welcome” events of welcome system 1000. Selective activation may be based on the presence of the user and may be pre-programmed for execution by controller 1040.

In some examples, depending on the time of day, controller 1040 may be pre-programmed to provide a greeting message once the one or more sensors 1022 indicate an incoming user and controller 1040 initializes a “welcome” event. For instance, controller 1040 may be pre-programmed to cause speakers 1026 to emit an audible “good morning” greeting message to the user, e.g., during morning hours. In some examples, controller 1040 is pre-programmed to cause speakers 1026 to emit an audible “good evening” greeting message to the user, e.g., during evening hours.

In some examples, controller 1040 may be pre-programmed to inform the user of the current time, weather, or any other information, based on preferences of the user. In some examples, controller 1040 is pre-programmed to play music, such as a pre-programmed radio station, a predetermined playlist, an audible book, or any other form of preferred audio. In some examples, speakers 1026 may be communicatively coupled such that any audio associated with imagery presented on display 1024 is emitted via speakers 1026. In some examples, the audio volume of the speakers 1026 is configured based on, for instance, user preferences, a particular type or category of welcome event, or which components of sink system 1010 are being activated. In some examples, speakers 1026 may output a lower audio volume in the mornings (e.g., creating a softer, more soothing environment), and a higher volume during the afternoon or evenings. Although not explicitly described herein, numerous other sounds, audio volumes, and corresponding presentations to the user are possible and contemplated.

In some examples, faucet 1050 is selectively activated during “welcome” events of welcome system 1000. In some such examples, controller 1040 is pre-programmed to automatically activate and deactivate display 1024 based on the preferences of the user. In some examples, faucet 1050 may be pre-programmed to automatically dispense fluid (e.g., water) at a predetermined (e.g., user-customized) temperature. In some examples, faucet 1050 is pre-programmed to automatically output material with a predetermined spray type (e.g., shower, jet, mist, etc.). In some examples, faucet 1050 is pre-programmed to automatically output a predetermined volume of material (e.g., 8 ounces of water to fill up a glass, as preferred by a particular user). Although not explicitly described herein, numerous other fluid-dispensing configurations and corresponding presentations to the user are possible and contemplated.

In some examples, depending on preferences of the user, a time duration of a “welcome” event of system 1000 may vary. In some examples, a “welcome” event of welcome system 1000 includes components of sink system 1010 briefly being activated for a predetermined period of time, e.g., to provide the approaching user with a general greeting. For instance, speakers 1026 can broadcast a brief “good morning” message, light features 1002 activate/illuminate, and faucet 1050 dispenses a predetermined volume of fluid at a predetermined temperature.

Once the predetermined duration of time expires, welcome system 1000 can automatically deactivate the activated components of sink system 1010. Additionally or alternatively, activated components of sink system 1010 may be automatically deactivated once sensors 1022 no longer detect the presence of the user (e.g., in response to the user departing from sink system 1010).

Sink system 1010 of FIG. 10-1 (or other sink systems of smart-kitchen environment 100 described herein), may integrate a variety of various components, such as speaker(s) 1026, display(s) 1024, light feature(s) 1002, etc., however, kitchen environment 100 is not so limiting. For instance, sink system 1010 can additionally or alternatively include one or more visual-projection systems 1070. In some such examples, visual-projection system 1070 may activated or incorporated either in addition to, or alternatively to, display 1024. In some examples, integrated visual-projection system 1070 enables a user to broadcast and project any type of multimedia onto a planar surface within sink system 1010. In some examples, visual-projection system 1070 may be wirelessly communicatively connected to other data-driven components of sink system 1010, e.g., to controller 1040. In some such examples, wireless communication is enabled via integration and compatibility with an application (via a smart device), a remote control (e.g., controller 1040), or voice activation. Accordingly, a user is able to watch TV, read recipes, follow an instructional internet video, stream movies, etc., via projection onto a preferred surface of kitchen environment 100. In some examples, physical buttons may be located on projection system 1070 or integrated into faucet 1050.

In some examples, visual-projection system 1070 may be functionally integrated with speakers 1026, such that corresponding audio from any multimedia projecting from visual-projection system 1070 may also be heard by the user. In some examples, light features 1002 can integrate or synchronize functionality with any visuals and/or audio projected via projection system 1070. For example, lights 1002 can automatically dim when a user activates projection system 1070 (e.g., thereby enhancing visibility of the visual projection).

In some examples, visual-projection system 1070 may be integrated into faucet 1050 itself. Visual-projection system 1070 may angled (e.g., relative to a vertical axis or gravitational orientation) such that it displays the projection on a vertical or horizontal surface, depending on the configuration of faucet 1050. For example, a projection of a desired form of multimedia may be projected onto backsplash 1012 of sink module 1036. In some examples, visual-projection system 1070 may be integrated into faucet 1050 such that visual-projection system 1070 projects on a wall 1072 behind faucet 1050, whether directly behind or at some alternative angle, so long as the projected imagery is visible to the user.

In some examples, faucet 1050 of sink system 1010 may be ceiling-mounted, such that it hangs vertically relative to sink module 1036. In some such examples, visual-projection system 1070 may be oriented downward, thus enabling projection of imagery into sink basin 1016 or another surface below faucet 1050. In some examples, visual-projection system 1070 may be oriented downward and at a slight angle such that the projection is displayed on the surface of countertop 1004. In examples in which faucet 1050 protrudes from backsplash 1012 or wall 1072, visual-projection system 1070 may be integrated into faucet 1050 and projected imagery may be displayed, e.g., similar to the example shown in FIG. 10-1.

In some examples, sink system 1010 (or any sink system of smart-kitchen environment 100 described herein) includes one or more features that are subject to a periodic subscription service. For instance, any or all of the components of sink system 1010 may be available for periodic replacement with interchangeable parts. For example, a user of sink system 1010 can subscribe to a monthly (or any suitable time period) service enabling the user to easily upgrade, service, change, replace, or otherwise implement new or other components within sink system 1010. For instance, the user could be enabled to replace their old sink module 1036, faucet 1050, varying knobs 1008, etc., and easily integrate the replacement components within their environment. That is, since design specifications of sink system 1010 would be stored within a user's digital profile as part of the subscription service, replacement components can be readily identified and incorporated into, e.g., sink base 1080 and/or countertop 1004, without requiring any additional measurements or alterations to other components of sink system 1010.

In some examples, the subscription for alternative components may include single components of the environment (e.g., an alternate faucet 1050, knobs 1008, sink basin 1016, etc.) or may include multiple components designed and assembled together. In some examples, the components may each be modular and adaptable (e.g., configured to be easily removed and replaced) without having to rework or reorganize any plumbing. In some examples, components may be readily attachable and detachable to other components of sink system 1010, easing integration and utilization of alternative components. This subscription service incentivizes users to implement components from a common manufacturer, which also enables affordable interchangeability, the ability to re-sell or return unwanted or old components, and an adaptable kitchen environment.

In some examples, a user may subscribe to a “rent to own” type of subscription service. For instance, the user may lease certain components, such as sink basin 1016 or faucet 1050, via contract with monthly (or any suitable time-dependent) subscription, enabling the user to rent and utilize those components until they want to upgrade to new models, or until the payment for the component is “complete.” In some examples, the subscription may allow, if desired, purchase of previously used components, or may automatically replace components upon expiration of the subscription period. In some examples, unwanted or unpaid-for components may be re-acquired, resold, or otherwise recycled, which keeps components out of landfills to reduce unnecessary waste.

FIG. 11-1 is a perspective view of an eleventh example sink system 1110 that may be implemented within smart-kitchen environment 100 of FIG. 1-1. In particular, sink system 1110 includes an integrated beverage system 1100, including a hydration-customization station 1102, an on-demand coffee station 1106, and/or a cocktail station 1108. In some examples, any or all of beverage stations 1102/1106/1108 may be discrete units placed on countertop 1104 adjacent sink module 1136. In other examples, any or all of beverage stations 1102/1106/1108 may be directly integrated into sink module 1136.

FIG. 11-2 is a conceptual block diagram of hydration-customization station 1102 of beverage system 1100 of FIG. 11-1. Hydration station 1102 may be compatible with (e.g., “retrofittable” to) existing sink systems, such as sink system 1110 of FIG. 11-1, or any other example sink system described throughout this disclosure.

In general, hydration-customization station 1102 is configured to dispense custom-infused water 1101A, e.g., infused with customizable flavors, additives, and other enhancements to satisfy a certain set of user-specified parameters and/or constraints. Hydration station 1102 may be used “on-demand,” allowing for automatic dispensing of flavors, proteins, vitamins, minerals, adaptogens, crushed ice, and other additions at the time of user request, rather than prepared in advance.

Example flavor additives include (but are not limited to): lemon, lime, orange, ginger, berry, fruit punch, cranberry, grape, and other related flavors. Other example enhancements include (but are not limited to): vitamins, minerals, adaptogens, caffeine, branched-chain amino acids (BCAAs), herbs, carbonation, chia seeds or Omega-3s, antioxidants, and pre- or pro-biotics. Example vitamin additives include (but are not limited to), customized blends of Vitamins A, B (e.g., B-12, thiamine, riboflavin, niacin, pantothenic acid, biotin, and B-6), C, D, E, and K. Example mineral additives include, but are not limited to, magnesium, zinc, calcium, potassium, folate, and iron.

Hydration-customization station 1102 can include a digital user interface (e.g., touchscreen) 1112 configured to display personalized suggestions for recommended additives (e.g., based on biometric data), while also allowing the user to maintain full freedom to adjust the blend or add other ingredients to it. In some examples, the user may further customize their water 1101A based on daily needs, in addition to the custom water blend created by hydration station 1102. This may include adding additional electrolytes, such as sodium, for hydration, caffeine for headaches, or ginger for other health and dietary needs. The user maintains full freedom to adjust the automated water blends, e.g., by adding any further additives they so choose.

In some examples, hydration station 1102 can interface with a designated (e.g., physically distinct) control unit (e.g., command center 1246 of FIG. 12) or a mobile computing device (e.g., smartphone 1270 of FIG. 12), to help generate customized beverage 1101A and enable visual and/or sound recognition for an enhanced user experience (“UX”). As a few illustrative examples, any or all of user interface 112, a separate control unit, or a mobile device can provide alerts to the user when hydration station 1102 needs to be serviced, needs to have new water added, or when hydration station 1102 prepares a new custom blend based on the user's preferences.

As detailed further in various illustrative examples below, a user selects a water type using digital user interface 1112. A water inlet 1114 optionally flows through a water filter or other treatment system 1116, such as a reverse-osmosis filtering system. User interface 1112 communicates with an additive unit 1118 via a controller 1120. One or more additive cartridges or canisters 1142 housed within additive unit 1118 are dispensed via solenoid valves (not shown) into the water outlet 1124 from optional treatment system 1116. Custom water blend 1101A is then dispensed via a fluid delivery unit, such as a faucet, as described throughout. Additionally or alternatively, a fluid other than (or in combination with) water, such as an alcohol, is fed to hydration station 1102. For example, as detailed further below with respect to FIG. 11-8, any or all of gin, vodka, rum, etc., can be flavored to produce a mixed cocktail.

FIG. 11-3 is a flowchart 1126 illustrating a general operation of hydration-customization station 1102 of FIG. 11-2, with subsequent flowcharts detailing more-specific examples thereof. At step 1126A, a user of hydration station 1102 selects, indicates, or otherwise specifies an intended purpose for water customization. Example intended purposes for water customization can include (but are not limited to): (1) satisfying flavor preferences of the user; (2) improving the user's health; (3) mimicking a flavor of tap water from a particular geographic region; and (4) producing water with particular properties, such as properties advantageous for cooking.

At step 1126B, the user further specifies any constraints, parameters, or other relevant information for the customized water. For instance, hydration station 1102 may prompt the user to input specific desired properties for infused water 1101A, along with any known information for assisting station 1102 to produce water 1101A with the desired properties.

At step 1126C, hydration station 1102 determines, based on the submitted information, a water-customization profile that approximately satisfies the user's constraints, parameters, and intended purpose.

At step 1126D, hydration station 1102 transmits, as appropriate, relevant information (e.g., the customization profile) and/or raw materials to the location of the end-user. For instance, a remote facility (e.g., water-testing laboratory) can digitally transmit data indicating the specifications of the custom-water profile directly to hydration station 1102. In other examples, the remote facility can compile and ship a customized additive canister 1142 to the end user, wherein the custom canister 1142 is configured to be installed within the local hydration station 1102 to produce the infused water 1101A.

At step 1126E, hydration station 1102 generates and dispenses customized water 1101A. For instance, the user may install a delivered custom-blend canister 1142 into hydration station 1102, and hydration station 1102 can mix tap water from faucet 1150 (FIG. 11-1) with material from canister 1142 to infuse and dispense water 1101A.

At step 1126F, when appropriate, the user can re-order more of the customized water 1101A, e.g., can re-order the necessary materials to produce more of water 1101A. For instance, additive canisters 1142 may be customizable and orderable via digital interface 1112 (or a smartphone application). This enables the user to adjust their blends 1142 via their personal cellphone, or to have a custom blend waiting for them when they arrive home. In other examples, the user can submit a new query directly into hydration station 1102 to cause hydration station 1102 to dispense a new custom water blend 1101A.

FIG. 11-4 is a flowchart 1128 illustrating an example operation of hydration station 1102 of FIG. 11-2 in which the user's intended purpose for the water customization is to satisfy the user's personal artificial-flavor preferences. At step 1128A, the user specifies any constraints, parameters, or other relevant information for the customized water 1101A. For instance, the user can submit data indicative of personal flavor preferences, such as by directly selecting individual artificial flavors displayed on user interface 1112, or via a mobile computing device (e.g., smartphone) that is communicatively coupled (e.g., “paired”) to hydration station 1102.

Additionally or alternatively, beverage system 1100 of FIG. 11-1 can provide the user with an online questionnaire to help system 1100 determine a custom flavor profile that the user would enjoy. Additionally or alternatively, users may also mail a water sample to a remote facility (e.g., a water-analysis laboratory) to have the water profile analyzed, including a breakdown of the minerals and other components that are naturally found in the water. This feature is particularly advantageous if the user dislikes their tap water, suspects some type of contamination, or otherwise wishes to alter the minerality of the tap water in their home.

At step 1128B, hydration station 1102 determines a water-customization profile that satisfies the constraints, parameters, and intended purpose. In examples in which the user has directly selected desired flavors, step 1128B is essentially negligible. In other examples, hydration station 1102 is configured to extrapolate a “recommended” flavor profile based on the user input (e.g., online questionnaire, etc.).

At step 1128C, beverage system 1100 transmits relevant information (e.g., the customization profile) and/or raw materials to the location of the end-user. For instance, a remote facility (e.g., water-testing laboratory) can digitally transmit data indicating the specifications of the custom-water profile directly to hydration station 1102. In other examples, the remote facility can compile and ship a custom canister 1142 to the end user, wherein the custom canister 1142 is configured to be installed within hydration station 1102 to produce the infused water 1101A.

At step 1128D, hydration station 1102 infuses and dispenses customized water 1101A. For instance, the user may install a delivered custom-blend canister 1142 into hydration station 1102, and hydration station 1102 can mix tap water from faucet 1150 with material from canister 1142 to infuse and dispense water 1101A.

FIG. 11-5 is a flowchart 1130 illustrating an example operation of hydration-customization station 1102 of FIG. 11-2 in which the intended purpose for the water customization is to improve the user's health. That is, hydration station 1102 may include infuse water with minerals, vitamins, caffeine, or flavors to create a special water blend based on health monitoring. For instance, users may select specific amounts of each addition, or have hydration station 1102 determine and infuse a unique blend based on user input.

At step 1130A, the user of hydration-customization station 1102 specifies any constraints, parameters, or other relevant information for the customized water. For instance, hydration station 1102 may be configured to actively and/or passively receive health data for a particular user. For instance, the user first may take a quiz or input specific health information to create a custom profile, or have their biometric data uploaded from a health-tracking device, such as a smartwatch, a heart-rate monitor, or a smartphone running a particular health application. In other examples, hydration station 1102 may receive health data input by a medical professional associated with the user, or by the user themself. The collected biometric data can include information about the user's medical condition(s), weight, current caloric intake, current energy expenditure, any ailments or injuries, and personal goals of the user (e.g., weight loss, weight gain, muscle gain, performance, etc.). At any time, the user can manually adjust these goals, and include updated information about progress or new needs. In some examples, beverage system 1100 can be configured to facilitate a urinalysis to help automatically identify the user's current health needs. Additionally or alternatively, hydration station 1102 can directly receive a doctor's recommendation for particular water additives for the user.

In some examples, hydration station 1102 may periodically collect the user's health data to dynamically adjust the user's water-additive profile (e.g., stored in a digital account for the user). This allows the user to track any changes in their health or dietary requirements. For instance, digital user interface 1112 can include a “share data” feature, allowing doctors or medical professionals to see changes in the user's health or consumption. This feature may be helpful for users who suffer from chronic conditions, or medical conditions that require careful monitoring of water intake, mineral intake, or other additions.

At step 1130B, hydration station 1102 determines a customization profile that satisfies the user's constraints, parameters, and intended purpose. For instance, in examples based on biometric data for the user, hydration station 1102 can be configured to generate a water-customization profile involving (but not limited to) particular quantities or ratios of four base ingredients: salt, magnesium, potassium, and calcium. Hydration station 1102 may determine other water additives to treat specific health conditions or needs, such as turmeric for inflammation, ginger for digestion, melatonin for sleep, or a variety of other additives.

At step 1130C, beverage system 1100 transmits information and/or raw materials to an end-user location. For instance, a remote facility (e.g., a water-testing laboratory) can digitally transmit data indicating the specifications of the custom-water profile directly to hydration station 1102. In other examples, the remote facility can compile and ship a custom canister 1142 to the end user, wherein the custom canister 1142 is configured to be installed within the local hydration station 1102 to produce the infused water 1101A.

At step 1130D, hydration station 1102 infuses and dispenses customized water 1101A. For instance, hydration station 1102 adds minerals and additives, according to the determined customization profile, to create a custom water blend based on the user's current health requirements and needs.

Additionally or alternatively, hydration station 1102 can be configured to re-mineralize reverse-osmosis water, e.g., without user input, to create a “basic” healthy-water blend, or a selected blend from among a plurality of pre-set healthy blends. The pre-set blends may include water with additional minerals added for health benefits, or, with certain minerals removed if a user has medical restrictions and/or already consumes too much of a certain mineral.

FIG. 11-6 is a flowchart 1132 illustrating an example operation of hydration station 1102 of FIG. 11-2 in which the intended purpose for the water customization is to mimic a flavor of tap water from a particular geographic region. The user may desire this feature, for example, to re-create the water from the geographic location where they grew up, or previously visited on vacation. For instance, a user may desire water that mimics the water in New York City, e.g., to make pizza dough that bakes and tastes similar to the pizza dough in New York City. In another example, a user may desire Vermont spring water to use for home brewing.

At step 1132A, the user of hydration-customization station 1102 specifies any additional constraints, parameters, or other relevant information for the customized water. In examples in which the tap-water flavor profile for a particular geographic region is already known, the user may simply select the preferred region from user interface 1112. In other examples, the user can mail a sample of the water from that region to a remote facility (e.g., a water-analysis laboratory).

At step 1132B, beverage system 1100 determines a customization profile that satisfies the constraints, parameters, and intended purpose. For instance, the remote facility can analyze the submitted water sample to identify a mineral profile of the water sample. In some examples, beverage system 1100 maintains a curated list of custom water profiles that may be used to mimic water from specific geographic locations. In some examples, users may share their customized tap-water profiles with others, allowing other users to re-create the custom blends from another user's profile. For example, a user may visit a friend or neighbor, enjoy the water in their home, and return to their own home to select that water blend from the neighbor's profile.

At step 1132C, beverage system 1100 transmits information and/or raw materials to an end-user location. For instance, the remote laboratory can digitally transmit the specifications of the custom-water profile directly to hydration station 1102, or alternatively, the known geographic profiles may already be stored in a memory of hydration station 1102.

At step 1132D, hydration station 1102 infuses and dispenses customized water 1101A. For instance, hydration station 1102 adds minerals and additives, according to the determined geographic profile, to mimic the tap water found at that geographic region.

Beverage system 1100 of FIG. 11-1 additionally or alternatively includes an on-demand coffee station 1106 configured to brew and dispense various coffee beverages 1101B. FIG. 11-7 is a conceptual block diagram illustrating some example components of coffee station 1106. Coffee station 1106 may be built into a wall or integrated into faucet 1150. In some examples, coffee station 1106 is an example of hydration station 1102 of FIG. 11-2. For instance, coffee station 1106 can include many or all of the same components as hydration station 1102, or equivalently, hydration station 1102 includes the functionality associated with coffee station 1106 detailed herein.

In the example shown in FIG. 11-7, coffee station 1106 includes a coffee/espresso bean receptacle 1134, a water reservoir 1136, a milk reservoir 1138, a flavor system 1140, a control unit 1120 having a visual-processing module 1144 and/or a sound-processing module 1146. In some examples, any or all of bean receptacle 1134, water tank 1136, milk tank 1138, and flavor system 1140 may be integrated into coffee station 1106. In other examples, any or all of these components may be separately housed, e.g., disposed within the wall behind coffee station 1106, or on either side of coffee station 1106. In examples in which coffee station 1106 is integrated into faucet 1150, any or all of these components may be located below faucet 1150 (i.e., under counter 1104), or built into a designated reservoir unit placed on counter 1104 adjacent to, or behind, faucet 1150.

In some examples, visual-processing module 1144 and sound-processing module 1146 enable a user to interact with coffee station 1106 without physically touching station 1106. For instance, a user may use voice commands with sound-processing module 1146, or gestures and proximity with visual-processing module 1144. Sensor 1122 interacts with visual-processing module 1144 and the sound-processing module 1146 to capture the user's visual and voice cues. In addition, coffee station 1106 may be programmed to store data regarding common usage, such as time of day the machine is used, preferred coffee temperature (i.e., extra hot, warm, etc.), whether the user prefers their coffee in a coffee cup or in a travel mug, and, if there is more than one user, coffee station 1106 may store information for each user.

In some examples, coffee station 1106 may be integrated into faucet 1150 of sink system 1110. In some such examples, control unit 1120 may be located adjacent to faucet 1150 to enable the user to interact with coffee station 1106. Similar to the example described above, beans 1134, water tank 1136, milk tank 1138, and flavor system 1140 may be located below or behind faucet 1150. Control unit 1120 can include touch-sensitive user interface 1112 (FIG. 11-2) enabling users to select from a variety of coffee-customization options. Control unit 1120 may be tied into other systems of smart-kitchen environment 100, allowing for synchronization of different kitchen features and functions.

Coffee station 1106 may be embedded in a kitchen wall, or integrated into faucet 1150. In some such examples, bean receptacle 1134, water tank 1136, milk tank 1138, and/or flavor system 1140 may be added into a wall mount for integration with coffee station 1106. A user may then interact with coffee station 1106 using visual module 1144 and/or sound module 1146 to select coffee preferences. In some examples, coffee station 1106 may include a “surprise me” feature in which coffee station 1106 suggests new coffee recipes and automatically makes the recipes for the user.

In some examples, a user may save their custom coffee recipes created by coffee station 1106. Coffee station 1106 may store data from the user's input for future use. Users may also create custom profiles to save and store their coffee recipes. In some examples, these profiles may be shared with others to access additional coffee recipes and creations. Coffee station 1106 may incorporate looseleaf tea to enable users to make recipes using tea rather than coffee or espresso beans. The tea may be stored in a compartment or canister, similar to how coffee or espresso beans are stored in bean receptacle 1134.

In some examples, milk tank 1138 may be compartmentalized or sub-divided to store different types of milk. For example, milk tank 1138 may be split into two or more compartments and include various types of milk, including (but not limited to) soy milk, oat milk, almond milk, coconut milk, and other varieties. Each compartment can include a distinct spout or output tube to avoid cross-contamination of different flavors, allergens, or dietary restrictions. For example, a user with a lactose sensitivity may use the same coffee station 1106 as a user without the allergy, because milk tank 1138 would provide separation between the different types of milk, which would be dispensed through different output tubes.

Beverage system 1100 of FIG. 11-1 additionally or alternatively includes a cocktail station 1108. FIG. 11-8 is a conceptual block diagram illustrating some example components of cocktail station 1108. Cocktail station 1108 may be built into a wall or integrated into faucet 1150. In some examples, cocktail station 1108 is an example of hydration station 1102 of FIG. 11-2. For instance, cocktail station 1108 can include many or all of the same components as hydration station 1102, or equivalently, hydration station 1102 includes the functionality associated with cocktail station 1108 detailed herein.

In the example shown in FIG. 11-8, cocktail station 1108 includes a housing 1148 defining a generally rectangular-prism shape defining an interior cavity or volume 1150. Housing 1148 can be formed from any suitably durable material, such as metal or plastic. Housing 1148 can define at least one exterior volume 1152 for use as a cocktail-dispensing area, and an aperture 1170 for receiving beverage ingredients.

Cocktail station 1108 can be operably coupled to any conventional power source, such as a standard 120-Volt circuit typical of residential power grids. In some examples, cocktail station 1108 can be operably coupled to wired or wireless data networks, such as via conventional LAN, WLAN, Bluetooth™, etc.

Within dispensing area 1152, cocktail station 1108 includes a first dispenser 1154 and a second dispenser 1156 removably affixed to a downward-facing exterior surface 1158 of housing 1148. In some examples, cocktail station 1108 further includes a mixing assembly 1160 adjacent to dispensers 1154, 1156 along exterior surface 1158.

Dispenser 1154 can include any suitable type of nozzle, sprayhead, spout, or tap configured to dispense a beverage 1101C retained within interior volume 1150 of housing 1148. For instance, dispenser 1154 may be fluidly coupled to interior volume 1150 via tubing 1162 in order to dispense a beverage 1101C into dispensing area 1152. A receptable, such as a cocktail glass 1164, can be placed within dispensing area 1152 to catch beverage 1101C as it is dispensed via dispenser 1154.

Similar to beverage dispenser 1154, ice dispenser 1156 can include any suitable type of nozzle or other fixture operably coupled to an ice box 1166 configured to generate and retain cubed and/or crushed ice. In some examples, cocktail station 1108 can dispense ice from ice box 1166 either automatically, e.g., during a pre-configured drink-mixing sequence, or manually, in response to a user's request via an actuator 1168. Actuator 1168 can include any suitable user-input device, such as a button, slide, switch, lever, or touchscreen (e.g., user interface 1112 of FIG. 11-2).

As described above with respect to hydration station 1102 and coffee station 1104, cocktail station 1108 includes a control unit 1120 and one or more sensors 1122, wherein control unit 1120 is configured to process signals generated by sensor(s) 1122 to determine, for example, a temperature (e.g., for monitoring the temperature of ice box 1166 or interior cavity 1150 to ensure liquids and ice are within predetermined “acceptable” temperature ranges) and/or pressure (e.g., for sensing actuation of actuator 1168) to enable one or more functions of cocktail station 1108.

Mixing assembly 1160 is configured to integrate two or more ingredients to produce beverage 1101C. In some examples, mixing assembly 1160 includes a conventional valve-and-pump operably coupled to control unit 1120. Mixing assembly 1160 can receive instructions from control unit 1120 to retrieve specified amounts and types of ingredients (e.g., alcohol, water from water tank 1136, ice from icebox 1166, etc.), and blend the ingredients according to a predetermined intensity and duration. Mixing assembly 1160 can then dispense the mixed beverage 1101C to dispensing area 1152 via dispenser 1154. In some examples, dispensers 1154, 1156 can directly dispense drinks to receptacles 1164 within dispensing area 1152, i.e., without having been mixed by cocktail station 1108 first. In some examples, a relatively larger dispensing area 1152 can accommodate additional dispensers, thus enabling cocktail station 1108 to mix and dispense multiple beverages 1101C simultaneously.

FIG. 12 is a conceptual block diagram illustrating a command system 1200 that may be incorporated within smart-kitchen environment 100 of FIG. 1-1, and operably paired to any or all of the various kitchen-related systems 1274 (and components thereof) described throughout this disclosure. As shown in FIG. 12, command system 1200 may include a main control unit 1246, a charging dock 1268, a mobile computing device 1270, and a display screen or touchscreen 1272. In some examples, charging dock 1268 functions as a personalized wireless charging dock for smartphones 1270 or other connected devices 1274. Charging dock 1268 may include several different features such as a speaker 1226 (e.g., speaker 1026), lighting 1202 (e.g., LEDs 1002), and another display screen or touchscreen 1224 (e.g., display 1024).

In general, command system 1200 is configured to enhance smart-kitchen environment 100 by transforming kitchen environment 100 into an entertainment space, e.g., by operably interconnecting any of various different kitchen systems, products, and features 1274 that may be wirelessly controlled by control unit 1246. For example, a user may use control unit 1246 to remotely preheat an oven without physically interacting with it, or to turn on a sink to begin heating water to wash dishes. Control unit 1246 may have voice and vision-recognition systems enabling a user to interact with control unit 1246 from anywhere within kitchen environment 100.

In some examples, control unit 1246 can take the form of a mobile computing device 1270, such as a smartphone, tablet, laptop, or wearable device. In such examples, a mobile application (or “app”) running on the device enables a user to control certain kitchen systems without actually being present at home. Example functions of control unit 1246 include (but are not limited to): turning on a sink faucet, preheating an oven, lowering the temperature of a refrigerator (e.g., refrigerator 1336 of FIG. 13-1), starting a dishwasher cycle, and selecting and dispensing a beverage from stations 1102, 1106, 1108. Upon user request, display screen 1272 of control unit 1246 can display recipes, e.g., based on voice recognition of verbal commands. Additionally or alternatively, display screen 1272 may show the current status of various kitchen devices 1274, such as the remaining lifespan of a water filter, whether coffee station 1106 needs to run a cleaning cycle, or any other relevant monitored parameter within kitchen environment 100.

FIGS. 13-1 through 13-4 illustrate a refrigeration unit 1336 that incorporated within smart-kitchen environment 100 of FIG. 1-1. Refrigeration unit 1336 includes an ozonated-misting system 1300 for automatically generating and dispensing ozone-purified mist 1301 (e.g., ozonated mist 301 of FIGS. 3-1 through 3-4) into designated compartments 1304A-1304F (collectively, “compartments 1304”) within refrigeration unit 1336. Misting system 1300 includes a plurality of elongated, movable/articulating fluid-conduit sections 1320 to enable precise control over the flow direction of ozonated mist 1301, wherein adjacent conduit sections 1320 are removably or fixedly coupled to each other via joints or hinges 1310. According to various examples, misting system 1300 can include one or more mist dispensers 1302A, 1302B, such as sprayers, spouts, or sprinklers.

FIG. 13-1 is a front view of an interior space 1312 of refrigeration unit 1336, enclosed by an insulated housing 1314. A first produce-refrigeration compartment 1304A, which is exemplary of a plurality of compartments 1304 within refrigeration unit 1336, can be positioned anywhere suitable within refrigeration unit 1336 such that the refrigeration compartment 1304A can sustain temperatures to promote longevity of food items (e.g., produce) and is configured to operate within a designated temperature range. Refrigeration compartment 1304A can be removably positioned within refrigeration unit 1336 such that it can easily be accessed by a user, for example, as a pull-out shelf or as a sliding door. Mist dispenser 1302A, positioned within refrigeration compartment 1304A, generates and dispenses mist 1301 over a user-configurable area. Mist dispenser 1302A is fluidly coupled to conduits 1320 running alongside each edge of refrigeration unit 1336.

Similarly, a freezer compartment 1304E can be positioned anywhere suitable within refrigeration unit 1336 to sustain reduced temperatures to promote longevity of frozen food items. Freezer compartment 1304E includes a cooling unit 1316, e.g., a standard refrigerator ice-machine, configured to generate and dispense ice cubes and water. Cooling unit 1316 is an example of ice box 1166 of FIG. 11-8, and vice versa.

FIG. 13-2 is a conceptual block diagram of a portion of misting system 1300 of FIG. 13-1 that includes mist dispenser 1302A, and FIG. 13-3 is a partial exploded view of an example of mist dispenser 1302A. As shown in FIGS. 13-2 and 13-2, mist dispenser 1302A includes a plurality of fluid conduits 1320A-1320G, at least one sensor 1322, a plurality of nozzles 1318, an input tube 1324, a supply tube 1326, and an ozone generator 1308.

Mist-delivery system 1300 can be configured such that a first end of input tube 1324 is fluidly connected, via fluid conduit 1320A, to cooling unit 1316. A second end of input tube 1324 can be fluidly connected, via fluid conduit 1320B, to ozone generator 1308. Ozone generator 1308 can be fluidly connected, via fluid conduit 1320C, to a first end of supply tube 1326. A second end of supply tube 1326 can be multiply connected to a plurality of fluid conduits 1320D-1320G each rotatably coupled to another fluid conduit 1320 via a conventional hinge 1310 or a magnetic joint 1328. Magnetic joints 1328 each include at least a first member 1330A and a second member 1330B, where each of the first member 1330A and second member 1330B includes a plurality of individual magnets 1332 (e.g., a first magnet array, etc.) that are spaced around the circumference of the respective member 1330.

As shown in FIG. 13-3, first magnetic-joint member 1330A can be rotatably coupled to second magnetic-joint member 1330B. First member 1330A can also be coupled to, or integrally formed with, an end of a first adjacent component (e.g., a conduit end, a component of a hinge, etc.) and second member 1330B can be coupled to or integrally formed with an end of a second adjacent component (e.g., adjacent to the first component). Each component can be selectively rotated relative to the other between a plurality of rotational positions that are defined by spacing and polarity of the magnets 1332 on the first and second members 1330, so as to selectively reorient the joint components 1330 relative to each other.

In some examples, each fluid-conduit section 1320 defines at least one end surface that is angled or tapered (e.g., non-orthogonal) relative to a central longitudinal axis of the conduit section. When the conduit section is coupled to another component (e.g., another conduit section, a tube, mist dispenser 1302, etc.), the angled surface enables a user to adjust an orientation of the conduit section relative to the other component simply by rotating the conduit section about its central axis.

Conduits 1320 of mist-delivery unit 1302A define respective conduit edges 1334 that are rotatably coupled to each other. Conduit edges 1334 can be substantially rigid and can be flexibly oriented. Conduits 1320 are configured to be coupled to a mounting surface 1338 (e.g., a hook 1352 (FIG. 13-1) or a tray holder edge within refrigeration compartment 1304A, etc.). Conduit 1320 can pivot or swivel about its central axis relative to mounting surface 1338. In some examples, fluid-conduit section 1320F includes a rotatable inner section 1342 therein that enables articulation of conduit section 1320F. Fluid conduits 1320 each define a central opening 1340 collectively defining a common fluid pathway for communicating fluid 1301 from supply tube 1326 to nozzles 1318. Input tube 1324 defines two opposite openings (and a fluid pathway therebetween) and can be mounted on secure mounting surface 1338 (e.g., via a hook 1352 or edge in refrigeration unit 1336, etc.) proximate cooling unit 1316.

Input tube 1324 can include a valve assembly 1344 (e.g., fluid-control valve 304 of FIGS. 3A-3D) having one or more sections 1350 (e.g., modules, portions, etc.) defining one or more chambers 1348. Valve assembly 1344 can include sections 1350 that, when combined, define at least a first chamber 1348A and an opening, and that fluidly and rotatably connects to cooling unit 1316 via a conduit 1320, and a second chamber 1348B that can connect to ozone generator 1308. Input tube 1324 can also include an inlet 1324A and an outlet 1324B each respectively configured to receive and dispense a supply of fluid 1301 (e.g., water, etc.). Valve assembly 1344 can include a fluid inlet 1344A.

In some examples, input tube 1324 can be rotatably coupled to cooling unit 1316 on one end, and to ozone generator 1308 on another end, each via a separate fluid-conduit 1320. Connecting input tube 1324 via chamber 1348A to cooling unit 1316 enables mist dispenser 1302A to receive fluid 1301 (e.g., cooled water, etc.) from cooling unit 1316 and, after ozonation, to dispense fluid 1301 via nozzles 1318. In some such examples, because input tube 1324 can obtain a steady supply of fluid 1301 from cooling unit 1316 (e.g., via inlet 1324A and valve chamber 1348A), the user is not required to manually remove and refill input tube 1324 with fluid or coolant for generation of cooled fluid 1301. As another example, because input tube 1324 includes second valve chamber 1348B that is rotatably coupled to ozone generator 1308, water 1301 is directly supplied to ozone generator 1308 for purification before ultimately traveling to supply tube 1326 and through the plurality of conduits 1320, to be dispensed via nozzles 1318 over a designated area.

Nozzle 1318 is configured to dispense ozone-treated mist 1301 according to a misting cycle selected from a plurality of cycle options (e.g., dispensing mist 1301 once every 60 seconds, etc.). Processing circuitry 1346 embedded within mist dispenser 1302 can automatically run the cycle. In other examples, processing circuitry 1346 can be located remotely from mist dispenser 1302 and can transmit, to transducer circuitry 1356 embedded within mist-delivery unit 1302, a signal indicating automated and/or manually scheduled cycle selections. Mist dispenser 1302 can also be configured such that the preselected cycle is automatically interrupted and resumed based on motion detected by sensor 1322, which can be located proximally to nozzle 1318. Nozzle 1318 can be retained within housing 1314 with an accessible attached valve 1354 that enables the user to modify the flow rate of fluid 1301 dispensed from nozzles 1318.

As shown in FIG. 13-1, ozone generator 1308 can be mounted on a hook 1352 of refrigeration interior 1312 to access a supply of water 1301 for purification from cooling unit 1316. Ozone generator 1308 is an example of ozone generator 308 of FIG. 3-4, and can include any or all of the features thereof.

Water 1301 is supplied from cooling unit 1316 via fluid-conduit component(s) 1320 which allows for pumping water 1301 through ozone generator 1308. Ozone generator 1308 then generates ozone, which is injected into water 1301. Treated water 1301 is sent to supply tube 1326 to be dispensed via nozzles 1318.

FIG. 13-4 is a flowchart 1360 illustrating an example operation of ozonated-mist system 1300 of FIG. 13-1. At step 1362, sensor(s) 1322, such as proximity/motion sensors, are configured to detect any objects (e.g., produce) stored within refrigeration compartment 1304A, and whether refrigeration compartment 1304A is in its “base” (e.g., default or “closed”) state. Additionally or alternatively, sensor(s) 1322 can include photonic sensor(s) calibrated to detect whether objects within refrigeration compartment 1304A, such as fruits or vegetables, display any chemical damage and/or bacterial overgrowth.

If, in step 1364, sensor(s) 1322 detect produce within refrigeration compartment 1304A, and that refrigeration compartment 1304A is in its “base” state (“YES” branch from step 1364), then processing circuitry 1346 generates a signal to select a cycle for automatic or manual scheduling (step 1366). Alternatively, if sensor(s) 1322 do not detect any objects within refrigeration compartment 1304A and/or if refrigeration compartment 1304A deviates from its base state (“NO” branch from step 1364), then processing circuitry 1346 either pauses the ongoing cycle or stops selection of a future cycle (step 1368) and continues to monitor for produce placed within refrigeration compartment 1304A and for the base state of refrigeration compartment 1304A (step 1362).

At step 1368, after processing circuitry 1346 has generated a signal to select a cycle for automatic or manual scheduling, processing circuitry 1346 further assesses whether a cycle has already been selected and is already ongoing (step 1370). If so (“YES” branch from step 1370), processing circuitry 1346 generates a signal to continue the ongoing cycle and/or proceed to dispensing ozonated mist 1301 (step 1372). Alternatively, if no cycle has yet been scheduled (“NO” branch from step 1370), processing circuitry 1346 generates a signal to select a cycle for automatic scheduling (step 1374). Cycles available for selection can include, for instance, a “default” cycle (e.g., nozzles 1318 dispense ozonated mist 1301 every 60 seconds for one hour); a “rain” cycle (e.g., nozzles 1318 dispense ozonated mist 1301 to mimic natural rainfall); a “night” cycle (e.g., nozzles 1318 dispense ozonated mist 1301 for a threshold nighttime period); and a “custom” cycle (e.g., wherein the mist-dispensing frequency, rate, and/or duration are manually specified by a user).

At step 1376, sensor 1322 continues to monitor the base state of refrigeration compartment 1304A and whether objects, such as fruits or vegetables, are detected within refrigeration compartment 1304A. If produce remains detectable and refrigeration compartment 1304A remains in its base state (“YES” branch from step 1376), the selected cycle is continued, resumed, or initiated without modification (step 1382). However, if sensor 1322 either detects an empty refrigeration compartment 1304A and/or a shift in the base state (“NO” branch from step 1376), then processing circuitry 1346 generates a signal to pause the current cycle for a threshold time (e.g., 30 seconds, etc.) (1380).

If, during the threshold time, the state of refrigeration compartment 1304A has not shifted to its base state and/or if sensor 1322 continues to detect an empty state for refrigeration compartment 1304A (“NO” branch from step 1376), then the selected cycle may be terminated (1380). Otherwise, if, within the threshold time, refrigeration compartment 1304A returns to its base state and/or sensor 1322 detects produce within the refrigeration compartment 1304A, the selected misting cycle is resumed to completion (1378).

FIG. 14 illustrates an example self-cleaning kitchen robot 1410, particularly configured to automatically scrub, mop, or otherwise clean various surfaces within smart-kitchen environment 100 of FIG. 1-1, e.g., with minimal-to-no human intervention.

In some examples, robot 1410 includes a main housing 1412, and is remotely controllable via control unit 1246 of FIG. 12. Control unit 1246 processes information received from one or more sensors 1422 integrated into robot 1410, e.g., to identify the robot's position, identify kitchen-counter edges, impeding objects, etc., and based on the information, determine what functions robot 1410 is to perform. In some examples, control unit 1246 controls motors integrated within robot 1410 (e.g., for propulsion, cleaning features, etc.). Information about the robot's surrounding environment, such as maps of current and previous surfaces (e.g., kitchen countertops or tabletops) and task-scheduling may be stored in non-volatile memory within robot 1410.

In some examples, robot 1410 includes one or more drive wheels 1416 configured to propel robot 1410 via one or more internal motors. In some examples, housing 1412 also retains an internal battery (not shown) configured to power robot 1410. In some such examples, the battery provides sufficient voltage to power the robot's internal processor, sensors 1422, and motors. In some such examples, robot 1410 can include a rechargeable battery configured to provide 1410 with sufficient power to completely clean a designated target surface area, such as an entire kitchen countertop table. In some examples, robot 1410 includes a docking station (e.g., charging dock 1268 of FIG. 12), configured to automatically engage and recharge robot 1410 while not in use (e.g., following the automatic cleaning of a given surface). In some examples, robot 1410 both initiates and concludes each cleaning cycle from the docking station.

In some examples, robot 1410 includes a “dry” cleaning system 1420. In some such examples, dry cleaning system 1420 is mounted on the bottom of housing 1412, spanning the entire orthogonal width of housing 1412. In some such examples, dry cleaning system 1420 may also span the parallel length of housing 1412. In other examples, dry cleaning system 1420 may extend across certain portions of the length and/or width of housing 1412. In some such examples, dry cleaning system 1420 may extend along housing 1412 leading up to, but not interfering with, drive wheels 1416. In some examples, dry cleaning system 1420 includes a scrubber 1414. Scrubber 1414 may include a plurality of scrubbing bristles, that, during cleaning cycles, scrape and/or scrub across the surface over which robot 1410 is propelled. In some examples, scrubber 1414 is operably coupled to rotatable gears, powered by the motor, such that the bristles of scrubber 1414 rotate or spin relative to housing 1412. In some examples, dry cleaning system 1420 is removable from housing 1412 for easy cleaning and maintenance.

In some examples, robot 1410 includes a “wet” cleaning assembly 1424. Wet cleaning assembly 1424 can include a moistened fabric device configured to wipe or mop a surface within kitchen environment 100. In some such examples, the wet fabric device may be pre-moistened (e.g., with water, soap, cleaning agent etc.). In some such examples, the wet fabric device may be pre-moistened at docking station 1268, such that, when robot 1410 is idle at docking station 1268, a moistening mechanism (e.g., a hose fluidly coupled to a kitchen faucet, or a previously moistened component retained in the docking station) may pre-moisten or re-moisten wet cleaning assembly 1424.

In other examples, wet cleaning assembly 1424 includes a pre-moistened fabric device assembled onto feed rollers (not depicted). In such examples, the pre-moistened fabric device may be configured similar to a scroll in which moistened fabric is “unwound” from a first roll of the feed rollers, and then “wound” onto a second roll of the feed rollers. In some such examples, the material may be wound from between rollers during an automatic-cleaning cycle, thus remaining virtually unsoiled throughout the cycle. In some examples, wet cleaning assembly 1424 may be removable from housing 1412 for easy cleaning and maintenance.

In some examples, robot 1410 can be activated into an automatic-cleaning mode controlled by its internal processor. In the “automatic-cleaning” mode, the internal processor monitors the position of robot 1410 relative to its starting or “home” position (e.g., docking station 1268). The internal processor may execute instructions stored in the robot's random-access, non-volatile memory to determine a path of motion for robot 1410 during the “automatic-cleaning” mode. Once in the automatic-cleaning mode, the internal processor can actuate certain features of robot 1410, such as propulsion via wheels 1416 along the determined path of motion, and actuation of dry cleaning system 1420 and/or wet cleaning system 1424 to clean a specified surface of kitchen environment 100 (e.g., a kitchen countertop upon which robot 1410 and docking station 1268 may be placed). In some such examples, robot 1410 is guided along a path of motion that was “memorized” during a prior cleaning cycle, or that was calculated by robot 1410 based on measured/detected dimensions of the surface to be cleaned. In some examples, robot 1410 can activation of dry cleaning system 1420 and wet cleaning system 1424 either simultaneously or sequentially.

Upon completion of the cleaning cycle, e.g., after reaching the end of the path of motion, robot 1410 automatically returns to docking station 1268. In some such examples, the path of motion may inherently conclude with robot 1410 completing the cleaning process at the docking station. In some examples, robot 1410 traverses the path of motion such that robot 1410 covers the entire area of the surface to be cleaned while avoids potential obstacles along the way. In some examples, robot 1410 continuously monitors the condition of one or more of its own components, such as housing 1412, drive wheels 1416, dry cleaning system 1420, etc. If robot 1410 detects an anomaly or other error (e.g. malfunctioning drive wheels 1416), robot 1410 may automatically stopped moving and output an alert, such as an audible alert and/or a textual notification.

In some examples, the overall shape and configuration of robot 1410 may affect its ability to autonomously clean and navigate certain surfaces, but generally does not affect, nor is affected by, the automated scrubbing, mopping or other cleaning aspects. However, reducing a form factor of robot 1410 enables it to access and clean ever-smaller spaces. In some examples, the smaller the robot 1410, the smaller the dry-clean-system bristles and mop-assembly materials that may be utilized, and accordingly, narrower regions of a surface may be cleaned per unit time, thereby extending the duration required to complete a cleaning task. However, smaller shapes and sizes of robot 1410 provide a significant benefit in reaching smaller, more crammed or condensed areas of smart-kitchen environment 100, such as kitchen countertops, kitchen tables, etc. Accordingly, larger form factors of robot 1410 (e.g., integrating relatively larger cleaning systems and enabling longer durations) for cleaning may be unnecessary, as the kitchen surface area to be cleaned (e.g., a countertop) may tend to be significantly smaller than, e.g., an entire floorspace of a building in the first place.

FIG. 15 is a flowchart an example operation of an electronic-design-remodeling-services (“EDRS”) system for smart-kitchen environment 100 of FIG. 1-1. As described in greater detail below, the EDRS system provides a user experience (“UX”) that enables a style-like configuration, and delivers computer-generated imaging (“CGI”) or augmented-reality (“AR”) UXs to view and experience kitchen environment 100 based on preferred styles, likes, dislikes, etc. of a particular user. The CGI or AR UX enables the user to visualize different versions of kitchen environment 100 (e.g., viewing various, alternative components, appliances, etc.) with ease. Once satisfied, the products displayed to the user may be available for purchase, delivery, and installation.

At step 1502, a user interface (“UI”) of the EDRS system provides access to, and receives input from, a user, thereby initiating electronic design-remodeling services. The UI may be accessible via an electronic webpage (or via a mobile application) from any suitable computing device (e.g., home computer, laptop, smart device, AR headset, etc.). The EDRS system receives user input indicating certain preferences for customizing kitchen environment 100. For instance, the user may indicate what or how many components are desired for replacement, updating, etc., such as a sink, faucet, cabinets, etc.

In some examples, the user input may include any preferred styles of components, such as types or styles of sinks and faucets, knobs, countertops, drawers, cabinets, etc. In some examples, the user input may include any preferred manufacturing material the components are constructed of, such as copper, aluminum, stainless steel, etc. In some examples, granite, wood, marble, or other material may be considered for components like countertops, draws, cabinets, etc. In some examples, user input may include any favorite or preferred (or prohibited) colors for their kitchen environment 100. In some examples, the user may include any general likes, dislikes or generalized comments to be considered. For example, a user could include a preference for only viewing the newest (e.g., most-recent) available components, in which case, the EDRS system will only consider and display the newest products. In some examples, a user may upload their own pictures, specifications, or dimensions of their preferred kitchen environment 100 (e, g., layout of kitchen 100, dimensions of countertops, sizes for a sink, etc.).

At step 1504, a controller of the EDRS system, such as controller 840 of FIG. 8-3 or control unit 1246 of FIG. 12, receives the user input and processes the indicated user preferences encoded therein. In some examples, the controller analyzes the information by comparing and contrasting details of the user preferences with design specifications for products stored within a product database. Once analyzed, the controller selects one or more recommended products determined to best-satisfy the user preferences. In some examples, the product database may be or may include a list of all products (e.g., sinks, faucets, knob, countertops, drawers, etc.) that include at least one unit of inventory available for purchase. In some examples, the product database may be or may include a list of only products (e.g., sinks, faucets, knob, countertops, drawers, etc.) that are in-stock to purchase. In some examples, the product database may be or may include a list of products (e.g., sinks, faucets, knob, countertops, drawers, etc.) only available for purchase within a certain radius from the user's current location. In some examples, the product database is configured to continuously or periodically update product availability. While a variety of example considerations have been disclosed for identifying kitchen environment preferences and recommended products, more and alternative aspects are possible and contemplated.

At step 1506, the controller generates and displays, via the UI, relevant imagery depicting kitchen environment 100 with one or more of the recommended products. In some examples, the generated imagery incorporates a generalized or “standard” kitchen environment 100 (e.g., any of a number of selectable, pre-programmed environments that most-closely relate to the environment 100 of the user) and replaces any indicated products with those products chosen after the analysis. In some examples, images or dimensions specific to the user's kitchen environment 100 may be incorporated, thus replacing a pre-programmed environment with the actual kitchen environment 100 specific to the user. In some such examples, the EDRS system replaces old products with newly selected products within the user's kitchen environment 100 for a more-comprehensive visualization provided to the user (i.e., the generated image takes a replica of the old environment and replaces alternative components within that kitchen environment 100). In some examples, the EDRS system generates and displays a three-dimensional rendition of kitchen environment 100 to the user for viewing. In some examples, the image may be or may include an interactive display viewable via an AR headset (or other virtual-reality-compatible system).

In some examples, the EDRS system generates and provides one or more images to the user, based on preferences, priority levels, and “matching” products identified. In examples in which the EDRS system identifies only a single compatible result for a particular product category, the EDRS system may only generate and display a single rendered image. Alternatively, if the EDRS system generates more than one image, the user can further specify differentiating priority levels among their preferences. For instance, the user may specify a preferred maximum number of images for the EDRS system to generate. While a variety of underlying considerations have been mentioned for generating and delivering images to a user, additional and alternative aspects are possible and contemplated.

At step 1508, the EDRS system provides the user with multiple, selectable options after displaying the rendered imagery to the user. For instance, one selectable option may include a “cancel” feature that directs the user back to the previous UI to amend or edit indicated preferences. In additional or alternative examples, another selectable option includes a “reset” feature that resets all indicated preferences and directs the user back to the original UI. In some examples, another selectable option includes a “purchase” feature enabling the user to purchase the recommended product(s) among each generated image, either separately or as a package.

Once purchasing is complete, the EDRS system can display an additional selectable option regarding delivery instructions. For instance, delivery instructions may include either delivering the products directly to the user's residence, or instead, scheduling an on-site pickup.

In some examples, the EDRS system may display an additional selectable option indicating various contractors or other contact information associated with options for product-installation services. Such options may enable selecting among different contacts listed, displaying their qualifications/experiences, contact information, fees, and presenting scheduling options. In some examples, the EDRS system may provide a discount on the purchase or other fees, subject to purchasing the recommended product or hiring from the list of contacts for installation.

Once the user has completed their transactions (e.g., electronic design-remodeling services), the EDRS system may revert the display back to the original UI, enabling the user to commence another cycle of electronic design-remodeling services. The EDRS system, as described herein, enables all-inclusive electronic-design-remodeling services, which provide the user with easy access to view, purchase, and install kitchen products.

FIG. 16 illustrates a twelfth example sink system 1610 that may be implemented within smart-kitchen environment 100 of FIG. 101. Sink system 1610 is an example of sink system 110 of FIG. 1-1, apart from any differences described herein. In particular, sink system 1610 includes a “seamless” drain catch and/or drain cover, both detailed further below.

As shown in FIG. 16, sink system 1610 includes a sink module 1636 having a first basin 1616 (e.g., basin 116 of FIG. 1-1) and a second basin 1628 (e.g., basin 128 of FIG. 1-1) separated by a partition 1630 (e.g., partition 130 of FIG. 1-1). First basin 1616 defines a first drain 1622A (e.g., drain 122 of FIG. 1-1), and second basin 1628 defines a second drain 1622B. By comparison, second basin 1628 includes a drain cover 1623 placed over drain 1622B, as detailed further below.

In some examples, second basin 1628 includes substantially similar features to those described with respect to first basin 1616. In other examples, second basin 1628 includes different, additional, and/or alternate features compared to first basin 1616. For instance, second basin 1628 may have a greater vertical depth (e.g., height between top surface 1612 and drain 1622B) than first basin 1616. As another example, second basin 1628 may be fluidly coupled to a garbage disposal, making second basin 1628 a dedicated food-waste basin. It should be known that, while first basin 1616 is shown to be larger than second basin 1628, different relative dimensions, depths, and fluid capacities of first and second basins 1616, 1628 are contemplated.

Drain cover 1623 may be configured to removably couple to drain 1622, optionally integrated with a drain catch or duo-strainer. For instance, the floor of sink basin 1628 can define a circular ridge surrounding drain 1622B, as illustrated. In some such examples, cover 1623 may be positioned over drain 1622B such that drain cover 1623 at least partially covers drain 1622B. While drain cover 1623 is in place over drain 1622B, a circular gap 1662 is defined between an outer circumferential edge of drain cover 1623 and sink basin 1628 to allow for adequate drainage. In other examples, cover 1623 may be “flush” with sink basin 1628 to provide a “sleek” and “seamless” appearance. Gap 1662 may be configured to filter out debris or other material above a certain size, while allowing fluid and smaller material to pass through drain 1622 (or be further filtered by a drain catch, if present). In some examples, drain cover 1623 may be held in place via one or more magnets that are integrated into drain cover 1623, affixed in or around the area of drain 1622B, and/or coupled underneath sink basin 1628.

While certain elements of sink system 1610 are shown in FIG. 16 as being generally circular or oval-shaped, any or all of these elements may define any other suitable shape, including elliptical, racetrack, obround, rectangular, rounded-corner rectangular, etc.

FIG. 17 is a perspective view of a thirteenth example sink system 1710 that may be incorporated within smart-kitchen environment 100 of FIG. 1-1. Sink system 1710 is an example of sink system 110 of FIG. 1-1, apart from any differences described herein. In particular, sink system 1710 includes a “dual” sink module 1736 having a first sink basin 1716 and a second sink basin 1728. Each sink basin 1716, 1728 defines a respective drain 1722A, 1722B, configured to drain wastewater, scraps of food, or other by-products from sink module 1736. In some examples, first drain 1722A is operably coupled to a primary drain flange or drain outlet 1730. In some such examples, second drain 1722B is also operably coupled to primary drain outlet 1730 via tubing 1720. For instance, tubing 1720 can connect to, or otherwise intersect with, primary drain outlet 1730 such that combined waste material from both first basin 1716 and second basin 1728 flows out together through a single primary outlet 1730.

In some examples, a waste-disposal unit 1740 (or “garbage disposal”) may be functionally coupled beneath sink module 1736. In some such examples, waste-disposal unit 1740 is coupled to primary drain outlet 1730 such that waste-disposal unit receives and macerates waste material from both first basin 1716 and second basin 1728. In this way, both sink basins 1716, 1728 could function without requiring a strainer (e.g., drain catch 1620) to filter out larger solid waste material. That is, because both drains 1722A, 1722B are fluidly coupled to waste-disposal unit 1740, the risk of build-up or blockage of plumbing (e.g., pipes) connected below waste-disposal unit 1740 is substantially reduced, or even eliminated.

Additionally, connecting both basins 1716, 1728 to a common drainage outlet 1730 can help simplify the installation of sink module 1736. Additionally, the use of a common drainage outlet 1730 can free up storage space underneath sink module 1736. Additionally, the use of a common drainage outlet 1730 can reduce manufacturing costs.

FIGS. 18-1 through 18-3 illustrate a fourteenth example sink system 1810 that may be incorporated within smart-kitchen environment 100 of FIG. 1-1. Sink system 1810 is an example of sink system 110 of FIG. 1-1, apart from any differences described herein. In particular, sink system 1810 includes a handsfree, magnetic sink-stopper system 1800.

Sink system 1810 includes a sink module 1836 defining a drain 1822 operably coupled, via plumbing 1820, to a P-trap (e.g., curved plumbing configured to retain enough water to create an airtight seal that prevents odors from escaping drain 1822) or a waste-disposal unit (e.g., unit 1740 of FIG. 17). Magnetic stopper system 1800 includes a drain cover 1823 (e.g., drain cover 1723) and one or more electromagnetic (“EM”) coils 1824. Drain cover 1823 may be substantially circular or round in shape, and may be approximately centered within drain 1822. Drain cover 1823 may be sufficiently weighted (e.g., non-buoyant) to remain centered within drain 1822 at all times.

When EM coil(s) 1824 are in a non-energized (or “off”) state, fluids and/or waste material can drain through circular gap 1862 (e.g., gap 1662) between drain cover 1823 and sink base 1808. The size of the gap 1862 may vary depending on the size of drain cover 1823 relative to the size or circumference of drain outlet 1822. For instance, gap 1862 can define a width “w” of about 1 inch, about 1.5 inches, or about 2 inches while EM coil(s) 1824 are “off.”

FIG. 18-2 is a perspective bottom view of an example of drain cover 1823 of FIG. 18-1. Drain cover 1823 may be constructed of rubber, silicon, or any other suitable material. Drain cover 1823 may include a protruding center 1814 configured to fit downward into drain 1822 when EM coil(s) 1824 are activated. As noted in FIG. 18-2, protruding center 1814 can define symmetrical, tapered outer edges such that drain cover 1823 is self-centering when placed in drain opening 1822. In the example shown in FIG. 18-2, a cross-section of protruding center 1814 defines a cross-hatch or “plus” shape. In other examples, protruding center 1814 can define a circular cross-section, or any other suitable shape configured to help create a fluid seal within drain 1822 of FIG. 18-1. An outer circumference of the bottom portion of drain cover 1823 can further include a rubber gasket 1830 configured to fluidly seal drain opening 1822 while EM coil(s) 1824 are activated.

FIG. 18-3 is a cross-sectional side view of magnetic sink-stopper system 1800 in a “sealed” or “energized” or “on” state. As shown in FIG. 18-3, drain cover 1823 includes a magnetic ring 1832, e.g., formed from ferrite, a ferrous material, or any suitable magnetic metal. Magnetic ring 1832 is positioned within drain cover 1823 such that, when drain cover 1823 is positioned within drain 1822, magnetic ring 1832 is substantially aligned with EM coil(s) 1824. As illustrated, when EM coil(s) 1824 are activated, the resulting magnetic force magnetically attracts magnetic ring 1832 downward toward EM coil(s) 1824, thus, sealing drain cover 1823 down over drain opening 1822 such that a fluid seal is formed between sink base 1808, drain opening 1822, and plumbing 1820. In other examples, EM coil(s) 1824 are configured to merely reduce the size or cross-section of gap 1862 when activated, e.g., without forming a complete fluid seal.

Upon deactivation of magnetic coil(s) 1824, the magnetic force upon magnetic ring 1832 ceases, thus allowing drain cover 1823 to rise vertically from drain opening 1822 to unseal the drain. For instance, drain cover 1823 can include an embedded spring (or equivalently, the elastic material of central protrusion 1814 of FIG. 18-2) configured to compress downward while magnetic ring 1832 is magnetically attracted to EM coil(s) 1824, and to revert to its natural, un-compressed (or expanded) state when magnetic coil(s) 1824 are deactivated.

FIGS. 19-1 through 19-5 illustrate a fifteenth example sink system 1910 that may be incorporated within smart-kitchen environment 100 of FIG. 1-1. Sink system 1910 is an example of sink system 110 of FIG. 1-1, apart from any differences described herein. In particular, sink system 1910 includes a produce-washing system 1900. Produce-washing system 1900 constitutes a more-efficient alternative to manually washing various produce (e.g., fruit, vegetables, etc.). For instance, hand-washing can often fail to fully clean the produce, or can even damage more-delicate produce, such as berries, leaf vegetables, etc. By contrast, produce-washing system 1900 is configured to thoroughly and gently rinse produce, e.g., without damaging it.

Produce-washing system 1900 may be either removably disposed, or rigidly integrated, within sink module 1936. In either case, produce-washing system 1900 can be fluidly coupled to a water intake line (and/or faucet) of sink system 1910. In some examples, washing system 1900 may be a distinct, coherent module that can be installed separately from sink module 1936. In other examples, washing system 1900 can form, or be incorporated into, a “second” basin 1928 of sink module 1936, e.g., distinct from “first” basin 1916. In some examples, washing system 1900 is pre-installed within sink module 1936, e.g., with only a shared drain outlet requiring installation. In other examples, washing system 1900 is configured to be mounted independently from sink module 1936 within smart-kitchen environment 100.

In the example shown in FIG. 19-1, produce-washing system 1900 includes a designated “cleaning” basin 1928 of sink module 1936, e.g., distinct from “primary” sink basin 1916. Cleaning basin 1928 facilitates cleaning or washing soiled objects (e.g., produce, tableware, etc.) placed therein. In some examples, cleaning basin 1928 is formed from a rust-resistant material, such as stainless steel.

Cleaning basin 1928 facilities a cleaning process during which at least the overwhelming majority of visible contaminants (e.g., dirt, oil, etc.) are washed or rinsed off of objects (e.g., produce, tableware, etc.) retained within cleaning basin 1928. Cleaning basin 1920 receives water 1901 from a fluid source (e.g., plumbing, water tank, etc.). For instance, the fluid source may be fluidly coupled to a spray bar 1912 comprising a plurality of fluid outlets 1914 configured to spray water 1901 above, over, or onto objects placed within cleaning basin 1928 in the form of a water-fall type stream. Fluid 1901 output from spray bar 1912 may at least partially fill cleaning basin 1928, as desired. Additionally or alternatively, cleaning basin 1928 can receive a cleaning product (e.g., soap, produce cleaner, etc.) from an appropriate source.

In some examples, produce-washing system 1900 includes a produce basket 1930. Basket 1930 is configured (e.g., sized) to be placed within cleaning basin 1928. In some examples, basket 1930 is an independent, removable component that can be positioned outside of cleaning basin 1928. As shown in FIG. 19-2, in some examples, basket 1930 includes a handle 1952 that may be used to easily and efficiently carry basket 1930, to place basket 1930 (and/or additional baskets 1932, 1934, detailed below) into cleaning basin 1928, and to remove it therefrom. As shown in FIG. 19-3, in some examples, handle 1952 may be rotatable by 180 degrees, about axis X, between a first side 1954A and a second side 1954B of basket 1930.

The bottom and walls of basket 1930 may be made of metal (e.g., wire), plastic or another suitable material. For instance, elongated strips of the material may be woven together, crosshatched, molded, or otherwise integrated such that the structure of basket 1930 defines numerous gaps to allow liquid to freely pass through basket 1930, while keeping objects in place within the basket. In some examples, an underside of basket 1930 includes legs or spacers to distance the internal storage cavity of basket 1930 from the bottom of sink basin 1928.

Basket 1930 may be used with a variety of objects (e.g., food, tableware, glassware, etc.), such as produce 1940 (FIGS. 19-2 and 19-5), e.g., relatively larger objects such as heads of lettuce, apples, pears, watermelon(s), etc. In some examples, the bottom of basket 1930 may establish a first, lowest level 1964 within cleaning basin 1928, where objects held within basket 1930 may be washed or rinsed with fluid 1901 (e.g., tap water, soapy water, and/or other cleaning materials) flowing out of spray bar 1912 and/or at least partially filling cleaning basin 1928.

With additional reference to FIGS. 19-3 and 19-4, basket 1930 may include additional containers configured to segregate objects by size and/or type. For example, a “second” rectangular basket 1932 may be positioned within “first” basket 1930. Second basket 1932 may be sized to rest above the base of basket 1930, defining a space therebetween. In such examples, the bottom of second basket 1932 defines a second, mid-level position 1966 within cleaning basin 1928 where objects held within second basket 1932 may be washed or rinsed by fluid 1901 (e.g., tap water, soapy water, or other cleaning materials) flowing out of spray bar 1912 and/or at least partially filling cleaning basin 1928. In some examples, second basket 1932 may be configured with clips to removably couple to the sidewalls of first basket 1930, e.g., to hold second basket 1932 in place within first basket 1930. In some examples, objects to be washed may be separated by size. For instance, relatively smaller objects, relative to the objects held in basket 1930, may be held within second basket 1932.

In some examples, a “third” basket 1934 may be similarly configured to rest within “first” basket 1930. Third basket 1934 may rest above the base of basket 1930 and/or second basket 1932, such that objects may be further segregated between baskets 1930, 1932, 1934. As shown in FIG. 19-3, third basket 1934 may be configured to rest within basket 1930 and/or clip onto a top surface of basket 1930. In some such examples, the bottom of third basket 1934 defines a third, highest-level position 1968 within cleaning basin 1928 where objects held within third basket 1934 may be washed or rinsed by fluid 1901 (e.g., tap water, soapy water, or other cleaning materials) flowing out of spray bar 1912 and/or at least partially filling cleaning basin 1928. When only utilizing “first” basket 1930 and one or more “third” baskets 1934, a relatively larger space is available between the bases of baskets 1930, 1934, e.g., as compared to when a “second” basket 1932 is also incorporating. In some examples, third basket 1934 is configured to hold objects of even smaller sizes (e.g., berries, grapes, etc.) as compared to baskets 1930, 1932. In some examples, third basket 1934 rotatable by ninety degrees within basket 1930, thereby transitioning from resting at high position 1968 to middle position 1966, where objects held within basket 1934 may be washed or rinsed with fluid 1901 (e.g., tap water, soapy water, and/or other cleaning materials) flowing out of spray bar 1912 and/or at least partially filling cleaning basin 1928.

In some examples, a single basket 1930 may be used by itself. In other examples, one or more second baskets 1932 and/or third baskets 1934 may be used in combination with basket 1930, e.g., depending on the sizes and/or shapes of objects to be cleaned.

As shown in FIG. 19-3, in some examples, produce-washing system 1900 includes a basin lid 1960 (e.g., basin lid 132 of FIG. 1-1). Basin lid 1960 may be configured to rest on a ledge 1926 (e.g., ledge 126 of FIG. 1-1) extending across cleaning basin 1928. Basin lid 1960 may be sized and shaped to cover the entirety of the top of cleaning basin 1928. In some examples, basin lid 1960 may be sized to be long enough to rest across cleaning basin 1928 on ledge 1926. In some examples, basin lid 1960 is made of dishwasher-safe material, such as metal, ceramic, plastic, etc.

Basin lid 1960 may be used to enclose at least a portion of cleaning basin 1928 during a washing cycle by resting on ledge(s) 1926. In some examples, basin lid 1960 may be held in place over cleaning basin 1928 by a temporary fastening mechanism, such as magnets, slots, gravity (e.g., from a heavy weight of basin lid 1960), etc. In some examples, a top surface of basin lid 1960 defines a series of parallel ridges configured to direct water when basin lid 1960 is used as a drying rack. Additionally or alternatively, basin lid 1960 may a substantially smooth portion for use as a cutting board.

FIG. 19-4 illustrates an example of produce-cleaning system 1900 that includes one “first” basket 1930 and two “third” baskets 1934 assembled within cleaning basin 1928. In other examples, one or more second baskets 1932 and/or third baskets 1934 may be positioned at middle position 1966 and/or high position 1968 (FIG. 19-3). In some examples, one or more second baskets 1932 and/or third baskets 1934 may be snapped into place within first basket 1930, such that relatively larger objects are trapped in the vertical gap between the bases of the baskets, thus holding the objects under water during washing.

FIG. 19-5 is a conceptual diagram illustrating different example washing cycles using the washing system of FIG. 19-1. During a washing cycle of produce-washing system 1900, a user can specify a desired level of water to be held within cleaning basin 1928. For instance, the user can indicate whether to fill cleaning basin 1928 only halfway, or to completely fill cleaning basin 1928, as desired by the user and/or based on how many objects are placed within baskets 1930, 1932, 1934.

Third basket 1934 is designed to be placed at mid-level position 1966 or high-level position 1968 relative to the basket 1930 and sink basin 1920. In some examples, third basket 1934 is configured to retain relatively small, delicate objects (e.g., grapes, berries, etc.) such that the objects can “float around” within the basket but not escape. During a “full” washing cycle of produce-washing system 1900, relatively larger objects 1940 may be placed within basket 1930, while relatively smaller objects 1944 may be placed within third basket 1934.

In some examples, cleaning basin 1928 may be “completely” filled such that basket 1930 is essentially “submerged,” and fluid 1901 covers all objects within cleaning basin 1928 without allowing smaller objects 1944 to float out from their corresponding basket 1934, e.g., limiting the extent to which smaller objects 1944 may float around within third basket 1934.

Similarly, a user can select a “half” washing cycle of produce-washing system 1900, in which cleaning basin 1928 is filled halfway with fluid 1901. In some such examples, any smaller objects 1944 retained in second or third baskets 1932, 1934 may be submerged in fluid 1901 without floating out, due to the lower level of fluid 1901 within cleaning basin 1928.

In some examples, produce basket 1930 can include a “collapsible” basket configured to expand and contract to attain a particular size, as desired by the user. For instance, produce basket 1930 may be configured to expand and contract vertically, to define an internal cavity of varying heights. For instance, in a first (or “collapsed”) configuration, basket 1930 can define a height extending between bottom level 1964 and mid-level 1966. In a second (or “partially collapsed/expanded”) configuration, basket 1930 can define a height extending between bottom level 1966 and high level 1968. In a third (or “expanded”) configuration, basket 1930 can assume the full vertical height depicted in FIGS. 19-1 through 19-5. Additionally or alternatively, produce basket 1930 may be configured to collapse along one or both horizontal directions. For example, a “first” produce basket 1930 can be configured to collapse inward on itself until it assumes the dimensions of a “second” produce basket 1932, or further yet until it assumes the dimensions of a “third” produce basket 1934. In this way, a user can purchase a plurality of identically manufactured produce baskets, and then uniquely (and reusably) customize their various sizes and nesting arrangements to fit the user's particular produce-washing needs.

In some such examples of a collapsible produce basket 1930, produce-washing system 1900 is configured to automatically adjust the produce-washing cycle based on a detected height of basket 1930. For instance, produce-washing system 1900 can include a “float switch,” e.g., integrated within produce basin 1928, that changes its vertical position based on the vertical height of collapsible basket 1930 at any given time. Based on the vertical position of the float switch, produce-washing system 1900 can automatically select a corresponding wash cycle, including at least a particular amount of water with which to fill produce basin 1928. While basket 1930 is in the “collapsed” configuration, produce-washing system 1900 may only partially fill produce basin 1928 with water 1901. By contrast, while basket 1930 is in the “expanded” configuration, produce-washing system 1900 may completely fill produce basin 1928 with water 1901.

In some examples, basket 1930 can include a mechanical water-agitation mechanism, such as magnetic impeller(s) 2034 described below. For instance, while basket 1930 is “submerged” in produce basin 1928 filled with water 1901, produce-washing system 1900 can activate an agitator device configured to stir and/or shake water 1901 so that water 1901 continually contacts and thoroughly rinses produce 1940 retained within the basket. Additionally or alternatively, produce-washing system 1900 can include an ozone generator (e.g., ozone generators 308, 1308) configured to purify water 1901 as detailed throughout this disclosure in order to clean produce 1940, 1944 even more thoroughly. For instance, an ozone generator can be integrated within sink module 1936 in order to purify water 1901 before it is dispensed from spray bar 1912 onto produce 1940, 1944. Additionally or alternatively, an ozone generator can be integrated within produce basket 1930 in order to purify water 1901 as it washes over produce 1940, 1944 during a wash cycle of produce-washing system 1900.

FIGS. 20-1 through 20-3 depict an example produce basket 2030A, which is an example of “first” produce basket 1930 of FIGS. 19-1 through 19-5, apart from the differences explicitly noted herein. In particular, basket 2030A includes a berry basket 2032 (e.g., “second” basket 1932 or “third” basket 1934) and a rotating impeller 2034. As used herein, the term “impeller” refers to a device configured to rotate about an axis in order to cause a fluid to flow parallel to the axis.

In the example shown in FIGS. 20-1 through 20-3, impeller 2034 is operably coupled to an underside of basket 2030A, specifically, beneath berry basket 2032, in order to convey water and/or air through berry basket 2032. For instance, in examples in which produce basket 2030A is positioned within a sink basin (e.g., produce basin 1928) that is at least partially filled with water, a user can actuate impeller 2034 in order to create a current of water that flows upward through the underside of berry basket 2032. Any produce (e.g., berries) disposed within berry basket 2032 may be rinsed by the current of water.

Additionally or alternatively, in examples in which basket 2030A is at least partially submerged in water 1901 within produce basin 1928, a user can actuate impeller 2034 to agitate the water 1901 to more-thoroughly rinse produce 1940, 1944 held within baskets 2030A, 2032, respectively. For instance, impeller 2034 can be actuated to rotate in a single rotational direction, e.g., in order to “stir” water 1901 within produce basin 1928. Additionally or alternatively, impeller 2034 can be actuated to periodically alternate rotational directions to more aggressively agitate water 1901 for a deeper clean.

After rinsing produce within basket 2030A according to any of these techniques, basket 2030A can be removed from produce basin 1928, and/or water 1901 can be fully drained from produce basin 1928. Subsequently, impeller 2034 can be actuated again, this time functioning as a fan blowing air through basket 2030A, thus drying off the moistened produce therein.

FIGS. 20-4 and 20-5 depict another example produce basket 2030B. Basket 2030B is an example of produce basket 2030A of FIGS. 20-1 through 20-3, apart from the differences explicitly noted herein. In particular, basket 2030B includes a pair of rotating impellers 2034A, 2034B, either of both of which may be an example of impeller 2034 of FIGS. 20-1 through 20-3. As depicted in FIG. 20-4, in examples in which sink basin 1928 is filled with an above-threshold level of water, impellers 2034A, 2034B can be actuated in concert (e.g., spinning in opposite directions) to form a circular current of water to rinse produce retained within basket 2030B.

Additionally or alternatively, in examples in which sink basin 1928 is not filed with a minimum threshold level of water, impellers 2034A, 2034B can be actuated together to form a circular current of air to dry off produce retained within basket 2030B, e.g., after having previously rinsed the produce with water.

FIG. 20-6 is a perspective view of a rotating impeller 2034C, which may be an example of any of impellers 2034, 2034A, 2034B of FIGS. 20-1 through 20-5. A rotational motion of impeller 2034C may be magnetically driven, e.g., by a rotating magnet positioned on an opposite side of a stainless-steel sink basin 1928. The rotating magnet can be motor-driven, motorlessly driven, or a combination thereof. For instance, FIG. 20-7 depicts an example of a motor-driven magnetic impeller in the form of a typical magnetic stirrer 2036A. Magnetic stirrer 2036A includes an internal electric motor that causes an internal magnet to rotate. The rotational motion of the internal magnet is imparted upon the rotating stir-bar across the housing of stirrer 2036A.

By contrast, FIG. 20-8 depicts an example of a “motorless” magnetic impeller in the form of a magnetic-induction-based liquid stirrer 2036B. Unlike stirrer 2036A, stirrer 2036B includes no internal moving parts, but instead, magnetically rotates the stir-bar through iterative, selective actuation of a plurality of internal magnetic coils. Either type of magnetic-rotation mechanism may be incorporated beneath sink basin 1928 to rotate the impellers 2034 of FIGS. 20-1 through 20-6.

In another example, the basket can be substituted for a basket for cleaning and drying vegetables, such as lettuce, such as a “salad spinner” in which the impeller rotates or spins the basket itself, thereby spinning off the moisture. An optional lid can be placed on the basket to reduce splashing or spraying.

FIG. 21-1 is a perspective view of a sixteenth example sink system 2110 that may be integrated within kitchen environment 100 of FIG. 1-1. Sink system 2110 is an example of sink system 110 of FIGS. 1-1 and 1-2, apart from any differences explicitly noted herein. In particular, sink system 2110 includes a sliding basin lid 2132. Basin lid 2132 is an example of basin lid 132 of FIG. 1-1 and/or basin lid 1960 of FIG. 19-3, apart from any differences explicitly described.

Basin lid 2132 may be configured to rest on a shelf, shown in FIG. 21-1 as ledge(s) 2126 (e.g., ledges 126, 1926), which, in some examples, extend across sink module 2136. Basin lid 2132 may be shaped to cover the entirety of the top of cleaning tub 2128 (e.g., produce basin 1928). In some examples, basin lid 2132 is sized long enough to rest across sink module 2136 on ledge 2126. In some examples, lid 2132 may be made of a dishwasher-safe material (e.g., metal, ceramic, plastic, etc.).

Basin lid 2132 may be used to enclose the cavity defined by cleaning basin 2128, by resting on the top portion of cleaning basin 2128. In some examples, basin lid 2132 may be used to cover at least a portion of sink module 2136. In some examples, basin lid 2132 may be held in place on cleaning basin 2128 and/or sink module 2136 by a temporary fastening mechanism (e.g., magnets, slots, etc.). In some examples, a top surface of basin lid 2132 includes a plurality of parallel ridges 2114 (collectively defining grooves 2116 therebetween) to direct water, e.g., when used as a drying tray. Additionally or alternatively, basin lid 2132 can define a substantially smooth portion for use as a cutting board.

FIG. 21-2 is a perspective view of sink system 2110 of FIG. 21-1, with basin lid 2132 supporting produce basket 2030B of FIG. 20-4, and FIG. 21-3 is a perspective view of sink system 2110 with produce basket 2030B lowered into cleaning basin 2128. As shown in FIGS. 21-2 and 21-3, basin lid 2132 is configured to slide left-and-right, e.g., along tracks or ledges 2126 defined by sink module 2136, to close or seal different portions of sink module 2136, as desired by the user. That is, in FIG. 21-2, basin lid 2132 has been used to seal off the right-hand produce basin 2128. In FIG. 21-3, basin lid 2132 has been manually slid to the left to un-seal produce basin 2128.

FIG. 21-4 is a perspective view of basin lid 2132 of FIG. 21-1. In some examples, basin lid 2132 may be integrally formed from a soft, high-friction material, such as rubber. In some such examples, basin lid 2132 can be used as a drying rack, wherein wet dishes may be retained within grooves 2116 defined between ridges 2114 along the top surface of basin lid 2132, in order to air-dry.

FIG. 21-5 is a perspective bottom view of basin lid 2132 of FIG. 21-1. As shown in FIG. 21-5, an underside of basin lid 2132 defines one or more “sharp” edges 2102. That is, a cross-section 2104 of basin lid 2132 defines one or more downward-facing acute angles 2106 that define a pointed, elongated edge 2102 orthogonal to the cross-section 2104. These sharp edges 2102 define “local minimum” surface features (e.g., gravitational low-points) of basin lid 2132, along which water runs and drips downward off of basin lid 2132. Sharp edges 2102 are strategically positioned along the underside of basin lid 2132 to draw wastewater away from the sink countertop and downward into the sink basin.

FIG. 21-6 is a perspective side view, FIG. 21-7 is a perspective bottom view, and FIG. 21-8 is a side view, of basin lid 2132 of FIG. 21-1. In the example shown in FIGS. 21-6 through 21-8, basin lid 2132 includes a main body structure 2108 and a bottom shell 2112. As referenced above, body structure 2108 can include a relatively soft, high-friction material (e.g., rubber), such that ridges 2114 and grooves 2116 along the upper surface can function as a drying rack.

By contrast, bottom shell 2112 comprises a relatively rigid, low-friction material that extends along the underside of basin lid 2132. Bottom shell 2112 is configured to help reduce friction between basin lid 2132 and the sink basin, such that basin lid 2132 slides more easily along the inner ledges 2126 of the sink. Bottom shell 2112 is smooth, domed (e.g., concave), and hydrophobic to shed/deflect water back into basin 2128, while still allowing air to escape (e.g., without forming a vacuum seal). As referenced above, bottom shell 2112 can define one or more “sharp” edges 2102 configured to break the surface tension of a pool of water, thereby forcing excess water to fall back downward into the sink basin.

FIGS. 22-1 through 22-3 depict a seventeenth example sink system 2210 that may be integrated within kitchen environment 100 of FIG. 1-1. Sink system 2210 is an example of sink system 110 of FIGS. 1-1 and 1-2, apart from any differences explicitly noted herein. In particular, sink system 2210 includes a washing system 2200. Washing system 2200 constitutes a more-efficient alternative to washing produce (e.g., fruit, vegetables, etc.) and/or other objects (e.g., plates, silverware, etc.). In general, washing system 2200 is configured to wash more-robust objects and tougher produce, such as pots, pans, root vegetables, etc., more effectively, as described in greater detail below.

Sink system 2210 includes a cleaning basin 2228 (e.g., cleaning basin 1928) defining a drain 2222. In some examples, a drain cover 2223 can be actuated up and down relative to drain opening 2222 to allow and inhibit, respectively, the draining of fluid from sink basin 2228. Although not shown, sink system 2210 can additionally include easily removable ductwork and/or plumbing that provides easy access to internal components, e.g., for cleaning.

To facilitate such washing within cleaning basin 2228, washing system 2200 includes one or more jets 2220. When cleaning basin 2228 contains enough fluid to rise above jet 2220, e.g., during a cleaning operation of washing system 2200, jet 2220 intakes fluid 2201A from within cleaning basin 2228 and dispenses fluid 2201B back into cleaning basin 2228 with a user-selectable/user-adjustable fluid pressure and/or flowrate. Additionally or alternatively, the user may select and/or adjust the amount of fluid 2201A that is taken in via fluid intake(s) 2202 (FIG. 22-2), and expelled through propulsion output 2204 by jet 2220. For instance, the user may select a “delicate” output of fluid 2201B with a low fluid pressure and/or flow rate while cleaning delicate produce, and a high-pressure output of fluid 2201B while cleaning extremely dirty dishes.

In some examples, one or more jets 2220 may be integrated within basin sidewalls 2218 (e.g., basin sidewalls 118 of FIG. 1-1). In some such examples, basin sidewalls 2218 can horizontally project fluid 2201B toward the center of cleaning basin 2228 to wash produce or other objects placed at that location. Additionally or alternatively, one or more jets 2220 may be integrated within sink base 2208. In some such examples, sink base 2208 can project fluid 2201B vertically within cleaning basin 2228, thus washing produce or other objects held therein. In some examples, jets 2220 integrated into sink base 2208 can be configured with a variable maximum fluid pressure based on the level of water 2201A within cleaning basin 2228. For example, a maximum fluid pressure may be set such that the vertical height of the resulting fluid output 2201B does not exceed the surface level of fluid 2201A filling cleaning basin 2228. In other words, the water propulsion from jet 2220 is restricted to the existing fluid level, thus remaining contained within cleaning basin 2228. Jet(s) 2220 may be removably coupleable to cleaning basin 2228 for easy replacement and cleaning.

Fluid intake 2201A and output 2201B may both be adjustable, depending on the size and/or type of object to be washed. For instance, the user can lighten the fluid output 2201B for sensitive or fragile objects, and can provide a more-intense fluid output 2201B for more durable, robust, or extremely filthy objects.

In some examples, jet(s) 2220 may be communicatively coupled to a mobile computing device (e.g., a smart phone, tablet, computer, etc.), and accessible via a user interface thereof, to select/adjust settings of jet(s) 2220 settings, turn jet(s) 2220 on/off, control the output pressure, etc. Additionally or alternatively, sink basin 2228 can include physical and/or digital user inputs (e.g., buttons, gauges, switches, slide bars, etc.) configured to control/adjust the settings of jet(s) 2220.

FIG. 22-2 depicts a first example of jet 2220 of FIG. 22-1. Jet 2220 includes left-and-right fluid intakes 2202, a propulsion output 2204, and a control system 2206. Control system 2206 may operably interconnect and/or retain electronic and mechanical components such as a power source, a motor and/or gear housing, one or more processors, a memory, etc. Control system 2206 is configured to power and operate jet 2220 according to instructions received from the user, as described above, or any other pre-programmed instructions that dictate, e.g., duration of output, propulsion pressure, velocity, temperature, volume, etc.

Jet 2220 is configured to intake fluid 2201A via fluid intakes 2202 and cycle it through jet 2220. The cycled fluid 2201B may then be output with a determined or pre-programmed fluid pressure via propulsion output 2204. In some examples, propulsion output 2204 includes a fan 2212 configured to rotate about axis ‘x’ to help propel circulated fluid 2201B into the washing basin 2228 via propulsion output 2204.

FIG. 22-3 depicts a second example jet 2250, which is an example of jet 2220 of FIGS. 22-1 and 22-2. Jet 2250 is a mechanical jet powered by a motor 2260, which may be integrated or otherwise coupled within cleaning basin 2228. Motor 2260 may be electrically coupled to a power source (not shown) via one or more power cables 2262. Upon activation of mechanical jet 2260, the mechanical interface 2264 may be controlled via any suitable user-input mechanism, examples of which are recited above. In some examples, activation of mechanical jet 2250 includes opening or manipulating throttle 2266 such that a flap or other obstruction is at least partially opened. Motor 2260 generates power to pump fluid 2201A into fluid intake 2202. Fluid 2201A flows through mechanical jet 2250 and sprays out via propulsion output 2204 and into cleaning basin 2228. The extent to which the flap or other obstruction is “opened” relative to propulsion output 2204 dictates the volume, pressure, flowrate, etc. of fluid 2201B expelled from propulsion output 2204. Activation, deactivation, control of throttle 2266, power generated by motor 2260, suction pressure, output pressure, etc., may each be separably controllable via user inputs, as previously described.

FIGS. 23-1 and 23-2 are perspective views of an eighteenth example sink system 2310 that may be integrated within kitchen environment 100 of FIG. 1-1. Sink system 2310 is an example of sink system 110 of FIGS. 1-1 and 1-2, apart from any differences explicitly noted herein. Sink system 2310 includes one or more sink basins 2316 (e.g., sink basin 116 of FIG. 1-1) and an apron-front 2320. Apron-front 2320 may be coupled to or integrally formed with the front wall of sink basin 2316, e.g., via the same outer rim. Apron-front 2320 includes a storage compartment 2330 coupled to sink system 2310 via a moveable joint 2340. In some examples, movable joint 2340 may be a hinge mechanism structured to allow storage compartment 2330 to pivot between an “open” position (as shown in FIG. 23-1) and a “closed” position.

As detailed further below, movable joint 2340 may be configured to resist or slow the movement of storage compartment 2330, e.g., to prevent slamming. In some such examples, movable joint 2340 may be a torque or friction hinge configured to provide resistance to a pivoting motion. In other examples, movable joint 2340 may be configured to facilitate movement of storage compartment 2330. For instance, movable joint 2340 may be a hinge mechanism including one or more springs that provide tension to reduce the effort required to move the storage compartment from the “open” position to the “closed” position.

In some examples, movable joint 2340 is a separable joint configured to allow storage compartment 2330 to be removed from apron-front 2320 for servicing and/or other tasks requiring removal of storage compartment 2330. For example, movable joint 2340 may be a hinge with a removable pin that, when removed, allows removal of storage compartment 2330 from apron front 2320. For instance, a technician may remove storage compartment 2330 to quickly access internal components of storage compartment 2330 for servicing.

In some examples, storage compartment 2330 may be configured such that, while in the “closed” position, apron-front 2320 appears “seamless,” similar to conventional apron-front sinks. For instance, while in the “closed” position, storage compartment 2330 may appear seamless (e.g., indistinguishable) within apron front 2320.

Rack 2302 may be configured to receive one or more kitchen accessories 2304 (e.g., sponges, brushes, scrubbers, etc.) and may be further configured to have an open bottom (e.g., a wire rack) to provide ventilation and drainage for items stored thereon. A tray (not shown) may be positioned underneath rack 2302 to capture moisture drained from the stored kitchen accessories 2304 and may be structured to be removable from storage compartment 2330 for cleaning.

FIG. 23-3 is a side view of storage compartment 2330 in the “closed” position, and FIG. 25-4 is a side view of storage-compartment 2330 in the “open” position. In some examples, storage compartment 2330 may include one or more sensors configured to detect whether storage compartment 2330 is in the “closed” position. For instance, a switch, an optical sensor, or any other suitable sensor can determine whether storage compartment 2330 is in the “closed” position. In some such examples, storage compartment 2330 may include a light bar 2306, such as UV-C LEDs, that indicate when storage compartment 2330 is open.

FIGS. 23-5 through 23-13 illustrate some example components of moveable joint 2340 of FIG. 23-1. As referenced above, moveable joint 2340 may include a “slow-open” mechanism, e.g., functionally similar to the mechanisms typically used in modern vehicle glove compartments.

In particular, FIGS. 23-5 through 23-7 show a laser-cut mounting plate 2308 configured to engage with moveable hinge 2340, e.g., one of a pair of symmetrical mounting plates 2340 coupled to opposite lateral sides of storage compartment 2330. That is, moveable hinge 2340 is configured to rotate relative to mounting plate 2308 about a pivot point 2312 (FIG. 23-11).

In the example shown in FIG. 23-5, mounting plate 2308 defines a plurality of vertical slots 2314. Vertical slots 2314 are configured to receive vertical-adjustment screws 2318 that retain mounting plate 2308, and accordingly, storage compartment 2330, in place at a desired height relative to sink module 2336.

As shown in FIG. 23-8, mounting plate 2308 is coupled to a control rod 2322. Control rod 2322 includes a horizontal bar capped on either end with a toothed gear. The toothed gears are configured to engage with a geared track 2324 (FIG. 23-11) defined by moveable hinge 2340. Control rod 2322 provides structural support to storage compartment 2330, and is configured to evenly distribute an applied force along the horizontal direction (e.g., parallel to a central axis of control rod 2322). In this way, control rod 2322 ensures that a user can press inward on storage compartment 2330 at any horizontal location to release the latch and open the compartment. Without control rod 2322, a pressure applied to storage compartment 2330 could, in some instances, cause compartment 2330 to merely bend or flex without actually opening.

As shown in FIG. 23-9, mounting plate 2308 includes a locking mechanism 2326. Locking mechanism 2326 enables a user to press inward on storage compartment 2330 to close the compartment, and locking mechanism 2326 will retain compartment 2330 in the “closed” position. Also shown in FIG. 23-9 is a one-way damper 2328. One-way damper 2328 includes a gear configured to engage with geared track 2324 (FIG. 23-11) defined by moveable hinge 2340. Rotational friction of one-way damper 2328 resists the motion of moveable hinge 2340 relative to mounting plate 2308, thereby slowing an “opening” motion of storage compartment 2330.

FIG. 24 depicts a nineteenth example sink system 2410 that may be integrated within kitchen environment 100 of FIG. 1-1. Sink system 2410 is an example of sink system 110 of FIGS. 1-1 and 1-2, apart from any differences explicitly noted herein. In particular, sink system 2310 includes an example countertop-mounted apparatus 2400 configured to both aggregate and discreetly conceal a plurality of air gaps 2402 associated with various appliances, such as dishwasher(s), within smart-kitchen environment 100 of FIG. 1-1. In general, air gaps 2402 are small fittings configured to prevent contaminated water from re-entering a kitchen appliance via backflow. While countertop-mounted apparatus 2400 can assume the general appearance and/or functionality of any suitable kitchen component and/or appliance, in the example shown in FIG. 24, countertop-mounted apparatus 2400 is depicted as a soap dispenser. Soap dispenser 2400 defines an internal alcove 2404 that is accessible from the bottom exterior, wherein a plurality of air-gap pipes valves 2402 can be inserted.

In some examples, each of air-gap pipe(s) 2402 is operably coupled to a different kitchen appliance within smart-kitchen environment 100, such as a dishwasher, a sink module, etc. In such examples, each connected pipe 2402 acts as a conventional air gap for its respective connected appliance. In some examples of sink system 2410, all air-gap pipes 2402 within kitchen environment 100 are conveniently accessible at a common location within soap dispenser 2400. As needed, a top portion 2406 of soap dispenser can be removed to access any or all of air-gap pipes 2402, e.g., for maintenance and/or replacement. In this way, each air gap 2402 can be accessed, inspected, detached, cleaned, and/or updated as needed from a common juncture.

FIG. 25 depicts a twentieth example sink system 2510 that may be integrated within kitchen environment 100 of FIG. 1-1. Sink system 2510 is an example of sink system 110 of FIGS. 1-1 and 1-2, apart from any differences explicitly noted herein. In particular, sink system 2510 includes an example “stowable” apparatus 2500 configured to both aggregate and discreetly conceal a plurality of air gaps 2502 associated with various appliances, such as dishwasher(s), within smart-kitchen environment 100 of FIG. 1-1. In general, air gaps 2502 are small fittings configured to prevent contaminated water from re-entering a kitchen appliance via backflow.

Apparatus 2500 defines an internal recessed alcove 2504 that is accessible from any side exterior of apparatus 2500. Recessed alcove 2504 is configured such that a plurality of air-gap pipes or valves 2502 can be retained therein. Air-gap pipes 2502 can include piping connected to relevant appliances (such as a dishwasher, a sink, etc.), wherein each connected pipe 2502 acts as a conventional air gap to the respective connected appliance.

Apparatus 2500 is configured to be “stowed” below a countertop 2540 within kitchen environment 100, or situated within a suitable crevice within smart-kitchen environment 100. Further, apparatus 2500 can be operably connected to a button, lever, or other actuator configured to retrieve apparatus 2500 above-deck, as needed. For instance, apparatus may be spring-loaded such that pressing downward on the top surface 2506 causes apparatus 2500 to “pop” up out of its concealed location. Conversely, once the user is done using apparatus 2500, the user can press downward on top surface 2506 (or use another actuator) to stow apparatus 2500 back below countertop 2540.

FIG. 26 is a perspective view of a twenty-first example sink system 2610 that may be integrated within kitchen environment 100 of FIG. 1-1. Sink system 2610 is an example of sink system 110 of FIGS. 1-1 and 1-2, apart from any differences explicitly noted herein. In particular, sink system 2610 includes an example solenoid-based drying system 2600. Drying system 2600 includes a produce basin 2628 configured to be covered or sealed by a basin lid 2632 during an automatic wash cycle. For instance, drying system 2600 can include a plurality of magnetic solenoids 2624 that, when activated or energized, magnetically seal basin lid 2632 over top of produce basin 2628 for the duration of the automatic washing cycle.

At the end of the automatic washing cycle, drying system 2600 is configured to selectively deactivate solenoids 2624, as appropriate, to break the magnetic seal between basin lid 2632 and produce basin 2628. In some such examples, drying system 2600 can selectively activate other ones of magnetic solenoids 2624 to vertically raise and/or horizontally slide basin lid 2632 away from produce basin 2628, thus enabling airflow through basin 2628 to ventilate and dry the newly cleaned objects (e.g., produce 2640, dishes, etc.) placed therein.

FIG. 27 illustrates a twenty-second example sink system 2710 that may be integrated within kitchen environment 100 of FIG. 1-1. Sink system 2710 is an example of sink system 110 of FIGS. 1-1 and 1-2, apart from any differences explicitly noted herein. In particular, sink system 2710 includes an example drying system 2700. Drying system 2700 includes a produce basin 2728, e.g., configured to retain produce 2740 during and after an automatic wash cycle of sink system 2710, and an ozone generator 2708 (e.g., ozone generators 308, 1308, as detailed above).

Upon completion of an automatic wash cycle of sink system 2710, either by forced manual input or through natural end of the predetermined cycle, ventilation and sanitization can occur. Drying system 2700 activates ozone generator 2708 and fans 2724 to generate and blow purifying ozone gas through produce basin 2728 such that the ozone gas further sanitizes produce 2740 held within produce basin 2728.

FIG. 28 illustrates a twenty-third example sink system 2810 that may be integrated within smart-kitchen environment 100 of FIG. 1-1. Sink system 2810 is an example of sink system 110 of FIGS. 1-1 and 1-2, apart from any differences explicitly noted herein. In particular, sink system 2810 includes an ozone-purifier system 2800 configured to sanitize water 2801 dispensed from faucet 2850.

Ozone-purifier system 2800 includes a conventional ozone-generation unit 2808 (e.g., ozone generators 308, 1308), and a flow meter 2822, both operably coupled to faucet 2850. Ozone generator 2808 can be removably affixed in a recessed location below countertop 2840. Flow meter 2822 is configured to monitor an amount (e.g., flowrate, fluid volume, mass, etc.) of water dispensed from faucet 2850. Based on data received from flow meter 2822, ozone generator 2808 is configured to determine, generate, and infuse a specific amount of ozone gas, e.g., in direct proportion to the amount of water dispensed from faucet 2850. In this way, ozone-purifier system 2800 is configured to precisely control the ozone concentration of the ozone-purified water dispensed by sink system 2810.

Additionally or alternatively, ozone-purifier system 2800 can include a fill-level sensor 2824 configured to monitor a volume of water retained within sink basin 2836. Based on data received from fill-level sensor 2824, ozone generator 2808 is configured to determine, generate, and infuse a specific amount of ozone gas, e.g., in direct proportion to the amount of water held within sink basin 2836. In this way, ozone-purifier system 2800 is configured to precisely control the ozone concentration of the ozone-purified water retained within sink basin 2836. Alternately or in addition, ozone generator 2808 can automatically start and cease ozone production based on, for example, selected wash cycles for rinsing produce or other objects within basin 2836, wherein each selectable wash cycle corresponds to a different target ozone concentration in the water.

FIG. 29 illustrates a twenty-fourth example sink system 2910 that may be integrated within kitchen environment 100 of FIG. 1-1. Sink system 2910 is an example of sink system 110 of FIGS. 1-1 and 1-2, apart from any differences explicitly noted herein. In general, sink system 2910 includes a pressure-controlled produce-washing system 2900. More specifically, washing system 2900 includes a water-control apparatus 2906, and one or more fluid-pressure sensors 2922 that enable washing system 2900 to precisely monitor and control water streams 2901 during various selectable produce-washing cycles.

Washing system 2900 can be particularly tailored to monitor and control water pressure, specifically regarding water 2901 dispensed via spray nozzles 2914 of spray-bar 2912. In some examples, water pressure of fluids flowing through plumbing 2907 can also be monitored and controlled. For instance, plumbing 2907 can include at least an inlet valve 2908 and an automatic pressure-release valve 2916. Washing system 2900 can receive processed signals from a control unit 2920 that enables a user to configure various parameters for water 2901 dispensed via spray bar 2912, including at least water pressure and water temperature and water pressure.

Control unit 2920 can be configured to enable users to select from a plurality of water pressure options, wherein each water pressure option corresponds to a distinct water cycle, such that water 2901 is dispensed according to specific velocities and for specific pulses based on user selection. Once the user has made a selection via control unit 2920, control unit 2920 transmits a signal to water-control apparatus 2906, which is configured to receive the processed signal and perform a corresponding action, such as regulating water pressure through water plumbing 2907 via allowing increased water flow via inlet valve 2908 or indicating that pressure release via valve 2916 is needed. Moreover, water-control apparatus 2906 is configured to communicate with sink module 2936 (e.g., sink basin 2928) and spray bar 2912, wherein each intelligent feature of system 2900 works in harmony to dispense water 2901 according to the user-selected duration and pulse for the appropriate water cycle, thereby enabling any objects within produce basin 2928 (such as, for example, fresh produce) to receive appropriate pulsed and timed water 2901.

FIG. 30 illustrates a twenty-fifth example sink system 3010 that may be integrated within kitchen environment 100 of FIG. 1-1. Sink system 3010 is an example of sink system 110 of FIGS. 1-1 and 1-2, apart from any differences explicitly noted herein. In particular, sink system 3010 includes an automatic sink-basin-fill system 3000. System 3000 further includes an automated soap-dispensing apparatus 3024 and water-flow and temperature controls via digital valve 3008 coupled below countertop 3040.

System 3000 can include an intelligent sink module 3036 with a basin 3028, a faucet 3050, an intelligent soap-dispensing apparatus 3024, and an intelligent water-control apparatus 3006. System 3000 can further include a level sensor 3016, which can be operably coupled to or within basin 3028. Level sensor 3022 can include or be coupled to an automated drain 3002, and can be set to automatically regulate the fill level of the basin 3028. Level sensor 3022 can maintain a predetermined level or depth of water within basin 3028 and maintain a predetermined temperature or range of temperatures of the water. Basin 3028 automatically monitors changes to water temperature within its interior and adjusts the water temperature dispensed from faucet 3050 accordingly. For example, basin 3028 can adjust the water temperature coming out of faucet 3050 based on a remaining fluid volume necessary to achieve the correct final desired fill-state based on different ambient temperatures. The predetermined fill-level and predetermined temperatures can be changed to new set values, in which case basin 3028 dynamically changes its status to achieve the new set values. For maintaining water temperature once the water level is already at its target fill level, a calculated volume of water is automatically drained from basin 3028 and an equivalent replacement volume is added back to basin 3028 to maintain the temperature, as the water is affected by the ambient environment over time. The fill level that is maintained by level sensor 3022 can be based on preferences and identification of the user.

FIG. 31-1 is a conceptual block diagram of a twenty-sixth example sink system 3110 that may be integrated within smart-kitchen environment 100 of FIG. 1-1. Sink system 3110 is an example of sink system 110 of FIGS. 1-1 and 1-2, apart from any differences explicitly noted herein. In particular, sink system 3110 includes a produce-washing system 3100 specifically configured to detect and eliminate toxic chemicals, such as pesticides.

In general, produce-washing system 3100 is configured to execute an automated cleaning cycle designed to reduce the detectable level of pesticides below a predetermined threshold level. As shown in FIG. 31-1, sink system 3110 includes a sink module 3136 defining at least one cleaning basin 3128 with a drain outlet 3120.

Sink system 3100 includes one or more sensors 3122, such as pesticide sensors, positioned at locations within cleaning basin 3128 configured to be submerged by fluid 3101 (e.g., water, cleaning solution, etc.) during a cleaning cycle. As one non-limiting example, pesticide sensors 3122 can use spectroscopy to detect pesticides or other contaminants in cleaning fluid 3101.

FIG. 31-2 is a flowchart illustrating an example automated cleaning cycle performed by washing system 3100 of FIG. 31-1. At step 3150, in response to a certain condition being met, washing system 3100 initiates the cleaning cycle. For instance, a user can manually initiate the cleaning cycle. As another example, washing system 3100 can initiate the cleaning cycle at a predetermined time of day.

At step 3152, washing system 3100 at least partially fills cleaning basin 3128 with a cleaning fluid 3101, such as tap water, soapy water, ozonated water, or another cleaning fluid. Meanwhile, the user places produce 3140, or other objects to be cleaned, within cleaning basin 3128, either while cleaning basin 3128 is still empty, while cleaning basin 3128 is filling with cleaning fluid 3101, or while cleaning basin 3128 is filled to a maximum or predetermined level.

At step 3154, washing system 3100 is configured to monitor the level of cleaning fluid 3101 within cleaning basin 3128, e.g., via a flow meter 3132. Flow meter 3132 measures the volume of cleaning fluid 3101 dispensed into cleaning basin 3128, and causes washing system 3100 to automatically cease output of cleaning fluid 3101 once a threshold level is reached. The threshold level of cleaning fluid 3101 may be predetermined, or automatically determined by washing system 3100 based on, for example: the number and/or volume of objects 3140 positioned within cleaning basin 3128, a desired fluid volume, or other factors. Additionally or alternatively to flow meter 3132, in some examples, washing system 3100 includes a fluid-level detector 3134 coupled within cleaning basin 3128. In some such examples, fluid-level detector 3234 senses the amount of cleaning fluid 3101 within cleaning basin 3128, e.g., based on a fluid pressure measured at or near base 3108 of cleaning basin 3128.

At (optional) step 3156, washing system 3100 measures a ratio between the volume of objects 3140 and the amount of cleaning fluid 3101 within basin 3128, in order to determine whether a potential concentration of pesticides (e.g., as measured in parts per million, or “ppm”) rinsing off of objects 3140 would even be detectable by pesticide sensor 3122. For instance, too little or few objects 3140 within cleaning basin 3128 may not provide sufficient pesticide content to enable pesticide sensor 3122 to register an accurate measurement of pesticide within cleaning fluid 3101.

At step 3158, washing system 3100 initiates an agitation cycle in which an automated agitation device 3138, such as a fan, impeller, blender, or the like, is activated to stir, vibrate, or otherwise agitate cleaning fluid 3101 to clean objects 3140 within cleaning basin 3128. In some examples, the agitation cycle may remove pesticides from objects 3136.

At step 3160, pesticide sensor 3122 measures the pesticide concentration within cleaning fluid 3101. At step 3162, based on the measured pesticide concentration, washing system 3100 may drain cleaning fluid 3101. For instance, should the pesticide concentration exceed a threshold value, washing system 3100 may drain cleaning fluid 3101 through drain 3120, and refill cleaning basin 3128 with fresh cleaning fluid 3101 (step 3152). Additional fluid fill/drain/refill and agitation cycles may be run until the pesticide concentration falls below the predetermined threshold, i.e., repeating steps 3152, 3154, 3158, 3160, 3162.

A pesticide concentration below a predetermined threshold may indicate that at least a substantial majority of detectable pesticides have been rinsed from objects 3140, at which point washing system 3100 automatically drains cleaning basin 3128 (step 3162) and terminates the automatic washing cycle (step 3164).

FIG. 32-1 is a perspective view of a twenty-seventh example sink system 3210 that may be integrated within smart-kitchen environment 100 of FIG. 1-1. Sink system 3210 is an example of sink system 110 of FIGS. 1-1 and 1-2, apart from any differences explicitly noted herein. In particular, sink system 3210 includes an integrated input panel 3260. Input panel 3260 includes one or more touch-sensitive buttons 3200 configured to easily control a respective aspect, feature, or function of sink system 3210 with a single touch by a user. For instance, touch button(s) 3200 may be used to activate a predetermined wash cycle for sink system 3210. In some examples, touch button(s) 3200 may be used to configure individual wash-cycle settings of sink system 3210.

In some examples, input panel 3260 may include a status light 3212. In some examples, an activation of status light 3212 (e.g., a color, a particular flashing pattern, etc.) may indicate a particular status of a wash cycle. In other examples, activation of status light 3212 may indicate an error detected by sink system 3210.

FIG. 32-2 is an exploded cross-sectional view of sink system 3210 of FIG. 32-1. In the example shown in FIG. 32-2, sink system 3210 includes a substantially planar sheet of material, such as stainless steel, that forms a top surface 3202 of the sink basin. An underside of sink surface 3202 defines a plurality a number of milled-out areas 3204, wherein a thickness of the planar sheet of material 3202 is substantially reduced at those locations.

A printed circuit board (PCB) 3206 includes a plurality of capacitive sensor(s) 3208 coupled to the top surface. PCB 3206 can then be coupled to the underside of sink surface 3202 such that capacitive sensors 3208 fit upward into the milled-out regions 3204. For instance, the underside of sink surface 3202 can include mounting hardware 3214, such as threaded bosses, configured to operably and removably couple PCB 3206 to sink surface 3202. Mounting hardware 3214 is configured to retain capacitive sensors at the height necessary to ensure proper functionality, while preserving serviceability. Milled-out regions 3204 allow for proper deflection of metal surface 3202, ensuring that capacitive sensors 3208 can operate as intended. That is, the substantially thinner sections 3204 of metal surface 3202 that form buttons 3200 are configured to elastically flex or bend downward when “pressed” by a user. In this way, the buttons 3200 make contact with or are within a capacitive sensing zone of the respective capacitive sensors 3208 just below, thus triggering an input to the system.

Now referring to FIGS. 33-1 to 33-5, an example of an integrated capacitive sensing system 3300 includes a substantially planar sheet of material, such as stainless steel, that forms a top surface of the sink basin and an input panel 3302, such as the panel 3202 described above. As shown in FIGS. 33-1 and 33-2, an underside of panel 3302 defines a plurality a number of milled-out areas or cavities 3304, wherein a thickness of the panel 3302 is substantially reduced at those locations. A steel disk 3306 is screwed into each cavity 3304, the position of which can be raised or lowered within cavity 3304, depending on use and preference. As depicted in FIGS. 33-3 and 33-4, PCB 3308 includes an insulative panel 3310 and a plurality of conductive copper circular pads 3312 that are electrically connected to a capacitive touch sensing primary control unit (not shown). The pads 3312 are actively driven by the primary control unit and thus act as sensing elements.

As depicted in FIG. 33-5, panel 3302 is placed over PCT 3308 such that disks 3306 align over one or more pads 3312. Spacers can be included on each end of panel 3302 or the position of disks 3306 can be varied to create a thin dielectric air gap between the disks 3306 and pads 3312, the combination of which acts as a capacitor. As buttons (not shown) or etchings on a top surface of panel 33012 are pressed, mechanical deflection or flexing of panel 3302 pushes the corresponding conductive disk 3306 downward into the air gap which causes a change in capacitance. The change in capacitance is read by the primary control unit that detects the active touch, and signals an input to the sink system to easily control a respective aspect, feature, or function, as described in other examples.

It should be understood that the individual operations used in the methods of the present teachings may be performed in any order and/or simultaneously, as long as the teaching remains operable. Furthermore, it should be understood that the apparatus and methods of the present teachings can include any number, or all, of the described examples, as long as the teaching remains operable.

Various examples of systems, devices, and methods have been described herein. These examples are given only by way of example and are not intended to limit the scope of the claimed inventions. It should be appreciated, moreover, that the various features of the embodiments that have been described may be combined in various ways to produce numerous additional embodiments. Moreover, while various materials, dimensions, shapes, configurations and locations, etc. have been described for use with disclosed embodiments, others besides those disclosed may be utilized without exceeding the scope of this disclosure.

Persons of ordinary skill in the relevant arts will recognize that the subject matter hereof may comprise fewer features than illustrated in any individual embodiment described above. The embodiments described herein are not meant to be an exhaustive presentation of the ways in which the various features of the subject matter hereof may be combined. Accordingly, the embodiments are not mutually exclusive combinations of features; rather, the various embodiments can comprise a combination of different individual features selected from different individual embodiments, as understood by persons of ordinary skill in the art. Moreover, elements described with respect to one embodiment can be implemented in other embodiments even when not described in such embodiments unless otherwise noted.

Although a dependent claim may refer in the claims to a specific combination with one or more other claims, other embodiments can also include a combination of the dependent claim with the subject matter of each other dependent claim or a combination of one or more features with other dependent or independent claims. Such combinations are proposed herein unless it is stated that a specific combination is not intended.

Any incorporation by reference of documents above is limited such that no subject matter is incorporated that is contrary to the explicit disclosure herein. Any incorporation by reference of documents above is further limited such that no claims included in the documents are incorporated by reference herein. Any incorporation by reference of documents above is yet further limited such that any definitions provided in the documents are not incorporated by reference herein unless expressly included herein.

For purposes of interpreting the claims, it is expressly intended that the provisions of 35 U.S.C. § 112(f) are not to be invoked unless the specific terms “means for” or “step for” are recited in a claim.

	Number	Date	Country
	63478046	Dec 2022	US
	63583636	Sep 2023	US

KITCHEN ENVIRONMENT WITH ENHANCED USER EXPERIENCE AND ACCESSORIES

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS-REFERENCE TO RELATED APPLICATIONS

Provisional Applications (2)