That is how it’s supposed to work. Autoplay is applicable to the Favorites page, not the underlying pages. Battery-powered cams like Battery Cam Pro and Wyze Cam Outdoor are exceptions to this design.
NEW BUG INTRODUCED
So this 3.2 version re-introduced a bug in the v3 Pan. (it cropped up in early 3.0 betas, but was fixed in the final release of 3.0)
All notifications work normally, including detection. Phone instantly receives notifications. If click on them in-app, or opened via phone notification, those events can be viewed instantly. SD card recording works normally.
BUT BUT BUT… LIVE VIEW is completely unavailable except immediately after a restart of the cam. (which is possible through the cam’s settings–which proves the cam is not completely hung). App restart, router restart, nothing brings it back except the complete restart of the cam. True no matter the device used for attempted viewing. Occasionally it will come back after app close, but usually it goes away when you leave the app and try to come back to view it after that.
My v3 cams are rock solid with this release and live view pops up almost immediately. New listed features work as intended. Don’t make new bugs.
Your scenario works fine on my phones and tablets running 3.2.0.b576 for CPv3. You should submit a log file and post the Log ID or your issue may get overlooked.
I’m a bit confused.
Is the question that if you App Settings > Condensed View it does not allow Autoplay.
If Auto play was allowed then I think we would be back to opening up the app and a bunch of cams would start Auto playing.
Personally I love the way b574 and b576 display Favorites. The app opens within a second. Then I have a choice–do I want to see what a singular camera is doing (fast response 1-3s).
Or do I want to see the cameras sequence through my property by opening my Cams group (acceptable response, 1st 3 cameras 3-5s).
Either way my opinion is this is the way Favorites should have worked 3 months ago.
I don’t have a question. Just stating that:
- Condensed view does not support Autoplay on the Favorites page nor does Autoplay apply to underlying pages
- Tapping a group in Favorites results in Autoplay of the visible cams in the group, as always has been
- Tapping a single cam in Favorites also starts Autoplay for a single selected cam, as always has been
My three CPV3s tried to make me think this, but my weird bug of switching from my primary SSID to my guest SSID or visa versa fixed it. Happens with OGs and apparently CPV3, so far.
Still watching V4s for similar.
That is indicative of local network issues.
Thanks for the clarification. I agree.
I also don’t mind if Wyze decides to apply the Autoplay option to Condensed view. My preference is: I won’t be using it. Little thumbnail-sized streams are not for me. But I’ll test it.
I take it back it Cpv3s stick on 1 in live view regardless of SSID. Opened once though.
May be network related, I have zwave, zigbee etc all over the place
Takes event vids and notifications no problem, live view is the issue. Will observe before submitting.
It cleared up immediately when 3.0 released, and returned immediately when 3.2 beta hit. Seems too coincidental to be my network.
It’s almost like it is sending a query to the cam and it sends the wrong response so it gives up. Mine only gets the bouncing dots. It does not get to the 1 of 3…. screens.
Cam has a clear line of site to the modem through one window. I have others going fine through 6 walls. 
WiFi travels through multiple layers of drywall easier and cleaner than one typical glass window.
I’m down to 1 of 3.
Two are like greased lighting, 1 is now stopping on the bouncing balls, #1 or #2. I did, try restart of cam in app, power down and restart and reboot phone. S23 Ultra.
That one cpv3 is still sticky. Shows no signal in the Wyze app. Retarted in the wyze app again and now its fine. So all 3 of mine are back 
for now.
Probably accurate, but It shows strong signal and I’ve verified this with both other cams and an app on my phone.
Strong does not equal clean and most apps don’t measure cleanliness.
b576. Still Very strange. 4 cams in favorites. 2 v4s almost always open quickly. But with OGs there is odd operation.
One regular OG opened right away, it sits on top of the OG-T stacked. The T had bouncing balls for 20 seconds in favorites view. Finally opened in favs.
Switch from primary to guest. Instantaneous opens any view, devices etc.
I can switch back and its also just fine. For s while.
I’m aware of the relationship to possible network issues. But, app 2 didn’t do it that I recall.
I’m no WiFi guru, but not a complete idiot either.
I clean cache daily, I reboot phone daily, occasionally restart modem and wifi.
Testing tools, Net Analyzer, Orbi app, Samsung phone wifi statistics etc.
I’m seeing no new WiFi or LAN/ISP anomalies, yet…
I never do this. Should not have to if your network is healthy.
I will repeat this until I’m blue in the face. “Mesh Wifi - WiFi 6 compatible”. THIS WILL SOLVE SO MUCH.
Your post piqued my interest.
b574 was the first time we saw the revised Favorites with the condensed view and autostreaming off. I can’t remember how many days we were on this release but I was happy. My 10 cameras in a group autoplayed reliably. The 10 cameras, non-grouped opened fast.
A few days ago I upgraded to b576. As this was a release candidate I expected equal or better performance than b574.
I was disappointed. It seemed that everything in Favorites had slowed down. As I started to trouble shoot, one camera, an older cam v3 started having trouble connecting. Sometimes I would get the bouncing balls followed by an error code (don’t remember).
This made me nervous so I decided to unplug the cam V3. My favorites then started working reliably as they had in b574.
I thought this was an odd coincidence - - upgrade and now a flakey camera. The cam is the oldest cam I have and has been relegated to roving duty. I figured it was end of life.
Then I read your post.
I’m not sure our observations point to the same issue but I reinstalled the cam V3 to see if I can recreate what I saw earlier.
As for a possible network issue—in days gone by we would never put wifi devices within a few feet of each other. They would interfere with each other.
Current chipsets do not seem to have this problem as the OG stack doesn’t seem to care and I have smart plugs with 2 plugs in one outlet–no problems.
You said you did not see this issue on app 2x. By chance did you see this on 3.2.0 b574?
Just to rule it out have you tried separating the stack, moving them apart, see if you see a difference.
Meanwhile I’m going to watch my cam V3 like a hawk to see if I can recreate what I saw earlier.
No, I dont recall on b574 or previous. I’m up to my ears testing the app & firmware in these and other brand cameras and WiFi configurations.
Mesh router south end middle, points x2 middle and north. Wifi everywhere inside and outside almost 2 acres. Drops at about 60+ yards. All brick rancher.
6 or 8 OGs in window mounts inside. Dbm as low as -30s inside. -50 to -60 walking all brick perimeter outside.
Cpv3 in garage, two in basement. V4s on outer edge of the deck, OG stack right edge of deck.
I do know its been stacked for quite some time, Many months. Pre 3. I don’t recall ever in the past, pre-3, having this issue. Of course I don’t keep notes. But should. 
Cam OGs were like greased lightning. Still are pretty fast. Compared to say cpv3s, which IMHO are slow on first wake, then improve.
V4s do an occasional ball bounce but getting more rare and consistent.
I have a v4 stuck magnetically to a steel door, poor place for WiFi penetration and it’s fine there. My timelapse Aurora etc cam. Stuck IR. Free to me, Thanks Wyze.
I guess its just some bug cleanup as they go.
I dont have a fancy wifi 7 etc. mesh. I refuse to spend that kind of money on a router and points.
Mines an Orbi refurbished, $200, two access points relatively steady. Wifi 5. RBK53.
I’ll go POE before I do that kind of buy and run Ethernet cables all over my attic.
At least I could see POE (Reolink) in Home Assistant. Might anyhow, I’m old and retired and need something new to fiddle with.
PS: this isn’t an all the time major hassle issue, it happens occasionally. At least once daily though. Recoverable with some fiddling as mentioned above. But it’s a PITA .