Docs menu
Events and notifications
Where events come from
| Source | What |
|---|---|
| ONVIF cameras | Motion detection, tampering, image problems, alarm input/output, the camera’s own object detection, sound alarms |
| GB28181 devices | Alarms reported by the device |
| Rerinku View SDK devices, Rerinku Cam | Motion detection and other events reported by the device |
| AI recognition | People, vehicles and pets recognized on this machine, and recognized faces |
| Local motion detection | Turned on per camera (Device details → Settings → Smart detection → Motion events). Off by default, and not pushed to phones |
Devices going online and offline are not events, but they can be pushed to your phone (see below). Event times are always recorded as the time Rerinku View received the event.
Events page
The Events page in the sidebar lists all events grouped by day, newest at the top. Scroll down to load more:
- You can filter by device and type, or jump to a specific day. Filters are written to the address bar, so you can bookmark them.
- When new events arrive, an N new events button appears at the top. Click it to refresh the list. This way, new events don’t interrupt what you’re looking at.
- Click an event to open its recording clip in a dialog. AI recognition events can show detection boxes. View in playback jumps to that time on the playback page.
- You can delete events. Deleting an event doesn’t delete the recording.
An event’s thumbnail is taken from the recording at the moment of the event when possible, and from a camera snapshot when there’s no recording. Event clips come straight from recordings, so the camera needs recordings (continuous or event recording, see Recording and playback). Without a recording, the clip shows “Recording unavailable”.
To view recognition results by category or by person, use the Recognition page. See AI recognition.
Event settings
Under Settings → General → Events:
| Setting | Default | Notes |
|---|---|---|
| Event duration | 20 seconds | How long an event lasts when the device doesn’t report its end. It’s also the length of event recordings |
| Event retention | 90 days | Older events are cleaned up automatically once a day. Recordings are not affected |
AI recognition events can also use Event interval and Longest event to control how often they fire. See AI recognition.
Phone push notifications
After you install the Rerinku View app on your phone and pair it:
- In the app, allow system notifications under Settings → Notifications → Alert notifications. The phone is then registered with the current Rerinku View.
- Manage it in the console under Settings → Notifications → Phone push. The Push notifications master switch is on by default. For each phone, you can choose which categories to push (People, Vehicles, Pets, Recognized people, Camera alarms, Camera offline; all selected by default) and which cameras. You can also Send test.
What a notification looks like: the title is the camera name, and the body is written in the phone’s language, for example “Person and Vehicle detected”, “Recognized: Alex” or “Camera went offline”. On Android, notifications include a screenshot of the event.
- The same content from the same camera is pushed at most once a minute. Notifications expire after 5 minutes. A camera must stay offline for 2 minutes before an offline notification is pushed.
- Pushes reach your phone through the relay at rerinku.com. No account is needed, and Quick Connect doesn’t need to be on, but Rerinku View needs internet access. Screenshots don’t go through the relay: after the phone receives a notification, it fetches the image from Rerinku View itself. See Remote access.
The console itself has no browser system notifications. Open pages refresh automatically over a live connection. To send events to other systems, use MQTT publishing.