Short Answer: Yes, but the Manufacturer Still Decides

Matter is the common smart-home standard that lets compatible devices work with controllers such as Home Assistant, Apple Home, Google Home, Alexa, and SmartThings. Home Assistant can update a Matter device without its vendor app when four things are true: the device implements Matter's optional over-the-air update feature, the manufacturer publishes a compatible update, Home Assistant's Matter Server can download it, and the local network lets the server deliver it to the device. Firmware is the software stored inside the plug, bulb, sensor, or lock; OTA simply means updating that software over the network.

Start by updating Home Assistant to the current release. Then update the official Matter Server app to version 9.0 or newer. Matter Server is the controller service Home Assistant runs to talk to Matter devices. Open Settings > Matter > Devices and select the device. If an Update entity—a row in Home Assistant that shows and installs software versions—appears, Home Assistant has detected the device's standard Matter update capability. Install from that entity, keep the device powered, and give a battery device enough charge and time to finish. If no Update entity exists, Home Assistant's official docs say the device is not advertising the optional Matter OTA feature; resetting it will not create one.

This does not make firmware maintenance fully offline. Normal Matter commands can remain inside the house, but the Matter Server needs internet access to check the Connectivity Standards Alliance ledger and download a vendor-hosted file. There is also one unusually important exception: Home Assistant currently says its Matter OTA path does not work for devices using Thread—the low-power mesh network used by many smart-home sensors—while an Apple border router is active on that Thread network. If Apple routers are the only border routers, Home Assistant cannot perform the update; check Apple Home or the manufacturer's route. If the network also has a non-Apple border router, use Home Assistant's temporary power-down procedure below.

Tara's rule: let Home Assistant try the signed, standard Matter update first. Keep the vendor app as a maintenance tool only when the manufacturer has not supplied that path or the controller network blocks it.

Why This Question Is Active Right Now

The demand is specific, not theoretical. A June 18, 2025 r/homeassistant thread asked why Cync Matter bulbs and plugs showed firmware in the vendor app but not Home Assistant. An August 13, 2025 discussion asking why Matter still needed a native app drew dozens of replies. In early 2026, IKEA ALPSTUGA and KLIPPBOK owners reported the exact “Target node did not process the update file” error; BILRESA owners separately reported updates that repeatedly failed.

Then the answer changed. Home Assistant released Matter Server app 9.0 on June 23, 2026 and explicitly said over-the-air updates were more reliable. Four days later, a June 27 r/homeassistant post reported that previously failing IKEA BILRESA updates completed after the move to Matter Server 9. Community reports are evidence that the new server helps; they are not a promise that every device, border router, or vendor channel now works.

This is also a gap in TaraHome's library. Existing guides explain direct IKEA pairing, Matter during an internet outage, and Thread border-router choice. None answers who actually supplies firmware or why the vendor app sometimes remains necessary.

The Four Gates Behind a Visible Matter Update

Matter creates a common update method, but it does not force every manufacturer to use it. Home Assistant's official documentation says OTA support is optional and that it creates an Update entity only for a device that implements the feature. Home Assistant then checks the Distributed Compliance Ledger (DCL) every 12 hours. The DCL is the Connectivity Standards Alliance's signed public record for product and software information.

A Matter logo indicates certification for the product's declared Matter features; it does not guarantee that every controller exposes every feature or firmware release. As of July 9, 2026, Home Assistant's current docs still name Eve and Nanoleaf as DCL publishers, but that list is not exhaustive. The live production DCL also contains official IKEA-hosted firmware files for ALPSTUGA, KLIPPBOK, and both the BILRESA scroll-wheel and dual-button remotes. Other vendors may use a different ecosystem pipeline or their own app even when everyday Matter control is local.

Required gate Official support boundary What it means in the house Local or cloud? Likely symptom when missing
1. Device implements Matter OTA Optional in Matter; Home Assistant creates an Update entity when the device reports support. The plug, bulb, sensor, or lock knows how to request and install a standard Matter firmware file. The capability lives on the device. No Update entity at all.
2. Manufacturer publishes a usable firmware file Home Assistant checks DCL metadata; the manufacturer controls the release and download location. A newer version must be available for the exact manufacturer ID, model ID, and current firmware. Publication and download are internet services. Entity says current while the vendor app offers something newer.
3. Matter Server reaches the internet The official matter.js server says internet is required to check the DCL and download vendor firmware. Home Assistant downloads the signed firmware file on the homeowner's behalf. Cloud is needed for maintenance, not normal local commands. Refreshes find nothing or downloads cannot begin.
4. Device reaches Home Assistant's local OTA provider Home Assistant serves the file locally; discovery relies on the home network. A powered-on Apple Thread border router on the affected Thread network is a documented current blocker. The device must stay powered or awake and have a working Wi-Fi or Thread path while installing. The transfer is local after the server downloads the file. “Target node did not process the update file” or a stalled install.

Try This Order Before Reinstalling a Vendor App

1. Back up, then update Home Assistant and Matter Server

Create a current Home Assistant backup, install the current Home Assistant update, and update the official Matter Server app to 9.0 or newer. Home Assistant says version 9.0 is a drop-in replacement that migrates existing Matter data automatically and makes OTA updates more reliable. Do not switch an otherwise stable home to an old beta merely because a community post from early 2026 mentions one; the matter.js server is now the released path.

2. Look for the device's Update entity

Open Settings > Matter > Devices, select the device, and look for an Update entity or an update notification. If it is present, Home Assistant has detected the device's Matter OTA support. If it is absent, stop troubleshooting the radio: the standard Home Assistant update path is not being advertised by that device. Check the manufacturer's documentation or app rather than resetting a working pairing.

3. Refresh the update metadata if it looks stale

Home Assistant checks the DCL every 12 hours. To ask it to check sooner, open Developer Tools > Actions, choose homeassistant.update_entity, and target that device's Update entity. This refreshes the available-version information; it does not force the manufacturer to publish a file and it does not install one by itself.

4. Install under stable conditions

Start the update from the device's Update entity. Keep mains-powered devices powered. Give a battery device a healthy battery and follow the maker's instructions for waking it if needed. For Matter-over-Thread devices, make sure the device already has a stable route; do not move border routers, reboot Home Assistant, or cut power during the transfer. Some updates take several minutes and the device may briefly become unavailable while it restarts.

5. Treat the exact error as evidence

If the message is “Target node did not process the update file,” first confirm Matter Server 9.0 or newer. Then check the device's power, Thread or Wi-Fi reachability, IPv6 (the local addressing Matter uses), and multicast discovery. Multicast is the local announcement traffic that helps devices find services; it can be blocked by a strict router or separate network segment.

If Apple devices are the only Thread border routers, Home Assistant says it cannot perform the OTA; check whether Apple Home offers the update or use the manufacturer's supported route. If the same Thread network also has a working non-Apple border router, Home Assistant documents this sequence: power down all Apple border routers, wait at least 30 minutes, then retry the update. Use a maintenance window because Apple Home automations and remote access may pause while every HomePod and Apple TV home hub is off. Keep manual control available for locks, heating and cooling, and other safety devices. Bring the Apple devices back after the attempt. Do not add another border router casually just to create this workaround; one with different Thread credentials can create a separate mesh instead of fixing the first one.

6. Verify the version and the real device behavior

After the device returns, reopen its Matter details, confirm the new firmware version, and test the controls and automations that matter in the house. A version number alone is not enough. For a lock, thermostat, leak sensor, blind, or shutoff device, test the physical control and manual fallback before trusting it again.

What Current Device Examples Actually Prove

This is a maintenance guide, not a product ranking. The named devices below show the difference between an official DCL listing, a manufacturer's consumer-support path, a successful Home Assistant transfer reported by the community, and a vendor-app mismatch.

Current example Official support Local Home Assistant control Cloud or vendor-app dependency Matter, HomeKit, and community caveat
Matter-enabled Eve Energy variants and Nanoleaf Essentials Matter lights Home Assistant's current Matter docs name Eve and Nanoleaf as DCL update publishers. Confirm the exact product and version in its device details. Normal Matter control can remain local in Home Assistant. The Matter Server still needs internet to find and download the update. Vendor apps may remain useful for product-specific features and diagnostics. Home Assistant currently says its OTA path does not work while any Apple border router on that same Thread network is powered on. Mixed-router homes can use the documented temporary power-down procedure above. See Tara's Eve and Nanoleaf setup guides for the wider control paths.
IKEA ALPSTUGA, KLIPPBOK, BILRESA scroll-wheel remote, and BILRESA dual-button remote The production CSA DCL contains official IKEA-hosted firmware files for these exact models: ALPSTUGA 1.0.26, KLIPPBOK 1.0.13, and both BILRESA remotes 1.9.15 as checked July 9, 2026. These current Matter-over-Thread devices can be controlled directly by Home Assistant when paired through a compatible Thread network. Home Assistant can fetch the firmware file listed in the DCL when its server has internet. For these devices, IKEA's documented consumer path is DIRIGERA with IKEA Home smart and internet access. The firmware's official availability is not merely a community claim. Successful transfer through Home Assistant—especially reliability on a particular Thread network—is community-tested rather than an IKEA Home Assistant support promise.
Cync Matter bulbs and plugs
Models not identified in the cited report		 No Home Assistant-specific update promise was found in the primary sources used for this guide. Standard supported Matter controls can still be local after pairing and setup. In the demand thread that prompted this guide, the Cync app offered firmware that Home Assistant did not see. Treat that report as a community example of separate update catalogs, not proof that every Cync model behaves the same way.

Home Assistant, Apple, Google, Alexa, and SmartThings Do Not Share One Update Inbox

Matter multi-admin lets the same device appear in more than one controller, but each ecosystem can have its own update provider and release rules. Google documents a Matter OTA pipeline that can use either its Developer Console or the Alliance DCL. Apple tells homeowners troubleshooting HomeKit or Matter accessories to check the manufacturer's app for firmware. Home Assistant uses the DCL path described above.

Alexa and SmartThings can control shared Matter devices, but sharing a device into those apps does not prove that they will expose the same firmware at the same time. Check the controller and manufacturer documentation for that exact model. Do not add a fifth app merely to chase an update; every additional Matter controller adds another fabric, meaning another secure controller-to-device relationship, and more cleanup if the device is later reset.

HomeKit-only is a separate path. A HomeKit accessory that does not support Matter will not gain a Matter Update entity in Home Assistant. It follows Apple or manufacturer maintenance instructions, even if a HomePod or Apple TV carries its Thread radio traffic.

Five Things Not to Do When Firmware Is Missing

  • Do not factory-reset first. A reset erases controller relationships and can break names, rooms, and automations without changing the manufacturer's update support.
  • Do not open the device directly to the internet. Home Assistant downloads and serves the file; ordinary devices do not need an inbound firewall hole.
  • Do not install a random firmware file. Matter updates are signed and the device validates them. The matter.js server has developer options for custom firmware files, but those are not the normal supported homeowner path.
  • Do not assume firmware adds every missing feature. Matter exposes standardized device features; a vendor app may still contain effects, calibration, maps, energy details, or settings that the device does not expose through its Matter version.
  • Do not update every safety device at once. Stagger locks, thermostats, leak sensors, blinds, and shutoff devices so a known manual fallback remains available.

What “Local” Really Means During a Firmware Update

Home Assistant can control a Matter device locally during normal operation. If the internet fails, a supported light, plug, sensor, or thermostat can continue talking to Home Assistant over the home network. That is the important no-cloud benefit explained in Tara's Matter outage guide.

Firmware maintenance has a narrower dependency. The official Matter Server documentation says it needs internet access to check the DCL and to download the firmware file from a vendor-specific location. Home Assistant then acts as the local update provider. The Matter device does not necessarily need its own direct connection to a vendor cloud, but the Home Assistant server cannot discover or download a new release while fully offline.

The update file is not just an ordinary download. Google's official Matter OTA documentation says the manufacturer signs the payload and the device validates that signature before installing it. That is why a random file from a forum is not an acceptable substitute. Normal Matter OTA also has no homeowner rollback button: a vendor must publish another firmware file with a higher version number even when it needs to return to older firmware content.

Safety and Recovery Boundaries

  • Keep a manual fallback. Have a physical key, thermostat control, blind control, or manual water shutoff available before updating a safety-relevant device.
  • Do not interrupt power. Follow the manufacturer's instructions and avoid power-cycling a device while firmware is actively installing.
  • Save setup codes before maintenance. Photograph the Matter QR and numeric code and store them securely, even though an update should not require a reset.
  • Protect diagnostics. Home Assistant diagnostics can contain device and network identifiers. Review and redact them before posting publicly.
  • Limit vendor-app permissions. If an app is required only for maintenance, deny unrelated location, contact, camera, microphone, and background permissions where the phone allows it.

Tara's Recommendation

Use Home Assistant's standard Update entity first, keep Matter Server current, and choose future devices from manufacturers with a documented update policy. Let Home Assistant own daily local automations. Keep a vendor app or hub only when it provides firmware, calibration, diagnostics, or special features that the standard path does not expose.

For a Thread home built only around Apple TV or HomePod, accept the current official limitation instead of rebuilding a stable mesh solely for one update; check Apple Home or use the vendor route. If a working non-Apple border router is already on that same network, use Home Assistant's documented temporary Apple power-down procedure. Then test the device in Home Assistant. A boring maintenance record—device model, firmware version, update path, and last test date—is more useful than another half-configured ecosystem.

FAQ

Can Home Assistant update Matter firmware without the vendor app?

Sometimes. Home Assistant can install an update when the device implements Matter OTA and its manufacturer publishes a usable update through a channel Home Assistant can reach. Otherwise the vendor app or hub may still be required.

Why does my Matter device have no Update entity in Home Assistant?

Matter OTA is optional. Home Assistant creates an Update entity only when the device reports support for the Matter update feature. A missing entity usually means the standard Matter path is unavailable for that device.

Can Home Assistant check and download Matter firmware without internet?

No. Normal Matter control can stay local, but the Matter Server needs internet access to check the CSA ledger and download the vendor's update file. The device itself does not necessarily need direct cloud access for a Home Assistant update.

Why does a Matter update say “Target node did not process the update file”?

First update to Matter Server 9.0 or newer and check device power and Thread reachability. If Apple devices are the only Thread border routers, Home Assistant says it cannot perform the update. On a mixed network with a working non-Apple border router on the same Thread network, use a maintenance window: power down all Apple border routers, wait at least 30 minutes, retry, and then power the Apple devices back on.

Do IKEA Matter devices need DIRIGERA for firmware updates?

Not necessarily. The production CSA DCL has official IKEA firmware for ALPSTUGA, KLIPPBOK, and both BILRESA remotes, so Home Assistant can use the standard Matter OTA path when the network supports it. IKEA's documented consumer-support path for these devices remains DIRIGERA with IKEA Home smart and internet access; reliable transfer through a particular Home Assistant Thread setup is still something to test.

Can I roll back a Matter firmware update?

Not through a normal homeowner rollback button. Official Google Matter documentation says a vendor must publish another firmware file with a higher version number even when returning to older firmware content.