C8 Pro
Android app 2.0.6
Platform 2.3.9.200
Recently added remote admin, but seems innocuous.
I was able to access via my laptop and tablet (also on 2.0.6).
I tried uninstall/install of the app. No change. Not sure where to go next. Any ideas?
What Android OS version are you running?
Android 14
And fun fact... It connected after several more attempts.
Heading out on Thursday for a 5 day trip. It would be awesome to have confidence that I can connect on the road.
I think there were new updates to the mobile app... Any help there?
Reboot phone?
I know you don't want to hear this now just as you're leaving, but I'm going to say it anyway. 
Absolute best friend & remote access solution is VPN. Tailscale\Wireguard would be a good travel buddy. Free for personal use.
I saw the same message locally, so not sure that the VPN would have helped. Haven't had a reason to access the hub on this trip (yet), so maybe I can just revisit when I get home.
True...if the "Cloud" issue is present a VPN likely won't make any difference. My comment was more generic regarding a VPN being my preferred/recommended way to get to the hub remotely.
2 Likes
Seeing this again today. Not sure what changed. Not digging it, though. Pretty much expecting to access my local system locally.
I used the IP address to do what I needed but would prefer to have the app behave. Not sure what to try.
Did you try clearing cache on the app?
Actually, yes. And a phone reboot.
For grins, I just tried to access remotely. The app goes in circles: switch to another hub <---> choose a device.
Clicking "Remote Admin" brings me back to the unsupported browser message.
The app still allows me to access the bottom menu (devices, dashboard, notifications).
remoteaccess.aws.hubitat.com still works on both the phone and computer.
1 Like
... And it is back to working again. Not smart enough to know if it was based on any of my own purposeful actions.
Since the message was "unsupported browser", I cleared the cache for Firefox (my default browser). Remote Admin now behaves as expected in the HE app.
So, my current hypothesis is that the Firefox app holds onto some artifact in its cache that eventually causes a hiccup. If/when I observe this again, I will try the browser cache first.
1 Like
Working fine for me on 2.0.9.292, on S21/Android 14. Default browser on my phone is Chrome. 
YMMV rears its head again.
Ah .. I am using Opera .. prob the problem 
1 Like
If you confirm changing default browser resolves the issue, post back about it. Not sure if there is a list anywhere of supported browsers for the mobile app.
Yeap .. that is it .. switched to chrome < works now.
Switched back .. no work ..
1 Like
I believe the HE documentation says that the mobile apps use an embedded browser. Funny that an OS default browser change affects use of the app's embedded browser. @bertabcd1234 - appreciate any comments on this?
No, but I'm not sure how Android works. On iOS, any app's embedded browser is basically the one from the OS that you don't have much control over (i.e., a slightly limited Safari), but maybe Android is different. I suppose the best question would be whether it works the same in that external browser -- and then what specific version of that you're using (and the UA string if you can figure out out).
2 Likes
On Android, apps use whichever browser you have set as default. Samsung forces the Samsung browser for a few apps (Samsung wallet is one). But uses the defualt OS browser for everything else. I keep Firefox and Vivaldi installed to swap when I have compatibility issues. Different apps have different issues with one or the other sometimes. I use a browser to listen to news on Youtube TV on the way to work so that I can turn off the screen and just get audio. Chromium browsers were having issues with the video extensions, so I have to use Firefox for that. Other apps don't like the chrome/chromium based browsers for logging in.... so, it is handy to be able to switch back and forth.
I never had a problem with HE and Firefox. BUT, I have my Firefox set to clear history and download cache on exit. So, maybe the original post was on to something with a cache clear.
Note: You can see which browser is in use by clicking the 3 dot menu in the upper right once you connect (but if you are not connecting, that could be an issue
1 Like
