Smart Home System Specification: Single-Vendor vs Multi-Protocol, Scalability and How to Quote for Ongoing Maintenance
Quick Answer: A smart-home specification should start with the user's actual needs and budget, not the technology. Decide whether to go single-vendor (Lutron, Crestron, Control4, Loxone, KNX with one manufacturer) for tight integration and simpler support, or multi-protocol (Hubitat, Home Assistant) for flexibility and lower cost. Scalability comes from designing the network and infrastructure for headroom (extra circuits, network ports, hub capacity), not buying every device upfront. Maintenance contracts typically run 1-3% of installed value annually, covering firmware updates, fault calls and refresh planning — quote for this at outset rather than as an afterthought.
Summary
Smart-home specification is the document that turns a client's wishes into a buildable, costable project. It sits between the brief ("I want voice control of everything") and the detailed design ("install Lutron QSWE-1RLD here, here and here"). A good specification:
- States the intent in plain English
- Lists what is in scope and what isn't
- Identifies which systems and protocols will be used
- Defines the integration architecture
- Sizes the network, electrical and other infrastructure
- Sets out commissioning and handover deliverables
- Quotes the budget transparently
- Plans for ongoing maintenance and lifecycle
Most failed smart-home projects have a specification gap somewhere — usually in scope (everyone assumed something was in / out and they disagreed), integration (devices that don't actually talk to each other), or budget (the "small extras" added up). This article covers the specification process and the trade-offs that shape it.
Key Facts
- Single-vendor — Lutron, Crestron, Control4, Loxone, KNX (sort of); tight integration, single point of support
- Multi-protocol hub-based — Hubitat, Home Assistant, SmartThings; mix-and-match flexibility
- Cost ratio — single-vendor typically 2-4x equivalent multi-protocol pricing
- Project phases — Brief → Specification → Design → Procurement → Installation → Commissioning → Handover → Maintenance
- RIBA stages — for new build: Stage 2 (Concept) often involves smart home; Stage 3 (Spatial coordination) defines spec
- CIBSE TM57 — Integrated School Design has lessons applicable to multi-disciplinary residential
- CEDIA Recommended Practice — published guidelines for residential design and documentation
- Scope categories — lighting, heating, audio, video, security, networking, energy, climate
- Network as backbone — every modern smart home depends on robust network infrastructure
- Power as backbone — circuits, redundant supply for critical systems
- Documentation as deliverable — as-builts, O&M, training are deliverables, not afterthoughts
- Maintenance contracts — 1-3% of installed value annually
- Refresh cycles — active devices 5-7 years, infrastructure 15-25 years
- Headroom — design for 25-50% spare capacity (network ports, breaker ways, controller channels)
Quick Reference Table
Spending too long on quotes? squote turns a 2-minute voice recording into a professional quote.
Try squote free →| Project Size | Typical Architecture | Typical Cost Range |
|---|---|---|
| Smart heating only | Tado / Drayton Wiser; integrate via app | £500-£2,000 |
| Lighting + heating | Hubitat / Home Assistant; Hue + Tado | £3,000-£8,000 |
| Lighting + heating + audio + cameras | Hubitat / HA + Sonos + UniFi Protect | £10,000-£25,000 |
| Whole-house automation (medium) | Lutron RA2 + Sonos + Hubitat overlay | £25,000-£60,000 |
| Whole-house automation (large) | KNX + cinema + multi-zone | £60,000-£150,000 |
| Premium / luxury | Crestron / Control4 / Loxone | £150,000-£500,000+ |
| Single-Vendor System | Strengths | Weaknesses |
|---|---|---|
| Lutron RA2 / HomeWorks | Best-in-class lighting; reliable; long support | Lighting-focused; less flexible for other systems |
| Crestron | Premium AV + automation; powerful | Very expensive; vendor lock-in |
| Control4 | Mid-premium AV + automation; strong dealer network | Annual support fees; closed ecosystem |
| Loxone | Strong residential automation; good dashboard | Smaller third-party support |
| KNX (multi-vendor) | Open standard; longevity; interoperable | Complex; high install cost |
| Multi-Protocol Hub | Strengths | Weaknesses |
|---|---|---|
| Hubitat Elevation | Local processing; affordable; powerful rules | Smaller community than HA |
| Home Assistant | Open source; massive integrations; flexible | Steeper learning curve |
| SmartThings | Easy setup; broad device support | Cloud-dependent; consumer-grade |
| Aeotec Hub | UK-friendly; Matter-compatible | Newer platform |
Detailed Guidance
The brief — what does the client actually want?
Every spec starts with an interview. Common areas to cover:
Lifestyle:
- Family composition; occupancy patterns
- Daily routines (wake, work, sleep)
- Entertainment preferences (movies, music, gaming)
- Cooking and dining patterns
- Home working / school
Pain points:
- "I always forget to turn the heating off"
- "My son's bedroom is too cold"
- "I can't ever find the right TV remote"
- "We can't hear the doorbell from the garden"
Aspirations:
- "I want it to be like a hotel"
- "I want to control everything from one app"
- "I want my house to recognise when I come home"
Constraints:
- Budget — actual figure, not "what does it cost?"
- Listed building / heritage — restricts wiring
- Existing systems to retain or integrate
- Time — when does it need to work?
Technical preferences:
- Apple, Google or Amazon ecosystem?
- Privacy concerns?
- Voice control desired or unwanted?
- Local control vs cloud-acceptable?
Single-vendor vs multi-protocol
Single-vendor pros:
- Tight integration — features work together because designed together
- Single point of support — one company, one help line
- Polished user experience — apps and remotes feel coherent
- Long-term commitment — large companies invest in product line
Single-vendor cons:
- Lock-in — switching means replacing everything
- Cost premium — proprietary hardware costs more
- Limited innovation — innovation comes from one company's roadmap
- Scope limits — vendor may not cover everything (e.g. Lutron is lighting-led)
Multi-protocol pros:
- Best-in-class per category — best lighting, best heating, best audio, integrated
- Lower cost — competitive pricing across categories
- Flexibility — swap out individual components without redoing everything
- Innovation — benefit from rapid changes in any category
Multi-protocol cons:
- Integration complexity — making different systems talk requires effort
- Multiple support lines — when something fails, who do you call?
- Documentation overhead — more diagrams, more credentials
- User experience consistency — different apps, different remotes
For a typical UK residential project under £50,000 the multi-protocol approach (Hubitat or Home Assistant as hub) is usually right. Above £100,000, single-vendor (Crestron, Control4, KNX) with a strong lead integrator typically delivers better results.
Scalability — design for headroom
Common scaling errors:
- Patch panel with 24 ports, 24 cables run; no spare for future
- 8-way consumer unit with 2 spare ways; not enough for EV + battery + new circuits
- Hub maxed at device limit; no headroom for growth
- Network UPS sized for current load with no headroom
Best practice:
- Network: 25-50% spare ports
- Electrical: 30-50% spare ways in consumer unit
- Hub capacity: limit at 60-70% of theoretical maximum
- Cable conduits: 30-50% spare capacity for future cable pulls
- Cabinet space: 30% spare U for future equipment
The marginal cost of these spares at install time is small. The cost of running new cables or changing equipment 3 years later is enormous.
Integration architecture
A typical multi-protocol architecture:
Internet
│
┌────────┐
│ Router │
└────┬───┘
│
┌──────────────┼──────────────┐
│ │ │
Switch (PoE) APs (Wi-Fi) Cabling to rooms
│
┌────┼────────────────────────┐
│ │ │
NVR Hub (Hubitat) AVR / Sonos
│
┌────┴────┐
Z-Wave Zigbee
mesh mesh
│
Devices: lights, sensors, locks, plugs
The hub is the integration point. Devices in different protocols are presented unified to the user. Voice control, mobile apps and rules all flow through the hub.
Quoting for the project
A good quote separates:
Hardware:
- Itemised by system (lighting, audio, networking, etc.)
- Models and quantities listed
- Manufacturer warranties stated
Installation labour:
- Day rates and estimated days
- Travel charges if applicable
- Out-of-hours work surcharges
Programming and commissioning:
- Hours estimated for system programming
- Calibration costs
- Training time
Documentation:
- As-built drawings
- O&M manual
- User guides
Project management:
- Site visits, coordination
- Liaison with other trades
- Procurement administration
Contingency:
- 5-10% of total for typical project
- 10-15% for retrofit or listed building
Total cost transparency builds trust. Hidden charges or "items extra" surprises destroy it.
Quoting for ongoing maintenance
Maintenance is often the most-skipped part of the quote — and often the source of the most friction post-handover. Quote it explicitly at outset.
Tier 1 — Reactive only:
- Free at handover
- Calls billed hourly + travel
- Average annual cost £500-£2,000 depending on system
Tier 2 — Annual visit:
- Fixed annual fee (typically 1-1.5% of system value)
- One scheduled visit per year
- Firmware updates, battery replacements, performance check
- Minor adjustments included
- Faults billed separately at member rate
Tier 3 — Comprehensive support:
- Fixed annual fee (2-3% of system value)
- All Tier 2 plus:
- Remote support (capped hours/month)
- Priority response (24-48 hours)
- Software updates, minor reconfigurations included
- Hardware replacement labour included (parts at cost)
The recommended tier depends on the system complexity and the client's technical comfort. Larger systems with more devices (and therefore more failure modes) benefit most from Tier 2/3.
Lifecycle planning
A 10-year lifecycle plan for a typical premium install:
- Year 0 — Install, commissioning
- Year 1 — First annual visit; minor adjustments
- Year 2 — Battery replacements (sensors, remotes); second annual visit
- Year 3 — Firmware refresh; review device end-of-life
- Year 4 — Major battery replacements; consider hub firmware upgrade
- Year 5 — Hub refresh consideration; Wi-Fi standards may have advanced
- Year 6 — Replace ageing IoT devices (cameras particularly); refresh networking
- Year 7-10 — Progressive renewal; major refresh or rebuild around year 8-10
Communicating this to the client at outset reduces the shock of "everything's broken" 7 years in. The client knows what to budget for.
Working with other trades
A smart-home install almost always sits within or alongside other works:
Builder / main contractor:
- Coordinate first-fix cabling before walls closed
- Backboxes, conduit, cable routes
- Access for in-wall and in-ceiling speakers, switches
Electrician:
- Mains circuits as designed
- Consumer unit work
- Notifiable Part P sign-offs
Plumber / heating engineer:
- Boiler / heat pump terminal access
- Manifold connections for UFH
- Cylinder thermostat positions
Joiner:
- Cabinetry around AV racks, panels
- Recess detail for in-wall touch panels
Decorator:
- After first-fix, before second-fix
- Avoid painting backboxes shut
Landscape:
- External speaker positions
- Outdoor camera positions
- Garden lighting circuits
The smart-home spec should call out interfaces with each trade clearly — what's being delivered to/by whom, and when in the programme.
Documentation deliverables
The spec should explicitly state what documentation will be delivered:
- As-built drawings (PDF + editable source)
- Network diagram (physical and logical)
- Equipment list with serial numbers
- Cabling schedule
- Programming files (ETS, Crestron projects, Hubitat backups)
- O&M manual
- User quick-start guide
- Training video (if recorded)
- Warranty documents
- Building Regulations certificates
If the spec doesn't state what documentation is delivered, scope ambiguity creeps in and clients end up with insufficient records.
Insurance and warranty considerations
Larger smart-home projects involve significant risk:
- Public liability — typically £2-£10m cover
- Professional indemnity (designers) — £500k-£2m cover
- Product warranty — manufacturer-specific, transferred to client
- Insurance-Backed Guarantee — for projects with significant integrated systems (rare for pure smart home; common for waterproofing-attached works)
- Plant insurance (during install) — covers tools and equipment on site
For projects above ~£25k, building this into the contract and quote is appropriate. Below that, standard public liability and household insurance typically suffice.
Frequently Asked Questions
How long does a typical smart-home project take?
For a single-system install (smart heating, smart lighting): 1-3 days. For multi-system (lighting + heating + audio): 1-2 weeks. For whole-house automation with cinema: 4-12 weeks for active works, with project schedule running 4-9 months including procurement and commissioning. Larger projects (>£100k) typically run 6-18 months.
What's the difference between Crestron, Control4 and Loxone?
Crestron is the premium tier — used in luxury residential and commercial. Maximum flexibility, maximum cost, requires Crestron-certified programmer. Control4 is upper-mid; closed dealer network, annual support fee, polished but less flexible. Loxone is European mid-market; strong residential focus; good dashboard; less third-party AV integration than Control4 / Crestron.
Should I include the network in the smart-home quote?
Yes — almost always. The network is the foundation; the smart-home installer's reputation hangs on it. Quoting for cabling, switches, access points and configuration as part of the smart-home scope means you control quality of the foundation. Carving out network to a separate IT contractor often results in mismatched expectations and finger-pointing.
What's a reasonable contingency to quote?
For new build with clear specification: 5%. For retrofit in occupied home: 10%. For retrofit in listed / heritage building: 15-20%. Contingency covers genuine unknowns (cable routes that don't work, devices that don't perform as expected, additional work uncovered during installation). It is not a buffer for poor specification.
How do I avoid scope creep?
Define scope clearly, document it, get sign-off, and quote variations explicitly. A typical change order process: (1) client requests change, (2) installer prices the change in writing, (3) client signs off, (4) work proceeds. Verbal "while you're there" requests are the start of disputes — document everything.
Regulations & Standards
CDM 2015 — Construction (Design and Management) Regulations
Building Regulations Parts A, B, C, F, K, L, P — All potentially relevant
BS 7671:2018+A2:2022 — Wiring Regulations
CEDIA Recommended Practices — Industry-standard documentation guidelines
PSTI Act 2024 — IoT product compliance
GDPR / DPA 2018 — Personal data through smart devices
CIBSE TM57 — Lessons from integrated school design applicable to multi-disciplinary residential
RIBA Plan of Work 2020 — Stage definitions for new build
JCT contracts — typical UK contract framework for residential works
NEC4 — Alternative contract framework
CEDIA Recommended Practices — Project documentation standards
CIBSE TM57 — Integrated School Design — Cross-disciplinary lessons
RIBA Plan of Work — Project stage framework
Lutron RA2 specification guide — Single-vendor lighting reference
Crestron residential portfolio — Premium single-vendor reference
Hubitat Community — Multi-protocol hub examples
cedia membership smart home — CEDIA-aligned design and documentation
smart home commissioning handover — Handover deliverables aligned with spec
home networking for av — Network specification within whole spec
iot device cybersecurity — Security at specification stage
voice control integration — Voice ecosystem decisions in spec