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

2.8.1 version with super slow issue #1167

Closed
34t614t1254y opened this issue May 2, 2024 · 5 comments · Fixed by #1184
Closed

2.8.1 version with super slow issue #1167

34t614t1254y opened this issue May 2, 2024 · 5 comments · Fixed by #1184

Comments

@34t614t1254y
Copy link

Hi there,

I use Wyze Bridge 2.8.1 on Home Assistant. (wyze v3 4.36.11.8391)

It has an issue that the frame has been broken. (or skipped)

The log shows up that the stream is super slow.

It really suddenly happens so can't figure out what's wrong.

Everything is fine when I downgrade the version.

@mrlt8
Copy link
Owner

mrlt8 commented May 2, 2024

The super slow warning can usually be ignored as the bridge is just trying to compensate for the late frames.

Is the actual video showing any significant frame drops?

@34t614t1254y
Copy link
Author

VID_20240502_230007_763.mp4
VID_20240502_230033_979.mp4

The bicycle is by wyze bridge docker and the person is by wyze bridge on Home Assistant.

It's especially serious when the video comes with the night vision.

mrlt8 added a commit that referenced this issue May 4, 2024
mrlt8 added a commit that referenced this issue May 4, 2024
@mrlt8
Copy link
Owner

mrlt8 commented May 8, 2024

@34t614t1254y could you try the dev branch to see if that helps?

@34t614t1254y
Copy link
Author

@34t614t1254y Thank you for your reply.

Just installed DEV version on Home Assistant add-on.

Let you know when there is the same issue again!

@34t614t1254y
Copy link
Author

@mrlt8 I've test it for 2 days and seems like it's been solved.

No idea what you did but thanks!

@mrlt8 mrlt8 linked a pull request May 12, 2024 that will close this issue
mrlt8 added a commit that referenced this issue May 12, 2024
* Sign motion event request #1125

* use device id instead of mac #1125

* remove wrong flags from mkfifo #1174

* less aggressive flush #1159 #1167

* Use K10052 for setting FPS #1161

* Refactor bits for going above 255 for quality

* Revert ffmpeg changes #1159 #1167

* version is obsolete

* default quality to hd180

* Update Wyze iOS App version from v2.44.5.3 to v2.50.6.1 (#1176)

* use struct pack

* Token based auth over the webUI

* Fix redirect for Home Assistant Ingress

* Use request headers to fix redirect for HA

* Change GET to POST for webhooks data

* Deprecate ifttt_webhook in favor of webhooks

* use yml for HA config and make credentials optional

* keep trying to identify audio #1172

* Snapshot on motion and push to mqtt #709 #970

* Add event time to motion message

* refactor auth

* EVENT_API option #1125

* Add additional headers  #1125

* Audio sync with higher bitrate

* Debug api request #1125

* Update api.py

* only debug on error

* Tweak audio sync

* don't raise error on lost frame

* clear buffer if out of sync

* Unique macs only #1125

Co-Authored-By: Cameron <32912464+kiwi-cam@users.noreply.github.com>

* Require auth by default and block non-ingress access #1181

* Allow non-ingress access with auth #1181

* Remove retain flag from commands #1182

* update webrtc to work with auth streams

* Add WB_API and rename WEB to WB #1181

WEB_USERNAME > WB_USERNAME
WEB_PASSWORD > WB_PASSWORD

* HA move /config/wyze-bridge/ to /config/

* Don't notify substream event and remove v2 #1125

* WebUI Auth related config for HA

* Don't retain discovery message? #1182

* Case sensitive credentials for WebUI

* changelog and readme

---------

Co-authored-by: Cameron <32912464+kiwi-cam@users.noreply.github.com>
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

Successfully merging a pull request may close this issue.

2 participants