The short answer
Night scenes change contrast, reflections and bitrate. Re-test useful events and false triggers after dark rather than reusing daytime sensitivity as proof.
Work through the checks
Check the camera power supply, PoE budget and link stability. Correlate restarts with infrared lights or other load changes before changing the viewer configuration.
Lower one camera parameter at a time: frame rate, resolution or bitrate. Re-test motion and readable detail; a lower idle bitrate alone does not prove a usable moving image.
Use representative day and night scenes, including empty scenes. Compare missed events and unwanted triggers before changing sensitivity; one successful alert is not a reliability measurement.
If detection regions are available, exclude irrelevant motion such as a road, tree or reflection. Test both activity inside the region and movement just outside its boundary.
What to verify
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.
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.