Home Assistant Release Notes in 2026: How to Read Them — and the Hardware That Keeps Pace

Home Assistant ships a new release roughly every month, and the release notes are arguably the most valuable document in the entire ecosystem. They tell you what has changed, what has been deprecated, and — increasingly — what your hardware now needs in order to run comfortably. Read them properly and you sidestep the classic mid-month breakage. Skip them, and a routine update can quietly strand an ageing hub that no longer meets the project’s minimum requirements.

That has a hardware consequence, which is what this guide is really about. Recent release cycles lean harder on 64-bit processing, more RAM and modern radio silicon than the releases of even two or three years ago, and a growing share of questions in UK owner communities comes down to the same thing: is my box still good enough? Below we explain how to find and read Home Assistant release notes, what they reveal about hardware floors, and which devices — from Nabu Casa’s own appliances to budget Zigbee coordinators and second-hand thin clients — keep pace with them.

Everything here is based on manufacturer specifications, published release documentation and aggregated owner feedback rather than hands-on testing. This is a research-based buying guide, not a lab report.

Quick picks

Where to find Home Assistant release notes

There are five reliable routes, and most owners only ever use one of them.

The official blog at home-assistant.io/blog publishes on the first Wednesday of each month. This is the canonical version: it carries the full highlights, the breaking changes list and the migration guidance in one place.

The GitHub releases page at github.com/home-assistant/core/releases is the developer-facing equivalent. It is more granular — every merged change appears here — and it is the place to look when you want to know precisely which pull request removed a YAML key you relied on.

The in-app path is the one most users overlook: Settings → System → Updates. The release notes surface in the update dialog before you confirm, which means the breaking changes list is displayed at the exact moment you are about to make the decision. If you only ever read one release note a month, read this one, because it appears at the point of no return.

The command line is useful on headless installs. Running ha core update --version 2026.X.0 both shows the available version and performs the update to a specific one — which doubles as a rollback mechanism (more on that below).

RSS is available at home-assistant.io/atom.xml if you would rather have release notes delivered to a feed reader than remember a date.

The monthly cadence, beta and patches

Home Assistant uses calendar versioning — 2026.1, 2026.2, 2026.3 and so on — with a stable release landing on the first Wednesday of each month. A beta (release candidate) drops the preceding Wednesday, roughly one week before stable. That beta exists so integrations can be exercised early: if you run hardware that depends on a third-party integration, the beta week is when breakages tend to surface publicly, before they reach you.

Patch releases follow the major release: .1, .2 and .3 typically land within days to weeks afterwards, fixing regressions the stable release introduced. The consensus among owners on r/homeassistant is to leave production systems on the .2 or .3 patch rather than jumping on the .0. Practically, that means your install sits one or two weeks behind the headline release and skips most of the pain.

The rhythm also has a commercial meaning worth spelling out. An appliance you buy in 2026 will receive roughly twelve feature releases and dozens of patches over the following year, all free of charge. The release notes are, in effect, the changelog for a product you already own.

Breaking changes: the section that matters most

Every release note opens with highlights and new features, but the section to read first is Breaking changes. This is where the project lists removed YAML keys, renamed entities, dropped integrations and raised minimum requirements — including the minimum supported operating system version and, occasionally, new hardware floors.

The pattern reported in community write-ups is consistent: most “Home Assistant broke after updating” incidents trace back to a breaking change that was documented weeks in advance. The information was there; the reader skipped the section. Five minutes spent on it before you press update is the single highest-return habit in the ecosystem.

Core vs Supervisor vs OS vs Add-ons: the confusion at the heart of it all

The most common misreading of a release note comes from assuming Home Assistant is one piece of software. It is four independently versioned layers: Home Assistant Core, the Supervisor, the Operating System (HAOS) and Add-ons.

Core is the application itself — the automation engine, integrations and dashboards — and it is what the monthly release note is mostly about. The Supervisor manages the installation, the OS layer provides the underlying Linux system, and add-ons (the containerised extras such as Zigbee2MQTT or a database viewer) ship on their own schedule, not on the monthly cadence.

Why this matters to a buyer: a headline release note about Core features will not necessarily appear on your add-ons page as an update that month, and conversely an add-on developer may push a major change in between monthly releases. If you are troubleshooting a problem, the first useful question is which of the four layers is actually misbehaving — the version number in the blog post often refers to a different layer from the one you are looking at in your own interface.

What the 2026 releases mean for your hardware

Most monthly releases run perfectly well on hardware from three or four years ago. But the notes do occasionally signal a genuine ceiling, and a few of those signals are now permanent.

32-bit ARM is gone. The armhf architecture was formally deprecated and dropped, announced on home-assistant.io/blog during the 2024.x release cycle. The current position is unambiguous: HAOS requires a 64-bit architecture, either x86-64 or aarch64. If you are running a 32-bit Raspberry Pi OS base, no amount of patching will bring you back onto the current release train — this is a hard floor, not a soft recommendation.

RAM is the next constraint. The current documentation puts the minimum comfortable figure at 4 GB. That number is driven partly by the recorder database and partly by the Assist voice pipeline, which adds roughly 500 MB to 1 GB of overhead when run locally on-device. Two gigabytes of RAM is technically workable in a minimal setup; add a local voice pipeline and a handful of add-ons and you are into swap, which is where responsiveness quietly disappears.

Storage grows faster than people expect. The recorder database grows at approximately 1 MB per entity per day, per Home Assistant’s documentation. A modest install tracking a hundred entities is therefore adding recorder data at a rate in the order of 100 MB a day. That is why database maintenance, retention settings and storage-related notes appear in release notes so regularly — the appliance you bought does not grow, but your database does.

Taken together, those three figures are the practical filter for any purchase below: does it do 64-bit, does it have 4 GB of RAM to spare, and does it have storage that will not fill up in a year?

How to choose hardware that keeps pace

Five things decide whether a device will still be comfortable on the 2026 release train.

Architecture first. Anything that cannot run a 64-bit OS is disqualified — x86-64 or aarch64 only, per the current HAOS requirement.

RAM second. 4 GB is the documented comfortable minimum, and the voice pipeline’s 500 MB–1 GB overhead comes out of that budget.

Storage third. Recorder growth of roughly 1 MB per entity per day means eMMC and SSD sizes matter more than CPU speed for many homes.

Radio fourth. Zigbee, Thread and Z-Wave are not built into most hosts. You need a coordinator — and crucially, the official Green appliance carries no built-in radio, so a radio purchase is a dependency rather than an optional upgrade.

Update path last. Settings → System → Updates allows version pinning, so you can hold a known-good release rather than being dragged forward; and Settings → System → Backups lets you take a snapshot before you update. Backing up before updating is the habit that makes every other risk in this article survivable.

Home Assistant Green

Best for: most people who want an official appliance and no tinkering.

Key specs: Cortex-A55 processor, 4 GB RAM, 32 GB eMMC storage, silent fanless operation, and no built-in radio.

Standout strength: it is the cheapest supported route to current releases. It meets the 64-bit requirement, matches the documented 4 GB comfortable-RAM figure, and arrives as a finished product rather than a project — the reason it is the default recommendation for anyone who wants Home Assistant to behave like an appliance.

The caveat, stated plainly: Green has no Zigbee, Thread or Z-Wave radio inside it. The Connect ZBT-1 is a bundle dependency, not an alternative — if you want Zigbee or Thread devices, you are buying both. Budget for the two together.

Where to buy: Pimoroni and The Pi Hut both stock it in the UK. The Green ships with a UK plug included in the power supply, so there is no separate mains adapter to source.

Verdict: the sane default for a UK household that wants current releases without a build project — as long as you add the radio at the same time.

Home Assistant Yellow

Best for: anyone who wants the radio integrated rather than hanging off a USB port.

Key specs: a Compute Module 4 (CM4) appliance with a built-in Zigbee/Thread radio and a PoE option, so it can be powered over Ethernet rather than from a wall socket.

Standout strength: the integrated radio removes the USB coordinator entirely, which eliminates a whole class of problems — dongle placement, USB extension cables and interference from USB 3.0 ports. The PoE option is genuinely useful if your router or switch sits somewhere convenient but your mains sockets do not.

The caveat: cost depends on which CM4 module you specify, which is why the realistic range is around £90 to £130. There is also no Z-Wave radio onboard, so Z-Wave users still need a separate adapter.

Where to buy: Pimoroni and The Pi Hut stock it in the UK.

Verdict: the tidiest single-box answer for Zigbee and Thread, provided you accept the CM4-spec price variability.

Connect ZBT-1 (formerly SkyConnect)

Best for: adding Zigbee, Thread and Matter support to any host — including the Green.

Key specs: the official Nabu Casa USB coordinator, supporting Zigbee, Thread and Matter. Note the rebrand: this device was previously sold as SkyConnect, so both names refer to the same hardware and you will still see the older name in forum threads and listings.

Standout strength: it is the official radio, which makes it the best-supported path for Matter and Thread updates. When Thread or Matter behaviour changes in a release note, the official coordinator is the device the developers test against — an advantage that compounds over time as those standards evolve.

The caveat: it occupies a USB port, and USB coordinator placement is the classic source of Zigbee reliability complaints. Plan on a short extension cable so the dongle sits away from the host’s USB 3.0 ports and any metal enclosure.

Where to buy: Pimoroni and The Pi Hut stock it in the UK, at around £30–£35.

Verdict: the default radio purchase — buy one with a Green rather than instead of it.

Connect ZWA-2

Best for: Z-Wave networks, which none of the other official options cover.

Key specs: a Nabu Casa Z-Wave USB adapter, pairing with Home Assistant’s Z-Wave integration in the same way the ZBT-1 pairs with Zigbee and Thread.

Standout strength: it comes from the same vendor as the platform itself, which means it sits on the officially supported path rather than depending on a third-party stick’s firmware roadmap. For anyone standardised on Z-Wave devices — locks, sensors and older lighting gear in particular — that support alignment is the whole point.

The caveat: Z-Wave is its own ecosystem. Buying a ZWA-2 does nothing for Zigbee or Thread devices, and vice versa; households running both technologies need two coordinators.

Where to buy: no specific UK retailer is listed for this one, but Nabu Casa hardware of this type is typically stocked by specialist smart-home and electronics retailers in the UK. Check availability at the same specialist shops that carry the Green and Yellow.

Verdict: the official answer for Z-Wave households, and a niche purchase for everyone else.

Sonoff Zigbee 3.0 Dongle Plus-E

Best for: budget Zigbee setups where the official coordinator is not essential.

Key specs: a Zigbee 3.0 USB coordinator at around £15–£20 — roughly half the cost of the official ZBT-1.

Standout strength: the price. For a first Zigbee network, or a second coordinator in an outbuilding, it is the cheapest credible way onto the platform. It has a large owner base, which means community troubleshooting threads are plentiful when something misbehaves.

The caveat: it is a Zigbee-only device. There is no Thread or Matter radio, so if your roadmap includes Matter-over-Thread devices, this purchase will not cover them and you will end up buying an official coordinator later anyway.

Where to buy: no named UK retailer is listed in our sources; the model is typically available from general online electronics retailers and smart-home specialists.

Verdict: the sensible budget pick if you are certain Zigbee alone is enough.

SMLIGHT SLZB-06 and SLZB-07

Best for: installs where the host sits far from the devices — a rack, a cupboard or a different floor.

Key specs: PoE-powered Zigbee coordinators that are network-attached, meaning they connect over Ethernet rather than USB.

Standout strength: removing the USB dependency solves the placement problem at its root. Instead of running a USB extension cable to move a dongle away from interference, you place the coordinator wherever the network reaches — ceiling void, loft, outbuilding — and power it over the same cable. For larger homes this is often the difference between a reliable Zigbee mesh and a flaky one.

The caveat: it assumes you have PoE available, either from a PoE switch or an injector. Without that infrastructure, you are adding another piece of gear to make the coordinator work.

Where to buy: no specific UK retailer is listed in our sources; these models are typically carried by specialist networking and smart-home retailers.

Verdict: the right answer for awkward layouts and larger properties, provided PoE is already in place.

Used thin clients: Dell Wyse 5070 and HP t640

Best for: the cheapest route to a capable 64-bit x86-64 host.

Key specs: x86-64 architecture, typically available used for around £40 to £80. Both are ex-corporate machines, which means large numbers come onto the second-hand market and prices stay low.

Standout strength: for the money, nothing else in this guide offers as much raw compute. They comfortably exceed the 4 GB comfortable-RAM figure in most configurations and run HAOS natively, which makes them a favourite in UK owner communities for installs with several add-ons.

The caveat — and it is an important one: Realtek network chipsets are a known HAOS pain point. Intel NICs are strongly preferred. If you are buying a thin client specifically for Home Assistant, confirm which network chipset the unit has before you pay, because a Realtek NIC can turn a bargain into a troubleshooting exercise.

Where to buy: no named retailer is listed in our sources; these machines are typically found through refurbished IT sellers and general second-hand marketplaces, so check the exact NIC specification in the listing.

Verdict: outstanding value if — and only if — you verify the network chipset first.

Intel N100-class mini PCs

Best for: large installs with lots of add-ons, cameras or a substantial recorder database.

Key specs: modern x86-64 hardware, so the 64-bit HAOS requirement is satisfied with room to spare on both RAM and CPU compared with an appliance.

Standout strength: headroom. Camera integrations, media processing and a recorder database growing at roughly 1 MB per entity per day all consume resources that a small appliance cannot spare — a mini PC absorbs them without the system becoming sluggish.

The caveat: no built-in radio, so a USB coordinator such as the ZBT-1 is still required, and the price varies with the RAM and storage configuration you choose rather than being a fixed figure.

Where to buy: no named UK retailer is listed in our sources; these units are typically sold by general computing retailers and business IT suppliers.

Verdict: the pick for ambitious installs — pair it with a coordinator and it will outlast several years of monthly releases.

Proxmox VM installs

Best for: anyone who already runs an always-on home server.

Key specs: running HAOS as a virtual machine under Proxmox is a fully supported path and adds zero hardware cost increment if the server already exists.

Standout strength: it consolidates hardware. One machine hosts Home Assistant alongside other services, backups become trivial, and snapshots give you a rollback safety net that a bare-metal install cannot match.

The caveat: you are responsible for the host. Virtualisation adds a layer between you and the operating system, and USB coordinator passthrough has to be configured correctly — a step that trips up first-time virtualisers.

Verdict: excellent economics for existing server owners, with a modest learning curve.

UK notes and regulatory practicalities

UK buyers have a genuinely short supply chain here, which is worth knowing before you start price-comparing internationally. Pimoroni and The Pi Hut are the named UK retailers stocking the Home Assistant Green, the Home Assistant Yellow and the Connect ZBT-1, so all three official products can be bought domestically without import charges or customs delays.

Power is one less thing to think about: the Green ships with a UK plug included, so there is no separate adapter purchase.

For the rest of the category — Z-Wave adapters, Sonoff coordinators, SMLIGHT units, thin clients and mini PCs — there is no single named UK stockist in our sources; these are typically found through specialist smart-home retailers, networking suppliers or refurbished-IT sellers depending on the product type. As ever with imported electronics, confirm the plug type and any warranty terms before ordering.

Frequently asked questions

How long can I safely delay a Home Assistant update? Longer than most people assume. The monthly release is not mandatory, and the community consensus on r/homeassistant is to hold production systems on the .2 or .3 patch rather than the initial .0 release, which typically means running one to three weeks behind the headline version. Version pinning in Settings → System → Updates lets you stay deliberately on a known-good build without being prompted into the latest one. The one exception is when a release note announces a security fix or an imminent removal — those are the occasions to move rather than wait.

Will a 32-bit install still work in 2026? No. The armhf architecture was formally dropped, announced on the Home Assistant blog during the 2024.x cycle, and the current HAOS requirement is a 64-bit architecture, either x86-64 or aarch64. A 32-bit system can keep running its existing installation, but it cannot move onto the current release train or receive the fixes that come with it. In practice, this is the single most common reason an older Raspberry Pi setup needs replacing rather than updating.

Do I need a separate Zigbee radio if I buy a Home Assistant Green? Yes. The Green has no built-in radio, so the Connect ZBT-1 is a genuine dependency rather than an upgrade you can defer — without a coordinator, there is nothing for Zigbee or Thread devices to talk to. The alternative is a Yellow, which includes a built-in Zigbee/Thread radio and an optional PoE power path in a single box. Both are legitimate approaches, but the Green’s lower headline price only holds if you remember to add roughly £30–£35 for the coordinator.

How much RAM does Home Assistant really need? The current documentation puts the minimum comfortable figure at 4 GB. That covers the core application and leaves room for a reasonable set of add-ons and a growing recorder database. If you plan to run the Assist voice pipeline locally, add another roughly 500 MB to 1 GB of overhead on top. Systems below the 4 GB mark tend to work until you add a couple of add-ons, at which point they start swapping and responsiveness drops away — which is why the official appliances all ship at that memory level.

Can I undo a bad update? Yes, and this is exactly why version pinning exists. Settings → System → Updates allows you to pin a specific version, and the command line offers the same capability via ha core update --version 2026.X.0, which lets you step back to a release you know worked. The prerequisite, though, is a backup: take one via Settings → System → Backups before you update, not after. With a recent snapshot in hand, a bad monthly release becomes a twenty-minute inconvenience rather than a rebuild.

Do add-on updates follow the same monthly schedule? No, and this catches people out. Home Assistant Core, the Supervisor, the Operating System and Add-ons are four independently versioned layers, and add-ons ship on their own schedule rather than on the monthly cadence. That means a release note about Core tells you nothing about when your Zigbee2MQTT or database add-on will update, and an add-on developer may push a significant change between monthly releases. When something breaks after an update, check which layer actually changed first.

The bottom line

Reading Home Assistant release notes is a five-minute monthly habit with an outsized payoff, and the notes double as an early-warning system for hardware. The hard floors are now clear: 64-bit architecture only, 4 GB of RAM as the comfortable minimum, storage that accounts for recorder growth of roughly 1 MB per entity per day, and a radio bought separately unless you choose the Yellow. For most UK buyers, the Green paired with a Connect ZBT-1 — around £90–£100 plus around £30–£35, both from Pimoroni or The Pi Hut — is the simplest way onto the current release train. Those with existing servers should look at Proxmox, those with awkward layouts at a PoE coordinator, and those watching every pound at a used thin client with an Intel NIC. Whichever route you take, back up before you update — that single habit makes every other decision in this guide low-risk.