Closed kksligh closed 12 months ago
Rtsp is recommended for go2rtc and only using tapo for two way talk.
How would I only use Tapo for 2-way talk?
go2rtc:
streams:
Camera_1_Frigate_Tapo: <===== WORKING
- tapo://admin:UPPCASEHASH@172.XX.X.XX
Camera_2_Frigate_Tapo: <===== WORKING
- tapo://admin:UPPCASEHASH@172.XX.X.XX
Camera_3_Frigate_Tapo:
- ffmpeg:rtsp://user:pass@192.168.1.123/stream1
- tapo://admin:UPPCASEHASH@172.XX.X.XX
Thanks - its semi working, however, its still throwing errors....
2023-11-16 04:01:57.330409252 [2023-11-15 22:01:57] frigate.video ERROR : Camera_3_Frigate_Tapo: Unable to read frames from ffmpeg process.
2023-11-16 04:01:57.330433569 [2023-11-15 22:01:57] frigate.video ERROR : Camera_3_Frigate_Tapo: ffmpeg process is not running. exiting capture thread...
2023-11-16 04:02:01.388665239 [2023-11-15 22:02:01] watchdog.Camera_3_Frigate_Tapo ERROR : Ffmpeg process crashed unexpectedly for Camera_3_Frigate_Tapo.
2023-11-16 04:02:01.388719898 [2023-11-15 22:02:01] watchdog.Camera_3_Frigate_Tapo ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2023-11-16 04:02:01.388756743 [2023-11-15 22:02:01] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : [segment @ 0x55599901aa00] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2023-11-16 04:02:01.388783542 [2023-11-15 22:02:01] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : [segment @ 0x55599901aa00] Non-monotonous DTS in output stream 0:0; previous: 0, current: 0; changing to 1. This may result in incorrect timestamps in the output file.
2023-11-16 04:02:01.388804742 [2023-11-15 22:02:01] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : rtsp://127.0.0.1:8554/Camera_3_Frigate_Tapo: Connection timed out
2023-11-16 04:02:01.388824076 [2023-11-15 22:02:01] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : Last message repeated 1 times
2023-11-16 04:02:06.508851080 [2023-11-15 22:02:06] frigate.video ERROR : Camera_3_Frigate_Tapo: Unable to read frames from ffmpeg process.
2023-11-16 04:02:06.508910160 [2023-11-15 22:02:06] frigate.video ERROR : Camera_3_Frigate_Tapo: ffmpeg process is not running. exiting capture thread...
2023-11-16 04:02:11.393695110 [2023-11-15 22:02:11] watchdog.Camera_3_Frigate_Tapo ERROR : Ffmpeg process crashed unexpectedly for Camera_3_Frigate_Tapo.
2023-11-16 04:02:11.393772999 [2023-11-15 22:02:11] watchdog.Camera_3_Frigate_Tapo ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2023-11-16 04:02:11.393836016 [2023-11-15 22:02:11] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : [rtsp @ 0x55580bbab140] Could not find codec parameters for stream 0 (Video: h264, none): unspecified size
2023-11-16 04:02:11.393887585 [2023-11-15 22:02:11] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
2023-11-16 04:02:11.393938744 [2023-11-15 22:02:11] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : Output file #0 does not contain any stream
2023-11-16 04:02:16.512998139 [2023-11-15 22:02:16] frigate.video ERROR : Camera_3_Frigate_Tapo: Unable to read frames from ffmpeg process.
2023-11-16 04:02:16.513101291 [2023-11-15 22:02:16] frigate.video ERROR : Camera_3_Frigate_Tapo: ffmpeg process is not running. exiting capture thread...
2023-11-16 04:02:21.398434240 [2023-11-15 22:02:21] watchdog.Camera_3_Frigate_Tapo ERROR : Ffmpeg process crashed unexpectedly for Camera_3_Frigate_Tapo.
2023-11-16 04:02:21.398493720 [2023-11-15 22:02:21] watchdog.Camera_3_Frigate_Tapo ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2023-11-16 04:02:21.398528907 [2023-11-15 22:02:21] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : [rtsp @ 0x55d611aa5140] Could not find codec parameters for stream 0 (Video: h264, none): unspecified size
2023-11-16 04:02:21.398558390 [2023-11-15 22:02:21] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
2023-11-16 04:02:21.398585129 [2023-11-15 22:02:21] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : Output file #0 does not contain any stream
Still working but constantly throwing these errors - any thoughts?
2023-11-17 20:17:59.270989793 [2023-11-17 14:17:59] watchdog.Camera_3_Frigate_Tapo INFO : No frames received from Camera_3_Frigate_Tapo in 20 seconds. Exiting ffmpeg... 2023-11-17 20:17:59.271274532 [2023-11-17 14:17:59] watchdog.Camera_3_Frigate_Tapo INFO : Waiting for ffmpeg to exit gracefully... 2023-11-17 20:18:03.905079247 [2023-11-17 14:18:03] frigate.video ERROR : Camera_3_Frigate_Tapo: Unable to read frames from ffmpeg process. 2023-11-17 20:18:03.905107682 [2023-11-17 14:18:03] frigate.video ERROR : Camera_3_Frigate_Tapo: ffmpeg process is not running. exiting capture thread... 2023-11-17 20:18:13.907396177 [2023-11-17 14:18:13] watchdog.Camera_3_Frigate_Tapo ERROR : Ffmpeg process crashed unexpectedly for Camera_3_Frigate_Tapo. 2023-11-17 20:18:13.907413325 [2023-11-17 14:18:13] watchdog.Camera_3_Frigate_Tapo ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2023-11-17 20:18:13.907503445 [2023-11-17 14:18:13] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : [segment @ 0x55ebef427080] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly 2023-11-17 20:18:13.907506475 [2023-11-17 14:18:13] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : [segment @ 0x55ebef427080] Non-monotonous DTS in output stream 0:0; previous: 0, current: 0; changing to 1. This may result in incorrect timestamps in the output file. 2023-11-17 20:18:13.907515634 [2023-11-17 14:18:13] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : [segment @ 0x55ebef427080] Non-monotonous DTS in output stream 0:0; previous: 1438, current: 1438; changing to 1439. This may result in incorrect timestamps in the output file. 2023-11-17 20:18:13.907522387 [2023-11-17 14:18:13] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : [segment @ 0x55ebef427080] Non-monotonous DTS in output stream 0:0; previous: 2874, current: 2874; changing to 2875. This may result in incorrect timestamps in the output file. 2023-11-17 20:18:13.907619509 [2023-11-17 14:18:13] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : [segment @ 0x55ebef427080] Non-monotonous DTS in output stream 0:0; previous: 2875, current: 2875; changing to 2876. This may result in incorrect timestamps in the output file. 2023-11-17 20:18:13.907622783 [2023-11-17 14:18:13] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : [segment @ 0x55ebef427080] Non-monotonous DTS in output stream 0:0; previous: 2876, current: 2875; changing to 2877. This may result in incorrect timestamps in the output file. 2023-11-17 20:18:13.907624333 [2023-11-17 14:18:13] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : More than 1000 frames duplicated 2023-11-17 20:18:13.907640211 [2023-11-17 14:18:13] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : rtsp://127.0.0.1:8554/Camera_3_Frigate_Tapo: Connection timed out 2023-11-17 20:18:13.907642456 [2023-11-17 14:18:13] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : [segment @ 0x55ebef427080] Non-monotonous DTS in output stream 0:0; previous: 219425789, current: 219425789; changing to 219425790. This may result in incorrect timestamps in the output file. 2023-11-17 20:18:19.020266761 [2023-11-17 14:18:19] frigate.video ERROR : Camera_3_Frigate_Tapo: Unable to read frames from ffmpeg process. 2023-11-17 20:18:19.020311952 [2023-11-17 14:18:19] frigate.video ERROR : Camera_3_Frigate_Tapo: ffmpeg process is not running. exiting capture thread... 2023-11-17 20:18:23.912058047 [2023-11-17 14:18:23] watchdog.Camera_3_Frigate_Tapo ERROR : Ffmpeg process crashed unexpectedly for Camera_3_Frigate_Tapo. 2023-11-17 20:18:23.912062142 [2023-11-17 14:18:23] watchdog.Camera_3_Frigate_Tapo ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2023-11-17 20:18:23.912063794 [2023-11-17 14:18:23] ffmpeg.Camera_3_Frigate_Tapo.detect ERROR : rtsp://127.0.0.1:8554/Camera_3_Frigate_Tapo: Invalid data found when processing input
looks like frigate is just receiving bad or no data at all from the camera
I have been troubleshooting with TP Link Support for a few days - it was a Camera S/W issue. They just released a new firmware release - Version is 1.0.27 Build 231120 Rel.55235n
it fixes the connection issues.
Also, the username in the TAPO url HASH changes from SHA-256 vs md5 HASH before - this happened recently with firmware updates to models C211 and others. I think it probably warrants some documentation updates if its not there already.
Describe the problem you are having
I have 2 other Tapo Cameras (both are C211s) set up in Frigate and they work well. I purchased a C225 which is extremely similar but with a few extra bells and whistles and it works for a short period and then starts erroring out - eventually crashing.
Can you please look at my set up and logs and give me any pointers?
Version
Frigate v0.12
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
No response
Operating system
HassOS
Install method
HassOS Addon
Coral version
USB
Network connection
Wired
Camera make and model
Tapo C225 Firmware: 1.0.24 Build 230731 Rel.42636n Hardware: 1.0
Any other information that may be helpful
No response