Your hubs are the sidebar now, each with a dot that says whether it answers, and every page sits in one panel beside them. The sidebar hides when you want the room.

Your hubs are the sidebar
There is no My Hubs page to go back to: every hub you’ve saved is a row, green while it answers and grey when it doesn’t, and the rows drag into the order you want. Studio opens on the first of them, and a hub on your network that nobody has claimed yet is offered at the foot of the list.

A sidebar that gets out of the way
Hide it with the button beside the traffic lights, View ▸ Hide Sidebar or ⌃⌘S. The page keeps its height while it goes, and Studio remembers how you left it.

A hub’s page starts with the hub
Its name, its address, who you joined as and whether it answers sit in one header over the five tabs, and Overview opens on a row of figures instead of a status card — so the page gets back the room the old header took.

Two ways to set up, side by side
An SD card and a Pi that’s already running are two equal cards, the card first because it asks the least. Once the hub is claimed, the last screen opens it — Return is enough.

A new look rather than new abilities: every tab of a hub’s page does what it did in 1.0.3, and the hub needs no update for it.

Device recognition, the assistant and the automations agent each name the model they run on, and each opens one menu with Claude and GPT side by side. Either agent now runs on either vendor’s key — and your phone asks before anything of yours goes to an AI.

One menu, both vendors
In Home Settings → AI on the phone and on Studio’s AI tab. A vendor you have no key for is listed as needing one, and the lists come from the hub — which moves a home onto a retired model’s successor when it updates, with no app release in between.

Either key writes rules
The automations agent runs on OpenAI now as well as Anthropic, so one key of either kind is enough to talk to the house and to have rules written. OpenAI alone still draws device portraits and carries the voice.

A switch for the part that runs by itself
Device recognition — the one job that spends money without being asked — has a switch of its own, so it can stop without a key being deleted. The assistant and the automations agent carry on.

Asked, not assumed
The first time anything of yours would go to an AI — a message, the microphone, a portrait, a key being saved — the phone says what leaves, where it goes and that we get nothing, with two plain answers. A no is never asked again by itself, and a yes is taken back with one line on the AI page.

What the AI did, all of it
Studio’s run log lists every kind of run — recognising a device, writing a rule, answering something typed or spoken, drawing a portrait, and the meter on a voice call — each with what it cost, how long it took, the model and how it was asked.

Consent is per phone: the keys are the home’s, but what you type, say and photograph is yours, so everybody in the house is asked for themselves.

The hub now pairs a factory-new Matter accessory over its own Bluetooth and hands it your Wi-Fi. Before, it could only take one that was already on a network.

Can the hub hear it?
Before a three-minute wait, the app asks the hub what it can hear and says which problem you have — out of range, or not in pairing mode. Bluetooth only has to reach while pairing, so add it beside the hub and move it wherever you like afterwards.

A pairing that says where it is
It tells you which half it’s in — hold the button, or leave it completely alone — can be cancelled, and always ends. The viewfinder has a torch, zoom and tap-to-focus for codes a few millimetres square, and a mistyped code is caught as you type it.

A network it can actually join
Most accessories only have 2.4 GHz, so the hub never hands one a 5 GHz-only network — the app asks which to use instead — and it tells the accessory which country it’s in, so a router on channel 12 or 13 is one it can see.

Found again, and Thread too
An accessory switched off for days is reached again within minutes of coming back, not whenever the router lets the right broadcast through. Thread accessories behind a border router you already own are reachable as well.

Bluetooth pairing is for Wi-Fi accessories: a factory-new Thread accessory needs a Thread border router, and the hub isn’t one — a Thread device already on yours pairs over the network as before. A WPA3-only network can’t be handed over, and the hub can’t yet share an accessory with another ecosystem.

Some routers sit on the broadcasts a phone uses to find a device, so a hub that was running perfectly could look dead for minutes. It now keeps itself known to every phone and computer that talks to it, and the apps can tell a slow hub from a gone one.

Known without being asked
Wi-Fi power saving is off, and the hub reminds each phone and computer that talks to it where it is — directly, rather than by broadcast — so a phone coming home knows it again within a couple of minutes.

Slow isn’t gone
The apps ask a slow hub twice, on a fresh connection, before calling it out of reach, and a hub that is switching radios or updating says so instead of reading as a failure. The hub keeps its own memory out of swap, too, so waking it isn’t a wait.

Closed to web pages
The hub refuses any request addressed to it by a public domain name — the trick a web page would need to read it through your browser — and advertises only the address it actually answers on. Studio no longer writes its token where the system log can see it.

Checked before it runs
Installing or updating checks the hub and the Node.js under it against published SHA-256 digests. A mismatch stops the install with the running hub untouched.

The hub can narrow a router’s faults, not fix them: a guest network or client isolation still keeps the phone and the hub apart.

Open the app with no homes and there are five pages to swipe through — your home on cards, one hub carrying both radios, a device the hub works out for itself, talking to the house, a rule written from a sentence — with “Add a home” and a demo under every one.

Nothing in the way
No Next, no Skip, no counter: tap on the first frame and you never see the rest. Each page floats real pieces of the app over its picture, and Profile opens the deck again whenever you want it.

Asked properly
Before iOS asks about the local network, a page says why a hub needs it. Say no anyway and you get the way into Settings rather than a spinner that never stops, and the search carries on by itself once access is back.

Can’t find your hub?
A page of what to check when no hub turns up — and the app keeps looking, asking twice before it gives up.

The assistant is real now. What you type or say reaches an agent on your hub that answers about the home, works your devices, presses your scenes — and hands the jobs that belong to another agent over to it, in the same conversation.

It works the home
Ask what’s on, what’s open or how warm the bedroom is, and it reads the house to answer. Tell it to switch something off or run a scene and it does — and the home’s history names whoever asked, not “the assistant”.

It hands the job on
Ask for a rule and it writes a brief for the automations agent rather than learning rules itself. That agent’s steps, its questions — answered right where you are — and the rule it saves switched off all appear in the same conversation, and a follow-up goes back to the agent that did the work.

Just talk to it
Tap the orb or the microphone and speak. It listens and talks at once, so you can cut in; a soft rising tone says it’s your turn, and the same notes falling say it has stopped. Nothing listens until you tap, and the line closes itself after a minute of quiet.

One conversation
What you say is written into the same conversation as what you type, so the page fills in while you talk and you can carry it on by typing. Past conversations are a tap away for a fortnight, each with what it cost.

The key stays on the hub
Your voice goes from the phone straight to OpenAI’s live model, over a call your hub sets up with the home’s key — the key itself never reaches the phone, and the answers come from the same agent your typing reaches.

Hub homes only — the agent lives on the hub. Typed answers run on the home’s Anthropic or OpenAI key; the voice is OpenAI’s live model, so it needs an OpenAI key and is billed for the time the line is open, silence included. It can’t send you a notification, and like the rest of gethome it only works on your own network.

A board with 1 GB or less used to pick Matter or Zigbee. Now “Run both radios” is a switch on every board, and the hub watches its own memory — warning first, and handing a radio back by itself only if the board starts running short.

It warns, then acts
With both on, the hub reads its memory every 30 seconds and acts on being throttled, long before anything is killed. You get about a minute and a half to choose for yourself; if it does hand a radio back, the home’s history and both apps say so.

Parked, not cancelled
Your choice survives a stand-down: the hub tries both radios again by itself after the Pi restarts or within a week — twice — and a button in the app tries it now.

Memory, not model
Every app now says what decides it: 2 GB or more runs both, and a 1 GB Pi 4 is set up for one radio at a time just like a Zero 2 W. A 1 GB board gets limits sized for its own memory, and a card moved into a bigger Pi is measured again.

Offline on purpose
Unplug the heater for the summer and say so on its page: the home stops saying it needs attention, on every phone, until the heater answers again. A radio resting its turn, or a device the hub is still finding, no longer counts as offline either.

Measured on a Zero 2 W: one Matter plug and three Zigbee devices ran both radios for seven hours without being throttled once. Nobody can tell you where a small board stops fitting — if you’re planning a large Zigbee network beside Matter, get 2 GB or more.

A second phone, a Mac, or the same phone after the app was reinstalled used to join the home as a stranger with your name. Now a sign-in code brings you back as yourself — with your favourites, your conversations and your line in the home’s history.

A code that names somebody
On your own row in People & access it’s “Add another device”, and it needs no permission; for somebody else it’s “Sign in again…”, for whoever may invite. Like an invite it lasts fifteen minutes and works once — but it brings a person back rather than adding one. In the app and in Studio.

Your name, in one place
Say what you’re called once, on Profile, and every home you’re in gets it; the dashboard greets you by it, and each home in your list says which role you hold there. A name you typed when you joined a hub arrives by itself.

Straight to your home
The app opens on your home from its first frame, instead of on a “Getting things ready…” screen while it remembered you had one.

The apps ask the hub before offering a code: a hub older than 0.1.2 would quietly add a second person instead, so it isn’t offered one.

Say what you want in a sentence and an agent on your hub builds the rule out of what your home actually has. Every rule is saved switched off until you turn it on, and every firing shows its working — including the commands the hub declined to send.

Describe it, don’t build it
Start from a preset — “I’m leaving”, “Night”, a light that follows movement — or just say it: “turn the hall light on when someone walks past after dark.” The agent asks a question or two with answers you tap rather than type, and shows you the rule before anything runs.

A rule you can read
Rules arrive drawn as a flow — what starts it, what has to be true, what happens — rather than as a paragraph to parse. It rests on one sentence and folds open into the steps.

Saved switched off
Nothing your house does starts happening because a model decided it should. A new rule lands inert; the moment between “here is what I wrote for you” and “your home is now doing it” is yours.

Why the light came on
A rule’s page keeps its firings, grouped by day — including the commands the hub refused. A relay is never switched twice a second, and a rule that runs away switches itself off and says so.

Scenes are automations
On a hub home the scenes on your dashboard are the home’s own rules — the ones somebody can press. One vocabulary, one place to edit them, and pressing one is the floor: every member can work the home.

Rules where they belong
A rule about one room appears on that room’s page, worked out from the devices it touches. The dashboard shows three with the rest one tap away.

They run on the hub
Rules keep working while your phone is away, and they keep running whether or not AI is switched on — “stop spending my money on this” should never put the lights out on a schedule.

Writing a rule needs an Anthropic API key on the hub; running one needs no key at all. There are no notifications yet — a rule can write a line into the home’s history and nothing more, and the agent says so rather than inventing an action.

A local hub that brings Matter, Zigbee and MQTT devices behind one typed schema, on a Raspberry Pi you own — no cloud account, nothing leaving your network. This is everything it did before automations.

One schema for everything
Twenty-seven capabilities across sixteen device kinds, with exact unit conventions shared with the app. Buttons and remotes arrive as structured events, multi-channel relays as separate endpoints, IR blasters as learn-and-replay.

Nothing unsupported by default
Three layers: typed capabilities first, then a generic control for every leftover parameter, then AI for the genuine gaps. The first two need no key and no network — a device is never simply unsupported.

Unknown devices, recognised
Plug in a no-name sensor and a mapping agent reads its published schema, researches it starting from its own Zigbee2MQTT page, and submits a validated mapping — data, never code. Bring your own Anthropic or OpenAI key; every run records what it searched, what it read and what it cost, and the answers are a library you can carry to another hub.

Sharing, and roles
A pairing code makes you the owner; short-lived invite codes add family. Owner, Member and Guest ship built in, a home can add roles of its own, and what each may do is a table either app edits.

Recorded readings
Temperature, humidity, air quality and power in five-minute buckets for about a week, so an app can draw what the last few days actually looked like. A device that goes quiet leaves a real hole rather than a flat line pretending the room was steady.

Portraits are the house’s
The AI picture of each device is drawn on the hub with the home’s own key and kept there, so everybody in the home sees the same kettle instead of one phone holding the only copy.

It updates itself
A phone can ask the hub to update. The installer unpacks the new build beside the running one and flips a symlink, so switching is atomic — and if the new build doesn’t answer its health check, it flips back and says so.

One radio at a time, said out loud
512 MB fits Matter or Zigbee2MQTT, not both. Plug a coordinator in and the board runs Zigbee; leave it out and it runs Matter. Switchable from the app at any time, and nothing loses its pairing either way.

64-bit only. Tested on the Raspberry Pi 5, Pi 4 and Zero 2 W; Zigbee needs a USB coordinator. LAN-only by design in v1 — remote access through an authenticated relay is planned, and the hub is never port-forwarded.

The Mac app that turns “install a smart-home hub” into a guided few minutes: write an SD card, or find a Pi already on your network, and watch the install happen step by step.

Two paths, both real
An SD card that already has Raspberry Pi OS on it, provisioned so the Pi installs the hub by itself on first power-up — or a Pi already running, installed over SSH. One four-step rail and the same checklist either way, and leaving halfway is safe: Studio offers to carry on where you left off.

It watches, it doesn’t guess
Studio reads the Pi’s own install log as it grows and names the failure — a Pi that never joined the Wi-Fi, a card carrying the 32-bit image, a coordinator whose firmware is too old to pair — instead of showing a spinner that means nothing.

You are never asked for a pairing code
Studio holds a key on the machine it installed, so it has the hub claim itself and brings the owner token back. The typed code is the fallback, not the route.

The hub’s own page
What it can talk to, which radios are live and why, the build it runs and the button that updates it, the members list, and the full permissions matrix — every row in the hub’s own wording, so a Studio one version behind still draws a complete table.

A live view of the broker
Every Zigbee signal passes through the hub’s MQTT broker; Studio streams it over the hub’s authenticated socket, with the pairing timeline beside the button that opened the network.

The device schema library
Download a mapping from one hub and upload it to another, or hand a refused one back to the agent to repair — a schema the hub can’t use comes back with the reasons rather than a dead end.

Device Studio (inventing your own devices) and Integrations are reserved and marked Soon. Writing a blank SD card end to end isn’t implemented — Raspberry Pi Imager does that, and Studio puts its steps on the screen. Requires macOS 14 or later.

The deployment floor drops to iOS 18.6, so the app installs on every iPhone from the XR onward. iOS 26 stays the design target: each Liquid Glass surface keeps the new API as its primary path and takes a documented fallback below it, rather than being flattened to what both versions can draw.

An iPhone app that holds the whole house — three kinds of home, every device grouped by room, and a dashboard that answers questions instead of listing switches. This is everything the app did before automations.

Three kinds of home
Mirror a whole Apple Home over HomeKit and control Matter and HomeKit accessories from one place; attach devices to a gethome Hub and share that home with the family; or build a demo home from one of five archetypes with no hardware, no account and no hub at all.

A dashboard that answers questions
A smoked-glass pulse panel with a calm-or-attention headline, one big hero reading, and tappable metrics — what’s on, what’s offline, whether the home is secure, how warm it is inside — each of which opens the Devices pane with that lens already set.

Controls that fit the device
Colour without switching the lamp on, warmth ramps, cover positions, a 270° thermostat dial with half-degree detents. Twenty-seven typed capabilities across sixteen device kinds, not a wall of identical toggles.

Rooms as places, arranged by you
Every room zooms open into its own page. Hold a room or a device card and drag it where you want it — that order lives on your phone alone, so everyone in the house can arrange the same home their own way, while the names and rooms themselves are shared.

Widgets and a Control Center toggle
A device pill in Control Center, on the Lock Screen or behind the Action button, a one-device Home Screen tile, and a room-or-favorites grid. A tap reaches the hub over your Wi-Fi from the widget’s own process, so there’s no app launch in the way. Hub homes only, on purpose.

What a reading was
A device that measures something carries its history — the last hour, six hours, day or week as a line with the low-to-high range of each moment shaded behind it. Drag across it and the value follows your finger.

Roles for a shared home
Owner, Member and Guest, plus any role the home invents, edited from a table in Home Settings. What your role can’t do is never a button that fails — one quiet line says the role is why.

AI device portraits, experimental
A clean, palette-matched render of the device on a transparent background, floating on its page and tilting to your phone’s motion. Make one from a photo in the portrait studio; on a hub home the hub draws it, so it is the house’s picture rather than one phone’s.

Adding devices
Matter by scanning the accessory’s setup code, Zigbee by opening the hub’s network for a few minutes. The radio switch, the hub’s address and build, and the button that updates it all live one floor down from Home Settings.

The assistant orb ships as a surface rather than an intelligence: it listens, it answers your voice with light, and it says honestly that understanding is still being wired in. Requires iOS 18.6; iOS 26 for the full design.