Wyze Cam v3 Pro Beta:
Version: 4.58.14.4178
What’s New:
- Fixed a bug that caused event frame loss
- Fixed a bug that caused microSD card playback to not function
I just experienced an unexplained anomaly.
I have 2 devices that have the Wyze app. A Samsung S24 Ultra, about 6 months old, and a Samsung A9+ tablet, about 2 months old.
I do not allow automatic updates on either device. I also do not allow auto on Google Play or android itself. I want total say for updates.
When I added the tablet it meant I had to do 2 operations for every update. This was for Wyze and all my other apps. A bit of a pain in the a… but my choice. I’m guessing in the past 2 months I’ve had a dozen or so updates and everything worked as expected. I would see your post in the forum. I would go to each device, click on Device Info, and be challenged that there was an update. I would acknowledge the update and when completed go to the other device and repeat the process.
During today’s update the anomaly appeared. I first updated the A9+ tablet. All was normal as described above. I then started the process on the S24 Ultra. When I clicked on Device Info I did not get a notice that an update was available. I looked at the firmware release and it was already at 4178, today’s release. Just then I got a pop up about a file being copied. It happened so fast I could not read all of it–then it disappeared. Thinking I may have fat fingered the auto update function when clicking on the Firmware Release I checked. Auto update was off.
Bottom line–somehow my S24 Ultra was updated–and I didn’t do it.
I have a sneaky suspicion that Samsung may have done it. The tablet and phone share a lot of info. For instance the tablet can text and make calls even though it does not have a simm card. I wonder if for some reason a config file was synced between the devices.
The other possibility I can imagine is 4178 was in beta with the same designation and I had previously updated the phone but not the tablet.
Everything appears normal on both devices. Maybe something to remember if the complaint is "my device is auto updating even when the setting is off.
Another minor issue with 4178. I needed to check Device Info on my v3pro this morning and discovered that the Network field was blank.
Everything seems to be working. I cleared caches, restarted tablet, restarted router–didn’t help. It’s a minor issue.
P. S. Spot checked my PS v3’s, v4’s, BCP’s. Did not have this issue.
Hmmm, I am on Android, pixel 7 Pro, and my v3pros on the same firmware as you are showing the ip address…
That’s bizarre. I have 2 AP’s and this AM I decided to switch AP’s. I reset the v3pro and reconfigured it. All seemed normal until I looked at Device Info.
I wonder if this is a case of a glitch during configuration. Later on today I’m going to factory reset and see what happens.
Thanks for checking.
Edit: for the record. Samsung S24 Ultra, Samsung A9+, both android 15.
Had some free time this morning and decided to factory reset the v3pro. Before I proceeded I checked Device Info.
Self healing feature must have kicked in. The IP and Network are filled in.
Problem solved👍
I just noticed that my Alexa routines with person detection no longer work on V3 pros. I think it’s related to this firmware.
I confirmed that it’s not an issue with all Wyze cameras in Alexa. Person detection triggered routines still work for several other Wyze camera models (definitely working for FLPro and DBD, And probably most other models), but Alexa routines are not working with any of my V3 pros that use person detection as the trigger. I suspect it was this firmware that broke that.
Can anybody else with a V3 Pro and Cam Plus and Alexa, try to confirm this. Creating a routine in Alexa where the trigger is person detected and then anything for the action? Maybe just temporarily have it send you a notification that a person was detected just so that you can see if it works.
All of my active V3 pros have this beta test firmware on them, so I can’t 100% confirm that this firmware is the problem. But it would be nice if some people with this firmware can confirm that Alexa person detection triggers no longer work, and if anybody has any V3 pros that do not have this beta firmware on them, it would be nice if you could test the same thing to see if Alexa still works with the other firmware or not on V3 pros.
Thanks to anybody who’s able to help test this out. If we can get anybody confirming the same issue and that it’s not an isolated incident with just me, than I think we will call tag. Jason and let them know about this issue.
I can confirm what you are seeing.
I have a v3pro watching the front yard. The routine with Alexa is simple. If the camera detects a person announce “A person is in the front yard”. I just tried it and:
Alexa was quiet
I received a Wyze notification that “Ron was detected in the front yard”.
I received a Descriptive Alert that Ron was in the front yard and what I was wearing.
I double checked the Alexa routine and clicked on the “try it” arrow and Alexa announced as expected.
I checked the v2 doorbell 2 feet below the v3pro. It did exactly as expected. I received a Wyze notification and Alexa made the expected announcement.
I checked the Alexa routine history. The doorbell was there, the v3pro was not.
So it was either Wyze did not send or Alexa did not receive and since we just updated Wyze I agree with you. Probably Wyze.
1 Like
Thanks Buddy.
@WyzeJasonJ @WyzeAndy we have confirmed an issue is not an isolated incident.
V3Pros are suddenly not working in Alexa routine triggers with a person detection trigger even though cloud events are correctly identifying a person (just not passing that on through to Alexa).
We suspect this firmware broke the integration for V3Pros because other cameras are still working with Alexa routine triggers. Can you pass this along to someone to investigate and fix, please?
I suspect that sending you a Wyze log won’t do anything since it is correctly detecting a person through the Wyze app, it’s just not sending that information through the Alexa integration for some reason. But if you guys do need some kind of a log, let us know what log to send.
I don’t do Alexa, nor have any V3 models, and don’t want to make matters worse either, but thought I’d ask if anyone unlinked Alexa and re-added it?
I’ve seen similar issues with Alexa and Google Assistant and Home on some cameras.
It could also just be the update.
Good point. In the past I would have done the relink without caution but I got burned a couple of months ago with a similar problem with Yolink. Everything worked as expected except Alexa. I unlinked and relinked and it would not relink. It was unlinkable for 4 days until Yolink and Amazon sorted it out.
This was the first time this had happened to me since the earliest days of linking.
As you go down the troubleshooting tree I would ask self at this point–what are the implications if it does not link?
1 Like
Also a good point. I did express use caution. 
Slippery slopes.
1 Like
I’m too dependent on Alexa to risk unlinking and relinking.
However, I will say that last night when I was trying to create new automation with a V3 Pro, I noticed that person detection trigger was grayed out and I couldn’t use it or select it at all. So then I went into my Wyze app and went into the camera settings and clicked reset services and then I restarted the camera, then I closed and reopened the Alexa app and suddenly it was fixed and not grayed out anymore. - Note that I have seen this happen many times in the past with myself and other people on various camera models, and clicking on reset services and restarting the camera has almost always fixed it in the past so I just assumed that’s what was going on here. And it did indeed remove person detection from being grayed out and allow me to select it.
In addition, not only could I now select person detection as a trigger, but I could now also select package detection as a trigger which was weird for a V3 Pro Camera. I thought that was only enabled for video doorbells. Regardless, I set up the person detection trigger and couldn’t get it to work.
That is when I started checking the same thing with my other V3 Pro cameras and found that person detection triggers weren’t working for any of them, but Alexa PD triggers were still working for other Wyze camera models with Alexa Routines. So I knew it wasn’t an isolated incident with just one camera acting weird, since multiple devices of the same model were doing it too, and the integration was working with the rest of my Wyze routines and devices, just not for the V3 pros.
And now another user has confirmed the same thing, so I’m pretty certain there has to be something on Wyze’s end going on here. However, if they want me to do more thorough checks I can. I think I also have a V3 Pro sitting in a box somewhere with older firmware that I might be able to set up and check. I’ll have to go look for it.
But considering everything else with the Wyze Alexa skill is working properly, I hesitate to unlink from it and potentially lose some of the routines and stuff that I have set up for all my other devices. I am trying to move most of my routines off of Alexa and into home assistant, but there are some that I need to leave directly in the Alexa app because it is my link between some Wyze AI detections and a home assistant helper entity.
For example, to get some Wyze person detections into home assistant (without using notifications), I set up a home assistant button helper entity and then I exposed that entity to Alexa, and then I just set up an Alexa routine that whenever that camera has a person detection triggered, it presses the home assistant button helper, and now home assistant knows that a person detection was triggered from my wyze camera. Now, I can set up routines in home assistant to do things like automated lighting for a room where the lights automatically turn on anytime a person is detected, and automatically turn off when there has been no person detection button press for something like 10 minutes or more. Easy way to automate lighting without pet interference (automated lighting with other kinds of sensors can be messed up by pets). Or in some cases I still might make a person choose to manually turn on a light, but still have it automatically turn off the light if nobody’s been in that room for a certain amount of time.
I’m kind of afraid that if I unlink the Wyze skill from Alexa that I might lose a bunch of those routines that I spent time setting up and have to redo them. Therefore, I will only attempt that as a last resort where I’m getting really desperate. Hence why I’m first asking if others can confirm having the same issue. Since others report having the same issue I feel like Wyze should be able to replicate it fairly easily and between their back end access and their contacts at Alexa, they should be able to figure out and resolve it without me risking creating lots of extra work redoing things. 
1 Like