# Z-wave network inclusion

**URL:** <https://community.homey.app/t/z-wave-network-inclusion/26098>\
**Category:** Ideas & Suggestions\
**Created:** [February 19, 2020, 10:10am UTC](https://community.homey.app/t/z-wave-network-inclusion/26098 "2020-02-19T10:10:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![josjg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/josjg/32/12397_2.png) [@josjg](https://community.homey.app/u/josjg)\
**Post date:** [February 19, 2020, 10:10am UTC](https://community.homey.app/t/z-wave-network-inclusion/26098/1 "2020-02-19T10:10:15Z")

</div>

I am badly in need of network inclusion for my z-wave devices. I am regularly “loosing” z-wave device functionality though the app (although the devices still work via the developer page). The only solution at the moment would be disconnecting the Homey and placing it close to the device (most of them are installed in wall boxes) to exclude/include them again in order to regain the functionality.

In a post ([Is my Homey "dead-ish" or is z-wave transmission power very low?](https://community.homey.app/t/is-my-homey-dead-ish-or-is-z-wave-transmission-power-very-low/1807)) dated back september 2018 network inclusion is already mentioned:

> Homey does not (yet) support inclusion over the mesh network…

The “not yet” now is 1 year and 5 months old. Is network inclusion impossible on the current hardware or just low on the feature request list?

I think that network inclusion would immensely facilitate this task and add greatly to the user friendliness of Homey!!

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [February 19, 2020, 11:02am UTC](https://community.homey.app/t/z-wave-network-inclusion/26098/2 "2020-02-19T11:02:01Z")

</div>

The feature is most likely really, really low on the list as the closer by inclusion does work, and Athom just doesn’t have the man power.  
Rather a message to the support email will help more, as just mentioning it here, a place where Athom doesn’t really read/respond, it will stay really low on the todo list.

It isn’t a hardware limitation to answer that question.

---

<div class="post-metadata">

**Author:** ![josjg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/josjg/32/12397_2.png) [@josjg](https://community.homey.app/u/josjg)\
**Post date:** [February 19, 2020, 11:18am UTC](https://community.homey.app/t/z-wave-network-inclusion/26098/3 "2020-02-19T11:18:06Z")

</div>

> [@Caseda](#):
>
> It isn’t a hardware limitation to answer that question

Thanks. That (the hardware) is the good news 👍  
The bad news, unfortunately, seems to be the manpower issue. That has become very clear to me the last few months. Athom seems to have a huge problem transiting from start-up to scale-up…

I posted this “feature request” here in “ideas & suggestions” because it seemed to be the right place and I could not find a “feature request” form like there is with device requests. Or am I missing something?

---

<div class="post-metadata">

**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\
**Post date:** [February 19, 2020, 11:31am UTC](https://community.homey.app/t/z-wave-network-inclusion/26098/4 "2020-02-19T11:31:46Z")

</div>

[Feature request form](http://go.athom.com/request-homey-feature)

---

<div class="post-metadata">

**Author:** ![josjg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/josjg/32/12397_2.png) [@josjg](https://community.homey.app/u/josjg)\
**Post date:** [February 19, 2020, 4:32pm UTC](https://community.homey.app/t/z-wave-network-inclusion/26098/5 "2020-02-19T16:32:03Z")

</div>

Great! Thanks a lot. I now also see that this form is mentioned on the support website. Feeling stupid 🤭 …
