Pan Cam 4 Live View Audio, No Video

Pan Cam v4 is not showing videos on Live View.

I’ve given it a factory reset, restarted it and synced it but nothing makes video show up on my.wyze. com…only a blank video

However, there IS audio!

Thanks for any help!

Brew

Thought I would include this…

No one has any ideas?

I went to the page “Release Notes & Firmware” where I tried to download the firmware for 4.70.0.3005 (January 6, 2026)

But there are no download links so I can revert the driver.

How would I revert the firmware?

I re-installed the camera in the app and the problem persists.

Should I return it?

Pan Cam 4 Live View Audio, No Video In Firefox

I’ve been having a problem with Pan Cam v4 not displaying in Events in Web View. I get audio but no video in events.

I just got off the phone with Support at Wyze and figured out that my problem is with Firefox as it works with Chrome

This is lazy programming. When programming net-centric applications like these it’s incumbent on the programmer to ensure it works with at least the top 5 browsers, which Firefox is in the top three.

Get it together WYZE!

[Mod Note]: Your new topic was merged to your original topic for context/continuity and to conform to the Community Guidelines. Please avoid cross-posting the same issue as multiple topics.

It isn’t lazy programming. Pan v4 uses the HEVC video codec (like nearly all 4K devices) which is not included with most browsers, hence seeing no video. Chrome includes it free. Edge charges for it.

It can be added on to Firefox but not sure if the wyze web view will “see” it or not.

This is why the system requirements for web view specifically list Chrome as the only supported browser.

It IS in FF

In about:config → media.hevc.enabled

As I said -

So, the issue is that Wyze won’t make their stuff compatible with FF…gotcha

I’ll add that HEVC is a PART of FF as of ver134.0 Jan 7 2025, as in the image I posted earlier

There’s still no excuse to not program for FF

Not sure what to tell you, the requirements for Web View state Chrome. Not sure the reasoning, FF does have more limitations built in than other browsers, may or may not be part of it.

Some have managed to trick Edge into working, maybe there is a workaround for FF, but like I said, officially they only support Chrome.

I did that with both Edge and Opera but failed with Firefox, and it’s why I think the presence or absence of a particular codec isn’t the determining factor for whether Web View will play video from a particular Cam. If it was, then I wouldn’t expect telling a non-Chrome Chromium-based browser to misrepresent itself and send the Chrome user agent string to actually work. Something else is going on, and I think at least part of that is Web Portal servers parsing the User-Agent string and using that to shape the user experience, which I’ve tried to suggest to Wyze that they shouldn’t do, at least in part because MDN seems to indicate that UA sniffing is a bad idea for determining how a server is going to present information to a given browser.

I’m not a developer, but whenever I see things like this happening (and I know I’ve said this before) it tends to remind me of the days when some Web sites were broken unless they were accessed with Internet Explorer because they were written with certain nonstandard markup and ActiveX dependencies, and that has never sat well with me. I do understand why things like that were done at that time, particularly for certain business use cases, but I think Web standards have advanced to the point now where giving users browser choice and adhering to open standards—especially with regard to accessibility—should be the norm, and I don’t think it’s unreasonable for consumers of a company with a stated goal of being friends with users to expect to be able to use whatever (modern, mainstream, standards-compliant) browsers they choose and access their content. Forcing the use of a specific browser seems narrow-minded and unfriendly.

Edge (being a chromium browser) may include HEVC/H.265 for playback or streaming, not positive. I know if you want to watch a 4K video locally on your PC, MS now makes you buy the codec.

Someone has to pay, in the case of youtube, netflix, etc they pay the fee as part of your subscription or their ad revenue. Maybe Wyze is doing that, but in that case I would not expect audio only with no video (which is exactly what you get when you don’t have the video decoder). Would expect just an error that your browser isn’t compatible or something.

I have experienced situations where downloading a cloud event video from certain new Wyze Cams and trying to play that file locally—like when Windows wants to open the MP4 in the default Media Player—causes Windows to prompt the user to buy the HEVC Video Extensions codec pack from the Microsoft Store, so I understand that part of what you’re saying. The matter of the codec in the browser itself (Edge or Opera or whatever) doesn’t seem to determine whether Wyze Web Portal will play videos from a newer Cam like Cam Pan v4, though, at least not in my experience. If the codec was the thing that mattered, then I would expect whatever browser with that component to just work with Web View. Because it doesn’t and because I’ve been able to make Web View work with non-Chrome (though still Chromium-based) browsers by having the browser report a different user agent string, it feels like Wyze has arbitrarily chosen to limit user choice based on a user’s preferred browser, and I don’t understand why this would be the case.


Edit @ 2026-05-18T16:26:10Z

I should probably also note that when trying to view one of these files locally (I downloaded a recent event video that was created by a Cam Pan v4 to my phone and then copied it to PC), Media Player in Windows will play the video file’s audio even after I deny the prompt to download the HEVC Video Extensions codec pack, but the video is just a black/blank screen. I think this is because—as I understand it—the MP4 format is just a container that can hold whatever encoding someone chooses to put into it, and in this case looking at the file’s contents (e.g., with ffmpeg -i [filename]) shows me that the audio stream is encoded in AAC but the video stream is encoded in HEVC. I think Windows is playing the portion it can without the installation of an additional component and saying, “You need this other thing that we’ll sell you if you want to see the video.” That part sort of makes sense to me (though it’d be nice if Microsoft would just include the codecs for HEVC and HEIC as standard).

I say that to say that I do think the codec issue is part of what causes the problem when trying to use Web View with a non-Chrome browser, but I don’t think that tells the whole story, because otherwise I wouldn’t expect to need to also lie to the Web Portal when using Edge or Opera, and I wouldn’t expect the lie to have any effect if only the codec mattered.

Incidentally, VLC media player on Linux (in this case a recent KDE neon User Edition) opened and played the downloaded Cam Pan v4 event video without issue and reports the same information about the packaged audio and video streams.

Tangentially, I still don’t understand why viewing Cam OGs (all models I’ve tried) fails in Web View when using Firefox (but works fine in other Chromium-based browsers without lying about the user agent). That’s another area where Wyze is hobbling the user experience, I think.

To be fair, I haven’t spent a lot of time in the most recent version of Web View, so maybe they’re addressing some of these issues, but the Help Center is still pushing Google Chrome, which gives the impression that they haven’t made any real efforts to open this up.

As far as I know one end has to pay for the use of the CODEC. So your browser or the site hosting the content (in which case the site basically just tells your browser that it is allowed to play, assuming the browser has the CODEC). So just because a browser like FF has it, doesn’t mean it will play without being told the content is licensed.

Of course there are workarounds, and I suspect spoofing the Chrome user agent may be one of them, i.e. Wyze reports that it is allowed since it thinks it is Chrome, and Chrome has the license (or Google offers a very discounted rate for streaming HEVC via Chrome or something like that).

The HEVC codec has been part of Firefox for over a year, in version 134 (it’s at 150 now)

And it doesn’t have anything to do with Windows because it works in Chrome. I even paid for the Windows HEVC driver for Win11 but it didn’t make a difference either way

I’m aware, I said that, and you’ve said it a few times.

But that in and of itself is not enough. It likely comes down to licensing.

The paid one for Windows 11 is for playing local files, not streaming video on the web.

Long story short, FF is not supported by Web View.

Here’s a video of the problem:

https://support.wyze.com/hc/en-us/articles/4410968629275-What-is-Wyze-Web-View

Wyze Web View is not supported on Firefox browsers.