ctrlspace
// The platform every CtrlSpace system runs on

Home Assistant

Open-source home automation that runs on hardware in your home, integrates with well over two thousand systems, and belongs to you rather than to a vendor. It is the foundation of every system we build, and the reason we can say yes to almost any brand.

Why we use Home Assistant

  • It runs locally. Automations, dashboards and device control all continue through an internet outage.
  • The integration catalogue is vastly larger than any commercial platform, which is what lets us mix brands instead of forcing a single ecosystem.
  • No subscription, no licence, no per-device fee, and no vendor who can reprice a feature you already paid for.
  • Full administrative access is handed to the client. If you replace us, nothing stops working.
  • Everything is exportable and backed up, so the configuration survives a hardware failure or a move.

Where we do not, and why

  • It is a system, not an appliance. Left unmaintained it drifts - updates go unread, batteries die unnoticed and backups stop.
  • The setup quality determines everything. A badly built Home Assistant is worse than a well-built closed ecosystem.
  • It releases monthly and occasionally makes breaking changes. That is manageable with discipline and painful without it.

Pros and cons at a glance

Pros
  • Local control and local data by default
  • Over two thousand integrations, including nearly everything sold in Singapore
  • Automations with real conditions, not just triggers
  • Runs on modest hardware and can be moved between machines from a backup
  • Exposes your devices to Siri, Alexa and Google, so voice still works
Cons
  • Needs to be designed, installed and maintained properly
  • Frequent releases mean updates must be read rather than clicked through
  • Not something most households want to run themselves
  • Some vendor-cloud devices remain cloud-dependent no matter what the platform does

The technical position

Runs on
Mini PC, Home Assistant Green or Yellow, or a server you already own
Local control
Yes, by design
Cloud dependency
None for local devices. Optional remote access via Nabu Casa or your own tunnel
Cost
Free and open source. You pay for hardware and for the work
Radios
Zigbee, Thread, Z-Wave, Matter, Bluetooth and Wi-Fi, via add-on coordinators

Where it fits in a CtrlSpace build

Every CtrlSpace project runs on it. The hub goes into the store room, the TV console or a small rack, with a Zigbee or Thread coordinator on a short USB extension and a UPS behind it. What varies between projects is the hardware tier and how much radio coverage the property needs, not the platform.

// Frequently asked

Home Assistant, answered plainly

Is Home Assistant free?

The software is free and open source. What costs money is the hardware and either your time or a professional to design, install and maintain it. There is no licence fee or subscription for local use.

What happens to my system if CtrlSpace disappears?

Nothing. You hold full administrative access, the hub is in your home, and the software is open source. That is the point of building on it.
// 4 more in this category

See others in platforms and hubs

Ecosystem Apple Home HomeKit as a control layer, not a foundation Ecosystem Google Home The best voice, on a cloud foundation Ecosystem Amazon Alexa Wide device support, same cloud problem Multi-protocol hub Samsung SmartThings The most capable closed hub, with a history of rewrites

Not sure what belongs in your home?

We do not sell hardware or carry brands. Bring your list to a design session and we will tell you what is worth buying, what you already own that can stay, and what to skip.

Book a design session See every brand