cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Smart Hub Plus SH31B Router Firmware changelog

monitorcurve
Established Contributor
Established Contributor

Hi,

Just thought it might be worth putting up a list of all the firmware rollouts for the Smart Hub Plus SH31B Router that have happened in the past year or so to see if this adds/removes functionality or fixes/introduces any bugs to the routers.

Last night mine updated to r1.34.1-R-1055417-PROD-83002 and with this firmware update the app version was unchanged.

Changes:

 

43 REPLIES 43
Huggons1
Established Contributor
Established Contributor

Will be interesting to see if the Smart Hub Pro receives r3.8.30-R-1627300-PROD-83002 and if it fixes the fixed channel bug and the ethernet port bug on the Smart Hub Pro.

monitorcurve
Established Contributor
Established Contributor

Yep my hub upgraded to

App version: 3.1.18
Firmware version: r3.8.30-R-1627300-PROD-83002

in the small hours last night

Also now get the following when going to the router page as well now which shows up as an invalid certificate.

Secure Connection Required
Access to the Hub Manager now requires a secure HTTPS connection.

Switch to HTTPS
⚠️ You might see a browser certificate warning - what do I do?

https://ee.co.uk/help/broadband/fix-problem/hub-manager-security-warning


 

Ewan15
Expert Contributor
Expert Contributor

@monitorcurve  Click Advanced

Ewan15_0-1764947513724.png

Click continue to 192.168.1.254

Ewan15_1-1764947599506.png

The EE Router page will then open

 

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Home Broadband & Home Phone or Option 2 for Mobile Phone & Mobile Broadband.
monitorcurve
Established Contributor
Established Contributor

Yep already done that and accessing the router page fine now - but may trip some people up and think there is something wrong as accepting invalid SSL certs from websites is bad practise and shouldn't be done.

From my understanding it's not possible for a valid SSL certificate to be issued (and globally signed) to a private IP range like 10.0.0.0 to 10.255.255.255, 172.16.0.0 to 172.31.255.255, and 192.168.0.0 to 192.168.255.255 etc it would have to be for a domain that is publicly resolvable, so the not secure icon is always going to show up in the browser url bar.