No longer getting Vehicle notifications on Wyze Android app

Hello all,

In the last couple days, I’ve stopped receiving vehicle notifications through the Wyze app for both my floodlight and doorbell cameras. I only receive person notifications on both. I used to receive several a day and then stopped (I figured this was Android maxing out on daily push notifications), but now nothing.

I have toggled on and off the notifications on both cameras, cleared the cache and data on the app and even deleted and reinstalled the app. I’ve restarted my phone a few times. It seemed to rectify it briefly but now back to nothing.

It IS recording events, though, but what’s odd is that the AI is recording ALL events at vehicle on the floodlight camera. I have a Google Pixel Pro 9 XL. I do wonder if the phone itself may be causing this issue, but maybe someone has gone through this before here. Any help is certainly appreciated.

Thank you in advance

Can anyone help maybe? Anyone else seen this before?

I tried support but they think it’s a hardware issue after factory resetting the camera. I can check off other motions and get notified that way, but not sure.

The events summary shows ALL events at vehicles so maybe that could be the issue and notifications are not coming through as a result?

I’m having difficulty understanding what you mean by this. How could you explain your experience in a different way?

My one immediate thought is trying  Settings ➜ Reset Services and then confirming that the Notifications selections are set for what you want (I think resetting devices and the services link might sometimes change these), and I might even try toggling Vehicle notifications off and then back on if they’re already set the way you expect.

Some of that is stuff that you may have already done, but I haven’t seen all of that explicitly described in your posts so far.

I haven’t personally seen this particular issue (at least as I currently understand it), but I think contacting Support is a good step, and I probably would’ve also submitted a log and included that with whatever I was communicating to Support. I’m also curious about why you thought this might be an issue with your specific phone. That’s probably not a thought I would’ve had, but I don’t know exactly what you’re experiencing and, like I said, I’m trying to better understand the problem.

Up until a couple weeks ago, I was getting all push notifications from my floodlight camera. Then I stopped getting vehicle notifications all of a sudden. At first I thought it might have been my Android maxing out the push notifications (my detection zone includes my street and it’s not a major road but a road travelled frequently, so I’d get maybe 100 vehicle notifications or so a day, and sometimes they’d stop at night and start again the next morning), which is why I gave my phone info and suggested that. However, this time, I’m getting no vehicle notifications.

I get ALL other notifications without issue. Nothing else gets missed.

I reset the camera a few times, toggled the notifications on and off (first vehicle and then all of them), reset the services, cleared the cache and data a couple times, and even deleted and reinstalled the app. Nothing resolved the issue.

The events are coming up as the motion detection comes in, and they’re ALL coming in as vehicles, regardless. The screenshot below is an example I sent to support.

I spoke to support today and we tried factory resetting the camera. It didn’t do anything to resolve. I did notice during our chat today that I can get notified if I check off the Other Motion option, but I don’t want that obviously.

They had thought it was a hardware issue, but there’s nothing physically wrong with the camera and everything else works on it, so I’m not convinced it’s the hardware.

I am using the Floodlight Cam Pro. The firmware version is 2.2.1.1223. I updated the app recently to 3.6.6.683, but this started before I updated the app.

Also, I have a doorbell cam v2 and there are no issues with any notifications there from what I’ve seen

Hope this helps explain it better

Just a suggestion and I don’t mean to stomp on @crease but & “if” your doorbell and floodlight look at the same areas.

Try turning off vehicle on the flood or one of them and make it just person.

There’s two vehicles in vehicles in the driveway, if im not mistaken, almost any motion will cause the smart detection to see vehicle.

So if both look at the same areas and no problem with the doorbell, set the flood for person , toggle off vehicle.

Test it then, walk out under the flood.

What matters to me most, maybe you’ve a different opinion, is person in my driveway or the road would be pinging my V4 all day long.

If that don’t work, then I’m wrong and there’s a potential firmware bug.

They don’t unfortunately. The doorbell cam looks at the walkway from the driveway where the car on the right.

When I first used the floodlight, I had thought our cars might set it off regardless, but the vehicle notification seems to only would go off if a car passed by the driveway or if one of us starts to move our own cars. I think occasionally a reflection of a car by our car windows during the day or a high beam down the street shining into the cars would set it off, but I had sent feedback to the AI reflecting a lighting change in those instances

Thanks for fleshing out the description of your experience more. I figured you had probably tried Reset Services, and it’s good to have that confirmed. :+1:

I’m really puzzled that all of your other notifications continue but the Vehicle notifications for this one camera have stopped. I don’t have a good explanation for that at all.

When you factory reset the camera, did you set it up with the same name as before? I wonder if something is glitched and “stuck” for some reason and if setting it up with a different device name would have any effect. (Probably not, but I’m really just grasping for whatever here.)

This puzzles me, too:

There seems to be a contradiction there, but your more recent statement indicates that the doorbell notifications maybe were an issue but are no longer? If that’s the case, then what do you suppose fixed that?

I’ve never seen anything like that documented and am unaware of any such limit.

The one person I can think of with extensive Cam Floodlight Pro experience is @carverofchoice, so maybe he has some ideas, because I’m baffled. :confused:

Stomp away. I’m stumped.

Disclaimer: I read the first post and only skimmed through a few others, so forgive me if I say anything ignorant here.

I have had vehicle notifications turned off on all of my floodlight pros, so I can’t currently confirm or deny whether this is happening to me. I’m going to go ahead and turn vehicle notifications back on for 1 to 3 of my floodlight pros And see if I can replicate the issue first. If I also can’t get vehicle notifications anymore, we will know it’s not an isolated or edge case issue. If I am able to get vehicle notifications, then we’ll go from there. And then I may read this thread a little more thoroughly once I have that foundation ready on my end.

A few quick caveats on this model device that are a little bit different from the other ones, the floodlight Pro supports full local AI detections for free without cloud use or hybrid local and cloud.

@D-Ray [sorry if you already answered this question above], are you using cam Plus or just the free AI? Detections for this camera model?

Another interesting thing that happens more often with this camera model, is sometimes after a firmware update, if the local edge AI model does not get fully loaded correctly, sometimes you need to do a full factory reset on the flood light by holding the reset button down for something like 10 to 30 seconds until it forces it to restart, then you let go of the reset button, and once it comes back up you go through setup again, and that often fixes the local edge AI issues that sometimes happen from a firmware update. You could always try that while you are waiting for me to test us on my end if this is happening. Because if it’s not happening to me, the next thing I will be doing is suggesting you do the above troubleshooting to factory reset and set it up again. I have had to do that with my garage floodlight Pro at least three times. I have had to do it with my front floodlight pros at least once each. It’s always resolved my issues when nothing else would when there are AI detection issues on this model.

Another thing, this camera will detect parked cars has a vehicle detected event, but it will not send a notification for a parked car unless there is another AI object in view at the time (pet, person, etc). But, it should still detect moving vehicles and send a notification for moving vehicles even if there is no other AI object in view. I haven’t thoroughly tested that since I don’t use vehicle notification, but it’s possible that they changed their detection rules to not notify on a moving vehicles anymore either, unless there is another AI object in view. If that’s the case, this should be an error that they need to correct and be informed of. Let’s start with seeing if I can replicate the issue.

This is my favorite model camera, and I own seven of them.

I didn’t know it was seven, but I knew that you had multiple devices and that this is your favorite camera. Thanks for responding! :+1:

Thanks for offering to test, too! :+1::+1:

I was guessing, I turned on vehicle on my driveway V4 just to see and blocked the road. Didn’t matter, vehicles like crazy this morning.

Turned that back off quick this morning. And I’ll leave the floodlights to people like @carverofchoice that have them. I was guessing based on standard cameras like V4s.

I didn’t realize they have local Ai.

I kept it the same name. I didn’t delete it from the device first and it came back to everything that was there before. I wonder if that could be an issue too and that’s what I might need to do?

I may have possibly jumped the gun on the doorbell cam. I have gotten vehicle notifications here recently and one was passing my driveway, but another was the camera thinking a 40 foot high waving tree was a car.

Neither did I but for a while after a significant amount of vehicle notifications came through in one day, they would stop but start back up the next morning and I had a similar issue with Gmail app one time so I figured that was the casd

No worries here! I have Cam Plus on both cameras.

I did do a factory reset with support, but like I mentioned to @Crease, I didn’t delete the device beforehand or change the name. I could try it again and see what happens too

This above seems to make sense from what I’ve read in other people’s posts about this in searching for my issue. Before, with one or both cars in the driveway, it WOULD detect moving cars, AND send a notification, but now, it just detects the event as a vehicle but NO notification. It is possible this is the answer maybe but I wonder if others are indeed having the same issue

@carverofchoice I appreciate your assistance and I’ll see what you say here. I may try to reset it again in the next couple days too and see what happens.

Thank you all!

I’m fairly certain some if not all phones limit the notifications.

Samsung at least, confirmed it to me in their Beta forum and I think another Pixal user noticed similar.

See this recent thread. Events and notifications are slow

This was the reply I got from Samsung.

Hello,

Thank you for the detailed suggestion and for sharing your experience regarding the MAX_PACKAGE_NOTIFICATIONS behavior.

You’re absolutely right—some notifications, especially from apps like security cameras, can be critical, and it’s understandable how hitting the notification limit could become a problem in those scenarios. While this limit is designed to prevent UI overload and preserve system stability, we agree that flexibility for user-prioritized apps would be ideal.

Your idea of adding user-controlled toggles (defaulted OFF for safety) to allow unlimited notifications for selected apps is a smart and practical suggestion. We’ve shared this feedback with the relevant team for review and future consideration.

We truly appreciate your attention to detail and commitment to improving the One UI experience.

Regards,

One UI Beta Team

I have a Google Pixel Pro XL 9 and they have a notification cool down tool which I shut off. They also note that some notifications may get delayed as they learn how you use your phone. I had thought that the phone was doing it, but other notifications came through, so who knows there

It might be worth a try, but I really don’t know if it’ll make a difference or not. Like I’ve said, I’m really at a loss with this one.

Deleting or changing the name aren’t necessary to to fully reprovision the FLPro. I’ve never deleted or renamed mine. No worries.

Well, I can confirm that moving vehicle notifications are working for me even when no other AI objects are in view (I watched the entire event to make sure there wasn’t a person or pet detected in view):

I am running app version:
3.7.0(b690). (Android version of the beta app)
Plug-in version: 3.6.0.3 (You can find this in the settings and device info page)
Firmware:
2.2.1.1223 (you can find this in the settings and then device info page)

I do know that there are reports of a floodlight Pro issue for some iOS users with a lower plug-in version than what I listed above. If your plug-in version or your firmware are lower than either of the above numbers, then we might be able to fix it by getting you onto a matching firmware or plug-in version.

Are you running iOS by chance?

I am running Android 16. The firmware version is 2.2.1.1223. I updated the app recently to 3.6.6.683, but this started before I updated the app. The plug-in version is also 3.6.0.3.

It’s funny that yours are coming in fine. Between noon and 1:30 today eastern time. I did receive two vehicle notifications coming from the floodlight cam. I looked and they were vehicles driving by. We were out so there’s only one car in the driveway. I didn’t think to screenshot it and post it, my bad.

Could it possibly be a server issue on wyze’s end?

Well, that’s good to hear that some vehicle notifications came in for you. :+1:

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.

I like reading this kind of detailed analysis and walking through a problem. Thanks again for chiming in here! :+1:

All these are very good possibilities and potentially could be a combination of everything as well.

Funny enough, if I check off OTHER MOTION, then it comes through as a notification but as a COMPLETE MOTION EVENT one.

You make a solid point about the app too. You have a beta version and I have the older final version, so maybe the new app update could fix this potentially.

Regardless, any of those make sense, and hopefully it gets rectified soon

I plan to factory reset it again this weekend and see what happens. I’ll let you know what happens as we go.

Thank you @carverofchoice @G2740 and @Crease for all your help here