Plan appliance cycles and EV charging around your electricity tariff using existing Home Assistant entities. Learn when an appliance uses energy during a cycle, compare running costs, and find suitable low-cost or negative-price windows.
- Appliance learning: capture completed cycles from power and energy sensors, retain learned programme profiles, and estimate costs across tariff periods.
- Scheduling recommendations: compare programmes and start windows using configured deadlines, programme policies and automatic cooldowns.
- Optional dishwasher controls: opt into Home Connect / Bosch-style controls with connection, door and already-running safety checks. Manual programme requests bypass automatic cooldowns, not physical safety checks.
- EV charging plans: use battery percentage, usable capacity, target, charge power and efficiency to select charging windows and estimate cost or profit.
- Ofgem comparison: choose a GB electricity region and payment method for a daily cached, effective-dated default-tariff unit-rate benchmark.
- Optional dashboards: a standard-card template, plus a richer chart example with tariff-local time, 24/48-hour coverage, benchmark and current-time markers.
EV charging is advisory: Load Optimizer does not switch a charger or power plug. Installing the integration does not enable automatic appliance starting. Your existing tariff, appliance and vehicle integrations remain required.
Load Optimizer is included in the default HACS catalogue.
- Open HACS in Home Assistant and search for Load Optimizer.
- Download the integration, choosing the latest stable GitHub release.
- Restart Home Assistant.
- Go to Settings > Devices & services > Add integration, then search for Load Optimizer to configure it.
If it does not appear in your HACS catalogue, use Custom repositories as a fallback. Add the following URL with category Integration, then download Load Optimizer and follow the restart and configuration steps above:
https://github.com/stevesherry123/load-optimizer-home-assistant
Do not choose a development branch for a normal installation. Catalogue inclusion was approved and merged on 2 November 2026. Existing custom-repository installations do not need to be removed or recreated; keep your configured integration and its learning data.
Home Assistant 2024.12 or later is required. The Ofgem benchmark is for Great Britain; other supplier integrations can supply compatible tariff data. No Octopus API token, separate app, or AI subscription is required.
Start with the setup guide and compatibility table. Configure one learned-appliance hub containing all your appliance instances; EV planning uses separate entries. Existing settings can be edited through the integration's Configure cog, including EV settings without recreating the entry.
Your first milestone is a completed learned cycle and a priced recommendation, not an automatic start. The setup example includes the explicit programme policy needed to make a learned profile eligible. See the separate Home Connect control and advisory EV guides for their additional requirements.
To migrate the existing add-on, create a Load Optimizer integration entry with
load type learned_appliance, paste your existing add-on instances_yaml and
tariff settings, then import the old /data/load_optimizer.json database with
the load_optimizer.import_legacy_state service.
See the migration guide. Stop the old add-on before activating the integration so two runtimes cannot capture or control the same appliance concurrently. Keep its database and backup until the imported counts and a new complete cycle are verified.
The old add-on distribution is retired. Do not add this repository to the Home Assistant add-on store. The compatibility engine and explicit administrator import action remain available for migration; ordinary new installations need no legacy database.
The HACS installation includes an optional dashboard template covering
integration health, appliance plans, EV charging, and learned-cycle data. It is
not automatically added to your sidebar and its example entity IDs must match
your installation. See
docs/dashboard.md for the short installation step.
Version 1.5 adds an effective-dated Ofgem default-tariff benchmark. Choose the electricity region and payment method in the integration setup or options. Load Optimizer checks Ofgem's official tables daily, caches the last validated value, and exposes it as a native sensor for the tariff chart. This is a comparison benchmark, not a price limit on dynamic tariffs such as Agile.
Normal users are offered stable GitHub releases. Pushing a branch, merging to
main, or creating a tag alone does not publish a new stable update.
Beta testers explicitly enable prereleases in HACS. Update installation is a
user action unless they have configured their own automatic-update automation;
integration code changes require a Home Assistant restart to take effect.
Tariff history, historical analysis, portable history import and optional AI summaries remain experimental beta features, not stable functionality. Public development branches can be inspected by anyone, even though they are not offered as normal stable updates. Do not enable beta updates on an installation that must remain on stable.
See release channels and publication for the exact workflow, notification process and limitations of download/installation counts.
- EV charging is advisory, not a built-in charger switch controller.
- Appliance setup uses YAML definitions; a fully guided appliance editor is planned. Only one learned-appliance hub is supported.
- Native dishwasher control currently targets appliance ID
1and requires Home Connect references plus explicit activation. Other appliance types do not inherit a generic start controller from learning support. - The packaged dashboard is a standard-card template. The richer tariff-chart example requires ApexCharts Card and installation-specific entity edits.
- Ofgem is a comparison benchmark, not a ceiling on Agile prices. Select the electricity region used by your meter's tariff, not a general geographic label.
- Home Assistant unavailable/unknown states and incomplete future tariffs can leave a recommendation waiting. Do not turn missing data into a start command.
Report faults with the release number, Home Assistant version and redacted diagnostics in GitHub Issues. Never post access tokens or a full private configuration. See the contribution guide for release-channel and testing rules.
For a suspected vulnerability, use the private reporting route in SECURITY.md, not a public issue. See data handling and privacy before sharing logs, dashboard screenshots or older diagnostic downloads. The integration adds no telemetry.
The release-channel guide distinguishes custom repository installation from inclusion in HACS's default catalogue.
The README is the front door, not the entire manual. HACS displays versioned README content; release notes describe each update, and the linked guides provide setup and troubleshooting detail.
- Installation and configuration
- Compatibility and supported control targets
- Optional Home Connect dishwasher control
- Advisory EV planning and input examples
- Dashboards, manual starts and scheduling explanations
- Troubleshooting and support checklist
- Migration from the retired add-on
- Release channels, HACS acceptance and statistics
- Changelog and GitHub releases
- Privacy and private vulnerability reporting
- Contributing, architecture and roadmap
Older design documents are historical proposals, not promises of released features. Use this README, the setup guide and the notes for your installed release when configuring the integration. The retired add-on and orchestration packages are no longer distributed; all supported learning, scheduling, recovery, and appliance controls live in the integration.