What is a smart meter actually doing?
Measuring your energy use at short intervals and sending the readings automatically — and the genuinely consequential part is not the display in your kitchen but what half-hourly data makes possible.
What it does:
Automatic readings, removing estimated bills and the need for manual submission. This alone resolves a large share of billing disputes.
Interval measurement, typically every half hour, sent daily or more frequently depending on the consent you gave. You can usually choose how often it is shared.
A separate communications network, not your home broadband, so it works without your internet.
An in-home display, showing near-real-time use and cost. Evidence on behaviour change is modest: displays produce small savings that tend to fade, which is the honest finding.
Remote switching between credit and prepayment modes, and remote disconnection capability — which is a genuine concern raised by consumer groups.
Why half-hourly data is the point. It enables time-of-use tariffs, where electricity is cheaper when demand is low or renewable output is high. This matters enormously as grids decarbonise: shifting car charging, heating and appliance use to cheap periods reduces the need for peaking plant and for network reinforcement, and can cut bills substantially for households able to shift load.
It also enables demand-response schemes paying you to reduce use at peak times, faster switching between suppliers, and better fault detection.
The legitimate concerns: interval data reveals occupancy patterns and something about appliance use, so the sharing frequency you consent to matters; older meters losing functionality when switching supplier, a real problem in some rollouts, largely addressed by newer versions; and remote disconnection.
What a smart meter does not do: save energy by itself. It measures; you or an automated system must act on it. A household that never changes its behaviour or tariff saves almost nothing, which is the gap between the policy case and many people's experience.
Practical advice: check which version is being installed, choose a data-sharing frequency you are comfortable with, and — most importantly — look at whether a time-of-use tariff actually suits your usage pattern.