You’re not off-base. If you want to know more details I can explain a little more. I think things like this are an occasional unexpected glitch based on the way Wyze’s initial database was set up. From what I gather/understand, when Wyze first started, their database was set up to where the email address was listed in the backend as what’s called “the primary key” in the database. This caused some issues in the past where people could never switch their email address because that was the “account number” and you can’t change the primary key (account number) or it can cause chaos. The best practice is to have a totally separate, unique account number as the primary key for each account and have the email address be a totally separate field that can be changed at any time without disrupting anything. Basically, it required canceling an account and starting a new one and setting everything up from scratch again. The bigger Wyze got and longer time went on, the bigger problem it became that people couldn’t change their email address. This particularly became an issue as it related to subscriptions and things like the Wyze Cam Outdoors and Base Station that were tied to a specific account. You couldn’t close and open a new account without potentially risking causing loss of subscription money or bricking WCO’s/Base-stations. So Wyze created a “fix” or a workaround to simplify Email address changes, and now it works fairly seamlessly for 99% of users, but there are still some weird circumstances like this where I believe what is happening is that because you had a grandfathered package that is no longer available, it won’t automatically transfer over correctly because of the foundational database structure issues (I believe they weren’t fully converted since I still rarely see weird issues like this). So in my somewhat educated opinion on the matter, I would argue that this isn’t your fault in any way, and is simply leftover fallout from the way their database foundation was structured less than optimally.
Therefore, I am hoping @WyzeMatt will take a look at this for you, agree that it’s not your fault, that you didn’t choose to cancel or change your HMS subscription, and that you deserve to keep your grandfathered plan rate and shouldn’t be “punished” just for changing your email address but not intending to change anything else. It’s a glitch I’ve seen on rare occasions, but I’m pretty confident it’s a backend glitch and I’m hoping WyzeMatt can find a way to resolve it for you, because I pretty much guarantee that it is above the access of anything that support can do for you.
Nonetheless, let’s give him a chance to look into it. I know you haven’t replied to your support ticket yet, and maybe Matt might ask you to do that still, but will you at least post the support ticket number for us in here?
Also, will you submit an app log of whichever you think might be the most relevant and post that log number in here?
Also, appreciate your patience and the way you handled this with grace, etc. You’ve always been a reasonable guy @raym64 and very helpful. I’ll follow up and make sure Matt gets some eyes on this. I know that as the main subscription guy he would like to be well aware of this glitch because he wants people to have a good experience with his subscriptions and this will be something really useful for him to look into better.
Edit: To be fair, my above hypothesis, is just a hypothesis, but I have seen email address changes through Wyze cause similar chaos before (particularly with subscriptions), so I believe this is a likely cause because I do know that the email addresses USED TO BE the primary key that everything else was tied to, and I see it still doing weird things on rare occasions. So, I am not saying this conclusively, but I feel it is a fairly educated guess based on my database education. 
