Welcome to the Forum, @audiofrost, @vfamily4, @BBCam, @bigsweg, @amejia66, @GoTron, @dcrockwell77, @jdotphan, and @sockeye7!
Thank you to those of you who are reporting this problem and sharing important details like your app version and how only shared-access users with the v3.10x app seem to be experiencing this issue. Hopefully that will be helpful in isolating and remediating this problem.
Any time you’re reporting a problem with something you’re seeing (or not seeing when you expect to see it) in the app, sharing your app version is a key piece of information. I imagine you’re probably using the v3.10x app, but if you could share your specific version, then that adds another data point for those looking into this issue.
Thanks for the @mention! 
As a community volunteer, I don’t have direct access to the engineers, and I haven’t seen any response from my contact on this, so I’m doing two additional things today:
- I dropped a link to this topic in the announcement topic for the v3.10x app version, because I think that’s the root of the problem, and I haven’t seen it mentioned there. That’s an official topic in a category where only Wyze employees are allowed to create posts, so it should be an area they track here in the Forum.
- Since my point of contact at Wyze hasn’t yet provided a response here, I’m going to attempt an out-of-band channel to see if I can increase awareness of this issue.
Although I don’t have the affected products and can’t replicate this issue, seeing the number of affected users grow frustrates me, and I want to see this solved for you guys. Thank you for taking the time to post your reports here!