Team Details

Team Number:

24AACR07

Senior Mentor:

Manav Patel

Junior Mentor:

Sujay Anishetti

Team Member 1:

H Satvika

Team Member 2:

G Krishna Sarayu

Team Member 3:

E Dheeraj Chandra

Team Member 4:

G Dwarak

Table of Contents

• Abstract
  
• Requirements
  
• How to use
  
• Preview
  
• Contribution

Abstract

Secure Nest is an automated security solution for residential complexes, enhancing safety and streamlining access control. It uses object detection, license plate recognition, and face recognition to ensure secure entry. For vehicles, cameras scan license plates to match registered residents, granting access upon a match. For pedestrians, face recognition verifies identities against stored profiles. The system features a dual-portal visitor management setup, allowing residents to preauthorize entry by generating a one-time password sent to the visitor’s mobile. This password, combined with the flat number, enables access.

Requirements

Python
opencv-python 4.8.0
face-recognition 1.3.0
numpy 1.24.4
paddleocr 2.6.1.3
firebase-admin 6.1.0

Installation and usage

• Clone the repository using

  git clone https://github.com/AAC-Open-Source-Pool/Secure-nest
  

• Install all the dependencies using

  pip install -r requirements.txt
  

• Run encoder.py to add your face into the encoded folder
• Now Run main_file.py to see whether it opens up the gate
• now open the websites Authorisation_website to allow outside access while otp check is used to verify it

Preview

Screenshots of the project

Contribution

This section provides instructions and details on how to submit a contribution via a pull request. It is important to follow these guidelines to make sure your pull request is accepted.

1. Before choosing to propose changes to this project, it is advisable to go through the readme.md file of the project to get the philosophy and the motive that went behind this project. The pull request should align with the philosophy and the motive of the original poster of this project.
2. To add your changes, make sure that the programming language in which you are proposing the changes should be the same as the programming language that has been used in the project. The versions of the programming language and the libraries(if any) used should also match with the original code.
3. Write a documentation on the changes that you are proposing. The documentation should include the problems you have noticed in the code(if any), the changes you would like to propose, the reason for these changes, and sample test cases. Remember that the topics in the documentation are strictly not limited to the topics aforementioned, but are just an inclusion.
4. Submit a pull request via Git etiquettes