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

Help Fix bitrate and super slow errors #1194

Open
airbornetrooper82573 opened this issue May 13, 2024 · 12 comments
Open

Help Fix bitrate and super slow errors #1194

airbornetrooper82573 opened this issue May 13, 2024 · 12 comments

Comments

@airbornetrooper82573
Copy link

airbornetrooper82573 commented May 13, 2024

I have 2 V4 cams and 1 v3. I'm getting these errors now and I'm not sure how to fix them. I can't seem to load the feeds on my iPhone anymore either.

My compose:

version: '2.4'
services:
wyze-bridge:
container_name: wyze-bridge
network_mode: host
restart: unless-stopped
image: mrlt8/wyze-bridge:latest
ports:
- 1935:1935 # RTMP
- 8554:8554 # RTSP
- 8888:8888 # HLS
- 8889:8889 #WebRTC
- 8189:8189/udp # WebRTC/ICE
- 5000:5000 # WEB-UI
environment:
# [OPTIONAL] (Can be set in the WebUI):
- WYZE_EMAIL=myemail
- WYZE_PASSWORD=mypass
- API_ID=my api ID
- API_KEY=my api key
# [OPTIONAL] IP Address of the host to enable WebRTC e.g.,:
- WB_IP=192.168.1.50
- ON_DEMAND=False
- IGNORE_OFFLINE=true
- FPS_FIX=true
- IGNORE_RES

My errors:
[WyzeBridge] 192.168.1.102 - - [13/May/2024 17:08:44] "GET /signaling/front-porch-cam?webrtc HTTP/1.1" 200 - [front-porch-cam] 📡 Getting 180kb/s 2K stream (H264/20fps) via LAN mode (WiFi: 23%) FW: 4.52.3.9455 🔒 [front-porch-cam] Re-encoding audio for compatibility with WebRTC in MTX [front-porch-cam] 🔊 Audio Enabled - AAC_ELD > LIBOPUS/16,000Hz [front-porch-cam] WARNING: Skipping wrong frame_size at start of stream [frame_size=1] [front-porch-cam] [video] super slow [front-porch-cam] WARNING: clear buffer [back-yard-cam] bitrate=108 does not match 180 [back-yard-cam] Requesting frame_size=0, bitrate=180, fps=0 [front-porch-cam] [video] super slow [back-yard-cam] bitrate=108 does not match 180 [back-yard-cam] Requesting frame_size=0, bitrate=180, fps=0 [front-porch-cam] [video] super slow [WyzeBridge] ✅ '/front-porch-cam stream is UP! (3/3) [WyzeBridge] 📖 New client reading from front-porch-cam [front-porch-cam] [video] super slow [back-yard-cam] bitrate=108 does not match 180 [back-yard-cam] Requesting frame_size=0, bitrate=180, fps=0 [WyzeBridge] 📕 Client stopped reading from front-porch-cam [front-porch-cam] WARNING: Audio pipe closed [front-porch-cam] Stream stopped [WyzeBridge] ❌ '/front-porch-cam' stream is down [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Front Porch Cam on 192.168.10.166 [WyzeBridge] ❌ '/front-porch-cam' stream is down [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Front Porch Cam on 192.168.10.166 [front-porch-cam] 📡 Getting 180kb/s 2K stream (H264/20fps) via LAN mode (WiFi: 25%) FW: 4.52.3.9455 🔒 [front-porch-cam] [Exception] Unable to identify audio. [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Front Porch Cam on 192.168.10.166 [front-porch-cam] 📡 Getting 180kb/s 2K stream (H264/20fps) via LAN mode (WiFi: 24%) FW: 4.52.3.9455 🔒 [front-porch-cam] [Exception] Unable to identify audio. [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Front Porch Cam on 192.168.10.166 [back-yard-cam] bitrate=108 does not match 180 [back-yard-cam] Requesting frame_size=0, bitrate=180, fps=0 [front-porch-cam] 📡 Getting 180kb/s 2K stream (H264/20fps) via LAN mode (WiFi: 23%) FW: 4.52.3.9455 🔒 [front-porch-cam] [Exception] Unable to identify audio. [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Front Porch Cam on 192.168.10.166 [back-yard-cam] bitrate=108 does not match 180 [back-yard-cam] Requesting frame_size=0, bitrate=180, fps=0 [front-porch-cam] 📡 Getting 180kb/s 2K stream (H264/20fps) via LAN mode (WiFi: 21%) FW: 4.52.3.9455 🔒 [front-porch-cam] Re-encoding audio for compatibility with WebRTC in MTX [front-porch-cam] 🔊 Audio Enabled - AAC_ELD > LIBOPUS/16,000Hz [front-porch-cam] WARNING: Skipping wrong frame_size at start of stream [frame_size=1] [back-yard-cam] bitrate=108 does not match 180 [back-yard-cam] Requesting frame_size=0, bitrate=180, fps=0 [front-porch-cam] WARNING: Still waiting for first frame. Updating frame size. [front-porch-cam] Requesting frame_size=3, bitrate=180, fps=0 [front-porch-cam] WARNING: Audio pipe closed [front-porch-cam] [Exception] Did not receive a frame for 20s [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Front Porch Cam on 192.168.10.166 [back-yard-cam] bitrate=108 does not match 180 [back-yard-cam] Requesting frame_size=0, bitrate=180, fps=0 [front-porch-cam] 📡 Getting 180kb/s 2K stream (H264/20fps) via LAN mode (WiFi: 25%) FW: 4.52.3.9455 🔒 [front-porch-cam] Re-encoding audio for compatibility with WebRTC in MTX [front-porch-cam] 🔊 Audio Enabled - AAC_ELD > LIBOPUS/16,000Hz [front-porch-cam] WARNING: Skipping wrong frame_size at start of stream [frame_size=1] [front-porch-cam] [video] super slow [front-porch-cam] WARNING: clear buffer [WyzeBridge] ✅ '/front-porch-cam stream is UP! (3/3) [WyzeBridge] 📖 New client reading from front-porch-cam [back-yard-cam] bitrate=108 does not match 180 [back-yard-cam] Requesting frame_size=0, bitrate=180, fps=0 [front-porch-cam] WARNING: Audio pipe closed [front-porch-cam] Stream stopped [back-yard-cam] bitrate=108 does not match 180 [back-yard-cam] Requesting frame_size=0, bitrate=180, fps=0 [WyzeBridge] ❌ '/front-porch-cam' stream is down [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Front Porch Cam on 192.168.10.166 [WyzeBridge] 📕 Client stopped reading from front-porch-cam [WyzeBridge] ❌ '/front-porch-cam' stream is down [WyzeBridge] 🎉 Connecting to WyzeCam V4 - Front Porch Cam on 192.168.10.166 [front-porch-cam] 📡 Getting 180kb/s 2K stream (H264/20fps) via LAN mode (WiFi: 25%) FW: 4.52.3.9455 🔒 [front-porch-cam] Re-encoding audio for compatibility with WebRTC in MTX [front-porch-cam] 🔊 Audio Enabled - AAC_ELD > LIBOPUS/16,000Hz [front-porch-cam] WARNING: Skipping wrong frame_size at start of stream [frame_size=1] [WyzeBridge] ✅ '/front-porch-cam stream is UP! (3/3) [WyzeBridge] 📖 New client reading from front-porch-cam [back-yard-cam] bitrate=108 does not match 180 [back-yard-cam] Requesting frame_size=0, bitrate=180, fps=0 [front-porch-cam] WARNING: clear buffer [back-yard-cam] bitrate=108 does not match 180 [back-yard-cam] Requesting frame_size=0, bitrate=180, fps=0

@airbornetrooper82573 airbornetrooper82573 changed the title Help Fix bitrate and slow errors Help Fix bitrate and super slow errors May 13, 2024
@mrlt8
Copy link
Owner

mrlt8 commented May 14, 2024

Can you try the latest dev build to see if that helps with the stability of the streams?

mrlt8 added a commit that referenced this issue May 14, 2024
@airbornetrooper82573
Copy link
Author

airbornetrooper82573 commented May 14, 2024

I switched to dev and same thing. Still getting bitrate does not match and super slow errors. I can't even get streams to play on the bridge web GUI and definitely not Home app. I did change the rtsp url to rtsp://wb:thekeythatisdisplayedatthebottomofthebridgegui@192.168.1.215:8554/driveway-v4

@airbornetrooper82573
Copy link
Author

I figured out the web gui part, I had my truenas server's IP as the WB_IP. I can see the feeds on WB gui fine now. Still can't get it to show up in Scrypted or Home app.

@mrlt8
Copy link
Owner

mrlt8 commented May 14, 2024

hmm, what kind of cam is back-yard-cam? I'm not sure where bitrate=108 is coming from...

FYI, the bridge will generate a random API key on startup if you don't define one or it doesn't find one in the local directory.
You can either set WB_AUTH=False if you keep everything local, or manually set the WB_API key:

environment:
...
    - WB_API=MyCustomAPIKey

or volume mount the token directory:

environment:
...
volumes:
      - /path/to/store/tokens/on/host:/tokens

and it will reuse the same data on subsequent starts.

@airbornetrooper82573
Copy link
Author

I added the custom key. In scrypted, I'm leaving user/pass blank and putting in rtsp://wb:mycustomkey@192.168.1.215:8554/driveway-v4 and still no snapshot or anything.

The back-yard-cam is a v3.

@mrlt8
Copy link
Owner

mrlt8 commented May 14, 2024

can you open rtsp://wb:mycustomkey@192.168.1.215:8554/driveway-v4 in another media player like VLC?

@airbornetrooper82573
Copy link
Author

It's not loading in VLC

@mrlt8
Copy link
Owner

mrlt8 commented May 14, 2024

What about just rtsp://192.168.1.215:8554/driveway-v4? VLC should prompt for some credentials if auth is enabled.

@airbornetrooper82573
Copy link
Author

I got both ways to work in VLC. I think my phone changed rtsp to rtps and I did't catch it.

In scrypted do I put in wb for username and my api as password and put the plain RTSP stream URL in?

@mrlt8
Copy link
Owner

mrlt8 commented May 14, 2024

I would try the plain RTSP url with the credentials in the fields since it has that option and will make it easier to maintain in the future.

@airbornetrooper82573
Copy link
Author

I did that for all 3 cameras and still not working on scrypted or Home.

[Back Yard Cam] rebroadcast error Error: rtsp socket closed
at Socket. (/@scrypted/prebuffer-mixin/main.nodejs.js:1:140295)
at Socket.emit (node:events:519:28)
at Socket.emit (node:domain:488:12)
at TCP. (node:net:338:12)
[Front Porch Cam] rebroadcast error Error: rtsp socket closed
at Socket. (/@scrypted/prebuffer-mixin/main.nodejs.js:1:140295)
at Socket.emit (node:events:519:28)
at Socket.emit (node:domain:488:12)
at TCP. (node:net:338:12)
[Driveway v4] rebroadcast error Error: rtsp socket closed
at Socket. (/@scrypted/prebuffer-mixin/main.nodejs.js:1:140295)
at Socket.emit (node:events:519:28)
at Socket.emit (node:domain:488:12)
at TCP. (node:net:338:12)

@airbornetrooper82573
Copy link
Author

I can only get the RTSP feed to work in Scrypted if I set WB_AUTH=False

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

2 participants