Let’s hope so otherwise I reckon I’ll be at an hourly reboot !!!
Not me, although I doubt I’d notice any difference, as I am already on 10.3.3, and it seems to work fine. I haven’t rebooted it since the day I migrated from my 2019 though (which is a bit over a week ago), and if I run the risk that I’ll have Zigbee issues as a concequence of the reboot that inevitably happens after the update, I’d rather not try.
I’m not using Matter, and I don’t care if they have improved some translations, so there is simply no reason for me to update to this one.
FYI: I had no real zigbee issues, but after upgrading to v10.3.5 the issues became more prevalent for me the last week. A couple of bulbs became unresponsive over the last few days (60 devices, plenty of routers).
I also have big zigbee problem on 10.3.5, can not add more, can not reconnect / repair and very slow. Anymore with some ideas to fix, while we are waiting at Athom ??
110 Zigbee, 90 is route and also 2 bridge on.
HUE is working again, Aqara roller and door sensor not. Repair and remove / add does not help
Version 11.0.0 now released and a lot of effort gone into developing Moods but no progress on the ZigBee issue, very frustrating and feels like effort would have been better spent in fixing the core issue, not adding new features. I’m still having to reboot 3-4 times per day to maintain some sort of stability with curtains and blinds. If anything, the issue seems to be getting worse since the orignal 10.3.0 that broke everything.
they do work on it, performing now QA - quality assurance / testing… in case they will not discover major issue, I would expect solution maybe within 2 weeks latest - let’s see
Can some tell me what’s in this version 11.0.0 update? I don’t know where to go and see what is new with these updates
Check this out for all changes
A solution in 2 weeks could be good as this has been affecting a lot of ‘patient’ users for quite a while now.
Thank you
v11.0.1-rc.1
Core
Fixes an issue where capabilities would be outdated after a reboot.
Fixes an issue where devices could show as unavailable after they were added using the Homey Web App.
Matter
Fixes an issue where a bridged Matter device would incorrectly remain unavailable.
Fixes an issue where new devices added to a Matter bridge would not be added to Homey Pro.
Fixes an issue where setting the dim value of a light to 0% would not completely turn off the light.
Fixes an issue that could cause error 0x0704 when adding a Matter device.
Removed beta status.
Zigbee
Fixes an issue where end devices could not rejoin the Zigbee network.
Fixes a Zigbee crash that could occur when a Zigbee device would rejoin.
Decreased the number of messages that will be sent to devices which are currently unreachable.
Sounds promising bugt may hold off for a little bit while its tested
I understand your frustration, but I expect that the ones solving the Zigbee problems are different developers than those developing Moods. So the Zigbee fix doesn’t have to be issued later because of Moods.
Am having Zigbee troubles as well and I hope too that they are fixed with the latest beta firmware. But I wait a little to see how this firmware holds as well… 
Yes this is absolutely right and involves developers outside Athom and deep firmware fixes.
A quote from Athom’s current release notes:
“We are working together with Silicon Labs to resolve this issue as soon as possible. A fix is currently being tested internally and will be released in a future firmware update”
2 Likes
Sharkys… are you saying that the fixes that are included in RC1 are designed to address specifically the current firmware issues that people have been experiencing for weeks?
I would say so, also the comment about Zigbee disappeared.
1 Like
That’s great news…. 
Henk
Probably my bad wording there, wasn’t really frustration as I’ve been very patient and continued to help others and work with some of the App developers to improve other things in parallel. It was meant more that prioritising the work with Silcon Labs to get stable again would be good as it seems to have taken quite a while. I guess the biggest drawback is not having a firmware rollback option unless you have a physical backup from same version, something that maybe good to add in the future so any issue like this could be rolled back while a fix is developed. It certaintly wasnt intended in a bad way, I’m very supportive of the product and its future development, I have a lot of devices attached to it and I’m a developer too so know how challenging issues like this can be sometimes.
2 Likes
