Solar¶

Solar panels that generate electricity. HAEO optimizes how generated power flows through your energy network.

Configuration¶

Name¶

Unique identifier for this solar system within your HAEO configuration. Used to create sensor entity IDs and identify the solar array in connections.

Examples: "Rooftop Solar", "East Array", "West Array", "Combined Solar"

Forecast¶

Specify one or more Home Assistant sensors providing solar generation data.

Single array example:

Multiple arrays example (e.g., different orientations):

Provide all solar array forecasts to get accurate total generation predictions. See the Forecasts and Sensors guide for details on how HAEO processes sensor data.

Production Price¶

Cost or value per kWh of electricity generated.

Default: Leave empty for zero cost (most common case)

When to use non-zero values:

• Modeling opportunity cost of generation
• Accounting for maintenance costs per kWh
• Rare specialized scenarios

Curtailment¶

Allow HAEO to reduce generation below the forecast level.

Default: Enabled (HAEO can curtail generation when beneficial)

When enabled: HAEO can curtail generation if:

• Export prices are negative (paying to export)
• Export limit is reached
• Battery is full and loads are satisfied

When disabled: Generation follows forecast exactly (useful when inverter cannot be controlled)

Requirements:

• Inverter must support active power limiting
• Control mechanism must be implemented separately (HAEO only optimizes)

Configuration Examples¶

Basic Configuration¶

Single solar array with forecast:

Multiple Arrays¶

Combine multiple solar arrays or forecast sources:

Input Entities¶

Each configuration field creates a corresponding input entity in Home Assistant. Input entities appear as Number or Switch entities with the config entity category.

Input entities include a forecast attribute showing values for each optimization period. See the Input Entities developer guide for details on input entity behavior.

Sensors Created¶

Sensor Summary¶

A Solar element creates 1 device in Home Assistant with the following sensors.

All sensors include a forecast attribute containing future optimized values for upcoming periods.

Sensor Details Power¶

The optimal power generated by the solar array at each time period after any curtailment decisions.

This represents the actual power output from the solar system. When curtailment is disabled, this equals the available power from the forecast. When curtailment is enabled, this may be less than available power if the optimizer determines curtailing generation reduces total system cost.

Example: A value of 4.2 kW means the solar array is producing 4.2 kW at this time period.

Power Available¶

The maximum solar power available from the forecast before any curtailment.

This represents what the solar array could produce based on weather forecasts and system capacity. It serves as the upper limit for actual generation. The difference between power_available and power shows how much generation is being curtailed.

Example: A value of 5.0 kW when power is 4.2 kW means 0.8 kW of solar generation is being curtailed at this time.

Forecast Limit¶

The marginal value of additional generation capacity. See the Shadow Prices modeling guide for general shadow price concepts.

This shadow price shows how much the total system cost would change if the solar forecast were increased by 1 kW at this time period. It indicates whether more solar generation would be beneficial or detrimental.

Interpretation:

• Zero value: Not curtailing generation (using all available solar power)
• Positive value: System would benefit from more solar generation
  • More generation would reduce total system cost
  • If curtailing, suggests curtailment may be too aggressive
• Negative value: System is better off with less solar generation
  • Curtailing generation reduces total system cost
  • Typically occurs when export prices are negative or battery is full with nowhere for energy to go
  • More negative values indicate curtailing more aggressively would further reduce costs

Example: A value of -0.10 means that if the solar forecast were 1 kW higher, the total system cost would increase by $0.10 at this time period, indicating that curtailing generation is economically beneficial.

Troubleshooting¶

Sensor Not Found¶

Problem: Error "Sensors not found or unavailable"

Solutions:

• Verify sensor entity ID exists in Home Assistant
• Check sensor is available (not "unavailable" or "unknown")
• Ensure solar forecast integration is configured correctly

Incorrect Generation Values¶

Problem: Generation values don't match expectations

Check:

• Sensor units are kW (not W or kWh)
• Multiple sensors sum correctly (intended?)
• Forecast integration is providing realistic data
• System size configured correctly in forecast integration

No Generation in Optimization¶

Problem: Optimization shows zero solar generation

Possible causes:

• Forecast covers wrong time period (nighttime only)
• Sensor values are zero due to weather
• Forecast data format not recognized

Solutions:

• Check sensor forecast attribute in Developer Tools → States
• Verify forecast covers daytime hours
• Review HAEO logs for format detection warnings

Next Steps¶