What should I budget for whole-home energy monitoring in a new build?

For a realistic comparison, I’d split the allowance into one-time costs and recurring service fees. The hardware and electrician’s work are obvious, but cloud access, advanced analytics, or control-platform subscriptions can materially change the total over several years.

I’d ask each vendor to price these separately:

- Monitor, CTs, gateways, and any required panel hardware
- Electrical installation, labeling, and commissioning
- Configuration of circuit names, solar, battery, and tariff data
- Integration or licensing for load control
- Annual cloud, app, API, or support fees

That matters especially with the proposed circuit-level monitoring. Adding CTs may look inexpensive beside the panel work, but a system that needs a paid account for historical data or automation can cost more than expected over the life of the house. I’d also confirm what still works locally if the subscription ends, particularly basic monitoring and demand-response rules.

I’d push back slightly on treating circuit-level monitoring mainly as a subscription-cost question. For a house with batteries, EV charging, and heat pumps, the first check should be whether the system provides dependable local data and can still control essential loads when the internet or vendor cloud is unavailable.

I’d ask the installer to demonstrate, in writing if possible:

- Whether current and power data remain available on the local network during an outage
- Whether load-shed or priority rules run locally, rather than through a remote server
- What happens to EV charging, water heating, and HVAC controls if the gateway loses connectivity
- Whether the data can be exported through a local API or standard protocol
- Which functions disappear when a subscription ends

A low annual fee isn’t much of a saving if a cloud outage prevents the battery from following the intended load strategy, or leaves a controllable resistance load running during a peak period. Subscription pricing still belongs in the allowance, but I’d rank local fallback behavior ahead of it when comparing systems.

I’d question putting outage behavior ahead of measurement coverage. Local fallback is important, but circuit-level CTs only earn their cost when they cover the loads the control strategy actually needs to see.

For budgeting, I’d start by mapping each intended action to its required measurements:

- EV charging: charger circuit, and possibly whole-home import
- Water heating or other resistance loads: the individual circuit
- Heat pumps: dedicated equipment circuits, if they’re part of the shed or tariff strategy
- Solar and battery: production, battery power, and grid import/export
- Pool equipment: only if it’s a meaningful flexible load

That also gives the installer something concrete to prove during commissioning: accuracy at low and high loads, correct import/export direction, and whether the control rule responds to the measured value rather than an estimate. A system can keep operating locally during an outage and still be a poor investment if it can’t distinguish the loads needed for tariff optimization.

I’d include local operation and subscription behavior in the specification, but set the circuit-CT allowance from the control goals first. Monitoring every branch circuit is usually less useful than accurately monitoring the handful of flexible loads that determine demand and battery decisions.

The commissioning check should include documented CT placement and phase mapping, not just a general accuracy test. A reversed CT or a CT assigned to the wrong phase can produce numbers that look plausible while making import/export direction and load-control decisions unreliable.

For each monitored circuit, I’d ask the installer to record:

- CT location and circuit name
- Phase assignment and polarity
- Meter or gateway channel used
- Expected direction for consumption, solar production, and battery flow
- Verification readings under a known load

For example, turning on the water heater should increase the mapped water-heating load and whole-home consumption by roughly the same amount. Solar production should reduce grid import, not appear as additional household demand. Those simple tests can expose a phase mismatch that a dashboard’s total may hide.

That documentation also makes future troubleshooting much easier if a CT has to be moved during panel work. It’s a small commissioning requirement compared with the cost of installing circuit-level hardware, and it directly supports Cedarnova47’s point about proving that control rules respond to the correct measured load.

Charles’s suggestion to record the expected direction and verify it under a known load is especially useful. I’d add a short post-occupancy verification period to the commissioning scope, rather than treating the handover test as the final check.

Once the house has experienced representative conditions, the installer could review a few days of data for unexpected baseloads, incorrect circuit labels, or control rules that behave differently when solar, batteries, HVAC, and EV charging overlap. I’d ask whether they can include a follow-up review or adjustment window, with the exact duration and included work priced separately. That seems more valuable than trying to predict every unusual operating condition during a single commissioning visit.