# 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:** 16

<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:** [August 18, 2023, 9:21am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/307 "2023-08-18T09:21:50Z")

</div>

Sure, but in the 300 posts above, I don’t see any definition of these terms.

“_Too much Z-wave traffic_”: **too much** = what, exactly?

From the support text posted here…  
“ **Chatty** ” = what, exactly?

“_Change the reporting settings of nodes with the exceedingly high amount of messages_”: “ **exceedingly high amount** ” = what, exactly?

“…do this for all devices with a high Rx value.”: What is a “ **high** Rx” value, exactly?

There is not even any definition of what the columns mean in the developer page (leaving aside that no consumer user should even have to know about this to make their device function).

I note from your earlier comments, you “_…believe the TX and RX are since the latest restart_”, and your observation that “_Most of the time the issue starts when RX numbers go up with 30-40 per second_”, but surely Athom make clear what trigger these messages and what they are supposed to mean to developers (i.e. users of the developer pages)?

As a non-developer, if I am to temporarily cripple the functioning of the house or compromise it’s function or security just to make some of the devices work, it would be useful to know what these specific thresholds are for devices considered “chatty”.

---

<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:** [August 18, 2023, 10:16am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/308 "2023-08-18T10:16:24Z")

</div>

> [@K\_S](#):
>
> I note from your earlier comments, you “_…believe the TX and RX are since the latest restart_”, and your observation that “_Most of the time the issue starts when RX numbers go up with 30-40 per second_”, but surely Athom make clear what trigger these messages and what they are supposed to mean to developers (i.e. users of the developer pages)?

Unfortunately not. But it’s a fact that they reset after a restart and that’s how you can spot if something is wrong.

For the rest; it’s just as much our guess as it is yours. We can only make conclusions about our experiences, as described above.

---

<div class="post-metadata">

**Author:** ![Simon777](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon777/32/78190_2.png) [@Simon777](https://community.homey.app/u/Simon777)\
**Post date:** [August 19, 2023, 6:19am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/309 "2023-08-19T06:19:32Z")

</div>

Before the last update my Homey had intermittent issues but I could be solved with at nightly restart.

After the last update it is completely useless. I get the error almost immediately after restart.

I hope athom is working hard to fix this error.

I just switched from indigo tempted by the nice interface but I am a bit disappointed at the moment.

---

<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:** [August 19, 2023, 6:37am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/310 "2023-08-19T06:37:19Z")

</div>

Athom indicated yesterday that they are working on it, but there are only a few people impacted by this issue.

I wonder if indeed there are so few, and what is common in our setup. My expectation was that everyone with some zwave sensors would be impacted. Are there users who have no issues with the zwave and have 3+ sensors in their setup?  
Can you please share your screenshot of the setup so I can compare?

---

<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:** [August 19, 2023, 7:25am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/311 "2023-08-19T07:25:24Z")

</div>

Its true that we are the minority but if I just count the users here and on Slack and on social media I believe there are at least 50 cases with this or similar issue. Looking at the general fact that only a small percentage will put their issue on this forum or even share it with Athom I think we can safely say that a minimum of 100-150 people are experiencing this issue. Doesn’t really matter though. Should be fixed anyway.

---

<div class="post-metadata">

**Author:** ![Undertaker](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/undertaker/32/53278_2.png) [@Undertaker](https://community.homey.app/u/Undertaker)\
**Post date:** [August 19, 2023, 7:38am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/312 "2023-08-19T07:38:15Z")

</div>

> [@Youri\_Pasternak](#):
>
> Are there users who have no issues with the zwave and have 3+ sensors in their setup?  
> Can you please share your screenshot of the setup so I can compare?

I have no problems at all. What kind of setup do you mean exactly? At the moment 60 Zwave devices mainly from Devolo, Neo Coolcam, Fibaro and Heiman. All devices are registered insecurely.

 ![Screenshot_20230819-093255_Chrome](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/0/c0ddd38980319c173927758c8693722004969798.jpeg)

---

<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:** [August 19, 2023, 7:51am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/313 "2023-08-19T07:51:36Z")

</div>

Great and which motion sensor do you have (brand) and how many?

Thanks!

---

<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:** [August 19, 2023, 8:45am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/314 "2023-08-19T08:45:27Z")

</div>

I have, 11 Aeotec multisensors - mains powered, 5 Aeotec recessed door sensors, ~40 Fibaro relays/switches, 5 HeatIt thermostats, 6 Fakro window/blind (mains), ~35 Sensative Strips (none of which are working with HP23). All the Fakro, HeatIt and some Fibaro and some Aeotec multisensors have higher “Rx” values than the rest.

My 2 neighbours (who can’t be bothered to post here) have mostly Fibaro, and (newer) Sensative strips and some Aeotec multisensors. About 20% of their Fibaro devices have higher “Rx” values than the rest. One is not able to add/pair or remove any z-wave devices (gets “too much traffic” message). The other just has flows that don’t work.

For all of us zone presence detection (and flows depending on them) is largely not functioning with HP23

---

<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:** [August 19, 2023, 9:02am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/315 "2023-08-19T09:02:04Z")

</div>

I start to wonder if the issue might be related to the combination of HP23 and Fibaro motion sensors.

Anyone who has no issues AND is using the fibaro motion sensors?  
Or the other way around, anyone who IS using fibaro motion sensors and has NO issues?

---

<div class="post-metadata">

**Author:** ![Undertaker](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/undertaker/32/53278_2.png) [@Undertaker](https://community.homey.app/u/Undertaker)\
**Post date:** [August 19, 2023, 9:08am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/316 "2023-08-19T09:08:10Z")

</div>

> [@Youri\_Pasternak](#):
>
> Great and which motion sensor do you have (brand) and how many?

Zwave:  
Aeotec Multisensor 2x  
Fibaro 2x  
Devolo 7x  
Heiman 1x

and Zigbee/Wlan:  
3x Aqara  
5x Shelly Motion 2  
2x Ikea Tradfri

---

<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:** [August 19, 2023, 9:49am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/317 "2023-08-19T09:49:35Z")

</div>

I have nearly 100 zwave Sensors and Actors in my system.

Fibaro Sensors, switches)  
Technisat Switches and binds)  
Devolo (sensors)  
Philio (sensors)  
Heimann (Abus) Fire sensors  
Qubino (switches and meters)  
Neo (plugs)  
Aeotec Range extender  
Danfoss (heating)  
Eurotronic sensor  
Popp outdoor switches  
Sensitive Strips

Included Secure and unsecured depending on device

@Undertaker: my problems startet as I added new devices to the migrated 2019 mesh (qubino Smartmeters and eurotronic sensors)

Currently I boot my Homey every hour

---

<div class="post-metadata">

**Author:** ![Undertaker](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/undertaker/32/53278_2.png) [@Undertaker](https://community.homey.app/u/Undertaker)\
**Post date:** [August 19, 2023, 10:07am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/318 "2023-08-19T10:07:54Z")

</div>

I had no problems there either. The migration worked immediately, I only had to fix Zigbee.  
Re-learning Zwave devices is also no problem. Just yesterday I switched back from HA to Homey with 7 Heiman smoke detectors.

---

<div class="post-metadata">

**Author:** ![danone](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/danone/32/115743_2.png) [@danone](https://community.homey.app/u/danone)\
**Post date:** [August 19, 2023, 12:36pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/319 "2023-08-19T12:36:27Z")

</div>

> [@Youri\_Pasternak](#):
>
> Or the other way around, anyone who IS using fibaro motion sensors and has NO issues?

Count of 8 and no issues with them if that’s what u mean. They respond instantly in fact.  
But loads of problems with most of Aeotec powered devices timing out as too much traffic and with one Fibaro double switch that was included after the migration from HP19 and while on firmware RC118.  
I have 75% Fibaro, 25% Aeotec.  
So yes, overall piece of crap this z-wave since RC118 onwards.

---

<div class="post-metadata">

**Author:** ![Marius\_Stensrod](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marius_stensrod/32/56540_2.png) [@Marius\_Stensrod](https://community.homey.app/u/Marius_Stensrod)\
**Post date:** [August 19, 2023, 1:19pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/320 "2023-08-19T13:19:16Z")

</div>

> [@Youri\_Pasternak](#):
>
> Anyone who has no issues AND is using the fibaro motion sensors?  
> Or the other way around, anyone who IS using fibaro motion sensors and has NO issues?

No issues, have 4 fibaro motion sensors. 41 Z-Wave devices in the system, Aetoec, Fibaro, Heatit and Namron.

---

<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:** [August 19, 2023, 1:33pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/321 "2023-08-19T13:33:19Z")

</div>

I don’t have any Fibaro motion sensors (just aeotec)

---

<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:** [August 19, 2023, 1:55pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/322 "2023-08-19T13:55:14Z")

</div>

I don’t have any Fibaro motion sensors, only Philio.  
But same problems

---

<div class="post-metadata">

**Author:** ![Dennis\_H74](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dennis_h74/32/11177_2.png) [@Dennis\_H74](https://community.homey.app/u/Dennis_H74)\
**Post date:** [August 19, 2023, 3:33pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/323 "2023-08-19T15:33:30Z")

</div>

Only issues with aeotec … no problems with fibaro

---

<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:** [August 19, 2023, 8:21pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/324 "2023-08-19T20:21:46Z")

</div>

Still seems like a random bug. 🤷🏻‍♂️

---

<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:** [August 20, 2023, 8:35am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/325 "2023-08-20T08:35:30Z")

</div>

Indeed, at random times it takes down my whole Z-Wave network. Then, at a random amount of time later, it starts working again. Or it needs a reboot. I do that at random when it doesn’t come back on in time or when I really want the light to go out.

/some random frustration on my part.

---

<div class="post-metadata">

**Author:** ![DuMees](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dumees/32/75943_2.png) [@DuMees](https://community.homey.app/u/DuMees)\
**Post date:** [August 21, 2023, 5:46am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/326 "2023-08-21T05:46:51Z")

</div>

I have the too much traffic issue and do not have Fibaro motion sensor. I do have Fibaro dimmers and switches + recently and Aeotec range extender (issues started after I added this but after removing is still there, probably coincidence). Roughly 60 Zwave devices

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

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