Cleaner System Logs and Alerts

Each site now has a dedicated Logs area with separate tabs for message logs, hardware errors, and alerts. The same organized experience is available when reviewing operational information from site and ticket views.

Why This Matters

System activity can include several different types of information, from communication history to active hardware issues. Separating these records makes it easier for O&M and service teams to find the information they need without sorting through one combined list.

How It Works

The Logs area organizes site activity into three tabs:

• Message Logs for recorded system messages

• Hardware Errors for equipment-related issues

• Alerts for conditions that may require attention

Teams can access this information while working from either the site or the related ticket view.

24-Hour Fleet Performance in Sites V2

Sites V2 now includes Daily Estimate and 24h Performance columns, giving teams a faster way to identify recent production changes across the fleet.

Why This Matters

Monthly performance is useful for understanding longer-term trends, but it may not reveal a sudden production drop quickly enough.

The new daily metrics help O&M teams spot systems that performed below expectations during the past 24 hours, prioritize investigation, and respond sooner when a site may need attention.

How It Works

Teams can add the following columns to their Sites V2 views:

• Daily Estimate, showing the expected production for the daily period

• 24h Performance, showing recent production relative to that estimate

These columns can be used alongside existing filters, sorting, and saved views to review short-term fleet performance.

Production-to-Consumption Ratios in Sites V2

Sites V2 can now display and export solar production-to-energy-consumption ratios for both the last 12 months and the lifetime of the system.

Why This Matters

Production totals do not always answer a customer’s most practical question: how much of their household energy use is being covered by solar?

These ratios give installers a clearer way to respond to customer and sales requests, compare solar generation with consumption, and provide additional context around long-term system performance.

How It Works

Teams can add the following ratio fields to Sites V2:

• Last-12-month production-to-consumption ratio

• Lifetime production-to-consumption ratio

The values can be reviewed within Sites V2 and included when exporting site data for further reporting or customer analysis.

More Energy Data in Site Exports

Site Energy exports from the customer view now include consumption, grid export, and grid import data in addition to solar production.

Why This Matters

A production-only report shows how much energy the solar system generated, but it does not provide a complete picture of how energy moved through the home.

Including consumption, import, and export data helps customers better understand how much electricity they used, how much excess solar energy was sent to the grid, and how much energy was drawn from the grid during the selected period.

How It Works

When a customer downloads a Site Energy report in CSV or XLSX format, the export can now include columns for:

• Solar production

• Household consumption

• Energy exported to the grid

• Energy imported from the grid

The additional data is included directly in the downloaded report.

New Automation Trigger for Project Extra Field Changes

Teams can now start an automation whenever a selected project extra field changes.

Why This Matters

Installers often use custom project fields to track information that does not fit into standard project stages, such as equipment details, approval statuses, service-plan information, or other company-specific data.

This trigger allows updates to those fields to automatically start customer communication or internal follow-up workflows, reducing the need for employees to monitor changes and respond manually.

How It Works

When building an automation, teams can select a project extra field and use a change to that field as the trigger.

Once the selected value is updated, Sunvoy starts the connected automation. Teams can then use the existing automation workflow to send a message, notify the appropriate team, or initiate another configured follow-up action.