#Wyze camera outage 2025-02-21?
1 messages · Page 1 of 1 (latest)
Looks related to discussion https://github.com/mrlt8/docker-wyze-bridge/issues/1429
TL;DR looks like Wyze locked down access to cameras across certain network boundaries. Moving all components onto same LAN seems to mitigate this.
Such a pain in the ass
Appreciate the article though, I've been messing with this thing all morning
Yea, it would be be understandable if they gave notice and a way to customize. It's a reasonable security change for average user but rollout seems to really pinch users like us.
LMK if you need any help with the mitigation. Can do my best to help debug if you need anything.
I wonder if this is a change they plan on sticking with, or something they will push an update to fix.
Seems intentional imo
Ya most likely. Just didn't want to have to dick around with everything and then have them update it and fix it had I waited haha
Hmm.. strange. I moved my HA VM to the same IP Subnet/VLAN that my cameras are on but I'm still getting IOTC ER TIMEOUT
What type of network interface does the VM use? You need to avoid virtual translation and use a host network interface or a bridge interface on the same LAN.
ya its a bridged interface on the same LAN
Can you check logs to confirm the server addresses used? Search for "Running on " to see those lines
Also, confirm camera addresses with log lines "Connecting to "
When it first starts up it says running on all addresses. I had it set to LAN, tried it on any and then back to LAN again and it still says all addresses, not sure if thats normal.. But the Connecting to is the correct IPs for the cams
I'm also using the HA Docker-Wyze-Bridge Add on
I tried setting up a separate docker instance on kali instead of a VM, on the same network, and still not having any luck
Wow, that's a real PITA. I don't know of a way to address for the HA addon so far. The docker instance on kali is running in host mode for sure?
Thats a great question actually, how do I check that?
You can find the container ID and then check docker inspect output like so:
$ docker inspect <container-id> | grep -A5 Networks
"Networks": {
"host": {
"IPAMConfig": null,
"Links": null,
"Aliases": null,
"MacAddress": "",
That host key tells the story. If you see something else it's a different mode.
Woot
@grave marsh are you still stable?
so far so good
Actually seems to be working better than it ever has
I'm getting that error now. I'm on HAOS.
Can I ask what settings you have? Does 2FA have to be on?
@peak spruce if you still need a hand, maybe check out this issue discussion starting about here: https://github.com/mrlt8/docker-wyze-bridge/issues/1432#issuecomment-2676066102
I recently noticed that my Wyze Bridge (v2.10.3) and Frigate servers stopped receiving camera feeds as of 5 PM EST on 2/20/2025. To determine whether the issue stemmed from a network-related proble...