Reolink video works in Synology, but motion events are missing
Separate live video from motion event delivery; check detection source, integration profile and Synology codec limits before changing cameras.
Quick answer
Live video alone does not establish that Synology receives the camera’s motion or person events. Check the detection source in Surveillance Station, then the camera profile and recording schedule. Reolink documents its native protocol for AI camera functions; ONVIF video is not proof of those events.
Camera events and Synology detection are different paths
Synology’s Motion settings under IP Camera > Edit > Event Detection let you choose the detection algorithm source. Its H.265 support changes can switch a camera away from motion detection by Surveillance Station when camera detection is available. Reolink’s Synology setup guide advises its Reolink profile for AI functions and visitor alerts; neither instruction proves those features for every model.
Synology: motion event detection settingsWhat a successful diagnosis establishes
A working Synology-generated motion event shows that the chosen Synology detection path works in that setup. It does not prove the camera delivered its own AI event category. Likewise, a camera alert in Reolink App does not prove Synology received it.
Check your setup
- Trigger a controlled event and distinguish a Reolink App notification from an event or recording in Synology. Record the time, model, firmware and selected Synology profile.
- Inspect IP Camera > Edit > Event Detection > Motion and note whether the source is By camera or By Surveillance Station; inspect the recording schedule and notification rules separately.
- If you need camera-side AI or visitor events, check the exact Reolink model in Synology’s support list and try the documented native profile rather than assuming ONVIF transfers every event.
- If a recent Synology update changed detection behavior, check the H.265 changes and the active codec before treating a missing event as a camera fault.
What this does not establish
No model-specific motion-event compatibility is asserted here. If the exact integration and firmware combination has no reviewed evidence, its verdict remains UNKNOWN.
Official references
Documentation checked: 25 September 2026. Confirm current specifications before purchasing.