Hmm that could be it. I still have my OGs that I replaced with V4s. Going to test later and see if they work. Maybe its an issue with the V4s.
What did you learn from this? I tested a few minutes ago by creating an Alexa routine for a Cam OG, and it actually played the voice announcement from a nearby Echo Dot when I moved around in front of the Cam to create a person detection event.
I also want to apologize to @Sam_Bam for my earlier comment. I think the question is valid, though Iâm having difficulty making the connection in my brain about how itâs related to the subject of triggering routines, and thatâs the point I wanted to make, though I feel I did so rather tersely because I was replying on my phone (I donât like typing on my phone) and I wanted to go ahead and answer a question that was directed at me. I didnât at all intend to give the impression that I thought it was a completely irrelevant question, and Iâm afraid I may have inadvertently done that. I was merely trying to assess the relevance to the subject at hand and to keep the topic from straying, and I feel that I may have communicated that poorly.
Edit @ 2026-06-07T03:40:25Z
I neglected to mention earlier that when I tried to view Routines â Activity (history) before, the Alexa app was telling me that this information was unavailable, so I thought there was some kind of glitch that might be related to this whole routine behavior issue, but now that Iâve triggered person detection on the Cam OG again, I see that itâs recorded in Activity (and I still hear the announcement from the Echo when I move in front of the Cam OG). ![]()
Just tested with an OG that I re-setup and the routine works as expected. So this seems to be narrowed down to a V4 issue if WildBillâs V3 works and the OGs work. As you can see here like I said earlier the og test i just did has the When âtest cam detects a personâ as opposed to the V4 that says when âBack view: Person Detectedâ which i think is the issue.
Does anyone have V4âs that they can also test with just to 100% confirm?
I thought thatâs what I already reported above.
Your issue sounded different since it wouldnt let you enable the person detection for your camera under camera event settings in the Alexa app I thought? Either way mine does and it doesnt work so seems like something with the V4âs.
No, I believe that Iâm setting up the same kinds of Alexa routines you are (only I havenât added a time constraint or schedule), and see that they fail when I do this with a Cam v4, but if I set up the same kind of routine with a Cam OG, then that triggers the Echo announcement as intended.
I have a new bulb cam (for a porch light fixture) and a battery cam pro. Routines stopped working for these cams some time ago - Iâm not sure when - same kind of issues. Iâve reset the skill, deleted and recreated the routines. The only options I have when selecting the smart home and the camera are the two shown above-person and package detection. I found no way to create a routine with a When saying X cam detects a person. Are we able to open support tickets for this or is Wyze ignoring the issue?
Sounds like the same issue. Something with the newer cameras and routines definitley seems to be messed up. I hope Wyze fixes this as these routines are one of the main reasons I keep buying them all these years.
I posted about this a while back, and then found a way to fix itâŚbut it looks like the Alexa app has updated once again, and the routines are now broken.
My routines were simple: when person is detected from 8pm-8am, announce person detected on several Alexas.
The workaround was to enable person detection in the Alexa app, but turn Person Announcements OFF.
When person announcements is ON, it will make the announcement every single time a person is detected. Turning it OFF now, and the routines still wonât trigger.
I have no idea what they changed, but I cannot get these routines to work at all anymoreâŚwhich is unfortunate because we donât want the Alexaâs going off every time the kids are outside, the mail comes, the groceries come, etc. Ideally, we only wanted them to go off between 8pm-8am, and this routine was working flawlessly for almost 3 yearsâŚuntil Alexa plus rolled out and they redesigned the app.
Edit: just to add, when looking at the routine history, itâs completely empty. These routines have not been working again for months now. v4âs with cam plus
Something is broken somewhere. Person detection does work, but it will not work with a specific time based routine. I believe this has more to do with the Alexa side than WyzeâŚbut who knows
When youâre setting up the routine, itâs important to note that you have to turn person announcements OFF (see screenshot)âŚotherwise youâll get person detection notifications from the Alexa all day and night. And you may think that the routine is actually working because of this, when itâs actually not.
the time based routines are not working at all anymore on their own with the v4. This just started happening again a few months ago
It looks like this is only with the V4s for some reason. I just tested with my V3, and the time based routine is working as intended with V3.
The v4 has a completely different set of options in the Alexa app as well.
Right. Thatâs why I left Person Detection Announcements toggled off in the Cam v4âs Alexa settings and left Person Detection Notifications toggled off in the Cam OGâs Alexa settings when I tested creating identical routines for both cameras. (I donât know why Cam v4 has âAnnouncementsâ and Cam OG has âNotificationsâ.)
I agree that things have changed with Alexa, though I donât know what, and Iâm not sure why this would be affecting Cam v4 but not Cam OG. ![]()
Hi. Something in this thread, specifically from Coley is confusing me. In the alexa camera settings, I see a parameter called âPerson Detection Announcements.â But I donât see a separate parm called âPerson Detection Notifications.â Itâs not in the screenshot posted. Is the screen and parms different for different types of cameras? My two are a battery cam pro and a bulb cam. Alexa detection announcements work but routines donât.
Note: This is what the wyze AI says about this. It wonât let me open a ticket.
Weâre aware of a current issue affecting all Alexa skills, including routines triggered by Wyze Cam person detection. Alexa engineers are actively investigating the root cause and working to resolve it, as this is impacting users globally. While there isnât an estimated resolution time yet, it is a top priority for the Alexa team.
Thats actually promising though. As much as I know that probably means nothing in terms of it being resolved, maybe its on their radar.
It looks like this is only affecting the V4âs as far as I can tell. Apparently a lot of the cameras have very different settings in the Alexa app. This is what I see with a V4. Previously for the routine to work, you would have to turn person detection OFF (otherwise it goes off anytime a person is detected) and turn announcements ON. This combination allowed the time based routine to continue to work. It would only announce during the hours you set. These settings were new about 5-6 months ago. They initially broke the routine, but it was quickly fixed. Now itâs broken again
Edit: this is what the V3 settings looks like. Turning person detection OFF and then creating a time based routine seems to still work for the V3
Ugh, I reported this issue on V3Pros back in August 2025:
Iâm disheartened that this issue has not only not been addressed/fixed but is now spreading to other camera models too! I was just about to start replacing a bunch of V3Pros with V4s so I could start using the Alexa Person detection triggers again when @Crease just informed me of this thread that the issue has now spread to infect other camera models now and I might be wasting my time trying to replace my V3Pros with V4s.
This is exactly the reason we need something like Fix-it-Friday again. Without it, there is no accountability for progress on issues the community decides are important and they just get ignored forever. Ugh, I really wanted a 2K cam that could use Alexa person detection triggers, but neither the V3Pro nor V4 are options anymore. Very annoying that this has been happening for nearly 11 months now since I first reported it.
YouâreâŚwelcome? ![]()
(Iâll crawl back into my
now.)
Iâd like to see that, too. ![]()
I think we as volunteers see a lot and try to recognize patterns and bring them to the community managerâs attention (at least thatâs a lot of what I try to do), but I donât even attempt to read everything, so itâd be good to actively solicit community input on high-priority issues again. I liked the progress updates that used to come with those topics, too.
I used toâŚI know Jason did when he was a mod. But itâs overwhelming to try now. I gave up trying. Now I watch the first post of select categories and tags (which is actually a lot of them), threads Iâve commented in, spent a lot of time in, and when Iâm tagged (minus the very few users I have muted/ignored). Then I read other random new threads sometimes. I definitely miss a lot. I have at least 5000 unread threads and Iâm consistently in the top active users⌠Itâs just too much to read everything. I need some balance in my life. So Iâm okay with following specific tags and having people call me to anything relevant I may miss. ![]()
My point is, I agree with you. Even you and I who read a lot, arenât able to read everything. It would be great if there was a way to do some survey or something similar to fix it Friday where the wisdom of the crowd could inform Wyze what their users think should be a priority to address. But maybe they donât WANT to know. Thatâs probably why they cancelled it in the first place.



