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

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

</div>

Just to share my experiences. With the latest update 10.0.5 it seems my flows on a Homey 2023 are more responsive with less errors. With 10.0.6 devices react a bit slower (then 10.0.5) but still react … also less of zwave error message.  
Update1: So far 10.0.5 seemed the best for my setup.  
Update2: With 10.0.6 more TRANSMIT\_COMPLETE\_FAIL’s. Also quite some issues to add Z-Wave devices. Need to retry a lot (6x), but some (Fibaro CO meter) just will not add. Still quite some work to do for Athom I guess.

---

<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 29, 2023, 10:20am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/493 "2023-09-29T10:20:05Z")

</div>

I have Robb Z-Wave dimmers and these regularly drop out of the network (2/3 time a year) and then I’ll have to factory reset them en then re-add them. So I have this on hand today but adding a Z-Wave device simply doesn’t work. Every time I try I get a time-out when the device is installing.

---

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

</div>

That’s exactly what I get too, with new z-wave devices until this bug is fixed

---

<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 29, 2023, 11:19am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/495 "2023-09-29T11:19:12Z")

</div>

I had something very strange in regards to this topic…

Because of the issues I decided to roll-back to the 2019Homey.

Pulled the plug of the 2023.  
Booted the 2019.  
Added to my account (had it removed)  
Restored the backup

And… it was not working… Hmmm maybe it needs some time to recover… So went to bed and let time do it’s thing…

Next day… still not a working and Evo Home still loosing connection the radiator knobs… GRRRRR…

Okay, switch all power of the whole home OFF…

Turned on the power to the Homey 2019, let it boot… Wait 3 more minutes and turned on the power of the rest of the house… Waited a few minutes and eurekaaaaaaa it all started to work again except my iblinds…

Also the Evo Home is happy again.

So finally I have a working house again, not let’s wait till the issue is fixed…

Take away: I needed to cut power to all my devices to get it up and running again…

---

<div class="post-metadata">

**Author:** ![Rockhoppers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rockhoppers/32/3994_2.png) [@Rockhoppers](https://community.homey.app/u/Rockhoppers)\
**Post date:** [September 30, 2023, 12:37pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/498 "2023-09-30T12:37:41Z")

</div>

Don’t believe it is off topic, Athom / Homey 23 has screwed up my home automation project and like others on this page i have been looking at something that can replace it with the same range of protocols. So this may help others with the same issue finding and alternative.

---

<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:** [October 3, 2023, 5:50pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/499 "2023-10-03T17:50:57Z")

</div>

It is a real shame Athom has chosen the silent approach here. There are quite a few people with 400 euro home automation devices that are not making life easier at the moment, and others such as me waiting to be finally able to (safely) migrate from a stable 2019 device to the new 2023 device that’s just waiting to be used.  
Why not be a bit more transparant about this issue and the projected solution? Is it solvable in the software? Is there an expected timeframe when a solution might come? Even it the answer is “weeks/months” that would be better than just saying nothing.

---

<div class="post-metadata">

**Author:** ![Daniel\_Esland](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daniel_esland/32/941_2.png) [@Daniel\_Esland](https://community.homey.app/u/Daniel_Esland)\
**Post date:** [October 3, 2023, 10:47pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/500 "2023-10-03T22:47:37Z")

</div>

I agree. Months and months of virtually no info. Then a glimmer of hope from emile himself and then Silence again. No progress report. I wonder if there is an unfixable problem with the chip. But that does not explain why it worked up until a certain release candidate and then stopped working. Something tangible must have gone wrong at that point. And I’m still upset about being told on here that homey shouldn’t be depended upon for home security or reliable switching. As I said then and I will say now. If you can’t really on it for security and emergency situations, what is it really for ? I think it should be absolutely dependable for these things. What is the point to all the integrations with locks, security devices, alarms etc if they are a ‘just nice to have ‘ thing.

---

<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:** [October 8, 2023, 12:45pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/501 "2023-10-08T12:45:55Z")

</div>

So things are marginally better. But it is still not consistent. Now it usually works turning on and off all my devices, but including is haphazard, some work, some don’t. Just a question of waiting for a permanent solution.

---

<div class="post-metadata">

**Author:** ![Ingmar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ingmar/32/3432_2.png) [@Ingmar](https://community.homey.app/u/Ingmar)\
**Post date:** [October 8, 2023, 1:20pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/502 "2023-10-08T13:20:21Z")

</div>

It’s like the early days when homey was just launched, of course they had a lot of goodwill, so all was forgiven and you know it should become better by time. Years later, all was running quite stable and as with a lot of people here, we felt the urge to get better hardware. How bizar is it that we are back at square one, starting al over. And yes, things got improved significantly over time, but in the end, if it is not reliable, it’s getting frustrating. It’s like an alarm system, it needs to be working 100% and if not, you get rid of it. In this case it is a matter of time that some company will stand up and becomes a real competitor for athom as the low hanging fruit seems to be communication. How much broken a platform is doesn’t really matter as long there is communication going on and there is some light at the end of the tunnel.

---

<div class="post-metadata">

**Author:** ![Martin\_von\_Rotz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_von_rotz/32/48286_2.png) [@Martin\_von\_Rotz](https://community.homey.app/u/Martin_von_Rotz)\
**Post date:** [October 8, 2023, 5:19pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/503 "2023-10-08T17:19:17Z")

</div>

Rolled Back to 2019 as well but mine worked immediately (had not removed it from my account). Will have to add all Z-Wave sensors again and that’s a pain because most of them are Window Sensors and “glued” to the frame. But before that I add the range extenders (had only one so far, ordered 2 more) and then start re-adding the other devices ☹

---

<div class="post-metadata">

**Author:** ![Daniel\_Esland](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daniel_esland/32/941_2.png) [@Daniel\_Esland](https://community.homey.app/u/Daniel_Esland)\
**Post date:** [October 9, 2023, 12:19am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/504 "2023-10-09T00:19:07Z")

</div>

It’s been a long time.  
No solution.  
V worried that the chip was a bad choice  
Lack of solution is starting to make me feel there is a very entrenched problem with the chip that Connot be fixed.  
So very quiet.

---

<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:** [October 9, 2023, 10:01am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/505 "2023-10-09T10:01:43Z")

</div>

You mean add all new added sensors? Cause in the backup the pairing is kept, only I had to restart all powered devices to start behaving again…

---

<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:** [October 9, 2023, 4:59pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/506 "2023-10-09T16:59:24Z")

</div>

The lack of solution combined with the lack of communication is starting to worry me also. Not even sure if it is software or hardware related. In case of software, when can a solution be expected. In case of hardware, is it structural or just a batch? I really do not understand why Athom has the policy of not communicating.

---

<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:** [October 9, 2023, 6:05pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/507 "2023-10-09T18:05:40Z")

</div>

To the people that are stating that communication is a issue, Emilie statet 28 dayd ago that they are working on it with Silicon Labs and :

> [@Emile](#):
>
> We’re confident we will solve this issue in time, but please be patient with us, and if you have found a reproduction scenario with a possible fix, please shoot me a message directly!

What are you guys/girls suggestion to more communication? “Hello everyone, we are still working on a fix”. I do not understand what good that will bring. As ofcourse, they are still working on it. It is stated in the release notes after this post that the problem is not solved but they are adding more logging and so on. The communication is there, but you do not wan’t to see it, obviously.

---

<div class="post-metadata">

**Author:** ![Ingmar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ingmar/32/3432_2.png) [@Ingmar](https://community.homey.app/u/Ingmar)\
**Post date:** [October 9, 2023, 8:40pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/508 "2023-10-09T20:40:49Z")

</div>

28 days without any update is just bad and it shows a wrong attitude to a lot of very loyal customers. There is always something to mention and in situations like these full transparency is the only right recipe. But he, well wait another 28 days.

---

<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:** [October 9, 2023, 8:42pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/509 "2023-10-09T20:42:35Z")

</div>

That is not communication. That is acknowledging there is a problem and then leave everyone in the dark about it.

---

<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:** [October 9, 2023, 8:55pm UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/510 "2023-10-09T20:55:46Z")

</div>

Did you sent them a supply request?

Mine was answered by Dennis with a first feedback after ~ 1 Month, the second within some days.

Yes, the Athom Service is not very fast. But regarding the zwave issue they are depending at the chip manufacturer which need to send Athom a new firmware for the zwave chip.

Athom has published the problem with Silicon labs on several plattforms.

---

<div class="post-metadata">

**Author:** ![Emile](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/emile/32/115314_2.png) [@Emile](https://community.homey.app/u/Emile)\
**Post date:** [October 10, 2023, 8:35am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/511 "2023-10-10T08:35:32Z")

</div>

Hey all,

I’ve written a blog post about the current status. I hope it gives some transparency in our challenges.

> **[An update on Homey Pro's roadmap](https://homey.app/en-us/blog/about-homey-pros-timeline/)**

---

<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:** [October 10, 2023, 9:00am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/512 "2023-10-10T09:00:15Z")

</div>

> [@Emile](#):
>
> I’ve written a blog post about the current status. I hope it gives some transparency in our challenges.

Thanks for the very good explanations. Being a developer with customers all over the world I do understand your struggle. Keep up your excellent work, your product is awesome.

---

<div class="post-metadata">

**Author:** ![Piotr\_Szczalba](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/piotr_szczalba/32/86648_2.png) [@Piotr\_Szczalba](https://community.homey.app/u/Piotr_Szczalba)\
**Post date:** [October 11, 2023, 10:45am UTC](https://community.homey.app/t/homey-pro-2023-zwave-too-much-traffic-error/84036/513 "2023-10-11T10:45:44Z")

</div>

Thanks for news. It’s good to know we’re not alone with our problems. It is also good to hear that the z-wave issue is “only” firmware not hardware. Except for this, I still prefer HP23 rather than HC3.

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

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