Time-Controlled Switch with ESP32 Web Server and DS3231 RTC

Devices on the same network can communicate using assigned IP addresses. Microcontrollers can function as web servers by listening for incoming HTTP requests. Socket programming provides the communication pathway: sockets are created and bound to specific IP addresses and ports (like port 80 for HTTP). The bind() method associates the socket with an address, while listen() starts accepting incoming connection requests. The accept() method waits for client connections and returns a new socket for each connection. After accepting connections, data is received using recv() and sent using send(). HTTP requests have a specific structure: the first line contains the method (GET), requested resource (URL path), and protocol version (HTTP/1.1), followed by headers and a blank line. Requests arrive as byte strings that must be decoded to regular strings using decode('utf-8'). The server parses requests by splitting on spaces to extract the HTTP method and URL path, enabling the server to determine which endpoint the client is accessing.

The Arduino Web Server demonstrates creating a web server on a microcontroller. The setup() function initializes serial communication for debugging, checks Wi-Fi connectivity, and starts a server on port 80. The loop() function continuously checks for incoming HTTP requests, reads them until finding a blank line (which marks the end of the request), and sends an HTML response back to the client. The response includes the Wi-Fi signal strength. HTTP is the standard protocol for web communication, with requests containing headers and responses containing headers followed by content.

This section covers the foundational concepts of hosting a web server on a microcontroller like the Raspberry Pi Pico. Key topics include: (1) Understanding how web servers enable bidirectional communication between devices and clients through web interfaces; (2) The distinction between serving web pages locally on the same network versus making them accessible over the internet; (3) The role of sockets as communication endpoints for receiving and sending data; (4) The importance of HTTP protocol basics including request-response cycles and response headers required by web browsers. These concepts form the theoretical foundation for building interactive IoT projects where web interfaces control hardware components.

HTTP (HyperText Transfer Protocol) is a network protocol used for transferring files on the internet, where clients send requests (like GET /on or GET /off) to servers, and servers respond with status codes (200 for success, 404 for failure) and data. In this ESP32 project, the microcontroller acts as a web server on port 80, receiving HTTP requests via WiFi and executing commands (turning an LED on or off) based on the request path, while sending HTML responses back to the client browser.

ESP32 microcontrollers can make HTTP client requests to web servers. When requesting code to connect to example.com and print the result to the serial monitor, ChatGPT generates code using the HTTPClient library. The code demonstrates how to establish a connection to a web server, make a GET request, and display the response. The IP address is printed to the serial monitor, and the web page content is retrieved and displayed.

This tutorial demonstrates how to interface the DS3231 RTC (Real-Time Clock) module with an ESP32 microcontroller using Arduino IDE. The DS3231 connects via I2C communication (SDA to pin 21, SCL to pin 22, VCC to 5V, GND to ground). The programming involves initializing the I2C interface with 400 kHz clock speed, reading temperature data in degrees Celsius, and retrieving time information including seconds, minutes, hours, day, date, month, and year. The code uses ESP_LOG function to print the date, time, and temperature values, which can be monitored through the serial monitor.

I²C (Inter-Integrated Circuit) is a serial communication protocol using two wires (SDA and SCL) for connecting low-speed peripherals to microcontrollers. It operates at standard speeds of 100kHz or fast mode at 400kHz, with maximum distance under 1 meter due to signal degradation. The DS3231 uses I²C to communicate with the Arduino via orange and yellow wires. The module includes a CR2032 coin cell backup battery that maintains time when main power disconnects. The DS3231 operates at 8MHz internally (vs 16MHz for standard Arduinos) but maintains sufficient accuracy for most applications. This architecture enables reliable, low-power timekeeping with minimal component count.

The I2C (Inter-Integrated Circuit) protocol, developed by Philips in the 1980s, is a synchronous two-wire communication interface (SCL for clock, SDA for data) that enables a single master device to communicate with multiple slave devices within an electronic system. The protocol operates at frequencies typically between 100 kHz and 400 kHz, with some devices supporting up to 5 MHz. Communication begins with a Start condition (SCL high, SDA falling edge) and ends with a Stop condition (SCL high, SDA rising edge). Data transfer involves sending a 7-bit slave address followed by a read/write bit, with slaves responding via acknowledgment (ACK) or non-acknowledgment (NACK) signals. For writing, the master sends 8-bit data to a specific register; for reading, the master initiates a Restart condition, sends the same address with a read bit, and the slave transmits 8-bit data back. External pull-up resistors are required due to the open-drain configuration of the bus lines.

This section covers the complete I2C communication protocol for interfacing with the DS1307 RTC. The write operation sequence involves: calling start() to initiate communication, sending device address with write mode (0xD0), sending the register address, verifying acknowledgment, then sending data bytes with acknowledgment verification after each byte. The read operation sequence involves: start(), device address in write mode, register address, restart operation to switch to read mode, device address in read mode (0xD1), and reading data byte by byte with acknowledgment verification. The RTC registers follow a specific sequence: seconds (0x00), minutes (0x01), hours (0x02), weekday (0x03), day (0x04), month (0x05), and year (0x06).

I2C (Inter-Integrated Circuit) is a synchronous communication protocol that uses two wires (SDA for data and SCL for clock) to connect a master device to one or more slave devices, where the master controls the communication by generating start and stop conditions. In ESP32 IDF SDK, I2C configuration requires setting up the peripheral with specific pins (SDA and SCL), enabling pull-up resistors, and configuring the clock speed (typically 400 kHz for standard mode). The communication sequence involves creating a link, sending a start condition, writing the device address, writing the register address, writing data, and sending a stop condition. The SDK provides simplified macros like `i2c_master_write_to_device` that automate this sequence, and reading uses a separate macro. Successful I2C communication requires consulting the device datasheet to determine the correct slave address and register map.

An electromagnetic relay is an electrically operated switch that uses a coil to control contacts, enabling low-power circuits to safely control high-power AC or DC loads; the relay has a coil that energizes when current flows through it, attracting a movable contact to switch between normally closed (NC) and normally open (NO) terminals, and when used with a transistor switch, it requires a freewheeling diode across the coil to protect the transistor from voltage spikes when the coil is de-energized.

Relays operate on electromagnetic principles where an energized coil creates a magnetic field that mechanically moves contacts to switch circuits. The control circuit (coil energization) and load circuit (contact connections) are electrically isolated, allowing completely different power supplies for each section. This isolation protects control electronics from high-voltage transients. Relays are rated for maximum voltage and current they can safely interrupt, such as 250V AC at 15A. AC switching benefits from natural zero-crossing points that help extinguish arcs, while DC requires additional measures since voltage never drops to zero. The coil requires continuous current (75mA when energized, 3mA when de-energized) to maintain its state, demonstrating that relays consume power even when not actively switching.

The relay can control AC loads by connecting the load in series with the relay's common terminal and one other terminal. The relay can safely handle up to 10 amps of load at 220V-240V AC. Exceeding this current rating can cause the relay to melt or fail. The relay can control various loads including fans, tube lights, and DC lights within this current limit. This makes the relay suitable for practical applications like automatic backup power switching for UPS systems.

A relay is an electromechanical switch containing a coil and contacts. When voltage is applied to the coil, current creates a magnetic field that attracts an anchor, closing contacts. Relays come in Normally Open (NO), Normally Closed (NC), and change-over configurations. Proper coil voltage is critical—too low causes unreliable operation; too high damages the coil. A flyback diode must be added across the coil to prevent 200+V voltage spikes during de-energization. Relays excel at switching high-current loads with minimal power loss and provide essential galvanic isolation between control and load circuits, enabling safe switching of 230V AC from 5V microcontroller signals.

Relays are electromagnetic switches controlled by small voltages (typically 5V). Simple relays switch on/off immediately with voltage changes, while latching relays maintain position after activation. AC relays can switch automatically because AC voltage crosses zero during each cycle. DC relays cannot switch off automatically because DC maintains constant polarity without zero crossings. High-current DC applications (up to 100A at 220V) require specialized DC relays with proper polarity markings. These relays are mounted on aluminum carriers for heat dissipation and cost approximately $5 with shipping under $10.