This is bizarre. I have found that if I change the resolution on my V4 critter cam from 2.5k to HD it also changes the resolution on my Driveway V4 cam to HD. If I set the driveway V4 back to 2.5k it also changes the critter V4 back to 2.5K 
I have tested this numerous times and get the same result. I have done it on both the iOS 2.50.9 app and also with the iOS 3.1.0.6 app. Both cams have the 4.52.8.0648 firmware. Can someone else try this out and let me know the results. Maybe I should just factory reset one of the cams?
2 Likes
Iāve been noticing similar v4 resolution setting issues over the past few weeks. I canāt say one camās setting is affecting another vs independently losing setting. It appears that the change is always in the downward direction which may be a coincidence as I prefer all to be set to 2.5K.
1 Like
I just wanted to test the critter V4 in HD to see if I could upload the saved cloud videos of all the critters on this site which has been driving me crazy trying to upload the original 2.5k videos. The videos from the driveway V4 will upload here without any issues?
Maybe I will reset the critter V4.
I just changed the Critter V4 to 360 and it also changed the Driveway V4 to 360 
1 Like
ok. So Iām not crazy.
Let me do another quick testā¦
Edit: Canāt reproduce at the moment. All working fine. 
Do they happen to be in a group together? Wonder if some bug is updating the whole group. Or maybe they share an automation or something. Obviously that shouldnāt happen but curious what is actually causing that ālinkageā.
I guess I lucked out, my OGs and Panv3s had not had any major glitches until the detection zone thing a couple months ago, before that 18 or so months of working fine from day 1. But that doesnāt seem to be the case with the v4. I wonder if theyāre getting spread too thin with all the new products or if the new app development has taken resources away from firmware (or just added new bugs given it was a pretty big overhaul). Hopefully not a sign of a new trend.
I also havenāt noticed this specific issue. What I do experience is a lot of inconsistency with Wyze app/camera performance, and Iāve just more or less resigned myself to that being the way their ecosystem works. When I take the time to even notice the resolution of the Live Stream, I often see that itās reset itself in the downward direction to 360p, as @Seapup noted.
The thing I really donāt understand is why the streams for cameras in groups load so quickly while selecting an individual camera often stalls with a āLoading Live Streamā¦ā message, usually at the āStep 1 of 3: Starting up a secure connection.ā stage or the āStep 3 of 3: Loading the video feed.ā stage. Thatās frequently my experience. I can tap to open a group of three Cam v4s and have each showing a stream within a few seconds, but then tapping an individual camera in that group puts me in a terminal holding pattern.
I feel like Wyze is continuously fussing around in my their backend, and I suppose I gave tacit consent to the constant diddling when I decided to begin using their products, but I can definitely understand why a lot of users seem to express a sentiment of feeling violated. 
What Iāve noticed with the new app is it loads the cameras so frequently (favorites page when you open the app, again when you go to the cam group, again if you then turn the phone sideways, again if you tap a cam to see it individually) it seems to get confused. I often have to close and reopen the app to get it to load after a few of those happen. It seems to be less of an issue if you make sure to wait until the cams successfully load on each of those steps before trying the next step. I think it is just getting confused with all the requests especially when one is already in progress. Iām considering deleting cams off my favorites page and just leaving the group, to at least remove one of those āloadingā processes.
The favorites page is hit or miss for me anyway, my OGs show live view fine, my Panv3s show a still frame that updates every 5-10 seconds and does this weird flash back to an old image each time it loads the new one.
I see the behavior I described whether I use the v2.5x or v3x app. Iām not convinced that itās app-version dependent. Iām often closing and reopening both versions of the app when I get stuck at the āLoading Live Streamā¦ā message (the ābouncing ballsā I think some users have called it). Sometimes that helps; often it does not.
This has not been my experience with either version of the app. Whether a camera group has one or more cameras, I let the stream(s) fully load and begin playingāwhich generally takes only a few seconds, at mostābefore tapping into an individual camera, and I still frequently experience the stall.
I donāt want to hijack @Antoniusās topic with what may be an unrelated issue. Iāll just continue to speculate about backend diddling until I have evidence to support another conclusion.
I have no groups and no automations. I factory reset the critter V4, set it up again and it still does the same thing, If I change the resolution on the V4 critter cam it still changes the resolution on the Driveway V4. Maybe I will try and see if it changes other settings. 
I have some v4s in groups, some in different groups and some not in groups.
Per Wyze, all cams models always stream 360p in group view.
When you start a live stream to a specific v4, the stream starts at 360p, then changes resolution based on your preference in your profile. You can see this change up in resolution if you watch the live stream closely at stream startup, especially if you have your cam set to stream 2.5K. Cam v3 Pro works the same. Maybe there is an automatic downgrade if sufficient WiFi resources to support your preference are unavailable?
I deleted the critter V4 and added it back as a new device. Still the same so I guess it will be staying on 2.5K. Maybe the Driveway Grey and Black Critter V4 sā are twins, Evil twins.
I just wanted to do a quick experiment and as I said in one of my other post āAlways Somethingā. 
2 Likes
For whatever is worth, I experienced the same behaviour on my V3s some time ago, way before I got the V4. It only lasted for a day or so and went away. After reading this thread I tried it and I canāt reproduce the issue anymore. 
2 Likes
My v4 resolution issues may be related to using different viewing devices with a v4 camās stream resolution set to whatever, temporarily setting it to a lower resolution, forgetting to set it back to 2.5K when done viewing, then going back to primary viewing device and wondering what happened. 
1 Like
And sometimes event recording is silently disabled; not very often but it happens.
You bring a good point. Couple of years ago I raised the question and a Wyze employee chimed in but didnāt answer the question completely. Gave me (us) a lame answer. I am to lasy to search for the thread, but my original question at the time was:
Whenever I would set the resolution to HD on my phone and to SD on my iPad what was the actual resolution that was being recorded to the uSD card?
The answer I got was that what ever device I used last to change the resolution thatās what would be recorded on the uSD card. From what I gathered at that time was that the live view resolution is device depended. On the other hand the uSD recording resolution is what the last device has set it up to a minimum of SD. Apparently you canāt record to 380 Dpi on uSD card, but you can view it in live view.
I hope I make sense.
Donāt even get me started on that one!
1 Like
And that is why I wanted to change the V4 to HD for a test with a smaller sized file.
2 Likes
Atta boy
3 Likes
Must be a combination of factors. For me the favorites page never seems to work right, the cam group was working ok until 3.1.0 now it has issues, but the individual cam live view almost always comes right up, unless Iāve gone through several of the other screens before getting to it (hence my theory that it is getting confused).