Skip to content
BranchesTags

Repository files navigation

PetTracer Home Assistant Integration

Test

⚠️ DISCLAIMER: This project is not affiliated with, endorsed by, or in any way officially connected with PetTracer.com or its parent company. This is an independent, unofficial integration created by the community. PetTracer® is a trademark of its respective owner.

A custom Home Assistant integration for PetTracer GPS pet collars. Track your pets' locations directly in Home Assistant!

This integration uses the petTracer-API client library to connect to the PetTracer service.

Features

  • 📍 Device Tracking: Each collar appears as a trackable device in Home Assistant
  • 🗺️ GPS Coordinates: Real-time latitude/longitude coordinates for all your pet collars
  • 🔋 Battery Monitoring: See battery level and voltage for each collar
  • 📡 Signal Quality: View satellite count and signal strength information
  • 🏠 Home Detection: Track whether your pet is at home
  • 📊 Individual Sensors: Each attribute is exposed as a separate sensor entity with appropriate device classes
  • 🔄 Automatic Updates: Location updates every 60 seconds

Requirements

  • Home Assistant 2023.1 or newer
  • A PetTracer GPS collar with active subscription
  • Valid PetTracer account credentials

Installation

HACS (Recommended)

This integration can be installed via HACS as a custom repository.

  1. Add and install this repository in HACS:
    • Open HACS in Home Assistant
    • Click on "Integrations"
    • Click the three dots (⋮) in the top right corner
    • Select "Custom repositories"
    • In the "Repository" field, enter: https://github.com/kylegordon/pettracer-ha
    • In the "Category" dropdown, select "Integration"
    • Click "Add"
    • Find "PetTracer GPS Tracker" in your integrations list
    • Click on the integration
    • Click "Download"
    • Restart Home Assistant

Manual Installation

  1. Copy the custom_components/pettracer directory to your Home Assistant configuration directory:

    cd /path/to/homeassistant/config
mkdir -p custom_components
cp -r /path/to/pettracer-ha/custom_components/pettracer custom_components/

    The final path should be: custom_components/pettracer/

  2. Restart Home Assistant

Configuration

Using the UI (Recommended)

  1. Go to Settings → Devices & Services
  2. Click + Add Integration
  3. Search for "PetTracer"
  4. Enter your PetTracer username and password
  5. Click Submit

Your pet collars will appear as device trackers in Home Assistant.

Using configuration.yaml (Legacy)

This integration supports config flow only. Configuration via configuration.yaml is not supported.

Usage

Device Trackers

Each collar appears as a device tracker entity with the pet's name:

  • Entity ID format: device_tracker.pet_name
  • Shows current GPS location on the map
  • Updates automatically every 60 seconds

Sensors

Each collar provides the following individual sensor entities:

Battery Sensors

  • Battery Level (sensor.pet_name_battery_level)

    • Device class: Battery
    • Unit: %
    • Calculated from battery voltage (3.0V-4.2V range)

  • Battery Voltage (sensor.pet_name_battery_voltage)

    • Device class: Voltage
    • Unit: mV
    • Raw battery voltage reading

Location Sensors

  • Latitude (sensor.pet_name_latitude)

    • GPS latitude coordinate

  • Longitude (sensor.pet_name_longitude)

    • GPS longitude coordinate

  • GPS Accuracy (sensor.pet_name_gps_accuracy)

    • Device class: Distance
    • Unit: m
    • GPS position accuracy in meters

Communication Sensors

  • Last Contact (sensor.pet_name_last_contact)

    • Device class: Timestamp
    • Last time the collar contacted the server

  • Position Time (sensor.pet_name_position_time)

    • Device class: Timestamp
    • Timestamp when GPS position was measured

Signal Sensors

  • Satellites (sensor.pet_name_satellites)

    • Number of GPS satellites in use

  • Signal Strength (sensor.pet_name_signal_strength)

    • Device class: Signal strength
    • Unit: dBm
    • Cellular signal strength (RSSI)

Status Sensors

  • Status (sensor.pet_name_status)

    • Device status code

  • Mode (sensor.pet_name_mode)

    • Device operating mode (update frequency setting)
    • State values (mode names):
      • Fast: Frequent updates (mode number: 1)
      • Normal: Standard updates (mode number: 2)
      • Slow: Infrequent updates (mode number: 3)
      • Slow+: Very infrequent updates (mode number: 7)
      • Fast+: Very frequent updates (mode number: 8)
      • Live: Real-time updates (mode number: 11)
      • Normal+: Enhanced standard updates (mode number: 14)
      • Unrecognized: Unknown mode (when device returns unexpected value)
    • Includes mode_number attribute with the numeric mode value

  • At Home (sensor.pet_name_at_home)

    • Text sensor indicating if pet is at home ("true" or "false")

Example Automations

Alert when pet leaves home:

automation:
  - alias: "Pet Left Home"
    trigger:
      - platform: state
        entity_id: sensor.your_pet_name_at_home
        to: "false"
    action:
      - service: notify.mobile_app
        data:
          title: "Pet Alert"
          message: "Your pet has left home!"

Low battery warning:

automation:
  - alias: "Pet Collar Low Battery"
    trigger:
      - platform: numeric_state
        entity_id: sensor.your_pet_name_battery_level
        below: 20
    action:
      - service: notify.mobile_app
        data:
          title: "Battery Warning"
          message: "Pet collar battery is low ({{ states('sensor.your_pet_name_battery_level') }}%)"

Notify when GPS accuracy is poor:

automation:
  - alias: "Pet Collar Poor GPS"
    trigger:
      - platform: numeric_state
        entity_id: sensor.your_pet_name_gps_accuracy
        above: 50
    action:
      - service: notify.mobile_app
        data:
          title: "GPS Warning"
          message: "Pet collar has poor GPS accuracy ({{ states('sensor.your_pet_name_gps_accuracy') }}m)"

Notify when collar switches to Live mode:

automation:
  - alias: "Pet Collar Live Mode"
    trigger:
      - platform: state
        entity_id: sensor.your_pet_name_mode
        to: "Live"
    action:
      - service: notify.mobile_app
        data:
          title: "Mode Change"
          message: "Pet collar switched to Live mode (mode number: {{ state_attr('sensor.your_pet_name_mode', 'mode_number') }})"

Troubleshooting

Authentication Errors

If you receive authentication errors:

  • Verify your username and password are correct
  • Check that your PetTracer subscription is active
  • Try logging into the PetTracer website/app to confirm credentials

No Location Data

If location data isn't showing:

  • Ensure the collar has GPS signal (check satellite count)
  • Verify the collar is powered on and charged
  • Check the collar's last contact time - it may be out of range

Integration Not Loading

If the integration fails to load:

  • Check Home Assistant logs for errors
  • Ensure the pettracer-client library is installed (should be automatic)
  • Restart Home Assistant after installation

Releasing

Releases are fully automated — no manual steps required beyond merging PRs.

How it works

  1. Merge any PR to master — no special title format needed.
  2. The Release workflow automatically:
    • Bumps the patch version (e.g. 1.0.5 → 1.0.6)
    • Generates release notes listing every PR merged since the last release
    • Creates or updates a release/next pull request
  3. Review and merge the release PR when you're ready to publish.
  4. Merging the release PR triggers the workflow again to:
    • Create a git tag (e.g. v1.0.6)
    • Publish a GitHub Release with auto-generated notes
    • Attach a HACS-installable ZIP package to the release

Notes

  • The release PR is updated automatically each time a new PR lands on master, so you can let several changes accumulate before publishing.
  • The release PR title always starts with chore: release v… — merging it is the trigger for publishing.
  • No conventional commit format is required on PR titles; all merged PRs are included in the release notes regardless of wording.

Development

This integration is built using:

Local Development

All development is done inside Docker to avoid polluting your host with dependencies.

Build the dev image (once, and after requirements-test.txt changes):

docker build -f Dockerfile.dev -t pettracer-dev .

Run the full test suite:

docker run --rm -v "$PWD":/workspace pettracer-dev \
  pytest --cov=custom_components.pettracer --cov-report=term -v

Run a single test file:

docker run --rm -v "$PWD":/workspace pettracer-dev pytest tests/test_sensor.py -v

Lint / format:

docker run --rm -v "$PWD":/workspace pettracer-dev ruff check custom_components/pettracer/
docker run --rm -v "$PWD":/workspace pettracer-dev ruff format custom_components/pettracer/

Interactive shell:

docker run --rm -it -v "$PWD":/workspace pettracer-dev bash

The source tree is bind-mounted at /workspace, so code changes take effect immediately without rebuilding the image.

File Structure

custom_components/pettracer/
├── __init__.py          # Integration setup and coordinator
├── config_flow.py       # UI configuration flow
├── const.py            # Constants
├── device_tracker.py   # Device tracker platform
├── manifest.json       # Integration metadata
├── strings.json        # UI strings
└── translations/
    └── en.json         # English translations

Support

For issues related to:

License

MIT License

Disclaimer

This is an unofficial integration. PetTracer® is a trademark of its respective owner. Use this integration at your own risk and respect the PetTracer service terms of use.

About

No description, website, or topics provided.

Resources

Readme

Contributing

Contributing
Activity

Stars

0 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages