Última discussão há 10 h

Fórum Wyze Forum

forums.wyze.com

Fórum Discourse em inglês. 12 seções acompanhadas: Wyze App, Beta, Cameras, Captured on Wyze, Home, Lifestyle, Wyze News, Sensors, Services & Integrations, Watercooler, In Progress e Wishes Granted.

Discussões por dia
12
Discussões coletadas
471
Mensagens por dia
62
Seções
12
Fontes acompanhadas
14
Motor
Discourse

Últimas discussões

Coletadas a cada 4 horas do feed público do fórum. Reproduzimos apenas o título, o link e o começo da mensagem; cada link leva à fonte.

Firmware Updates - Released 9/14/2026

I updated my pan v3 and it’s still not loading the sd card, before it would load for a few secs then I would have to restart the device for it to work agaon but now the card won’t load at all

Lighting change constantly tripping pet detection

OK yeah that’s a pretty quick and extreme lighting change, are you in the south or midwest? In New England we rarely see something like that, I think something to do with the sun being a bit further away or maybe just different types of clouds here. What you’re seeing is akin to headlights on my yard at night which always trips my cams. Use detection zone to exclude that casting (maybe the well pump and log in the corner too, who knows which one it is thinking is an animal), but no it won’t help with the lighting change still triggering events unless you turn off “other motion”. I think it is just because your porch stays quite dark but the yard has a significant change in a short time. You could also try excluding the borders (trees and shrubs in the distance). The cam makes decisions based on how many pixels change so perhaps reducing that will help? Maybe even reducing some dark spots like the porch roof and maybe even the poles will help? The OG is actually one of the better ones as not detecting lighting changes, when I had one on my front walkway (very small detection zone) it rarely was triggered by headlights. But now that I have a v4 there, it constantly is. I have an OG in another area that gets washed with headlights and again is a pretty small detection zone with sensitivity 100, and it never triggers on headlights. But then for a while I had an OG watching my front lawn (trying to figure out who was letting their dog constantly go in one spot leaving a huge brown

Firmware Updates - Released 9/14/2026

Yesterday I received a prompt on my Android phone to update the V4 … I cancelled since I wanted to update later … but later when I went to the V4 Firmware page it did not offer the update … maybe because I have Auto Updates turned OFF?? Today I received a prompt on my iPad to update the V4 and I accepted … the update processed OK.

Wyze app 3.22 - Released 9/16/2026

The App has been compiled for Android 16 and above which now forces “edge-to-edge” screens and the developers have not adjusted all the screens to account for this. In 3.21 the OG landscape view clipped at the top and bottom with black/white bar at bottom depending on Dark Mode setting … Looks like this is FIXED in 3.22. Now they just have to fix: The Air Purifier Screen clipping at the bottom. Thermostat screen has a much larger font. …

Lighting change constantly tripping pet detection

Thanks for your suggestions. Reducing the sensitivity (to about 30 percent - usually at 50) caused me to miss recording a flock of wild turkeys sauntering through the yard. I happened to be viewing the camera at the time or I wouldn’t have even known. It is clearly the shadows cast by the sun that trip the detection. There is a concrete casting of a bear on the porch (see clip below for an example of a false positive, casting is in the lower left corner), but it’s hard to believe that the algorithm thinks it’s an animal. Note that most of the detections involving lighting changes show up as motion, but every once in a while it comes up as a pet. Why just those times? I can try excluding that casting, but it won’t stop the lighting change from causing a detection. At least it won’t show up as a pet if you’re right. I’m dubious it will make a difference. I use the web viewer ( my.wyze.com ) and it’s obvious that Wyze does not put the same effort into it that they put into the phone app. The lighting problem is just one example. When you’re reporting an erroneous detection with the phone, that’s a choice. Not so on the PC. I have to select “none of the above”. And there used to be a way to share and download clips through the web site viewer and they removed that feature. They actually made their crappy software worse! I had to use my phone to grab the clip below…

Web app "Web Connection Failed" — camera never sends SDP_ANSWER over KVS WebRTC (captured the signaling)

Two of my cameras won’t load in the web app at my.wyze.com and show “Web Connection Failed.” Both stream fine in the mobile app. Rather than guess, I captured the WebRTC signaling from the browser side, and the result is specific enough that I think it’s worth posting — the browser is doing everything correctly and the camera simply never answers. SETUP Cameras that FAIL in the web app: Cam A — model WYZEC1-JZ (Cam v2), firmware 4.9.9.3006 Cam B — model HL_CFL2, firmware 4.53.11.7154 Cameras that WORK, in the same tab, on the same network, at the same moment: Cam C — model HL_CFL2, firmware 4.53.11.7154 Cam D — model WYZE_CAKP2JFUS Cam E — model HL_PAN2 Cam C is the same model and the same firmware as Cam B and works fine, so this isn’t a model or firmware issue. It’s per-device. Browser: Chrome 152 on macOS, tested with a brand new empty profile — no extensions, no cached cookies — to rule out anything on my end. WHAT ACTUALLY HAPPENS The web app streams over AWS Kinesis Video WebRTC. For every camera, the get-streams API call succeeds and returns a valid signaling URL, ICE servers, and auth token — including for the two that fail. The browser then opens the KVS signaling WebSocket (handshake succeeds, HTTP 101), sends a well-formed SDP offer, and gathers a full set of ICE candidates: host, server-reflexive, and TURN relay. All normal. Then nothing comes back. No SDP_ANSWER. The web client waits 15 seconds, closes the signaling socket (close code 1005), retries exactly once,

Firmware update trouble

@Cld If you can, pick one of your cams having the issue and format the SD card using the WYZE app. After the format completes, let it record for at least 10 minutes. When you go to view the video that was recorded, are you still experiencing the jumping time issue?

Wyze app 3.22 - Released 9/16/2026

I received the update twice today. Not sure what that was all about. I use 3 button navigation on my android device, don’t have an air purifier and am not noticing any text cut off. I just own cameras, bulbs, and plugs.

Wyze app 3.22 - Released 9/16/2026

muerte33: This happens on folks using 3-button Navigation on Android 17 And for those of us not using the 3 button navigation, some of the text at the bottom is partially cut off. So it’s definitely a wider layout structural issue.

471 discussões coletadas desde 1 September 2026. Acompanhe este fórum com uma palavra-chave →