Clicking on Dashboards on the Hub menu gives the usual list of dashboards.
Selecting the little House button for Local dashboard links seems to work..well at least there is no error displayed.
Clicking on a Dashboard gives a long delay, and then a blank page with the message:
"No response from hub".
Ever since the remote access feature has been released, accessing my hubs has been more and problematic. And thats when the internet is working. When the internet is offline, the hub slows to a crawl - at least from a UI perspective its unclear to me if that also affects processing and messaging / I/O - and the dashboards are not working at all.
Local LAN access and independence from the cloud should be a priority - this has always been the ethos that attracts many of us to the Hubitat platform - but now those of us using the system in an internet-challenged country find ourselves 2nd class citizens.
It looks to me like your hub is maxed out doing something. Your local dashboards should work fine without any Internet connection. Anything in the logs? What do the status logs show? Any run away apps or devices taking loads of compute power? Any power monitoring going on with a too high frequency?
i've had a brief look at the logs, but this only happens when the internet is down, and then miraculously stops when the internet comes back, so it seems that an intrinsically misbehaving device is not the issue, more that the hub is now trying/relying on the internet connection and its causing the UI to freeze or something. i get that annoying http://169.254.9.62/apps/api/1/dashboard/ blank screen error half the time i try to access my dashboards now..especially from the phone - its flaky to be honest and i'm suspicious that these changes to enable remote support have had an unexpected side effect of impacting the hub while offline.
hi there, yep i know what that address is/means.
the hub is dhcp reserved, and its address has never wavered from what it should be.
i've been seeing this msg since the remote access/subscriptions stuff appeared in the UI.
hi @Navat604 thanks for the suggestion..but not sure what you're suggesting?
i'm not using VPN, especially for accessing my hub from my home LAN.
when i mention remote access, i'm referring to the Hubitat Remote Access Feature recently rolled out.
thanks for the BobbyD tag @Navat604 , yes I also run a VPN server for remote access.
Which is why I don't use the Hubitat remote access service.
But this is not the issue, I'm talking about a LAN connected PC talking to a Hubitat hub on the same LAN via its native IP address. No VLANs/routers/VPNs/fireWalls/physicalWalls/Proxies in the middle.
I can't even blame the wifi, this is cat.6 1GE LAN.
when internet WAN is down, it goes pear-shaped, despite LAN communications being unaffected.
when internet is back, voila its back to its happy self...
well this aspect is part of my whinge at the bottom of the original post,.
In my opinion the Dashboard should default to Local LAN links. But they don't, no matter what I do the Dashboard screen (which shows all the available Dashboards ) seems to default to cloud links. At least there should be the option to choose which Dashboard links (LAN or cloud) I would like to default to.
So in terms of WAF (and me) factor:
I have a 'House overview' dashboard on my HA tablet. To view other devices, the user path is to click on the little House emblem at the top left to view the available Dashboards, and click on to desired Dashboard.
Now, if you forget the extra step of clicking on the little House at the top right of the available Dashboards screen, you end up trying to access a cloud dashboard, which of course fails when the internet is down, and after a timeout delay ends up with the error message in the post 1.
The main part of the issue I was raising, is that the hub (just UI? or processing as well?) slows to a crawl when the internet is down.