many of the comments here are off topic from what I intended to point out to wyze. great camera btw.. on a phone or tablet client you get a fantastic over 200 degree panoramic view which is lovely. but it’s a new camera and probably has more than a few little deficiencies. one of which is the data from cam to client isn’t local, and for this particular dual 2k cam generates 2 or more Gb/hour of traffic.. I only ran it a couple hours yesterday, and my traffic logged by Xfinity was 19 Gb.. Last month - around oct 20, I got a notice that I had used 70% of my 1.2 Tb limit from Xfinity. So, I cut back on my continuous monitoring and managed to finish the month right at the limit.. yesterday, just a few hours of live streaming the dual view at 2k used about 15 Gb. it should have been insignificant. you guys talking RTSP - yeah, that could work, but the other older cameras manage to keep the data local.. so let’s try to keep it on topic from the peanut gallery, OK?
maybe a little off topic from my post, but I have 14 cative cams on my local wifi. one being a duo cam pan. I had had zero connectivity issues with any of them, but I run 3 nodes of wifi 6. your issue might be with wifi connectivity on your local net, not the camera or ISP. you may want to try re-orienting your router for better signal at the camera.. if you still want to discard the camera, you can send it to me.. lol
On the app it is (as long as you’re on the same network with nothing blocking it). Only on webview does it have to leave your network, and that is not something that can be changed. You can try some of the suggestions I gave to avoid using webview.
It did not use 19GB in 2 hours.
The discussion here has been about keeping the stream local vs looping through the web, which is the topic you started. If you mean “only reply directly to me”, that’s not how discussion forums work.
This thread has always been about webview, and in several replies I re-iterated to you that we are talking about webview as you seemed to be missing that important point.
Obviously your browser can access a web site hosted on your local LAN. But that web site can not then tell your browser to access other devices on the LAN directly, not without a plugin or daemon running on the PC. Not even sure a plugin would work on Chromium browsers now that they’ve gotten much more strict with their requirements for that.
Where have you seen that webview uses WebRTC to talk directly from your browser to the cams? If that was the case, this thread would not exist (it also isn’t how WebRTC works). They may be using it for the connection between the webview server and your browser, that doesn’t change the bandwidth consumption.
Right here on the forum, 4 years ago, too.
Again, nothing to do with Wyze Web View which is the topic here.
WebRTC works between devices and apps, not browsers. It can do browser to browser, but not browser to a device on your LAN, at least not with some sort of “helper” app on your PC or browser plugin.
Did you catch the Chromecast referenced in the article? What do you think Chromecast is? Clue: It’s browser-based.
Nope, it is Android based and runs a wyze app, just like your phone. Same for alexa and google home referenced there. The only “browser based” portion of chromecast is the ability to cast from chrome (using a plugin built into chrome, not a web site). Even then, it usually is not actually casting video from your PC, it is just telling the local browser on the chromecast to load the page you’re looking at.
Apparently you’re convinced, so no point in arguing. But please post evidence of your wyze web view streaming video directly from the cams over your LAN.
You’re trying to limit things to your liking, but …
The original OP is about his internet charges getting out of hand, because he’s using a browser, not necessarily WebView. He didn’t even mention it.
Read the OP again.
Take your own advice.
What else would they be doing with a browser?
I did, and I note that WebView isn’t even mentioned. It came from you. And I’m trying to correct your flase assertion that a browser can’t access a LAN host.
I literally circled the word “web-view” for you.
I’m done, this is a constant theme with you.
So I can’t post anything that corrects a wrong post from you?
doi you have a duo cam? I don’t think so. you’re making an assumption. I made a measurement. most of that 19gb was due to the duo cam.
good. not using web view. using an Android client. please read more carefully.
Android client. local network. hefty data up and back through the internet. not staying on the local lan. It’s a new product.. people are making assumptions here who don’t have the new cam, so they make assumptions based on prior products.
It really doesn’t matter whether you’re using the Wyze app or a browser, if you’re accessing your cameras from outside the LAN. Anytime the network path involves your ISP, the ISP meter runs. If your ISP service has a cap, and if the camera has a high resolution, there’s a good chance that you’ll go over that limit.
Don’t entertain @bryonhu when he recommends an 8K Reolink camera. 
i’ll type slowly for you. client and camera are on the same lan. I retired as an internet engineer a while back, but this stuff isnt oit of my league as i was fluent in internet testing, voip and video over internet.. I also have 37 wyze cameras. the duocam behaves differently in this regard to the other cameras. some of the other cameras had this issue before and wyze quietly resolved it as those cameras will supply video from camera to client when the internet is down ( and i’ll repeat - client and camera ore on the same local net.. now - if you dont have a duocam - you arent helping, you’re only speculating and verging on trolling.
If you think Wyze app running on the same LAN is contributing to your ISP usage totals, think again.
I’m surprised that a network engineer, even retired, can only afford a capped internet service.
Appreciate the vote of confidence in my finances, but let’s stick to bits over budgets. Xfinity’s usage graph doesn’t “think”—it logs 1.8+ GB/hr outbound to Wyze IPs 100% relay bloat. Not here to arm-wrestle—
@WyzeTom
(or any mod), this is a quick firmware win for the new Duo: Post-auth direct UDP for on-LAN. Thread link for your QA queue. Early feedback like this keeps the product sharp.