# How to diganosticate Zigbee problems?

**URL:** <https://community.homey.app/t/how-to-diganosticate-zigbee-problems/87286>\
**Category:** Questions & Help\
**Tags:** zigbee, homey-pro\
**Created:** [August 16, 2023, 9:54pm UTC](https://community.homey.app/t/how-to-diganosticate-zigbee-problems/87286 "2023-08-16T21:54:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Christox](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/christox/32/71278_2.png) [@Christox](https://community.homey.app/u/Christox)\
**Post date:** [August 16, 2023, 9:54pm UTC](https://community.homey.app/t/how-to-diganosticate-zigbee-problems/87286/1 "2023-08-16T21:54:25Z")

</div>

Hi,

I’m having Zigbee problems.

How the problems manifest themselves is that sporadically zigbee devices are no longer accessible. This means that they then simply no longer go to switch.

This can happen manually via the web interface as well as via flows.

Is there any way to diagnose these problems? Or any fix?

Information:

--------------- Homey Pro Overview v1.12 --------------  
Homey version: 10.0.2  
Homey model: Homey Pro (Early 2023) (4 core(s))  
Uptime: 1509.17 (0 hour, 25 minutes, 9 seconds)  
WiFi: Connected  
Ethernet: Connected  
Throttled: No (Currently: No)  
Under voltage: No (Currently: No)  
Update available: No  
Storage: 2.66 GB (1.18 GB free)

------------------ Main ---------------------  
2 Users (1 Owner, 0 Manager, 1 User, 0 Guest)  
41 Apps (39 Stable, 1 Test, 1 Development/Community Appstore, 0 SDKv2, 41 SDKv3, 1 Updateable, 0 Disabled/Crashed)  
19 Zones  
250 Notifications (Timeline)  
2 Logic Variables (1 Boolean (Yes/No), 0 Number, 1 String (Text))  
25 Flows (0 Broken, 4 Disabled)  
9 Advanced flows (0 Broken, 0 Disabled)  
0 Alarms (0 Enabled)  
16 HomeyScript scripts (0 Token/Tag)

----------------- Devices -------------------  
1 Virtual devices  
0 Infrared (database) devices  
0 Z-Wave devices (0 Unsecure, 0 Secure (S0), 0 Secure (S2 Authenticated), 0 Secure (S2 Unauthenticated), 0 Router, 0 Battery, 0 Unreachable, 2 Unknown)  
16 Zigbee devices (11 Router, 5 End device)

---

<div class="post-metadata">

**Author:** ![Bulletcather](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bulletcather/32/13738_2.png) [@Bulletcather](https://community.homey.app/u/Bulletcather)\
**Post date:** [August 17, 2023, 5:31am UTC](https://community.homey.app/t/how-to-diganosticate-zigbee-problems/87286/2 "2023-08-17T05:31:59Z")

</div>

I had this problem to.  
Lastest firmware was for me the solution.

v10.0.3-rc.4

---

<div class="post-metadata">

**Author:** ![Uniamock](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/uniamock/32/17934_2.png) [@Uniamock](https://community.homey.app/u/Uniamock)\
**Post date:** [August 20, 2023, 9:27am UTC](https://community.homey.app/t/how-to-diganosticate-zigbee-problems/87286/3 "2023-08-20T09:27:04Z")

</div>

I am on v10.0.3-rc.4 and try to add “Wiser” and “Hue without the bridge” devices - but they will only add as zigbee devices.  
Anyone, with similar issue but have found a solution - or any recommendations?

---

<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 20, 2023, 9:49am UTC](https://community.homey.app/t/how-to-diganosticate-zigbee-problems/87286/4 "2023-08-20T09:49:30Z")

</div>

I don’t see how this is relevant for this thread, but if you mean they are added as _generic_ Zigbee devices it means that there’s no support for them in any of the apps you installed.

---

<div class="post-metadata">

**Author:** ![Uniamock](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/uniamock/32/17934_2.png) [@Uniamock](https://community.homey.app/u/Uniamock)\
**Post date:** [August 20, 2023, 10:37am UTC](https://community.homey.app/t/how-to-diganosticate-zigbee-problems/87286/5 "2023-08-20T10:37:12Z")

</div>

OK got it - thx for fast response.
