I believe the slow page load issues has been identified. Something on the hub side of things in trying to communicate with something on the internet. Because I have the hub blocked from the internet most of the time. the pages load incredibly slow while it is waiting for something to time out.
It seems like hub without cloud might be getting harder and harder to do!
@gopher.ny I know you are looking at this issue now so please let me know what you come up with!
I'll look into the Wait for Mode Home thing. There is a new version of Rule coming in 2.2.5 (Rule-4.1), and one thing that's been gone over is Wait for Mode. So, all of that code is very familiar to me right now, and I'll see what's going on.
It does try to connect to Amazon MQTT, yes. But that's been around for a long time. I'll put an endpoint to turn the cloud off (and back on) in the next version. Nothing critical depends on it. Safe mode, for example, loads without cloud. Anyway, this would be better than cutting the traffic off at the router and having the hub try to pointlessly reconnect all the time. Also, you'd need to turn it back on if you want us to look at the hub.
I don't see anything obvious tying the hub up at the moment. You got plenty of devices but not that many, and average load is low. So this slowdown thing is UI specific, I got all the necessary information off the hub now and will try to see where that slowness comes from.
There is no DHCP setting for NTP, true, but we got these endpoints (since 2.2.4):
/hub/advanced/scanForNtpServers - scans local network for NTP servers and shows the list.
/hub/advanced/ntpServer - shows current NTP server
/hub/advanced/ntpServer/<-value-> - sets NTP server
In my limited experience, emails sent using SMTP from a home IP address are most likely to get rejected outright by the ISPs, anyway. There are too many malware/spambot networks out there. Even with reputed providers, deliverability is hit and miss.
There is a DNS timeout setting in 2.2.4 meant, ironically, to recover from a temporary connection drop. The hub is trying to resolve a name on every click.
The good news is that "no cloud" flag is easy to implement, and it appears to solve the "slow UI" issue by the virtue of skipping the offending network request altogether. The bad news is it's not going to be available until 2.2.5.
That doesn't sound quite right as it should be able to resolve the DNS name because it has access to a local DNS server. (which can access the internet) unless it is again using some other DNS sever that is not assigned via DHCP.