Not really, for the full investigation is required to share not only symptoms but even what happens before or what has triggered that behavior… so far I have seen zero System diag shared, so I hope they were provided on all the cases to Athom at least…
I don’t even know how to share that with you… So i guess this goes for most people. Like probably everyone else you make a diagnostics report and submit that to Athom. That’s what I did.
Well, it’s the diagnostic id (eg. 1DDC38D9), that you shared in the form used to report bugs in HP23 (Settings-General -Create diagnostic report). But anyway, I was expecting to get few reports yesterday, to increase priority of complains here.
Ah, are we talking about that id? That wasn’t clear for me. You’re free to check out mine; 5705B7F2.
But, are you part of Athom, since you’re saying you want to increase priority?
No, I’m not - more over, please share the ID when it happens, not eg. when the issue is already in progress for several hours
The ID’s are shared with Athom when it was in fault. There is no way to know exact when it starts, as Homey does not give an error proactively. It is only that I notice when nothing is responding.
…and if you notice it early, then it’s worth to imidiately create diag. id - because then Athom sees what precedes the issue, nothing more nothing less - just increasing the probability they catch the problem as obviously it did not happen possible for hundrets of users (eg. like me)
I also did, they have 3 reports from me since about 10 days, unfortunately still no response.
How many zwave sensors do you have? And what do they report and how frequent?
I think the pattern is that the chatter is always high , but when someone walks from the attic downstairs (passing 5 sensors), homey might collapse. Perhaps users with less sensors, dont experience that, as the chatter is in the background.
Also if you look in your log, do you also see same sensors having tons of messages in seconds?
That report is from when it happens.
1 Like
Great, so we have one 
Hello,
I have the same problem after las update
Since I migrated to homey pro 2023, there is also a significant latency on all zwave objects and that I did not have on my homey pro 2019
Some objects no longer respond and you have to switch off and on for them to work again
Sorry for my english ; i’am french
Just moved over from smart things and added more than 100 z wave GE switches to the new 2023 homey pro. I get the same error “Could not send command. Too much z-wave traffic”and now nothing works. What a bad move.
Athom has replied via Slack;
Yes. Somethings different between the chips and we’re looking into the issue with Silicon Labs.
2 Likes
I get your disappointment, but you bought a ‘early access’ device, and you’re part of the test team for now 
I suddenly got the same behaviour yesterday also using RC122. It works for a brief period of time after a restart, but then it comes back.
My quick solution is restart of Homey all 6 hours twice
Not nice, but solves the biggest problems.
Well, my wife is now also a part of the test team and I can assure you that the WAF is well below freezing point.
1 Like
You must keep sharing the progress with her and lower the expectations
I do hope there will be fix within a week latest… it’s nothing more then just my personal hope
1 Like
The firmware change log has just listed v10.0.0-rc.133 as now Stable, changing it from Experimental.
How can that be when we are reporting “Zwave too busy” issues
Could not be further from the truth, extremally unstable on my system.
You can see from this thread that the issue appears to be affecting lots of people using 122 as well as 133. The issue didn’t seem to have arisen before 122 but 122 was already marked stable before this issue was first raised. So I guess the argument could be that 133 is at least as stable as 122. Slim comfort for those with this issue.
Although I am one of the lucky ones who hasn’t YET seen this issue (touching wood as I type this) I will not be upgrading firmware or doing pretty much anything else with my Homey until this issue resolved as I am dependent on a large set of z wave devices and I want to minimise the risks of causing this issue to crop up for me. I still have my Homey Pro 2019 to fall back on if needed but I’d really rather not. Let’s hope there’s a fix for this soon or at least some comms from Athom.
In my view it is poor that this is not listed on the ‘known issues’ section of the early access page by now given how many people are seeing it and how significant the impact is for those that are.
