Well, that’s good to hear that some vehicle notifications came in for you. 
There are certainly multiple things that could be going on.
Off the top of my head, they may have modified the detection sensitivity thresholds, which they’ve done silently before in the past, and caused people to stop getting detections at the same distances they used to. I believe they do this to reduce how often the cameras upload videos to save on their cloud event uploads/costs. This would make sense as to why you got vehicle notifications when you were outside, because presumably you would then be closer to the camera and so so the detection sensitivity threshold was hit by you being outside and close to the camera, and then it happened to review the car passing by which was farther away. Even if it was outside the detection sensitivity threshold had you not been there. I don’t think this is your problem, since your events are still being detected with the vehicle label, you’re just not receiving the notifications.
They also could have changed the AI detection confidence interval to require a higher confidence interval. So, in the past the AI may have been able to post something as a detection at a lower threshold for things smaller or farther away. The problem with a low confidence interval is that you are more likely to get false positives. So in some cases if there are a lot of people submitting events or complaining about false detections, they may raise the confidence interval to reduce those faults positives. The problem with doing so is now that increases false negatives and makes it harder to detect objects that are smaller and farther away. So things that used to be detected at a certain distance may not be detected every time anymore. I don’t think this is your issue since you say that your events still show up as vehicle detected events, you’re just not getting the notifications.
There could be some new weird algorithmic change that caused some breakage like I mentioned in my previous post. Perhaps they are only sending notifications for something that is detected by both the edge ai and the cloud AI at a certain confidence interval threshold. So if one or the other has a confidence interval below the certain threshold, they may still tag it as a vehicle, but not send the notification. I would assume this is an unintentional bug.
There are probably a number of other explanations. It could also be some kind of issue related to how the app is handling notifications. You have the same plug-in version and the same firmware version as I do, but you do have a lower app version. Maybe the lower app version has something messed up related to the notification channels and it’s not specifically something to do with the floodlight Pro itself, or it’s plug-in.
As you said, there could also be something on the back end somewhere.
The thing that will make this particularly difficult to diagnose is that the notifications are kind of working for you in some cases but apparently not always. Those situations suck to troubleshoot because when someone asks you to try something, it’s hard to know if it’s just currently intermittently working or if it’s fixed. Maybe one of your factory resets resolved it?
Anyway, keep an eye on it. Wyze should be releasing a new public app update sometime within the next week and a half. They do at least one full public app update every month, and they haven’t had one in August yet, so I anticipate we should get one soon. That might rule out the app notification question.