@Chris_B You can keep tuning the reason you give but it still stands that it's does not change what I said about having a router level web admin interface to unpause a device group. The servers being down need not prevent a user from changing wifi controls, it currently does because EE chose to expose the wifi controls in the mobile app only and not in the hub manager.
You said "The app is just a portal to your account and it needs to link to your account in order for it to work correctly." which is just another way of saying what I said above about the app workflow. But is also ignores the fact that technically EE could allow us to manage wifi controls like pausing without actually needing to be signed in with our EE account at all, it's just that they've setup the mobile app workflow that way currently. To explain further, you have linked two accounts to the app when you first set it up. First, you have linked your EE account as you have rightly pointed out. This will be used to pull data about your account and contract services into the app. It will not be used to pull the status or config of your router/hub. For that, the second account linked to the app is the hub admin account (the one printed on the back of the plastic insert on the back of the hub, the credentials of which are stored by the app when you either scanned the QR code or input the username and password manually). So now that the app has those two sets of credentials, it can query your account details from EE services, and it can query the hub status and config directly from the hub itself.
In addition, you can log directly into the hub in a browser using the second account I mentioned above (the hub admin account) and manage a limited set of the configuration. You do not need the EE account to do this. However, the functionality of the hub manager directly on the hub is limited for some reason and this forces you to use the app. So, if, like I said originally, the hub had been given a fully functioning hub admin interface, we would not need to use the mobile app, ergo we could update the pausing and unpausing of the device groups without needing to login to the EE account. So it wouldn't matter if the account or the servers were unavailable because those are not where the WiFi control configurations are stored - they are on the router directly. Do you see the difference now and understand why I said "they should have implemented an actual useful admin web-interface in the hub" to solve this problem of not being able to update the router config when the mobile app is affected by account access, be it server maintenance or app updates?
