# Homey pro 2023 - zwave too much traffic error?

**URL:** <https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036>\
**Category:** Questions & Help\
**Tags:** z-wave, homey-pro\
**Created:** [July 5, 2023, 9:16pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036 "2023-07-05T21:16:23Z")\
**Posts on this page:** 20\
**Page:** 21

<div class="post-metadata">

**Author:** ![elfrigo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/elfrigo/32/7893_2.png) [@elfrigo](https://community.homey.app/u/elfrigo)\
**Post date:** [September 6, 2023, 4:04pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/410 "2023-09-06T16:04:50Z")

</div>

Still trying to for the traffic issue.  
So I started cleaning up de Z-Wave device list.  
Removed so devices that were not needed any more.  
Increase the time for device sensor updates.  
But ran into the next problem.  
I’ve got 9 “Unknown Node”.

1. When I click “Test” - some are Reachable - but I have NO idea what device it is (I’m pretty sure the device is completely offline - removed the power on all devices I dont need).
2. When I click “Test” - some are still Unreachable - but when I click “Remove” it stats “Node Not Found” [screenshot below]  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/9/c9ea97254a677b4dbebb540befce74831b31079d.png)

Anyone suggestions or idea’s?  
Guess this kinda z-wave “mess” will at least not help in the traffic error 😏

---

<div class="post-metadata">

**Author:** ![Martin\_Ahlert](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_ahlert/32/9579_2.png) [@Martin\_Ahlert](https://community.homey.app/u/Martin_Ahlert)\
**Post date:** [September 6, 2023, 4:34pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/411 "2023-09-06T16:34:31Z")

</div>

It looks like zwave devices which are not assigned to your Homey zwave network are the unknown devices. I have the same problem with my second zwave network for the security relevant devices steered by homee

---

<div class="post-metadata">

**Author:** ![Robin\_Lunden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robin_lunden/32/12626_2.png) [@Robin\_Lunden](https://community.homey.app/u/Robin_Lunden)\
**Post date:** [September 6, 2023, 7:41pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/412 "2023-09-06T19:41:13Z")

</div>

I have exactly the same problem. Unknown devices racking up hundreds of thousands of pings. And they are not removable either. I do now know which devices they are. Is it some old switch I’ve forgotten about. I am considering the nuclear option of reseting z-wave network, but the amount of work digging out all my fibaros is daunting.  
This error is driving me crazy.

---

<div class="post-metadata">

**Author:** ![elfrigo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/elfrigo/32/7893_2.png) [@elfrigo](https://community.homey.app/u/elfrigo)\
**Post date:** [September 6, 2023, 8:09pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/413 "2023-09-06T20:09:51Z")

</div>

Thanks for your thoughts and experiences.

The only Z-Wave network I have/had is from my sole Homey. The Unknown Node(s) are remnants from devices I do not use anymore. I removed them using the Homey app, but they are still somehow linked to Homey. They are offline / no power / battery removed.  
So quite weird that Homey thinks that some still can be Reached. And also weird that those Homey cannot reach, can’t be removed due to a “NODE\_NOT\_FOUND” error.

I’m puzzled

---

<div class="post-metadata">

**Author:** ![Willy](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/willy/32/9673_2.png) [@Willy](https://community.homey.app/u/Willy)\
**Post date:** [September 7, 2023, 5:21pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/414 "2023-09-07T17:21:53Z")

</div>

> <https://twitter.com/Athom/status/1699731799608304079?t=8WzxP0qVvjOueLnRzmepng&s=19>

---

<div class="post-metadata">

**Author:** ![K\_S](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/k_s/32/11635_2.png) [@K\_S](https://community.homey.app/u/K_S)\
**Post date:** [September 7, 2023, 5:40pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/415 "2023-09-07T17:40:56Z")

</div>

🙄 professional reviewers who haven’t paid for the devcies

---

<div class="post-metadata">

**Author:** ![Youri\_Pasternak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/youri_pasternak/32/55754_2.png) [@Youri\_Pasternak](https://community.homey.app/u/Youri_Pasternak)\
**Post date:** [September 7, 2023, 5:59pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/416 "2023-09-07T17:59:35Z")

</div>

Its also only partially written, I read the review of [tweakers.net](http://tweakers.net) for example, and they actually refer to this issue and this topic. From marketing perspective I understand though, I just don’t understand why this issue is pending for so long.

---

<div class="post-metadata">

**Author:** ![Martijn\_C](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_c/32/39993_2.png) [@Martijn\_C](https://community.homey.app/u/Martijn_C)\
**Post date:** [September 7, 2023, 6:20pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/417 "2023-09-07T18:20:54Z")

</div>

Which I am too, but never ever have I been positive about a device because it was ‘paid for’.

That being said; also I have received a HP2023 but I am also one of the Z-Wave users with the major issue! I have been in talks with Stefan (owner of Athom) and agreed to postpone my review with 3 months. Otherwise the review would be short; Avoid the HP2023 if you’re using Z-Wave. I can’t use it at all.

Will I mention the big issue when the review is done? For sure!! I’ll make a big deal out of it. So no, probably that quote won’t and up there. 😉

---

<div class="post-metadata">

**Author:** ![Robin\_Lunden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robin_lunden/32/12626_2.png) [@Robin\_Lunden](https://community.homey.app/u/Robin_Lunden)\
**Post date:** [September 7, 2023, 6:29pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/418 "2023-09-07T18:29:54Z")

</div>

So i wiped my H2023, and restored my last backup from my old homey. This way I was able to identify the “unknown device” that was flooding he zwave system. It was a HeatIt thermostat. Hasn’t solved the problem but now I know which unit to focus on.

---

<div class="post-metadata">

**Author:** ![K\_S](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/k_s/32/11635_2.png) [@K\_S](https://community.homey.app/u/K_S)\
**Post date:** [September 7, 2023, 6:38pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/419 "2023-09-07T18:38:43Z")

</div>

> [@Martijn\_C](#):
>
> Which I am too, but never ever have I been positive about a device because it was ‘paid for’.

Sure, but you can’t genuinely portray a customers value for money experience if you haven’t parted with any

---

<div class="post-metadata">

**Author:** ![Martijn\_C](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_c/32/39993_2.png) [@Martijn\_C](https://community.homey.app/u/Martijn_C)\
**Post date:** [September 7, 2023, 8:31pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/420 "2023-09-07T20:31:06Z")

</div>

I disagree with that, since that’s exactly my job (and the job of others).

---

<div class="post-metadata">

**Author:** ![Youri\_Pasternak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/youri_pasternak/32/55754_2.png) [@Youri\_Pasternak](https://community.homey.app/u/Youri_Pasternak)\
**Post date:** [September 7, 2023, 8:50pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/421 "2023-09-07T20:50:51Z")

</div>

But its not entirely objective either if you agree to wait 3 months to write a review.

---

<div class="post-metadata">

**Author:** ![Martijn\_C](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_c/32/39993_2.png) [@Martijn\_C](https://community.homey.app/u/Martijn_C)\
**Post date:** [September 8, 2023, 7:53am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/422 "2023-09-08T07:53:28Z")

</div>

Why is that? I can’t even write a review now since the whole product doesn’t work for me. And I do take into account that we are a minority. And I will add this issue even if it’s solved. I just simply can’t write a review of a product that doesn’t start to work to begin with. Because if I did that the majority would write the same; how can that guy burn down a product which works well for 95% of the people? You can’t please everyone.

There’s always a ‘grace period’ if a manufacturer finds a bug shortly after a release. Most professional journalists accept this and communicate about it with the manufacturer.

---

<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:** [September 8, 2023, 8:36am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/424 "2023-09-08T08:36:55Z")

</div>

I’m interested to hear what you would do if the 3 month grace period is over and your issues are still not fixed. Will you accept Athom’s standard reply (as in: they say this for _every_ issue, and have so for years) that only a few users are affected?

Also, I assume they have offered you a replacement device to rule out a hardware issue?

---

<div class="post-metadata">

**Author:** ![K\_S](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/k_s/32/11635_2.png) [@K\_S](https://community.homey.app/u/K_S)\
**Post date:** [September 8, 2023, 8:38am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/425 "2023-09-08T08:38:09Z")

</div>

> works well for 95%

Really? Where’s this number from?

---

<div class="post-metadata">

**Author:** ![Martijn\_C](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_c/32/39993_2.png) [@Martijn\_C](https://community.homey.app/u/Martijn_C)\
**Post date:** [September 8, 2023, 8:41am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/426 "2023-09-08T08:41:09Z")

</div>

Good question and a simple answer; I will write a short review (since I can’t do much) and talk about how my situation is indeed a stress test for Homey but the conclusion about that test it that this product is not suitable for elaborate installations with a focus on Z-Wave. I’m always honest and I’ll be honest then.

But, when an update shows up after I published it, I will for sure add the new experiences and alos mention it if it IS solved. But I’ll also leave the first experience in there.

p.s. I don’t ‘accept’ that reply as an excuse. I accept the reply as a reason to give them time since i also can see that many people have no issues.

95% quote: My estimate. But I believe it’s even higher. The Z-Wave issue is not wide spread, looking at Slack, the forum and social media. Also Athom (obviously) confirms that. And, I’m only talking about this big Z-Wave issue.

But hey! I have my whole house connected to Homey, based on Z-Wave! I want it to be fixed too! 🙂

---

<div class="post-metadata">

**Author:** ![Martijn\_C](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_c/32/39993_2.png) [@Martijn\_C](https://community.homey.app/u/Martijn_C)\
**Post date:** [September 8, 2023, 8:45am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/427 "2023-09-08T08:45:01Z")

</div>

> [@robertklep](#):
>
> Also, I assume they have offered you a replacement device to rule out a hardware issue?

Sorry, forgot. Yes, I bought one myself too, way before they send me one. Both have the same issue.

---

<div class="post-metadata">

**Author:** ![Anders\_Gregow](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anders_gregow/32/61721_2.png) [@Anders\_Gregow](https://community.homey.app/u/Anders_Gregow)\
**Post date:** [September 8, 2023, 8:46am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/428 "2023-09-08T08:46:24Z")

</div>

I have seen many people in different forums/groups stating that there Homey2023 works flawless. So this issue does definitely not affect everyone. We, as usually, only see the people having problems, posting in forums.

---

<div class="post-metadata">

**Author:** ![K\_S](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/k_s/32/11635_2.png) [@K\_S](https://community.homey.app/u/K_S)\
**Post date:** [September 8, 2023, 8:56am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/429 "2023-09-08T08:56:18Z")

</div>

> many people in different forums/groups stating that there Homey2023 works flawless

I suspect many probably also use homey without m/any z- wave devices (like one of my 3 neghbours)

> usually, only see the people having problems, posting in forums.

Often the inverse is also true: many people with problems don’t / can’t / can’t be bothered to post. Forums are not a good measure of problems (or overall satisfaction)

---

<div class="post-metadata">

**Author:** ![Jo\_San](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jo_san/32/3732_2.png) [@Jo\_San](https://community.homey.app/u/Jo_San)\
**Post date:** [September 8, 2023, 11:36am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/430 "2023-09-08T11:36:53Z")

</div>

I have postponed my migration for quite some time now as I am afraid my currently flawlessly running (70% zwave) installation will be affected by this zwave issue.  
Is it easy to revert back to the old homey once you have migrated?

[Previous page](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036.md?page=20)

[Next page](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036.md?page=22)
