Load¶

Loads represent power consumption in your system. The Load element uses forecast data to model any type of consumption pattern from fixed baseline loads to variable time-varying consumption.

Configuration¶

Name¶

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

Examples: "Base Load", "House Load", "Total Load", "EV Charger", "Pool Pump"

Forecast¶

Specify one or more Home Assistant sensor entities providing power consumption data. The Load element is flexible and works with both constant and time-varying patterns.

Single forecast example:

Multiple load components example:

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

Constant Load Pattern¶

For fixed baseline consumption that doesn't vary over time, use an input_number helper providing a constant value.

Creating a Constant Load¶

1. Create Input Number Helper:

   • Go to Settings → Devices & Services → Helpers
   • Add a new "Number" helper
   • Set name: "Base Load Power"
   • Set unit: kW
   • Set desired constant value (e.g., 1.0)

2. Configure Load Element:

   Field	Value
   Name	Base Load
   Forecast	input_number.base_load_power

This configuration represents constant consumption (e.g., 1 kW = 24 kWh per day).

Determining Your Baseline¶

To find your baseline consumption:

1. Measure overnight minimum: Check your consumption during hours when everything is "off" (e.g., 2-4 AM)
2. Add always-on devices: Include refrigerators, networking equipment, standby devices
3. Add safety margin: Increase by 10-20% to account for variations

Typical Values¶

• Small apartment: 0.2-0.4 kW
• Average home: 0.5-1.2 kW
• Large home: 1.0-2.0 kW
• Commercial: 2.0+ kW

Forecast-Based Load Pattern¶

For variable consumption that changes over time, use sensors that provide forecast data.

Single Variable Load¶

The forecast sensor should provide:

• Current consumption value
• Forecast data for future periods
• Unit of measurement: kW

Common Forecast Sources¶

Direct Measurement:

• Home energy monitors
• Smart meters with forecast capability
• Utility consumption APIs

Calculated Forecasts:

• Template sensors combining multiple sources
• Machine learning predictions
• Historical pattern averaging

Scheduled Devices:

• EV charger schedules
• Pool pump timers
• HVAC duty cycles

Combining Constant and Variable Loads¶

For most accurate optimization, combine a constant baseline with variable consumption:

Configuration 1: Constant baseline

Configuration 2: Variable consumption on top

Total consumption = 1.0 kW (constant) + variable forecast.

This approach:

• Simplifies forecast creation (only forecast variable portion)
• Ensures baseline is always covered
• Improves optimization reliability
• Makes it easier to adjust baseline without changing forecasts

Combining Loads¶

Combine multiple load sources in a single element:

HAEO automatically sums all sensors at each timestamp, allowing you to model complex load profiles from simple components.

Configuration Examples¶

Simple Constant Load¶

Fixed baseline consumption:

Variable Household Consumption¶

Time-varying consumption with forecast:

Combined Constant and Variable¶

Baseline plus variable components:

Multiple Variable Sources¶

Combine multiple consumption sources:

Input Entities¶

Each configuration field creates a corresponding input entity in Home Assistant. Input entities appear as Number 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 Load element creates 1 device in Home Assistant with the following sensors.

Power¶

The optimal power consumed by this load at each time period.

Since loads are not controllable in HAEO, this value matches the forecast or constant value provided in the configuration. The optimization determines how to supply this power (from grid, battery, or solar), but the load consumption itself is fixed.

For constant loads: The sensor shows the same value for all periods (the configured constant power).

For variable loads: The sensor reflects the forecast values for each period from the configured sensor(s).

Example: A value of 2.5 kW means this load requires 2.5 kW at this time period, which the optimization must supply from available sources.

Power Possible¶

The maximum possible load from the forecast configuration.

For loads, this equals the power sensor since load consumption is fixed. Shows the value from the configured forecast sensor(s).

Forecast Limit Price¶

The marginal cost of supplying power to this load at each time period. See the Shadow Prices modeling guide for general shadow price concepts.

This shadow price represents the cost of the most expensive power source needed to satisfy this load. It reflects what it costs the system to deliver 1 kW to this load location.

Interpretation:

• Positive value: Represents the cost of serving this load (typically grid import price when importing)
• Higher values: Indicate serving the load is expensive (peak grid prices, battery constraints, etc.)
• Lower values: Indicate serving the load is cheap (off-peak prices, excess solar, etc.)
• Magnitude: Shows the economic pressure at this load point in the network

Example: A value of 0.28 means it costs $0.28 per kW to serve this load at this time period, reflecting the marginal cost of the power source.

All sensors include a forecast attribute containing future optimized values for upcoming periods. For constant loads, the forecast shows the same value for all periods. For variable loads, the forecast reflects the configured sensor forecast values.

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 sensor provides numeric values
• For input_number helpers, ensure they are created and have a value set

Incorrect Load Values¶

Problem: Load values don't match expectations

Check:

1. Units: Ensure sensor reports power in kW (not W or MW)
2. Multiple sensors: Verify you want additive combination
3. Constant vs Variable: Confirm sensor type matches intent
4. Forecast data: Check sensor attributes contain forecast if expected

Optimization Infeasible¶

If optimization fails with loads:

1. Check total load vs supply: Ensure grid + solar + battery can supply the total load
2. Verify load values: Check that load power is reasonable
3. Grid limits: Ensure grid import limit is sufficient for load
4. Constant load too high: If using constant load, verify it's within available power

Load Too Low¶

Problem: Optimizer shows lower consumption than expected

Cause: Loads in HAEO represent required consumption that must be met. If your forecast includes optional or deferrable loads, the optimizer may schedule them differently.

Solution: Only include loads that represent actual required consumption in the Load element. For controllable/deferrable loads, model them separately with appropriate constraints.

Next Steps¶