Thinking Spaces
Visit our demonstration home ↗

BEHIND YOUR THINKING SPACE

Personal on the surface.
Powerful underneath.

Home Assistant connects your home. Your Home AI agent helps shape its life routines. MCP connects the conversation to the tools that make changes possible.

YOU DESCRIBEHow you want to live
YOUR AI ASSISTANTChatGPT or Claude
THE CONNECTIONMCP tools
AT HOMEHome Assistant
& your devices

Conversation shapes the life routine. Home Assistant runs it when the relevant conditions arise.

01 / THE FOUNDATION

Why we build on
Home Assistant.

For the homes we design, we believe Home Assistant offers the strongest foundation: broad integration, local control and the freedom to shape behaviour around the household.

Meet Home Assistant ↗
01

Your devices can share a bigger picture.

Home Assistant is an open-source home automation platform running on a computer in your home. Integrations bring supported lights, sensors, blinds, aircon and other equipment into one system. A sensor from one brand can inform an action by another.

02

Life routines can have nuance.

Triggers, conditions and actions let us combine occupancy, temperature, time and device state. We can design exceptions and manual overrides, so a life routine responds appropriately instead of repeating the same action regardless of circumstances.

How automation conditions work ↗
03

Keep everyday decisions close to home.

Supported local devices and life routines can operate without internet while power and the local network remain available. Cloud-only equipment, remote services and cloud AI still need an internet connection.

Local operation explained ↗
04

Room to grow, with controls that fit.

Personal dashboards bring each person’s useful controls into view. Open software and a broad integration community give us options as your home changes. Compatibility, updates and maintenance still matter; we design and support the foundation.

Explore dashboards ↗

FROM INTENTION TO A LIFE ROUTINE

“Keep the living room
comfortable on hot afternoons.”

We help turn that intention into behaviour that fits your home. A light on a timer follows a schedule. A life routine considers relevant conditions, your preferences and exceptions.

  1. NOTICESunlight and room temperature reach the agreed conditions.
  2. CONSIDERCheck whether someone is home and whether the room is being used.
  3. RESPONDCoordinate compatible blinds and cooling.
  4. RESPECTLeave a manual adjustment alone until the agreed reset point.

Illustrative life routine. Sensors, thresholds, operating limits and override behaviour are agreed for your installation.

02 / THE CONNECTION

What is MCP?

A common language between your AI assistant and the tools it is allowed to use.

MCP stands for Model Context Protocol. It is an open standard that lets AI applications discover and use tools supplied by a connected server. It is a connection protocol, rather than an AI model or a home automation engine.

In a Thinking Spaces setup, a locally hosted MCP server connects your Home AI agent to configured Home Assistant tools. Depending on the agreed access, the agent can inspect relevant devices, help create or edit life routines, personalise dashboards and investigate supported problems.

The tools determine what is possible. Connecting an assistant to MCP alone does not automatically give it automation-editing or dashboard-design capabilities. We configure the required tools, permissions, validation, backups and recoverable changes as part of your installation.

About the MCP standard ↗Home Assistant and MCP ↗

03 / YOUR CONVERSATION

The assistant you enjoy.
A home it can help you shape.

ChatGPT or Claude can become the conversational interface to your configured home tools. We confirm the supported connection and account requirements with you.

OpenAI

ChatGPT

Use a supported custom MCP connection to bring permitted home tools into your conversation. Available tools, account features and approval behaviour depend on your ChatGPT setup.

OpenAI connection documentation ↗
Anthropic

Claude

Connect through a supported MCP connector. Remote connectors reach your server from Anthropic’s cloud; local desktop connections are a separate option with different requirements.

Claude connection documentation ↗

MORE THAN AN IMMEDIATE COMMAND

“We’re working from home on Fridays now. Keep the study comfortable, but don’t cool the rest of the house just for us.”

Your agent can clarify the details and implement supported changes through its configured tools. Once established, Home Assistant runs the life routine. You don’t need to leave the conversation open, or ask an AI model to decide every time a device switches on.

Cloud AI needs internet access and may receive relevant requests and home information. We explain data flows, remote access and any subscriptions before setup. A local home server does not mean the AI conversation stays entirely local.

FAMILIAR BRANDS. A MORE CONNECTED HOME.

Bring the things you love
into your thinking space.

A curated starting point across lighting, comfort, appliances, entertainment, security and energy. Open a logo to see the connection route and what we check.

We choose the connection as carefully as the device.

We favour local integrations and documented account-linking routes that do not normally require repeated manual token replacement. Automatic token renewal is normal. No integration is a promise of zero maintenance, and a logo does not mean every product or feature is supported.

29 connections · choose a logo for details

AutomateLocal · Core / HACSConnection details

Rollease Acmeda motorised shades and blinds connected to an Automate Pulse hub.

Pulse v1 uses the core Acmeda integration; Pulse v2 uses the Automate Pulse v2 HACS integration. Both communicate locally, without cloud token renewal. Reserve a stable hub address and check firmware, radio coverage and motor features.

Integration documentation ↗
LG · AppliancesCloud · Core LG ThinQConnection details

Supported ThinQ washers, dryers, dishwashers, fridges, ovens and other connected appliances.

Uses LG’s official ThinQ Connect API with a personal access token configured at setup. We check token validity, account region and the exact model. Available controls vary; remote start must be enabled where required.

Integration documentation ↗
Samsung · AppliancesCloud · Core SmartThingsConnection details

Supported SmartThings-connected washers, dryers, fridges, dishwashers and cooking appliances.

Use the current account-linking integration with automatic token renewal, rather than manually replacing short-lived tokens. Samsung has announced a paid API transition from October 2026; we confirm current plan requirements. Features vary by model.

Integration documentation ↗
BoschCloud · Core Home ConnectConnection details

Selected Home Connect-enabled dishwashers, laundry appliances, ovens, fridges and coffee machines.

Official Home Connect account authorisation uses automatic token renewal. A developer application is configured during setup. Available controls and remote-start requirements depend on the appliance.

Integration documentation ↗
SiemensCloud · Core Home ConnectConnection details

Selected Home Connect-enabled kitchen and laundry appliances.

Uses the same official Home Connect integration and automatic token renewal. We confirm model support, available programmes and whether remote operation must first be enabled on the appliance.

Integration documentation ↗
MieleCloud · Core MieleConnection details

Supported Miele@home-connected washing machines, dryers, dishwashers, ovens, fridges and other appliances.

Official account authorisation uses automatic token renewal. Features exposed to Home Assistant can differ from the Miele app; many appliances require Mobile start or remote control to be enabled.

Integration documentation ↗
Philips HueLocal · Core HueConnection details

Bridge-connected lights, switches and sensors.

Pair the Hue Bridge locally. Prefer the native Hue integration for richer features than Matter.

Integration documentation ↗
AqaraLocal · Core Matter / HomeKitConnection details

Selected Matter devices and supported HomeKit accessories.

Choose the exact model and exposed features. Matter over Thread needs a suitable Thread border router; selected Zigbee products are another route.

Integration documentation ↗
IKEALocal · Core TRÅDFRI / MatterConnection details

Compatible lighting, plugs, blinds and sensors.

TRÅDFRI uses a local gateway key. DIRIGERA uses Matter or HomeKit Device; bridge routes expose different features.

Integration documentation ↗
SONOFFLocal · Core ZHAConnection details

Selected Zigbee sensors, switches and plugs.

Pair supported Zigbee models to a compatible coordinator. This shortlist does not make a claim about all eWeLink Wi-Fi devices.

Integration documentation ↗
ShellyLocal · Core ShellyConnection details

Supported relays, dimmers, plugs and meters.

Home Assistant talks directly to supported devices. BLU accessories can require a different Bluetooth integration.

Integration documentation ↗
TP-Link · Tapo & KasaLocal · Core TP-LinkConnection details

Supported plugs, lights, switches and selected cameras.

Check hardware and firmware against the supported list. Account credentials or local camera credentials may be needed; local control is not the same as account-free setup.

Integration documentation ↗
LIFXLocal · Core LIFXConnection details

Compatible Wi-Fi lighting.

Uses the local network rather than the LIFX cloud for control. Model and network discovery checks still apply.

Integration documentation ↗
NanoleafLocal · Core Nanoleaf / MatterConnection details

Panels, Canvas, Shapes, Elements and Lines.

The native integration covers panels. Essentials use a different Matter or HomeKit route depending on generation.

Integration documentation ↗
SwitchBotLocal · Core Bluetooth / MatterConnection details

Selected Bots, Curtains, sensors and supported hub-bridged devices.

Bluetooth range or a proxy matters. Some encrypted devices need keys; a compatible Matter bridge exposes a subset of features.

Integration documentation ↗
AirTouch 5Local · Core AirTouch 5Connection details

Ducted-aircon units and zones controlled by AirTouch 5.

Connect to the controller locally. Respect the aircon system’s own zone and damper operating constraints.

Integration documentation ↗
Advantage AirLocal · Core Advantage AirConnection details

Supported MyAir / MyPlace, e-zone and zone10e controllers.

The wall tablet stays part of the system and needs a stable network address. Available controls depend on the installation.

Integration documentation ↗
BondLocal · Core BondConnection details

Compatible RF fans and shades via a Bond Bridge.

Uses a local access token. One-way RF equipment may report an assumed state rather than confirmed position.

Integration documentation ↗
SonosLocal · Core SonosConnection details

Supported network speakers and grouped playback.

Local speaker control; streaming services can still need internet and their own subscriptions. UPnP must be enabled.

Integration documentation ↗
SamsungLocal · Core Samsung TVConnection details

Supported network-connected televisions.

Approve local pairing on the TV. Wake-up support depends on the model, settings and network; this is not a whole-brand SmartThings claim.

Integration documentation ↗
LGLocal · Core webOS TVConnection details

Supported LG webOS televisions.

Pair with the television locally. Power-on can require Wake-on-LAN or another configured action.

Integration documentation ↗
DenonLocal · Core Denon AVRConnection details

Compatible network AV receivers.

Uses the receiver’s local network interface. Features and standby control vary by model.

Integration documentation ↗
YamahaLocal · Core MusicCastConnection details

Compatible MusicCast receivers, soundbars and speakers.

Local control on the home network. Online music services retain their own internet requirements.

Integration documentation ↗
ReolinkLocal · Core ReolinkConnection details

Supported cameras, doorbells, NVRs and hubs.

Configure local device access. Some battery cameras need a compatible Reolink hub or NVR; not every camera connects directly.

Integration documentation ↗
UniFi ProtectLocal · Core UniFi ProtectConnection details

Cameras, doorbells and supported sensors on a UniFi OS console.

Requires a supported Protect installation and local API access. Stable software releases are preferred over early-access versions.

Integration documentation ↗
FroniusLocal · Core FroniusConnection details

Compatible inverter, meter and energy readings.

Enable the local Solar API where needed. Monitoring via Solar API is distinct from changing inverter settings.

Integration documentation ↗
Apple HomeLocal bridge · Core HomeKit BridgeConnection details

Expose supported Home Assistant controls to Apple Home and Siri.

This sends supported controls into Apple Home; it does not import every Apple device. Remote access depends on the Apple home setup.

Integration documentation ↗
Google NestCloud · Core Nest; local Cast for speakersConnection details

Selected SDM-supported thermostats, cameras and doorbells; Cast for supported speakers/displays.

Nest needs Google Device Access setup and a fee. Set OAuth to Production to avoid seven-day expiry. Tokens normally renew automatically; revocation can still require sign-in. Nest Protect is not covered by the SDM route.

Integration documentation ↗
Amazon AlexaCloud · Home Assistant CloudConnection details

Use Alexa voice commands with exposed Home Assistant devices.

Our preferred voice route uses Nabu Casa account linking. This is different from importing Echo devices or media controls; those separate integrations have their own login and service limitations.

Integration documentation ↗

Research reviewed 13 October 2026. Inclusion reflects documented integration routes, not a claim that we have tested every model. Logos identify their respective brands; they do not imply a Thinking Spaces partnership or endorsement.

HOW WE CHOOSE

Compatibility should
make life easier.

Core first. Community where it adds value.

Core integrations ship with Home Assistant. HACS—the Home Assistant Community Store—helps install community-maintained integrations and dashboard components. We consider both, checking maintenance, permissions and the authentication method before selecting a route. A HACS listing alone is not a quality guarantee.

The shortlist includes core integrations, Home Assistant Cloud voice control and the local Automate Pulse v2 community integration. We assess each connection for your project rather than giving an entire brand a blanket recommendation.

About HACS ↗

Nest and Alexa deserve a little explanation.

Nest’s official integration uses Google’s cloud. Correct OAuth configuration avoids the seven-day expiry associated with Testing mode. Alexa voice control through Home Assistant Cloud is different from using an unofficial media-player integration to import Echo devices. We keep those distinctions clear when designing your setup.

Appliances can take part in life routines, too.

A supported washer can let the home know when a cycle ends, so a life routine can notify someone who is home without interrupting quiet time. Connected appliances usually depend on their manufacturer’s cloud. We check account requirements, exposed features and any remote-start setting before promising a particular behaviour.

The exact model matters.

We check your model, firmware, region, available controls and any hub requirements. A camera feed is different from a motion event; switching an aircon on is different from controlling each zone. We choose the capabilities your life routines actually need.

A LITTLE MORE CLARITY

Powerful, without
the homework.

Do I need to learn Home Assistant, MCP or code?

No. We handle the setup and show you how to use your controls and Home AI agent. You describe supported changes in everyday language.

Does every brand need its own hub?

No. Some devices connect directly; others need a bridge or radio. We choose what your particular devices and home need.

Can I still use Apple Home, Alexa or physical switches?

Yes, with compatible equipment. We can keep familiar controls alongside life routines. We confirm which features will work before installation.

Will my life routines keep working if I stop using the AI assistant?

Yes. Home Assistant runs the life routines already set up. They still need their required devices, power, network and any cloud services. AI is needed when you want its help making changes.

My brand isn’t listed. Can you still help?

Send us the model and what you want it to do. We’ll check whether there’s a reliable way to connect it.

Let’s connect the possibilities.

Tell us what you already own and how you want your home to behave.

Your cookie choices

We use Google Analytics and Google Ads to understand visits and promote Thinking Spaces. These services receive visitor information. Your location determines the default; your saved choices take priority. Change them any time using Privacy & cookie choices in the footer.

Withdrawing an active permission reloads this page to stop tracking. Any unsaved form entries may be lost.

Read our privacy policy