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)

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"

#define DEFAULT_TIME_MS_1 4*60*1000
#define DEFAULT_TIME_MS_2   30*1000

void setup() {
  pinMode(D1, OUTPUT);
  pinMode(D3, OUTPUT);
  // This is required to read ADC values reliably
  // Delay is required only for debugging
  Serial.println("Setup complete");
void loop() {
  Serial.println("Open Valve 1:");
  triggerValve(1, DEFAULT_TIME_MS_1);
  Serial.println("Close Valve 1:");

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

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

void triggerValve(int gateNumber, int openDuration){
  Serial.println("Open Relay"); 
  digitalWrite(D(gateNumber), HIGH);    
  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.


Popular posts from this blog

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 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.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.