Homey pro 2023 - zwave too much traffic error?

Although I understand it would be better if more people report these issues, I really do not dare to perform the migration to HP2023 at this time. It feels like Russian Roulette.

I have same issues can’t add zwave
Last firmware


It’s not ok to sell homey pro
:sleepy:

Please send a bug report to Athom via the mobile app. We need to raise the knowledge about this.

1 Like

I don’t now how

Maybe this is one place to report issues?

https://support.homey.app/hc/en-us/requests/new

1 Like

Homey Pro 2019 (or earlier) users are also affected by the dying RS3 and the pulsing blue LED, so it’s not only HP23 related.
What’s really interesting, it seems that only Homey user in generell affected by this. So I would suggest to contact Athom and inform they about this issue.
Bot this issue is OT.

1 Like

What can I do it’s not working right now can’t add some
Zwave only zigbee I write to the support an they say 1 or 2 weeks I must wait but I bought this for 5000 Swedish krons is not ok

I have the same problem. The only work around is to disable other apps while you do the adding of the new device.

From the phone app click the 3 dots/ More > Apps > then select an app > then click the cog/ settings > then disable the app. Keep doing that with more apps (except the one that you need to add the new device, of course) until the new device pairs properly. Then re-enable them.

1 Like

Hello thanks for helping me but it’s not working


Not sure what else to suggest. Maybe try turning off all apps except for the one that is for the device you’re trying to pair, rebooting Homey (unplug the power) and then restarting.
In any case, probably worth raising a support ticket as others here have suggested

1 Like

A send a ticket but it’s long time to wait 1 or 2 weeks
Homey say

As i wrote in the german topic Early 23 Z-Wave Problem:

With new versions of Homey-Firmware, my procedure for testing the new version was always the same: Creating a Cloud-Backup from the HP23-1, set HP23-2 to factory settings and set it up again with the Cloud-Backup from the HP23-1.

After that, the well-known Z-Wave problem was present and the HP23-2 was not usable. New idea (delusion): USB-Backup and USB-Restore.

Created a backup of the HP23-1 with v10.0.0-rc.118 via USB. Setup HP23-2 via USB with the USB-Backup from HP23-1 and updated the HP23-2 from v10.0.0-rc.118 to v10.0.3. Findings:

  • Temperature
    HP23-1 v10.0.0-rc.118 > 68 degrees / HP23-2 v10.0.3 > 74 degrees

  • Load Avergage
    HP23-1 v10.0.0-rc.118 > 3 to 35 % / HP23-2 v10.0.3 > 25 - 65 %

  • Flows Limit
    Creating a new flow is not possible because there is a limit of 1000 flows.

For about 24 hours now, there have been no failures. I don’t really like the high temperature, same with limiting the number of flows. Reported the Results to Athom.

2 Likes

Another observation:
If chaning a parameter on e.g. an Aeotec switch, Z-Wave acknowledges its service. The temperature goes up to 76 degrees (sysInternals). I don’t really have confidence in my HP23-2. Using the “new” Powery-Supply from Athom.

Shouldn’t solve the problem. You add a new unit, but to what? A network that does not work due to the chatty units.


This is an unknown unit, it think it is an orphaned Sunricher transformer. The problem is that I am unable to remove the unit (I press the three dots and it is grayed out).My plan now is to do a reset, and reainstall my last backup from my old homey, but he sun richer app has now been ported. Hopefully it works.
This is driving me insane, nothing of the smart home stuff is working since two months, and the family patience is wearing thin.

This is 100% a Homey23 issue. Early adopter or not, Athom has to fix this.

1 Like

It doesn’t fix anything, except if the so-called/undefined “chatty” devices are not chatting at the point at which you’re adding your new device but their “chat” would have otherwise drowned out the pairing communication

I agree homey are shit now it’s a joke

I had relatively little discomfort the past 2 weeks. In the meantime the timeouts are increasing rapidly and it is no longer workable here either :frowning: This is really a disappointment! Athom?

Athom does not normally check this community forum. It is for us users to exchange information.
Only good way to get attention from Athom is to report a bug via the app.

Exactly, we should all report the issue to Athom.
I don’t know if it is true, or how long it will be true, but Athom is mentioning that only a limited amount of users is affected. So if the majority does not report the issue, it might not have the same priorities as developing more widgets in the homey app.

3 Likes