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.

Sign up for GitHub

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

Jump to bottom

Viewing stream in app changes bitrate #929

Open
plat2on1 opened this issue Jul 22, 2023 · 7 comments
Open

Viewing stream in app changes bitrate #929

plat2on1 opened this issue Jul 22, 2023 · 7 comments
Labels
bug Something isn't working

Comments

@plat2on1
Copy link

Viewing a stream in the Wyze app will change the bitrate, perhaps a periodic check to change the bitrate back should be implemented?
@mrlt8
Copy link
Owner

mrlt8 commented Jul 23, 2023

We used to, but the more recent firmware versions actually support multiple streams so it was removed.

I can see if we might be able to add the bitrate check back for older firmware.

@mrlt8 mrlt8 added the enhancement New feature or request label Jul 23, 2023
@plat2on1
Copy link
Author

Hmm. I'm running 40.36.10.4054 on my V3 and when I set the bitrate to 180 and then open the stream on the app, after when I query the API the bitrate is set to 120. Which firmware works differently?

@mrlt8
Copy link
Owner

mrlt8 commented Jul 23, 2023

can confirm the issue. will look into it.

@mrlt8 mrlt8 added bug Something isn't working and removed enhancement New feature or request labels Jul 23, 2023
mrlt8 added a commit that referenced this issue Jul 23, 2023
@mrlt8
Monitor and set preferred bitrate #929
fb88530
mrlt8 added a commit that referenced this issue Jul 24, 2023
@mrlt8
v2.3.12 (#932)
f4c57c4 
* Start from index 1 for cruise_point/waypoint #835

* update_snapshot via MQTT

* fix camera status always online #907 #920

* Additional MQTT entities #921

* QSV related changes

* i965-va-drivers #736

* FIX power status #921

* Fix cruise_point type #921

Thanks @jhansche

* return index from command payload #921

* Update docker-image.yml

* Monitor and set preferred bitrate #929

* Default to `-` for cruise_point #921

* clear out stale entities #921

* changelog
@mrlt8
Copy link
Owner

mrlt8 commented Jul 24, 2023 •
edited

This should be fixed in v2.3.12, and will also try to maintain any bitrate changes made over the MQTT/REST API.

@plat2on1
Copy link
Author

plat2on1 commented Jul 24, 2023 •
edited

Seems to be working but it looks like you have a type error in your check? Logs are being spammed with

[DEBUG][back-yard-cam] Wrong bitrate='200' does not match 200

Also perhaps related, querying the API for bitrate returns this:

{
"command": "bitrate",
"payload": "1,2,3,4,5,21,22,27,50",
"response": "invalid literal for int() with base 10: '1,2,3,4,5,21,22,27,50'",
"status": "error",
"value": null
}

@mrlt8
Copy link
Owner

mrlt8 commented Jul 25, 2023

Thank you! The get and set commands for the bitrate topic seem to be getting mixed up. Will try to get this patched.

mrlt8 added a commit that referenced this issue Jul 25, 2023
@mrlt8
Fix preferred_bitrate for bitrate topic #929
9f9f050
@mrlt8 mrlt8 mentioned this issue Jul 25, 2023
Merged
mrlt8 added a commit that referenced this issue Jul 25, 2023
@mrlt8
v2.3.13 (#936)
f70840c 
* Fix preferred_bitrate for bitrate topic #929

* prevent exception if empty dictionary payload

* changelog
@mrlt8
Copy link
Owner

mrlt8 commented Jul 25, 2023

I think it should be fixed this time. Thanks again for the feedback!

@mrlt8 mrlt8 mentioned this issue Aug 18, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mrlt8 @plat2on1