Built to order

IoT Pet Collar with Geofence and Activity Tracking

Pets slip out of gates and go missing every day, and owners discover it hours later when someone notices the empty yard. Commercial GPS pet trackers exist but charge subscriptions and hide their workings. Suitable for B.E./B.Tech final-year projects in IoT & Embedded Systems and Electronics.

IoT Pet Collar with Geofence and Activity Tracking — project thumbnail preview
More project photos (2)

The problem

Pets slip out of gates and go missing every day, and owners discover it hours later when someone notices the empty yard. Commercial GPS pet trackers exist but charge subscriptions and hide their workings. This project builds an open pet collar on an ESP32: a NEO-6M GPS module for position, an MPU6050 IMU that classifies rest versus activity, and firmware that defines a home geofence — crossing it raises an immediate alert on the owner's phone dashboard, which also shows the track history and a daily activity summary. The collar is a genuine wearable design problem: weight, battery life and a pet-safe enclosure all constrain the build, and the report documents those trade-offs honestly. GPS accuracy is the NEO-6M's rated outdoor performance, stated as a datasheet value, not a measured claim.

How it works

  1. The GPS, IMU and ESP32 are assembled in the lightweight enclosure and fitted to a standard collar strap.
  2. The owner sets the home coordinates and geofence radius in the firmware configuration.
  3. On power-up the collar acquires a GPS fix (outdoors) and starts publishing position and activity over Wi-Fi.
  4. The IMU continuously classifies rest versus movement; the firmware accumulates active minutes.
  5. Crossing the geofence boundary triggers an immediate alert on the dashboard; the track history records the excursion.
  6. The dashboard renders the live position, track history and daily activity summary for the owner.

Tech stack:

  • ESP32 development board (Wi-Fi)
  • NEO-6M GPS module
  • MPU6050 IMU
  • Li-ion battery + charging module
  • 3D-printed pet-safe enclosure
  • Blynk / ThingSpeak class dashboard
  • Status LED
  • Arduino IDE (C/C++ firmware)
Parameter Value
GPS NEO-6M, approximately ±2.5 m accuracy outdoors (datasheet)
IMU MPU6050 6-axis, rest/activity classification
Geofence Configurable radius around home coordinates
Battery Li-ion; life depends on fix rate (design target: a full day)
Weight budget Enclosure + electronics target under ~80 g (design)
Connectivity Wi-Fi 2.4 GHz; tracking works within home-network range
Enclosure 3D-printed, rounded, collar-strap mount
Alerts Geofence breach + low battery on dashboard

Project features

  • [GPS geofence alerts] A configurable home radius around the house; the collar raises an immediate dashboard alert when the pet crosses the boundary.
  • [Live location tracking] GPS fixes are published over Wi-Fi to the dashboard with a track history of where the pet has been.
  • [IMU activity classification] An MPU6050 distinguishes rest from movement, building a daily activity summary (active minutes vs rest).
  • [Daily activity summary] The dashboard aggregates active time per day so owners can spot lethargy trends worth a vet visit.
  • [Low-battery alert] Battery voltage is monitored and a low-battery alert is raised before the collar goes dark.
  • [Pet-safe wearable enclosure] A lightweight 3D-printed enclosure with rounded edges and a standard collar strap mount, documented with a weight budget.
  • [On-collar status LED] A small LED signals GPS fix and alert states without needing the phone.

What is included

  • ESP32 collar electronics with GPS and IMU in a pet-safe enclosure
  • Collar strap mount and weight-budget documentation
  • ESP32 firmware (GPS, geofence logic, activity classification, dashboard)
  • Enclosure 3D-print files and assembly guide
  • Project report PDF, PPT presentation and viva Q&A document

Limitations & prerequisites

  • GPS needs open sky — indoors or under dense cover, fixes degrade or drop; the dashboard shows last-known position honestly.
  • Tracking range is limited to Wi-Fi coverage; this is a home-and-neighbourhood tracker, not a cellular one (cellular variant is future scope).
  • ±2.5 m GPS accuracy is the module's datasheet rating outdoors, not a measured claim.
  • Battery life depends on the GPS fix rate; continuous tracking trades against the design target of a full day.
  • Activity classification is rest-vs-active only — not a veterinary diagnostic.

Frequently Asked Questions

How does the geofence alert work?

The owner configures home coordinates and a radius. The collar checks each GPS fix against the boundary and publishes an immediate alert to the dashboard when the pet crosses it.

How accurate is the location?

The NEO-6M is rated at approximately ±2.5 m outdoors (datasheet). Indoors or under dense tree cover, accuracy degrades and the dashboard shows the last-known fix.

What is the tracking range?

Wi-Fi range — this is a home-and-neighbourhood tracker with no subscription. A cellular (4G) variant for unlimited range is listed as future scope.

How does it track activity?

The MPU6050 IMU classifies rest versus movement; the firmware accumulates active minutes and the dashboard shows a daily summary, useful for spotting lethargy trends.

Is the collar safe and comfortable?

The enclosure is 3D-printed with rounded edges, mounts on a standard collar strap, and the design targets under ~80 g total. The weight budget is documented in the report.

Is this project suitable for a final-year project?

Yes — for IoT & Embedded and Electronics programs. It combines GPS, IMU sensing, geofence logic, wearable power budgeting and a mobile dashboard. Suitable for B.E./B.Tech final-year projects in IoT & Embedded Systems and Electronics.

Components & software requirements
  • ESP32 development board (Wi-Fi)
  • NEO-6M GPS module
  • MPU6050 IMU
  • Li-ion battery + charging module
  • 3D-printed pet-safe enclosure
  • Blynk / ThingSpeak class dashboard
  • Status LED
  • Arduino IDE (C/C++ firmware)
Delivery information

Built-to-order project. Delivery timeline is shared after order confirmation based on current queue.

Support terms

Complete documentation, setup guide, and viva preparation included. Support for setup and explanation provided.

Download abstract (PDF)

Related guides

All guides
Technical illustration of three electronic control units linked by a twisted-pair CAN bus cable carrying signal pulses between them.Electronics, E&TC, IoT and robotics students who keep hearing “CAN bus” in EV, automotive and industrial project ideas and want to understand it properly before wiring anything

CAN Bus Basics for Students: How ECUs Communicate

CAN bus is the shared network that lets dozens of controllers in a car, EV or robot communicate over two wires. This guide explains message IDs, arbitration, the physical layer, frame structure, error handling and CAN FD, then walks through building a working two-node bench network with an ESP32 and a transceiver.

Read guide
Illustration of a quadcopter drone build showing labeled parts including frame, motors, propellers, ESCs, flight controller, and battery.B.E./B.Tech Electronics, Mechanical, and Computer Science students planning to build a quadcopter drone who need to select compatible parts without wasting money on mismatched

Drone Build: Parts Selection Guide

Picking drone parts that actually work together is a sizing problem, not a shopping problem. This guide walks the compatibility chain — frame to props to motors to ESCs to battery — with the thrust math, firmware choices, LiPo safety, and the bench-test order that prevents disasters.

Read guide
Illustration comparing three smart-home wireless paths: a Zigbee mesh of devices, a Thread IPv6 mesh with a border router, and the Matter logo layer above them unifying brands.B.E./B.Tech Electronics, E&TC and IoT students choosing a smart-home wireless standard for projects with lights, sensors and switches

Zigbee vs Thread vs Matter Explained

Zigbee, Thread and Matter are not interchangeable. Learn what each one is (mesh standard vs IP networking layer vs interop application layer), how they stack together, which ESP32 variants support 802.15.4, and how to choose the right one for your smart-home project.

Read guide
Get a quotation