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

<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 3, 2023, 2:34pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/388 "2023-09-03T14:34:46Z")

</div>

The 2023 is supposed to be the most advanced Homey and an upgrade of the 2019. It shouldn’t have any performance issues the 2019 didn’t have.

---

<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 3, 2023, 2:54pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/389 "2023-09-03T14:54:29Z")

</div>

Today is one of the “better” days. Sixth reboot so far and the error immediately after reboot.

---

<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 3, 2023, 3:37pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/390 "2023-09-03T15:37:11Z")

</div>

That’s the article Athom‘s Help Desk refers to before they close your ticket.

They are working at the problem, but can’t help more atm.

---

<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:** [September 4, 2023, 5:11am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/391 "2023-09-04T05:11:44Z")

</div>

Couple of weeks in with this error, received a couple of days ago an email stating they’re working on it but due to not many users experiencing this issue supposedly it is difficult to resolve this issue.

I’m at this point where I’m seriously thinking of moving away from Homey. I think I’ll give it another week.

If an organization is not capable of fixing an bug of this magnitude they shouldn’t be in the home automation market. I’m imagining what would have happened if it is winter and my Z-wave switches are not opening my floor heating groups. I have 2 little kids and they should not be affected by tech that is straight up not working.

---

<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 4, 2023, 7:05am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/392 "2023-09-04T07:05:45Z")

</div>

I “upgraded” from my Homey 2016 to the early 2023 Pro and also have the "Could not send command. Too much Z-wave traffic. (TRANSMIT\_COMPLETE\_FAIL).” error.  
So far no luck solving it.  
The 2016 had no problems with exactly the same devices and flows.

Guess I’m reverting back to the Pro 2016 until Athom fixes this.  
Will update this post if I find a (temporary) solution.

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [September 4, 2023, 8:25am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/393 "2023-09-04T08:25:39Z")

</div>

> [@Martin\_Ahlert](#):
>
> That’s the article Athom‘s Help Desk refers to before they close your ticket.

Didn’t know that, because I’m not affected by the “too much traffic” bug, so I’m not in contact with Athom support about this issue. Maybe the link will be helpful for some users who are not in contact with Athom’s support.

---

<div class="post-metadata">

**Author:** ![Ricardo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ricardo/32/84170_2.png) [@Ricardo](https://community.homey.app/u/Ricardo)\
**Post date:** [September 4, 2023, 11:18am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/394 "2023-09-04T11:18:21Z")

</div>

10.0.4-rc.9 is available with much Zigbee fixes.  
Z-wave seems not the priority:

_Reduce logging while creating and restoring a backup._

Z-wave problems I’ve notice at this moment in my system = iBlinds are very chatty and not able to reduce in their parameters. Already contact iBlinds and forwarded the reaction trough Athom… Right now I have to disable the iBlinds app to let my system work 😒

---

<div class="post-metadata">

**Author:** ![Ricardo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ricardo/32/84170_2.png) [@Ricardo](https://community.homey.app/u/Ricardo)\
**Post date:** [September 4, 2023, 11:26am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/396 "2023-09-04T11:26:42Z")

</div>

I’m curious, different Z-wave apps? In my case I’ve disabled **iBlinds** and enabled **Fibaro** to make it works.

---

<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 4, 2023, 11:42am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/397 "2023-09-04T11:42:56Z")

</div>

> Couple of weeks in with this error, received a couple of days ago an email stating they’re working on it …give it another week

I wouldn’t hold your breath. 2 weeks (with only 2 developers full time on it) is really not much effort in a given software ‘sprint’ / cycle given the depth of the problem they’re obviously not coping with. I expect it will take them 2-3 more x 3 weeks at least given the quality assurance testing they’ll need to do, and then the various apps developers might need to make changes too. Several months is probably more realistic (unless they put more resource into it - which I doubt they’ll do, because it seems they only have 9 developers on [LinkedIn Login, Sign in | LinkedIn](https://www.linkedin.com/company/athombv/people/?keywords=developer)). (The other 19 employees are presumably commercial)

---

<div class="post-metadata">

**Author:** ![Dennis\_Ek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dennis_ek/32/83937_2.png) [@Dennis\_Ek](https://community.homey.app/u/Dennis_Ek)\
**Post date:** [September 4, 2023, 3:20pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/398 "2023-09-04T15:20:51Z")

</div>

It’s not ok fix the problems 😤

---

<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 4, 2023, 4:42pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/399 "2023-09-04T16:42:17Z")

</div>

No point expressing it here - they don’t read read it. Only Support tickets, App store reviews and Facebook

---

<div class="post-metadata">

**Author:** ![Dennis\_Ek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dennis_ek/32/83937_2.png) [@Dennis\_Ek](https://community.homey.app/u/Dennis_Ek)\
**Post date:** [September 5, 2023, 3:56am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/400 "2023-09-05T03:56:06Z")

</div>

hi do you think homey pro will get better or if i do a reset or is better a send unit back

---

<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 5, 2023, 6:55am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/402 "2023-09-05T06:55:30Z")

</div>

In case anyone is wondering, the latest release candidate isn’t a fix

 ![Screenshot_20230905-075423-01](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/d/2d2d61994f2f4de509a1582c99603265010aaa46.jpeg)

 ![Screenshot_20230905-075144](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/e/fe51a39bbe73ac1be3eb943e0d7ae36e7eaa257b.png)

---

<div class="post-metadata">

**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\
**Post date:** [September 5, 2023, 8:41am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/403 "2023-09-05T08:41:32Z")

</div>

What did you expect? The bug isn’t mentioned in the changelog.  
I expect that if the bug is fixed in a new firmware version, it will be definitely mentioned in the changelog.

---

<div class="post-metadata">

**Author:** ![Eric\_Meiss](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eric_meiss/32/85864_2.png) [@Eric\_Meiss](https://community.homey.app/u/Eric_Meiss)\
**Post date:** [September 5, 2023, 9:12am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/404 "2023-09-05T09:12:07Z")

</div>

I am personally fed up. Just asked for refund.  
Not acceptable such behavior from Athom in 2023  
Everybody should do the same… may be they’d move their ass!

---

<div class="post-metadata">

**Author:** ![MauriceQuaedackers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mauricequaedackers/32/11034_2.png) [@MauriceQuaedackers](https://community.homey.app/u/MauriceQuaedackers)\
**Post date:** [September 5, 2023, 9:20am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/405 "2023-09-05T09:20:21Z")

</div>

Hi,

I am looking for alternatives for my z-wave network since my home is not working due to the problems all above. Really concidering a HomeCenter 3 and was looking into HomeAssistant where I found a really know description:

> Until recently, 700 series Z-Wave Controllers had a bug that could cause the mesh to be flooded on some networks and the controller to become unresponsive. At present, all 700 series controllers share the same firmware and are subject to this bug. It appears that this bug is largely, if not completely, resolved as of firmware version 7.17.2.
> 
> Users should upgrade the firmware on all 700 series controllers to version 7.17.2 or greater. Firmware can be upgraded using the below directions

I sent this information to the Athom support team as well…

---

<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 5, 2023, 9:29am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/406 "2023-09-05T09:29:15Z")

</div>

Even though this sounds similar to the issues that Homey has, it would be very strange that this is the cause of the problems, notably because Athom has stated they’re working with Silabs to fix the issue and firmware 7.17.2 was released [in March 2022](https://www.silabs.com/documents/public/release-notes/SRN14862-7.17.2.0.pdf)(!), before HP2023 even existed.

---

<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 5, 2023, 9:38am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/407 "2023-09-05T09:38:39Z")

</div>

> [@DirkG](#):
>
> What did you expect? The bug isn’t mentioned in the changelog.

My expectations from Homey have long been low based on experience of how unreliable the experience is overall, and especially the practice of keeping things in beta for years to get away with not being accountable for quality. However, given the claim in the bug report response that " _a couple of our best engineers working on this topic full-time, together with our chip-providing partner Silabs_ …_one of our top priorities_ _…expect this to get better soon_, I though this release might contain more that the logging error improvement…which by the way also seems not to have worked:

 ![Screenshot_20230904-184727](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/8/f82a1f780e0305c047cbb761975a961d74da64e5.png)

---

<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:** [September 5, 2023, 7:18pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/408 "2023-09-05T19:18:28Z")

</div>

Ask Pierre to buy you one 😉

---

<div class="post-metadata">

**Author:** ![claus](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/claus/32/6867_2.png) [@claus](https://community.homey.app/u/claus)\
**Post date:** [September 5, 2023, 8:04pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/409 "2023-09-05T20:04:47Z")

</div>

Like many of you I struggle a lot with this issue and I am now using my old Homey, without (the same) issues.

Is there anyone with this problem that did NOT migrate from another Homey?

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

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