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

Post 2.6 drops connections #1175

Open
jdeath opened this issue May 4, 2024 · 4 comments
Open

Post 2.6 drops connections #1175

jdeath opened this issue May 4, 2024 · 4 comments

Comments

@jdeath
Copy link

jdeath commented May 4, 2024

All versions post 2.6 have issues for me. Even though "on demand" off, I get lots of drop in/outs of cameras. Frigate is always pulling camera feed, so should not get clients dropping in/out. No change with "on demand" on.

Version 2.6 is much, much better. In 2.8.3 and 2.7, most cameras do not load (or only load intermittently). As soon as stop, and then switch to 2.6 all cameras load instantly.

[WyzeBridge] 📖 New client reading from backyard
[WyzeBridge] 📖 New client reading from front-door
[WyzeBridge] 📕 Client stopped reading from front-door
[WyzeBridge] 📖 New client reading from side-door
[front-door] Requesting frame_size=0, bitrate=120, fps=0
[WyzeBridge] 📖 New client reading from front-door
[WyzeBridge] 📕 Client stopped reading from front-door
[WyzeBridge] 📕 Client stopped reading from side-door
[WyzeBridge] 📖 New client reading from side-door
[WyzeBridge] 📕 Client stopped reading from side-door
[WyzeBridge] 📖 New client reading from side-door
[WyzeBridge] 📕 Client stopped reading from side-door
[WyzeBridge] 📖 New client reading from side-door
[WyzeBridge] 📕 Client stopped reading from side-door
@mrlt8
Copy link
Owner

mrlt8 commented May 4, 2024

Could you try the latest dev builds to see if things have improved?

@jdeath
Copy link
Author

jdeath commented May 4, 2024

DOCKER-WYZE-BRIDGE v2.8.3 X86_64 DEV BUILD [2024-05-04t14:12:39.486z] 8aea9e9

Is working great. Only been on for 5 minutes, but all cameras came up. I'll report back in a couple days if still good. Did you change anything or I just got lucky?

@jdeath jdeath closed this as completed May 13, 2024
@guaycuru
Copy link

guaycuru commented May 13, 2024

I'm still seeing frequent disconnects on v2.9

[sala-de-jantar] [CONTROL] ERROR - error=AssertionError('Please call _connect() first!'), cmd='_bitrate'
[sala-de-jantar] [Exception] Did not receive a frame for 20s
[sala-de-tv] [Exception] Did not receive a frame for 20s

@jdeath
Copy link
Author

jdeath commented May 13, 2024

2.9.0 was definitely less disconnects than 2.8.3, but I switched back to 2.6 too. My HA instance actually crashed pretty regularly using 2.9.0 or the dev build. Thought it was a bad drive. I swapped drives and still got crashes. 2.6 seems stable so sticking with that.

@jdeath jdeath reopened this May 13, 2024
mrlt8 added a commit that referenced this issue May 14, 2024
mrlt8 added a commit that referenced this issue May 16, 2024
mrlt8 added a commit that referenced this issue May 17, 2024
* Tweak AV sync and ffmpeg cmd #1175 #1196 #1194 #1193 #1186

* Catch AccessTokenError

* don't drop timestamp #1175 #1196 #1194 #1193 #1186

* Don't use_wallclock_as_timestamps  #1175 #1196 #1194 #1193 #1186

* keep audio in sync #1175 #1196 #1194 #1193 #1186

* Ignore whitespaces in api key/id #1188

* Remove quotes from credentials #1158

* HA Add FORCE_FPS option #1161

* FORCE_FPS option for all cameras #1161

* changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants