Pretty sure DoT is the problem. Although, to be clear, it is Wyze’s problem to fix.
I have switched over to Cloudflare’s IPv4 and IPv6 DNS servers without DoT and my Wyze devices are still working fine. The only difference between now and when no devices would connect was having DoT enabled.
I did share this with a troubleshooting email chat I’m having with Wyze but I have not heard back yet.
A few people on the reddit channel suggested summoning the great and powerful @WyzeGwendolyn
I had an issue with a domain being blocked on Cloudflare DNS and they told me to fill out this forum (https://report.teams.cloudflare.com/) to get the domain put in the right category so it is not blocked, a few days later the domain I was having issues with was unblocked, so I would recommend trying to find the domains wyze uses and add them in with this forum, I am currently using Cloudflare DNS and have no issues with the forums or the app but I also use the RTSP firmware on my camera’s
Thank you I will try this . I have been having problems with my Wyze product and I also use 1.1.1.1
It worked . Thank you so much !!!
I have been summoned! And I’ll send this to the team. Thanks! 
You’re amazing, thank you!!
My pleasure! 
Hello @WyzeGwendolyn . It’s been two weeks and I’m just checking in. Has the team discovered or corrected anything regarding Dot?
And sorry reading all of this, if the user is having problems connecting to the wyze app or wyze server using CloudFlare, how are the wyze cameras connecting to the wyze servers to upload videos etc., Are wyze cameras hardcoding some other DNS server?
I’ll poke at this again. Someone said they were going to try it themself but I haven’t heard back about it. Thanks for the reminder!
You’re welcome. I’m also poking them again.
I will find the IP address that Wyze needs from the Router. I know it is somewhere in the forum but I couldn’t find it right now. I will share it once I found it.
I’m showing no issue resolving Wyze.com however I am not privy to the internal DNS mapping used by Wyze, so can’t speculate beyond that.
root@mydnspi1:/home/pi# dig wyze.com @1.1.1.1 ; <<>> DiG 9.11.5-P4-5.1+deb10u2-Raspbian <<>> wyze.com @1.1.1.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48507 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;wyze.com. IN A ;; ANSWER SECTION: wyze.com. 2 IN A 151.101.193.124 wyze.com. 2 IN A 151.101.65.124 wyze.com. 2 IN A 151.101.129.124 wyze.com. 2 IN A 151.101.1.124 ;; Query time: 26 msec ;; SERVER: 1.1.1.1#53(1.1.1.1) ;; WHEN: Thu Oct 29 08:16:47 PDT 2020 ;; MSG SIZE rcvd: 101
If you are looking to speed up not only your Wyze cam response times, but radically remove and eliminate most ads, then I highly recommend the use of pi-hole.
Been running two instances for over a year and it made an immediate and noticeable impact to all activity that uses DNS. additionally my bandwidth utilization was reduced, and even resulted in additional benefits such as more stability for my development server and my RaspberryPi’s.
It is nice to have a local DNS for simple benefits like your local device name mappings, facilitated analysis and tracking of billable hours and detailed breakout for any clients, just a clean tidy little bundle.
I chose to run an instance on a $10 pi zero w, you can run it in a docker container on your home system or laptop, I even have an instance on some cloud servers that anyone can get free development credits and run for the benefits to be accessible externally without reliance or need to be on a local VPN tunnel.
I do have a VPN tunnel available as there is a nice bundle that will provide that package as well, but depending on your volume, I’d recommend a bit more horsepower such as a Pi 4, but UMMV.
Downside? None that I’ve encountered.
Upside? Faster performance in most tasks, global protection for any on your LAN, no need for any paid VPN, just a tight little solution…
Very nice
Setting up my pi-hole now and already running into the same issues mentioned earlier in this thread. Seems to be related to this:
@alanizat did you have to whitelist anything in particular to enable your Wyze Devices to function?
@XuLi were you able to find those addresses?
Hi Random,
I think the latest CloudFlare (https://1.1.1.1) has whitelisted Wyze. As I just checked, I could setup and connect to the cameras with CloudFlare DNS enabled. The CloudFlare legal is 6.0(1596).
If you or anyone else that still having problem with the CloudFlare 1.1.1.1, could you provide a detail Steps-To-Repeat for us to take a look?
Thank you.
My Wyze devices are working properly with Cloudflare 1.1.1.1 and 1.0.0.1 set as the DNS servers on my router (as well as the IPv6 cloudflare addresses). @XuLi what do you mean by:
The CloudFlare legal is 6.0(1596).
with DNS over TLS on the router enabled, there are issues on several Wyze devices
see: DNS over TLS support - Wishlist - Wyze Forum (wyzecam.com)