You are correct, but either way, neither appear to address the Zwave issue.
I have the same problem as all of you. For me it was a couple of relays that were reporting power back to Homey atleast one time per sec. By changing the parameters for the Relays to âPower report on power change (%)â to 80 (example is for Quibuno) it solved my problems
Also, when I set the Power reporting interval to a higher value helps
Marcus, is the homey still working fine? As I did the same, and the problem came back within one day.
Did anyone find a fix with the latest firmware or are we still all having the same issue? Beta phase is over and since then Athom support is silent, perhaps the new firmware had a silent fix?
Iâm facing the same error whenever I restart Homey Pro 2023. It takes an hour, sometimes more, to resolve. Sometimes I just give up waiting and restart again and it magically works. Checking the tools, I donât even have any device that has >10 Tx Sent.
I have the latest firmware and the problem is not fixed. I have sent quite a serious email to athom regarding it, outlining my main concern regarding safety, with things not being turned off when they should be, security that simply doesnât work. Have heard nothing back.
Still the same hereâŚ
Yes,
I have now had the homey running with 90+ Z-wave units for a couple of days without any problems.
I do sometimes see 1 unit here and there sometimes getting a little more RX than normal but it has never been as bad as it was earlier.
Itâs not perfect, but working.
Iâve been migrating my Z-Wave devices (about 25) from HomeSeer to Homey Pro 2023 and hit the same issues.
After reviewing Dev Tools my highest Rx devices were Aeotec Dual Nano switches. These had Report Groups 1-3 set to Expert. Once I changed to Disabled the Z-Wave network has stabilised and useable, even if no energy data coming through for now. Still working fixing some other issues like an Unknown Node and will continue to fine tune.
Also, reviewing the Dev Tools Z-Wave logs in real time showed a non-stop flow of data which also identified the nodes. This data flow can now be up to 30 seconds before anything comes through.
To be honest, you shouldnât rely on Homey for anything that may impact the safety or security of your home or your family.
Good to hear. But still, Homey shouldnât even have a problem with an update from a sensor each second. I have some devices that do this on the HP2019 (just some) and this doesnât cause any issues. The problem happens when the messages of a lot of devices are duplicated 30 times per second. That crashes the network. In my opinion your issue was (fortunately for you) not related to that.
yes that is correct. It should not be like this.
i have to correct you here. i did have have the same problems everyone is pointing out here in the thread.
I had horrible rx traffic causing crashes and âtoo much z-wave trafficâ. I could not use my Homey at all minutes after a reboot. My experience is changing parameters on all units slowed it down. This worked for me. As i said itâs not perfect and Athom needs to solve the main issue.
But now I donât want to send the unit back anymore 
Well⌠then itâs up to Athom cause I have checked and set all intervals to ideal numbers, but no changes for me unfortunately. And I believe that is because the sensor doesnât send too much information. Itâs Homey that messes that one message up.
1 Like
My Homey Pro 2023 is due to arrive tomorrow and this discussion has me a bit concerned (I found this discussion after I placed my order). Most of my devices are from Aeotec (6 x Smart Switch 6, 4 x Motion Sensor 6, 3 x Door Sensor Gen 5). Iâm planning on moving only a few devices initially while I learn the features / behavior of Homey Pro 2023.
As I move my z wave devices from my old hub (Vera Edge) to the Homey Pro 2023, does the group have any advice on how to avoid / minimize the âtoo much trafficâ issue? Thank you!
Quite disappointed to read this.
If homey isnât for integrating security and safety in the home and not to turn devices on and off safely and reliably, what is the point of it, what IS it for?
I received an official answer from Athom. In short: the Z-Wave chip shows issues in very specific situations for a limited number of users. Two guys are working on it fulltime so a fix should arrive soon.
4 Likes
Thanks for the update Martijn!
Waiting for the delivery of my HP2023 and finding this thread after my order had me worried. Have a mixture of +120 Z-Wave devices from different vendors. Today running a Fibaro HC3 as the controller but had planned to move to Homey Pro (2023) when it arrives, but guess it is better to wait until this is fixed to avoid problems.
You shouldnât rely on any home automation platform if safety or security depends on it.
After the problems with the too high Z-Wave traffic, Aeotec has updated their app and optimized the energy reporting basic parameters for some devices. As you start from scratch, these optimized parameters are already set during inclusion. Detailed changelog of the App version 3.9.6 can be found here.
Users who have migrated from their âoldâ Homey have to either exclude and include the Aeotec devices, or manually adjust the parameters (mostly the parameters 111-113: set on interval 3000).
My suggestion would be that you start with a few devices and observe for 2-3 days how the Z-Wave network behaves. Under Developer Tools you can also check the traffic.
2 Likes
You need to run heal or test first.
Than remove is applicable
I got the same message from support, for the beta version of the app. Didnât make a difference for me, but maybe for some. In the last try I didnât see problems with Aeotec products specifically.
