# Zwave timeout and routing via non-existing nodes

**URL:** <https://community.homey.app/t/zwave-timeout-and-routing-via-non-existing-nodes/56334>\
**Category:** Questions & Help\
**Tags:** z-wave\
**Created:** [December 10, 2021, 12:27pm UTC](https://community.homey.app/t/zwave-timeout-and-routing-via-non-existing-nodes/56334 "2021-12-10T12:27:39Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![paaland](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paaland/32/26023_2.png) [@paaland](https://community.homey.app/u/paaland)\
**Post date:** [December 10, 2021, 12:27pm UTC](https://community.homey.app/t/zwave-timeout-and-routing-via-non-existing-nodes/56334/1 "2021-12-10T12:27:39Z")

</div>

Homey Pro firmware 7.2.0  
Device Namron z-wave smart plug with termostat and power meter (model 4512725). Added via the Namron App.

I have two z-wave devices that keeps falling off the network. They are both in a room with another z-wave device (of the same make & model) that I can reach. The strange thing is that both devices are apparently trying to route via non-existing nodes.

I can unplug them and they work for some time (1-5 hours) before they fall off again. Any ideas?

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/8/68885b43219bfb192985dca22147ee43327d8e22.png)

---

<div class="post-metadata">

**Author:** ![Lupadi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lupadi/32/48816_2.png) [@Lupadi](https://community.homey.app/u/Lupadi)\
**Post date:** [December 13, 2021, 2:11pm UTC](https://community.homey.app/t/zwave-timeout-and-routing-via-non-existing-nodes/56334/2 "2021-12-13T14:11:22Z")

</div>

did you already find a solution for this problem? i’m having the same issue with a different device

---

<div class="post-metadata">

**Author:** ![paaland](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paaland/32/26023_2.png) [@paaland](https://community.homey.app/u/paaland)\
**Post date:** [December 13, 2021, 2:54pm UTC](https://community.homey.app/t/zwave-timeout-and-routing-via-non-existing-nodes/56334/3 "2021-12-13T14:54:15Z")

</div>

No, unfortunately not. I even tried the new 7.2.1 rc-1 firmware for the Homey.

---

<div class="post-metadata">

**Author:** ![Rudi\_Hendrix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rudi_hendrix/32/31931_2.png) [@Rudi\_Hendrix](https://community.homey.app/u/Rudi_Hendrix)\
**Post date:** [December 14, 2021, 8:45am UTC](https://community.homey.app/t/zwave-timeout-and-routing-via-non-existing-nodes/56334/4 "2021-12-14T08:45:00Z")

</div>

I have the same issue with different devices as well.

Interesting thing is: the devices that are “unreachable” do still seem to send their data to Homey. So, is there an actual issue?

In my case, one is unreachable through non existing nodes.  
A few others that are unreachable are connected through a Greenwave power node. Not all nodes that are connected through that Greenwave power node are unreachable however.  
All of them do send data to Homey. The one that is unreachable through non existing nodes previously was connected through that same Greenwave power node.

I started looking into this because I had [this issue](https://community.homey.app/t/bewegingssensor/17509/25) .

Do you guys see these devices working or not working?

---

<div class="post-metadata">

**Author:** ![paaland](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paaland/32/26023_2.png) [@paaland](https://community.homey.app/u/paaland)\
**Post date:** [December 14, 2021, 9:42am UTC](https://community.homey.app/t/zwave-timeout-and-routing-via-non-existing-nodes/56334/5 "2021-12-14T09:42:02Z")

</div>

My devices are not working when unreachable. If there were working I’d not care.

---

<div class="post-metadata">

**Author:** ![Aron\_Kovacs](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aron_kovacs/32/11593_2.png) [@Aron\_Kovacs](https://community.homey.app/u/Aron_Kovacs)\
**Post date:** [December 20, 2021, 2:10pm UTC](https://community.homey.app/t/zwave-timeout-and-routing-via-non-existing-nodes/56334/6 "2021-12-20T14:10:23Z")

</div>

@paaland Which screen is this routing table? (I also have device which is not reachable and would like to know how my zwave network is setup)

---

<div class="post-metadata">

**Author:** ![paaland](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paaland/32/26023_2.png) [@paaland](https://community.homey.app/u/paaland)\
**Post date:** [December 20, 2021, 2:21pm UTC](https://community.homey.app/t/zwave-timeout-and-routing-via-non-existing-nodes/56334/7 "2021-12-20T14:21:59Z")

</div>

[http://developer.athom.com/](http://developer.athom.com/)

---

<div class="post-metadata">

**Author:** ![EdStaal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/edstaal/32/35035_2.png) [@EdStaal](https://community.homey.app/u/EdStaal)\
**Post date:** [January 11, 2023, 2:38pm UTC](https://community.homey.app/t/zwave-timeout-and-routing-via-non-existing-nodes/56334/8 "2023-01-11T14:38:28Z")

</div>

> [@paaland](#):
>
> ing to route via non-existing nodes.

Hi, did you solve this issue and if so. How? Because I have the same

---

<div class="post-metadata">

**Author:** ![paaland](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/paaland/32/26023_2.png) [@paaland](https://community.homey.app/u/paaland)\
**Post date:** [January 11, 2023, 2:56pm UTC](https://community.homey.app/t/zwave-timeout-and-routing-via-non-existing-nodes/56334/9 "2023-01-11T14:56:34Z")

</div>

I removed and repaired the devices in question. I think that solved it issue for me. At least I don’t have it anymore 🙂
