-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
2.3.17 - 2.5.0 no connection with V3 #1036
Comments
Can you try going to the WebUI and selecting "restart" -> "clear cache and reconnect"? |
Did that multiple times before & after the update to 2.5.0 |
The bridge seems to be detecting the camera:
Do you get any error messages when trying to open the stream? Can you also try rebooting the camera from the webUI: |
No error messages when opening the stream. No stream either. Reboot command from the webUI worked but after boot completes nothing changes
|
Looks like you're trying to open the webrtc stream? Can you see if you get any error with the RTSP stream in something like VLC? |
Tried various combinations of:
|
That doesn't seem right. Try clicking the RTSP link from the webUI or use this format in VLC:
|
Same situation like you after 2.5 update. [WyzeBridge] 🏠 Home Assistant Mode 🚀 DOCKER-WYZE-BRIDGE v2.5.0
|
Same problem on my side. Can no longer access the cams (v2). I have them connected to Frigate using RTSP stream but they all fail to read. Ffplay test says: rtsp://192.168.28.53:8554/vhod: Server returned 404 Not Found Edit: I have downgraded docker image to mrlt8/wyze-bridge:2.3.17 and they are now both working. So something is wrong with version 2.5.0. Let me know how can I help debug this. |
Same issue here, cameras lost all connection after auto upgrade to 2.5.0 this morning. Reverting to 2.3.17 restored all functionality. |
No change
|
Try Sync the time on the cameras. It worked for my 2xV3, 1xV3 and my Doorbell v1 |
Tried. Restarted the add on & camera as well to be sure. Issue persists |
I'm not seeing this issue with v2.5.0, but will try to look into this. Is everyone having issues using the Home Assistant add-on? Can someone post the logs from the bridge when trying to access the streams to see if there are any errors with the connection to the camera? |
having similar issues on the standalone docker version. all latest tags and dev. |
hmm, I reverted MTX from v1.1.1 back down to v1.1.0 in the dev branch to match what we were using in v2.4.0 of the bridge. |
better on dev image HLS works but loading is taking forever and webrtc is still giving issues |
seems the cams lose connection now and clearing cache+reconnect doesn't bring them back. |
Any errors in the logs? Does rolling back to a previous build of the bridge improve things? |
Same issue. I'll try to fork the repo and apply changes and see if that helps.
I'm assuming TUTK patched their protocol, because Wyze put out a statement saying that they had to force an update because of "security vulnerabilities". |
@UnexDev it looks like the bridge is able to connect to your cam, but something goes wrong while getting the video. Was it connecting in the previous release (v2.4.0) of the bridge? Can you set Wyze did make some changes to their v4.x.11.x firmware that messed up the bitrate info, but it seems like you're still on a really early version |
Same issue. @mrlt8, so far the fix for me is going into the UI, and on each camera, select "enable" for the stream to start. The stream's won't enable automatically for some reason...
|
Working now 👍 |
Updated to 2.5.1. No change for me
Adding in camera info
|
@madjetey Any chance you can run the bridge in docker or on another machine to rule out any local connection issues with HA? |
Well will you look at that. Connected the camera to next door WiFi then installed & ran Docker Wyze Bridge on the bare metal HA setup there. There was a power cut immediately I finished the setup & the jumper cables for the generator were missing BUT After defeating that nonsense, and running the add on IT WORKED.
Camera info from add on
|
UPDATE: ORIGINAL: Woke up to a power cut that lasted 13hrs. Now that things stabilized I rebooted my HA & wifi to discover that it's all working fine. I don't get it.
|
Just got some new v3 cameras and after the obligatory update your firmware several times, simply doing the aforementioned steps made them appear immediately. And to @mrlt8 awesome project, keep up the great work! |
Home Assistant 2023.10.5
Supervisor 2023.10.1
Operating System 11.1
Frontend 20231005.0 - latest
Initially was working fine. Stopped using the camera for 91 days waiting for a replacement USB cable. Updated multiple times to 2.3.17 over the period. Cable comes in & camera works fine with Wyze app but getting no results in Wyze Bridge. Updated to 2.5.0 but same result.
Here's my log:
The text was updated successfully, but these errors were encountered: