New APP Issues

,

I upgraded to the new Hubitat Elevation app because the old app said that it was going to go away by the end of last month.

I previously had everyone logged in as the same e-mail address and selected different presence devices. I kept getting logged out of the app so I ended up creating guest accounts and logging in everyone with the guest accounts and that worked for the logout issue

Now, the issue that I am having is that the guest logins don't seem to allow presence to happen. My icon in the dashboard just shows a question mark on the location status. Is there any way to get a guest account to work with presence? So far, this new app is completely worthless to me because it doesn't work the same as the old app. I can't use HSM because the guest accounts don't register presence of their phones.

I have a C-8 Hub with Samsung Galaxy S23+ phones running the Android version of the app.

Thanks in advanced!

Go to More > App settings and verify each phone is connected to the correct virtual device on the hub.

Go to Home > Tab Hub Name at top > Switch to Another Hub
Re-select your hub and it should auto-select the previously selected device (if not select it again).
This will reconnect the app to that device.

If still not working after that you can try this procedure where you let the new app app create a new virtual device on the hub.

Thanks for the response! I did this exact same process and it fixed their notifications but it did not fix the presence issue. I noticed with the new app that it automatically resolves the device ID to the phone and it doesn't appear to give the option to switch to a different device. Our family all has the exact same model of phone so I have to let it build the device, go into the device in the hub and add our initials to the end of the SM-S916U (phone model) within the devices and then log out and back in on the app, it always updates to the one with our initials at the end but that is the only way I have found to get it to work with the same phone models. Does the new app handle that differently where I don't have to do that and could that be causing a problem? The old app wouldn't work at all without doing that process.

It links directly to the device ID on the hub, the name of the virtual device on the hub does not matter (and has never). Once the app creates the device you can name it anything you want.

The change with the new app is that it also remembers the "DNI" of the device it attached to which is what lets it auto select the same device if you log out and back in again, or if you have multiple hubs and switch hubs. Based on how it behaves I think this is linked to the actual HE account on the cloud side (guest or otherwise) but the dev did not confirm this. When you let the new app create the virtual device itself it creates a DNI in its preferred style (which I think is the Android device UUID for the android app). For some reason it seems to work better when using its self-created DNI and not a virtual device created from the old app using a different style of DNI.

That makes sense - thanks for the additional information on that.

I think the reason why I had to put our initials as the end before was because it didn't show the device name only the model and so I had 3 phones with the exact same model so by adding the initials it made it easier to make sure I was selecting the right one. Now it shows the device name as long as that is added to the device when it gets added to the hub so I will try it again without adding the initials and see if that works better. Thanks for the input! I won't have the chance to work on it until tonight since I don't have access to their phones during the day.

If you already had the new app create the virtual devices I don't think doing it again without renaming them will fix anything.

Have you check the geofence settings on each device to make sure the circle/pin is where you want it? The app should default to the coordinates set on the hub itself in the Settings > Hub Info page, so if that is wrong the geofence will be in he wrong spot.

I have done that - initially our hub didn't have the right longitude and latitude for our house so it was defaulting to a different area but I updated that in the hub and the pin comes up in the right area now. I had to enable the Geo Fence within their app and it shows that they are inside the geo fence but when I look at my dashboard on their device it just has a question mark. HSM isn't arming due to it not receiving their presence data. Which I guess is better than arming and constantly throwing intrusion alarms :slight_smile:

I did all the steps again and still didn't work with their app presence sensors. So I renamed the presence sensor with all the automations attached to it to _OLD again and then let both Hubitat Mobile (old app) and Hubitat Elevation (new app) build new separate devices and named one Phone-Tiffiny and Phone-Tiffiny2 for the new app. The one that is on the original app is working with presence and the one that is on the new app is not working with presence at all, it has a ? on it even though geofencing is enabled while the original app is working with presence. I really think there is a bug with guest accounts and presence on the new app. My account is the admin account and it works fine with presence on the new app. In fact, the other phones that I am having problems with were all working with presence on the new app with my login but the GUI wouldn't stay logged in since it kept logging out every time someone else would login but the presence continued to work when they were under my account, we just kept kicking each other off. That is the reason why we are having to use guest accounts, I would prefer to just use a single login like I was doing but that doesn't appear to be an option if we want access to the GUI.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.