Wyze Camera App causes Bell Internet to drop.

Gord_R
Contributor III

I switched to Fibre to the Home, 1.5GB/s, in February 2023. My set-up is quite standard, a Bell Giga Hub running my network with a couple of PCs, an i-phone, Andriod phone, a couple of i-pads. Most are connected by WiFi, one PC is connected by Ethernet cable. Nothing fancy, modem settings are pretty much as received.

Immediately after installation, we started experiencing internet outages several times a day, each outage 3-6 minutes duration. Everything (even the wired PC) experiences the outage at about the same time (so it is unrelated to the WiFi). We found that outages were correlated to the use of the Wyze Cam app (wyze.com). We use the app to stream video from a remote camera (on a different network). The use of this app does not always force out network down, probably about 50% of the time. But, almost all outages of 3-6minutes happen when the wyze app is used. (There are shorter outages of a minute or so that are unrelated to the wyze app.)

The anatomy of a typical outage looks like this: We will open the wyze app and start the video streaming. At this point, the CPU usage in the modem often spikes to >30% (as high as 70%) (up from the usual 0-5%). Pings from a PC to the modem (via ethernet, not WiFi) take longer (up to several hundred ms , as opposed the the usual 1ms). The home phone (on the phone port of the hub) sometimes become erratic, audio breaking up several times a second. This only lasts for maybe a minute, then the phone, CPU, and ping times return to normal, but the internet on all computers is down. I can ping the modem from a computer on my network just fine. I can ping the outside world from the modem (using a modem utility) just fine. But I cannot ping from the computer to the outside world. It returns "Request timed out". All other computer browsers return messages like "xxx not found", or just do nothing. This will go on for 3-6 minutes, and then everything starts working again. There is nothing interesting on the modem system log. The wyze app (running from an i-pad or i-phone) is working perfectly all through this. Sometimes we run the wyze app for a half hour, sometimes for 2 minutes, but the outage is usually 3-6 minutes (ie, the length of the outage is unrelated to how long the Wyze app is running)

I have a PC (the Ethernet cable one, no WiFi) pinging the outside world every 30 seconds, keeping records for me, and I have about 6 weeks of records now, well over 100 drops.

@BellPatricia  and @BellNick has been collecting data, but have not offered any suggestions or solutions. (except turning off UPnP, made no difference) Bell service has been linked in. They made 2 service calls, replaced the modem (with an identical model), replaced the fibre to the modem, and they connected to a different circuit in the box behind the house. No difference. The technician concluded that it's a problem with the app. I don't accept this because: 1) wyze worked fine when we were on DSL. 2) Relatives of ours also use the same app with the same camera without issue. 3) it works with Rogers (using cellular data) 4) There are no issues like this listed on the wyze site (though I am asking them about it now) and 5) The wyze app runs at about 60-200kb/s (and I have verified that this is approximately right), so < 0.1% of our 1.5Gb/s bandwidth, this should be easy! Furthermore, our neighbours are experiencing some drops (they got fibre a week after we did), but they have not noticed a pattern yet.

So my question to anyone out there who has read this far (thank you for reading!):
-In general, should an app (no matter how poorly it is written) be able to bring down the entire network?
-Do you use the wyze camera app with Bell? Which modem do you have? Does the camera work, have you looked for dropped internet?
-I am, at best, a computer hack, and don't know anything about internet protocol. Do these symptoms point to anything?
-Can you suggest other diagnostics that might help us narrow down the problem?

Thanks for listening... GR

0 15 3,244
1 helpful reply

Accepted Solutions

I am thinking the optimize home wi-fi feature of these modems might need some "adjustment". I am thinking it keeps moving devices to the 5/6 Ghz bands who can only operate at 2.4 bands.

There's a feature for that called "band steering", but I am thinking it's causing issue on the home hubs with certain devices. Ubiquiti seems to have this feature implemented better. My U6+ is just like your U7 Max provides rock solid wi-fi connectivity and coverage.

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

View reply in original post

15 REPLIES 15

FTemplar
Bell Employee

Hello, I used to have Fibe 300 with the good old HH3000 and everything worked fine for several years. I upgraded to Fibe 1,5GB recently because it was basically the same price for 5x the speed. Or so I thought. We are experiencing the same symptoms (4-5 minutes outages occuring every 30 minutes or so, all the time). The internet connection drops over both WiFi and Ethernet. The problem went away for almost a full week before coming back again. We already had the modem replaced for another HH4000. It's worth mentioning that we don't use Wyze at all. Here is a small part my home made log below I made (ping a website every second). To replicate this program, go into Windows Powershell and paste the following :

ping.exe -t www.bell.ca | Foreach {"{0} - {1}" -f (Get-Date),$_}

This has something to do with the HH4000 and what we need is a new firmware version to fix this issue. This is a serious matter that requires attention. I work for Bell as a FTTH network designer and frequently get dropped out of meetings, VPN has to reconnect, etc. Switching for a competitor is out of the question, so please get it fixed ASAP.

@Gord_R @BellNick @BellPatricia 
Thanks, Jonathan

2023-06-11 8:30:02 PM - Reply from 45.60.101.212: bytes=32 time=10ms TTL=54
2023-06-11 8:30:03 PM - Reply from 45.60.101.212: bytes=32 time=10ms TTL=54
2023-06-11 8:30:04 PM - Reply from 45.60.101.212: bytes=32 time=10ms TTL=54
2023-06-11 8:30:05 PM - Reply from 45.60.101.212: bytes=32 time=10ms TTL=54
2023-06-11 8:30:06 PM - Reply from 45.60.101.212: bytes=32 time=10ms TTL=54
2023-06-11 8:30:07 PM - Reply from 45.60.101.212: bytes=32 time=10ms TTL=54
2023-06-11 8:30:08 PM - Reply from 45.60.101.212: bytes=32 time=10ms TTL=54
2023-06-11 8:30:10 PM - Reply from 45.60.101.212: bytes=32 time=10ms TTL=54
2023-06-11 8:30:14 PM - Request timed out.
2023-06-11 8:30:19 PM - Request timed out.
2023-06-11 8:30:24 PM - Request timed out.
2023-06-11 8:30:29 PM - Request timed out.
2023-06-11 8:30:34 PM - Request timed out.
2023-06-11 8:30:39 PM - Request timed out.
2023-06-11 8:30:44 PM - Request timed out.
2023-06-11 8:30:49 PM - Request timed out.
2023-06-11 8:30:54 PM - Request timed out.
2023-06-11 8:30:59 PM - Request timed out.
2023-06-11 8:31:04 PM - Request timed out.
2023-06-11 8:31:09 PM - Request timed out.
2023-06-11 8:31:14 PM - Request timed out.
2023-06-11 8:31:19 PM - Request timed out.
2023-06-11 8:31:24 PM - Request timed out.
2023-06-11 8:31:29 PM - Request timed out.
2023-06-11 8:31:34 PM - Request timed out.

I am a Bell employee and a customer. My views on the Community Forum are my own and may not be the views of Bell or any of its affiliates.

Gord_R
Contributor III

Thanks so much for sharing your experience, @FTemplar  / Jonathan. We were on vacation for about 3 weeks, and I left the computer pinging every 30 seconds. There were only 2 brief "request timed out" drops. But as soon as we returned and ran the Wyze app, the 3-5minute drops returned. So, it works great as long as you don't use it. It is very interesting that you are experiencing this all the time. I wonder if you have another app running frequently that stresses the modem the same way as Wyze?

I spoke to the Wyze people, asked if they did anything unique or unusual in their protocols, and after quite a run-around, they claimed that there is nothing unusual happening. However, it as a vague question, and, heck what else WOULD you to expect them to say?. Looking at their help chats, I did not see any symptoms like this (but they seem to have much bigger issues!).

I am optimistic that you, working for Bell, may have better luck getting someone's attention. (I don't really think anyone at Bell has taken my complaints seriously) I agree with your thought, that it has something to do with the firmware in the modem. The fact that the modem CPU activity increases, and ping times (just to the modem) increase when Wyze starts up suggests that. But, getting the firmware debugged and fixed (and I assume that would be done at Sagemcom, not Bell) will be a long task, and won't happen unless there are more users affected.

Hey, do you have a phone connected to your modem? Does it break up at the beginning of a drop? 

Please let me know if you are able to get someone's attention.

Thanks,

@Gord_R  

@BellNick @BellPatricia 

@Gord_R 

You're very welcome, after all, we're in the same boat and I was glad to find someone else that is experiencing the same issue that we are (and able to troubleshoot to some degree). We don't have any phones connected to the modem, other than via WiFi. After seeing your post here and in another thread, you got me thinking and I looked at my background processes. I decided to terminate a bunch of them, and so far I haven't had a drop in over 2 hours. Really weird...

Amongst the processes that I interrupted :

- Plex (streaming app which I use to stream movies from my PC to a PS5, phone or tablet).
Intel Killer network (software for Intel network adapter that is supposed to optimize performance and minimize packet loss, I honestly had no idea this was running, but since I never had any problem before with the HH3000, I never had to shut down processes in the first place). The tech that came today basically could do nothing other than validate that the network between the CSP (Central splitting point, the almond colored cabinet near your home) and the modem was working fine. He switched my fiber optic from the Huawei dividers over to the newer Alcatel dividers and that's about it. (There are more or less 12 fibres entering the CSP which are then divided into 32 ports each, in order to be able to service a few hundred customers). He did say he thinks it's the modem itself being the issue, and that if there's several of us with the same issue, Bell should be rolling out a firmware update soon (wishful thinking), from what I see you've been having that issue for a while now. Anyway, you might be onto something. I will let my script run overnight and report on the results tomorrow morning. 

Regards, Jonathan

I am a Bell employee and a customer. My views on the Community Forum are my own and may not be the views of Bell or any of its affiliates.

FTemplar
Bell Employee

@gord I'm happy to report that i've not experienced any outages since last night, so there is definitely something going on in regard to Windows processes running in the background which is putting stress on the HH4000.

I would be curious to see if these outages happen at all without a device connected via Ethernet. One of the processes that I terminated was a software related to my Network Card's ethernet controller. That can't be a coincidence.

I am a Bell employee and a customer. My views on the Community Forum are my own and may not be the views of Bell or any of its affiliates.

Gord_R
Contributor III

Interesting.

It raises a question: If a particular process or app causes the internet to drop, how do we assign blame? Should the connectivity provided by Bell be so robust that no app, no matter how poorly written, cannot make it fail? Or, is it possible that an app could cause connectivity to drop, no matter how good the infrastructure is? In this case, I tend to blame the infrastructure because we both found things worked well before we got the HH4000. And these apps seem to work fine on other networks. 

Anyway, how do we work together to get Bell's attention?

Cheers, @Gord_R 

Gord_R
Contributor III

I've been quite busy, so have not been able to nag Bell on this issue. However, it still happens. At about the same frequency as before, about 2 times a day when we run the wyze ap. It's been almost 6 months now, and I have some time to nag!

So, @BellNick @BellPatricia , what do I do next? Clearly, waiting for a solution does not work.

@Gord_R 

Hi there @Gord_R,

Thank you for keeping in touch with the Bell Community 🙂

Our next recommendation to troubleshoot further would be to do a factory reset on your modem. Check out this article on our website: How to reset my modem to its factory settingsOpens in a new tab or window

If the issue persists after a factory reset it could perhaps be something on your network causing the connection to drop.

To test that simply set up a Guest network, and have your phone connected to the Guest network only. This will ensure the phones traffic is separate from the rest of your network.

We have a great Blog for you to check out that includes more information Creating a Guest networkOpens in a new tab or window

Keep the Community posted on how things are going.

- Patricia

Gord_R
Contributor III

Hi, @BellPatricia ,

I have been at this for 6 months, and have rebooted, and factory reset (and even replaced, for that matter) the modem several times. If there is some reason that you suspect that a factory reset will fix it NOW where it has not in the past, I'll try it, but I want some assurance that you think it will fix it. Otherwise, I will spend the rest of my life resetting the modem. 

And it has nothing to do with the wifi. The wired ethernet connection drops as well.

What I really need is advice on how to escalate this to a higher level of support. We are beyond the "check to see if it is plugged in and give it a reset" stage. I am convinced that it is a bug in the modem firmware, and someone at Bell will actually have to do some troubleshooting. I can reliably (80% of the time) make my connection drop. If Bell can watch what's happening on my line when the network drops, then we may have a chance of actually fixing it. Just give me a time when I am home and we can coordinate. I'm happy to help, I see it as a win-win situation. But, I need a technical contact within Bell to work with. 

Good day @Gord_R,

Thank you for your reply.

We do appreciate all of the troubleshooting that you've tried so far, and we want to continue to work together on this.

We will be reaching back out to you via private message shortly. Please check your Messages within your profile avatar in the top right corner.

Unsure how to check or send a private message? See How to send a private messageOpens in a new tab or window

In the meantime, were you able to test a Guest network to see if that happens to make a difference?

- Patricia

Vinny1
Contributor II

Exact same situation as you, any positive outcome?

Gord_R
Contributor III

No. I got up to another level of support, he witnessed the failure, but basically said that it was not a priority to fix it, not enough people complained. And, from what I've seen, Bell's network is in chaos, they have bigger problems to fix than mine, and no one seems to know what they're doing. But, that's being very charitable. I'm considering switching to Rogers and raising it with the CRTC, but honestly, I'm just tired of dealing with it. It's a couple of drops a day at the most inconvenient times, I'll live with that until Bell messes something else up.

...defeated Gord

Alexander Huzar
Contributor

My internet does not drop out, but 4 out of my 7 Wyze cameras refuse to (stay) connected. At first I thought it was a new firmware to my Ubiquity AP, but the Wyze cams connect perfectly fine to my cell phone's hotspot and every other network that isn't going through Bell Fibe. I have zero other issues with Bell Fibe. Also I'm completely baffled why 3 of the 7 cameras work perfectly fine and why it's always 4 of the 7. Reflashed firmware, etc. I also made a post on Ubiquity to let them know it's not their issue.

To Bell folks - happy to work with whatever engineer to determine why Wyze connectivity is so broken. I have a perfectly reliable way to reproduce now.

If all 7 connect to an Ubiquiti AP it would be very easy to figure out why they are disconnecting as those AP's have robust logging features.

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

After further diagnosis there seem to be TWO issues.

First issue: Ubiquity U7-Pro-Max APs needed a firmware update to fix 2.4 GHz issues. For me the 7.1.29 firmware fixed everything.
Second issue: The Bell "Giga Hub"'s 2.4 GHz is giving me identical issues with Wyze cameras so the Giga Hub also needs a new firmware to address 2.4 GHz IoT device connectivity issues.

Maybe Bell can talk to Ubiquity about how they fixed their firmware? Reason why I say this is because based on the conclusions of my testing, I myself came to the wrong conclusion. The internet itself is perfectly fine, it's the firmware that's causing 2.4 GHz issues.