Thanks @grapefruityoda !!
Good grief. Like anyone is going to do all that! Wow.
Well the 2 he cited did, too. That I think qualifies for, âanyoneâ.
Lol then donât do it. Itâs no skin off my back. Iâm just trying to provide a possible solution instead of waiting for Wyze to come and fix this issue and who knows when that will be. The people experienced in networking should have no problem doing this assuming they have their own routerâŚ
Wow, really? You got me âanyoneâ.
My point is, 99% of customers are not going to do this. [Mod Edit] So the solution per yo his to buy a router and do some lan work. Good, have fun.
And Iâm sure youâre one of them. Let him help those 1%. As for you continue your âdialogueâ with Wyze.
All the more reason I advocate to buy and use your own isp certified gateway. When I decided to go TP Link mesh, all I had to do was connect an ethernet cable to my 1G Motorola gateway and I never missed a beat with any of my IoT devices or cameras. No bridging necessary. I have Xfinity and based on what I know is charged for monthly rental, buying your own gateway would pay for itself in about 12 to 18 months.
Verizon is my cellular provider and I am always able to view my cams remotely wherever I am traveling with the 4g network. Also ignoring all the marketing to upgrade to its 5g.
Thanks for sharing! I used to have Xfinity, and had constant issues with them related to connectivity. They were always messing with things. Once I switched to Fiber, all my connectivity issues were no more.
This gives some good starting points to test out. Iâm going to start asking some people with this issue who their ISP is, what router they use, etc. I wonder if something as simple as changing the DNS could help. I know when I used Xfinity, their default DNS was atrocious. It felt like they weaponized it in a way that some stuff would work better than others now that they were no longer bound by net neutrality.
That post you linked to provides some interesting ideas to explore further. It certainly helps to point to a potential explanation of why some people have this issue and others donât. Some people may be using hardware or a service that is blocking external TUTK connections. That might be difficult for Wyze to overcome though. If someoneâs hardware is blocking the service Wyze uses for remote authentication, it stands to reason that the only real solution would be for Wyze to switch to a different service that isnât being blocked by a major ISP.
At least youâve shown us a potential workaround that some people could explore for the time being. I wonder if now Wyze can use this info or share it with TUTK to see if they can confirm what is causing this blockage for some people and not others. I have passed this on to see if it will help them find a resolution.
Oh good god! Like anyone is going to read all that. I did, ugh.
The bottom line is this is on Wyze! Not for any of us to trouble shoot, buy additional equipment, change DNS routes.
Seriously how can any of this be taken seriously when the message is for US THE CUSTOMER to fix this.
I could never tell my client any of this for a fix. Theyâd fire me and laugh at me.
Mine is very simple: ISP is Xfinity with my own Motorola MG8702 modem with integrated AC3200 router. I have never had an issue connecting from any remote location via Cell Data or a different wifi.
So yours works because you arenât using their default hardware and custom security.
Iâm reading that they have their own custom âxFiâ security that is designed to intentionally âblock remote access to smart devicesâ from sources they deem concerning. Which is exactly what is happening to people here.
My guess is that whatever blocklist they are using is blocking TUTK. Ironically, Wyzeâs own routers use a blocklist through âFiredomeâ which has, more than once, added TUTK IP addresses to itâs block list (probably from some randos reporting it in some way), and Wyze had to get them to whitelist it again. I bet the same thing is happening to Xfinity with whatever blocklist they are leveraging. I bet their blocklist keeps telling them to ban TUTK remote access, but that then prevents Wyze being able to authenticate the camera connection.
The start of the resolution might actually be for Wyze to contact Xfinity and figure out what blocklist they use and get that blocklist to whitelist the TUTK IP range that their services use. I really wouldnât be surprised at all if this is the primary issue (not saying it is or isnât, but it really wouldnât surprise me). Then if they resolve things from that blocklist it might fix the issue for others who arenât on Xfinity, but whose routers/ISPs use the same blocklist.
Well, I am not home and canât connect to 2 of my v2 cameras. Says theyâre off line. 2 out of 5 v2 and 2 out of 11 cameras. I have Spectrum. So now tell me itâs me. 1 hour ago I could connect to 1 of the 2.
This is on Wyze! All my other devices Wyze and other connect remotely right now.
Eufy Solocam S220 or Kasa Smart 2K WHD.
Great reviews on Amazon. I have other Kasa stuff that has always worked.
I also have some Govee stuff that always works.
My Nest smart thermostat has been working good too BTW.
So not a WiFi or internet gateway issue. Of all the WiFi stuff I have, bulbs, Alexa shows, or WiFi outlets all work remotely from my desk at work EXCEPT Wyze.
Exactly!! Notice how you did that post not in 6 paragraphs too? Concise.
One of the reasons I went with Wyze in the first place is I didnât have to be an IT nerd to do it. Setting up another router in the system might just be another weak link in the chain for me.
The Govee WiFi heater in my basement workshop has never not worked.
Ok thanks for sharing
Exactly!! But here youâre expected to be an IT nerd and want to spend hours and money fixing this stuff.
BMICHâs words may seem harsh, but the reasoning and logic are clear. This is four months of frustration piling up, with possibly four more to come. That being said, I will give the benefit of the doubt and try adjusting the WiFi setup, hoping for the best.
Most of my WiFi gadgets are from Wyze, including an air purifier, sensors, light bulbs, cameras, and even headphones. Moving to another system would be financially challenging. My Habitat and Nest thermostats work just fine, and all devices are on the same network. Iâve had the same network provider and equipment for years without making any changes. All Wyze cameras worked fine until the incident in February.
Most Wyze cameras are experiencing this issue, except for the Doorbell Pro. When I open the app using cellular data, the Doorbell Pro works every time, providing live footage in just a second or two. White all other wyze cameras struggling.