10 Mistakes to Avoid Before Installing a Smart Home

The expensive smart home failures we are asked to rescue share a pattern: the fatal decisions were made months before any equipment arrived – in the wiring specification, the programme sequencing, and the choices nobody made because nobody was asked. This guide sets out the ten mistakes we see most often on high-end residential projects, why each one happens, what it genuinely costs, and the professional practice that prevents it. If you are earlier than second fix, every one of these is still avoidable.

1. Choosing products before defining requirements

The most common mistake is starting with a brand – a platform seen in a friend's house or a showroom – and working backwards. It happens because products are tangible and requirements documents are not. The consequence is a system shaped by what the chosen product does rather than what the household needs, discovered only in occupation: the scene logic that cannot express how the family actually lives, the staff workflow the platform was never asked about. The professional solution is unglamorous: a written requirements document covering rooms, subsystems, users, scenes and expansion intent, agreed before any platform is named. Our platform decision guide assumes exactly this sequence: requirements first, brand second.

2. Choosing purely on price

Three integrator quotations are rarely for the same thing. The lowest number usually omits what does not show in a demo: engineered drawings, network segmentation, commissioning time, documentation, training and post-completion support. It happens because clients – and, more often, main contractors under cost pressure – compare bottom lines rather than scope. The real cost arrives over the following decade as change requests, callouts and eventually re-engineering; we quantify these failure modes in The Hidden Costs of Choosing the Wrong Smart Home Platform. The solution is a levelled comparison: require every bidder to price the same specification, with documentation and commissioning as explicit line items.

3. Under-specifying the cabling infrastructure

Cable is the cheapest component of the entire project while the walls are open and the most expensive once they are closed. The mistake takes several forms: too few data points, Cat5e where Cat6A belongs, no containment spare capacity, lighting wired conventionally with no neutral or bus provision, shading pockets without power. It happens because first fix is priced by electricians before the technology design exists. Professional practice runs the opposite way: a structured cabling design – typically two to four Cat6A points to every TV, AP and desk position, home-run to the rack, with 25–40% spare containment capacity – issued before first fix, coordinated with the electrical design. The full specification logic is set out in How to Future-Proof a Prime Home Automation System.

4. Treating Wi-Fi as an afterthought

A single router in a plant cupboard cannot serve a 600m² masonry house, yet that is what an unplanned project delivers. Poor Wi-Fi is experienced as "the smart home not working" even when the control system itself is wired and healthy – the apps, streaming and voice interfaces all live on the wireless layer. The engineering answer is a designed wireless network: ceiling-mounted access points on wired PoE backhaul, positioned against a predictive survey of the actual fabric (masonry, foil-backed insulation and low-e glazing are radio obstacles), with controller-managed roaming. We cover the design method – and why coverage is the wrong goal – in Prime Residential Wi-Fi Design.

5. No rack, no plant space, no ventilation

Integrated systems need a physical home: a ventilated equipment rack with clean power, on a dedicated circuit, with working clearance and thermal management. The mistake is discovering this at second fix, when the only remaining space is an unventilated understairs cupboard – where electronics cook, fans whine through the snug wall, and every service visit becomes archaeology. Heat is the quiet killer of AV and network equipment: sustained high temperature shortens electronic life substantially, which is why rack cooling is an engineering calculation, not an accessory. The solution costs nothing if made at design stage: allocate the space on the architect's plans, size the rack with 30% spare capacity, and treat its power, cooling and containment as part of the MEP design.

6. Excluding the smart home from the electrical design

Lighting control changes the electrical design fundamentally – panelised dimming relocates circuits to central positions, keypads replace banks of switches, DALI needs its own wiring topology, and the distribution boards need space, ways and surge protection accordingly. When the electrical package is designed and priced without the control system, the result is abortive work: circuits rewired, boards replaced, walls reopened. Coordination also has a compliance dimension – the installation must be certified against BS 7671 as designed, not patched afterwards; see our guide to electrical certification every developer should understand. The solution is sequencing: the automation designer issues load schedules and wiring topologies to the electrical engineer before the electrical package is tendered.

7. Ignoring HVAC, shading and the physical building

A control system can only command what was installed to be commanded. If the VRF system was procured without an integration gateway, if the MVHR unit has no control interface, if the windows have no pockets, power or fixings for shading – then "we'll integrate it later" means builders' work, not programming. This mistake happens because HVAC, glazing and automation are procured in separate packages by teams who never meet. The solution is a coordination pass at design stage: every mechanical and shading item that will ever be controlled is specified with its control interface (BACnet, Modbus, dry contact, or native driver) and its wiring provision, before procurement.

8. No BIM or spatial coordination

On a serious project the automation infrastructure – containment routes, rack space, ceiling devices, floor boxes – competes for the same voids as ductwork, pipework and structure. Left uncoordinated, technology loses: the AP lands behind a beam, the shading pocket clashes with a sprinkler run, the rack's cooling duct has nowhere to go. Bringing the technology package into the federated BIM model catches these collisions while they cost nothing to move; we set out the method in BIM Coordination for MEP: How Clash Detection Saves Projects. On projects without full BIM, the minimum is overlay drawings reviewed jointly by the MEP and technology designers before first fix.

9. Treating commissioning as "setup"

Commissioning is an engineered phase with deliverables: every load tested against its schedule, every scene walked through with the client, network documented and security-hardened, integrations exercised across their failure modes, snags recorded and cleared. The mistake – compressing it into the final chaotic week alongside decorators and snagging – happens because commissioning sits last in the programme and absorbs everyone else's delay. The result is a system that is 90% right, which in daily life reads as unreliable. The solution is contractual: a defined commissioning period protected in the programme, a witnessed demonstration against the requirements document, and handover documentation as a condition of final payment – the same Soft Landings discipline applied to any other building service.

10. No documentation, no maintenance plan, no exit strategy

The project ends; the ownership begins. Without as-built drawings, load schedules, programme files, credentials and a service agreement, the home is hostage to one person's memory – and people retire, sell up and disappear. This mistake is invisible for years, then suddenly very expensive. The professional standard: a documentation set deposited with the client at practical completion (drawings, schedules, code, credentials, licences), a maintenance agreement covering firmware, monitoring and response times, and cybersecurity housekeeping – the UK's product security regime now sets baseline expectations for connected devices, but the network architecture and credential hygiene remain the integrator's responsibility. If a prospective integrator cannot show you a sample handover pack from a previous project, that tells you what yours will look like.

Executive summary

Smart home projects fail in the planning phase: products chosen before requirements, packages priced before designs exist, infrastructure under-specified while it is cheap to install, and commissioning and documentation squeezed out at the end. Every one of the ten mistakes above is prevented by sequence – requirements, then infrastructure design, then coordinated procurement, then protected commissioning, then documented handover. The remedy is not a bigger budget; it is engaging the technology designer at the same stage as the architect and MEP engineer, and holding the delivery to the same documentation standards as every other building service.

Key engineering takeaways

• Requirements before brands; specifications before prices.
• Cable and containment while walls are open – with 25–40% spare – cost a fraction of any retrofit.
• Wi-Fi, rack space, and electrical integration are design tasks, not site improvisations.
• Every controllable device must be procured with its control interface and wiring provision.
• Protect commissioning in the programme and make documentation a condition of final payment.

Decision checklist

1. Is there a written requirements document agreed by the household and design team?
2. Was the structured cabling and containment design issued before first fix was priced?
3. Do the architect's plans show the rack location, with power, cooling and clearance?
4. Has every HVAC, shading and specialist item been specified with its integration interface?
5. Does the contract define commissioning scope, handover documentation and a service agreement?

Further reading

Start with Crestron vs Lutron vs Control4: Which Should You Choose? for the platform decision itself, and How to Future-Proof a Prime Home Automation System for the infrastructure specification in full detail.