Multi Smart Safe Locker System

An ESP32 smart locker system designed for secure and efficient access management. It provides a web interface for configuration, email-based user authorization, and seamless unlocking via the Smart Link mobile app, making it ideal for individuals, organizations, and homeowners.

Contents

1. Features
2. System Responses
3. System Flow
   • System Web Interface Flow
   • Smart Link and Firmware System Flow
4. Setup
   • Firebase Project Setup
   • Firmware Configuration
   • Uploading HTML Files
5. Usage
   • Smart Link Integration
6. Admin Panel Web Interface Previews
7. Libraries

1. Features

Feature	Description
Remote Setup & Control	Seamlessly manage locker settings through the locally hosted ESP32 web interface, providing an easy way to configure the system.
Wi-Fi Configuration	Admins can configure Wi-Fi SSID and password for quick network setup, ensuring smooth connectivity for the device.
Secure User Authorization	Access is granted by adding the Gmail IDs that users used to sign up on the app, ensuring only authorized individuals can unlock the locker.
Real-Time Notifications	The WebSocket sends real-time timeout notifications to users when the locker is about to auto-lock.
Firmware Revocation	Firebase is only used for firmware-level restrictions for developers.
Individualized Auto-Lock Timers	Each locker has a unique 20-second auto-lock timer that ensures security by re-locking the locker after each use.
Fingerprint Authentication	The app prompts users for fingerprint authentication before submitting their unlock request to the firmware, adding an extra layer of security.

---

2. System Responses

Type	Status Code	Message
Locker Unlocked	200	Locker (GPIO number i.e 14) has been unlocked.
WebSocket connection exists	409	Websocket connection is already established!
Access Denied	403	Access Denied. Please contact the admin to gain access.
Firmware Restrictions	403	Locker access is restricted. Contact Developers for further details.
Network Connection Issues	403	Unable to connect. Please contact the admin to configure the system's network settings.
Invalid or malformed JWT	401	Unauthorized! Code - 2
JWT signature validation failed	401	Unauthorized! Code - 3
Invalid email format	400	Invalid email format.
Invalid token format	400	Invalid token format.

3. System Flow

System Web Interface Flow

graph TD
    A[Access Web Interface: 192.168.4.1] --> B[Login Page]
    B --> C{Is Login Successful?}

    %% Login Handling
    C -->|No| B  
    C -->|Yes| D[Admin Dashboard]

    %% Admin Settings & Actions
    D --> E[Change Wi-Fi Settings]
    D --> F[Add Authorized User]
    D --> G[Change Web Interface Password]
    D --> H[Reboot Firmware Manually]
    D --> I[Change Device SSID & Password]

    %% Reboot Handling (All settings changes trigger reboot)
    E --> X[System Rebooting Page]
    F --> X
    G --> X
    H --> X
    I --> X

    %% Reboot Success Page
    X[The system has rebooted successfully! You can now close this page safely.]

    %% Styling
    style A fill:#ffffff,stroke:#000000,stroke-width:2px,color:#000000
    style B fill:#f0f0f0,stroke:#000000,stroke-width:2px,color:#000000
    style C fill:#d9d9d9,stroke:#000000,stroke-width:2px,color:#000000
    style D fill:#e6e6e6,stroke:#000000,stroke-width:2px,color:#000000
    style E fill:#e6f7ff,stroke:#000000,stroke-width:2px,color:#000000
    style F fill:#e6ffe6,stroke:#000000,stroke-width:2px,color:#000000
    style G fill:#ffffe6,stroke:#000000,stroke-width:2px,color:#000000
    style H fill:#f0f0f0,stroke:#000000,stroke-width:2px,color:#000000
    style I fill:#f0f0f0,stroke:#000000,stroke-width:2px,color:#000000
    style X fill:#ffcc99,stroke:#000000,stroke-width:2px,color:#000000

Loading

---

Smart Link and Firmware System Flow

flowchart TD
    %% Level 1 – Authentication
    A[Smart Link App] --> B[Fingerprint Authentication Screen]
    B --> C{Fingerprint Authentication Succeeds?}
    C -- Yes --> D[Request Sent to Firmware Local Server & WebSocket]
    C -- No --> N[Show: Locked Out Due to Too Many Attempts. Please Try Again Later.]
    N --> B

    %% Level 2 – Connectivity Check
    D --> O{Is Firmware Connected to Internet?}
    O -- No --> X[Show: Unable to Connect. Please Contact the Admin to Configure the System's Network Settings.]
    X --> B
    O -- Yes --> F[Check Firebase Authorization for Firmware]

    %% Level 3 – Firebase Authorization
    F -- Not Authorized --> G[Show: Locker Access is Restricted. Contact Developers for Further Details.]
    G --> B
    F -- Authorized --> H[Verify JWT Signature in Request]

    %% Level 4 – JWT Verification
    H --> I{Is JWT Valid?}
    I -- Yes --> J[Check User Authorization in Firmware]
    I -- No --> K{Is error due to JWT Signature Issue?}
    K -- Yes --> M[Show: Unauthorized! - Code 3]
    K -- No --> L[Show: Unauthorized! - Code 2]
    M --> B
    L --> B

    %% Level 5 – User Authorization
    J --> Q{User Authorized?}
    Q -- Yes --> R[Unlock Locker]
    Q -- No --> Y[Show: Access Denied]
    Y --> B

    %% Level 6 – Locker Operation
    R --> S[Start Timer for User]
    S --> T[Locker Countdown 20s for User]
    T --> U[Locker Auto-Locks or User Locks Locker]
    U --> B

    %% Styling
    style A fill:#ffffff,stroke:#000000,stroke-width:2px,color:#000000
    style B fill:#f0f0f0,stroke:#000000,stroke-width:2px,color:#000000
    style C fill:#d9d9d9,stroke:#000000,stroke-width:2px,color:#000000
    style D fill:#e6e6e6,stroke:#000000,stroke-width:2px,color:#000000
    style N fill:#ff6666,stroke:#000000,stroke-width:2px,color:#000000
    style O fill:#ffcc99,stroke:#000000,stroke-width:2px,color:#000000
    style X fill:#ff9999,stroke:#000000,stroke-width:2px,color:#000000
    style F fill:#f9f9f9,stroke:#000000,stroke-width:2px,color:#000000
    style G fill:#ffcccc,stroke:#000000,stroke-width:2px,color:#000000
    style H fill:#f2f2f2,stroke:#000000,stroke-width:2px,color:#000000
    style I fill:#cccccc,stroke:#000000,stroke-width:2px,color:#000000
    style K fill:#ffcc99,stroke:#000000,stroke-width:2px,color:#000000
    style M fill:#ffcccc,stroke:#000000,stroke-width:2px,color:#000000
    style L fill:#ffcccc,stroke:#000000,stroke-width:2px,color:#000000
    style J fill:#f2f2f2,stroke:#000000,stroke-width:2px,color:#000000
    style Q fill:#cccccc,stroke:#000000,stroke-width:2px,color:#000000
    style Y fill:#ffcccc,stroke:#000000,stroke-width:2px,color:#000000
    style R fill:#c1e6c1,stroke:#000000,stroke-width:2px,color:#000000
    style S fill:#ffffb3,stroke:#000000,stroke-width:2px,color:#000000
    style T fill:#ffeb99,stroke:#000000,stroke-width:2px,color:#000000
    style U fill:#d1f2ff,stroke:#000000,stroke-width:2px,color:#000000

Loading

---

4. Setup

Firebase Project Setup

1. Create a Firebase project and obtain Firebase Web API Key and Realtime Database (RTDB) URL.
2. Add these to the config.hpp file:

#define FIREBASE_WEB_API_KEY "<your-firebase-web-api-key>"
#define FIREBASE_RTDB_REFERENCE_URL "<your-firebase-RTDB-reference-url>"

Firmware Configuration

Set REGISTER_ESP_ON_FIREBASE to true in config.hpp for initial device registration. Compile and upload the firmware to the ESP32. After registration, set REGISTER_ESP_ON_FIREBASE back to false.

Uploading HTML Files

1. Install the arduino-littlefs-upload plugin.
2. Place the web interface HTML files in the data directory.
3. Use the plugin to upload these files to the ESP32.

5. Usage

1. Connect to the ESP32 Hotspot.
2. Access the web interface at http://192.168.4.1.
3. Log in and configure the system.
4. Enter Wi-Fi credentials.
5. Add users' email to assign lockers.

Smart Link Integration

1. Download the Smart Link mobile app.
2. Sign in with a Google account.
3. Admins must add the same Google account email to the ESP32 for authorization.

6. Admin Panel Web Interface Previews

7. Libraries

• LittleFS
• Firebase_ESP_Client
• ESPAsyncWebServer
• UUID
• arduino-littlefs-upload
• CustomJWT