I'm sure this is a simple change, but I can't find it. I have searched online and through the forum but can't find the answer.
It's driving me mad...
I'm sure this is a simple change, but I can't find it. I have searched online and through the forum but can't find the answer.
It's driving me mad...
I have the same problem since yesterday. It was working fine and I didn't change anything. Sounds like an update broke that part.
It's not the first time and it's usually just a matter of days until a fix. I keep a direct link in my browser's bookmarks for when it happens.
I experienced the same problem myself recently.
In my case, I had changed the IP address of my hub during some testing. When I opened the app, it kept coming up showing Cloud Access, and if I clicked on that, it showed my old IP address.
So can you confirm that the app is showing your current IP address? You may have to try connecting to your hub with a browser to confirm your IP is still what you think it is, and hasn't changed if it is configured as DHCP.
You may also want to keep an eye on this topic. I won't say they are the same cause just yet, but worth watching and comparing notes.
Hi user5298 . Yes, my ip address is correct. I can connect using a Web page, but not the app.
Your problem seems to be different than mine.
From observation and experimentation it appears the app doesn't scan the LAN looking for a hub. It tries to connect to the previously successful local IP address. If that address is unreachable, it then goes to my.hubitat.com and uses the address logged by the hub when it called home.
In my case, after changing my IP, I found my.hubitat.com had been updated with the new address, but the app still showed the old address which made the hub unreachable. It seamed that the app was not updating with the current information from my.hubitat.com.
I tried flushing the cache, which didn't help, and finally clearing all storage resolved the problem.
Based on the above, your app seems to be configured correctly. Did you actually connect to the hub with a browser on your phone, or from another device on your LAN?
Finally, try flushing the apps cache. If that doesn't work, take the more drastic step of clearing all app memory.
I connected to the hub on the browser on my phone. I can connect locally using a shortcut. I can also connect locally by opening the app, select the 'my account' head figure at the top left of the first page upon opening, selecting 'registered hubs', then clicking 'connect to hub'. (hope you can follow this... )
I have also deleted the app and reinstalled it with no joy. Clearing the cache makes no difference either. I'm reluctant to clear data as I don't know what this will do, also I think uninstall the app will have done this anyway??
I'm at a loss.
You have described your problem very well, but I just want to clarify that when you open the app, while connected to WI-FI, you see a screen that says "cloud" while you are expecting to see "local". See image below.
If you open the dashboards tab (bottom of screen), do you have access to your dashboards? Do they respond quickly, or is there a lag indicating they are being accessed over the cloud?
You are correct, clearing all storage brings you back to a freshly installed app.
Although unlikely to help, if a fresh install didn't help, you could try rebooting the phone to force all apps to reinitialize.
Yes, it says Cloud. I tried rebooting earlier, but it made no difference to this issue. The dashboard opens and there is a small delay, but only a couple of seconds.
I have this same issue, and have had it for awhile. I'm on the latest Android app, but still use the old one because it is the only way I can access and see some of my dashboards that Actions taken that have not solved this:
There is a thread here about it that I also posted to: New App Dashboard Local Access - #5 by calinatl