I reported this in the beta thread, but I don’t think they’ve resolved this with Alexa yet. The problem may be caused by this updated V3Pro firmware. So if you use V3 Pros triggers with any Alexa routines, be aware that this firmware might break that.
I mean, it was tested, and I reported it, and another user confirmed it. I guess they just decided that the stuff it fixed now was more important than the stuff it broke?
Little confused here. I see that this firmware update shows up for the V3 Pro on release notes page, but is not available to me, which judging by the few posts in here, that is a good thing.
My question is, did they pull this firmware release?
If so, shouldn’t it be noted as it has in previous times under release notes page.
If not, then why does it not show as an option in the app?
Just curious what happened here with this release, and thus my confusion.
I haven’t seen any mention of that, and I won’t claim to speak for Wyze, but I’ll note that in the past (even in the Release Notes & Firmware history for Cam v3 Pro) they’ve often done slow or phased roll-outs of firmware and app releases, but they don’t always make this explicit, and I imagine that’s what’s happening here. I believe that’s been the case with some recent firmware updates for other products, as well. I don’t know what the typical practice is, but I have a vague recollection of reading that in some cases it can take a couple of weeks before an update is made available for all users.
I understand the confusion, and I’m definitely in favor of more transparency. I’d also tend to agree that maybe it’s a good thing you haven’t yet received this one. (I don’t have any Cam v3 Pros, so I haven’t experienced any of the issues described.)
My V3 Pro has garage duty now, I put another V4 where the Pro was.
I originally set up the V3 Pro November 11, 2022 but lately it was having issues with the recordings, they would start, skip for a second then continue. Scatter shot video or the first second or so.
Gwendolyn once told us that For app releases they always this hold back some people from receiving it just so that they have the option to stop the release. I imagine they do the same thing for all firmware updates too.
Often longer. I’m sure it can vary, but I know that in a few cases they will split it up into segments of 1 or 2 weeks at a time and sometimes not have it fully pushed out for over 4 weeks. It partially depends on the estimated impact. If they know that X percent of people will have a camera that requires specific troubleshooting like a factory reset or maybe even just a regular restart, they may anticipate that that they will get X number of people calling support. So in that case they purposely stage the release so that support isn’t overwhelmed and backed up all at once, and they can more easily. Just tell people to restart the camera or whatever else without having long hold times etc.
I’m not saying that’s what’s going on here, but it could be why there is a slow rollout.
Also, some firmware updates are linked to only be available to certain app versions. So it’s also possible that somebody with an older app version may not see a new firmware update.
Yeah, I recall reading that on the Discord server. I’ve gotten the sense that this has become their standard operating procedure with firmware even when they’re not explicitly saying so in the release announcement. Those of us who watch and wait after a release just tend to shrug off the delays, I think.
Oh, yeah, for sure, like with the v3 app last year:
Yeah, I’d call it educated speculation based on past experience and previously released information. Works for me.
That’s a good point to keep in mind, as well. Thanks for the reminder.
the update is still showing the moving gears after over one hour. What’s up with this. I have one outdoor camera. Why the issue. I can’t leave it run like that continuously and I can’t access camera while it “updating”.
I’ve also had experiences where the firmware update screen with the moving gears timed out after 10 minutes with no indication that the update had ever finished or with a failure message, but if I close and reopen the app and navigate back to Device Info I see that the firmware is current and the update apparently succeeded.