Smart Distribution Board / IoT Consumer Unit Installation Guide (UK)

A smart consumer unit, sometimes called an IoT distribution board, is a standard BS EN 61439-3 type-tested domestic distribution board with three additions: per-circuit current measurement, a local intelligence module, and a communications interface. Everything BS 7671 requires of a traditional CU — main switch, RCD or RCBO protection, AFDD where mandated by A4:2026, correct earthing arrangement — still applies. The "smart" layer sits on top, not in place of it.

Measurement is normally done with split-core CT clamps around each outgoing live conductor, terminated at a measurement bus, with data brought back to a DIN-rail controller. The controller is typically a low-power ARM device with local storage and a WiFi, Zigbee or wired LAN radio. Some products go further: smart RCBOs replace conventional electromechanical RCBOs with a microprocessor-controlled trip mechanism that can be commanded open or closed remotely, and some integrate AFDD into the same device. That is where the category diverges from a traditional CU and where the regulatory questions start to bite — particularly around Section 537 isolation, fault discrimination, and TTA status.

The feature stack is reasonably consistent across products in 2026. Not every product offers every feature, and the regulatory implications differ:

A useful mental model: a smart CU is a normal CU plus per-circuit telemetry, plus optional remote breaker control, plus optional rule-based automation. Each addition interacts with BS 7671 differently.

How a smart CU talks to the outside world is one of the most important practical decisions. The dominant options each have different implications for reliability, cybersecurity and installer responsibility.

1. WiFi (most common) — the CU joins the homeowner's 2.4 GHz network and communicates with the vendor cloud. Zero extra hardware, simplest commissioning, but exposed to whatever else is on the SSID.
2. Zigbee or Thread to a hub — the CU joins a local mesh and talks to a vendor hub. Better isolation from general WiFi traffic, but adds a hardware dependency.
3. Wired LAN — Cat5e/6 to an RJ45 inside or adjacent to the CU. Best reliability and cybersecurity, but requires structured cabling that most retrofits do not have.
4. LAN-only (no cloud) — a small subset of products that operate purely on the local network. Aimed at integrators; smallest external attack surface.
5. Power-line communications — minority approach; reliable in newer builds but susceptible to VFD, inverter and LED-driver interference.

For new-build and major refurbishment, specify wired LAN to the meter position where reasonable. For retrofit, WiFi is usually the only practical option — in which case the cybersecurity controls below become important.

The cloud architecture dictates where personal usage data lives, who can see breaker state, and what happens during a vendor outage. The dominant UK pattern is a vendor-operated multi-tenant cloud: telemetry pushes to the vendor, the homeowner's app pulls from the same endpoint, and remote breaker commands traverse that round trip.

At handover, document where data lives, what happens during a cloud outage, and the vendor's data retention policy. If the homeowner has PV-plus-battery and wants per-circuit data for self-consumption analysis, confirm the vendor exposes a usable export or API.

The single most consequential feature of a true smart CU — and the one with the most BS 7671 implications — is the ability to open and close breakers remotely. Smart RCBOs contain a motor or solenoid that can drive the contacts on command. That command can come from the homeowner's app, from an automation rule on the controller, from a third-party home automation system, or from the vendor cloud.

For the installer, the safety implication is the inverse of what most homeowners assume. The homeowner imagines turning the kitchen off from a beach in Spain. The installer must imagine someone, somewhere, turning the kitchen back on while a circuit is being worked on. Section 537 of BS 7671:2018+A4:2026 is unambiguous: isolation devices must be capable of being secured against unauthorised reclosure — and a cloud command is precisely the unauthorised reclosure that Section 537 is concerned with.

A second consideration is fault discrimination. Smart RCBOs have firmware that can be updated, and an update can in principle alter trip characteristics. Record firmware version at commissioning, retain it on the EIC, and treat any vendor-pushed change to trip behaviour as a fault that requires re-verification. See our consumer unit upgrade guide and BS 7671 A4:2026 AFDD changes for context.

Section 537 of BS 7671:2018+A4:2026 deals with isolation, switching and control. The text predates smart CUs by decades, but reads on them cleanly when the right questions are asked.

1. Means of preventing inadvertent reclosure — the device must be capable of being secured against unauthorised reclosure. For a smart RCBO this means a physical lock-off slot, a removable handle, or an upstream lock-off. A software-only "isolation mode" is not a Section 537 means.
2. Verification of isolation — conductors must be capable of being verified as dead. Smart telemetry showing "0 W" is not a substitute for testing with a GS38-compliant voltage indicator on a known live source.
3. Visible indication of off-state — for many smart RCBOs the handle position still provides this. Where the handle position is reliable, use it; where it is not, isolate upstream.
4. Independence from automatic reclosure logic — any automation rule capable of reclosing the breaker must be disabled at commissioning and re-enabled only after work is complete.
5. Documentation — the EIC should record that Section 537 has been considered for the smart switching elements specifically.

The strongest commercial case for a smart CU in 2026 is the household with an EV, a heat pump, an electric shower and a tendency to run them at once. A 60-80 A single-phase supply will trip the main fuse if these loads coincide, even though no one circuit is overloaded. The traditional answer is a DNO service upgrade — months of waiting, several thousand pounds, disruption. The smart CU answer is load shedding: rank the controllable loads (EV charger, heat pump, immersion, towel rail) and curtail the lowest-priority one whenever whole-house current approaches a configured threshold. With a properly tuned rule set the household never trips the cut-out, and the perceived supply size effectively rises. The actual cable, fuse and earthing arrangement are unchanged — but the practical likelihood of nuisance tripping drops dramatically.

See our V2H bidirectional EV charging guide — a smart CU plus V2H plus a dynamic Octopus tariff genuinely changes the economics of a 60-80 A supply.

Octopus Energy publishes fixed and dynamic tariffs in a structured API, and most credible smart CU vendors integrate directly. Typically a one-time OAuth handshake from the vendor app makes half-hourly Agile prices, Cosy heat-pump windows, and Intelligent Octopus EV slots available to the rules engine.

A smart CU is a mains-rated, safety-critical device permanently connected to a domestic WiFi network. A compromised smart bulb is a nuisance. A compromised smart CU can in principle open or close breakers — including those feeding life-safety equipment such as carbon monoxide alarms, fridges, medical equipment or heating in cold weather. The Product Security and Telecommunications Infrastructure Act 2022 (PSTI) sets minimum cybersecurity requirements for consumer connectable products sold in the UK. Look for vendors that publish a PSTI statement of compliance, a security disclosure address, and a stated minimum security update support period. Where the vendor will not commit in writing, treat that as a significant risk.

1. Network segmentation — recommend the CU sits on a dedicated IoT SSID, not the main household SSID. Most consumer routers support this.
2. Strong passphrase — unique to the IoT SSID and not shared with the homeowner's general guest password.
3. Vendor account hygiene — unique strong password and two-factor authentication where the vendor supports it.
4. Firmware update policy — automatic updates enabled, but the homeowner should be told that any firmware-pushed change to RCBO trip behaviour requires re-verification.
5. Disable unused features — open APIs, MQTT brokers and remote administration ports should be off unless actively used.
6. Handover documentation — record the cybersecurity choices made at commissioning so the next installer or owner can see what was set up and why.

BS EN 61439 governs low-voltage switchgear and controlgear assemblies, with Part 3 covering distribution boards intended for use by ordinary persons — domestic consumer units. A CU sold in the UK is type-tested as an assembly: the manufacturer has demonstrated the specific combination of enclosure, busbar, main switch, RCDs and RCBOs meets the standard for thermal performance, fault-current withstand and EMC. Certification applies to the assembly as supplied. For a smart CU, the type-tested assembly is the whole thing — enclosure, controller, CTs, smart RCBOs together. That is fine when the installer uses it as the manufacturer intends. Where TTA status comes under pressure:

BS 7671:2018+A4:2026 expanded the situations in which AFDDs are required. Smart CUs interact with this in two useful ways. First, several vendors now ship smart RCBOs that integrate AFDD into the same physical device, so one busbar slot provides overcurrent, residual-current and arc-fault protection plus telemetry — a tidy compliance outcome where A4:2026 mandates AFDD. Second, telemetry can assist diagnosis of nuisance trips. On a conventional CU the only forensic information is "it tripped"; on a smart CU the controller may have a high-resolution snapshot of current and voltage either side of the event, and may distinguish a true arc fault from a switching transient or faulty appliance.

The category in 2026 spans three rough tiers. We name them by category, not specific product, because the lineup is still moving:

1. Mainstream CU manufacturers with a smart range — the established UK distribution board names have introduced smart variants of their existing lines. These are usually easiest to specify because dumb and smart variants share enclosure geometry.
2. Energy-monitoring specialists who have moved into protection — companies that started in retrofit CT-clamp energy monitoring have moved into smart RCBOs and full smart CUs. Usually the slickest apps and strongest tariff integration.
3. Home automation crossover products — products designed primarily for integrators and Home Assistant users. Often LAN-first, open API, strong for households that want full local control with no vendor cloud dependency.

For a domestic customer wanting a smart CU because of an EV-plus-heat-pump supply constraint, a mainstream manufacturer with a smart range is the lowest-risk specification — TTA status is unambiguous, wholesalers supply spares, and any electrician can work on it later.

Replacing a consumer unit is notifiable work in a dwelling in England and Wales under Building Regulations Part P, whether traditional or smart. Notification is via registered competent person scheme (NICEIC, NAPIT, ELECSA, Stroma) or a Building Control notice.

Two trends are likely to drive smart CU specification over the next two to three years. ISO 15118-20 is the next-generation vehicle-to-grid communication standard, extending ISO 15118 to bidirectional energy flow and richer flexibility messaging between EV, charger and grid. FlexiOrb is the National Grid ESO's evolving flexibility-signal scheme that lets half-hourly demand-side flexibility signals reach connected devices in the home.

For 2026 installations, specify a smart CU from a vendor that has published a roadmap for ISO 15118-20 and Matter, supports the Octopus API, and commits in writing to a multi-year firmware support period.