The ESP32 RFID Smart Security & Intrusion Alert System demonstrates an end-to-end access control and IoT telemetry application combining high-frequency RFID scanning, dual-state physical feedback, and automated cloud dispatch over encrypted HTTPS.
In this project, an ESP32 microcontroller interfaces with an MFRC522 13.56 MHz RFID reader over the Serial Peripheral Interface (SPI) bus and an I2C 16x2 character display. When a user presents a badge or key fob, the ESP32 captures and sanitizes its Unique Identifier (UID). If an authorized key is matched, the system triggers a welcome audio chime and illuminates a green confirmation LED. If an unauthorized badge or intruder card is detected, the firmware executes a zero-latency local alarm sequence (strobe red LED and 4-pulse buzzer warning) before dispatching an encrypted push alert directly to your smartphone through the Telegram Bot API.
This project introduces:
MFRC522 RFID Interfacing via Hardware SPI (MFRC522.h)
I2C Character Display Control (LiquidCrystal_I2C.h)
Non-Blocking Reconnection Architecture using millis() Timers
Hardware Required
ESP32 Development Board
Embedded URL Nibble Encoding for REST Payloads
Direct HTTPS Cloud Webhooks (WiFiClientSecure & HTTPClient)
Zero-Lag Event-Driven Hardware Prioritization
By completing this project, you will understand how to interface complex SPI and I2C peripherals simultaneously, handle credential logic, and deploy cloud notification pipelines without relying on paid third-party brokers.
Components Required
ESP32 DevKit V1 (30-Pin) × 1
RC522 13.56 MHz RFID Reader Module × 1
Mifare Classic 1K RFID Card / Key Fob × 2
16x2 Character LCD with I2C Backpack (PCF8574) × 1
Male-to-Male & Male-to-Female Jumper Wires × 1 Set
Micro-USB or Type-C Cable × 1
Circuit Connections
Design Note: The RC522 reader is strictly a 3.3V logic device. Connecting its power rail to 5V will permanently destroy its internal receiver circuitry. Tie all grounds together on a shared breadboard power rail to avoid floating reference voltages.
Step 1: Connect the MFRC522 RFID Reader (SPI Bus)
Connect the RFID module to the ESP32 primary hardware SPI bus:
3.3V (VCC) → ESP32 3V3(Strict: 3.3V only)
RST → ESP32 GPIO 4 (D4)
GND → Breadboard GND Rail
MISO → ESP32 GPIO 19 (D19)
MOSI → ESP32 GPIO 23 (D23)
SCK → ESP32 GPIO 18 (D18)
SDA (SS) → ESP32 GPIO 5 (D5)
IRQ → Leave Unconnected
Step 2: Connect the 16x2 I2C LCD
Connect the four pins of the I2C LCD backpack to the hardware I2C lines:
Inside setup(), the ESP32 flushes its stored flash network settings, initiates Station Mode (WIFI_STA), and disables modem sleep via WiFi.setSleep(false) to prevent packet drops. In loop(), network retries are throttled to 10-second intervals using non-blocking millis() tracking. This prevents CPU core panics and stops wifi:sta is connecting, return error driver loops.
Poll SPI Registers & Extract Card UID
The main loop continuously queries the RC522 using PICC_IsNewCardPresent() and PICC_ReadCardSerial(). When an RFID transponder enters the 13.56 MHz electromagnetic field, the firmware iterates through the module's byte array, converts the raw binary values into a two-digit uppercase hexadecimal string, and halts the card to prepare for the next read cycle.
Prioritize Immediate Physical Response
Traditional cloud devices often freeze while waiting for an HTTPS response. To eliminate physical lag, handleUnauthorized() drives the hardware first:
It sets RED_LED HIGH immediately.
It displays ! WARNING ! Access Denied on the LCD.
It executes an acoustic 4-pulse cycle on the buzzer pin (150 ms active, 80 ms pause) with zero latency.
Dispatch Cloud Webhook over Secure TLS
Once the local alarm cycle executes, sendTelegramAlert() constructs an encrypted outbound socket using WiFiClientSecure with client.setInsecure(). The string payload is passed through an onboard urlEncode() helper function, and an HTTPS GET request hits the Telegram Bot API endpoint:
This delivers an instant Markdown notification containing the unauthorized UID, lock status, and incident timestamp directly to your Telegram chat.
Expected Output
After uploading the firmware and opening the Serial Monitor at 115200 baud:
The LCD initializes and displays Connecting WiFi while the ESP32 associates with your 2.4 GHz network.
Upon successful association, the display changes to Security System / Tap ID Card... and the Serial Monitor prints the assigned local IP address.
Scanning Authorized Tag (1A4E12B0): The green LED lights up, a pleasant two-tone welcome chime sounds, and the screen confirms >> WELCOME! << Access Granted for 2.5 seconds before returning to idle.
Scanning Unauthorized Tag: The red LED instantly illuminates, the buzzer sounds an urgent 4-pulse alarm sequence, the LCD displays ! WARNING ! Access Denied, and your smartphone immediately receives an encrypted Telegram notification with the scanned UID.
Operational Troubleshooting
LCD Backlight On But No Characters Visible: Turn the small contrast potentiometer on the back of the I2C backpack using a small flathead screwdriver until the letters become sharp. Ensure the LCD VCC pin is wired to VIN (5V), not 3.3V.
RFID Module Fails to Detect Tags: Verify that the RC522 is wired to the exact hardware SPI pins (SCK: 18, MISO: 19, MOSI: 23, SDA: 5, RST: 4). Ensure your solder joints on the RC522 pin header are solid and not bridging adjacent pins.
Wi-Fi Times Out on Hotspot: Ensure your hotspot is configured strictly to 2.4 GHz (ESP32 cannot communicate with 5 GHz channels). If connecting through a mobile phone hotspot fails due to Protected Management Frame (PMF) negotiation, share your laptop's connection using the Windows 11 2.4 GHz Mobile Hotspot.
Buzzer Clicks Instead of Beeping: If using a passive buzzer, driving the pin HIGH only produces a dull click because it lacks an internal oscillator. Use an active buzzer (continuous sound when given 3.3V/5V DC) or implement PWM frequency modulation using the ESP32 ledcWrite() API.
What You Learned
By completing this project, you have learned:
How to interface and read high-frequency RFID transponders over hardware SPI
How to operate I2C character displays without blocking system execution
How to design safe non-blocking Wi-Fi reconnection loops in ESP-IDF/Arduino C++
How to send direct HTTPS REST API requests with URL encoding to cloud endpoints
How to prioritize critical real-time local hardware feedback over asynchronous cloud telemetry
.jpeg&w=3840&q=75)