You’re welcome. No apology is necessary.
Unfortunately, I don’t have any experience with the Video Doorbell Pro, and I’m also not an iOS user, but I hope that someone who uses both products can provide some helpful input for you. In the meantime, I skimmed recent posts in some related topics:
There’s some speculation that it may be related to a back-end server issue (Wyze seems to occasionally change stuff on the server side that breaks things) and/or a recent firmware update (Wyze has released past firmware updates that have reportedly broken notifications for the Video Doorbell v2), so you may want to take a look at recent posts in those topics and contribute your own experience there for more visibility.
I’d also suggest trying to replicate your problem and then submitting a log to Wyze:
Be aware of the note at the end of the article:
Note: App logs are sent directly to our engineering team to use toward improving future app and firmware releases and will not receive a reply. These logs cannot be accessed or reviewed by our support team.
While that’s true, it’s my understanding that the engineers’ system collects so many logs that they’re often unable to address them without a direct connection to something like a ticket, so when you generate and submit a log to Wyze, their system will send you a confirmation e-mail that suggests creating a ticket. You’ll do yourself a favor by following that advice, and I think it’s a good idea to refer to the log number when you create a ticket. Whichever Wyze Wizard support person responds will likely tell you that he or she doesn’t have access to the log, but it’s important to stress that you want the engineers to be aware of the problem you’re describing in the ticket and the log number for the issue.
It’s not an ideal system, but I hope that it gets this issue some attention and helps to provide a resolution for you.