# Re-add existing zigbee device automatically

**URL:** <https://community.homey.app/t/re-add-existing-zigbee-device-automatically/110005>\
**Category:** Devices\
**Tags:** app, zigbee\
**Created:** [May 17, 2024, 7:01am UTC](https://community.homey.app/t/re-add-existing-zigbee-device-automatically/110005 "2024-05-17T07:01:41Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thomas\_Buran](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thomas_buran/32/107750_2.png) [@Thomas\_Buran](https://community.homey.app/u/Thomas_Buran)\
**Post date:** [May 17, 2024, 7:01am UTC](https://community.homey.app/t/re-add-existing-zigbee-device-automatically/110005/1 "2024-05-17T07:01:41Z")

</div>

Hi everyone. I keep experiencing an issue where some Zigbee devices stop responding after a certain period, even after creating the Zigbee network anew according to the instructions, which state that routers should be added first and then end devices from their intended locations.

Whenever I notice this, I add the new device again by holding the button for 3 seconds. It tells me that the device is already added and needs to be removed first. However, I simply restart the app and the device starts working again.

So, I was wondering, is there a way to automate this process? For example, could there be a script that sends a signal to the device once an hour, and if the device does not respond, it indicates that the device is unresponsive and automatically restarts both the device and the app?

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [May 17, 2024, 8:14am UTC](https://community.homey.app/t/re-add-existing-zigbee-device-automatically/110005/2 "2024-05-17T08:14:34Z")

</div>

> [@Thomas\_Buran](#):
>
> is there a way to automate this process

Unfortunately there is not. The pairing must be still invoked on the device itself.  
There is a script however might might help you to check if device is alive (depending of device type) -

> [@A script to check sensor last update](https://community.homey.app/t/a-script-to-check-sensor-last-update/63142/25):
>
> Updated script I posted above - added counter of non responding devices - eg, in case you would like to initiate some action based on number of not-responding devices - please note this is the version I’m using, so feel free to change relevant variables below the section // Filter devices to check Changelog : 0.1 - update - converting notReportingCount to a number - if you used previous version of script, delete tag by await tag(‘notReportingCount’, null);\* 0.2 - added filtering based on dev…

or for Zigbee only

> [@A script to check sensor last update](https://community.homey.app/t/a-script-to-check-sensor-last-update/63142/39):
>
> As there is for some time options to see Lastseen timestamp for Zigbee devices, here is the script for Zigbee devices only, which might be more accurate for Zigbee devices. Thanks @Caseda for your overview script wink Version 0.3 - updated for HomeyScript v. 3.5.1 Version 0.3b - fixed for THEN card (returning TEXT value), primary use-better use is for AND card though Version 0.4 - added option to filter out routers and/or end devices Version 0.5 - added option to exclude ZONES, moved varia…

Beware of some specifics, eg. lights, unless powered on, send update in between 12-24 hours, battery powered devices sometimes on external trigger only (eg. motion) etc.

As you are probably on HP19, I would also suggest you to have a look on recommendations (if any) provided by this script :

> [@\[Community Survey\] Homey v5 ZigBee Health check and statistics collection (HomeyScript)](https://community.homey.app/t/community-survey-homey-v5-zigbee-health-check-and-statistics-collection-homeyscript/44231):
>
> Hi Guys, With the ZigBee improvements in Homey Firmware v5 and reading about all tips for building and fixing a good ZigBee mesh network I wanted to know how big ZigBee Meshes grow on Homey and how Happy the Homey users are with it. To collect all Data I ask you to run a [HomeyScript](https://homey.app/en-gb/app/com.athom.homeyscript/HomeyScript/) on your Homey V5 and report back some results here. The script is placed on my Github as it is to large for here. For copying the script to HomeyScript you can better open it [RAW here!](https://raw.githubusercontent.com/Dijker/nu.Dijker.UnseenHomeyScripts/master/ZigBeeHealth.js) How to run the script: I…

_(might not be however compatible with latest HomeyScript)_

---

<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:** [May 17, 2024, 1:12pm UTC](https://community.homey.app/t/re-add-existing-zigbee-device-automatically/110005/3 "2024-05-17T13:12:16Z")

</div>

> [@Thomas\_Buran](#):
>
> For example, could there be a script that sends a signal to the device once an hour, and if the device does not respond,

That just shouldn’t be necessary in a healthy zigbee mesh, and sounds like a workaround ‘fix’.

Imho it makes more sense to solve the cause of the ‘silent’ sensors issue.

Zigbee is a sort-of-standard.  
Several manufacturers use their own flavour, which does not easily work together with devices from other brands, _also depending on which zigbee controller is used_.

With my Pro 19, Aqara sensors stopped sending updates just like you described.  
That started to occur after I added Ikea Tradfri lights.  
It seems when a Aqara sensor has started using such a light as zigbee hop, it can’t communicate to the mesh anymore, and it also doesn’t seem to be able to switch to an other hop.

However, these problems do not occur when I use zigbee2mqtt as controller 🤷‍♂️

With Homey as zigbee controller:  
after I replaced the Ikea lights with Lidl lights, the Aqara’s work 100% fine.

This is just an example.

Most probably some of your zigbee router devices (=almost any mains powered zigbee device) aren’t 100% compatible with some of your sensors, _when using Homey as zigbee controller_;

Either replace the routers OR the sensors, or migrate your zigbee mesh to zigbee2mqtt

---

<div class="post-metadata">

**Author:** ![Thomas\_Buran](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thomas_buran/32/107750_2.png) [@Thomas\_Buran](https://community.homey.app/u/Thomas_Buran)\
**Post date:** [May 17, 2024, 1:44pm UTC](https://community.homey.app/t/re-add-existing-zigbee-device-automatically/110005/4 "2024-05-17T13:44:19Z")

</div>

I bought Homey precisely because I didn’t want to have a million different hubs forming my smart home. Now, after several years, I find out that Homey can’t properly (in some cases) unify various products from different brands. That’s “great.”

Anyway, I have one device from IKEA in my Zigbee network, which is an end-device, a switch. Then, I have a Philips light as a router (maybe this is the problem because when I look at the network, many of the devices using it as a router are failing). Additionally, I have one Gledopto router, and the rest are Sonoff and Aqara devices.

While writing this comment, I noticed that my routing has suddenly changed, and the mentioned Philips light is no longer used as a router and has been replaced by the Gledopto. So, my question is: is it possible to disable certain devices from acting as routers?

---

<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:** [May 17, 2024, 2:13pm UTC](https://community.homey.app/t/re-add-existing-zigbee-device-automatically/110005/5 "2024-05-17T14:13:33Z")

</div>

> [@Thomas\_Buran](#):
>
> is it possible to disable certain devices from acting as routers?

Unfortunately not

---

<div class="post-metadata">

**Author:** ![Floppus](https://avatars.discourse-cdn.com/v4/letter/f/898d66/32.png) [@Floppus](https://community.homey.app/u/Floppus)\
**Post date:** [May 18, 2024, 7:45pm UTC](https://community.homey.app/t/re-add-existing-zigbee-device-automatically/110005/7 "2024-05-18T19:45:31Z")

</div>

Why are you just not honest to people asking questions and tell them Homey itself is the cause there _IS_ no healthy Zigbee environment?

@op  
There is a known Zigbee issue that for many keeps throwing out zigbee as a whole.  
See last stable release note

> **[Homey Pro (Early 2023) Changelog](https://homey.app/en-us/wiki/homey-pro-early-2023-firmware-changelog/)**

If you have an IKEA air Quality zigbee device, I was told in pursuit of my legal case that that one caused more issues than others. Worth a try. Of course they didn’t bother to inform anyone else.

Just be aware information is limited, issues remain unresolved, and Homey has been more than overtaken by prebuilt Home Assistant boxes for half the price.

There, indeed if you want for some reason to readd a device, just pair it again and all the automations keep working.

Get out while you can, I did.

> [@Homey don't find zigbee units after last updated to version 10.0.6(09.02.2024)](https://community.homey.app/t/homey-dont-find-zigbee-units-after-last-updated-to-version-10-0-6-09-02-2024/103620/88):
>
> The situation is absolutely fantastic! Yes, some things require careful reading instructions and checking some stuff. But anyone who already did a cloud integration with API keys and such for Homey (anything beyond the very basic) will easily get things set up quickly. The Home Assistant box from above came completely preconfigured with essential tools and zigbee dongle installed. It took me one day in between work to set up the devices, today to customize dashboards. Standard dashboards are …

---

<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:** [May 19, 2024, 12:21am UTC](https://community.homey.app/t/re-add-existing-zigbee-device-automatically/110005/8 "2024-05-19T00:21:48Z")

</div>

Excuse me? I’m honest, but I try to keep in mind this is a Homey forum, not a _anti_-Homey forum.  
I think it’s not classy to tell everyone: “hey ditch Homey, and go use zigbee2mqtt, and all of your problems are gone”, before trying to solve things first.

And I’ve had my share of grey hairs with z2m as well, if you believe me, which I doubt 🤣  
Nothing is 24/7 100% perfect, believe it or not.

Also, with my Pro 2019 I had no issues with zigbee, except for the Ikea - Aqara ‘clash’.  
So to me, you are not honest to write just this:

> [@Floppus](#):
>
> Homey itself is the cause there _IS_ no healthy Zigbee environment

Yes, I moved my zigbee to z2m out of curiousity ánd because of the support for much more devices, and way quicker support for the latest devices. I’m very happy with it.  
When folks ask me if I know a better zigbee implementation than Homey has to offer, I’d be happy to tell it’s z2m.

PS  
I had your account muted, but I was curious if you had some useful info. Not. It’s going back to mute I can tell you. You seem to think you are hired by HA appearantly 🤓
