Add enphase solar monitor

[ammyyou112]

What does this Ability do?

Voice-activated solar monitoring for Enphase IQ Gateway systems. Users can check real-time solar production, battery status, consumption, and grid import/export with natural voice commands.

Suggested Trigger Words

• "solar"
• "how's my solar"
• "solar status"
• "solar production"
• "battery level"
• "battery status"
• "am I exporting"
• "grid status"
• "solar today"
• "enphase"
• "solar panels"

Type

• New community Ability
• Improvement to existing Ability
• Bug fix
• Documentation update

External APIs

• No external APIs
• Uses external API(s):
  • Enphase Cloud API v4 (requires OAuth 2.0 authentication)
  • Endpoints: /systems/{system_id}/summary, /systems/{system_id}/encharge, /systems/{system_id}/consumption_stats
  • Requires: System ID, API key, OAuth client ID/secret, access/refresh tokens

Testing

• Tested in OpenHome Live Editor
• All exit paths tested (said "stop", "exit", etc.)
• Error scenarios tested (API down, bad input, etc.)

Checklist

• Files are in community/enphase-solar-monitor/
• main.py follows SDK pattern (extends MatchingCapability, has register_capability + call)
• README.md included with description, suggested triggers, and setup
• resume_normal_flow() called on every exit path
• No print() — using editor_logging_handler
• No hardcoded API keys — using placeholders
• No blocked imports (redis, connection_manager, user_config)
• No asyncio.sleep() or asyncio.create_task() — using session_tasks
• Error handling on all external calls
• Tested in OpenHome Live Editor

Anything else?

Demo Mode Included:
The ability includes a DEMO_MODE = True flag that returns realistic fake data for testing without real Enphase credentials. Perfect for trying out the conversation flow before connecting a real system.

Features:

• 15-minute data caching to minimize API calls
• OAuth token auto-refresh
• Multi-intent classification (production, battery, consumption, grid status)
• Voice-optimized formatting ("kilowatts" not "kW")
• Conversational loop with context awareness

Conversation Example:

User: "enphase"
Assistant: "Sure! Let me check your solar system."
Assistant: "You're producing 4.2 kilowatts right now."
Assistant: "Today you've generated 28.0 kilowatt hours."
Assistant: "Your battery is at 73 percent and charging."
User: "what about consumption?"
Assistant: "You're using 3.1 kilowatts right now."
User: "stop"
Assistant: "Okay, talk to you later!"

Loom Demo: https://www.loom.com/share/0ae21d6369eb4310bc96446dd5f5923c

---

## 📋 **Files to Include in PR:**

community/enphase-solar-monitor/
├── main.py
└── README.md

[github-actions]

🔀 Branch Merge Check

PR direction: add-enphase-solar-monitor → dev

✅ Passed — add-enphase-solar-monitor → dev is a valid merge direction

[github-actions]

✅ Community PR Path Check — Passed

All changed files are inside the community/ folder. Looks good!

[github-actions]

✅ Ability Validation Passed

📋 Validating: community/enphase-solar-monitor
  ✅ All checks passed!

[github-actions]

🔍 Lint Results

✅ __init__.py — Empty as expected

Files linted: community/enphase-solar-monitor/main.py

✅ Flake8 — Passed

✅ All checks passed!

[uzair401]

Hello @ammyyou112,

Thank you for your submission and the effort you’ve put into these abilities. Since they involve hardware interactions, we will need to test them with real hardware to fully verify their functionality. To keep the workflow clean, we are closing the PRs for now so they don’t remain stale. Once the hardware testing and verification are complete, we will reopen the PRs and proceed with merging them.

We truly appreciate your contributions and encourage you to continue submitting new abilities, as your work helps strengthen the ecosystem.