One coordinated heat pump for home comfort, hot water, and pool heat

What is onePump?

onePump is a coordinated residential thermal energy hub concept: one heat pump system that can serve home cooling, home heating, domestic hot water, and pool heating from a shared thermal loop.

Those loads are usually separate appliances with separate controls, which duplicates equipment and wastes useful heat. The onePump thesis is that the real opportunity is packaging, controls, hydronic integration, installer workflow, safety, and serviceability — not basic thermodynamics.

One system, four overlapping loads

In cooling season the system can recover heat removed from the home and redirect it to hot water or the pool instead of rejecting it outdoors. When demand exceeds capacity, the controller explains which load is active, what is waiting, and why.

Why it matters

Many homes run separate systems for air conditioning, heating, water heating, and pool heating. That means duplicated equipment, missed heat-recovery opportunities, and poor coordination with solar, batteries, and dynamic electricity pricing.

The concept targets premium electrification homeowners in mild-to-warm regions whose cooling, hot water, and pool loads overlap, and installers who need a repeatable design, commissioning, and diagnostics package. It is not a promise of unlimited simultaneous heating for every load, drop-in compatibility with every home, or savings independent of climate, usage, and installation quality.

Current status

Status: under development. onePump is an early product concept. The repository holds product framing, requirements, architecture notes, an executable simulation model, and planning documents. No production hardware, firmware, or real equipment control software has been implemented.

• Simulation: onepump_sim models load priority, heat recovery, deferrals, and pool readiness across 24-hour scenarios. The Stage 1 scorecard recorded a "narrow" decision: bounded target-home, summer-recovery, and explainability profiles pass executable checks, while pool-expectation risk needs tighter bounds before any customer-facing claims.
• Controller research: platform discovery and source-capture research for candidate controller families (Siemens, Schneider, WAGO) is in progress. No controller hardware is selected, purchased, or approved; all release claims stay blocked until reviewed evidence exists.
• Research prototype: the walkthrough below lets homeowners and installers compare four candidate launch-package boundaries. It is a reversible, local walkthrough with no equipment control, connected service, or default data storage.

This site tracks the repository's current state. For the latest status and roadmap, see the onePump repository and its README. Nothing here is an offer, quote, certification, or readiness claim.

Research walkthrough

The interactive sections below are a local, reversible research prototype for evaluating the four candidate onePump launch-package boundaries. It supports the seven research journey stages: proposition review, home qualification, site survey, budgetary scope, mock commissioning, status and deferral interpretation, and service handoff. All package scopes and dollar ranges are illustrative research prompts, not offers or binding quotes.

1 of 7 · Proposition

What the concept is trying to simplify

2 of 7 · Qualification

Could this home fit the current research boundary?

Choose the closest answer for every item. Unknowns go to installer review; they are never treated as compatible by default.

3 of 7 · Installer site survey

Inputs needed before a scope can be credible

4 of 7 · Candidate package and budgetary scope

Compare what onePump might—and might not—provide

Select each boundary during research. None has been selected for release.

Every displayed dollar range is an illustrative estimate for research discussion. It is not a binding quote; site work, taxes, permits, freight, and service needs may be unresolved.

5 of 7 · Mock commissioning

A conceptual 16-step walkthrough

1. Select system topology.
2. Select modules and record IDs, revisions, and interface contracts.
3. Enter heat-pump capacity and operating limits.
4. Enter DHW tank volume, target range, and sanitization settings.
5. Enter pool volume, exchanger rating, target, and allowed windows.
6. Enter comfort equipment type, design temperatures, and flow limits.
7. Map sensors to physical locations.
8. Map pumps and valves to controllable loops.
9. Run module verification for safety-critical modules.
10. Run actuator tests.
11. Run sensor plausibility checks.
12. Prove branch flow and check heat-exchanger delta-T direction.
13. Verify branch isolation and safe-state behavior.
14. Run a dry-run day simulation.
15. Confirm homeowner priorities and schedules.
16. Keep automatic control locked until safety-critical checks pass.

6 of 7 · Homeowner status

Say what the system is doing in plain language

7 of 7 · Service and warranty handoff

Make accountability visible before anyone proceeds