I recently had an update (yesterday or today). Now Zigbee is not working:
I have done two restarts of Homey, but no luck. I just pulled the plug. Let’s wait a few minutes. In the meantime I am wondering if someone has a different solution
What do you mean? Your Zigbee overview is empty except the single row (Homey itself) in your screenshot?
I think your Homey might be rebuilding its Zigbee network. Let it sit for a while (do not restart).
(Most of) The route info will be updated once Homey gets the necessary info from the Zigbee network / once you start using the devices. That info needs to be rebuild after every reboot.
One of the recent Homey OS updates also updated the firmware of the Zigbee radio. Not sure whether you installed that update recently.
I will let it sit. However it was like this when I got home. Completely unresponsive. Is the question mark in the coordinator identification correct?
I did install the most recent update. No preview though… I stopped doing that 
I suppose so. It’s exactly the same in my case on my Homey Pro 2026.
Thanks for confirming
I had the same on an update about 3 weeks back (Homey Pro 2026).
My zigbee had worked flawlessly until then.
I had to “repair” all my zigbee devices (go around push repair on homey app, and press the physical reset buttons on the devices) to make em work again.
I am still struggling with slow zigbee network. all my pwered zigbee devices has a TX error of about 20% after I rebuilt the routes.
I am in contact with support but so far we haven’t been able to pin point whats causing it unfortunatly
Mine seems to be working again.
The ? Question mark is actually in the “Last Seen” column, it is just the size of the window you have it in has the columns sized so it appears next to the word “coordinator” in the type column.
The Last Seen column contains the amount of time since the Zigbee coordinator last saw traffic from that device. If there is no time data it just shows a “?” question mark. The Homey Pro is the coordinator, and it can always see itself, so there is no time data to display.
If you ask me Honey should be less vain and stop looking at itself 
Have you tried running a WiFi scanning utility to see what 2.4GHz WiFi channels are congested in your area, and to make sure your own WiFi isn’t stomping all over your Zigbee network (that also uses 2.4GHz… along with Thread and Bluetooth). There are lots of WiFi scanning apps available in the Apple/Google app stores for mobiles.
The only way to change your Zigbee channel (and consequently your Thread channel too, as they use the same chip on Homey) is by resetting your network in the developer tools web page, which also tells you which channel Zigbee is currently using.
You obviously can’t change your neighbours WiFi channels, but you can change your own, and try to shift your Zigbee and WiFi as far apart as possible to minimise interference.
I have my 3 WiFi access points set to channels 2, 5 & 7 to avoid the worst interference from neighbours, and stay well clear of my two Zigbee networks on channels 15 (Aqara M3 Hub) and 25 (Homey Pro). It’s damn near impossible to completely avoid interference these days with everything being connected, especially in the most congested and overcrowded 2.4GHz band (also used by microwave ovens… why devices in your kitchen can go offline sometimes ha ha) but you can choose your battles, and minimise the interference.
Limiting your 2.4GHz WiFi to 20MHz channel width, instead of 40MHz can also help reduce Zigbee interference. But the consequence is reducing the bandwidth for your IoT devices that will be stuck with 2.4GHz WiFi. But it doesn’t impact things like you mobile or laptop that can use 5 or 6GHz WiFi.
This might help:
Clear with regards to the ? It was just new to me as I never really paid attention.
Yeah, scanning the network I have done the previous time when the Zigbee network was dramatically slow. This time it was not just slow it was just not working, Me restarting the Homey etc of course did not help.
In this case it was just a matter of rebuilding the network. Zigbee continues to be a pain in the behind at times. Let’s hope gradually moving to Matter over Thread will finally solve this.
I have found Matter over Thread to be far more troublesome than Zigbee so far. Hopefully Homey’s implementation of Thread will improve and become more stable and start to play nicely with other ecosystems over time.
Hi
Ye I used a wifi scanner and there isn’t any strong signals from any of my neighbours wifi around the Homey
I’ve checked that my Wifi is running on channel 4, and Zigbee is on channel 25.
I do not have any BT or Thread devices running through my Homey
It all happened after an update that bricked my zigbee routes, so I had to “repair” all my Zigbee devices. After that it started to act up
It’s not just if they are connected to you Homey or not, they still transmit signals in your home in the same frequency band as your Homey’s Zigbee network. You may not even realise with some devices that they are using Bluetooth. My WiFi Govee lights also transmit Bluetooth to communicate with the mobile app. All Thread devices also transmit Bluetooth for pairing and talking to mobile devices. My Samsung TV remote uses Bluetooth (despite not having a Bluetooth logo or name anywhere on it).
All I’m trying to say is that the 2.4GHz frequency band is one of if not the most over used fequency bands there is.
Have you tried looking on the developers tools web page on your Homey at the Zigbee page, to see if that shows any problem devices or errors? It can be found at this URL:
OTOH, Homey seems to be exceptionally sensitive to 2.4Ghz congestion/interference.
I’m using Z2M with a €20 dongle, and to be honest, I don’t know the WiFi channels nor the Zigbee channel that I’m using. It just works. And that’s with 100+ WiFi/BLE/Thread/Zigbee devices spread around the house (and a microwave that never causes devices in my kitchen to go offline).
I know from other Homey users that migrated to Z2M that it almost instantly cleared all their Zigbee issues.
Ye I know it’s crowded. Its just weird that it happened the same day Homey updated to v13.5.0.
I have 41 Zigbee devices and I added a screenshot here
I of course know that devices with long routes that are placed far away from the hub will have problems, and there is also a high percentege of tx errors on my batterydevices (also understandable)
But as you can see, devices that is even next to the Homey shows a TX error rate at around 20%
I can walk in to a room and lights go on instantly, and then 10min later, no reaction 
Like device number 3 is 90cm from the Homey pro, and it still gives me errors like “Can’t reach the device, is it turned on?” and “timeouts”
I have about 90 Zigbee devices, and a growing number of Thread devices (they use the same chip controller, antennas and channel (25 in my case). I do have some occasional problems with Aqara FP300 presence sensors (but I believe this to me more with the firmware of the FP300’s and the Aqara app on Homey).
You have to make sure you have plenty of permanently mains powered Zigbee router devices spread evenly throughout your home, for the sleepy battery end devices to connect to. Or no matter how close your battery devices are, you are likely to have connection issues. I use Zigbee bulbs and smart plugs in every room to form my mesh network… then after they are all connected, start adding the battery presence, contact, temp & humidity sensors, and wireless buttons etc.
And you need to remember that Homey firmware updates require your Homey to reboot as part of the update process, which which will temporarily cause some Zigbee devices disruption for a short while after, until everything rejoins the network and reports in. It’s important to give it time after an update to re-mesh, changes or further reboots etc will cause prolonged issues.
