App no longer allowing downtime schedule or managing devices

Thank you for reaching out to us @JohnKG! Upon signing in to the primary username for my account, I was able to add a person, assign devices, and then schedule downtime for that member. We will want to make sure you are signed in as the primary username on the account. Please

Sign in to our website here.

Sign in by clicking the icon in the top right of the page.

Once signed in, please select the purple icon in the top right of the page.

Select “Account and Identity”.

This will take you to the Account and Identity page. The name linked to the username used to sign in will have “Primary”, “Manager”, “Member”, or “Viewer”. 

We will want to make sure it shows “Primary”.

With that confirmed, we will want to confirm this user is on the correct address for your current account. On the “Account and Identity” page, the address will be below “Account Details”.

Went through these steps and even though absolutely no one else has access to my account when I checked it does not indicate Primary, Manager, Member or anything else. This is so frustrating 

Tried in a web browser as well as the broken app. Same results nothing

Hey there, @user_eambnj! Thank you so much for taking the time to reach out to us here on the Xfinity Forums. I am sorry to hear about the experience with your profile access. Have you attempted to clear the browser cache and cookies and attempt to see if the option to indicate what level of access you have? 

@XfinityAldrik​

UPDATE!!! UPDATE!!! UPDATE!!! UPDATE!!! UPDATE!!!

All my "People" ARE BACK!

For no discernible reason — other than that Xfinity must have quietly fixed something on their end — everything is back to the way it was almost TWO MONTHS AGO.

So now, I can once again assign devices to people, turn on/off access to WiFi for individual devices or people, set downtimes, etc.

Also important to note, I have not updated the app to regain these features; I'm still running the 5.38.0 version of the app from their update 3 weeks ago. The latest version of the app (5.39.0) was released 6 days ago, but my phone had not yet updated to it.

So, it's still a mystery why this problem appeared — and how it was fixed — but I'm glad it FINALY HAS BEEN FIXED.

p.s. Also notable is that no amount of signing out and signing in with my "Primary ID" — which is the ID that I had been using ALL ALONG — helped to solve this problem.