My 2nd Smarthub packed up today.
2.4ghz became unresponsive attempted log in to Smarthub manager, this was unresponsive taking ages to load with Chrome asking me to 'kill' the page.
Power cycled the hub, now stuck on orange, attempted factory reset, un responsive. UNIT DEAD.
Believe the 236 firmware still in use.
Back to the HH5 AGAIN.
I haven,t had any problems with the HH5 since i replaced it for the Smart Hub 6 rubbish ! I was going to get an Asus or TP Link Router ,but i,m happy with the speed and wifi i get in the house from the HH5 🙂
No DHCP issues of note.
Reported earlier that 2.4Ghz was solid....spoke too soon
as I am now getting drop outs and 'Limited' on 2.4 as
well as similar issues plus 'Cannot find network' messages on
5Ghz so it seems latest firmware 223E is not yet right or better.
Problem with all these issues is it is impossible to put
a finger on what is going on. You just end up with a
frustratingly unreliable service with no fix in sight.
Talking to India is a waste of time as they just cut you
off when the going gets tough and the 'script' is not
My Hub 5 was better if not completely stable.
May bite the bullet and try an TP-LINK VR2600 V2
which on paper looks an upgrade in spec with
pretty good reviews. The VR900 is a lot cheaper and
gets similar reviews and might also be on my list.
It appears with Routers it is sensible to wait until issue
2 or 3 of firmware arrives but with BT routers a lot more
versions before you can get mildly excited.
This latest update is driving me nuts every time we need to connect to the internet I have to do a factory reset (the only way I can get it to work)
I'm not very tech savvy but in sheer desperation have joined this Community to see if I can get help.
BT PLEASE do not work on implementing any more features before you have
got the UNSMART HUB TO HOLD IT'S CONNECTION FOR MORE THAN 10 MINS.
Just added to my observations, if any device is connected to the hub, it works fine. If a device disconnects from the network, it is impossible to connect until a factory reset is carried out.
This happened on 27/11 after a firmware update, prior to the firmware update, the hub was rock solid.
Please can the firmware be rolled back!!!!!
I had this problem with the first three firmware versions (currently on 2236). Rolling back the firmware would make no difference to me.
I think the problem is the inability of the Hub DHCP server to allocate IP addresses to connected devices. My solution, described elsewhere on this forum, has been to assign static IP addresses, outside the DHCP range, on the devices which do not seem to be fully recognised by the Hub.
I know we shouldn't have to do this but it has stopped my wi-fi problems.