LeapConnect

Web dashboard for monitoring and controlling Leapmotor vehicles via the leapmotor-api Python client.

What is LeapConnect?

LeapConnect is a self-hosted web application that gives you a complete, private dashboard for your Leapmotor vehicle — everything the official app does, plus a lot more, all running on your own server.

Leapmotor cars expose their data and remote commands through a cloud API. LeapConnect connects to that cloud on your behalf, then presents it in a clean, fast interface you can open from any browser on your network — phone, tablet, or desktop. Because it runs on your own machine, your vehicle data stays with you instead of being scattered across third-party services.

What you get out of the box:

• A live cockpit for your car — battery, range, location, climate, doors, tires, and more, refreshed automatically in real time.
• Full remote control — over 50 commands (lock, climate, charging, windows, sunroof, find car…), each respecting your account permissions and your car's actual hardware.
• Your own history — every reading is optionally saved to a local database, so you can chart battery health, charging sessions, efficiency, and driving trends over weeks and months.
• Dedicated tools for the things that matter most: a Charging hub with real cost tracking, a Trips log with maps and comparisons, and a Maintenance tracker that reminds you before a service is due.
• It talks to your other tools — push everything into Home Assistant via MQTT, send live telemetry to A Better Route Planner, or control and monitor your car straight from a Telegram bot.
• Stay informed — a configurable notification system alerts you about charging, security, geofencing, and maintenance events.

LeapConnect is an independent, community-driven project (see the disclaimer) — not affiliated with Leapmotor.

Features

• Live vehicle status: Battery, range, speed, odometer, temperature, lock status and more — with configurable auto-refresh via WebSocket
• 51 remote commands: Lock/unlock, trunk, windows, sunroof, sunshade, climate (A/C, quick cool/heat, defrost), battery preheat, start/stop charging, charge schedule, climate schedule, seat heating & ventilation, steering wheel heat, sentry mode, speed limit, send destination, media playback, firmware OTA, find car, and more
• Charge management: Adjustable charge limit slider, charge schedule programming (days, times, SOC target), healthy charging toggle, start/stop charging, unlock charger
• Charging tab: Dedicated hub with automatic session detection, cost & energy KPIs, per-session and daily charts, time-of-use band distribution, monthly summary, and an editable session list
• Multi-tier charging costs: Configurable price tiers for home grid, home solar, public AC, and public DC — flat rate or time-of-use bands (e.g. Italian ARERA F1/F2/F3) — with automatic AC/DC tier detection on each charge
• Trips tab: Driving log grouped by day with distance, energy, and regen; trip detail with GPS route map, speed chart, and per-trip stats; monthly totals
• Trip comparison: Compare any two trips side-by-side, or auto-discover similar trips by route, time of day, and distance with ranked efficiency insights
• Maintenance & health: Model-aware service schedules (T03, B10, C10 BEV/REEV), service logging, overdue/upcoming tracking, importable community maintenance packs, and proactive reminders
• Climate scheduling: Create, edit, and delete scheduled climate pre-conditioning timers
• Vehicle details: Battery & charging info, doors, windows, tire pressure, climate, seat comfort, security, connectivity, charge plan, and vehicle info
• Location: OpenStreetMap embedded view with coordinates and send-to-car destination picker
• History & analytics: Interactive charts for SOC, range, speed, efficiency, charging sessions, energy consumption, vampire drain, tire pressure, usage heatmap, trip map with GPS traces, an events timeline, and CSV export
• Notifications: Event-driven alerts (charging, driving, security, geofencing, maintenance) with configurable thresholds, per-event toggles, and dynamic vehicle images
• Telegram bot: Full interactive bot to query and control the car — 20+ commands, per-command PIN auth, permission-aware menu, location tracking, and multi-user access with an approval workflow
• Cloud statistics: Weekly energy consumption ranking and distribution from Leapmotor cloud
• Vehicle messages: Notifications from Leapmotor with unread count and pagination
• Car picture: Dynamic image reflecting lock status, doors, windows, sunshade, and lights
• Permission gating: Controls filtered by vehicle hardware abilities and user account permissions
• Multi-vehicle: Tab switching for accounts with multiple vehicles
• Home Assistant integration: Optional MQTT export of all vehicle data (sensors, controls, and cloud statistics) for smart home automation
• ABRP integration: Optional live telemetry to A Better Route Planner for real-time route planning
• Local history recording: Optional SQLite database to track and visualize vehicle data over time
• Dark & light theme: Switchable UI theme
• Live log viewer: Real-time application logs in the browser for troubleshooting
• Guided setup wizard: Step-by-step first-run configuration for certificates, account, and services

Screenshots

Dashboard	Charging	Trips	Trip Comparison	Maintenance

Maintenance Library	History (Local)	History (Cloud)	Details	Energy & Charging Costs

Tested Vehicles

Model	Status
T03	✅ Tested
C10	🟡 Should work (same cloud API)
B10	🟡 Should work (same cloud API)
B05	🟡 Should work (same cloud API)

Requirements

• Docker & Docker Compose (for production)
• uv (for local development)
• Leapmotor app certificate files (.pem) — download here or use the built-in Download from GitHub button in the Certificate Setup screen / Settings → Account → Certificates
• A valid Leapmotor account

⚠️ Strongly recommended: Create a separate Leapmotor account and share your vehicle with it, rather than using your primary account. This way, if anything goes wrong (e.g. account suspension), your main account remains unaffected.

Quick Start (Docker)

Using the pre-built image

docker pull ghcr.io/markoceri/leapconnect:latest

Create a docker-compose.yml:

services:
  generate-certs:
    image: alpine:latest
    entrypoint: /bin/sh
    command:
      - -c
      - |
        if [ -f /certs/traefik.crt ] && [ -f /certs/traefik.key ]; then
          echo "Certificates already exist, skipping."
          exit 0
        fi
        apk add --no-cache openssl
        SAN="DNS:localhost,IP:127.0.0.1"
        for ip in $$(hostname -I 2>/dev/null); do SAN="$$SAN,IP:$$ip"; done
        openssl req -x509 -nodes -days 3650 \
          -newkey rsa:2048 \
          -keyout /certs/traefik.key \
          -out /certs/traefik.crt \
          -subj "/CN=leapconnect" \
          -addext "subjectAltName=$$SAN"
    volumes:
      - ./traefik/certs:/certs
    network_mode: host

  traefik:
    image: traefik:latest
    depends_on:
      generate-certs:
        condition: service_completed_successfully
    command:
      - "--providers.docker=true"
      - "--providers.docker.exposedbydefault=false"
      - "--entrypoints.web.address=:80"
      - "--entrypoints.websecure.address=:443"
      - "--entrypoints.web.http.redirections.entrypoint.to=websecure"
      - "--entrypoints.web.http.redirections.entrypoint.scheme=https"
      - "--providers.file.filename=/etc/traefik/dynamic.yml"
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - ./traefik/dynamic.yml:/etc/traefik/dynamic.yml:ro
      - ./traefik/certs:/certs:ro
    restart: unless-stopped

  app:
    image: ghcr.io/markoceri/leapconnect:latest
    environment:
      - DB_PATH=/app/data/leapconnect.db
      - DATA_DIR=/app/data
    volumes:
      - ./data:/app/data
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.leapmotor.rule=PathPrefix(`/`)"
      - "traefik.http.routers.leapmotor.entrypoints=websecure"
      - "traefik.http.routers.leapmotor.tls=true"
      - "traefik.http.services.leapmotor.loadbalancer.server.port=8099"
    restart: unless-stopped

docker compose up -d

The app will be available at https://localhost.

Building from source

git clone https://github.com/markoceri/leapconnect
cd leapconnect
docker compose up -d --build

The app is available at https://localhost.

Traefik handles reverse proxying with HTTPS on port 443 and automatic HTTP→HTTPS redirect on port 80. The app container runs internally on port 8099.

Vehicle history data is persisted in a Docker volume (app-data).

HTTPS & Certificates

The Docker Compose setup includes automatic TLS certificate generation. On first docker compose up, a one-shot init container generates a self-signed certificate with all local IP addresses in the SAN (Subject Alternative Name), so you can access the app via https://<server-ip> without certificate errors.

• Certificates are stored in traefik/certs/ (git-ignored)
• If certificates already exist, the init container skips generation
• To regenerate (e.g. after an IP change), delete the old certificates and restart:

rm traefik/certs/traefik.crt traefik/certs/traefik.key
docker compose up -d

Alternatively, you can use the standalone script to regenerate certificates with custom IPs or hostnames:

rm traefik/certs/traefik.crt traefik/certs/traefik.key
./generate-traefik-certs.sh                     # auto-detect local IPs
./generate-traefik-certs.sh 192.168.1.100       # add extra IP
./generate-traefik-certs.sh myhost.local        # add extra hostname

Leapmotor API Certificates

The Leapmotor cloud API requires mTLS client certificates (app.crt + app.key), stored in data/certs/. You can obtain them in two ways:

1. Automatic download (recommended): Use the Download from GitHub button available in:

   • The initial Certificate Setup wizard (first run)
   • Settings → Account → Certificates

   This fetches the latest certificates from the leapmotor-certs repository automatically.

2. Manual upload: Download the .pem files manually from the latest release and upload them via the Certificate Setup screen.

Contributing

Interested in contributing? Read the contributing guide for development setup, testing, and PR guidelines.

Environment Variables

Variable	Required	Description
APP_CERT_PATH	Yes	Path to the app certificate PEM file
APP_KEY_PATH	Yes	Path to the app key PEM file
ACCOUNT_P12_PASSWORD	No	P12 password (usually auto-derived from login)
DB_PATH	No	SQLite database path (default: /app/data/leapconnect.db)

Login

You will need:

• Email & Password: Your Leapmotor account credentials
• Vehicle PIN (optional): Required for remote control actions (lock, unlock, climate, etc.)

Password Reset

If you are locked out of your LeapConnect local account (the app login password, not your Leapmotor cloud credentials), you can reset it from the command line:

# Direct
python -m leapconnect --reset-password "new_password"

# Docker
docker compose exec app uv run python -m leapconnect --reset-password "new_password"

Note: Quote the password to prevent shell interpretation of special characters ($, &, !, etc.).

This does not affect your Leapmotor cloud account password — only the local LeapConnect application login.

Disclaimer

This is NOT an official Leapmotor product.

LeapConnect is an independent, community-driven project with no affiliation to Leapmotor International or its subsidiaries. It interacts with Leapmotor's cloud services through unofficial, reverse-engineered APIs.

By using this software you acknowledge that:

• You use LeapConnect entirely at your own risk.
• The author(s) accept no responsibility for any consequences, including but not limited to account suspension or ban by Leapmotor.
• Vehicle commands are sent over unofficial channels — use remote controls with caution.
• The project may stop working at any time if Leapmotor changes its APIs.