The short answer
Detection, event storage and notification presentation are separate checks. Confirm which notification controls exist in the installed build before concluding that detection failed.
Work through the checks
Match an event entry to the camera, timestamp and any linked local media. An event is metadata; its presence does not guarantee that a complete video clip was saved.
Check event creation separately from in-app banners and Windows notifications. A hidden notification does not establish that detection stopped; verify each layer independently.
Check both computer time and camera time, including time zone and synchronization settings. ONVIF authentication and event ordering can be affected by clock differences.
Change one setting, then repeat the same short test after a controlled app or device restart. Record the error time and whether the problem recurs rather than treating a temporary recovery as a diagnosis.
What to verify
When the issue remains, send support the app version, camera model, firmware, error time and a redacted connection format. Include what changed between a successful and failed test.
Sources and scope
AeoCam is available for Windows. Camera settings below describe protocol preparation, not a certification of a particular camera or a promise of every feature in every app version. Check the installed build and the Microsoft Store listing for current availability.
Vendor documents describe the camera or protocol. No physical-camera compatibility test is claimed here. Menus and capabilities can change with model and firmware.