Smart Key Finder (IOT)

 

A Project Report

on

Smart Key Finder (IOT)

By

Mistry Jayeshkumar Bharatkumar Santosh (25208)

Shaikh Aayan Abdul Mannan Ashiya (25230)

Tiwari Vishal Rambelas Sunita (25209)

Pandey Anurag Pavan Kumar Manju (25207)

Mishra Saurabh Dharmraj Rekha Devi (25215)

Under the esteemed guidance of

                                       Mr. Mahesh Kudalkar

 

Submitted in partial fulfilment of the Requirements for

 the award of the Degree of

BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY)

SEMESTER V EXAMINATION

DEPARTMENT OF INFORMATION TECHNOLOGY

THAKUR COLLEGE OF SCIENCE AND COMMERCE

(Permanently Affiliated to University of Mumbai)

KANDIVALI (E) -400101, MUMBAI, MAHARASHTRA

A.Y. 2024-25

Synopsis

 

The project “Smart Key Finder – An IoT Based Key Locating Solution” aims to address the common problem of misplaced keys by designing a compact, low-cost, and efficient IoT-enabled device. Misplacing keys is a frequent issue that leads to stress and time loss, and traditional solutions like simple keychains or costly Bluetooth trackers are not always effective. To overcome this, the proposed solution uses an ESP32 microcontroller integrated with the Blynk IoT cloud platform, enabling the user to trigger an alert through a smartphone app or PC web dashboard. When the user presses the “Find My Key” button, the ESP32 receives the command via Wi-Fi and activates both a buzzer for audio alert and an LED for visual indication, helping the user quickly locate the keys. The system is powered by a 3.7V rechargeable Li-ion battery with a TP4056 charging module, ensuring portability and reusability. This project is designed to be user-friendly, cost-effective, and scalable, with applications not only for key finding but also for locating other small personal items. The expected outcome is a reliable smart device that bridges IoT with everyday life, while future scope includes integration with GPS tracking, Bluetooth Low Energy (BLE), and voice assistants like Alexa or Google Assistant.

 

 

1. Introduction

 

a. Objective and Scope of the Project

The primary objective of this project is to design and implement a Smart Key Finder system that addresses one of the most common problems in day-to-day life: misplacing keys. The device is intended to be cost-effective, compact, and user-friendly, ensuring that it can be widely adopted by students, working professionals, and households. By combining the power of IoT and wireless connectivity, the system provides an efficient way to locate misplaced keys in real time.

The device integrates both audio and visual alerts — a buzzer for sound and an LED light for visibility — which can be triggered remotely through the Blynk IoT application on either a smartphone or PC web dashboard. The ESP32 microcontroller, with its built-in Wi-Fi capabilities, serves as the heart of the system, ensuring seamless connectivity to the Blynk Cloud.

The scope of the project extends beyond just key finding. The same principle can be applied to locate other small but essential objects, such as wallets, bags, remote controls, or even ID cards. In larger institutions and offices, where misplacing keys can cause significant delays or security concerns, this project can serve as a reliable and affordable solution. The design is also scalable, allowing future integration of advanced features such as GPS-based location tracking, Bluetooth Low Energy (BLE), or voice assistant compatibility.

Thus, the project not only solves an immediate real-world problem but also lays the groundwork for more advanced IoT-based personal item tracking systems.

 

b. Theoretical Background

The Internet of Things (IoT) refers to the concept of connecting everyday objects to the internet so that they can collect, share, and respond to data. IoT technologies are rapidly transforming how we interact with our environment, from smart homes and wearable health trackers to industrial automation. At the core of IoT lies the principle of enabling communication between devices, cloud platforms, and end-users through wireless networks.

In this project, the IoT concept is applied by connecting a key-finding device to the internet using the ESP32 microcontroller. The ESP32 is a highly versatile, low-power, and cost-effective microcontroller with built-in Wi-Fi and Bluetooth capabilities. Its integration of wireless communication eliminates the need for additional modules, making it an ideal choice for compact IoT projects. With dual-core processing and multiple GPIO pins, ESP32 provides enough performance and flexibility to handle sensor data, device control, and cloud communication simultaneously.

The Blynk IoT Cloud platform serves as the middleware that connects the hardware with the user. Blynk allows developers to design dashboards with widgets (such as buttons, sliders, and notifications) that can directly interact with the device. By creating a datastream linked to virtual pins, users can trigger specific actions — in this case, turning on a buzzer and LED when the “Find My Key” button is pressed.

From a theoretical standpoint, this project also demonstrates the use of Client-Server communication models. The ESP32 acts as a client that connects to the Blynk server (cloud) via Wi-Fi. When the user presses a button in the Blynk app, the server transmits the command to the ESP32, which executes it by activating the connected hardware components.

In addition, the system design highlights key IoT concepts such as:

• Remote Accessibility: Control from anywhere using the internet.
• Real-Time Communication: Immediate response when a button is pressed.
• Scalability: The same IoT framework can support more devices in the future.
• Energy Efficiency: ESP32 and Li-ion battery provide a portable, low-power solution.

By grounding itself in IoT principles, the project showcases how even simple hardware components can be transformed into smart solutions through cloud integration and wireless connectivity.

 

c. Problem Definition

Keys are one of the most commonly misplaced items in day-to-day life, leading to stress, wasted time, and inconvenience. Existing solutions such as Bluetooth trackers are often expensive and not widely accessible, while ordinary keychains provide no functionality to actively locate the keys. Therefore, there is a need for an affordable, portable, and user-friendly IoT-based device that enables users to quickly locate their keys when misplaced.

 

d.User Requirements / Software Requirement Specification (SRS)

The Smart Key Finder project is designed keeping in mind the end-user needs for simplicity, affordability, and practicality. The following requirements have been identified:

1. Portability and Compact Design
• The device must be small and lightweight, making it easy to attach to a keychain or keep in a pocket.
• The enclosure should be durable enough for daily use.
2. Dual Alert Mechanism
• The system must provide both visual indication (via LED) and audio indication (via buzzer) when triggered.
• The alerts should be strong enough to be noticeable even in moderately noisy environments.
3. Remote Control via IoT
• Users should be able to activate the buzzer and LED remotely through the Blynk mobile application or PC web dashboard.
• The system must support real-time command execution, ensuring minimal delay between user input and device response.
4. Battery-Powered Operation
• The device should operate on a rechargeable Li-ion battery, making it portable and independent of wired power sources.
• Charging should be supported through a TP4056 charging module for convenience.
5. Cost-Effectiveness and Usability
• The system must be designed with low-cost components so it remains affordable for students, households, and office users.
• It should feature a user-friendly interface requiring minimal technical knowledge for operation.
6. Wi-Fi Connectivity
• The ESP32 must connect to a 2.4 GHz Wi-Fi network for communication with the Blynk IoT Cloud.
• The system should ensure reliable connectivity to enable continuous remote access.

3. System analysis and design (Hardware Projects)

3.1 Detailed life cycle of the project

A hardware-oriented life cycle adapted for this student IoT project, with phases, activities and deliverables:

1. Requirement & Feasibility (Week 1)

• Activities: Define problem, gather user requirements, set budget, research similar products.
• Deliverable: Project synopsis, SRS (user requirements), bill of materials (initial).

2. System Design & Planning (Week 2)

• Activities: High-level architecture, block diagrams, select components, order parts, project schedule (Gantt/PERT).
• Deliverable: System architecture diagram, detailed component list, Gantt chart.

3. Prototype Design (Week 3)

• Activities: Breadboard prototype wiring, schematic/circuit diagram, PCB/perfboard planning if needed.
• Deliverable: Working prototype on breadboard (or direct-wired), schematic diagram.

4. Firmware & Software Development (Week 3–4)

• Activities: Implement basic firmware (LED + buzzer test), Wi-Fi connection, integrate Blynk, debug serial output.
• Deliverable: Stable firmware (tested), source code, upload instructions.

5. Integration & Testing (Week 4)

• Activities: Combine hardware + firmware, battery charging and powering tests, run functional and stress tests.
• Deliverable: Test report (test cases, pass/fail), screenshots/logs.

6. Packaging & Finalization (Week 5)

• Activities: Solder final circuit to perfboard or design small PCB, mount components into enclosure, label ports.
• Deliverable: Final prototype in enclosure, charging port accessible.

7. Documentation & Presentation (Week 5)

• Activities: Prepare report, deployment instructions, user manual, PPT, demo script.
• Deliverable: Final report, user manual, presentation slides.

8. Maintenance & Future Enhancements (Post-delivery)

• Activities: Bug fixes, optional add-ons like GPS, BLE, voice assistant integration.
• Deliverable: Maintenance log, future scope list.

 

3.2 Circuit Diagram (textual description + wiring table)

Note: include the provided drawing/PNG of your schematic in the report. Below is a clear wiring description to accompany the diagram.

High-level wiring summary

• Power: 3.7 V Li-ion battery → TP4056 charging module → (via boost/regulator) → power ESP32 VIN (or use ESP32 board Li-Po input if present). During development use USB power.
• ESP32 GND is common ground for all components.
• LED: GPIO4 → 220Ω resistor → LED anode; LED cathode → GND.
• Buzzer: GPIO5 → (base resistor + NPN transistor) → transistor collector to buzzer negative; buzzer positive → Vcc (3.3 V or 5 V depending on buzzer rating); transistor emitter → GND. Add diode if buzzer is inductive.

Pin mapping table (recommended)

Component	Module Pin	ESP32 Pin	Notes
LED (+ via 220Ω)	LED anode (through resistor)	GPIO 4	Resistor in series to limit current
LED (−)	LED cathode	GND	Connect to any ESP32 GND pin
Buzzer (+)	Buzzer positive	Vcc (3.3V or 5V)	Check buzzer rated voltage
Buzzer (−)	Buzzer negative → transistor collector	—	Use NPN transistor as a low-side switch
Buzzer control (base resistor)	base resistor (1kΩ)	GPIO 5	Drives transistor base; add base resistor
Transistor emitter	—	GND	Common ground
TP4056 B+ / B- (battery)	B+ / B-	Battery + / Battery −	TP4056 charges the cell; observe polarity
TP4056 OUT (if present)	OUT+ / OUT-	Boost converter input	Use boost to generate stable 5V if feeding VIN

Example wiring steps (practical):

1. Development (USB): Connect ESP32 to PC via USB for programming and testing.
2. LED: Solder or connect a 220Ω resistor to the LED anode; other end of resistor → GPIO4. LED cathode → any GND on ESP32.
3. Buzzer with transistor:
• Buzzer positive → Vcc (preferably 3.3 V if buzzer supports it; otherwise 5 V via boost).
• Buzzer negative → transistor collector (e.g., 2N2222).
• Transistor emitter → GND.
• GPIO5 → 1kΩ resistor → transistor base.
• Add a diode across buzzer if it is inductive (cathode to Vcc, anode to transistor collector).
4. Battery & TP4056:
• Battery to TP4056 B+/B-.
• USB 5V → TP4056 IN+/IN- for charging.
• Battery output feeds boost/regulator if needed to get stable VIN for ESP32.
5. Common ground: Connect TP4056 GND, ESP32 GND, boost GND and component GNDs together.

 

3.3 Component level description and Specifications

1. ESP32 DevKit (ESP-WROOM-32)

• Role: Main microcontroller — Wi-Fi, (optional) Bluetooth, GPIO control, program storage.
• Key specs: Dual-core Tensilica LX6 ~240 MHz, 4 MB flash (varies), 320 KB SRAM, 3.3 V logic, built-in Wi-Fi 802.11 b/g/n, Bluetooth (BLE + Classic depending on module).
• Pins used: GPIO4 (LED), GPIO5 (Buzzer control), 3V3, GND, VIN/USB for power and programming.

2. Buzzer (Active or Passive)

• Role: Audible alert.
• Active buzzer: Requires only DC to sound; easier to use from GPIO with transistor for higher current. Typical voltage: 3–5 V.
• Passive buzzer: Requires PWM to produce tone. Use transistor and/or driver.
• Specification examples: Operating voltage 3.3–5 V, typical current 10–30 mA (active) or higher for louder buzzers.

3. LED + 220Ω resistor

• Role: Visual alert.
• Spec: Standard 3 mm or 5 mm LED, forward voltage ~2.0 V (red) / 3.0 V (blue/white), resistor 220 Ω to limit current to safe level (~10–15 mA).

4. 3.7 V Li-ion Battery (single cell)

• Role: Portable power supply.
• Spec: Typical capacity 500–1200 mAh (choose based on size and runtime). Nominal voltage 3.7 V, charge voltage 4.2 V.
• Safety: Do not short terminals; use protection if battery lacks built-in protection circuit.

5. TP4056 Charging Module

• Role: Linear Li-ion battery charger with micro-USB input.
• Spec: Input 5 V (USB), charging current adjustable via resistor (default 1A or 500 mA), B+/B- battery terminals. Include module with battery protection (DW01 + FS8205A recommended) if using bare cells.
• Note: TP4056 only charges cell; it does not boost voltage to 5 V.

6. NPN Transistor (e.g., 2N2222 / 2N3904)

• Role: Switch to drive buzzer (protects GPIO, allows higher current).
• Spec: Collector current >100 mA, base resistor 1kΩ recommended.

7. Flyback Diode (e.g., 1N4148 / 1N4007) — if buzzer inductive

• Role: Protect transistor from voltage spikes when driving inductive loads.

8. Optional Boost Converter (e.g., MT3608)

• Role: Step up battery 3.7 V to stable 5 V to feed VIN/5V if the ESP32 power section expects >4.5 V.
• Spec: Input 2–12 V, output adjustable to 5 V, rated current ≥500 mA.

9. Miscellaneous

• Jumper wires, male/female headers, switch (ON/OFF), USB cable, enclosure, double-sided tape, soldering items.

---

3.4 Architecture Design

Functional layers

1. User Layer (Presentation):
• Blynk app (mobile) / Web Dashboard — user interface to send commands.
2. Cloud/Middleware:
• Blynk Cloud — receives button press events and forwards commands to device.
3. Device Layer (Edge):
• ESP32 — connects to Wi-Fi, receives commands from Blynk, executes actions.
4. Hardware Output Layer:
• LED (visual) and Buzzer (audio) — physical indicators attached to the key.

Data & control flow (sequence)

• User presses button in Blynk app → Blynk Cloud receives event → Cloud forwards event to ESP32 over Wi-Fi → ESP32 parses virtual pin message → ESP32 sets GPIO HIGH → LED and buzzer activate → user finds key and presses STOP → ESP32 sets GPIO LOW.

Security considerations (brief)

• Use Blynk Auth Token (device-specific) to prevent unauthorized control.
• Keep Wi-Fi credentials secure; prefer WPA2 network.
• Limit physical access to the enclosure to prevent tampering.

---

3.5 Block Diagram (text + ASCII)

Use this block diagram in the report; you can copy into a slide or draw a neat graphic version.

Block description

• User: interacts via Blynk app/button.
• Blynk Cloud: mediator; device authenticates with Token.
• ESP32: receives commands, toggles GPIOs.
• LED & Buzzer: output devices.
• Power subsystem: battery + charger; optionally boost to VIN.

 

4. System Planning (PERT Chart / Gantt Chart)

a. Process Involved

The development of the Smart Key Finder (IoT Project) follows a structured series of processes, ensuring that the project is completed within the given timeframe and budget. The processes include:

1. Problem Identification and Requirement Gathering
• Understanding the frequent issue of misplaced keys.
• Gathering user requirements (portability, alerts, cost, IoT integration).
2. System Design
• Designing block diagram, architecture, and circuit schematic.
• Selecting appropriate hardware (ESP32, buzzer, LED, TP4056).
3. Procurement of Components
• Purchasing ESP32, LED, buzzer, Li-ion battery, charger module, etc.
4. Circuit Assembly and Prototype Development
• Connecting components on breadboard or direct wiring.
• Testing basic functionality (LED blink, buzzer sound).
5. Firmware Development
• Programming ESP32 with Arduino IDE.
• Integrating Wi-Fi connectivity and Blynk Cloud control.
6. Integration and Testing
• Combining hardware and software.
• Running test cases (button press → buzzer/LED response).
7. Enclosure Design and Final Implementation
• Assembling device into a portable case.
• Ensuring USB port access for charging.
8. Documentation and Presentation
• Preparing report, PPT, user manual, and demo script.

---

b. Methodology Adopted

The project follows a prototyping model methodology commonly used in hardware and IoT projects:

1. Requirement Analysis – Initial identification of problem and user needs.
2. Quick Design – Creation of system architecture, block diagram, and circuit plan.
3. Prototype Development – Assembling hardware prototype on breadboard/PCB and writing initial code.
4. User Testing & Feedback – Testing the device functionality with sample users (team members).
5. Refinement – Making necessary improvements (better code, battery optimization).
6. Final Product Delivery – Completing the project with proper enclosure, documentation, and demonstration.

This methodology was chosen because:

• It allows early testing of hardware.
• Iterations are possible (debugging circuit, modifying code).
• It fits well within the short academic project timeline.

---

PERT Chart / Gantt Chart (Suggested Timeline)

Week	Task
1	Problem identification, requirement analysis, literature survey
2	System design (block diagram, architecture, circuit schematic)
3	Component procurement and prototype circuit assembly
4	Firmware development and Blynk integration
5	Integration testing and debugging
6	Final assembly into enclosure + charging setup
7	Documentation, report writing, PPT preparation, and demo rehearsals

 

 

5. System Implementation

The implementation phase involves the actual realization of the Smart Key Finder system by combining hardware components, circuit design, firmware coding, and IoT integration through the Blynk platform. Below are the steps and screenshots (to be inserted from your testing environment).

 

5.1 Arduino IDE Setup and Code Upload

• The ESP32 was programmed using the Arduino IDE.
• Necessary libraries such as WiFi.h and BlynkSimpleEsp32.h were installed.
• The code was written to connect ESP32 with Wi-Fi and the Blynk cloud, and to control the LED and buzzer using virtual pin V0.

Explanation:
This step ensures that the ESP32 firmware has the correct instructions to communicate with the Blynk IoT cloud and respond to user commands from the app/web dashboard.

 

5.2 Serial Monitor Output

• After uploading the code, the Serial Monitor (115200 baud) was used to verify Wi-Fi and Blynk connectivity.
• The ESP32 successfully connected to the Wi-Fi network and authenticated with the Blynk server using the unique Auth Token.

Explanation:
This step confirms that the ESP32 is online, connected to both the Wi-Fi network and the Blynk IoT cloud, ready to accept remote commands.

 

5.3 Blynk Web Dashboard Implementation

• A template was created in the Blynk cloud console with Template ID and Auth Token.
• A datastream (V0) was added for control.
• A button widget was placed on the web dashboard to toggle the LED and buzzer ON/OFF.

Explanation:
The button on the Blynk web dashboard acts as a virtual switch. When toggled, the Blynk cloud sends a command to the ESP32, which in turn activates or deactivates the LED and buzzer.

---

5.4 Mobile App Integration

• The Blynk IoT mobile app was installed and linked with the same device.
• A button widget was added and configured with datastream V0.
• The ESP32 was successfully controlled from the mobile app, enabling real-time switching.

Explanation:
This demonstrates the portability and ease of use of the system. Users can locate their keys by simply pressing a button on their smartphone.

---

5.5 Hardware Circuit Implementation

• The ESP32 was connected to the LED and buzzer according to the circuit diagram.
• A 3.7V Li-ion battery with a TP4056 charging module was used to power the device.
• The circuit was initially tested on a breadboard and later transferred to a compact setup.

Explanation:
This is the physical realization of the Smart Key Finder. The buzzer provides an audio alert, while the LED offers a visual indication when the key is triggered via the app.

---

5.6 Working Demonstration

• When the user taps the “Find My Key” button on the app/web dashboard, the ESP32 activates the LED and buzzer simultaneously.
• The sound and light make it easy for the user to quickly identify the location of their misplaced keys.

 

 

7. System Testing

i. Methodology Used for Testing

The testing of the Smart Key Finder system was carried out using the Black-Box Testing Methodology, where the focus is on input–output validation without delving into the internal code logic. The tests ensured that:

• The ESP32 successfully connects to the Wi-Fi network and Blynk Cloud.
• The mobile app/web button (V0) correctly controls the LED and buzzer.
• The system provides both audio and visual alerts as intended.
• The device operates properly in both USB-powered and battery-powered modes.
• The charging mechanism using the TP4056 module works as expected.

This methodology was chosen because it aligns with the real-world use case — the system is judged based on its actual functionality and user interaction.

---

ii. Test Report

Test Case ID	Description	Input Action	Expected Output	Actual Output	Status
TC-01	Wi-Fi Connectivity	Power ON device with correct SSID/Password	ESP32 connects to Wi-Fi and prints IP addr	Works as expected	Pass
TC-02	Blynk Cloud Connection	Use valid Auth Token	ESP32 connects to Blynk Cloud (Ready msg)	Works as expected	Pass
TC-03	LED Trigger via Blynk App	Press ON button in Blynk (V0)	LED on GPIO4 should glow	LED glows	Pass
TC-04	Buzzer Trigger via Blynk App	Press ON button in Blynk (V0)	Buzzer on GPIO5 should sound	Buzzer sounds	Pass
TC-05	Dual Output Check	Press ON button in Blynk (V0)	Both LED and buzzer activate together	Both work fine	Pass
TC-07	Battery-Powered Operation	Run on Li-ion battery only	Device functions normally	Works as expected	Pass
TC-08	TP4056 Charging Test	Connect USB charger to TP4056 module	Battery charges, CHRG LED shows status	Works fine	Pass
TC-09	Range Test	Use app from ~10m away on Wi-Fi	Device responds instantly	Responds properly	Pass
TC-10	Invalid Wi-Fi/Token	Wrong credentials in code	Device fails to connect	Fails as expected	Pass

 

8. System Maintenance and Evaluation

System Maintenance

The Smart Key Finder requires minimal maintenance, but the following aspects are important for reliable operation:

• Battery Care: Recharge the 3.7V Li-ion battery regularly using the TP4056 charging module. Avoid over-discharge or exposure to extreme temperatures to extend battery life.
• Firmware Updates: The ESP32 firmware can be updated anytime through Arduino IDE to fix bugs or add new features.

 

 

 

 

9. User / Operational Manual

9.1 Introduction

The Smart Key Finder is an IoT-based system designed to help users quickly locate misplaced keys using audio (buzzer) and visual (LED) alerts. The device is controlled remotely via the Blynk mobile app or web dashboard, using Wi-Fi connectivity.

---

9.2 Hardware Setup

1. Ensure the Li-ion battery is charged using the TP4056 charging module.
2. The device can also be powered via the USB port of ESP32 during testing.
3. Attach the device to the keychain using the enclosure provided.

---

9.3 Software Setup

1. Blynk App (Mobile/Web):
• Download and install Blynk IoT app (Android/iOS).
• Alternatively, open the Blynk Web Dashboard on PC.
2. Login/Register:
• Create a Blynk account and log in.
• Add the device using Auth Token generated from the Blynk Cloud.
3. Interface:
• Add a Button Widget linked to virtual pin V0.
• Label it as “Find My Key”.

---

9.4 Operating Instructions

1. Power on the Smart Key Finder (battery or USB).
2. Open the Blynk app or web dashboard.
3. Press the “Find My Key” button (V0):
• LED glows.
• Buzzer sounds.
4. Once the keys are found, press the button again to switch OFF the alerts.

---

9.5 Security Aspects

• Auth Token Security: Each device is linked to a unique Blynk Auth Token. Do not share it with unauthorized users.
• Wi-Fi Security: Always use a secured WPA2 Wi-Fi network. Avoid using public or open networks.
• Firmware Security: Update ESP32 firmware only from trusted sources to prevent malicious code injection.

 

9.6 Access Rights

• Administrator (Owner): Full control via Blynk app/web, including device setup, firmware updates, and network configuration.
• User: Can only press the button to activate or deactivate the key-finder alerts.
• Guest Access: Not allowed, unless explicitly shared by the owner through Blynk app invite.

 

9.7 Backup and Recovery

• Wi-Fi Change: If the Wi-Fi SSID/Password changes, update credentials in the Arduino IDE code and re-upload to ESP32.
• Blynk Account Recovery: Use the registered email to reset password if login credentials are lost.
• Device Reset: In case of malfunction, reflash firmware via Arduino IDE and reconfigure in Blynk.

---

9.8 Controls

• On/Off Button (Blynk App/Web): Main control for activating buzzer and LED.
• Hardware Reset: Press ESP32’s EN/Reset button to reboot the device.
• Power Control: The device automatically switches between USB power and battery power when charging.

STEPS:

Step 1: Required Materials and Components

So you are ready, great!

Here’s what you’ll need for this project:

• ESP32 development board (e.g., ESP32 DevKit V1)
• Active buzzer (3.3V)
• NPN transistor (e.g., 2N3904)
• Breadboard and jumper wires
• USB cable for programming
• Optional: 3.7V LiPo battery with a voltage regulator (if you want to run it standalone later)

 

Step 2: ESP32 Getting Started

I have worked with many microcontrollers, and ESP32 is one of the most powerful and versatile ones. It has Wi-Fi, Bluetooth, dual-core processing, and plenty of GPIO pins compared to ESP-01.

Some quick points about ESP32:

• It operates at 3.3V logic level (never connect 5V directly to GPIOs).
• You can program it directly using the Arduino IDE via USB, no extra programmer required.
• It has multiple boot modes, but normally you don’t need to toggle pins manually. The onboard USB-to-serial chip handles flashing automatically.

Reset and Boot buttons:
Most ESP32 boards have two small buttons:

• EN (Reset): Restarts the chip.
• BOOT: Used if manual flashing is ever needed (usually not necessary in Arduino IDE).

---

Step 3: Preparing the Buzzer for ESP32

There are two types of buzzers:

• Active buzzer: Makes sound when supplied with voltage.
• Passive buzzer: Needs PWM to generate tones.

We’ll use an Active 3.3V buzzer.

Since ESP32 GPIO pins can only provide limited current (~12 mA), we’ll use an NPN transistor (2N3904) as a switch to safely drive the buzzer.

Connections:

• ESP32 GPIO (e.g., GPIO 23) → 1kΩ resistor → transistor base
• Transistor emitter → GND
• Transistor collector → Negative terminal of buzzer
• Positive terminal of buzzer → 3.3V

This way, ESP32 can control the buzzer safely.

 

Step 4: Getting Ready for Programming

Let’s set up the Arduino IDE for ESP32.

1. Open Arduino IDE.
2. Go to File > Preferences.
3. In the Additional Boards Manager URLs field, paste this link:
4. https://dl.espressif.com/dl/package_esp32_index.json
5. Go to Tools > Board > Boards Manager.
6. Search for esp32 and install esp32 by Espressif Systems.
7. Now go to Tools > Board > ESP32 Arduino and select your ESP32 board (e.g., ESP32 Dev Module or DOIT ESP32 DevKit V1).

Done! Arduino IDE is now ready to program your ESP32.

 

 

10. Conclusion and Scope for Future Work

Conclusion

The Smart Key Finder project successfully demonstrates how IoT can be applied to solve simple yet common real-life problems. By integrating an ESP32 microcontroller, LED, buzzer, and the Blynk IoT platform, the system provides a reliable and low-cost solution for locating misplaced keys.

The device is:

• Compact – can be attached to a keychain.
• Affordable – total cost within ₹1,200, making it much cheaper than commercial alternatives.
• Efficient – uses rechargeable battery and simple Wi-Fi connectivity.
• User-friendly – easily operated through a mobile or web app.

Through rigorous testing, the system was found to be stable, responsive, and effective in meeting all user requirements.

 

Scope for Future Work

While the current implementation is functional and practical, there are several enhancements that can be added in future versions:

1. Bluetooth Low Energy (BLE) Integration
• Allow the device to work without Wi-Fi, improving portability and range indoors.
2. GPS Tracking
• Adding a GPS module for precise outdoor location tracking in case keys are lost outside the house.
3. Mobile App Enhancements
• Adding features like location history, last seen location, and customizable alert sounds.
4. Battery Optimization
• Implementing low-power modes in ESP32 to increase battery life.
5. Multi-Device Support
• Single app controlling multiple trackers (keys, wallet, bag, TV remote, etc.).
6. Voice Assistant Integration
• Compatibility with Google Assistant or Alexa for voice-based key finding.

 

• Hardware Checks: Ensure all connections remain secure. If soldered, periodically check joints for looseness. Replace faulty components (LED, buzzer, battery) if needed.
• Network Settings: Update Wi-Fi SSID/Password or Blynk Auth Token in the firmware if there is a change in the user’s network or cloud template.

 

System Evaluation

The system was evaluated against its objectives and user requirements:

• Functionality: Successfully provides both audio (buzzer) and visual (LED) alerts when triggered from Blynk app or web dashboard.
• Performance: Fast response (<1 second) to commands; buzzer is loud and LED visible in most environments.
• Usability: Compact, portable, and easy to operate even for non-technical users.
• Economics: Total cost (~₹1,200) is far lower than commercial alternatives. Maintenance cost is negligible.
• Reliability: Stable operation during repeated testing in USB-power and battery-power modes without failures.
• Conclusion

The Smart Key Finder is a low-cost, reliable, and user-friendly IoT solution. It meets all defined objectives, requires very little maintenance, and has been evaluatedto perform consistently in real-world use.

11. References

1. Bahga, A., & Madisetti, V. (2015). Internet of Things: A Hands-On Approach. Universities Press.
2. Rajkamal (2019). Internet of Things: Architecture and Design Principles. McGraw-Hill Education.
3. Hanes, D., Salgueiro, G., Grossetete, P., Barton, R., & Henry, J. (2017). IoT Fundamentals: Networking Technologies, Protocols, and Use Cases for the Internet of Things. Cisco Press.
4. Tzafestas, S. (2018). Introduction to Mobile Robot Control. Elsevier. (For IoT-based control mechanisms).
5. Espressif Systems (2023). ESP32 Technical Reference Manual. Retrieved from: https://docs.espressif.com/
6. Blynk IoT Platform (2024). Getting Started with Blynk IoT. Retrieved from: https://blynk.io
7. Sharma, P., & Kumar, R. (2020). “IoT Based Smart Security and Alert System.” International Journal of Emerging Technologies in Engineering Research, 8(6), 45–49.
8. Ali, M., & Anwar, S. (2021). “Low-Cost IoT Based Smart Tracking Device.” IEEE International Conference on Computing, Electronics & Communications Engineering (iCCECE).
9. Arduino Community (2023). ESP32 with Arduino IDE Setup Guide. Retrieved from: https://docs.arduino.cc
10. Hackster.io (2022). IoT Key Finder Projects and Tutorials. Retrieved from: https://www.hackster.io/
11. TP4056 Datasheet. (2018). 1A Li-Ion Battery Charger with Protection. Retrieved from: https://datasheetspdf.com
12. MT3608 Datasheet. (2020). DC-DC Step-Up Converter Module. Retrieved from: https://components101.com
13. Wokwi IoT Simulator (2024). ESP32 Online Circuit Simulation Platform. Retrieved from: https://wokwi.com
14. IEEE Internet of Things Journal. (2022). “Advances in Smart Consumer IoT Devices.” IEEE Xplore.
15. GeeksforGeeks (2024). Introduction to IoT and Applications. Retrieved from: https://www.geeksforgeeks.org