No way. They would have gone out of business by now relaying all that traffic. The only hits they get are for authentication and hand off to the P2P provider. The Throughtek / TUTK P2P service (3rd party) establishes a direct link between your phone and your camera. On your LAN it doesn’t even have to. It took me a long time to find this again, the most authoritative post from Wyze on the process:
Below is the logic between device and TUTK servers for illustrative purpose. I intentionally use generic words to hide detail implementation.
During device setup time, the device registers itself with TUTK server to let Server know where it is. This is needed for TUTK to connect phone and the device in the future. However TUTK doesn’t know anything about Wyze user name, MAC, etc. We intentionally protected that.
During device boot time, it registers itself with TUTK servers. Wyze’s code used …
Of course for event recordings the camera does have to upload clips to Wyze servers. But not for any live or SD card viewing. Some more interesting info below.
FAQs How does Wyze protect my videos? The communication requests between your mobile device, your Wyze product, and the AWS Cloud Server are made via https (Transport Layer Security (TLS)) for Event videos. We use symmetric and asymmetric encryption,...
Here is more information on this from Wyze. Click on “How does Wyze protect my Live Stream and Event videos”.
FAQs How does Wyze protect my videos? The communication requests between your mobile device, your Wyze product, and the AWS Cloud Server are made via https (Transport Layer Security (TLS)) for Event videos. We use symmetric and asymmetric encryption,...
How does Wyze protect my Live Stream and Event videos?
With Wyze Cam, users can view camera videos using two methods: live streaming and recorded videos. Streaming is encrypted during transfer from device to phone. Camera videos are transferred under a secure channel from device to Wyze Cloud (ingestion) and from Wyze Cloud to phone (digestion).
Wyze employees do not have the ability to view a user’s camera’s live feed. This is because we use a P2P live streaming solution, which establishes a direct connection between the phone and the camera. While this is a technical solution to privacy, we also have a policy at Wyze prohibiting employees from viewing live streams.
Event videos, which are videos recorded when motion or sound is detected, are securely uploaded to the Wyze AWS server. From here, the video only would be accessed with permission from executive-level Wyze managers in extremely rare or severe cases, such as if Wyze were to be presented with a court subpoena. No other Wyze employees have access to these videos.
@WyzeTao ,
I have observed this behavior - it’s a clever design, as no internet bandwidth need be consumed for viewing the camera if the client (the app) is local. However, your search for the device doesn’t work if there is no internet connection. Even if the app (smartphone) and camera are on the same WiLAN and the same subnet, the camera does not respond to the search if there’s no internet connectivity. So the app cannot connect to the camera. No Live View. No viewing of Events recorded …
Let me try to explain what we are seeing on our end.
The Google Home integration is working for the most part. Meaning that we are seeing a large number of success connection and streaming.
BUT… we have seen a series of issues related to oAuth. oAuth is the mechanism that allows us to establish a trust between the user, Google and Wyze that the user is who is says he is and allowing to google to connect to the camera that belongs to the user. Because oAuth relies on tokens with expiration, a …
1 Like