BUG: short recording times and lots of disconnects #1333
Comments
|
hmm, not sure why it's doing multiple connections to the same cam, but that is probably what is causing the disconnects since the 2024 firmwares are limiting the number of connections and is probably what is causing the Can you do a btw, |
|
@tabooki could you try dev build to see if that works better? |
|
I removed those parts of the file and restarted with the compose. It's been
running for 2 hours so far. Will update later with logs if anything
happens.
…On Wed, Aug 28, 2024, 9:15 AM mrlt8 ***@***.***> wrote:
@tabooki <https://github.com/tabooki> could you try dev build to see if
that works better?
—
Reply to this email directly, view it on GitHub
<#1333 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHKN6NTMKBFTYUDQMH6ILNDZTXEO5AVCNFSM6AAAAABNGY23MOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJVGI4DSOJRGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Ran for a couple hours then stops. Not getting the crazy disconnects though. Here's my logs. I'm going to switch to dev right now and will post those logs later. docker logs wyze-bridge ��� DOCKER-WYZE-BRIDGE v2.10.2 X86_64 [WyzeBridge] SET WB_IP to allow WEBRTC connections.
|
|
Over 4 hours running on dev. It's a record for me after trying this for a month. |
|
After ten hours or so it went crazy again. WyzeBridge] ✅ '/cat-cam stream is UP! (3/3) |
|
Restarted and left running over night. Same issues again. ] |
|
The cameras will sometimes struggle with the higher bitrates. Can you try lowering it to something like HD300 and see if it improves stability? I can't work on it right now due to a personal emergency, but I'll try to look into the source of the problem as soon as I can. |
|
Done. Will report back tomorrow. Btw life comes before code. Hope everything works out ok. |
|
Running much better now. Out of curiosity what are the available options similar to the one you posted I'd like to try a few different ones |
|
The app used to use these values: 360p - SD30 |
* Delete old snapshots #1330 * purge old snapshots when taking any snapshot * Tweak RTMP and add RestreamIO #1333 * Increase MTX_WRITEQUEUESIZE for higher bitrates * Fix typo * restart stream on RTMP fail #1333 * Fix restore user data on restart #1334 * Use email from wyze api response directly * Bump previous build to 2.9.12 * Update config.yml * bump previous build * Changelog
Describe the bug
I keep getting disconnects and 10 minute uploads when streaming. Running latest updated today.
Any ideas on what to try?
down
[WyzeBridge] ✅ '/cat-cam stream is UP! (3/3)
[WyzeBridge] ✅ '/cat-cam stream is UP! (3/3)
[WyzeBridge] ❌ '/cat-cam' stream is down
[WyzeBridge] ❌ '/cat-cam' stream is down
[WyzeBridge] ✅ '/cat-cam stream is UP! (3/3)
[WyzeBridge] ❌ '/cat-cam' stream is down
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[WyzeBridge] ✅ '/cat-cam stream is UP! (3/3)
[WyzeBridge] ❌ '/cat-cam' stream is down
[WyzeBridge] ✅ '/cat-cam stream is UP! (3/3)
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[cat-cam] Getting 120kb/s HD stream (H264/20fps) via LAN mode (WiFi: 78%) FW: 4.36.
13.0416
[cat-cam] Custom (rtmp://live.restream.io/live/re_8013929_debXXXdac1b8081f16ec) liv
estream enabled
[cat-cam] WARNING: Skipping wrong frame_size at start of stream [frame_size=1]
[WyzeBridge] ❌ '/cat-cam' stream is down
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[WyzeBridge] ✅ '/cat-cam stream is UP! (3/3)
[WyzeBridge] ❌ '/cat-cam' stream is down
[WyzeBridge] ✅ '/cat-cam stream is UP! (3/3)
[WyzeBridge] ❌ '/cat-cam' stream is down
[WyzeBridge] ✅ '/cat-cam stream is UP! (3/3)
[WyzeBridge] ❌ '/cat-cam' stream is down
[WyzeBridge] ✅ '/cat-cam stream is UP! (3/3)
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[cat-cam] [-48] IOTC_ER_DEVICE_EXCEED_MAX_SESSION
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[cat-cam] [-48] IOTC_ER_DEVICE_EXCEED_MAX_SESSION
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[cat-cam] Getting 120kb/s HD stream (H264/20fps) via LAN mode (WiFi: 73%) FW: 4.36.
13.0416
[cat-cam] Custom (rtmp://live.restream.io/live/re_8013929_debd7XXXc1b8081f16ec) liv
estream enabled
[cat-cam] WARNING: Skipping wrong frame_size at start of stream [frame_size=1]
[WyzeBridge] ✅ '/cat-cam stream is UP! (3/3)
[WyzeBridge] ❌ '/cat-cam' stream is down
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[cat-cam] [-48] IOTC_ER_DEVICE_EXCEED_MAX_SESSION
[WyzeBridge] ❌ '/cat-cam' stream is down
[WyzeBridge] ✅ '/cat-cam stream is UP! (3/3)
[WyzeBridge] ❌ '/cat-cam' stream is down
[WyzeBridge] ✅ '/cat-cam stream is UP! (3/3)
[WyzeBridge] ❌ '/cat-cam' stream is down
[WyzeBridge] ✅ '/cat-cam stream is UP! (3/3)
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[cat-cam] [-48] IOTC_ER_DEVICE_EXCEED_MAX_SESSION
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[cat-cam] [-48] IOTC_ER_DEVICE_EXCEED_MAX_SESSION
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[cat-cam] [-48] IOTC_ER_DEVICE_EXCEED_MAX_SESSION
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[cat-cam] [-48] IOTC_ER_DEVICE_EXCEED_MAX_SESSION
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[cat-cam] [-48] IOTC_ER_DEVICE_EXCEED_MAX_SESSION
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[cat-cam] [-48] IOTC_ER_DEVICE_EXCEED_MAX_SESSION
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[cat-cam] [-48] IOTC_ER_DEVICE_EXCEED_MAX_SESSION
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[cat-cam] [-48] IOTC_ER_DEVICE_EXCEED_MAX_SESSION
[WyzeBridge] Connecting to WyzeCam V3 - Cat Cam on 10.0.0.159
[cat-cam] Getting 120kb/s HD stream (H264/20fps) via LAN mode (WiFi: 50%) FW: 4.36.
13.0416
[cat-cam] Custom (rtmp://live.restream.io/live/re_8013929_debdXxxac1b8081f16ec) liv
estream enabled
Affected Bridge Version
V2.10.2
Bridge type
Docker Run/Compose
Affected Camera(s)
No response
Affected Camera Firmware
No response
docker-compose or config (if applicable)
The text was updated successfully, but these errors were encountered: