How it connects
Cameras in. One queue out.
Nexus Connect takes events from whatever is already on the site, through the account or appliance it belongs to, and delivers alarms to the people watching in the format their platform already decodes. Nothing is installed on the customer network unless it is a Nexus appliance, and nothing inbound is ever opened.
Sources
What can feed the alarm queue.
Four classes of source. Each one enrols differently and gives the operator a slightly different picture; the alarm queue treats them all the same.
| Alarms | Clip and snapshot | Live view | Health | |
|---|---|---|---|---|
| Cloud camera accounts (consumer and prosumer cameras, through the manufacturer’s cloud service, with the customer’s own credentials) | ✓ | ✓ | Where the service provides a stream | Battery, signal and connectivity, as the camera reports them |
| Professional cloud video services (connected through the service’s own interface) | ✓ | ✓ | Where the service provides a stream | Connectivity, as the service reports it |
| Nexus NVR (cameras on the site’s local network, behind the appliance) | ✓ | ✓ | On demand, over the appliance’s outbound link | Connectivity; events queued during an outage catch up |
| Nexus Roam (battery LTE camera) | ✓ | ✓ | Not yet | Battery and signal |
Credentials for cloud accounts are encrypted before they are stored and never shown again. Which specific manufacturers are supported is discussed during onboarding, not listed here.
From event to alarm
What the platform adds in between.
- 01
The site’s arming schedule decides
Each site has arming windows per day of the week in its own time zone. An event inside a window becomes an alarm; outside it is recorded and kept, and the operator is not disturbed.
- 02
The event is typed
Motion, person, vehicle, intrusion or line crossing, loitering, tamper, audio, and device health each become a distinct alarm type, so the monitoring platform can prioritise and file them differently.
- 03
The clip and snapshot are attached
The alarm carries a JPEG snapshot the operator sees at once and the MP4 clip behind it. The media travels with the alarm rather than as a link, so nothing expires and nothing on the site has to be reachable from the monitoring centre.
- 04
Delivery is watched
Every delivery is recorded. A camera whose alarms are not getting through shows up on the camera-health page as a delivery problem, not as silence.
Destination
How alarms reach SureView Immix.
Alarms arrive in SureView Immix with the clip and snapshot attached, in the format it decodes natively. Support for further monitoring platforms is planned.
The mechanics
Immix accepts alarms by email on a per-site, per-input basis. Nexus Connect sends each alarm to the address for the site’s S-number and the camera’s input number, with the alarm type as the subject and the standard alarm body Immix decodes without configuration: version, input, event type, a line of context, and the time. The snapshot and the clip ride as attachments, snapshot first.
Device-health events (offline, back online, low battery) can be routed to a separate health input on the same site, with a single alarm type of your choosing, so operators can file them apart from intrusion alarms.
Alarm types sent
- Motion
- MotionDetected
- Person
- PersonDetected
- Vehicle
- VehicleDetected
- Intrusion, line crossing, loitering
- IntruderDetected
- Tamper
- TamperAlarm
- Audio
- SensorAlarm
- Camera offline
- VideoLoss
- Camera back online
- SystemEvent
- Low battery
- Battery Health
Setting a site up
- 01
In the monitoring platform
Create the site and its camera inputs as you would for any email-alarm device, and note the site’s S-number and each input number.
- 02
In Nexus Connect
Create the client organisation and the site, enter the S-number, and set the arming schedule in the site’s time zone.
- 03
Map each camera
Connect the cameras through their account or appliance, then give each one its input number. Optionally give the site a health input for offline and battery events.
- 04
Test
Press “Test alarm” on a camera and watch it arrive on the right input with a snapshot. There is a separate test for the health input. Both tests are labelled as tests in the alarm text and written to the audit trail.
Questions
About connecting things.
Do you install anything on the customer’s network?
Only if the site uses a Nexus NVR, and that appliance connects outbound only. Cloud cameras and professional services are connected through their own accounts; nothing is installed and no port is opened.
Which camera brands work?
We describe sources by class on this site and go through specific manufacturers during onboarding. If a camera reports to a cloud service with an interface we can read, or sits on a local network behind a Nexus NVR, it is a candidate.
Does the alarm email contain a link to live video?
No. The clip and snapshot travel as attachments. Operators open live video from the alarm in the Nexus Connect dashboard, which needs nothing reachable on the site.
What happens to events outside the armed window?
They are recorded with their clip and kept under the site’s retention, and they count in reports. They do not reach the operator.
Can you deliver to a platform other than SureView Immix?
Not today. Support for further monitoring platforms is planned; ask us which one you run.
The dashboard the operators use is described on the platform page; what happens when a camera fails is on the camera health page.
Now in early access.
We are onboarding a limited number of monitoring providers, integrators and multi-site operators ahead of general release. Join the waitlist, or sign in if you are already enrolled.