Enphase API

Package
CI/CD
Meta
Community

A Rust client library for interacting with Enphase solar systems via the Entrez cloud service and local Envoy gateway.

Note

This library is in early development. Currently, only authentication and basic power control are implemented. Additional API endpoints will be added over time. Contributions are very welcome!

Installation

Add this to your Cargo.toml:

[dependencies]
enphase-api = "1"
tokio = "1"

This library uses async/await and requires an async runtime like tokio.

Quick Start

use enphase_api::{Entrez, Envoy, PowerState};

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    // Step 1: Authenticate with Enphase Entrez and get a JWT token
    let entrez = Entrez::default();
    entrez.login("your-email@example.com", "your-password").await?;
    let token = entrez.generate_token("your-site-name", "your-envoy-serial", true).await?;

    // Step 2: Connect to your local Envoy gateway
    let envoy = Envoy::new("envoy.local");
    envoy.authenticate(&token).await?;

    // Step 3: Control your system (example: set power state)
    envoy.set_power_state("device-serial-number", PowerState::On).await?;

    Ok(())
}

The library supports Enphase's two-step authentication:

1. Entrez Cloud Service: Authenticate with your Enphase account to generate JWT tokens
2. Local Envoy Gateway: Use the JWT token to access your local Envoy device

The client then remembers the authentication state for subsequent API calls. Note that the JWT token has a limited lifespan and re-authentication may be necessary.

Note: All API methods are async and require .await. You'll need an async runtime like tokio to run the examples.

Using Environment Variables

For convenience, you can use environment variables for authentication:

use enphase_api::{Entrez, Envoy};

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    // Set these environment variables:
    // - ENTREZ_USERNAME
    // - ENTREZ_PASSWORD
    let entrez = Entrez::default();
    entrez.login_with_env().await?;

    let token = entrez.generate_token("your-site-name", "your-envoy-serial", true).await?;

    let envoy = Envoy::new("envoy.local"); // or use IP address like "192.168.1.100"
    envoy.authenticate(&token).await?;

    Ok(())
}

Current API Coverage

This library is in early development. Currently implemented:

Entrez Client

• User authentication (login, login_with_env)
• JWT token generation for Envoy devices (generate_token)

Envoy Client

• JWT authentication (authenticate)
• Power state control (set_power_state)

Planned Features

The following features are planned for future releases:

• Production API: Real-time solar production data
• Consumption API: Energy consumption monitoring
• Inverter API: Individual inverter performance data
• System API: Overall system information and status

We welcome contributions! If you need a specific API endpoint, please consider opening an issue or submitting a pull request.

Documentation

• API Documentation
• Enphase Website
• Enphase Developer Portal

Contributing

We welcome contributions! This library is in active development and there are many API endpoints still to implement. Please see our Contributing Guide for details on:

• Setting up the development environment
• Running tests and examples
• Code style and formatting guidelines
• Submitting pull requests

If you'd like to add support for additional API endpoints, please feel free to open an issue or submit a pull request!

Testing

This library includes both unit tests and integration tests:

Unit Tests

Unit tests run without credentials or hardware access using mock servers (wiremock):

cargo nextest run

Unit tests cover:

• Entrez client: login, token generation, environment-based auth
• Envoy client: JWT authentication, power state control
• Models: PowerState and PowerStatusResponse serialization

These tests rely on fixtures stored in the fixtures/ directory, which contain sanitized HTTP request/response pairs. These fixtures can be recreated or updated using the script:

./scripts/generate-fixtures
# Or for a dry run without saving:
./scripts/generate-fixtures --dry-run

Integration Tests

Integration tests require actual Enphase credentials and hardware access:

# Run integration tests (requires environment variables)
cargo test --test integration -- --ignored

Required environment variables for integration tests:

• ENTREZ_USERNAME - Your Enphase account username
• ENTREZ_PASSWORD - Your Enphase account password
• ENVOY_HOST - Your Envoy device hostname/IP
• ENVOY_NAME - Your Envoy site name
• ENVOY_SERIAL_NUMBER - Your Envoy device serial number

License

This project is licensed under the MIT License - see the LICENSE file for details.

Support

• 📚 Documentation
• 🐛 Issue Tracker
• 💬 Discussions