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

TutkError V3-Pan #990

Open
letrain02 opened this issue Sep 7, 2023 · 11 comments
Open

TutkError V3-Pan #990

letrain02 opened this issue Sep 7, 2023 · 11 comments
Labels
bug Something isn't working

Comments

@letrain02
Copy link

seeing a lot of errors with v3 pan cameras. if this is repeat sorry.

[WyzeBridge] 📕 Client stopped reading from pasture
[small-pasture] WARNING: Still waiting for first frame. Updating frame size.
[small-pasture] [CONTROL] ERROR - error=TutkError(-20021), cmd=('param_info', '1,2,3,4,5,6,7,21,22,27,50')
[chickens] bitrate=200 does not match 120
[front-lot] WARNING: Still waiting for first frame. Updating frame size.
[back-lot] WARNING: Still waiting for first frame. Updating frame size.
[chickens] [CONTROL] ERROR - error=TutkError(-20018), cmd=('param_info', '1,2,3,4,5,6,7,21,22,27,50')
[front-lot] [CONTROL] ERROR - error=TutkError(-20010), cmd=('param_info', '1,2,3,4,5,6,7,21,22,27,50')
[chickens] Stream did not receive a frame for over 15s
[front-lot] [-20021] AV_ER_SENDIOCTRL_ALREADY_CALLED
[back-lot] [CONTROL] ERROR - error=TutkError(-20018), cmd=('param_info', '1,2,3,4,5,6,7,21,22,27,50')
@mrlt8 mrlt8 added the bug Something isn't working label Sep 11, 2023
@mrlt8
Copy link
Owner

mrlt8 commented Sep 11, 2023

hmm. Will have to look into this.

@letrain02
Copy link
Author

letrain02 commented Sep 12, 2023 •
edited
Loading

i've made some changes and am using the dev-qsv. and i haven't seen the error for a while. i am seeing

[WyzeBridge] Error parsing event_data='pasture,st'
[WyzeBridge] Error parsing event_data='art,1'

i can't be exactly sure if my change to SD30 fixed anything but i did change to that as bitrate. i did change ondemand=false as i was having inconsitent streaming issues and thought maybe that would help keep a connection going when my grafana dashboard refreshes. fps_fix=true is also being used.

mrlt8 added a commit that referenced this issue Sep 12, 2023
@mrlt8
buffer mtx event data #990
bf1d3e3
@lcoll154
Copy link

Starting to receive the same error

family-room] [CONTROL] ERROR - error=TutkError(-20021), cmd=('param_info', '1,2,3,4,5,6,7,21,22,27,50')
[patio] bitrate=120 does not match 60
Requesting frame_size=0, bitrate=60, fps=0
[WyzeBridge] ❌ '/breezeway-door' stream is down
[breezeway-door] Stream did not receive a frame for over 15s
[patio] [CONTROL] ERROR - error=TutkError(-20018), cmd=('param_info', '1,2,3,4,5,6,7,21,22,27,50')
[patio] Stream did not receive a frame for over 15s
[front-ptz] Stream did not receive a frame for over 15s
[doggo-cam] [CONTROL] ERROR - error=TutkError(-20018), cmd=('param_info', '1,2,3,4,5,6,7,21,22,27,50')
[doggo-cam] Stream did not receive a frame for over 15s
[family-room] [CONTROL] ERROR - error=TutkError(-20021), cmd=('param_info', '1,2,3,4,5,6,7,21,22,27,50')
Error opening output files: Invalid argument
[family-room] Stream did not receive a frame for over 15s
[WyzeBridge] 📕 Client stopped reading from breezeway-door
[WyzeBridge] 📕 Client stopped reading from breezeway-door
[WyzeBridge] 🎉 Connecting to WyzeCam Pan V3 - Family Room
[WyzeBridge] 📕 Client stopped reading from doggo-cam
[WyzeBridge] ❌ '/doggo-cam' stream is down
[WyzeBridge] 📕 Client stopped reading from doggo-cam

@mrlt8 mrlt8 mentioned this issue Sep 23, 2023
Merged
mrlt8 added a commit that referenced this issue Oct 10, 2023
@mrlt8
Motion Events and Audio Fix (#1006)
27fd845 
* audio latency #388

* Motion Events

* Log number of cams from API #974

* Store and reuse s3 thumbnail from events #970

* better error handling

* Increase MTX_WRITEQUEUESIZE #984

* MOTION_START for HA

* limit login attempts

* pass exceptions upstream

* motion images for webhooks/ntfy in header

* REST API motion endpoint

* Additional audio codecs

* keep stream alive if livestream enabled #985

* Catch RuntimeError #994

* assert bitrate value

* refactor av_send_io_ctrl

* Refactor API client and use battery from device_info

* motion_ts endpoint

* use .pipe instead of .wav for audio pipe

* update frame size if not preferred_frame_size

* Exclude battery cams from RTSP snapshots #970

* revert changes

* buffer mtx event data #990

* Match all 11.x or newer firmware #975

* MOTION_WEBHOOKS

* clean

* revert changes

* Media MTX changes

* ffmpeg v6

* Use ffmpeg-for-homebridge in QSV build #736

* remove unneeded packages

* don't return none

* Adjust queue size and compression #388

* Adjust sleep, queue, and fifo for lag

* Catch other HTTPErrors for events

* Revert "Adjust sleep, queue, and fifo for lag"

* Update ffmpeg.py

* Update tutk.py

* adjust thread_queue_size #388

* Add build date time

* Update ffmpeg.py

* Additional queue tweaks and fifo options #388

* Catch RequestException in motion events

* Update MediaMTX version from v1.1.0 to v1.1.1 (#1007) (#1008)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: mrlt8 <mrlt8@users.noreply.github.com>

* Fix ETag header for MediaMTX 1.1.1

* Don't use wallclock  #388

* remove asetpts

* audio #388

* Update ffmpeg.py

* allow wallclock flag in FFMPEG_FLAGS #388

* changelog

* Update .env
@lcoll154
Copy link

ERROR - error=TutkError(-20021), cmd=('param_info', '1,2,3,4,5,6,7,21,22,27,50')

This error is still coming up on the latest build I have. I am runing docker in unraid.
Maybe im missing something that I need to do?

@giggo
Copy link

giggo commented Nov 9, 2023

Same here. Happens randomly with random cameras (v2, v2 Pan, v3).

@lcoll154
Copy link

Just upgraded to the latest version and the issue is now more persistent then it was before. Almost making it unusable now at this point

@letrain02
Copy link
Author

@lcoll154 another unraid user i see. i've been using dev branch and the issue has subsided. playing with bitrate has at times helped any errors or streaming issues. i have a monitor that streams all cameras atleast 18 hours a day. a bitrate of 30 might be a place to start. it may not have anything to do with the error, but after doing that i dont see an error.

unraid: i've been meaning to take over the template as i've added in just about every variable, and ports for webrtc, etc.

@mrlt8
Copy link
Owner

mrlt8 commented Nov 10, 2023

The param_info error can usually be ignored as it's just the error response when the main thread closes the connection to the camera.

Will try to clean up the logging in the next release.

@lcoll154
Copy link

@letrain02
Ok, I will try that.
I do have the bitrates adjusted, some on 30 some on 60 for picture quality.
so for the dev branch I need to change
mrlt8/wyze-bridge:latest to
mrlt8/wyze-bridge:dev
in the repository field in docker
Is that correct?

@lcoll154
Copy link

Seems I have tried everything from dev to latest, even latest-hw since I have a GPU I can use and it still is giving me this error "CONTROL] ERROR - error=TutkError(-20018), cmd=('param_info', '1,2,3,4,5,6,7,21,22,27,50'
and I can't view the cameras that are getting that error on the web gui.
I have tried changing the quality, FIX_FPS, OnDemand, nothing seems to work or gets me a connection to any camera that is getting that error. I have even reset the cameras.

@erikgranlund
Copy link

erikgranlund commented Dec 14, 2023 •
edited
Loading

After updating from 2.3.15 to the latest version (2.6) all my camera streams restart repeatedly with: ERROR - error=TutkError(-20010), cmd=('param_info', '1,2,3,4,5,6,7,21,22,27,50').

This is via Home Assistant Blue / Hardkernel ODROID-N2/N2+ installed via the Home Assistant AddOn Store.

Reverting back to 2.3.15 fixes the issue for me.

5 x Wyze V3 with 4.61.0.3 firmware (RTSP firmware)

All cameras use these options (specified individually):

- CAM_NAME: Cam Name
  SUBSTREAM: true
  CONNECT_TIMEOUT: 5
  MTX_READTIMEOUT: 10s
  FPS_FIX: true

mrlt8 added a commit that referenced this issue Dec 19, 2023
@mrlt8
Don't log failed tutk if stream is down #990
9e66ab5
mrlt8 added a commit that referenced this issue Jan 11, 2024
@mrlt8
sync audio (#1067)
bbacb0f 
* Drop late audio frames to keep sync #388

* show running architecture

* Don't log failed tutk if stream is down #990

* Use valid FPS for sleep #388

* Refactor

* Adjust sleep_interval #388

* Increase sleep time between frames #388

* Set larger buf size #388

* add SLEEP_INTERVAL_FPS #388

* Adjust sleep interval #388

* use genpts #388

* avoid conflicting names with errno module

* refactor _audio_frame_slow

* LOW_LATENCY mode

* show github SHA on dev build

* substream support and more refactoring #388

* div tag for jittery video in Firefox #1025

* Re-encoding audio for WebRTC/MTX

* reduce sleep time for audio thread #388

* Target firefox for jittery video fix in css #1025

* Use K10050GetVideoParam for FW 4.50.4.x #1070

* Use K10006 for newer doorbell #742 and refactor

* Reduce audio pipe flushing #388

* show gap when audio out of sync #388

* don't include ARCH in version

* Update iotc.py

* reset frame_ts on clock sync

* update auth api

* Restructure and cleanup

* remove unneeded files

* update path

* Forget alarm/siren state #953 #1051

* use addon_config for Home Assistant

* Additional refactoring to auth api

* don't skip keyframes #388

* Update ffmpeg.py

* delay audio when ahead #388

* format iotc logging so we know what cam is late

* drop late video frame and speed up audio #388

* Add Floodlight V2

* Set default sample rate for all cams

* Delay audio by 1 second if ahead of video #388

* tweak ffmpeg buffer #388

* Retain MQTT Discovery Message #920

* Update change log

Special thanks to @carlosnasillo!
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
5 participants
@giggo @erikgranlund @letrain02 @mrlt8 @lcoll154