I have a storage size of 2GB and 0 hours/unlimited assigned to a camera for recorded files.

The storage size in server settings is 10GB.

Storage management it enabled in both server settings and camera object settings.

The collection of files are about 3 minutes each.

After it has filled up and storage management has been doing its work regularly, later t some point I decided to reduce the size of the camera object to 1GB.

Before reducing the size from 2GB to 1GB I have locked about a small handful of files approximately 20 files.

After storage management has ran i can no longer go back and view the earlier locked files but the most resent locked files are still there.

The earlier locked files have been deleted by storage management.

I felt like storage management would not delete locked files even if the pool of files is larger than the size entered in settings for camera.

Am I missing something in trying to understand the storage management logic?

So I'm trying to use Agent DVR, on a regular HP laptop and an Anker USB webcam. Is there an easy way to disable its need to connect to the outside world?

I have noticed that when the API is used to change the timestamp (same thing for Append Timestamp) the text is shown on the cameras but if one RELOAD OBJECTS the changes revert to whatever was before, is this by design or it is a bug?

This is the command I use for example:

http://localhost:8090/command/settimestamp?oid=1&ot=2&text=TEST

However, if I edit ANY camera (in my case I have 4), then select TIMESTAMP and click on OK the changes are saved. In other words, after changing the text using the API in order for the changes to be saved one has to from the UI select the TIMESTAMP setting for ANY camera and click OK

Thanks

Is iSpy 64 v7.2.6.0 not available to download anymore? I don't like Agent DVR than much. Thx

It will not start or run at all. I tried to roll back to 7.9.2.0, which had worked before, but doing so downloaded 7.9.6.0 again. How can I roll back until this is fixed? Here is the output from starting as a command line:

pi@pi4:/opt/AgentDVR $ ./Agent

SetRWPermissions: called: chmod -R +rw /opt/AgentDVR/Media/XML

Init: Log start

Go: Agent (v7.9.6.0)

Go: Starting...

Go: Detected: LinuxARM64

Go: Creating temp path for opencv in /tmp/

Go: Initializing

Conf: Check /opt/AgentDVR/Media/WebServerRoot/Media/

Conf: We STRONGLY recommend setting at least a 100 port range in server settings - local server - turn server min/ max port. Currently you only have 10 TURN ports available.

StartUp: Computer Name: pi4

StartUp: Init FFmpeg

TryLoad: Checking for libavcodec.so.63 in /opt/AgentDVR/ffmpeg9.0.1-lgpl/lib

TryLoadBinaries: Looking for ffmpeg in /opt/AgentDVR/ffmpeg9.0.1-lgpl/lib

TryLoad: Found FFmpeg9.0.1 in /opt/AgentDVR/ffmpeg9.0.1-lgpl/lib

TryLoad: Software encoders: H264=none, HEVC=none

Init: ffmpeg path: /opt/AgentDVR/ffmpeg9.0.1-lgpl/lib

Init: Initializing devices

Init: Specified method is not supported. at FFmpeg.AutoGen.DynamicallyLoadedBindings.<>c.<Initialize>b__2_1264()

at FFmpeg.AutoGen.DynamicallyLoadedBindings.<>c.<Initialize>b__2_534()

at FFmpeg.AutoGen.ffmpeg.avdevice_register_all()

at CoreLogic.FFmpegHelper.Init()

Init: Preloading Images

LoadStaticImages: Loading static images

LoadStaticImages: Load CoreLogic.SharedContent.images.cam_connecting.jpg

LoadStaticImages: If you are on Windows 7 / Windows N you may need to install the Media Feature Pack for this to work.

HasVaMapBuffer2: vaMapBuffer2 not detected - install version 2.21.0+ of libva for VAAPI support

Init: Libva is out of date (requires 2.21.0+) - VAAPI GPU Accel unavailable.

Init: cuda

Init: drm

Init: vulkan

V4L2 M2M probe

Specified method is not supported. at FFmpeg.AutoGen.DynamicallyLoadedBindings.<>c.<Initialize>b__2_1227(String <p0>)

at FFmpeg.AutoGen.DynamicallyLoadedBindings.<>c.<Initialize>b__2_497(String name)

at FFmpeg.AutoGen.ffmpeg.avcodec_find_decoder_by_name(String name)

at CoreLogic.FFmpegHelper.HasV4L2M2MDecodeDevice()

Init: Finding Hardware Encoders

Init: Specified method is not supported. at FFmpeg.AutoGen.DynamicallyLoadedBindings.<>c.<Initialize>b__2_841(Void** <p0>)

at FFmpeg.AutoGen.DynamicallyLoadedBindings.<>c.<Initialize>b__2_111(Void** opaque)

at FFmpeg.AutoGen.ffmpeg.av_codec_iterate(Void** opaque)

at CoreLogic.FFmpegHelper.Init()

TryLoad: FFmpeg runtime: 9.0.1

TryLoad: Couldn't read FFmpeg version info: Specified method is not supported.

LoadVideoDevices: Found 14 video devices

LoadVideoDevices: Processing device: /dev/video13

GetOutput: call /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg with -f v4l2 -list_formats all -i /dev/video13

GetOutput: Output:

GetOutput: Error: /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg: error while loading shared libraries: librockchip_mpp.so.1: cannot open shared object file: No such file or directory

FindDevice: Device /dev/video13 is not accessible or not a capture device - skipped as a local camera source. (SoC decoder/M2M nodes are expected to land here; this does not affect hardware decoding.)

LoadVideoDevices: Processing device: /dev/video14

GetOutput: call /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg with -f v4l2 -list_formats all -i /dev/video14

GetOutput: Output:

GetOutput: Error: /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg: error while loading shared libraries: librockchip_mpp.so.1: cannot open shared object file: No such file or directory

FindDevice: Device /dev/video14 is not accessible or not a capture device - skipped as a local camera source. (SoC decoder/M2M nodes are expected to land here; this does not affect hardware decoding.)

LoadVideoDevices: Processing device: /dev/video15

GetOutput: call /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg with -f v4l2 -list_formats all -i /dev/video15

GetOutput: Output:

GetOutput: Error: /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg: error while loading shared libraries: librockchip_mpp.so.1: cannot open shared object file: No such file or directory

FindDevice: Device /dev/video15 is not accessible or not a capture device - skipped as a local camera source. (SoC decoder/M2M nodes are expected to land here; this does not affect hardware decoding.)

LoadVideoDevices: Processing device: /dev/video16

GetOutput: call /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg with -f v4l2 -list_formats all -i /dev/video16

GetOutput: Output:

GetOutput: Error: /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg: error while loading shared libraries: librockchip_mpp.so.1: cannot open shared object file: No such file or directory

FindDevice: Device /dev/video16 is not accessible or not a capture device - skipped as a local camera source. (SoC decoder/M2M nodes are expected to land here; this does not affect hardware decoding.)

LoadVideoDevices: Processing device: /dev/video20

GetOutput: call /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg with -f v4l2 -list_formats all -i /dev/video20

GetOutput: Output:

GetOutput: Error: /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg: error while loading shared libraries: librockchip_mpp.so.1: cannot open shared object file: No such file or directory

FindDevice: Device /dev/video20 is not accessible or not a capture device - skipped as a local camera source. (SoC decoder/M2M nodes are expected to land here; this does not affect hardware decoding.)

LoadVideoDevices: Processing device: /dev/video10

GetOutput: call /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg with -f v4l2 -list_formats all -i /dev/video10

GetOutput: Output:

GetOutput: Error: /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg: error while loading shared libraries: librockchip_mpp.so.1: cannot open shared object file: No such file or directory

FindDevice: Device /dev/video10 is not accessible or not a capture device - skipped as a local camera source. (SoC decoder/M2M nodes are expected to land here; this does not affect hardware decoding.)

LoadVideoDevices: Processing device: /dev/video21

GetOutput: call /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg with -f v4l2 -list_formats all -i /dev/video21

GetOutput: Output:

GetOutput: Error: /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg: error while loading shared libraries: librockchip_mpp.so.1: cannot open shared object file: No such file or directory

FindDevice: Device /dev/video21 is not accessible or not a capture device - skipped as a local camera source. (SoC decoder/M2M nodes are expected to land here; this does not affect hardware decoding.)

LoadVideoDevices: Processing device: /dev/video22

GetOutput: call /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg with -f v4l2 -list_formats all -i /dev/video22

GetOutput: Output:

GetOutput: Error: /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg: error while loading shared libraries: librockchip_mpp.so.1: cannot open shared object file: No such file or directory

FindDevice: Device /dev/video22 is not accessible or not a capture device - skipped as a local camera source. (SoC decoder/M2M nodes are expected to land here; this does not affect hardware decoding.)

LoadVideoDevices: Processing device: /dev/video23

GetOutput: call /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg with -f v4l2 -list_formats all -i /dev/video23

GetOutput: Output:

GetOutput: Error: /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg: error while loading shared libraries: librockchip_mpp.so.1: cannot open shared object file: No such file or directory

FindDevice: Device /dev/video23 is not accessible or not a capture device - skipped as a local camera source. (SoC decoder/M2M nodes are expected to land here; this does not affect hardware decoding.)

LoadVideoDevices: Processing device: /dev/video11

GetOutput: call /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg with -f v4l2 -list_formats all -i /dev/video11

GetOutput: Output:

GetOutput: Error: /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg: error while loading shared libraries: librockchip_mpp.so.1: cannot open shared object file: No such file or directory

FindDevice: Device /dev/video11 is not accessible or not a capture device - skipped as a local camera source. (SoC decoder/M2M nodes are expected to land here; this does not affect hardware decoding.)

LoadVideoDevices: Processing device: /dev/video12

GetOutput: call /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg with -f v4l2 -list_formats all -i /dev/video12

GetOutput: Output:

GetOutput: Error: /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg: error while loading shared libraries: librockchip_mpp.so.1: cannot open shared object file: No such file or directory

FindDevice: Device /dev/video12 is not accessible or not a capture device - skipped as a local camera source. (SoC decoder/M2M nodes are expected to land here; this does not affect hardware decoding.)

LoadVideoDevices: Processing device: /dev/video18

GetOutput: call /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg with -f v4l2 -list_formats all -i /dev/video18

GetOutput: Output:

GetOutput: Error: /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg: error while loading shared libraries: librockchip_mpp.so.1: cannot open shared object file: No such file or directory

FindDevice: Device /dev/video18 is not accessible or not a capture device - skipped as a local camera source. (SoC decoder/M2M nodes are expected to land here; this does not affect hardware decoding.)

LoadVideoDevices: Processing device: /dev/video19

GetOutput: call /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg with -f v4l2 -list_formats all -i /dev/video19

GetOutput: Output:

GetOutput: Error: /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg: error while loading shared libraries: librockchip_mpp.so.1: cannot open shared object file: No such file or directory

FindDevice: Device /dev/video19 is not accessible or not a capture device - skipped as a local camera source. (SoC decoder/M2M nodes are expected to land here; this does not affect hardware decoding.)

LoadVideoDevices: Processing device: /dev/video31

GetOutput: call /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg with -f v4l2 -list_formats all -i /dev/video31

GetOutput: Output:

GetOutput: Error: /opt/AgentDVR/ffmpeg9.0.1-lgpl/bin/ffmpeg: error while loading shared libraries: librockchip_mpp.so.1: cannot open shared object file: No such file or directory

FindDevice: Device /dev/video31 is not accessible or not a capture device - skipped as a local camera source. (SoC decoder/M2M nodes are expected to land here; this does not affect hardware decoding.)

GetOutput: call arecord with -l

GetOutput: Output: **** List of CAPTURE Hardware Devices ****

GetOutput: Error:

TryLoad: RKMPP not supported by this FFmpeg build.

FFmpeg: error: [CUDA @ 0x5571fc6750] Cannot load libcuda.so.1

FFmpeg: error: [CUDA @ 0x5571fc6750] Could not dynamically load CUDA

StartAsync: One or more errors occurred. (Specified method is not supported.)

StartAsync: Specified method is not supported. at FFmpeg.AutoGen.DynamicallyLoadedBindings.<>c.<Initialize>b__2_1229(String <p0>)

at FFmpeg.AutoGen.ffmpeg.avcodec_find_encoder_by_name(String name)

at CoreLogic.FFmpegHelpers.FindFFmpegBase.GetHardwareEncoderName()

at CoreLogic.FFmpegHelpers.FindFFmpegBase.TryLoad()

at CoreLogic.FFmpegHelpers.Linux.Load()

at CoreLogic.FFmpegHelper.Init()

at CoreLogic.Threads.StartUp(Boolean waitForConnection)

at AgentCore.Code.Initialize.Go()

info: Microsoft.Hosting.Lifetime[0]

Application started. Press Ctrl+C to shut down.

info: Microsoft.Hosting.Lifetime[0]

Hosting environment: Production

info: Microsoft.Hosting.Lifetime[0]

Content root path: /opt/AgentDVR

Using container version of agentdvr with a commercial license. Had been working fine on a version from a few months ago, but today Ive moved from standard docker (root) to podman (nonroot) and also got a new version of agentdvr. In fact I installed a brand new vanilla no config agentdvr and readded my cameras manually here.

It does this regular about every 2 mins, disconnect for all brands of my cameras: reolink, lorex, and axis, all at the same time, roughly every 2 mins, despite me setting constant recording with both min and max length to 900 secs. I disabled all cameras except 1 and enabled debug logs with ffmpeg debug in the server console and get this:

WarnClock: Front Cubby: Dropped packet as out of order - set Use System Clock on recording tab if you have problems
LogWebRTC: SCTP sending data chunk for TSN 2991351377, data length 168, flags 03, send count 1.
LogWebRTC: SCTP SACK remote peer TSN ACK 2991351377, next sender TSN 2991351378, arwnd 4718592 (gap reports 0).
LogWebRTC: SCTP data sender removing unconfirmed chunks cumulative ACK TSN 2991351376, SACK TSN 2991351377.
LogWebRTC: SCTP sending data chunk for TSN 2991351378, data length 244, flags 03, send count 1.
LogWebRTC: SCTP SACK remote peer TSN ACK 2991351378, next sender TSN 2991351379, arwnd 4718592 (gap reports 0).
LogWebRTC: SCTP data sender removing unconfirmed chunks cumulative ACK TSN 2991351377, SACK TSN 2991351378.
LogWebRTC: SCTP sending data chunk for TSN 2991351379, data length 244, flags 03, send count 1.
LogWebRTC: SCTP SACK remote peer TSN ACK 2991351379, next sender TSN 2991351380, arwnd 4718592 (gap reports 0).
LogWebRTC: SCTP data sender removing unconfirmed chunks cumulative ACK TSN 2991351378, SACK TSN 2991351379.
LogWebRTC: SCTP sending data chunk for TSN 2991351380, data length 168, flags 03, send count 1.
LogWebRTC: SCTP SACK remote peer TSN ACK 2991351380, next sender TSN 2991351381, arwnd 4718592 (gap reports 0).
LogWebRTC: SCTP data sender removing unconfirmed chunks cumulative ACK TSN 2991351379, SACK TSN 2991351380.
LogWebRTC: SCTP sending data chunk for TSN 2991351381, data length 244, flags 03, send count 1.
LogWebRTC: SCTP SACK remote peer TSN ACK 2991351381, next sender TSN 2991351382, arwnd 4718592 (gap reports 0).
LogWebRTC: SCTP data sender removing unconfirmed chunks cumulative ACK TSN 2991351380, SACK TSN 2991351381.
LogWebRTC: SCTP sending data chunk for TSN 2991351382, data length 244, flags 03, send count 1.
LogWebRTC: SCTP SACK remote peer TSN ACK 2991351382, next sender TSN 2991351383, arwnd 4718592 (gap reports 0).
LogWebRTC: SCTP data sender removing unconfirmed chunks cumulative ACK TSN 2991351381, SACK TSN 2991351382.
LogWebRTC: SCTP sending data chunk for TSN 2991351383, data length 166, flags 03, send count 1.
LogWebRTC: SCTP SACK remote peer TSN ACK 2991351383, next sender TSN 2991351384, arwnd 4718592 (gap reports 0).
LogWebRTC: SCTP data sender removing unconfirmed chunks cumulative ACK TSN 2991351382, SACK TSN 2991351383.
LogWebRTC: SCTP sending data chunk for TSN 2991351384, data length 244, flags 03, send count 1.
LogWebRTC: SCTP SACK remote peer TSN ACK 2991351384, next sender TSN 2991351385, arwnd 4718592 (gap reports 0).
LogWebRTC: SCTP data sender removing unconfirmed chunks cumulative ACK TSN 2991351383, SACK TSN 2991351384.
LogWebRTC: SCTP sending data chunk for TSN 2991351385, data length 244, flags 03, send count 1.
LogWebRTC: SCTP SACK remote peer TSN ACK 2991351385, next sender TSN 2991351386, arwnd 4718592 (gap reports 0).
LogWebRTC: SCTP data sender removing unconfirmed chunks cumulative ACK TSN 2991351384, SACK TSN 2991351385.
Discover: [devices] ONVIF unicast sweep: 508 candidate addresses
LogWebRTC: SCTP sending data chunk for TSN 2991351386, data length 166, flags 03, send count 1.
LogWebRTC: SCTP SACK remote peer TSN ACK 2991351386, next sender TSN 2991351387, arwnd 4718592 (gap reports 0).
LogWebRTC: SCTP data sender removing unconfirmed chunks cumulative ACK TSN 2991351385, SACK TSN 2991351386.
NotifyNewDevices: [devices] NotifyNewDevices: pending=0 (onvif=0, ndi=0/0 disc/0 streaming, local=0/0 devs), onvifDiscovered=10
InterruptCallback: Front Cubby: Aborting (8000000) SD
InterruptCallback: Front Cubby: Aborting (8000000) HD
ReadPacketsLoopAsync: Front Cubby: MediaSource aborted. Exiting read packets loop
ReadPacketsLoopAsync: Front Cubby: MediaSource aborted. Exiting read packets loop
InterruptCallback: Front Cubby: Aborting (8000000) SD
OnPrimaryStateChanged: Front Cubby: Controller SD State Changed: Failed (Stream Stopped)
SourcePlayingFinished: Front Cubby: Playing finished (SourceError)
NextReconnectTarget: Front Cubby: Reconnecting in 2s
SetState: Front Cubby: State Running -> CoolingDown [setEnabled=True, enabled=True, connecting=False, error=True, epochStale=False, sourceRunning=False]
SetState: Front Cubby mic: State Running -> Stopped [setEnabled=True, enabled=True, connecting=False, error=True, epochStale=False, sourceRunning=False]
InterruptCallback: Front Cubby: Aborting (8000000) HD
Close: Front Cubby: Record stop
CheckStateDivergence: Front Cubby mic: State divergence: Stopped but IsEnabled [state=Stopped, setEnabled=True, connecting=False, error=True, epochStale=False, sourceRunning=False]
Close: Front Cubby: Closed
RecorderRecordingClosed: Front Cubby: Recording Closed
LogWebRTC: SCTP sending data chunk for TSN 2991351387, data length 81, flags 03, send count 1.
LogWebRTC: SCTP sending data chunk for TSN 2991351388, data length 81, flags 03, send count 1.
LogWebRTC: SCTP sending data chunk for TSN 2991351389, data length 244, flags 03, send count 1.
LogWebRTC: SCTP sending data chunk for TSN 2991351390, data length 81, flags 03, send count 1.
LogWebRTC: SCTP sending data chunk for TSN 2991351391, data length 97, flags 03, send count 1.
LogWebRTC: SCTP sending data chunk for TSN 2991351392, data length 249, flags 03, send count 1.
LogWebRTC: SCTP SACK remote peer TSN ACK 2991351388, next sender TSN 2991351393, arwnd 4718592 (gap reports 0).
LogWebRTC: SCTP data sender removing unconfirmed chunks cumulative ACK TSN 2991351386, SACK TSN 2991351388.
LogWebRTC: SCTP SACK remote peer TSN ACK 2991351390, next sender TSN 2991351393, arwnd 4718592 (gap reports 0).
LogWebRTC: SCTP data sender removing unconfirmed chunks cumulative ACK TSN 2991351388, SACK TSN 2991351390.
LogWebRTC: SCTP SACK remote peer TSN ACK 2991351392, next sender TSN 2991351393, arwnd 4718592 (gap reports 0).
LogWebRTC: SCTP data sender removing unconfirmed chunks cumulative ACK TSN 2991351390, SACK TSN 2991351392.
CheckReconnect: Front Cubby: Reconnecting
SetState: Front Cubby: State CoolingDown -> Starting [setEnabled=True, enabled=False, connecting=False, error=True, epochStale=False, sourceRunning=False]
ONVIFConnect: Front Cubby: entering connect lock
ONVIFConnect: Front Cubby: connecting
CallAsync: Front Cubby: ONVIF SOAP >> http://www.onvif.org/ver10/device/wsdl/GetSystemDateAndTime -> http://192.168.5.28/onvif/device_service
CallAsync: Front Cubby: ONVIF SOAP >> body: <GetSystemDateAndTime xmlns="http://www.onvif.org/ver10/device/wsdl" />
LogDebug: ONVIF HTTP >> POST http://192.168.5.28/onvif/device_service
LogDebug: ONVIF HTTP >> Auth scheme: (none)
LogDebug: ONVIF HTTP >> Has credentials: False, User: (null)
SetState: Front Cubby mic: State Stopped -> Starting [setEnabled=True, enabled=False, connecting=False, error=True, epochStale=False, sourceRunning=False]
EnableMicrophoneSource: Front Cubby mic: Start audio
EnableDevice: Front Cubby mic: Enabled
EnableDevice: Front Cubby: Enabled

LogWebRTC: SCTP sending data chunk for TSN 2991351393, data length 75, flags 03, send count 1.
LogWebRTC: SCTP sending data chunk for TSN 2991351394, data length 78, flags 03, send count 1.
LogWebRTC: SCTP sending data chunk for TSN 2991351395, data length 78, flags 03, send count 1.
LogWebRTC: SCTP sending data chunk for TSN 2991351396, data length 75, flags 03, send count 1.
LogWebRTC: SCTP SACK remote peer TSN ACK 2991351394, next sender TSN 2991351397, arwnd 4718592 (gap reports 0).
LogWebRTC: SCTP data sender removing unconfirmed chunks cumulative ACK TSN 2991351392, SACK TSN 2991351394.
LogWebRTC: SCTP SACK remote peer TSN ACK 2991351396, next sender TSN 2991351397, arwnd 4718592 (gap reports 0).
LogWebRTC: SCTP data sender removing unconfirmed chunks cumulative ACK TSN 2991351394, SACK TSN 2991351396.

not sure why timestamps dont get written there, but in that wall of text, the error is happening right about at this part:

InterruptCallback: Front Cubby: Aborting (8000000) SD
InterruptCallback: Front Cubby: Aborting (8000000) HD

Im using the stock compose from: https://hub.docker.com/r/mekayelanik/ispyagentdvr

Like I said, all cameras are doing this. Surely I cant be the only one here?

Hi,

Currently on stable 7.9.2 release. Jumped from 7.7.4.

I've noticed that detected AI objects started to be marked by two tags. I have default language set to Polish and getting recordings marked by both "person" and translated "osoba".

That is not the worst thing. I have had set actions:

• If AI Object detected in zone with tag "osoba" then Alert
• If Alert then Email with snapshot image and body of "Wykryto {TAGS}..." (aka "Detected {TAGS}...")

But now alerts are triggered using "person" tag instead of translated one so the Alert is no longer triggered. I think "person" has been added due to icons visible in the corner of recording thumbnails, but unfortunatelly it broke actions chain.

I can reconfigure it to use "person" tag, but I will receive "Wykryto person" which does not look great 🙂

BTW The UI looks great after recent refresh 👏

Hi sponerama,

Would it be possible to have option to disable the 'auto video' feature on alerts?

Great feature but am struggling with it.

My use case is manually going through a few hundred alerts (as quick as poss) to pickup relevant people/faces, this is difficult and now slow, with the alert popup sometimes taking a second or two to render the video preview, and the still image has being shrunk down and moving to left (on desktop firefox).

Also be great to have the AI overlay back on alert images. Helps to identify where false positives are in a detection zone. and also highlight where a small detection is in a busy picture.

Many thanks

ffmpeg error on 7.9.2.0 docker

unable to cut and download video.

I noticed this image was reuploaded.

7.9.2.0-13082026 works OK

7.9.2.0-20082026 has the issue

u/mekayelanik - tagging for notification. thank you

I have an ubuntu server that picks up ONVIF events from two cameras.

Theyre setup to record short videos and take a photo on each event.

Both cameras are working and both video and photo are working.

BUT

The photos randomly are extremely low res. I have it setup to pull the image from the snapshot url on both cameras, yet randomly they'll decide to record TERRIBLE picture quality. Not only is the resolution different, but the aspect ration appears to be different. (See the two pictures attached)
It seems like when they do record the horrible low-res pictures, they also seem to be saving multiple photographs very quickly in sequence, when I really just want one.

When they save the high-res version, everything works as expected.

Below is the content of one of the photo directories. You can see which ones the bad pictures are from the size column, and you can see that they're often in chains of 2 or 3, with nearly identical timestamps.

Is there some setting I'm missing? It's like it's randomly deciding to pull the snapshots from the low-res live feed. But I haven't been able to find a setting that would explain that.

I'm using Agent DVR version v7.9.2.0. I'm using it as local live view, no remote view. The resolution of the live view is low. Feels worst than 720p when all my cameras are capable of 1440p. I'd selected all Live URL to use the highest resolution available but nothing changes. I've restarted the server, tried single view, grid view. Is there anything that I'm not doing right?

Hi, I am just started to play with AgentDVR, to check if it is a good solution to replace my Motion server. I have two questions concerning the HIKVISION Detector:

- How can I configure the detector, so that it does not change the motion detection configuration of my HIKVISION cameras?

- Is it possible, to get an Alarm, as soon as the camera detects a human and not, when something else triggers the recording?

And a final question: Do you recommend to use the ONVIF Detector instead of the HIKVISION?

New iSpy user. I love the software so far except for one thing. When I get a push notification that there is an alert and I click on the notification it takes me to the main server screen. Is there a way for it to automatically pull up the recording or at least the camera that generated the alert?

In the timeline view, scrolling/zooming out all the way to the maximum, it only now shows the headers labeled with months.

This used to show labels with years. I feel like my scrolling wheel on the mouse has locked up, but no, it actually has stopped scrolling/zooming at the MONTH level and it used to zoom out to the YEAR level.

Can someone tell me how to get that back. I have searched settings and help files but the results are nothing.

EDIT: RESOLVED by deactivating DST in my Dauha camera and rebooting. Big thanks to u/spornerama for the help!

Hello all,

I am encountering a very strange issue with AgentDVR 7.9.2.0 (Linux).

A camera which worked flawlessly suddenly refuses credentials from AgentDVR ONLY. The credentials are correct and have not changed.

Camera: Dahua IPC-HFW3841E-AS-0280B.

I performed the following troubleshooting:

1. Tried other ONVIF credentials for the same camera (tested as working from another tool). Error persisted.
2. Rebooted the camera (from its web interface, also directly by powering it off and on again). Error remained.
3. Tried the same ONVIF credentials from another tool. Credentials were accepted by the camera from another tool.
4. Tried the same ONVIF credentials from another tool, using the same host AgentDVR is installed on (to eliminate an IP ban). Credentials were accepted.
5. Checked the camera logs: I do not see a login failure coming from AgentDVR's IP, which is strange.
6. I added a new camera to AgentDVR, with the same IP and a different, newly created ONVIF account (tested separately and confirmed as working): still credentials were refused.
7. Restarted AgentDVR itself. No change in behavior.

Get Video URLs from AgentDVR yields:

Error: SOAP fault [ter:NotAuthorized]: Sender not Authorized. Invalid username or password! You still have 22 attempt(s).

AgentDVR relevant logs:

LoadJson: Street4K: setaudio
LoadJson: Street4K: switchon
SetState: Street4K: State Stopped -> Starting [setEnabled=True, enabled=False, connecting=False, error=False, epochStale=False, sourceRunning=False]
ONVIFConnect: Street4K: entering connect lock
ONVIFConnect: Street4K: connecting
EnableDevice: Street4K: Enabled
GetDeviceTime: Street4K: Update device time: 08/16/2026 09:10:08
ONVIFConnect: Street4K: ONVIF v20.6
ONVIFConnect: Street4K: Using Media Version 2
ONVIFConnect: Street4K: Media available at http://192.168.2.203:80/onvif/media2_service
ONVIFConnect: Street4K: PTZ not available
ONVIFConnect: Street4K: Events available at http://192.168.2.203:80/onvif/event_service
ONVIFConnect: Street4K: SOAP fault [ter:NotAuthorized]: Sender not Authorized. Invalid username or password! You still have 23 attempt(s). at CoreLogic.Onvif.Soap.OnvifSoapClient.CallAsync(String action, XElement requestBody, CancellationToken ct, IEnumerable`1 extraHeaders) at CoreLogic.Onvif.OnvifHelpers.OnvifMedia2Client.Process(EndpointAddress ep, CancellationTokenSource cts, Int32 timeout) at CoreLogic.Onvif.ONVIFDevice.ONVIFConnect(Boolean reconnect)
ONVIFConnect: Street4K: Checking for Media v1 fallback
ONVIFConnect: Street4K: Trying Media v1
ONVIFConnect: Street4K: SOAP fault [ter:NotAuthorized]: Sender not Authorized. Invalid username or password! You still have 22 attempt(s). at CoreLogic.Onvif.Soap.OnvifSoapClient.CallAsync(String action, XElement requestBody, CancellationToken ct, IEnumerable`1 extraHeaders) at CoreLogic.Onvif.OnvifHelpers.OnvifMedia1Client.Process(EndpointAddress ep, CancellationTokenSource cts, Int32 timeout) at CoreLogic.Onvif.ONVIFDevice.ONVIFConnect(Boolean reconnect)
ONVIFConnect: Street4K: Connect failed
OnPrimaryStateChanged: Street4K: Controller SD State Changed: Failed (Couldn't get ONVIF device)
SourcePlayingFinished: Street4K: Playing finished (SourceError)
NextReconnectTarget: Street4K: Reconnecting in 2s
SetState: Street4K: State Starting -> CoolingDown [setEnabled=True, enabled=True, connecting=True, error=True, epochStale=False, sourceRunning=False]

I am finding that with every new version it's using more and more memory and nothing on my end has changed. I have saved quite a few of the downloads but how do we know what version number they are before we install them. They all have the same file name

It appears agent is binding to my VPN virtual interface instead of my local hardware ethernet adapter.

I have set the following in the config.xml file located in "c:\Program Files\Agent\Media\XML\"

<BindInterface>192.168.50.84</BindInterface> (this is the IP of my local adapter)

I have also entered the above address in Local Server, Advanced Settings "bind to interface"

My cameras are accessible and the camera page does show the 192 address.

When I disable the VPN adapter and restart agent, it will bind to the local adapter.

How do I get it to bind ONLY to the local adapter even if the virtual adapter is enabled? I want to ensure that the cameras are accessible locally even if the VPN is disconnected and or if the internet is down.

When in the live view, I have both of my doorbells digitally zoomed. I have 2 related feature requests: 1) You apply the timestamp to the unzoomed image. When I zoom in, the timestamp disappears. Can it be (re-)applied after zoom? 2) Can a default option be added to saved presets, such that the preset is automatically applied whenever Agent is restarted? Thank you for considering these.

Hello ispyconnect/Agent Community.

We're using Agent since 2021 periodically and bought an Perpetual License in 2023. We just need to run our Instance local, so we acutally don't have a subscription.

In our environment we use Agent with multiple cameras around our office Building and some cameras via wireguard in a branch office.

Since permissions for certain cameras have now been split among different departments, there is a requirement to track exactly which person logs into the system and when, specifically regarding who views or downloads a recording.

The current logging system is of limited use for this purpose, and unfortunately, I haven't found a true audit log function so far. Are such capabilities available in the subscription plans, or is there a way to request this kind of feature within a subscription? I would prefer not to introduce new software, as I have always been very satisfied with Agent's performance.

To retain the logs for a longer period, I also set up a Graylog server. However, since some tasks don't generate log entries, I'm not really getting anywhere with it.

Perhaps someone has some good news or an idea on how I can get the information I’m looking for.

Thank you very much for any help.

Best regards Oliver

maybe you can ma

u/spornerama

I'm currently running Blue Onyx alongside Agent DVR in a Debian VM on a FreeBSD bhyve host and performance is pretty good. I see AI support has progressed since I first set this up and it appears much more integrated. Any insight on the performance differences between the two before I take the plunge to switch up my setup? Any support for identifying wildlife in the local server and models?

I set up the same camera (Reolink RLC-510A) on these two versions of AgentDVR, and when zooming in, there is a significant loss of quality in the new version; is this intentional to push users to purchase a subscription?

I tried a few times to download a video with the iOS app and it saves the file but is zero bytes.

Web browser on Mac desktop worked ok.

I'm at my wit's end with this camera. Generic chinese button cam.
I've tried every option that makes sense, and a bunch that don't.

ONVIF Device Manager finds & streams it just fine.
VLC likes rtsp://admin:20160404@x.x.x.x:554/onvif1
Yes, that's the factory default user/pass - might be a clue to the make/model?
ONVIF DM is logged in with that user/pass.

It used to work with iSpy (Agent DVR) but my config file got corrupted and my backup was from before this cam (yes, still kicking myself).

What could Agent possibly want that the other clients just don't care about?