-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[Support]: Delay/lag with Amcrest IP4M-1051 #2379
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
hmm it appears I have the same issue ... but I I`m feeding my home assistant with .jpg from frigate in order to do rooom presence with double-take ... In the logs bellow it Maybe some settings ? it was working before .. Logs bellow .. [2022-01-10 10:23:07] frigate.object_processing WARNING : Unable to create jpg because frame 1641810184.543911 is not in the cache [2022-01-10 10:23:09] ws4py INFO : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:44914] [2022-01-10 10:23:09] ws4py INFO : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:44936] [2022-01-10 10:23:09] frigate.object_processing WARNING : Unable to create jpg because frame 1641810184.543911 is not in the cache [2022-01-10 10:23:09] frigate.object_processing WARNING : Unable to save snapshot for 1641810179.330937-iq7iv4. [2022-01-10 10:23:09] frigate.object_processing WARNING : Unable to create clean png because frame 1641810184.543911 is not in the cache [2022-01-10 10:23:09] frigate.object_processing WARNING : Unable to save clean snapshot for 1641810179.330937-iq7iv4. [2022-01-10 10:23:09] frigate.object_processing WARNING : Unable to create jpg because frame 1641810184.543911 is not in the cache [2022-01-10 10:23:10] frigate.object_processing WARNING : Unable to create jpg because frame 1641810184.543911 is not in the cache [2022-01-10 10:23:10] frigate.object_processing WARNING : Unable to send mqtt snapshot for 1641810179.330937-iq7iv4. [2022-01-10 10:23:13] ws4py INFO : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:44936] [2022-01-10 10:23:14] ws4py INFO : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:44950] [2022-01-10 10:23:16] ws4py INFO : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:44950] [2022-01-10 10:23:16] frigate.object_processing WARNING : Unable to create jpg because frame 1641810184.543911 is not in the cache [2022-01-10 10:23:16] frigate.object_processing WARNING : Unable to send mqtt snapshot for 1641810179.330937-iq7iv4. [2022-01-10 10:23:16] ws4py INFO : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:44958] [2022-01-10 10:23:23] ws4py INFO : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:44958] [2022-01-10 10:23:23] ws4py INFO : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:44994] [2022-01-10 10:23:38] frigate.object_processing WARNING : Unable to create jpg because frame 1641810213.936492 is not in the cache [2022-01-10 10:24:31] frigate.object_processing WARNING : Unable to create jpg because frame 1641810184.543911 is not in the cache |
My problem is somewhat similar but I have a feeling it's due to decoding. I'm able to get the AD410 into Frigate and the debug shows it processing at 5fps but when I try to view the camera through Frigate or the Home Assistant Frigate Card, it's very delayed (by almost 30 seconds or more) and stuttering. All my other cameras(Wyze Pan, ReoLink RLC520A) seem to do ok and show the same fps in debug. Any suggestions? Oh and I'm running on a RPi4 8gig with a coral usb |
right ... I don`t quite have such issues ... with fps delays ... or at least not 30 seconds .. Is this a wireles camera or wired ? usually all wireless cams are useless and loose lots of fps. |
All of my cams are wireless except the ReoLinks. I have Wyze cams on beta RSTP that don't do this. From looking through the logs it looks to be something with the deciding. I was finally able to get the Raspian OS into true 64 bit mode and update the firmware and kernel. But even with a TPU if I run htop the CPU cores look maxed. Yet it's only using 1.7 gigs of ram. I'm probably going to have to play with the input and output args and hopefully get better results. If not I'll just display that camera through WebRTC and use the Frigate card as a still image and clip review. Was just hoping I could get the live restream from frigate. I've tried but never successfully gotten RTMP working. Everything is storing in a OpenMediaVault NAS share except the frigate DB and config files. With that, DeepStack on a Jetson Nano, and Double Take. It's been working pretty well. Just got to tweek things out which is a pain |
Did anyone get this resolved/figured out? |
Describe the problem you are having
I recently replaced my cameras with an Amcrest AD410 and IP4M-1051. They are the only 2 cameras I have integrated into Home Assistant/Frigate running on a Pi 4 with a Coral USB Accelerator. The live stream from the AD410 seems to be working great, but the IP4M-1051 is constantly refreshing pretty slow, followed by fast forwarding to catch up (ie. 1 second on the cameras built in timestamp takes about 5 seconds). I loaded the rtsp stream in VLC to see if it has the same delay, but it's working perfectly there.
Version
0.9.4-26AE608
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Not sure how to do this. Can provide it if someone can help me out.
Operating system
HassOS
Install method
HassOS Addon
Coral version
USB
Network connection
Wired
Camera make and model
Amcrest IP4M-1051
Any other information that may be helpful
Some info from the camera itself if it helps:
Encode: H264
Resolution: 1920x1080
Framerate: 30
Bitrate: 4096
The text was updated successfully, but these errors were encountered: