Repository navigation
Ecosystem
Projects built on top of the eero-api SDK, and where this library sits among them.
eero-api is the transport layer and nothing more. Since v2.0.0 it returns the Eero Cloud API's
responses unmodified — every consumer owns its own data extraction, presentation, and storage.
┌──────────────┐ ┌──────────────┐ ┌──────────────────────────┐ ┌────────────────────┐
│ eeroctl │ │ eero-ui │ │ eero-prometheus-exporter │ │ home-assistant-eero│
│ (CLI) │ │ (dashboard) │ │ (metrics) │ │ (integration) │
└──────┬───────┘ └──────┬───────┘ └────────────┬─────────────┘ └─────────┬──────────┘
└─────────────────┴──────────────┬────────┴──────────────────────────┘
│
┌────────▼─────────┐
│ eero-api │ ← this project
│ (raw JSON SDK) │
└────────┬─────────┘
│ HTTPS
┌────────▼─────────┐
│ api-user.e2ro.com│
└──────────────────┘
Note: If you are looking for a finished tool rather than a library, start with eeroctl. Reach for the SDK when you are building something of your own.
| Project | What it is |
|---|---|
| 🖥️ eeroctl | Terminal interface for Eero networks. This is where all CLI commands (eero auth login, eero network list, …) live — they are not part of this SDK. Installable with Homebrew from homebrew-eeroctl
|
| 🛜 eero-ui | Svelte dashboard for network management |
| 📊 eero-prometheus-exporter | Prometheus metrics for monitoring Eero networks |
| 🏠 home-assistant-eero | Home Assistant custom integration (installable through HACS): networks, eeros, profiles and connected devices as entities, plus actions such as pausing a profile, blocking a device, toggling the guest network and installing firmware. Talks to the eero cloud through eero-api since its 2.0.0 |
Port: 🦀 rusteero is an async Rust client for the same cloud API, ported from this library. It is a port, not a consumer — it does not depend on eero-api.
Community projects that depend on eero-api:
| Project | Description |
|---|---|
| eero-dashboard | Self-hosted React + FastAPI dashboard for Eero mesh networks |
| eero-cli | Tiny CLI for non-interactive SMS auth, device listing, and bulk block |
| py-bandwith-monitor | Python bandwidth monitor with an optional Eero-backed data source |
| assorted | Personal Eero router debug and inspection scripts |
| tripwire | Detects new, missing, renamed or regrouped devices against a saved baseline; ships a CLI and an MCP server |
💡 Tip: Building something on top of
eero-api? Open a PR against README.md to get listed.
A few things the existing consumers learned the hard way:
- Own your schema. Responses are raw and the upstream API is undocumented and unversioned in practice. Define your own TypedDicts or models at your application boundary so an upstream field rename breaks in one place.
-
Respect the rate ceiling. Roughly 100 requests/minute across the account. Tune
cache_timeoutrather than adding sleeps — see Caching and Rate Limits. - Do not persist preferences in the SDK. It deliberately stores credentials only. Preference storage moved out to the CLI in v4.0.0; your project should own its own config.
- Pin the version. Major releases have carried real breaking changes — see Migration.
This project is a modern revamp of the original eero-client by @343max, and was previously published under that name.
- Home — Overview and quick start
-
Python API — Full guide to
EeroClient - Raw Response Format — Why consumers own data extraction
- Caching and Rate Limits — Staying under the request ceiling
- Contributing — Development setup for this repository
eero-api — unofficial async Python client for the Eero cloud API. Not affiliated with or endorsed by Eero.
This wiki is generated from wiki/ in the main repository — edit there, not here. · MIT License