This has been going on for some time now and I'm not sure if its intended to work this way or if I have some unique issue.
If I am at home or any of my local hub locations and use the local EZ dashboards, I have to log in with the hub username and password. If I am away and no longer local (not on WiFi) all the dashboards load up and work without issue...
It's frustrating because not only do I have to stop and enter credentials, but the family members do also... Its more of a pain for them to do it and doesn't really seem necessary given when we turn off WiFi or leave home, the dashboards just work.
I've tried deleting the app on the phone and resetting it, deleting the created device on the hub and even messed with the beta version, and they all keep displaying the same behavior.
Is this supposed to work this way? I would think the app would pass the logged in user credentials along to the hub. That appears to be what happens when it goes remote.
Thank you.
@gopher.ny any update on when this might be fixed?
As a temporary work around for this, you can log into your hub via your phone browser and go to the dashboard page, then open the cloud links for the EZ dashboards you want to use. from the browser, install the link to your home screen. I created a folder and saved all the EZ cloud dashboards there. The cloud links don't require login.
Yeah, that's what was throwing me... the cloud links work...
Thanks for the suggestion. I might do that for me, but that will be too complicated for the family... Wife, kids, and in-laws won't understand when to use which one...
I'm hoping gopher picks it up as its been lingering out there for a bit... 
Maybe if others weigh in, we can up vote it... 
@jtp10181
I just gave up using and testing the app, stuff being reported was not being fixed. Every update now is just to fix crashing and geofence issues it seems like.
2 Likes
Honestly, just having the bookmarks would probably be easier for the rest of the family. That way they don't have to navigate the UI of that new app.
The problem is when they leave the house... Unless you mean just load cloud links?
Yeah I made special (classic) dashboards for my kids and had them save the cloud link, works from anywhere as long as the hub is online. Our internet and power is pretty reliable here so not an issue for me.
1 Like
Yes, just save the cloud link as a homescreen app on IOS. Much easier for non-techie persons to use.
1 Like
Thanks for the suggestions, I'll give it a try!
but @gopher.ny hopefully you still get this on the to do list...
This is still an issue, still waiting for a fix.
Really?
This started working for me again with a recent beta app update. I don’t recall which build exactly, but I can now get to easy dashboards without the hub login screen butting in. I’m using 2.1.1 build 404.
I am on 2.1.1 (404) iOS, I just tried it again. I even logged in once, it worked while app was open. Force quit the app and restart, back to asking for log in.
Because of this I have not even bothered making any EZ Dashboards other than a simple test one. I was planning on moving all of mine to EZ. I dont use them often but its handy if you need access to something quick that I don't want to share to Homekit.
Oops I’m on build 404, that was a typo (now fixed).
But that’s strange. Since the issue occurred (quite a while now as you noted), each time I update the mobile app, I usually try to load an easy dashboard to see whether it persists.
It wasn’t too long ago that it started working again for me. Maybe build 390 or 387.
Hmm, now if I force quit the app and try to load an easy dashboard again, I do get the hub login screen.
But if I tap around to a few other app screens, such as the home tab, then go back to the dashboards tab, I am able to load the easy dashboard without first seeing the login screen.
Not sure what’s going on there, but it does seem like they’ve changed something and are making progress on the issue at least.
@moncho1138
1 Like
A fix for this will be on the next beta build.
3 Likes
Thank you… it really is a pain, especially being home in a relatively safe and secure environment… I’ll just add it has been a constant for me since I weighed in and I never experienced a fix even with some of the betas… Extremely grateful for you all looking at it…
1 Like
This is still an issue as of 2.1.2 (411)
