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.
Today is one of the “better” days. Sixth reboot so far and the error immediately after reboot.
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.
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.
1 Like
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.
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.
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 
I’m curious, different Z-wave apps? In my case I’ve disabled iBlinds and enabled Fibaro to make it works.
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). (The other 19 employees are presumably commercial)
It’s not ok fix the problems 
No point expressing it here - they don’t read read it. Only Support tickets, App store reviews and Facebook
hi do you think homey pro will get better or if i do a reset or is better a send unit back
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.
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!
1 Like
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…
1 Like
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(!), before HP2023 even existed.
1 Like
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:
Ask Pierre to buy you one 
1 Like
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?
