Skip to main content

IoT Home Automation | Basic plant watering system

Almost 3 months past without working on the own IoT home solution. In the meantime, I was able to lose the UI implementation. Because of this in the next 1-2 weeks, I will try to rewrite it.
The previous post about my IoT solution: IoT Home Automation | Stabilize the garage doors solution after power break (resistors and capacitors) http://vunvulearadu.blogspot.ro/2018/02/iot-home-automation-stabilize-garage.html

Because summer holidays are here and I didn't want to bother my neighbors to water the flowers I decided to come up with a fast and cheap solution based on ESP8266. For grass I already have an automation solution from Gardena, but if you can do it yourself why not. Especially if you take into account the price of Gardena controller.

The first version is pretty basic, from the features perspective. No internet connection, no reporting, no humidity sensors and other stuff like this. Lack of time forced me to keep things super necessary, but I've replicated 100% the Gardena controller with less than 10 euros.
The pipes and connectors are another stories from the cost perspective, but you cannot avoid this. I highly recommend to use high-quality water tube connectors.
I just added a timer and every 12 hours I open different water circuits for 4 minutes or 30 seconds.

#include <Arduino.h>
#include <ESP8266WiFi.h>
#include <ESP8266HTTPClient.h>
#include <time.h>

#ifdef ESP8266
extern "C" {
#include "user_interface.h"
}
#endif

#define DEFAULT_TIME_MS_1 4*60*1000
#define DEFAULT_TIME_MS_2   30*1000
#define DEFAULT_TIME_SLEEP (12*60*60*1000)-DEFAULT_TIME_MS_1-DEFAULT_TIME_MS_2

void setup() {
  pinMode(D1, OUTPUT);
  pinMode(D3, OUTPUT);
    
  // This is required to read ADC values reliably
  wifi_set_sleep_type(NONE_SLEEP_T);
  
  Serial.begin(57600); 
  
  // Delay is required only for debugging
  delay(2000);
  Serial.println("Setup complete");
  
  WiFi.mode(WIFI_STA);
}
void loop() {
  Serial.println("Open Valve 1:");
  Serial.println(DEFAULT_TIME_MS_1);
  triggerValve(1, DEFAULT_TIME_MS_1);
  Serial.println("Close Valve 1:");

  Serial.println("Open Valve 2:");
  Serial.println(DEFAULT_TIME_MS_2);
  triggerValve(2, DEFAULT_TIME_MS_2);
  Serial.println("Close Valve 2:");

  Serial.println("Sleep for the next 12h");
  Serial.println(DEFAULT_TIME_SLEEP);
  delay(DEFAULT_TIME_SLEEP);
}


void triggerValve(int gateNumber, int openDuration){
  Serial.println("Open Relay"); 
  digitalWrite(D(gateNumber), HIGH);    
  delay(openDuration);
  Serial.println("Close Relay");
  digitalWrite(D(gateNumber), LOW);    
}

uint8_t D(uint8_t index) {
  switch (index) {
    case 1: return D1;
    case 2: return D3;
  }
}  
As you can see, I reset the ESP8266 every 12h automatically. This is something temporary until I'm able to connect to the internet and add some new features.
As you can see the code is super simple, in the lack of time and a UI for my previous solution, I kept things pretty simple. Most of the time was invested in the hardware part - especially water tubes.
Once I recreate the UI, I want to be able to push custom time intervals to the controller and to be able to add reporting capabilities.
Even if I have some humidity sensors, I am not interested to integrate them, especially because I would need around 4 different sensors and the idea of having too many cables is not so appealing for me.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too