# Matter OTA Firmware updates

**URL:** <https://community.homey.app/t/matter-ota-firmware-updates/150684>\
**Category:** Questions & Help\
**Created:** [February 6, 2026, 12:33pm UTC](https://community.homey.app/t/matter-ota-firmware-updates/150684 "2026-02-06T12:33:22Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![EdP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edp/32/42069_2.png) [@EdP](https://community.homey.app/u/EdP)\
**Post date:** [February 6, 2026, 12:33pm UTC](https://community.homey.app/t/matter-ota-firmware-updates/150684/1 "2026-02-06T12:33:23Z")

</div>

Was this silently released? Or is my Google Nest doing this?

![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/4/84b610a8313d6334f1948e40011b00986ac29ecb.png)

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [February 6, 2026, 3:30pm UTC](https://community.homey.app/t/matter-ota-firmware-updates/150684/2 "2026-02-06T15:30:34Z")

</div>

Your Google Nest has no influence on the Matter device, since it’s linked with Homey via the cloud.

Is it a Matter-over-WiFi device? In that case, it could have also updated from the internet by itself.

---

<div class="post-metadata">

**Author:** ![Olex](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/olex/32/79016_2.png) [@Olex](https://community.homey.app/u/Olex)\
**Post date:** [February 6, 2026, 3:47pm UTC](https://community.homey.app/t/matter-ota-firmware-updates/150684/3 "2026-02-06T15:47:21Z")

</div>

I have my Ikea devices added to Apple home and then shared to Homey.

When the devices is updated in Apple home, I also get the same message as you in Homey.

---

<div class="post-metadata">

**Author:** ![EdP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edp/32/42069_2.png) [@EdP](https://community.homey.app/u/EdP)\
**Post date:** [February 6, 2026, 4:31pm UTC](https://community.homey.app/t/matter-ota-firmware-updates/150684/4 "2026-02-06T16:31:26Z")

</div>

It’s connected with Homey SHS over thread and connected over thread with Google Nest as well. OTA firmware updates for Matter devices were to be released by Homey early 2026, so maybe they already did it in silence.

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [February 6, 2026, 6:16pm UTC](https://community.homey.app/t/matter-ota-firmware-updates/150684/5 "2026-02-06T18:16:26Z")

</div>

> [@EdP](#):
>
> over thread with Google Nest as well

AFAIK that is not possible (Thread works the same as ZigBee, right?)

---

<div class="post-metadata">

**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\
**Post date:** [February 6, 2026, 6:17pm UTC](https://community.homey.app/t/matter-ota-firmware-updates/150684/6 "2026-02-06T18:17:03Z")

</div>

> [@EdP](#):
>
> Homey SHS over thread

Gues you mean over matter… SHS doesn’t support thread by itself. So if it is a thread device it is thread to your TBR and matter to Homey SHS.

Probably the TBR did the Firmware updates

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [February 6, 2026, 8:56pm UTC](https://community.homey.app/t/matter-ota-firmware-updates/150684/7 "2026-02-06T20:56:51Z")

</div>

> [@EdP](#):
>
> so maybe they already did it in silence.

They def will let everyone know when OTA finally is possible 🍾

---

<div class="post-metadata">

**Author:** ![EdP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edp/32/42069_2.png) [@EdP](https://community.homey.app/u/EdP)\
**Post date:** [February 7, 2026, 12:27am UTC](https://community.homey.app/t/matter-ota-firmware-updates/150684/8 "2026-02-07T00:27:34Z")

</div>

Homey SHS is managing it’s own Thread Fabric, so that means it’s connected over thread.

SHS is no TBR, but with an external TBR it supports thread.

---

<div class="post-metadata">

**Author:** ![EdP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edp/32/42069_2.png) [@EdP](https://community.homey.app/u/EdP)\
**Post date:** [February 7, 2026, 12:31am UTC](https://community.homey.app/t/matter-ota-firmware-updates/150684/9 "2026-02-07T00:31:04Z")

</div>

Nope, it’s not the same. Zigbee devices connect to one router, but matter devices can connect to multiple.

---

<div class="post-metadata">

**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\
**Post date:** [February 7, 2026, 7:45am UTC](https://community.homey.app/t/matter-ota-firmware-updates/150684/10 "2026-02-07T07:45:19Z")

</div>

Yes, a device can connect to multiple TBR’s within the same thread network as failover. If I judge your configuration correctly you effectively are running 2 separate thread networks that connect to each other over matter.

I can imagine a device that’s updates just broadcasts a message saying it updated and Homey reacted on it with posting a timeline message.

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [February 7, 2026, 7:55am UTC](https://community.homey.app/t/matter-ota-firmware-updates/150684/11 "2026-02-07T07:55:45Z")

</div>

Since Homey SHS doesn’t have a Thread radio, how can it create and manage its own Thread fabric? You need a Thread radio for that.

---

<div class="post-metadata">

**Author:** ![EdP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edp/32/42069_2.png) [@EdP](https://community.homey.app/u/EdP)\
**Post date:** [February 7, 2026, 9:10am UTC](https://community.homey.app/t/matter-ota-firmware-updates/150684/12 "2026-02-07T09:10:46Z")

</div>

![IMG_5206](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/1/f1d0eeaf72960c91fef4cb2b3ae6017dc0ccf448.jpeg)

#1 is Google

#2 is created by Homey

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [February 7, 2026, 9:24am UTC](https://community.homey.app/t/matter-ota-firmware-updates/150684/13 "2026-02-07T09:24:12Z")

</div>

Ah right, we’re confusing Thread with Matter here. Fabrics are a Matter thing, and SHS _does_ support Matter. But it doesn’t support Thread.

---

<div class="post-metadata">

**Author:** ![praseodym](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/praseodym/32/121042_2.png) [@praseodym](https://community.homey.app/u/praseodym)\
**Post date:** [February 13, 2026, 10:44am UTC](https://community.homey.app/t/matter-ota-firmware-updates/150684/14 "2026-02-13T10:44:02Z")

</div>

I’ve seen this same notification when triggering OTA firmware updates to Matter over Thread devices from Apple Home, so I suspect in your case the OTA update is coming from Google Nest. Is there no firmware update history in Google Nest?
