# Firmware update of devices in Homey

**URL:** <https://community.homey.app/t/firmware-update-of-devices-in-homey/11641>\
**Category:** Devices\
**Created:** [April 9, 2019, 12:35pm UTC](https://community.homey.app/t/firmware-update-of-devices-in-homey/11641 "2019-04-09T12:35:54Z")\
**Posts on this page:** 12\
**Page:** 3

<div class="post-metadata">

**Author:** ![Vincent\_Vans](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vincent_vans/32/16788_2.png) [@Vincent\_Vans](https://community.homey.app/u/Vincent_Vans)\
**Post date:** [February 1, 2023, 11:29am UTC](https://community.homey.app/t/firmware-update-of-devices-in-homey/11641/43 "2023-02-01T11:29:52Z")

</div>

Does anyone know if OTA will be a part of the Matter inplementation? I googled it but can’t find any information about this.

---

<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 1, 2023, 11:55am UTC](https://community.homey.app/t/firmware-update-of-devices-in-homey/11641/44 "2023-02-01T11:55:20Z")

</div>

> [@Vincent\_Vans](#):
>
> Does anyone know if OTA will be a part of the Matter inplementation?

I don’t think even Athom knows this, but given the lack of OTA support for Zigbee and Z-Wave I don’t think they will implement it.

---

<div class="post-metadata">

**Author:** ![torarnv](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/torarnv/32/83065_2.png) [@torarnv](https://community.homey.app/u/torarnv)\
**Post date:** [August 15, 2023, 9:50pm UTC](https://community.homey.app/t/firmware-update-of-devices-in-homey/11641/45 "2023-08-15T21:50:51Z")

</div>

Is there any way to run Zigbee2MQTT on the Homey itself, so I don’t need to buy a separate Zigbee dongle just to get OTA updates?

Alternatively, can I expose Homey’s Zigbee device via the SSH sandbox over the network?

---

<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:** [August 16, 2023, 5:13am UTC](https://community.homey.app/t/firmware-update-of-devices-in-homey/11641/46 "2023-08-16T05:13:10Z")

</div>

> [@torarnv](#):
>
> Is there any way to run Zigbee2MQTT on the Homey itself

AFAIK, the Linux OS that runs on Homey doesn’t have direct access to the Zigbee hardware (like you would have when using a USB dongle), but there’s an ESP32 in between. If so, that sort of proprietary setup would make it impossible to get Z2M (or any other Zigbee implementation) to access the Zigbee chip.

---

<div class="post-metadata">

**Author:** ![torarnv](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/torarnv/32/83065_2.png) [@torarnv](https://community.homey.app/u/torarnv)\
**Post date:** [August 16, 2023, 7:38pm UTC](https://community.homey.app/t/firmware-update-of-devices-in-homey/11641/47 "2023-08-16T19:38:22Z")

</div>

Ah, so I won’t be able to forward the Zigbee serial device from the container over TCP to Z2M either. I don’t suppose there’s a “jailbreak” for Homey that allows access to the HW for these use-cases?

---

<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:** [August 16, 2023, 7:47pm UTC](https://community.homey.app/t/firmware-update-of-devices-in-homey/11641/48 "2023-08-16T19:47:00Z")

</div>

> [@torarnv](#):
>
> I don’t suppose there’s a “jailbreak” for Homey that allows access to the HW

Correct,  
At least not that we know at this moment.  
(And I really don’t expect it to come although it probably technically could be possible)

---

<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:** [August 17, 2023, 5:46am UTC](https://community.homey.app/t/firmware-update-of-devices-in-homey/11641/49 "2023-08-17T05:46:35Z")

</div>

> [@torarnv](#):
>
> I don’t suppose there’s a “jailbreak” for Homey that allows access to the HW for these use-cases?

There is a jailbreak available, but again, the hardware is proprietary so you won’t be able to achieve much by it.

---

<div class="post-metadata">

**Author:** ![torarnv](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/torarnv/32/83065_2.png) [@torarnv](https://community.homey.app/u/torarnv)\
**Post date:** [August 17, 2023, 10:17am UTC](https://community.homey.app/t/firmware-update-of-devices-in-homey/11641/50 "2023-08-17T10:17:23Z")

</div>

Ah, thanks, I saw the topic in the other forum now. So even if the serial device is available in `/dev/`, it’s not something Z2M can talk to as the communication/protocol with the device is not known?

I saw this post about adding additional ZWave controllers as client devices to Homey: [Z -Stick Gen 5 (+) as Secondary Controller in Homey : Aeotec Help Desk](https://aeotec.freshdesk.com/support/solutions/articles/6000263528-z-stick-gen-5-as-secondary-controller-in-homey) and doing UTA updates via that, without having to remove and re-add all devices from Homey.

Is something along those lines possible if I do get a USB Zigbee dongle? And run Z2M/ZHA for the update ?

---

<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:** [August 17, 2023, 10:24am UTC](https://community.homey.app/t/firmware-update-of-devices-in-homey/11641/51 "2023-08-17T10:24:40Z")

</div>

> [@torarnv](#):
>
> So even if the serial device is available in `/dev/`

~~It won’t be, that’s what I’m trying to say 🥴~~

Apologies, I was wrong: the Zigbee controller should be available as `/dev/ttyZigbeeNCP`. So I guess in theory, if you jailbreak your Homey you might be able to use it, although you probably have to make sure that you have exclusive access to the device (and not have the rest of Homey core crash because it can’t access it anymore).

> [@](#):
>
> I saw this post about adding additional ZWave controllers as client devices to Homey: [Z -Stick Gen 5 (+) as Secondary Controller in Homey : Aeotec Help Desk](https://aeotec.freshdesk.com/support/solutions/articles/6000263528-z-stick-gen-5-as-secondary-controller-in-homey) and doing UTA updates via that, without having to remove and re-add all devices from Homey.
> 
> Is something along those lines possible if I do get a USB Zigbee dongle? And run Z2M/ZHA for the update ?

I don’t think Zigbee has a similar concept (using a “secondary controller”).

---

<div class="post-metadata">

**Author:** ![torarnv](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/torarnv/32/83065_2.png) [@torarnv](https://community.homey.app/u/torarnv)\
**Post date:** [August 17, 2023, 12:25pm UTC](https://community.homey.app/t/firmware-update-of-devices-in-homey/11641/52 "2023-08-17T12:25:38Z")

</div>

Interesting, thanks for the details @robertklep ! I’ll post here if I end up pursuing that avenue further 🙂

---

<div class="post-metadata">

**Author:** ![OH2TH](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oh2th/32/111414_2.png) [@OH2TH](https://community.homey.app/u/OH2TH)\
**Post date:** [December 23, 2025, 7:37am UTC](https://community.homey.app/t/firmware-update-of-devices-in-homey/11641/53 "2025-12-23T07:37:47Z")

</div>

See also

> [@🎙️ The Homey Podcast | Megathread](https://community.homey.app/t/the-homey-podcast-megathread/113474/251):
>
> New Homey Podcast (#12) available with topics: Introduction Our week in smart home New Homey Apps Looking back at 2025 OTA (device) updates Homey Self-Hosted Server Python support for Homey Apps Looking ahead at 2026 [[The Homey Podcast #12 • Homey Self-Hosted Server, New Partners, Looking back at 2025 & more] ](https://www.youtube.com/watch?v=mB9yb7CW58c)

---

<div class="post-metadata">

**Author:** ![deejayreissue](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/deejayreissue/32/81912_2.png) [@deejayreissue](https://community.homey.app/u/deejayreissue)\
**Post date:** [December 23, 2025, 11:56am UTC](https://community.homey.app/t/firmware-update-of-devices-in-homey/11641/54 "2025-12-23T11:56:57Z")

</div>

Whatever your opinions about Thread, the future proofing argument is pretty clear

Move devices over to Matter from Zigbee or Z Wave.

I have a lot of devices I can’t currently update the firmware because companies like Eve can’t be bothered to build an Android app.

Well done Athom team!

[Previous page](https://community.homey.app/t/firmware-update-of-devices-in-homey/11641.md?page=2)
