Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: Wyze App can't connect for "View Live Stream" or "View Playback" when WyzeBridge is running #1411

Open
puterboy opened this issue Jan 23, 2025 · 8 comments
Labels
bug Something isn't working

Comments

@puterboy
Copy link

Describe the bug

I have 2 WyzeCam v3 cameras.
Both the standard WyzeCam mobile app (for Android) and WyzeBridge separately work fine.
However, if I have WyzeBridge already running, then the WyzeCam mobile app doesn't work properly.

Specifically.

  • I can still see live streams from the mobile app home page (but only from there -- not when I click on an individual camera) as well as from the web streaming page
  • I cannot initiate live or playback streams from the "View Livestream" or "View Playback" buttons respectively on any individual cam -- the app tries to connect "securely" three times and then gives up saying "connection failed"
  • The mobile app otherwise is able to connect to the cameras to change settings, reboot them, upgrade firmware, etc. -- just the streaming functionality is affected

Note that ff WyzeBridge is not running the "View Livestream" and "View Playback" work fine.
Also, ff WyzeBridge is started while running "View Livestream" or"View Playback", then the current stream continues to play fine (and WyzeBridge works fine); however, any new live or playback stream will fail to connect

In summary, it seems that having WyzeBridge connected, prevents the mobile app from connecting properly to the Wyze cameras.
However, conversely the mobile app streaming doesn't seem to prevent WyzeBridge from connecting.

Is this a known issue?
Are there any workarounds or potential fixes? (other than avoiding running WyzeBridge and the mobile app simultaneously)

Affected Bridge Version

v2.10.3 X86_64

Bridge type

Docker Run/Compose

Affected Camera(s)

WyzeCam v3

Affected Camera Firmware

4.36.13.0416 (and at least other recent firmware)

docker-compose or config (if applicable)

@puterboy puterboy added the bug Something isn't working label Jan 23, 2025
@kriodoxis
Copy link

kriodoxis commented Jan 26, 2025

Same here, I have 2 cameras and only one is affected, if I stop the container, log in to the app, stream and then start the bridge, the camera works for a while.

@vfadool
Copy link

vfadool commented Feb 13, 2025

Not sure whats wrong with mine but I have 10 cameras and only 4 will show in a "live" view where the others are black. In snapshot mode all the cameras have snapshots from 1-5 days ago. I deleted and reinstalled the bridge, but still get the same results. My WYZE app works fine, all 10 cameras show live views and all connected. The App works while the bridge is up no problem. Rebooted server, and still issues with not getting current snapshots or live views on all cameras. So to net it out.. in snapshot view, ALL snapshots are old, and wont refresh despite trying to turn off/on, enable, start, etc... In Video view, this will not work at all if you click on camera. will only show some cameras live, not all (it varies with each selection of video while auto-play is on), the others remain black. I wish it would work, because all my other cameras are Ring and my Security is Ring and thats working great.

@Deach01
Copy link
Contributor

Deach01 commented Feb 13, 2025

There has to be something specific to your environment that’s causing this.
It’s working fine here with 7 cams.

Is the network saturating?
2.4GHz isn’t wide bandwidth and if the signal strength is low and it’s trying to do multiple streams it can get nasty.
Also if you have the Wyze bridge on the same network as the cams (you should) then set Allowed Net Mode to LAN. If, for some reason, you’re linking via the internet, it may not be able to handle two streams.

Remember that if you are trying to watch the cam on the same network, you are doubling the bandwidth needed. The cam sends to Wyze Bridge, then Wyze Bridge sends to your viewer.

I do have problems with one particular Wyze V3 cam that drops off line in WyzeBridge at random and needs reboot from Wyze app to recover. It IS a weaker signal but I have another V3 in high signal strength, V4 cams and CamPan V3’s that are rock solid.
I suspect that the Wyze V3’s are not that good at recovering from network issues. They were always a bit temperamental. The V4’s are a better, more stable cam overall (imo), but they need more bandwidth for the higher resolution.

If you show us your yaml file (take out the security info) maybe there’s a setting that’s making it fail.
Maybe try turning On Demand on (or off) and see if that makes a difference.

@vfadool
Copy link

vfadool commented Feb 13, 2025

OK, I did some research and did 2 things helped me figure this out.. first off, I switched from Safari to Brave and guess what? Significant improvement and also was able to figure out that the cameras causing me trouble are the WV0D1 Models. The V3's are working much better. Second, HLS works great, WebRTC not so much.. spinning. When in safari, they are both the slow same spinning.

Also, Safari doesnt display the up/down arrows next to the number of camera feeds per row at the top of the screen. Brave shows that. In Safari I have to enter a number to increase the views per row.

Also in Brave, the snapshot viewer works when I click on a view. I am just amazed at the difference. I'll look at my settings to see if there is anything in safari that is inhibiting internal traffic/communication with the cameras. Since it loads and some work and others dont, im not sure how much affect that will have. I KNOW Brave is a much faster browser.

Also meant to add that in an iPad the chevrons (carets) are also missing at the top in both the App and WebUI. On MacOS, they are there in the MacOS App but not the WebUI.

Another Bug I noticed is that when you are on an IPAD and try to change the Video drop down at the bottom to select Autoplay, it triggers the button and refreshes the screen, never allowing you to enter the dropdown menu and change to HLS or WebRTC, or Autoplay. When you hit the down arrow it thinks you are hitting the button to refresh the screen

@cheme75
Copy link

cheme75 commented Feb 13, 2025

FWIW, I'm kind of an old school guy and use Firefox as a sort of updated Netscape. Just a comfortable way it works with customizations that best work for me. I only use safari in iOS part time for some basic browsing, but I use Firefox for the wyzebridge, homebridge and scrypted. Anyway, have not had any issues. All displays and control in web ui seem to behave well.

@vfadool
Copy link

vfadool commented Feb 13, 2025

FWIW, I'm kind of an old school guy and use Firefox as a sort of updated Netscape. Just a comfortable way it works with customizations that best work for me. I only use safari in iOS part time for some basic browsing, but I use Firefox for the wyzebridge, homebridge and scrypted. Anyway, have not had any issues. All displays and control in web ui seem to behave well.

im old school too! Me and buddy at work were testing (playing with) this thing called mosaic/netscape that allowed us to connect online to a local university. I worked for a software company called Legent at the time as a consultant..

@cheme75
Copy link

cheme75 commented Feb 13, 2025

Haha, ya, recall mosaic way back in my early net days. That's when things actually worked on a 9600 baud dialup connection - never could get up to 14.4 with the crappy pots lines we had at home until 56k modems arrived and I kept calling the telco support to fix our lines. Finally got a new run from pole at street to our house and I ran new interior wire to my modem. The good ole days!

@vfadool
Copy link

vfadool commented Feb 13, 2025

Haha, ya, recall mosaic way back in my early net days. That's when things actually worked on a 9600 baud dialup connection - never could get up to 14.4 with the crappy pots lines we had at home until 56k modems arrived and I kept calling the telco support to fix our lines. Finally got a new run from pole at street to our house and I ran new interior wire to my modem. The good ole days!

yep, I remember the 300 baud where you put the phone handle in the cups.. I was one of the first ones at our company to log on to the mainframe from home.. and yes, the 56K seemed like light speed ! let the good times roll!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants