Device, system and method for dispensing a liquid

The smart irrigation device addresses the reliability issues of automatic irrigation systems by using local data storage and real-time clock functionality to operate independently and synchronize data, ensuring continuous and efficient watering even without internet access.

WO2024245552A1PCT designated stage expired Publication Date: 2024-12-05AMANN RAPHAEL
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2023/064620
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-31
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

Existing automatic irrigation systems require an internet connection to operate and transmit data, leading to disruptions if the connection is interrupted, and data loss during power failures or battery changes, making them unreliable for independent operation, especially for small plants with individual watering needs.

Method used

A smart irrigation device with a non-volatile data memory and real-time clock that stores user-defined operating data locally, allowing it to operate independently and send warnings without internet access, using sensors to adjust irrigation times and log data for later transmission.

Benefits of technology

Ensures reliable and timely irrigation operations even without internet connectivity, preventing data loss during power outages and allowing for remote monitoring and data synchronization when connections are restored.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2023064620_05122024_PF_FP_ABST
    Figure EP2023064620_05122024_PF_FP_ABST
Patent Text Reader

Abstract

The invention relates to a device for dispensing a liquid, wherein the device comprises at least one housing (1), a dispensing means (2) protruding from the housing (1) for dispensing liquid, a conveying unit (3) provided in or on the housing (1) for conveying liquid from a reservoir (4) to the dispensing means (2), and a control unit (5) accommodated in the housing (1) for controlling the conveying unit (3), wherein the device has a non-volatile data memory (6) and a real-time clock (7), wherein the control unit (5) is configured to query operating data for the operation of the conveying unit (3) from an external server (9), to store this operating data on the non-volatile data memory (6), and to operate the conveying unit (3) as a function of a comparison of the stored operating data with a timestamp of the real-time clock (7).
Need to check novelty before this filing date? Find Prior Art

Description

Device, system and method for dispensing a liquid

[0001] The present invention relates to a device for dispensing a liquid, wherein the device comprises at least a housing, a dispensing element projecting from the housing for dispensing liquid, a conveying unit provided in or on the housing for conveying liquid from a reservoir to the dispensing element, and a control unit housed in the housing for controlling the conveying unit. The invention further relates to a system comprising a device for dispensing a liquid and methods for controlling such a device. State of the art

[0002] Devices for dispensing liquid are generally known from the prior art. In particular, so-called irrigation controllers can be used for the automatic watering of plants, which trigger the dispensing of liquid based on moisture measurements (JPH0654629 A, CN109220738 A, W02006070784 A1). Some of these irrigation controllers can also communicate with other devices via a network to exchange operating data—such as watering times, enabling remote operation—or to inform users about necessary or completed watering.

[0003] Irrigation systems are often used for the fully automated watering of larger gardens, landscaped areas, or parks. For potted plants, however, irrigation systems are primarily intended to ensure a reliable water supply during extended periods of absence. These systems can be equipped with a battery or rechargeable battery to power their electronic components, particularly the pump. The pump itself can be operated based on user-defined parameters, which may be stored on a server. Log data about the pump's operation and other information can also be transmitted from the irrigation system to the server, allowing for monitoring and analysis of the watering process.

[0004] The problem is that an internet connection is absolutely necessary for the operation of these irrigation controllers and for the transmission of log data. If this connection is interrupted, the required operating data cannot be accessed, and no data can be transmitted from the irrigation controller to the server. Furthermore, in the event of a power outage or battery replacement, log data that has not yet been transmitted to the server may be lost. Object of the invention

[0005] The present invention therefore aims, among other things, to avoid the aforementioned disadvantages. In particular, it seeks to provide a smart, automatic irrigation system for small plants, comprising several independent irrigation units. It should be possible to supply multiple plants according to their individual needs. The operating settings should be predefined by a user and changeable at any time. Furthermore, the irrigation processes should be logged and their analysis made possible. Furthermore, it should be ensured that the irrigation system can still be operated based on user-defined operating data even if the internet connection or power supply is interrupted. Additionally, warnings should be able to be transmitted to the user if a critical liquid level is reached. Further objectives of the invention will become apparent from the description and the figures. Description of the invention

[0006] One object of the invention is solved by a device for dispensing a liquid, wherein the device comprises at least a housing, a dispensing means projecting from the housing for dispensing liquid, a conveying unit provided in or on the housing for conveying liquid from a reservoir to the dispensing means, and a control unit housed in the housing for controlling the conveying unit, wherein the device has a non-volatile data storage device and a real-time clock, wherein the control unit is configured to query operating data for the operation of the conveying unit from an external server, to store this operating data on the non-volatile data storage device, and to operate the conveying unit depending on a comparison of the stored operating data with a timestamp of the real-time clock.The control unit comprises (or is configured as) a data processing unit that is configured to carry out a computer-implemented method. In the context of the present invention, "operating data" can be understood to mean all data necessary for the operation of the device, in particular the conveying unit. For example, the operating data can include one or more times at which irrigation (i.e., liquid dispensing) is to take place, as well as one or more pieces of information associated with the respective irrigation time, such as an irrigation duration and / or an irrigation quantity. By storing the operating data on the device's non-volatile data storage, it becomes possible to operate the device according to the user-defined operating settings even when no access to the server is possible.This situation can occur particularly due to an interrupted internet connection; the device can then access the operating data stored in the data storage device – and thus locally – and continue to operate the pumping unit as intended. Furthermore, the design of the data storage device as a non-volatile data storage device ensures that the stored operating data is not lost in the event of a power interruption. Thanks to the real-time clock, the device according to the invention has an intrinsic timing mechanism that enables the timely execution of the predefined irrigation actions (liquid dispensing) even without any external contact, such as with the server or another server (NTP server) or a user's terminal device.The device according to the invention thus represents a compact, self-contained irrigation system that is largely independent of external influences. It can be remotely controlled based on user-defined operating data and can continue to operate even with an interrupted internet connection or power supply. Unlike the prior art, where operating data is either specified directly on the device, for example via a control panel, and stored (only) locally, or where operating data is stored (only) on a server or terminal device and continuously queried by the device, the device according to the invention accesses both the operating data stored on the server and the locally stored data. This enables particularly reliable operation of the device and a reliable supply of liquid (e.g., water) to plants, for example. The irrigation process can then be carried out... For example, it can be triggered whenever an irrigation time specified in the operating data matches the current timestamp of the real-time clock, or when the current timestamp has exceeded this irrigation time (since the last synchronization). The device can generally include an energy storage device (battery, rechargeable battery) and / or an energy source (e.g., a photovoltaic module); alternatively or additionally, the device can be equipped with connections for connection to an external power supply. In particular, the housing can have two sockets (or plugs), with the device itself being powered via the first of the two sockets, and the second of the two sockets providing the possibility of powering another device, particularly one according to the invention, via a connecting cable.For this purpose, the two sockets can be short-circuited, so that the same voltage is applied to both sockets.

[0007] According to a preferred embodiment of the device according to the invention, the control unit is configured to operate the conveying unit based on a measurement from at least one sensor of the device and / or at least one sensor connected to the device. Irrigation times, which are predetermined according to the queried and stored operating data, can be brought forward, postponed, and / or changed. In other words, the control unit can generate operating signals for the conveying unit based on the measurements of these sensors.

[0008] According to a preferred embodiment of the device according to the invention, the control unit is configured to query the current time from the external server or from another external server, such as a (regional) NTP server, and to update the real-time clock using this current time. Preferably, this current time is queried together with or simultaneously with the query of the operating data for the operation of the pumping unit. This ensures that the real-time clock and the server time underlying the input of the operating data are synchronized—except for predefined deviations. In particular, it can be provided that synchronization only occurs when a predefined difference is exceeded between the current time queried from the server and a (corresponding) current timestamp of the real-time clock. In this way, the timeliness of the desired irrigation actions can be ensured.

[0009] According to a preferred embodiment of the device according to the invention, the control unit is configured to update the real-time clock only in the event of a predetermined deviation of a current timestamp of the real-time clock from the current time. This ensures energy-efficient and economical operation of the device according to the invention.

[0010] According to a preferred embodiment of the device according to the invention, the control unit is configured to log the operation of the conveying unit. The control unit can record and / or store log data about the operation of the conveying unit. This makes it possible to collect, forward, and / or statistically process information about completed irrigation processes. The user can also monitor whether the irrigation actions they have specified have been carried out (in a timely manner). In the context of plant irrigation, this also allows for a comparison of the amount and frequency of irrigation with the condition of the plant.

[0011] According to a preferred embodiment of the device according to the invention, the control unit is configured to transmit log data about the operation of the conveyor unit to the external to transmit data to a server. This enables remote monitoring of irrigation operations as well as centralized collection and evaluation of the log data from one or more devices. Therefore, the device according to the invention is versatile in its applications.

[0012] According to a preferred embodiment of the device according to the invention, the control unit is configured to store or temporarily store log data about the operation of the conveying unit on the non-volatile data storage device. This enables the (local) backup of the log data when transmission of this log data to the server is not currently possible, for example, in the event of an interrupted connection to the server and / or after a power supply interruption. In particular, the log data can be temporarily stored on the device's non-volatile data storage device until it can be successfully transmitted to the server—for example, during the transmission of log data from a subsequent irrigation operation or a later operation of the conveying unit.

[0013] According to a preferred embodiment of the device according to the invention, the control unit is configured to delete log data from the non-volatile data storage after its transmission to the external server. According to this embodiment, the device's non-volatile data storage can only be used as temporary storage for the log data. In principle, a log data record can be transmitted after completion of the respective irrigation operation or after the operation of the pumping unit has ceased; only if this transmission is not possible or unsuccessful can this log data record be temporarily stored locally and transmitted after the connection to the server has been re-established.For example, attempts can be made at periodic intervals to transfer data records stored on the non-volatile data storage to the server; alternatively or additionally, a check can be performed during (or shortly before) the transmission of a later log data record to see if older log data is present on the non-volatile data storage, and any such older log data can then be transmitted to the server along with the later log data record. Overall, this allows the device to be designed in a particularly simple and cost-effective manner, while simultaneously enabling complete and seamless monitoring of irrigation operations. The device is therefore particularly well-suited for applications where precise and reliable dosing of the liquid to be dispensed is necessary or advantageous.

[0014] In principle, the device according to the invention can be used not only in connection with plants, in particular potted plants, gardens, garden facilities or parks, but also, for example, in connection with swimming pools (dispensing chemicals, bath water treatment), with the dispensing of sugar water for beehives, with the dispensing of liquid fish food or the supply of other living beings with a nutrient solution, with the spraying of liquid fragrances for the scenting of rooms, or with the application of pesticides / insect repellents.

[0015] According to a preferred embodiment of the device according to the invention, the device comprises a microcontroller, preferably one capable of WWAN and / or WLAN. Particularly preferably, this microcontroller or the control unit includes means for integrating the device into a wireless network in order to communicate with external devices (servers, end devices, other irrigation controllers).

[0016] Wireless Local Area Network (WLAN or Wireless LAN) refers to a local wireless network, usually referring to a standard from the IEEE 802.11 family. Wireless Wide Area Network (WWAN) refers to a wide wireless network. It is the wireless equivalent of a WAN (Wide Area Network). Unlike WLAN (Wireless Local Area Network), WWAN covers greater distances (outdoors). The signals are transmitted outdoors via electromagnetic waves from antenna masts. The term WWAN encompasses, among others, the wireless network types WiMAX, GSM, UMTS, and LTE. They are currently used primarily for mobile phones, tablet computers, and laptops. The device according to this embodiment is characterized by a particularly simple communication capability with external devices, especially with the server and / or the user's terminal device.The data required for the operation of the device (operational data) can be stored in a database and managed appropriately, allowing the device's control unit to ultimately query and synchronize this data via Wi-Fi (or another suitable wireless network) using an API (application programming interface). Irrigation processes (irrigation actions, operation of the pumping unit) can also be logged or transmitted for display in a web interface. Alternatively or additionally, other wireless networks can be used, or the device can be integrated into other wireless networks. Furthermore, integration into cloud environments is also conceivable. For example, Narrowband Internet of Things (NB-IoT) and / or Long Range Wide Area Network (LoRaWAN) can be used.

[0017] According to a preferred embodiment of the device according to the invention, the device comprises a field-effect transistor for controlling the dispensing unit, preferably for voltage-dependent control of the dispensing unit and / or for controlling a dispensing speed and / or dispensing duration of the dispensing unit, wherein the field-effect transistor is preferably connected between the microcontroller and the dispensing unit. The field-effect transistor can be a metal-oxide-semiconductor field-effect transistor (MOSFET). In this way, particularly precise control of the dispensing unit or precise metering of the dispensed liquid is enabled. At the same time, the design of the device according to the invention can be kept as simple as possible.

[0018] According to a preferred embodiment of the device according to the invention, the device comprises an operating element, in particular a push button, to enable manual operation of the control unit and / or the conveying unit. The operating element can be actuated from outside the housing. In addition to remote control or fully automated control of the device based on the operating data stored on the server, this embodiment enables manual control of the control unit and / or the conveying unit. For example, the conveying unit can be directly put into operation or switched on and / or off by actuating the operating element. Additionally or alternatively, a reset of the control unit, an initialization of the operating system, a configuration of the captive portal, and / or a switching on and / or off of the device or the control unit can also be forced by actuating the operating element.Furthermore, information can also be displayed on any display of the device after the control element has been activated.

[0019] According to a preferred embodiment of the device according to the invention, the conveying unit is formed by a pump, in particular by a peristaltic pump. By using a With a peristaltic pump, the amount of fluid dispensed can be controlled very easily and precisely; moreover, this embodiment is characterized by a particularly cost-effective design. The pump can be easily integrated into or attached to the housing. Mounting the pump, especially the peristaltic pump, on the outside of the housing has the advantage of enabling particularly easy maintenance and allowing for quick repairs and replacement of a defective pumping unit. Furthermore, a suction-side connection of the pump accessible from outside the housing allows for a particularly simple fluidic connection to the reservoir; in particular, a hose can be positioned with one end in the reservoir and its other end easily connected to the suction port of the pump, especially the peristaltic pump.This increases the user-friendliness of the device. Alternatively or additionally, the pumping unit can include a valve, such as a solenoid valve or a ball valve, which is located upstream and / or downstream of the pump. Alternatively or additionally, the pumping unit can be designed with a valve that can be connected to a water supply, particularly an external one (water line). This further simplifies the design of the device.

[0020] According to a preferred embodiment of the device according to the invention, the non-volatile data storage is formed by an EEPROM. An EEPROM (abbreviation for electrically erasable programmable read-only memory) 2PROM (Process-in-Time Memory Module) is a non-volatile electronic memory chip whose stored information can be electrically erased. This design has the advantage that data cannot be lost in the event of a power interruption. Other variants of non-volatile memory are also conceivable, such as SD cards, USB flash drives, CDs, hard drives, or other removable storage media; however, it is important that data stored on the memory chip is not lost when the power supply is interrupted.

[0021] According to a preferred embodiment of the device according to the invention, the EEPROM is emulated by the microcontroller. The microcontroller can, for example, be an ESP8266 NodeMCU. This allows for a reduction in the number of electronic components without sacrificing functionality.

[0022] According to a preferred embodiment of the device according to the invention, at least one fastening means for detachably attaching the device to a container is provided on an outer surface of the housing. This makes it possible to easily attach the device to a container, such as a flowerpot. Fastening means that are preferably detachably connected to the housing have the advantage that the same housing can be used for different containers and requirements; only the fastening means need to be adapted to the respective situation. For example, one or more screw hooks can be used as fastening means if the housing is to be attached to a flowerpot, or suction cups if the device is to be attached to or in an aquarium or swimming pool. This makes the device even more versatile.

[0023] According to a preferred embodiment of the device according to the invention, the fastening element, in particular the screw hook, is fixed in position by means of projections provided on the inside of the housing. These projections can be an integral part of the housing or can be formed by separate components. In both cases, these projections enable the fixing The position and / or orientation, in particular the rotational position, of the fasteners allows for a clear and permanent determination of the optimal positioning of the fastener for the reliable attachment of the housing to the container. The length by which the fasteners protrude from the housing can also be conveniently adjusted; for this purpose, a fixing element can be provided, such as a knurled nut or similar device located outside the housing, which creates an additional positive fit between the fastener and the housing.

[0024] According to a preferred embodiment of the device according to the invention, a display for showing information is provided in or on the housing, wherein the display is connected to the control unit. In principle, storing operating data on the device and transmitting the log data to the server enables the display of information via a web interface. In addition, a display or other display means can also be provided on the housing itself to show the user specific information beyond the aforementioned option. In particular, information about upcoming irrigation processes, such as the time until the next dispensing of liquid and / or other operating data or information derived from the operating data, can be displayed on the screen. Warning messages, such as a low liquid level in the reservoir or an upcoming battery change, can also be displayed.By connecting to the control unit, the control unit can not only control the conveyor unit and receive and transmit data, but also serve as a controller for the display. This further simplifies the design of the device with regard to the required technical components.

[0025] According to a preferred embodiment of the device according to the invention, the dispensing means comprises several liquid guide elements and / or liquid guide sections that are adjustable relative to one another. This makes it possible to precisely define the point at which liquid is to be supplied to the container. The dispensing means can include the liquid guide elements, each of which can be adjusted separately, resulting in an overall path of the liquid guide elements through which the liquid can be transported from the housing to the dispensing point. Similarly, several sections of a deformable liquid line (liquid guide sections) can be separately adjusted and set to give the liquid line the desired path.

[0026] According to a preferred embodiment of the device according to the invention, the dispensing means comprises at least one nozzle. Multiple nozzles may also be provided, arranged, for example, equidistantly along a specific length of the portion of the dispensing means projecting beyond the housing. In principle, the dispensing means can have one or more outlets to dispense liquid into the container at a specific point or over a desired area. Unlike an outlet, however, a nozzle also enables the atomization of the dispensed liquid. This is particularly advantageous when using the device with potted plants. The device is thus even better suited for plant-related applications.

[0027] According to a preferred embodiment of the device according to the invention, the dispensing means comprises a hose, which is guided through an inlet opening into the housing and through an outlet opening out of the housing. Particularly preferably, the dispensing means can be formed by this hose. According to a preferred embodiment of the device according to the invention. The hose is connected to the pumping unit at one end. Preferably, the hose has a nozzle or outlet at its other end. This allows for a particularly simple, reliable, and maintenance-friendly design of the dispensing medium, especially in embodiments where the pumping unit is located on the outside of the housing rather than inside. In this case, the hose connected to the pressure port of the pumping unit, particularly the peristaltic pump, can simultaneously form the dispensing medium. For this purpose, the hose can first be guided from the pressure port through the inlet opening into the interior of the housing, optionally secured there, and finally led back out of the housing through the outlet opening. The section of hose protruding from the housing can then form the dispensing medium. This further simplifies the design of the device.

[0028] In principle, the housing can be designed to be (splash-)proof or sealed to prevent water from entering and / or escaping the housing. The inlet and outlet openings can also have appropriate seals to ensure a (largely) watertight connection for the hose.

[0029] One object of the invention is solved by a system comprising at least one device according to one of the embodiments described above and the server. The device and server are connected to each other, or a connection between the device and the server can be established. In particular, the device has the task of executing irrigation actions based on the predefined operating data, especially at the times specified therein. For the purpose of querying (synchronizing) the operating data, the device can be connected to, or connect to, a WLAN (or other wireless network) available at the installation site and communicate via the control unit with the application programming interface (API) available via the internet.The programming interface can access the database stored on the server – also via the internet – and provide the relevant data (operating data) to the respective device of the system based on a query from the respective control unit. Furthermore, the programming interface can receive data on completed irrigation processes or on the operation of the pumping unit and forward it to the server or the database. Unlike known irrigation systems, the invention provides that operating data is not programmed directly on the device by the user.instead of having to be specified, they can be stored centrally in a database on a server; this enables a high degree of flexibility and user-friendliness of the system according to the invention, especially since not every device has to be programmed individually, but operating data for several (essentially any number) devices is stored in a (shared) database and this operating data is then queried by the respective devices or their control units.The associated problem, namely that the intended and reliable operation of the devices—and thus the timely and precisely metered dispensing of liquid—is only possible when a connection to the server exists, is avoided according to the invention by storing the queried operating data of the device locally (namely in the device's data memory); as soon as the queried operating data no longer contains any future irrigation times, a new request can be sent to the server. Then the old (processed) operating data can be deleted from the data memory or overwritten with the new data. New (currently queried) operational data will be overwritten. Log data can be handled similarly, as explained in detail above.

[0030] According to a preferred embodiment of the system according to the invention, the system further comprises an end device, wherein the end device is configured at least to transmit operating data for the operation of the conveying unit of one or more devices to the server, to manipulate operating data of one or more devices stored on the server, and / or to query operating data and / or log data of one or more devices stored on the server. The end device can preferably be a mobile device, such as a smartphone, a tablet, or a computer. Interaction with the server or the database can, in particular, take place via a web interface. This enables the user to manipulate the database via the end device (so-called "clients") by means of user input and thus to create, modify, and delete irrigation-related database resources.In this way, operational data can be created, modified, deleted, and viewed without requiring any interaction with the device itself. This makes the system particularly well-suited for applications where interaction with the devices themselves should be minimized (such as maintenance and repair) and where the user is located (far) away from the devices.

[0031] One object of the invention is solved by a method for controlling a device for dispensing a liquid, comprising at least the following method steps: a. Querying operating data for the operation of a conveying unit of the device from an external server; b. Storing the operating data on a non-volatile data storage device of the device if the query according to a. was successful; c. Checking whether operating data is stored on the non-volatile data storage device if the query according to a. was unsuccessful; d. Operating the conveying unit based on a comparison of the operating data stored (on the non-volatile data storage device) and / or queried (from the external server) with a timestamp from a real-time clock of the device;

[0032] One object of the invention is solved by a method for controlling a device for dispensing a liquid, comprising at least the following method steps: a. transmitting log data about the operation of a dispensing unit of the device to an external server; b. storing the log data on a non-volatile data storage device of the device if the transmission according to a. was unsuccessful; c. deleting the stored log files from the non-volatile data storage device after these log files have been successfully transmitted to the server.

[0033] Unlike in the prior art, the operation of the device for dispensing a liquid is not based on an operating signal transmitted, for example, from an external server or an end device; rather, the control unit controls the dispensing unit based on the Operating data is stored on the external server or in a database on the server for the respective device. This has the advantage that, after an initial query of the user-defined operating data and apart from occasional queries for updated operating data, no connection between the device and the server is necessary for the device's intended operation. Theoretically, it would therefore be conceivable that after an initial query of the user-defined operating data, which specifies the device's operation or irrigation actions for a calendar year, the connection to the server could be terminated. Nevertheless, the device could regularly, for example, daily or hourly, send a query to the server for updated operating data.In this case, if the (regular) query of operating data was unsuccessful, the device would access the operating data stored on the local data storage and operate the conveying unit based on this data. To this end, the control unit can regularly compare the operating data, for example, every second, with a current timestamp from the device's real-time clock. If there is a match or if a predetermined irrigation time is exceeded, the device can activate or operate the conveying unit for the predetermined irrigation duration (or until the predetermined quantity of dispensed liquid is reached) in order to execute the irrigation action associated with that irrigation time. Thus, the method according to the invention enables completely autonomous operation of the device once operating data has been successfully queried.Even after a power supply failure of the device according to the invention, no operating data is lost, since this data is stored on a non-volatile data storage device and is therefore not deleted when the device is not in operation or is not supplied with power.

[0034] To ensure seamless monitoring of the pumping unit's operation and thus of completed irrigation actions and processes, corresponding log data can be created and transmitted to the server. If such transmission of current log data is not currently possible, for example, because the server is unavailable or the internet connection has been interrupted, this current log data can be stored locally on the device's non-volatile data storage. As soon as a new irrigation action has been carried out and the pumping unit has been restarted, corresponding current operating data can be created again.Before attempting to transfer the current operating data to the server, the system checks whether further log data about past irrigation operations (historical log data) is stored on the data storage device. If so, the current and historical operating data are transferred to the server together. If the transfer fails, the current log data is also cached locally on the data storage device until it can be successfully transferred at a later time (e.g., after the internet connection is restored). Once the cached log data has been successfully transferred to the server, it is deleted from the data storage device to free up storage space.

[0035] A method is particularly preferred in which all of the above-mentioned steps a. to d. and a. to c. are carried out.

[0036] Preferably, the reservoir's fill level can also be monitored by the device, system, and / or methods according to the invention. For this purpose, it is provided that during or after filling the reservoir with liquid (this is usually done manually), the level of the reservoir can be monitored. The amount of liquid added (approximately 1 liter) by the user is stored in the database or on the server. This fill level can be part of the operating data and also stored locally on the device's data storage. The device's control unit, the external server, the user's device, and / or the web interface can then be configured to calculate, based on the operating data, how many of the planned (or, based on the operating data, specified) irrigation cycles the liquid in the reservoir will be sufficient for, and / or when the reservoir will need to be refilled to ensure continuous operation of the device.Unlike current technology, the reservoir level does not need to be measured or monitored (using sensors). Instead, the system can calculate when refilling is necessary based solely on operating data and the amount of liquid added (which, for example, could correspond to the reservoir's maximum capacity). A notification can then be sent to the user's device; alternatively or additionally, the current (calculated) reservoir level, along with the corresponding log data, can be transmitted to the server. Alternatively or additionally, the current level can also be calculated based on the transmitted log data (always up-to-date), and the user can be notified that refilling is required. This is particularly useful when the reservoir level falls below a predefined critical threshold.

[0037] Preferably, the dispensing device can include a sealing hose fitting on the housing instead of a flexible spout, through which the liquid-carrying hose from the pump (or peristaltic pump) can be routed and extended to the plant at any desired length, either lying on or buried in the soil. Along this length, the hose lying on the soil can be secured / fixed using plastic ground stakes.

[0038] Preferably, the device includes at least one ground stake onto which the end of the hose leading to the plant can be attached. Alternatively or additionally, the device may include a nozzle or a sieve to reduce the discharge pressure of the liquid or to improve the distribution / atomization of the discharged liquid.

[0039] Preferably, the device includes a limit switch, an ultrasonic sensor and / or other (optical or mechanical) sensors to determine whether the device is attached or suspended from a (planting) container as intended, and, if necessary (e.g., if the device has been removed from the container due to maintenance, relocation, conversion, etc., or if the device is unintentionally no longer attached to the container), to prevent the delivery of liquid or to interrupt an ongoing irrigation process (operation of the delivery unit).

[0040] Preferably, all or individual electronic components of the device can be arranged on a printed circuit board in order to make the device even more space-saving and compact.

[0041] Preferably, the housing of the device may be provided with means for emitting acoustic and / or visual signals in order to inform the user about certain circumstances (such as low water level, low battery level, other malfunctions).

[0042] Preferably, the device, in particular the control unit, includes means for communication within the local network via the MQTT protocol (Message Queueing Telemetry Transport). This allows access to relevant information (such as the reservoir level, the next scheduled irrigation, etc.) and integration of the device into a smart home environment. Other wireless standards (such as ZigBee, Thread, Matter, Z-Wave) are also possible.

[0043] Preferably, the device includes sensors for detecting environmental conditions, such as temperature, relative humidity, light intensity, and UV radiation, particularly wired / wireless accessories, such as a capacitive soil moisture sensor or a wind sensor. This enables the individual triggering of irrigation (e.g., soil moisture below 50% - irrigation of 10 ml, temperature below 20°C - irrigation of 30 ml, light intensity below 3 cd - irrigation of 25 ml). Furthermore, the logging and transmission of this environmental data for further processing on the server, as well as its retrieval via a web interface, is facilitated.

[0044] Preferably, the device includes means for manually confirming that the reservoir (water tank) has been refilled. This eliminates the need to access the web interface to confirm the refill, as this can be done directly on the device and the control unit can transmit a corresponding message to the server. Brief description of the characters

[0045] The invention will now be described in more detail using specific exemplary embodiments. However, these descriptions are neither intended to exhaustively present nor to limit the inventive concept. The following are shown: Fig. 1 shows a schematic representation of the system according to the invention. Fig. 2 shows an isometric view of the housing of the device according to the invention. Fig. 3 shows a top view of the housing from Fig. 2. Fig. 4 shows a cover of the housing, Fig. 5 shows a top view of the lid from Fig. 4. Fig. 6 shows a front view of a peristaltic pump (delivery unit). Fig. 7 shows a rear view of the peristaltic pump from Fig. 6. Fig. 8 shows a MOSFET module, Fig. 9 shows a microcontroller (control unit), Fig. 10 shows a display module, Fig. 1 shows a detailed view of the display module from Fig. 10 in operation. Fig. 12 shows an RTC module (real-time clock). Fig. 13 shows a button cell battery of the RTC module, Fig. 14 shows a DC-DC converter, Fig. 15 a power supply, Fig. 16 shows a detailed view of the power supply from Fig. 15. Fig. 17 shows a detailed view of the positioning of a fastener based on the shapes in the Housing, Fig. 18 first fastening means of the device, Fig. 19 second fastening means of the device, Fig. 20 shows a dispensing device for delivering liquid, Fig. 21 shows a device according to the invention with the housing open. Fig. 22 shows the device from Fig. 21 in its assembled state in a side view. Fig. 23 shows the device from Fig. 21 in its assembled state in a front view. Fig. 24 shows the device attached to a container by means of the first fastening device, Fig. 25 shows the device attached to a container by means of the second fastening means, Fig. 26 shows a schematic representation of the components of the device according to the invention, Fig. 27 shows the pin assignment of the microcontroller (control unit), Fig. 28 shows a schematic representation of the method according to the invention. Fig. 29 shows a schematic representation of the database structure according to the invention. Fig. 30 shows a schematic detail view of the device according to the invention, which is connected to a reservoir. Fig. 31 shows a schematic representation of the device according to the invention in a side view, Fig. 32 shows a schematic representation of the device according to the invention with a partial section, and Fig. 33 shows a schematic representation of the components of the device according to the invention. Ways to implement the invention

[0046] Fig. 30 shows a schematic representation of an embodiment of a device according to the invention. The device comprises a housing 1 in which a pumping unit 3 and a control unit 5 (Fig. 33) for controlling the pumping unit 3 are housed. The pumping unit 3 is connected on the suction side via a hose 16 to a reservoir 4, in which the liquid to be dispensed (here: water) is provided; the reservoir 4 can be part of the device or, as is the case here, arranged and designed separately from the device. On the pressure side, the pumping unit 3 is connected to a dispensing means 2 for dispensing liquid, the dispensing means 2 projecting from the housing 1.In the illustrated embodiment, the dispensing means 2 comprises several liquid guide elements 14, which are adjustable relative to each other in their position and orientation, as well as a nozzle 15, which forms the end of the dispensing means 2 and serves for the intended discharge of the liquid to be dispensed into a container to which the device can be attached or is attached by means of a fastening means 18 (see Fig. 31). Furthermore, a display 13 for showing operational information and a push button 11 for (manual) control of the device can be seen in Fig. 30.

[0047] To reliably and permanently connect the fastening element 18 to the housing 1, recesses 12 are provided in the housing 1 – more precisely, on a housing base facing the container during normal use of the device – with which the fastening element 18 engages directly or indirectly (see Fig. 32). These recesses 12 can be formed integrally with the housing 1 or by separate components.

[0048] Figure 33 illustrates a possible structure and operation of the control unit 5: In the illustrated embodiment, the control unit 5, which is arranged inside the housing 1, first comprises a microcontroller 8, which is connected to the conveyor unit 3 via a field-effect transistor 10 in order to control the conveyor unit 3 or a motor of the conveyor unit 3. Furthermore, the microcontroller 8 is equipped with a non-volatile data memory 6, wherein It can also be an emulated data storage device of the microcontroller 8, and is connected to a real-time clock 7. In the illustrated embodiment, the field-effect transistor 10, the data storage device 6, and the real-time clock 7 are part of the control unit 5; alternatively, the field-effect transistor 10, data storage device 6, and real-time clock 7 can also be designed as separate components and connected to the microcontroller 8 that forms the control unit 5. The push button 11 and the display 13 are also connected to the microcontroller 8.

[0049] Unlike prior art, the device according to the invention does not receive any control or operating signals from external devices, such as a server 9 or a user's terminal device 17. Instead, the control unit 8 itself controls the delivery unit 3, so the device does not require a connection to the server 9 or the terminal device 17 to function as intended. The control unit 5 accesses a database on the server 9 via the microcontroller 8, which is equipped with a radio module (e.g., a WLAN module). This database contains operating data according to which the device is to be operated. The operating data typically includes a multitude of irrigation times at which the respective device is to deliver a specific quantity of liquid.The database can contain operating data for multiple devices, with each individual operating data record being assigned to a specific device via its own unique identification or assignment. Crucially, the queried operating data is stored locally on the non-volatile data storage 6 of the respective device, so that the operation of the conveying unit 3 at the respective irrigation times no longer requires a connection to the server 9; the microcontroller 8 simply accesses the operating data stored on the data storage 6 and compares the irrigation times (preferably the nearest irrigation time) with a current timestamp from the real-time clock 7.If the irrigation time matches the current timestamp of the real-time clock 7 (or if an irrigation time is exceeded), the microcontroller 8 starts the motor of the conveying unit 3 (by means of the field-effect transistor 10, whose operation is described in detail below); the operating time is controlled so that the amount of liquid specified in the operating data is dispensed.

[0050] Afterwards, the microcontroller 8 switches off the motor of the pumping unit 3 and logs the irrigation operation by creating corresponding log data. This log data should record the operation of the pumping unit 3 as precisely as possible; for example, the log data can include the switching-on and switching-off times of the motor of the pumping unit 3, so that, knowing the pumping rate of the installed pumping unit 3, the amount of liquid delivered can be calculated. As soon as the log data is created, it should be transmitted to the server 9 as soon as possible to enable precise remote monitoring of the irrigation system (which typically comprises several devices).To prevent the loss of log data and ensure uninterrupted remote monitoring, log data not yet transmitted to the server is also temporarily stored locally on the device's data storage 6. The control unit 5, or rather its microcontroller 8, periodically attempts to establish a connection to the server 9 and / or transmit log data to the server 9. In doing so, the control unit 8 checks whether, in addition to the current log data, historical log data is also present (i.e., data relating not to the most recent irrigation process, but to one from further back in time). are stored on data storage 6. If this is the case, an attempt is made to transfer the current and historical log data to server 9. If the transfer is successful, the log data is deleted from data storage 6; otherwise – i.e., if the transfer was unsuccessful – the current log data is also temporarily stored on data storage 6.

[0051] This ensures that the device according to the invention executes the irrigation actions specified in the operating data in a timely manner both in the event of an interruption of the (Internet) connection to server 9 and after an interruption of the device's power supply. On the one hand, the lack of a connection to server 9 does not pose a problem because the control unit 5 does not need to access server 9 for the operation of the pumping unit 3, but only the local data storage 6 and the also local real-time clock 7. Furthermore, log data is not lost if it cannot be transmitted to server 9, but is temporarily stored locally until transmission is possible again. On the other hand, the local storage of the operating and log data on the device's non-volatile data storage 6 guarantees that no data is lost due to an interruption of the device's power supply.

[0052] The input of operating data, in particular the specification of the respective irrigation times and the respective quantities of liquid to be dispensed, can be carried out using the terminal device 17. The user can then access the database of server 9 (via a suitable web interface) to view, create, or modify operating data and / or to view or further process log data (e.g., for statistical analysis). By regularly updating the operating data—that is, by regularly querying the operating data from server 9 and, if necessary, comparing it with the operating data already stored locally from a previous query—the device can, in principle, be operated remotely.

[0053] The following describes a project in which specific embodiments of the device or system according to the invention for supplying potted plants with water were developed and tested. The following descriptions are therefore purely exemplary and are not intended to restrict or exhaustively reproduce the inventive concept outlined above. Unless otherwise specified, features of the individual embodiments can be combined arbitrarily with other embodiments or with features of other embodiments.

[0054] Table 1 presents the requirements for the hardware and software components of the system. Table 1: Results of the requirements analysis

[0055] Figure 1 shows a schematic representation of the individual project components, how they interact, and which other components surround them. The upper part of the diagram shows three irrigation controllers (or embodiments of the devices according to the invention), the two on the right of which have been combined to form an irrigation group, as evidenced by the fact that they draw their water from the same reservoir. The irrigation controllers, which contain a microcontroller (as part of the control unit), are responsible for executing irrigation actions according to predefined times. For synchronization purposes, they are connected to the WLAN available at the installation site and communicate with the API accessible via the internet, shown in the lower part of Figure 1.This component accesses the database – also via the internet – and provides relevant data to each irrigation controller. It also receives data on completed irrigation cycles for logging purposes. Another component with database access is the web interface. This allows users to manipulate the database via suitable devices (so-called "clients") by entering user input, thus creating, modifying, and deleting irrigation-related database resources. In this way, operational data for the irrigation controllers and their pumping units can be stored in the database (which may be located, for example, on a server).

[0056] The following sections explain in more detail the requirements for automatic irrigation systems, their individual components, and their assembly.

[0057] An automatic watering system should house all the necessary components for its operation in a single unit. It should also be mountable on the plant pot. and can be powered by two built-in sockets, one for its own use and the other for powering another irrigation controller via a connecting cable. This is made possible by short-circuiting the two sockets so that the same voltage is applied to both.

[0058] The following is a list and detailed description of the components of an automatic irrigation system. For the sake of clarity, detailed descriptions of purely mechanical components are largely omitted. Figures 22 and 23 show views of a fully assembled automatic irrigation system. Housing

[0059] This section describes the creation of the housing. This includes 3D modeling, 3D printing, and assembly. The housing was designed with a focus on a simple, functional, and straightforward design for the irrigation system. The overall dimensions of the housing, comprising a base and a lid, are 120 x 60 x 47 mm (H x W x D) when assembled. Where feasible with 3D printing, all outer edges of both components were rounded with corner radii between 0.5 mm and 5 mm to prevent sharp edges. For all elements onto which other components would later be mounted, an appropriate allowance (0.5 mm to 1 mm) was incorporated to ensure trouble-free assembly without the need for rework. The 3D printing was performed using Prusa MK3+ 3D printers.

[0060] The base (see Figures 2 and 3) of the housing forms the back panel of the automatic watering unit. A circular cutout with a 10.5 mm diameter is located on the top of the base, through which the 1 / 8" male thread for mounting the flexible spout (dispensing device) fits with some play. The housing wall thickness has been increased at this point to provide greater stability and resistance to breakage, and to ensure optimal clamping between the flexible spout connection and the adapter (which compensates for the difference between the flexible spout's NPT thread and the hose fitting's inch thread). A 5 mm hole has also been provided on the top for installing an LED. Four screw channels are provided in the corners of the components for attaching the lid (see Figures 4 and 5) to the base using self-tapping sheet metal screws.Each of these screw channels was integrated into a slightly chamfered projection on the outer edges of the component, extending 5 mm beyond the rest of the component and ensuring a precise fit of the lid to the base. Furthermore, the contours for two M4 nuts were incorporated into the upper area to create recesses into which two M4 nuts can later be inserted or glued. M4 hook bolts can be screwed into the nuts through a corresponding hole behind the recesses to attach the watering system to the plant pot. On the underside of the base, there are two holes of the appropriate diameter to accommodate the two sockets for powering this watering system via a power supply unit (see Figures 15 and 16) and for connecting another watering system via a connecting cable.

[0061] The housing lid forms the front of the automatic watering system and thus seals the base (see Figs. 4 and 5). Through holes for screwing the lid to the base using four pan-head sheet metal screws are located in the four corners of the front. A suitable recess for the display (see Figs. 10 and 11) and four holes for its attachment using M2 polyethylene socket head screws and nuts are provided. A circular cutout with a 35 mm diameter is located centrally below the front panel, through which part of the peristaltic pump motor, including its connection pins, will later protrude. Two screw channels, spaced appropriately, are located on either side of this cutout for securing the peristaltic pump with two countersunk sheet metal screws. Two domes are provided on the back of the component at these points to protect the inside of the housing, particularly the water-carrying polyvinyl chloride tubing and the electronic components, from damage caused by the sharp metal tips of the countersunk sheet metal screws.Below the cutout for the peristaltic pump, and at the appropriate distance, there is also a 10 mm diameter through-hole in the center, in which a metal push button is mounted. To the left of this is another hole with a 6 mm diameter, through which the pressure-side hose of the peristaltic pump will later be routed into the interior of the housing. Peristaltic pump

[0062] The peristaltic pump (see Figures 6 and 7) is visibly mounted on the front of the housing. A commercially available peristaltic pump with a suitable flow rate can be used for this purpose, or it can be manufactured using 3D printing or other manufacturing processes (such as injection molding). The peristaltic pump used here uses a 3 x 5 mm hose (3 mm inner diameter, 5 mm outer diameter) which is continuously compressed against its wall behind a transparent cover by three rollers. With each rotation of these rollers, a specific amount of water is pumped from the suction to the pressure side. The cover can be lifted by loosening four screws, allowing the hose behind it to be easily replaced if it shows signs of wear. A connector is located on both the suction and pressure sides, allowing the peristaltic pump to be connected to other hoses (with the same cross-section).The drive motor protrudes from the rear of the peristaltic pump's pumping mechanism and is supplied with 12 V DC via two solder pads on the rear. Two eyelets with 3 mm holes are located on the sides of the pump housing, allowing the peristaltic pump to be mounted to other components. The water flow rate of the peristaltic pump used here was determined experimentally and is 133 ml / min. MOSFET module

[0063] The MOSFET module D1184, which is installed in the irrigation controller, is used to control the peristaltic pump motor (see Fig. 8). The module has two inputs (ground, GND; trigger input, TRIG), with TRIG being connected to a digital output of the microcontroller. The voltage at the output terminals is proportional to the voltage applied to the input terminals. Microcontroller (ESP8266 NodeMCU)

[0064] The irrigation system's control unit includes a microcontroller; a NodeMCU was chosen due to its integrated ESP8266 Wi-Fi module (see Fig. 9). This NodeMCU has an ESP-12F processor, eleven digital I / O pins, and one analog I / O pin. Also relevant is the ability to... to emulate an EEPROM. The microcontroller can be accessed via the n -Pin must be supplied with a voltage of 5 V DC. Display

[0065] The display integrated into the irrigation controller uses an LCD display module with adjustable backlighting (see Figures 10 and 11). The display has a resolution of 84x48 pixels and can be controlled via a serial interface, with the backlighting switched via a dedicated digital input. The display is easily readable without backlighting in bright sunlight. In dark environments, the backlighting can be activated with a short press of a button to ensure readability. It then automatically deactivates after, for example, 5 seconds. This makes the irrigation controller suitable for use in environments where visual distractions are undesirable (e.g., bedrooms).In addition to two power supply pins (common collector voltage VCC, GND), the display also has five pins for SPI communication (reset input RST, chip activation input CE, data command input DC, data input DIN, clock input CLK) and one pin as a digital input for switching the backlight (LIGHT). The display's supply voltage is 5 V. Two libraries from Adafruit are available for controlling the display; these will be discussed in more detail below. Real-time clock (RTC)

[0066] The real-time clock built into the irrigation controller uses an RTC module with the "DS3231" chipset (see Fig. 12), which is equipped with a rechargeable "LIR2032" button cell (see Fig. 13) and has l 2The RTC module can be controlled via a serial data bus (inter-integrated circuit). In addition to two power supply pins (VCC, GND), it has two pins for communication via I. 2 The RTC can be communicated via serial clock input (SCL), serial data input (SDA), and via clock output pins (32K, SQW), which are not used in this project and therefore will not be described further here. A library is available for communication with the RTC, which will be discussed in more detail below. DC / DC converter (7-28 V DC to 5 V DC)

[0067] This DC / DC converter from the manufacturer "RECON", model designation "R-78E5.0-0.5" (see Fig. 14), converts DC input voltages between 7 V and 28 V to a DC output voltage of 5 V and a maximum output current of 500 mA. It is connected between the power supply sockets and the nThe microcontroller's -pin is used to supply it with the required operating voltage of 5V. Power supply (12 V, 500 mA)

[0068] The power supply (see Figures 15 and 16) is used to supply the sockets—and consequently the DC / DC converter built into the irrigation controller—with an input voltage of 12 V DC. It bears the model designation "SYS1381 N-1212-W2E" and has a cable length of 1.4 m. The power supply plug has an outer diameter of 5.5 mm and an inner diameter of 2.1 mm and therefore fits easily into the socket built into the housing. assembly

[0069] Starting with the two sockets, these are first mounted in the two holes on the underside of the housing base by tightening the flat nuts. The positive (pin at the edge) and negative (pin in the center) terminals of each socket are then connected to each other using short wires and soldered together. The metal push button is also mounted to the housing cover by tightening its flat nut. Two wires are run from one socket to the inputs of the DC / DC converter (12 V, pin 1 & GND, pin 2), whose output (5 V, pin 3) is connected to the nThe microcontroller's pin is soldered. Two wires are run from the other socket directly to the MOSFET module to supply it with the full 12 V input voltage. Next, the peristaltic pump is mounted in its designated position on the housing cover and secured with two countersunk sheet metal screws in the designated screw channels. Furthermore, all connections indicated in Fig. 27 are made by soldering wires between the microcontroller outputs and the indicated components. Once this is done, the display is positioned on the housing cover and secured with four M2 PE socket head cap screws in the designated holes by carefully tightening the corresponding nuts. Finally, two M4 nuts are inserted into the designated recesses.The molded inserts in the base of the housing are placed, and then—depending on suitability—either two L-shaped screw hooks or two ring screw hooks (or other fasteners, such as suction cups) with knurled nuts screwed on in reverse are screwed into the newly inserted nuts from the outside (see Fig. 17, Fig. 18, and Fig. 19). Once this is done, a 10 cm piece of PVC tubing is connected at one end to the pressure side of the peristaltic pump and fed through the designated hole in the housing lid. The other end of the tubing is then attached to the elbow screw fitting and secured by tightening the fitting. Finally, the reducing nipple is taken, and its external thread is wrapped approximately twice with thread sealant tape (such as polytetrafluoroethylene tape) in the direction of tightening before it is screwed into the elbow screw fitting.The threaded end of the flexible spout's connector is also wrapped with PTFE thread sealing tape in the same manner, inserted through the reinforced hole on the top of the housing base, and screwed onto the reducing nipple using a 14 mm wrench. Next, the remaining parts of the flexible spout (see Fig. 20) are assembled, so that all water-carrying components are connected. Finally, all components and cables are stowed in the housing base, and the housing cover is then fitted and secured with four pan-head sheet metal screws. Fig. 21 shows all components before the housing is screwed together. After completing the aforementioned steps, the automatic watering system is fully assembled and ready for use. The final state (see Fig. 22) now allows the automatic watering system to be attached to plant pots (see Fig. 23).Thanks to the two different types of screw hooks, the automatic watering system can be adapted to various plant pot shapes and, for optimal stability, its length can also be adjusted by screwing the hook screws in or out and then clamping them in place using the knurled nuts. The two screw types are shown side-by-side in Figures 24 and 25. microcontroller

[0070] The following sections explain in more detail the requirements, functionality and implementation of the microcontroller.

[0071] The microcontroller performs the following functions: synchronization of irrigation settings (operating data) and logs (protocol data) with the API or server; (temporary) storage and management of all settings and log data; timely, reliable execution of the set irrigation cycles according to operating data; offline functionality thanks to the RTC module and locally stored irrigation settings; display of all relevant data on the built-in display. How it works

[0072] This section describes how the microcontroller interacts with the other components of the project and what processes it follows. Vicinity

[0073] Figure 26 shows a schematic representation of the microcontroller's environment. The diagram includes relevant components; the arrows between them indicate how they communicate with the microcontroller and with each other (unidirectionally or bidirectionally). Pin assignment

[0074] Figure 27 shows the pin assignment in which the other components are connected to the microcontroller. Operating conditions

[0075] The method according to the invention, or the corresponding states, conditions and state transitions, are shown in Fig. 28. Implementation / Programming

[0076] The microcontroller used is an ESP8266 NodeMCU. The microcontroller was programmed in the "C" programming language, and the Arduino IDE (Integrated Development Environment) version 1.8.19 was used as the development environment. Libraries used

[0077] For the implementation of the project, the following libraries were used, particularly for communication with (external) components:

[0078] ESP8266WiFi.h: The Arduino-native “ESP8266WiFi” library provides an interface to the WLAN functionality of the ESP8266 chip and provides simple function calls for using these functionalities in the program flow.

[0079] ArduinoJson.h: The “ArduinoJson” library by Benoit Blanchon (“bblanchon” on GitHub) provides functions for decoding and encoding JSON constructs (JavaScript object notation) during program execution.

[0080] EEPROM.h: The Arduino-native "EEPROM" library provides an interface to the EEPROM functionality of the ESP8266 chip and offers functions for writing to and reading EEPROMs, which can be used during program execution.

[0081] WiFiManager.h: The "WiFiManager" library from "tzapu" provides functions that, among other things, allow a configuration portal to be implemented within the program flow for configuring WLAN settings via an external, WLAN-enabled device. This functions as a so-called "captive portal," meaning that a configuration dialog is displayed on various devices as soon as a connection to the created network is established. The library also handles the storage of the WLAN access data (WLAN network name, service set identifier, or SSID, and security key), thus eliminating the need for individual programming in this area.

[0082] Wire.h: Arduino's own "Wire" library provides functions for using the l 2 C interfaces are available during program execution.

[0083] Adafruit_GFX.h: The “Adafruit_GFX” library from Adafruit (“adafruit” on GitHub) provides functionalities for displaying graphical content on a variety of different display types, including the display used in this project.

[0084] Adafruit_PCD8544.h: The “Adafruit_PCD8544” library from Adafruit (“adafruit” on GitHub) provides functionalities for controlling LCD displays which (like the “Nokia 5110nDisplay” used in this project) are equipped with the “PCD8544” driver board.

[0085] RTClib.h: The "RTCIib" library from Adafruit ("adafruit" on GitHub) provides an interface for data exchange with a variety of FC-enabled RTC models. In this project, it is used to set the RTC's time, update it as needed, and retrieve the current time or timestamp from the RTC. Control of external components

[0086] The following sections explain how external components are controlled by the microcontroller. Explanations of trivial components (display, metal push button, MOSFET) are largely omitted. EEPROM

[0087] The microcontroller's emulated EEPROM, acting as non-volatile memory (non-volatile meaning that data is not lost during a power interruption), handles the local storage of all operating data required for the irrigation system's operation. It can be written to and read from using the corresponding library (EEPROM.h). Further information and features of the EEPROM: 4 kB maximum storage capacity; emulation by the microcontroller; write operations: limited to 100,000 per memory location; read operations: unlimited; all data is stored as characters (1 byte per character).

[0088] Table 2 lists all the first memory locations for the data stored in the EEPROM. These are divided into the sections "Irrigation settings" (0-289), "Log buffer" (290-1889) and "Device settings" (1890-1961). Table 2: EEPROM memory location allocation RTC

[0089] The RTC module integrated into the irrigation controller, which was discussed in more detail above, is able to maintain the accuracy of its stored timestamp for a very long time, even during an interruption of the external power supply, thanks to the rechargeable LIR2032 battery cell. This ensures the functionality of the irrigation controller after a power outage, even if the stored Wi-Fi connection is unavailable when power is restored and the current time cannot be retrieved from the server.

[0090] The corresponding library checks the current timestamp of the RTC (Real-Time Clock) for accuracy every time the settings are synchronized with the API. If the RTC's timestamp is more than 10 seconds ahead or behind the current server timestamp, the RTC's timestamp is reset or updated (the real-time clock is synchronized based on the time retrieved from the server). This also occurs during initial setup or after replacing or completely discharging the built-in battery cell. During program execution, the RTC is queried every second, and its current timestamp is compared with the next irrigation setting or action in the operating data. If the two timestamps match, the irrigation process is triggered, or the pumping unit is activated. MOSFET module

[0091] The MOSFET module is connected to the digital output D8 at TRIG and to a GND pin of the microcontroller at GND. When a voltage is applied to TRIG, the external input voltage (12 V from the integrated socket) is switched on, thus activating the peristaltic pump. The voltage applied (and therefore the speed or water flow rate of the peristaltic pump) depends on the voltage applied to TRIG. database

[0092] The following sections explain in more detail the requirements for the database and their implementation. Requirements

[0093] The purpose of the database is to store all data required for the operation of the system (operational data of the device(s)) and to output it according to incoming queries via PHP scripts (structured query language). Implementation

[0094] Based on the requirements discussed above, a relational (tabular) database system with five database tables can be used for the irrigation system's operation. Due to its straightforward setup, simple administration and maintenance, simple structure, easy querying, good compatibility with PHP, and suitable restrictions, a MySQL database system hosted on the servers of an internet service provider was chosen. The MySQL version used is 5.7.

[0095] The MySQL database system comprises five database tables, each with a unique number of columns. Figure 29 schematically illustrates the database structure (see tables below). Table 3: Details Database table "users" Table 4: Details of the database table "devices" Table 5: Details of the database table "groups" Table 6: Details of the database table "logs" Table 7: Details of the database table "watersettings" Primary key

[0096] Primary keys (PKs) have been defined in the database, enabling the unique identification of a record within a database table. These are marked with a key symbol in the database diagram (see Fig. 29). These primary keys are often generated by auto-increment (AI) when a new database entry is created. Foreign key

[0097] Furthermore, foreign keys were defined in the database, establishing references between columns of different tables within the database. The corresponding dependencies are indicated by lines in the database diagram (see Fig. 29). The label above (1 or *) indicates the type of dependency, with "1" denoting a reference and "*" indicating the use of this reference elsewhere, in a so-called "referential" position.

[0098] The following dependencies were defined: Tab. "devices": "dev_linked_usr_id" references Tab. "users", column (Sp.) "usr_id" "dev_linked_grp_id" references Tab. "groups", column "grp_id" Tab. "watersettings": "wt_usr_id" references Tab. "users", column "usr_id" "wt_dev_id" references tab "devices", column "dev_id" "wt_grp_id" references table "groups", column "grp_id" Tab. "logs": "log_dev_id" references Tab. "devices", Sp. "dev_id" Tab. "groups": "grp_owner_usr_id" references Tab. "users", column "usr_id" Web interface

[0099] The following sections explain in more detail the requirements, implementation and functionality of the web interface. Requirements

[0100] The web interface is responsible for accepting user input on various settings and operating data (e.g., desired irrigation settings, user account settings, irrigation controller settings, and group settings) and for displaying the data collected by the system, particularly log data (e.g., data on completed irrigation actions, current water levels in the reservoir, etc.). This is done in conjunction with the MySQL database to fulfill these tasks. Implementation

[0101] The web interface was implemented using the programming languages ​​HTML and PHP. A MySQL database serves as the data source in the background. How it works

[0102] This section describes how the web interface works. Below you will find a description of all subpages, including the variables and parameters used. User area

[0103] The user area includes all functionalities that allow system users to view and edit system settings and retrieve log data. The basic layout of each subpage includes a menu bar containing the menu items "Dashboard," "Statistics," "Administration" (with the sub-items "Devices" and "Groups"), and "My Account" (with the sub-items "Settings" and "Logout"). This menu bar, visible only to logged-in users, is displayed on every subpage of the web interface. When a user accesses a subpage intended for logged-in users, the system checks whether the session variable is set before the page is loaded. If it is not, the user is immediately redirected to the login page before any page content is displayed.

[0104] User login ( / login.php): When accessed, a form with an email and password input field is displayed, allowing users to log in. A "Register" link is also present, which redirects the user to the user registration page. Clicking the "Log in" button verifies the entered data against the MySQL database. If the email / password combination is correct, a session ID (user ID of the account) is assigned, and the user is then redirected to the user area. Otherwise, an error message is displayed. A password reset option, similar to those found on other websites, may also be implemented.

[0105] User registration ( / register.php): When accessed, a form with various input fields (first name, last name, email address, password, password confirmation) is displayed, which can be used to create a new user account. Clicking the "Register" button below checks the email address; if it already exists in the database, an error message is displayed. Next, the two password fields are checked. If they match, a new user account with the entered data is saved in the MySQL database. If the contents of the two password fields do not match, an error message is displayed.

[0106] Dashboard ( / dashboard.php): Upon access, a time-of-day-dependent greeting including the first and last name of the logged-in user account ("Good morning / afternoon / evening, [First Name] [Last Name]!") is displayed. Subsequently, all irrigation timers linked to the user account are displayed, along with their details (name, remaining water level in the device's water reservoir, if configured). If irrigation groups exist, the timers are displayed sorted by these groups, along with the corresponding remaining water level in the group's water reservoir (if configured). Next to each timer, a "Settings" link is displayed, which leads to the details page of that specific timer. This same link is also displayed next to each irrigation group, but this one leads to the details page of that particular irrigation group.

[0107] Overview of Irrigation Controllers ( / devices.php): This page provides a clear overview of all irrigation controllers linked to the user account. Users can also add new irrigation controllers by entering their 6-digit device ID, or remove them from the account by clicking the "Remove from Account" button next to the respective controller. Furthermore, a "Settings" link is displayed next to each irrigation controller, leading to its detailed settings page.

[0108] Overview of Irrigation Groups ( / groups.php): This page provides a clear overview of all irrigation groups in the user account. Here, users can create new irrigation groups by entering the new group name in the designated input field, or delete existing groups by clicking the "Delete Group" button next to the respective group. Additionally, a "Settings" link is displayed next to each irrigation group, which leads to the detailed view of that group.

[0109] Detailed view of the irrigation timer ( / deviceview.php?id=[device ID]): This subpage displays more detailed information (name, identifier, all programmed watering times including synchronization status, group link) for the selected irrigation timer. Settings can also be configured here (add / edit / delete watering times, edit name, group membership, device water tank capacity, email notification threshold, remove irrigation timer from account).

[0110] Detailed view of irrigation group ( / groupview.php?id=[group ID]): This subpage displays more detailed information (group name, group ID, all programmed group irrigation times including synchronization status) for the selected irrigation group. Settings (adding / editing / deleting group irrigation times) can also be adjusted here. Changes such as group name (edit), associated devices, group water tank capacity, email notification threshold, group deletion & device removal) can be made.

[0111] Irrigation Settings ( / watersetting.php?dev_id=[Device ID]&grp_id=[Group ID]&wt_id=[Setting ID]): This subpage allows you to create and edit irrigation settings by displaying form fields. When this subpage is accessed, the parameters are checked and the content is built or preselected according to the set parameters: Set Device ID (dev_id) or Group ID (grp_id): Creation of a new irrigation setting; the relevant irrigation timer or irrigation group is preselected. Set Setting ID (wt_id): Editing of an existing irrigation setting (forms already filled out); option to delete the irrigation setting (POST parameter delete = true). No set parameter: Creation of a new irrigation setting without a preselected irrigation timer or irrigation group.

[0112] Statistics ( / stats.php?dev_id=[device ID]): This subpage displays a chronologically sorted list of all executed and reported irrigation cycles for the selected irrigation controller, provided a device ID linked to the user account is specified as a parameter. A "Delete" button is located to the right of each log entry, allowing the entry to be deleted. A dropdown menu at the top of the subpage allows selection of all irrigation controllers linked to the user account. To the right of this menu is a "Retrieve" button, which reloads the subpage and appends the selected device ID as a parameter to the URL. If no parameter is set, a message is displayed prompting the user to select an irrigation controller from the dropdown menu.

[0113] User settings ( / accountdata.php): This subpage displays all saved information for the user account. It also allows you to edit this data using the form fields below (change name / email / password, set master alarm water level limit). Additionally, you can delete the user account.

[0114] Functional Area (API): The API, which is contacted by the individual irrigation controllers at regular intervals (e.g., every 30 minutes), handles all data traffic with them. Depending on the purpose, all data is exchanged via appropriate requests, such as HTTP GET or HTTP POST requests. The three use cases are listed and described in more detail below.

[0115] Retrieving settings (Zsync.php?id=[device ID]): When a parameter is passed, selected device settings (device name, group name if assigned, current UNIX (Uniplexed Information and Computing Service) timestamp), as well as the data for all irrigation settings of the selected device (device and group irrigation settings), are output in JSON format. The first index (0) of the JSON array contains the device settings; all subsequent indexes contain the data for each irrigation setting (operational data).

[0116] Reporting back stored irrigation settings ( / sync.php): When a POST request is sent with the parameter "storedjds" set, containing all setting IDs of the irrigation settings stored in the irrigation controller specified by the parameter "id" in JSON format, the status of each irrigation setting is set to "synchronized" (value "1" in the "wt_status" column of the "watersettings" database table) for display in the web interface. If this is a group irrigation setting, the device ID is added to the JSON string in the "wt_grp_syn_dev" column of the "watersettings" database table.

[0117] Irrigation process reporting ( / sync.php): A POST request with the parameter "log" containing log data for one or more irrigation processes performed by the automatic irrigation system, with the device ID specified in the parameter "id" in JSON format, creates a new database entry in the "logs" table for each irrigation process. This entry contains the specified data. After each log entry, the water level in the device or group water reservoir is recalculated using the reported water volume. The system then checks whether the set device, group, or master water level limit has been reached. If the limit is reached for the first time (value in the "dev / grp / usr_alarm_sent" column of the corresponding database table is "0"), an email reminder to refill the water reservoir is sent to the email address registered in the user account. Evaluation

[0118] The project results are described and evaluated below based on various aspects. Reliability tests

[0119] The following section explains the testing methodology and the resulting data, which were designed to examine and demonstrate the reliable operation of the irrigation system. To conduct these tests, the system was tested with various settings over a period of 30 days each, and the system's reliability was subsequently determined based on the generated logs. These tests also examined the system's behavior during short- and long-term interruptions of the internet connection, as well as during short-term power outages, in order to comprehensively evaluate the interaction of the integrated modules. For better reproducibility, only the irrigation controller with the ID "ABCDEF" was used.The columns of the following evaluation tables bear the following labels: log id: ID of the log entry (automatically generated) log_time: Time of irrigation (timestamp of the installed RTC module) log_created: Creation time of the log entry in the database log_amount: Irrigation quantity in ml. Target time: Target time for irrigation / / X: Irrigation performed correctly / not performed correctly

[0120] The first four columns of the evaluation tables were extracted from the database system after the end of the respective test periods; the last two were created manually and serve the purpose of evaluation. Regular irrigation

[0121] A regular irrigation process is defined as one that occurs when the Wi-Fi network is available and without any interruption to the power supply, allowing the log entry to be transmitted to the server immediately after the irrigation has taken place. The three types of irrigation settings are then evaluated for their reliability by analyzing the system-generated logs and comparing them to target times. For this purpose, the "one-time" setting was tested five times at different times, and the "recurring (weekly)" and "recurring (at regular intervals)" settings were tested over a period of four calendar weeks (28 days) each. Setting "one-time only"

[0122] To evaluate the "one-time" setting, five irrigation settings with different times and water quantities were created between 25.01.2022 09:28 and 25.01.2022 12:05.

[0123] Irrigation volumes of 10, 25, 70, 65, and 30 ml were defined, and irrigation times of 9:28, 10:09, 10:49, 11:03, and 12:05 were defined for the respective irrigation actions. In the corresponding section of the web interface, the user sees this operational data, along with a "synchronized" message. "Synchronized" means that the operational data for each irrigation action has already been cached locally on the non-volatile data storage.

[0124] As can be seen in Table 8, all planned irrigations were carried out at the right time and with the correct amount of water. Table 8: Evaluation of the "one-time" setting Setting “recurring (weekly)”

[0125] To evaluate the setting type "recurring (weekly)", an irrigation setting was created with initial irrigation on January 26, 2022 at 12:00 PM, which consequently waters the plant weekly with a quantity of 10 ml of water each time.

[0126] This evaluation was conducted over a period of 28 days (672 hours) between January 26, 2022 at 12:00 and February 23, 2022 at 12:00. As can be seen in Table 9, all irrigations were carried out at the correct time and with the correct amount of water. Table 9: Evaluation of the "recurring (weekly)" setting Setting “recurring (at regular intervals)”

[0127] To evaluate the setting type "recurring (at regular intervals)", an irrigation setting was created with initial irrigation on March 2, 2022 at 12:00 PM, which consequently irrigates the plant every 10 hours with a water quantity of 5 ml.

[0128] This evaluation was conducted over a period of 28 days (672 hours) between March 2, 2022 at 12:00 PM and March 30, 2022 at 11:00 AM. It should be noted that the annual change from winter to summer time (in calendar year 2022, from 2:00 AM to 3:00 AM on March 27, 2022) took place during this test period. As can be seen in Table 10, all irrigations were carried out at the correct time and with the correct amount of water. No problems occurred during the entire 28-day test period. System restart required. The first log entry after the time change (log id 885), which was also carried out correctly, was marked with "**". Table 10: Evaluation of the setting "recurring (at regular intervals)" Wi-Fi connection interruption

[0129] The following test examined the functionality of the irrigation system under conditions of unavailability of the Wi-Fi connection. In this case, the logs of the completed irrigation processes can be temporarily stored in the system's EEPROM before being transmitted to the server along with the next log message after successful irrigation once the Wi-Fi connection is restored.

[0130] For this purpose, an irrigation setting of the type "recurring (at regular intervals)" was created, which irrigates every 10 minutes with a water quantity of 15 ml starting on 02.4.2022 at 12:00 pm.

[0131] The irrigation settings were synchronized on April 2, 2022, at 11:48 AM and the process was allowed to complete. Subsequently, the Wi-Fi network was deactivated at 11:51 AM for a period of 60 minutes. After 60 minutes, the Wi-Fi network was reactivated at 12:52 PM, and another irrigation cycle (1:00 PM) was observed before the corresponding logs were extracted from the database and subsequently evaluated. The results of this evaluation are shown in Table 11.

[0132] As can be seen in Table 11, all planned irrigation actions were reliably carried out at the correct times despite the interruption of the WLAN network, temporarily stored, and successfully transferred to the server after the WLAN network was available again with the subsequent irrigation. Table 11: Evaluation with interruption of the WLAN connection Power outage & Wi-Fi connection

[0133] The following investigation examined the functionality of the irrigation system under conditions of a temporary power outage and subsequent unavailability of the Wi-Fi connection. In this scenario, the current UNIX timestamp is not available from the web interface upon the microcontroller's restart. Therefore, the system, via the RTC module, must be able to provide the current UNIX timestamp despite the power interruption. This ensures that the system has access to the correct time until the Wi-Fi connection is restored, allowing for the reliable execution of any irrigation processes scheduled during the interruption.

[0134] For this purpose, the irrigation settings described above (see Table 10) were used. Since synchronization had already been achieved with the previous evaluation, the prototype's power supply was interrupted at 1:52 PM on April 2, 2022. Subsequently, at 1:55 PM, the Wi-Fi network was deactivated and the prototype's power supply was switched off. The connection was restored at 1:57 PM, allowing the next scheduled irrigation to take place as planned at 2:00 PM. After 60 minutes, the Wi-Fi network was reactivated at 3:00 PM, and another irrigation cycle was observed before the corresponding logs were extracted from the database and evaluated. The results of the evaluation are shown in Table 12. Table 12: Evaluation with interruption of power supply & WLAN connection

[0135] As can be seen in Table 12, all planned irrigation actions were reliably carried out at the correct times despite the interruption of the power supply and the WLAN network, temporarily stored, and successfully transferred to the server with the last irrigation after the WLAN network was available again.

Claims

Patent claims 1. A device for dispensing a liquid, the device comprising at least a housing (1), a dispensing means (2) protruding from the housing (1) for dispensing liquid, a conveying unit (3) provided in or on the housing (1) for conveying liquid from a reservoir (4) to the dispensing means (2), and a control unit (5) accommodated in the housing (1) for controlling the conveying unit (3), characterized in that the device has a non-volatile data memory (6) and a real-time clock (7), the control unit (5) being designed to query operating data for the operation of the conveying unit (3) from an external server (9), to store this operating data on the non-volatile data memory (6), and to operate the conveying unit (3) depending on a comparison of the stored operating data with a time stamp of the real-time clock (7).

2. Device according to claim 1, characterized in that the control unit (5) is designed to query a current time from the external server (9), preferably together with the operating data for the operation of the conveyor unit (3), and to update the real-time clock (7) using this current time.

3. Device according to claim 2, characterized in that the control unit (5) is configured to update the real-time clock (7) only in the event of a predetermined deviation of a current time stamp of the real-time clock (7) from the current time.

4. Device according to one of claims 1 to 3, characterized in that the control unit (5) is designed to log the operation of the conveyor unit (3).

5. Device according to claim 4, characterized in that the control unit (5) is configured to transmit protocol data about the operation of the conveyor unit (3) to the external server (9).

6. Device according to claim 5, characterized in that the control unit (5) is configured to temporarily store protocol data on the operation of the conveyor unit (3) on the non-volatile data memory (6).

7. Device according to claim 6, characterized in that the control unit (5) is configured to delete protocol data from the non-volatile data memory (6) after its transmission to the external server (9).

8. Device according to one of claims 1 to 7, characterized in that the device comprises a microcontroller (8), preferably WWAN and / or WLAN-capable.

9. Device according to one of claims 1 to 8, characterized in that the device comprises a field effect transistor, in particular a metal oxide semiconductor field effect transistor (10), for controlling the conveyor unit (3), preferably for voltage-dependent control of the conveyor unit (3), particularly preferably for controlling a conveying speed and / or conveying duration of the Conveyor unit (3), wherein the field effect transistor is preferably interposed between the microcontroller (8) and the conveyor unit (3).

10. Device according to one of claims 1 to 9, characterized in that the device comprises an operating element which can be actuated from outside the housing (1), in particular a button (11), in order to enable manual actuation of the control unit (5) and / or the conveyor unit (3).

11. Device according to one of claims 1 to 10, characterized in that the conveying unit (3) is formed by a pump, in particular by a peristaltic pump.

12. Device according to one of claims 1 to 11, characterized in that the non-volatile data memory (6) is formed by an EEPROM.

13. Device according to claim 12, characterized in that the EEPROM is emulated by the microcontroller (8).

14. Device according to one of claims 1 to 13, characterized in that at least one fastening means (18) for releasably fastening the device to a container is provided on an outer side of the housing (1).

15. Device according to claim 14, characterized in that the fastening means (18) is formed by at least one or more screw hooks.

16. Device according to one of claims 14 or 15, characterized in that the fastening means (18), in particular the screw hook, is fixed in position by means of formations (12) provided on an inner side of the housing (1).

17. Device according to one of claims 1 to 16, characterized in that a display (13) for displaying information is provided in or on the housing (1), wherein the display (13) is connected to the control unit (5).

18. Device according to one of claims 1 to 17, characterized in that the dispensing means (2) comprises a plurality of liquid guiding elements (14) which are adjustable relative to one another.

19. Device according to one of claims 1 to 18, characterized in that the dispensing means (2) comprises a nozzle (15).

20. Device according to one of claims 1 to 19, characterized in that the dispensing means (2) comprises a hose (16), which hose (16) is guided via an inlet opening into the housing (1) and via an outlet opening out of the housing (1).

21. Device according to claim 20, characterized in that the hose (16) is connected at one end to the conveyor unit (3).

22. System comprising the device according to one of claims 1 to 21 and the server (9).

23. System according to claim 22, comprising a terminal (17), wherein the terminal (17) is at least configured to a. transmit operating data for the operation of the conveyor unit (3) of one or more devices to the server (9), b. manipulate operating data of one or more devices stored on the server (9) and / or c. query operating data and / or protocol data of one or more devices stored on the server.

24. A method for controlling a device for dispensing a liquid, comprising at least the following method steps: a. querying operating data for the operation of a conveyor unit (3) of the device from an external server (9); b. storing the operating data on a non-volatile data memory (6) of the device if the query according to a. was successful; c. checking whether operating data is stored on the non-volatile data memory (6) if the query according to a. was unsuccessful; d. operating the conveyor unit (3) based on a comparison of the stored and / or queried operating data with a time stamp of a real-time clock (7) of the device; 25. A method for controlling a device for dispensing a liquid, comprising at least the following method steps: a. transmitting log data about the operation of a conveyor unit (3) of the device to an external server (9); b. storing the log data on a non-volatile data memory (6) of the device if the transmission according to a. was unsuccessful; c. deleting the stored log files from the non-volatile data memory (6) after these log files have been successfully transmitted to the server (9).

Citation Information

Patent Citations

  • Potted soil humidity monitoring device

    CN109220738A

  • Automatic waterer for potted plant

    JP1994054629A

  • Plant culturing device

    WO2006070784A1

  • Fertilizer installation, irrigation system and method for operating an irrigation system

    DE102017114740A1

  • Plant watering system

    US20070089365A1