Please set all Video (Livestream, Cloud Events, SD card Playback) to default to playing audio like it used to be (or make a setting toggle option).
Recently, many people have been expressing frustration that Wyze changed camera video to default to being muted in the v3.2 app. They have given several logical rationales as to why it should be the other way around.
For one thing, the industry standard is to have videos default to playing audio as pointed out by @Known1 :
Would it make sense to have Netflix default to muting every time someone tries to play a new video? TikTok every time you swipe to a new video? Youtube? Nearly no video-app defaults to being muted when a person intentionally selects to play a video. Why would someone want that when they are clearly intending to watch a video? Even if you can come up with a rare edge case, we still must ask, what is the norm and general expectation? It’s reasonable to request that Wyze fix this to be in-line with the industry standard experience everyone expects.
Another reason: anyone who does not like audio to play by default still have the option to implement this on their own by either muting the media volume on their phone or choose to just watch the new animated GIF notifications Wyze is developing and testing out at the time of this writing. Those are general reasonable workarounds for those who prefer it muted by default, but which isn’t possible for those who like it to play by default (we currently can’t just make sure our media volume is on to make sure all videos play sound, though we wish that was the case).
Reasonable exceptions to allow for muted by default could be acceptable when multiple cameras are streamed all at the same time such as in a camera group or on the favorites page when auto-stream is active for multiple cameras. But Individual camera page livestreams, Events Tab, and SD Card Playback should definitely all play audio with their videos by default.
If you truly believe that a large percentage of people prefer videos muted by default (something I highly doubt), an acceptable alternative solution would be to provide an app-wide setting toggle that lets each user decide whether they want the audio on by default or muted by default. However, I would suggest switching back to on by default until you create said setting toggle since “off” is clearly an edge use case compared to the industry standard experience and expectation that apparently only changed after the 3.2 app version.