# Zigbee stopped working/broken

**URL:** <https://community.homey.app/t/zigbee-stopped-working-broken/19120>\
**Category:** Questions & Help\
**Tags:** zigbee\
**Created:** [October 10, 2019, 8:01pm UTC](https://community.homey.app/t/zigbee-stopped-working-broken/19120 "2019-10-10T20:01:10Z")\
**Posts on this page:** 8\
**Page:** 3

<div class="post-metadata">

**Author:** ![Rocodamelshekima](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rocodamelshekima/32/8209_2.png) [@Rocodamelshekima](https://community.homey.app/u/Rocodamelshekima)\
**Post date:** [December 15, 2020, 11:02am UTC](https://community.homey.app/t/zigbee-stopped-working-broken/19120/41 "2020-12-15T11:02:51Z")

</div>

> [@Erwin\_De\_Jong](#):
>
> Maybe someone also knows if there is an easy way to check if all devices/apps are supported ?

[There is](https://community.homey.app/t/apps-currently-not-working-on-homey-v5/35748)!

---

<div class="post-metadata">

**Author:** ![B4ZZY](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/b4zzy/32/40486_2.png) [@B4ZZY](https://community.homey.app/u/B4ZZY)\
**Post date:** [July 28, 2021, 1:39pm UTC](https://community.homey.app/t/zigbee-stopped-working-broken/19120/42 "2021-07-28T13:39:35Z")

</div>

Hi All,  
I had the same issue.  
This trick solved the problem for me…

1. Hold your Homey upside down for 1 minute to enter recovery mode.
2. When Homey enters the recovery, please go to [setup.athom.com](http://setup.athom.com/) with a laptop or desktop.
3. Select your preferred language, Press the ALT (Option on Mac) button to make continue in browser visible and click “continue in browser”, shown in grey.
4. While entering your WiFi information hold your ALT/Option button and keep holding it until you get the “Download full update” option.
5. When this process is done, please press the button “keep your data”, and let Homey finish the setup process.

Hope this solves it for you too

---

<div class="post-metadata">

**Author:** ![MarkT](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/markt/32/3061_2.png) [@MarkT](https://community.homey.app/u/MarkT)\
**Post date:** [January 24, 2022, 10:04pm UTC](https://community.homey.app/t/zigbee-stopped-working-broken/19120/43 "2022-01-24T22:04:21Z")

</div>

This worked for me, but I wanted to add a quick update; in order for this to work with current versions of Google Chrome and Edge (as of Jan 2022), because of security changes, you have to:

1. Run:  
`chrome.exe --disable-web-security --disable-gpu --user-data-dir=C:/tmp/chrome`

2. Type chrome://flags and then search for and set the following:  
`Block insecure private network requests = Disabled`  
`Consider Same Party cookies to be first-party = Enabled`

3. Restart Chrome by closing the browser and then running the command in (1) again - i.e.:  
`chrome.exe --disable-web-security --disable-gpu --user-data-dir=C:/tmp/chrome`

4. Follow the steps outlined by @B4ZZY.

5. Close Chrome and (if you wish) delete the Chrome profile that was created at C:\tmp\chrome. Because you used a temporary profile, none of this should make it into your standard Chrome (which will remain secured by what are ultimately good policies).

If you don’t do the above extra steps, you will see errors in the Chrome console when running through the athom setup process. I believe this is because:

1. The setup process makes a call to Homey on a local IP address, which is now denied because this is considered a “more private” address as per: [Private Network Access update: Introducing a deprecation trial - Chrome Developers](https://developer.chrome.com/blog/private-network-access-update/)

2. The setup process uses cookies which are accessed via both an https and an http version of the site and this is now denied by default as per: [Schemeful Same-Site](https://web.dev/schemeful-samesite/)

---

<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:** [January 25, 2022, 6:04am UTC](https://community.homey.app/t/zigbee-stopped-working-broken/19120/44 "2022-01-25T06:04:19Z")

</div>

Or use Firefox.

---

<div class="post-metadata">

**Author:** ![MarkT](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/markt/32/3061_2.png) [@MarkT](https://community.homey.app/u/MarkT)\
**Post date:** [January 25, 2022, 5:20pm UTC](https://community.homey.app/t/zigbee-stopped-working-broken/19120/45 "2022-01-25T17:20:02Z")

</div>

For now.

> Additionally, browsers including [Chrome](https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html) and [Firefox](https://groups.google.com/g/mozilla.dev.platform/c/F163Jz32oYY) are working toward upgrading or blocking passive mixed content.

Usually, with things like this, it doesn’t take long before all browsers follow suit. Athom will be able to fix the issue by changing their setup process, but as I’m not sure setup in a browser is considered “official” given the need to hold _alt_ to access it, they may choose not to do so.

Just trying to save research time for anyone who hits the same issue I did.

---

<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:** [January 25, 2022, 6:53pm UTC](https://community.homey.app/t/zigbee-stopped-working-broken/19120/46 "2022-01-25T18:53:50Z")

</div>

> [@MarkT](#):
>
> For now.

True that.

---

<div class="post-metadata">

**Author:** ![daniel\_pro](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daniel_pro/32/120739_2.png) [@daniel\_pro](https://community.homey.app/u/daniel_pro)\
**Post date:** [September 6, 2025, 9:06am UTC](https://community.homey.app/t/zigbee-stopped-working-broken/19120/47 "2025-09-06T09:06:02Z")

</div>

For others that are trying to use this flow on Mac, with Google Chrome:

## Homey Network Setup Fix for Mac (Chrome)

1. **Enter Homey Recovery Mode**

2. **Launch Chrome with Security Disabled**

3. **Disable Chrome Security Flags**

4. **Run Homey Setup**

---

<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:** [September 6, 2025, 8:29pm UTC](https://community.homey.app/t/zigbee-stopped-working-broken/19120/48 "2025-09-06T20:29:27Z")

</div>

> [@daniel\_pro](#):
>
> Go to [setup.athom.com](http://setup.athom.com)

But, this is over 3 years old and not needed anymore…

Everything can be done per Homey app.  
[https://support.homey.app/hc/en-us/articles/360012077534-Restarting-Homey-Pro-to-Recovery-Mode](https://support.homey.app/hc/en-us/articles/360012077534-Restarting-Homey-Pro-to-Recovery-Mode)

> [@\[HowTo\]\[Pro\] Restarting Homey Pro to Recovery Mode - Adv. Options From Mobile](https://community.homey.app/t/howto-pro-restarting-homey-pro-to-recovery-mode-adv-options-from-mobile/61222):
>
> This option is only for Homey (Pro) models “Early 2016”, “Early 2018” and “Early 2019” so Only the White Ball’s Sometimes you need the extra options, things hidden for normal use, for example: Full Firmware download Complete Reset to sell your old Homey Or maybe you just want to change Homey’s WiFi. There are now a couple of extra options in the mobile Apps, so no need to use an FireFox or Chome Browser with flags enabled to press the Alt- key on your keyboard. Just use your App from no…

[Previous page](https://community.homey.app/t/zigbee-stopped-working-broken/19120.md?page=2)
