Home Assistant Green vs Yellow: Which Local Hub Is Better?

The real divide is underneath the operating system: one is a sealed appliance built for a predictable setup, while the other is a modular carrier board built around a Raspberry Pi Compute Module.

That distinction affects almost everything that follows. It changes how much hardware you need to buy, which radio protocols are available from the start, how storage can be expanded, whether PoE is practical, and how much room the system leaves for a more demanding installation later.

The Green is the simpler product. The Yellow is the more flexible one. But “more flexible” does not automatically mean “better,” particularly now that the Yellow has been discontinued and the Green has moved into a different price bracket.

The Evolution of Nabu Casa Hardware: From Modular to Plug-and-Play

Home Assistant Yellow was designed for users who wanted a local hub but did not necessarily want to assemble a small computer from unrelated parts. It used a carrier-board approach: the board supplied the connectivity and expansion features, while the main computing hardware came from a Raspberry Pi Compute Module 4 or, depending on the configuration and availability, a later compatible module.

That arrangement made the Yellow unusually interesting for a Home Assistant appliance. The compute module determined the available RAM and some of the storage configuration. The board itself added features that are awkward to retrofit onto a conventional Raspberry Pi setup, including an M.2 M-key slot for an NVMe drive, an optional Power-over-Ethernet board, and an integrated Silicon Labs MGM210P radio module on supported versions.

The result was not a completely plug-and-play product in the conventional appliance sense. You still had to think about which Compute Module to buy, how much memory was appropriate, whether you needed additional storage, and whether the PoE accessory justified its cost. The Yellow rewarded planning. It also gave the owner more ways to adapt the system to a particular installation.

Home Assistant Green, launched on September 17, 2023, took the opposite route. The Rockchip RK3566, 4 GB of LPDDR4X RAM, and 32 GB of eMMC storage are fixed inside the enclosure. There is no Compute Module to replace and no internal M.2 slot waiting for a future upgrade. Setup is intentionally narrow: connect power, connect Ethernet, and install or restore Home Assistant.

That is the Green’s central appeal. It removes the decisions that make small self-hosted systems feel more like projects than products. There is no need to compare Compute Module variants or source a suitable carrier board. The trade-off is equally straightforward: the hardware ceiling is set at the factory.

The Yellow was a modular platform; the Green is an appliance. Once that distinction is clear, most of the buying decision becomes much less mysterious.

The change also reflects a broader shift in Nabu Casa’s hardware strategy. Yellow was aimed at enthusiasts who wanted official hardware without giving up expansion options. Green is aimed at the much larger group of users who want Home Assistant to behave like an appliance: local, quiet, and uncomplicated.

That does not make Green a limited device in software terms. It can still manage IP cameras, Wi-Fi devices, Matter-over-Wi-Fi accessories, integrations for cloud services, dashboards, scripts, and automations. Its lack of built-in radios only becomes a serious constraint when the installation depends on protocols such as Zigbee, Thread, or Z-Wave.

Performance and Power: Analyzing the RK3566 vs. CM4 Architecture

The Green uses a Rockchip RK3566 with four Cortex-A55 cores and 4 GB of soldered memory. For ordinary residential Home Assistant work, that is a sensible configuration. It leaves enough room for the operating system, integrations, dashboards, automations, and a normal Recorder database without asking the owner to manage Linux resources by hand.

The important point is not a particular benchmark result. Home Assistant workloads are too variable for a single number to tell the whole story. The size of the entity database, the number of state changes, camera processing, voice pipelines, add-ons, log retention, and custom integrations can all change the shape of the workload. A home with several hundred mostly quiet entities may be easier to run than a smaller installation that records frequent updates from power meters, environmental sensors, and cameras.

The Green’s fixed hardware is therefore best understood as a stable baseline rather than a performance promise. It is well suited to a focused residential installation, especially when heavy video processing and large local databases are handled elsewhere. If the goal is to run Home Assistant, connect common smart-home devices, build dashboards, and maintain a reasonable history, the Green has the right character: limited in expansion, but consistent in operation.

The Yellow’s compute performance depends on the Compute Module installed. A CM4 with more memory gives the system additional headroom for larger databases, more add-ons, and workloads that compete for memory. That does not mean every Yellow will feel dramatically faster than every Green. The comparison depends on the specific CM4 configuration and on what the system is doing.

The Yellow’s advantage is easier to see when the workload is no longer modest. A large Recorder database, local voice processing, more extensive dashboards, and multiple supporting services all benefit from having more memory available. The optional NVMe drive also offers a more appropriate home for an active database than removable flash storage, particularly for users who expect to keep a substantial history or who want to reduce dependence on the system’s fixed storage.

Power use follows the same design logic. The Green’s integrated platform is designed around a compact, efficient appliance. The Yellow combines a carrier board, a Compute Module, an optional SSD, and potentially a PoE accessory. Depending on the configuration and workload, that flexibility can require more power and can produce more heat. It is not a defect; it is part of the cost of adding components and expansion paths.

Neither device should be judged by idle power alone. A Green with several USB peripherals may have a different real-world draw from a bare Green. A Yellow with an SSD and PoE hardware will not represent the same electrical load as a Yellow used with basic power input. For an always-on system, those differences matter, but they should be evaluated across the complete installation rather than attributed to the hub in isolation.

The CM4-versus-RK3566 question is therefore less about declaring one processor the winner. The Green offers a known, fixed platform. The Yellow lets the owner choose more of the platform around the Home Assistant workload. If you value predictable deployment more than future expansion, Green’s fixed specification is a benefit. If you already know that storage, memory, or network power delivery will matter, the Yellow’s architecture remains more attractive.

Connectivity Constraints: Why the Green Requires External Dongles

This is the most visible difference in day-to-day use.

Home Assistant Green has Ethernet and USB ports, but it does not include a Zigbee, Thread, or Z-Wave radio. That does not leave it unable to connect to smart-home devices. It can communicate with devices and services over Ethernet or Wi-Fi, including many Matter-over-Wi-Fi products, vendor integrations, MQTT devices, and platforms that expose a local network API.

What Green cannot do by itself is act as a local radio coordinator for Zigbee or Thread, or as a Z-Wave controller. For those protocols, an external adapter is required.

The usual Home Assistant route is a USB radio such as the Home Assistant Connect ZBT-2, priced at approximately €45 / $49. Depending on how it is configured, the adapter can provide Zigbee or Thread connectivity. A separate Z-Wave controller is needed for Z-Wave devices; an 800-series USB stick is a common choice, with pricing often falling in the $40–$55 range depending on the model and market.

That additional hardware is not automatically a disadvantage. External adapters can be positioned away from the hub, connected through a short extension cable, or replaced independently if a newer radio becomes available. A USB coordinator also makes it possible to move the radio to another Home Assistant host without replacing the entire computer.

The disadvantage is practical rather than mysterious: there are more parts to configure, more firmware considerations, and another device occupying a USB port. The adapter’s placement can matter for radio performance. A coordinator hidden behind a metal rack, crowded against a computer, or placed next to a noisy USB device may have a worse Zigbee or Thread environment than the same coordinator positioned in open air.

The Yellow’s integrated MGM210P radio gives it a cleaner starting point for Zigbee and Thread. There is no need to purchase a separate coordinator for those protocols, and the radio is part of the board layout rather than hanging from a USB cable. That makes the Yellow particularly appealing when the hub will sit in a central network cabinet or when the owner wants the fewest possible external components.

Still, the integrated radio should not be treated as a universal wireless solution. It does not turn the Yellow into a Z-Wave controller, and radio coverage is still affected by the hub’s physical location, building materials, interference, and the distribution of mains-powered mesh devices. A built-in radio reduces hardware clutter; it does not remove the realities of wireless networking.

The same nuance matters when discussing latency. A USB adapter is not inherently slow simply because it is connected over USB. USB enumeration is part of device discovery and startup, not a new enumeration cycle that occurs for every command. In a correctly configured system, the coordinator remains available to Home Assistant and communicates with the mesh according to the radio protocol.

In practical terms, the difference between an integrated Yellow radio and a well-placed external Green adapter is unlikely to be the deciding factor for ordinary lighting and sensor automations. Network topology, coordinator placement, firmware, mesh quality, and the behavior of the end devices usually matter more. The Green’s external-dongle design is an inconvenience for some installations, but it is not a built-in guarantee of sluggish automations.

Green does not have “no devices to connect.” It connects to everything that speaks through the network; it simply needs a separate radio when the device speaks Zigbee, Thread, or Z-Wave.

For anyone comparing the two hubs, the useful question is not whether a dongle is theoretically acceptable. It is whether you want to manage the radio as a separate component. If the answer is no, the Yellow has a clear advantage for Zigbee and Thread. If the answer is yes, Green remains a capable local hub and gives you freedom to choose the adapter and its location.

Expandability and Longevity: The M.2 SSD and PoE Advantage of the Yellow

The Yellow’s strongest argument is not that its Compute Module is always faster. It is that the platform gives you somewhere to go when the original configuration stops being sufficient.

The M.2 M-key slot supports compatible NVMe drives in supported form factors, including 2230 and 2242 drives. Moving Home Assistant’s active data to NVMe can make sense for installations with a busy Recorder database, extensive local history, or additional services that generate regular writes. It also avoids treating a removable SD card as the long-term foundation of the system.

That does not turn the Yellow into a storage server. The M.2 interface and the chosen drive still determine what the system can deliver, and the board does not provide enterprise-style power-loss protection by itself. An SSD is not a substitute for backups. If the data matters, keep a current backup somewhere outside the hub, and consider how the system will behave during an unexpected power interruption.

The storage question is more complicated on Green because the 32 GB eMMC is fixed. For many homes, that is enough when Recorder settings are sensible and the database is periodically maintained. For others, especially installations recording frequent changes from energy monitoring, environmental sensors, or large groups of devices, the available space can become a planning constraint.

There is no universal retention period at which Green runs out of storage. The result depends on the number of entities being recorded, how often they change state, the attributes stored with each event, database maintenance, add-ons, logs, and whether media or backups are kept on the same device. A one-second recording policy can be light for one system and excessive for another.

This is where configuration matters more than a dramatic storage deadline. Home Assistant users can reduce unnecessary Recorder activity, exclude noisy entities, manage purge settings, and move backups or selected data to another system. Those measures may be enough for a normal home. They are less appealing if the aim is to keep a large, detailed history without ongoing maintenance.

The Yellow also has a more substantial path to network power. With the appropriate PoE accessory, it can receive data and power over a single Ethernet cable using an IEEE 802.3at-compatible setup. That is useful in structured wiring cabinets, wall-mounted network enclosures, and installations where a local power outlet is inconvenient. It can also simplify backup power: a suitably protected network switch or injector can support both the hub and the network connection.

Green uses a 12 V DC barrel-jack input and has no native PoE option. A PoE splitter or other third-party arrangement may be possible in some deployments, but that is not the same as having a purpose-built PoE path integrated into the product. If the hub is going into a rack or a remote wiring location, this distinction should be considered before installation rather than after the power cable becomes the least elegant part of the setup.

The Yellow’s modularity also helps with serviceability. A replaceable Compute Module gives the owner more options than a fixed appliance, although availability is a real consideration now that the Yellow is discontinued. A theoretical upgrade is not very useful if the required module, carrier accessory, or replacement board is difficult to source.

That is the longevity trade-off in its clearest form:

• Green has fewer parts that can become unavailable, but the parts it has are fixed. You get a known configuration and limited upgrade paths.
• Yellow offers more ways to extend the system, but its future depends on sourcing compatible Compute Modules, SSDs, PoE hardware, and replacement components.
• External USB radios on Green are easier to replace individually, while Yellow’s integrated Zigbee and Thread hardware is cleaner but tied to the board.
• Neither platform removes the need for backups, database housekeeping, and sensible storage planning.

Cost of Ownership: Factoring in the 2026 Price Adjustments and Add-ons

The original appeal of Green was its low-friction price. It entered the market at $99, making it easy to recommend as a first official Home Assistant appliance. That position changed after component-cost pressures, particularly around memory, led to two price adjustments.

The first adjustment was announced on January 8, 2026. The second took effect on April 24, 2026, bringing the current listed price to $199 / €179. That changes how Green should be evaluated. It is still simpler than building a host from separate components, but it is no longer a throwaway purchase whose limitations can be ignored because the entry cost is minimal.

The base price also does not tell the whole story for a radio-based smart home. A Green installation using Zigbee or Thread will usually need a compatible USB adapter. With the ZBT-2 at approximately €45 / $49, the appliance-plus-radio cost is closer to $248 in the dollar example before adding anything else. Add a separate Z-Wave stick if the home uses that protocol.

A current Green deployment might therefore look like this:

• Green hub: $199 / €179
• Home Assistant Connect ZBT-2: €45 / $49
• Optional Z-Wave 800-series stick: $40–$55
• Ethernet cable, USB extension, or other installation accessories as needed
• Approximate hub-and-radio total: $248–$303, depending on the protocol mix and local pricing

The Yellow is harder to price because it is no longer manufactured as a current mainstream product. Retail listings vary according to the carrier board, Compute Module configuration, storage, and whether a PoE accessory is included. The figures below describe the kind of package a buyer may need to assemble rather than a guaranteed current retail bundle:

• Carrier board: $130–$170, where available
• CM4 module with 4 GB RAM and 32 GB eMMC: $75–$95
• NVMe SSD, 1 TB, in a compatible 2230 or 2242 form factor: $60–$100
• Optional PoE HAT: $25–$40
• Approximate configured total: $290–$405

A less ambitious Yellow configuration can cost less if the buyer already owns a suitable Compute Module or does not need an NVMe drive and PoE. Conversely, scarcity can push a complete package above the expected range. The Yellow is not a stable commodity product anymore; it is a hardware platform being assembled from remaining stock.

That makes the ownership comparison more than a simple Green-versus-Yellow price table. Green asks you to pay for simplicity up front and accept a fixed ceiling. Yellow asks you to spend more time and potentially more money in exchange for internal storage expansion, modular compute, integrated Zigbee and Thread, and PoE potential.

There is also a risk calculation. With Green, a failed radio adapter can be replaced without replacing the hub. With Yellow, a failed or unsupported carrier board is more consequential, but the Compute Module itself may be reusable in another compatible project. With Green, there is less to configure. With Yellow, there are more components whose compatibility should be checked before purchase.

Which Local Control Smart Home Hub Fits the Installation?

The best hardware for Home Assistant depends on where the system sits between “a few local automations” and “a small piece of infrastructure.”

Green is the more sensible choice when the priority is a clean installation with minimal decisions. It works particularly well when:

• Home Assistant will run primarily as a local automation and dashboard platform.
• Most devices communicate over Wi-Fi, Ethernet, Matter-over-Wi-Fi, or existing vendor integrations.
• Zigbee or Thread can be handled by a separate, well-placed USB coordinator.
• The Recorder database can be kept under control through sensible exclusions and purge settings.
• There is no requirement for internal NVMe storage or native PoE.
• The owner would rather replace a peripheral than troubleshoot a modular computer.

The Green’s fixed specification is not a weakness in every context. For a normal household, hardware consistency can be more valuable than theoretical upgrade potential. A sealed appliance is easier to document, easier to restore, and easier to hand over to someone who does not want to maintain a small computer.

Yellow remains the more compelling platform when the installation has structural requirements that Green cannot meet internally:

• Zigbee and Thread should be available without a separate USB radio.
• The system needs an internal NVMe option for active storage and a larger local history.
• PoE is useful or necessary because the hub will live near network equipment.
• A replaceable Compute Module is preferable to a fixed processor and fixed RAM.
• The owner is comfortable sourcing discontinued or surplus hardware.
• The installation is being designed as infrastructure rather than as a simple appliance.

The thresholds are not absolute. It would be misleading to say that Green is only suitable below a particular device count, or that Yellow automatically becomes necessary once a home passes a certain number of Zigbee devices. Device behavior, reporting intervals, mesh topology, automations, and database settings all influence the result. A quiet network of many devices may be easier to manage than a noisy network of far fewer ones.

The same caution applies to “commercial” versus “residential.” A technically demanding home can place more pressure on a hub than a small office. A modest business deployment may be perfectly comfortable on Green if storage and radio requirements are straightforward. The architecture of the workload matters more than the label on the building.

The Verdict: Green for Certainty, Yellow for Headroom

Home Assistant Green and Home Assistant Yellow converge at the software layer, but they do not offer the same ownership experience.

Green is the straightforward local hub. It has fixed memory, fixed eMMC storage, no built-in smart-home radio, and no internal expansion path. In return, it is easier to buy, easier to deploy, and easier to understand. Add the right external coordinator and it can serve a broad range of local smart-home installations without becoming a hardware project.

Yellow is the enthusiast and infrastructure platform. Its CM4-based design, integrated Zigbee and Thread radio, M.2 storage option, and PoE capability give it more room to adapt. Those features are valuable when they solve a real installation problem. They are less valuable when they simply add components and sourcing decisions to a system that would have been perfectly happy with a fixed appliance.

The fact that Yellow is discontinued changes the recommendation. It is no longer the obvious premium alternative that a buyer can select from the same current product range. It is a strong option when a complete, sensibly priced unit is already available, particularly for someone who specifically wants NVMe, PoE, or the integrated radio. It is a weaker choice when buying piecemeal components at inflated prices or relying on uncertain replacement availability.

For most new users, Green is the safer default: buy the hub, add a compatible radio only if the device mix requires one, and keep storage and Recorder settings deliberate. For users designing a more expandable installation and willing to accept discontinued hardware, Yellow still offers the more capable architecture.

So, in the Home Assistant Green vs Yellow specs comparison, Green wins on simplicity and predictable ownership. Yellow wins on expansion and built-in connectivity. The better local hub is the one whose limitations match the installation rather than the one with the longer feature list.