Monitor your SunPower solar system locally from Home Assistant with no cloud dependency. Supports all PVS hardware (PVS5 and PVS6), all firmware versions, SunVault battery systems, and individual inverter health tracking. Real-time data direct from your PVS supervisor over your local network.
Recent additions include optional WebSocket live data for new firmware users (BUILD 61840+), a new "PVS Live Data" device with sensors that update in real time, and several bug fixes and reliability improvements.
Some changes shown in this README or the changelog may be in pre-release testing and not yet in the current stable release. Check the Releases page for what is actually available to install, and the CHANGELOG for the full history including unreleased work.
⚠️ Old Firmware Support Sunset Notice: Support for old firmware (dl_cgi, BUILD below 61840 on PVS6 or below 5408 on PVS5) will be removed in an upcoming release. If you are on old firmware, read the section below before updating.
Primary support: new firmware (BUILD 61840+ on PVS6, BUILD 5408+ on PVS5). The integration automatically detects your firmware and selects the correct communication method.
PVS5 Firmware Version Formats: SunPower uses different version formats for PVS5 vs PVS6. The integration automatically parses all formats:
- PVS5 new firmware:
"2025.11, Build 5412"→ extracts BUILD5412 - PVS5 dotted format:
"0.0.25.5412"→ extracts BUILD5412 - PVS6 format:
"2025.10.20.61846"→ extracts BUILD61846
The BUILD number determines which API method is used (not the version string). You can check your firmware at: http://YOUR_PVS_IP/cgi-bin/dl_cgi/supervisor/info
In Home Assistant, go to Settings, Devices and Services, Enhanced SunPower, and open the PV Supervisor device. The firmware version shown there contains your BUILD number. Alternatively check the Enhanced SunPower Diagnostics device.
If your PVS6 shows a BUILD below 61840, or your PVS5 shows a BUILD below 5408, you are on old firmware. Here is what to do now, before old firmware support is removed:
If you installed via HACS:
- Go to HACS, find Enhanced SunPower, and remove it
- Go to the GitHub Releases page and download the last release that supports old firmware (v2026.04.6)
- Extract the
custom_components/sunpowerfolder into your HAcustom_componentsdirectory - Restart Home Assistant
Your sensors, history, and automations will be preserved. You will simply be pinned to that version and will not receive future updates via HACS. The integration will continue working indefinitely on that version.
If you installed manually: You are already protected. Just do not update past v2026.04.6 and you will be fine.
Why is HACS a problem? HACS always installs the latest version. If you leave it installed via HACS, a future HACS update will silently upgrade you to a version that drops old firmware support, and the integration will stop working.
If you are on new firmware and have a SunVault battery system, full battery monitoring and control is supported.
<-- Why not sponsor me, even a few bucks shows you appreciate the work and gives encouragement. You can sponsor me monthly, or just a one time thing. Check out my other HA Automations & Blueprints while you're here.
Enhanced Fork: This is an improved version of @krbaker's original SunPower integration with simplified 24/7 polling, comprehensive PVS protection, individual inverter health monitoring, and authentication support.
⭐ Help Others Find This Integration! If Enhanced SunPower is working well for you, please star this repository to help other SunPower owners discover these improvements!
👀 Watch this repo to get notified of new releases, bug fixes, and discussions. Use the Watch button at the top of the page and select "Releases" at minimum, or "All Activity" if you want to follow discussions too. The more eyes on the integration, the better it gets. User reports, battery behavior observations, firmware findings, and automation ideas from the community have shaped nearly every release. If you have a SunVault or an unusual setup, your reports are especially valuable since not everyone has hardware to test with.
Core Improvements:
- WebSocket Live Data: Real-time sensor updates direct from the PVS WebSocket (new firmware only); sensors update as values change, not on poll schedule
- Battery Control: Control SunVault battery modes and reserve percentage directly from Home Assistant; enable TOU optimization, emergency backup, or automated battery management via HA automations
- Flash Memory Monitoring: Critical alerts for PVS storage & wear usage, configurable notification thresholds
- Simplified Polling: Single consistent polling interval for reliable 24/7 monitoring
- Individual Inverter Health Monitoring: Failure detection and recovery alerts for each panel
- Flexible Alert System: Critical notifications sent directly to your phone as notifications, emails, and HA UI
- Diagnostic Dashboard: 7 sensors tracking integration reliability and performance
- PVS Hardware Protection: Firmware-aware throttling (10s new firmware, 60s old firmware, 20s battery), health checking, and intelligent backoff
Technical Enhancements:
- Multi-Channel Notifications: 6 separate notification streams
- Comprehensive Battery Monitoring: 10 dedicated ESS/battery sensors (SOC, SOH, power, temps, voltages, charge/discharge limits), more data than original or SunStrong forks
- Modular Architecture: Clean, well-commented, maintainable codebase with separated concerns
- Production Reliability: Battle-tested stability with comprehensive error handling and graceful degradation
Can now install anytime - day or night!
- Dynamic entity discovery allows setup even when inverters are offline (nighttime)
- Entities are automatically created when inverters come online at sunrise
- You'll receive a notification when your solar system is fully discovered and monitored
IMPORTANT - New Firmware Users (BUILD 61840+):
New firmware connects directly to your PVS over your home network - no Raspberry Pi bridge or proxy needed. The PVS has built-in WiFi; just connect it to your home network and use that IP:
- WiFi WAN (Recommended): Check your router's DHCP leases for "PVS" or "SunPower" device; reserve the IP so it doesn't change
- LAN port (Alternative): Fixed IP
172.27.153.1, requires VLAN isolation (LAN port runs its own DHCP) - Ethernet WAN (Do not use): We've seen issues using wired WAN port where it works for a bit, then stops. So use Wifi, or isolate the LAN port of the PVS Ethernet connection. (Isolated VLAN off router or managed switch)
- Raspberry Pi bridges/proxies: Not needed and won't work - new firmware uses HTTPS (port 443) which most bridges don't support
Don't have HACS yet? Install HACS first; it's the easiest way to manage custom integrations.
HACS requires integrations to be registered in the home-assistant/brands repository for manual custom repository adds to work. (Well you can manually install, but it's tricky, just use the buttons below) This integration uses the direct install method instead. Also once the integration is installed you will get notified of updates just like any other HACS install.
- Click the install button:
-
This will open a webpage asking you to open a page in Home Assistant, click the Open Link Button.
-
A window should open asking to Add custom repository, click ADD on that window.
-
After a moment it should show you the integration page, with a Download button in the bottom right of screen, click that button to download, and click Download again when the new window opens asking about version.
-
Click the main "Settings" link in Home Assistant Sidebar, there should be a repair listed at the top saying Restart Required, click that and click Submit and then the Finish button. If it's not there, restart anyway!
-
Now to add the integration click link below, or on your main integration page in Home Assistant click Add Integration and look for the Enhanced Sunpower integration, and add it.
Recommended: Set a static DHCP reservation for your PVS IP address in your router settings.
- Prevents the PVS from receiving a new IP address after a DHCP lease renewal
- Ensures the integration continues polling without interruption
- Standard best practice for all IoT devices on your network
- Router configuration is beyond the scope of this guide, but most routers allow reserving IPs by MAC address
- Page 1: Enter PVS IP (WAN or LAN) address and polling interval
- Integration automatically detects firmware BUILD and serial number
- Validates connection and selects optimal communication method
- Page 2: Confirm password (auto-detected and pre-filled for new firmware)
- Old firmware (BUILD < 61840): Password step skipped automatically
- New firmware (BUILD ≥61840): Password pre-filled, just confirm
- Page 3: Configure notifications and advanced settings
- Set flash memory threshold
- Select mobile device for critical alerts
- Configure email notifications
After initial setup, new firmware users can enable real-time WebSocket live data via integration options (Settings > Devices & Services > Enhanced SunPower > Configure).
The Live Data page appears only for new firmware installs:
- Enable WebSocket live data: Subscribes to the PVS WebSocket on port 9002 for 1-second sensor updates
- Power change threshold: Minimum kW change required to write a state update for power sensors (default 0.05 kW). Reduces database writes during stable conditions.
⚠️ SD Card Warning: Real-time updates generate significantly more database writes than standard polling. If Home Assistant runs on an SD card, leave live data disabled or the card will wear out quickly. SSD storage is strongly recommended.
These sensors are designed for real-time dashboard display, not historical tracking. Since they serve no statistics purpose, even SSD users may want to exclude them from the recorder to keep the database smaller. SD card users who want to use live data should treat this exclusion as required. See TROUBLESHOOTING.md for ready-to-use recorder.exclude configuration for both solar-only and battery systems.
Missing sensors after setup? If you don't see consumption or grid import/export sensors, your installer may not have installed or provisioned the CT clamps in your electrical panel. See TROUBLESHOOTING.md for diagnosis steps and workarounds.
| Setting | Description | Default | Recommended |
|---|---|---|---|
| Host | PVS IP Address | N/A | WAN: 192.168.1.x LAN: 172.27.153.1 |
| Polling Interval | Update frequency (seconds) | 300 | 10-3600 seconds (firmware-aware: 10s new, 60s old, 20s battery) |
| PVS Password (last 5) | Auto-detected from serial number | Auto-filled | Confirm auto-detected value (new firmware only) |
| Flash Memory Threshold | PVS storage alert level (MB) | 0 (disabled) | 30-50 MB for early warning |
| Flash Wear Threshold | PVS flash lifetime alert (%) | 90 (90% wear) | 0 to disable, 85-95% recommended |
| Email Notification Service | Email service for critical alerts | Disabled | Select email service to enable |
| Email Recipient | Override recipient address | `` | Enter send to Email address |
| General Notifications | Show status updates | true |
Enable for monitoring |
| Debug Notifications | Show diagnostic info | false |
Enable for troubleshooting |
| Replace Status Notifications | Reuse notifications | false |
Enable to reduce clutter |
| Mobile Device | Device for critical alerts | Disabled | Select your phone |
| Enable WebSocket Live Data | Real-time 1-second updates (new firmware only) | false |
Enable only with SSD storage |
| Power Change Threshold | Min kW change to trigger state write | 0.05 kW |
Lower = more precision, more DB writes |
✨ Fully Automated: No manual serial number entry required!
How Auto-Detection Works:
- Integration queries PVS for firmware BUILD number and full serial number
- Automatically extracts last 5 characters for authentication password
- Pre-fills password field in UPPERCASE format (matches serial format)
- For old firmware (BUILD < 61840): Skips password step entirely
- For new firmware (BUILD ≥61840): Shows pre-filled password for confirmation
Firmware-Specific Behavior:
- BUILD < 61840: No authentication required, password step skipped automatically
- BUILD ≥61840: LocalAPI authentication with auto-detected password
- Buggy Firmware: Automatic fallback to legacy mode if LocalAPI fails
- Failed Detection: Manual password entry available as fallback
Manual Override (if needed): If auto-detection fails, you can manually enter the last 5 characters of your PVS serial:
- Physical Device: Remove PVS cover, serial on device label
- SunPower/SunStrong App: Profile → System Info → Serial Number
- Format: UPPERCASE letters/numbers only (e.g., "W3193" not "w3193")
Authentication Details:
- Username:
ssm_owner(configured by SunStrong Management) - Password: Last 5 characters of your PVS serial number
- Coverage: Applied to both main device polling and battery system endpoints
- Error Handling: Clear messages when authentication fails or serial number needed
Simplified Architecture: Single consistent polling interval for reliable 24/7 monitoring:
Use Cases:
- Continuous monitoring: Track both solar production and consumption throughout the day
- PVS hardware protection: 300-second minimum protects against overloading
- Battery support: Automatic detection and monitoring of SunVault systems
- Home automation: Reliable data for automations and energy tracking
Configuration:
- Standard setup: 300 seconds (5 minutes), recommended default balancing data freshness with hardware protection
- Faster updates (new firmware): 10-60 seconds for frequent data updates
- Conservative setup: 600-3600 seconds for minimal PVS load
- Battery systems: 20-second minimum (per SunStrong guidance for less aggressive polling)
- Old firmware: 60-second minimum enforced automatically for hardware protection
SunStrong Recommendations:
- Battery systems: Use less aggressive polling intervals to reduce system load
- Non-battery systems: 10-second minimum supported for future varserver compatibility
- Current default: 300 seconds maintained for proven stability
Benefits:
- Consistent behavior: no complex day/night mode switching
- Simpler troubleshooting: predictable polling schedule
- Better battery support: continuous monitoring with appropriate intervals
- Hardware protection: built-in minimums prevent system overload
- Future-ready: prepared for varserver's faster capabilities
Performance Considerations:
- Faster polling (10-60s): Significantly increases Home Assistant database size; 10s polling creates 30x more data than 300s polling
- Database growth: With ~50 solar entities, 10s polling generates ~180,000 database entries per hour vs 600 entries with 300s polling
- Hardware impact: Larger databases slow performance on Raspberry Pi systems, affect backup times, and increase storage requirements
- Standard polling (300s): Recommended default balances data freshness with manageable database size
- Conservative polling (600-3600s): Minimal database growth, ideal for basic monitoring and slower hardware
- System load, uptime, memory usage, firmware version
- Communication errors and scan statistics
- Flash storage availability with critical alerts
- Diagnostics and health monitoring
- Inverters: Power output, individual MPPT data, temperature monitoring
- Power Meters: Energy consumption/production, voltage, frequency
- Virtual Meter: Aggregated inverter data when no physical meter present
- Individual Batteries: State of charge, voltage, current, temperature
- ESS System: Environmental conditions, power meters
- Hub Plus: Grid status, phase voltages, humidity monitoring
When enabled, a separate "PVS Live Data {serial}" device provides real-time sensors updated as values change from the PVS WebSocket on port 9002:
| Sensor | Unit | Notes |
|---|---|---|
| Production Power | kW | Solar production, real-time |
| Production Energy | kWh | Cumulative solar energy |
| Net Power | kW | Grid import/export (negative = exporting) |
| Net Energy | kWh | Cumulative net grid energy |
| Site Load Power | kW | Total site consumption |
| Site Load Energy | kWh | Cumulative site load energy |
| Battery Power | kW | Battery charge/discharge (battery systems only) |
| Battery Energy | kWh | Battery energy throughput (battery systems only) |
| Battery State of Charge | % | Real-time SOC (battery systems only) |
| Backup Time Remaining | min | Estimated backup duration (battery systems only); may show Unknown if PVS does not broadcast this field in the live stream |
| MID State | Transfer switch state (battery systems only); may show Unknown if PVS does not broadcast this field in the live stream | |
| Data Timestamp | WebSocket message time (disabled by default) |
Enable in integration options after setup. See WebSocket Live Data section above.
Requirements:
- SunVault or compatible battery system
- New firmware (BUILD >= 61840) with authentication
- Integration configured with PVS password (auto-detected during setup)
Control your battery directly from Home Assistant:
Select Entities:
select.battery_control_mode- Switch between operating modes- Self Supply: Use battery to offset home consumption (default)
- Cost Savings: Charge during off-peak, discharge during peak hours (TOU optimization)
- Reserve: Preserve battery for backup power only
select.battery_reserve_percentage- Set minimum battery reserve (5%-100%)
Example TOU Automation:
# Switch to Cost Savings before peak hours (5pm-9pm)
automation:
- alias: "Battery: Cost Savings During Peak"
trigger:
- platform: time
at: "15:00:00"
condition:
- condition: template
value_template: "{{ now().month >= 10 or now().month <= 4 }}" # Winter only
action:
- service: select.select_option
target:
entity_id: select.battery_control_mode
data:
option: "Cost Savings"More automation examples: docs/battery_tou_automation_example.yaml
Note: Mode changes are sent to the PVS immediately when you change the selector in HA. However, the PVS varserver updates its status data every few minutes, so there will be a short lag before HA reflects the new state. This is normal behavior from the PVS itself, not the integration.
- 24-Hour Persistent Error Tracking: Only alerts after 24+ hours of continuous problems, eliminating false positives
- Batched Notifications: Multiple inverter issues grouped into single notification instead of spam
- Smart Recovery Detection: Automatic notifications when persistent issues resolve after extended periods
- Context-Aware Monitoring: Understands normal inverter dormancy (nighttime STATE="error") vs actual hardware failures
- Gmail Rate Limit Protection: Prevents overwhelming email services with notification floods
- Poll Success Rate: Real-time percentage of successful PVS polls
- Total Polls: Integration activity counter since startup
- Consecutive Poll Failures: Current streak of failed PVS poll attempts for troubleshooting
- Last Successful Poll: Timestamp of last successful data retrieval (e.g., "14:29 08-16-25")
- Average Response Time: PVS performance monitoring
- Active Inverters: Count of responding inverters
- PVS Uptime: System availability tracking
Multi-channel notification system:
Notification Channels:
- Setup, Polling, Health, Inverter status
- Mobile notifications with smart fallback to persistent notifications
- Email notifications for critical alerts (PVS offline, inverter failures, flash memory critical)
Prerequisites:
- Email Integration: Set up a Home Assistant email integration (Gmail, SMTP, etc.)
- Service Detection: The integration auto-detects available email services
Configuration:
- Navigate: Configuration → Page 3 (Notifications)
- Select Service: Choose your email service from dropdown (e.g., "Gmail" or "SMTP")
- Custom Recipient (Optional): Override default with dedicated notification address
- Submit: Email notifications are automatically enabled
Critical Alerts That Trigger Emails:
⚠️ Flash Memory Critical: PVS storage below threshold- 🔴 PVS Offline: System connectivity failures
⚠️ Inverter Failures: Individual inverter offline detection- 🔑 Authentication Errors: PVS6 firmware authentication issues
- 🔧 Hardware Issues: Critical system protection alerts
Example Gmail Setup:
# configuration.yaml
notify:
- name: gmail_smtp
platform: smtp
server: smtp.gmail.com
port: 587
sender: your-email@gmail.com
username: your-email@gmail.com
password: your-app-password
recipient: homeassistant-alerts@gmail.comBest Practices:
- Dedicated Account: Use separate email for HA notifications
- App Passwords: Use Gmail app passwords (not account password)
- Test: Use Flash Memory Threshold = 199 MB to trigger test email
- Recipient Override: Enter custom email for dedicated notification accounts
Allow the integration to run for a few hours after setup before configuring the Energy Dashboard, so statistics have time to accumulate.
Step 1: In the HA sidebar, click Energy.
Step 2: Click the pencil icon in the top right corner to open the Energy configuration.
Step 3: Add grid connection
Click Add grid connection and set:
- Energy imported from grid: select
KWh To Home(listed under Solar System - Power Meter ...c) - Energy exported to grid: select
KWh To Grid(same device)
Important: Make sure you select sensors from the
...cmeter (consumption meter), not the...pmeter. Thepmeter does not have bidirectional grid sensors and will not work correctly for the Energy Dashboard.
These sensors come from the consumption meter (CT clamps in your electrical panel). If they are not in the dropdown, see the troubleshooting guide.
Step 4: Add solar production
Scroll down and click Add solar production. In the "Configure solar panels" dialog:
- Solar production energy: search for "Lifetime Power" and select the inverter (e.g., "Lifetime Power - Solar System - Inverter E0..."). Add each inverter as a separate entry for per-panel visibility.
- Solar production power: optional, leave blank.
Battery storage (SunVault / ESS systems only):
In the Energy configuration, click Add battery system and set:
- Energy going in to battery:
sensor.sunpower_ess_<serial>_pos_lte_kwh(ESS Positive Lifetime Energy) - Energy coming out of battery:
sensor.sunpower_ess_<serial>_neg_lte_kwh(ESS Negative Lifetime Energy)
Grid sensors not available? See TROUBLESHOOTING.md for CT clamp, provisioning, and PVS5 firmware limitation scenarios.
For 24/7 Full-Time Monitoring:
Utility Smart Meter (Best Accuracy)
- Direct utility company integration where available
- Real-time production/consumption data
- Grid-tied accuracy for billing reconciliation
Dedicated CT Energy Monitor (Recommended) For comprehensive whole-home monitoring, I recommend dedicated current transformer (CT) systems:
SEM-Meter (Smart Home Energy Meter) (Developer Tested)
- Whole house: ~$100 for main monitoring
- Circuit-level: ~$129 for 16 individual circuits & mains.
- 100% Local Operation: No cloud dependency required
- Direct HA integration via MQTT
- Real-time updates (1-second intervals)
- Professional installation recommended for CT clamps
This monitor is used and recommended by the integration developer for production reliability.
Enhanced SunPower Role
- Individual inverter diagnostics: Per-panel performance monitoring
- PVS system health: Firmware tracking, error detection, communication monitoring
- Equipment maintenance: Temperature monitoring, MPPT analysis, inverter health tracking
- Solar-specific metrics: Frequency analysis, power factor, voltage regulation
- System reliability: Integration performance and diagnostic monitoring
- Network troubleshooting: Connection monitoring and diagnostic capabilities
- Simplified polling: Consistent 24/7 monitoring
Why Separate Monitoring Systems?
Energy Monitor Strengths:
- Real-time data (1-second updates)
- Continuous reliability (purpose-built for 24/7 operation)
- Energy Dashboard optimized (designed for utility-scale accuracy)
- Whole-home coverage (beyond just solar)
Enhanced SunPower Strengths:
- Equipment diagnostics (individual component health)
- PVS integration (official system monitoring)
- Environmental data (temperatures, frequencies)
- Maintenance alerts (firmware updates, communication errors)
- Inverter health tracking (individual panel monitoring)
- MPPT monitoring (DC-side performance analysis)
- Integration reliability (diagnostic dashboard monitoring)
- Network intelligence (connection monitoring and diagnostics)
- Simplified 24/7 polling
Together: Complete solar installation monitoring from grid-level accuracy down to individual panel performance, network connectivity, and panel-specific scheduling.
Polling Frequency: Enhanced SunPower supports 10-3600 second intervals with firmware-aware minimums (10s new firmware, 60s old firmware, 20s battery systems), with a conservative 300-second default. Fast polling capabilities prepare for upcoming varserver migration while maintaining hardware protection.
New Firmware (BUILD 61840+):
- WiFi WAN (Recommended): PVS connects to your WiFi network, gets DHCP IP (typically
192.168.1.x or 192.168.0.x)- Most reliable WAN option for monitoring
- Easy to discover via your router's DHCP client list
- Authentication eliminates need for network isolation
- Requires port 443 (HTTPS) access from Home Assistant to PVS
- LAN Port (Alternative): Fixed IP
172.27.153.1- Most reliable wired connection option
- Must be isolated on a dedicated VLAN or switch port (LAN port runs its own DHCP server)
- Requires static route on your router or HA host to reach the
172.27.153.0/24subnet - Same authentication and features as WAN
- Ethernet WAN (Not Recommended): USB-to-Ethernet adapter on newer PVS6 models
⚠️ Known reliability issues: intermittent connectivity drops that require PVS reboots- Multiple users have reported the PVS becoming unreachable over Ethernet WAN while WiFi and LAN continue working
- If you must use Ethernet WAN, do NOT also have WiFi active - the PVS becomes unreliable with both interfaces on the same network
- Raspberry Pi Bridges/Proxies: Not needed and not supported with new firmware
- The PVS has built-in WiFi - connect it to your home network and use that IP directly
- The RPi bridge was only required for old firmware's LAN port isolation; new firmware has no such requirement
- Technical reason: new firmware uses HTTPS (port 443); most bridges only forward HTTP (port 80)
Different VLANs: The integration works across VLANs as long as routing is configured between them and port 443 is accessible from HA to the PVS.
Old Firmware (BUILD < 61840 on PVS6, BUILD < 5408 on PVS5):
⚠️ Old firmware support is being removed in an upcoming release. See the Old Firmware Users section above.
- LAN Port Required: Must use
172.27.153.1 - Network Isolation Required: PVS LAN port must be isolated (VLAN or separate network)
- See TROUBLESHOOTING.md for VLAN setup
- Or use Raspberry Pi proxy (@krbaker's documentation)
Quick Test: Check if your WAN port responds: curl http://YOUR_PVS_WAN_IP/cgi-bin/dl_cgi/supervisor/info
Quick Fixes:
- PVS Not Responding: Check network connectivity; verify IP address (WAN port recommended for new firmware)
- All Entities Unavailable: Force browser refresh (Ctrl+F5 / Cmd+Shift+R) to clear cached files
- Diagnostic Sensors Not Working: Wait for a few polling cycles; check "Enhanced SunPower Diagnostics" device
- Mobile Notifications Not Working: Verify Home Assistant mobile app installed and mobile service configured
For detailed troubleshooting: See TROUBLESHOOTING.md
We welcome contributions! Please:
- Fork this repository
- Create a feature branch
- Test thoroughly with real PVS hardware
- Submit a pull request with detailed description
Development Guidelines:
- Test both solar-only and battery-equipped systems if possible
- Never increase polling frequency or add PVS stress
- Maintain backward compatibility with existing configurations
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.
- Original Integration: @krbaker - Thank you for creating the foundation
- ESS/Battery Support: @CanisUrsa - Battery system integration
- Enhanced Edition: @smcneece - Community-driven improvements for production reliability
This integration is not affiliated with or endorsed by SunPower or SunStrong Corporation. Use at your own risk.
- Issues: GitHub Issues
- Discussions: GitHub Discussions
- Community: Home Assistant Community Forum
- Changelog: CHANGELOG.md
- Troubleshooting: TROUBLESHOOTING.md
- Migration Guide: MIGRATION.md
Special thanks to community contributors who have helped improve this integration:
- @jtooley307 - Dynamic entity discovery for nighttime installation support (PR #18), Session management with proactive re-authentication and enhanced error handling (PR #23)
- @joshchiou - Fixed memory leak crash caused by timestamp-based virtual meter naming for IP-serial PVS devices (PR #64)
Max Roberts - For helping get basic battery functionality working Ian Jones - For helping beta test battery control features
Hardware: SunPower PVS, SunPower PVS5, SunPower PVS6, SunStrong, SunVault, ESS Battery, Solar Inverters
Software: Home Assistant, HACS, Python, krbaker fork
Features: Solar Monitoring, Inverter Health, Battery Tracking, Flash Wear, Energy Dashboard, Mobile Notifications