Use this page to add a device by entering its details yourself, or to connect any device that can send alarms by REST API, e-mail (SMTP) or FTP.
Watch:
Step 1: Open Sites & Cameras. Click Add sites & cameras at the top, or in the site row open Actions > Add device.
Step 2: The form Device details opens. If you started from Add sites & cameras, choose Add a site and camera and enter the name under What should we call this site?, or choose Add a camera to an existing site and select the site under Which site?.
Step 3: Fill in Device name, Device IP or hostname
Step 4: Use case is detected automatically from the device IP, port and brand. It decides if the device is handled as public (Public Camera Setup) or private (Private Camera Setup (Local Agent)).
Step 5: Under Contact information you can enter a contact person, e-mail and phone. All are optional.
Step 6: Click Add device. If you started from Add sites & cameras, the button is Add site & device.
What happens next is the same as in Public Camera Setup for a public device and Private Camera Setup (Local Agent) for a private device. Use the tables there if something goes wrong.
Watch:
Use this for any device or system that can send alarms by HTTP, by e-mail or by FTP upload: cameras of other brands, recorders, video management systems, alarm panels or your own software. The screen calls this Universal device support. GC Surge gives you connection details. You enter them on the device.
Step 1: Open Sites & Cameras. Click Add sites & cameras at the top, or in the site row open Actions > Add device. In the window that opens, click Device sends to us. The window Universal device support opens.
Step 2: The dialog asks How should alarms be sent to GC Surge? Enter a Device name (required). If you started from the site row, Site name is filled in already ("Existing site — this device will be added to …"). If you started from Add sites & cameras, choose the site under Site name.
Step 3: Choose the method your device supports:
Method | Description | Typical use |
|---|---|---|
REST API | Send alarms via HTTP POST (JSON) | Software, video management systems, devices with an HTTP alarm action. |
Email (SMTP) | Device sends alarm emails to an address we provide | Cameras and recorders with "send e-mail on alarm". |
FTP | Device uploads alarm images or files to an FTP server | Cameras with "upload snapshot on alarm". |
Step 4: Click Add Device. The dialog moves to Connection details.
Step 5: Under Connection details, the dialog shows the values for this device. Copy them into the device.
Method | Values shown in the dialog | What to do on the device |
|---|---|---|
REST API | Device ID, API endpoint, API key (hidden; use the show and copy buttons) | Send an HTTP POST with JSON to the endpoint for each alarm. Authenticate with the API key. Include the device ID, an event code and the alarm pictures. |
Email (SMTP) | The mail server settings and the alarm recipient address | Enter them in the e-mail alarm settings. Switch on e-mail with picture for the detection you want. |
FTP | The FTP host, port and folder | Enter them in the FTP upload settings. Switch on picture upload on alarm. |
Example of a REST API alarm
Send one HTTP POST per alarm to the API endpoint. In Setup details of the device this address is shown as Events URL. Put the API key in the Authorization header as a Bearer token. Send the pictures in time order: before the alarm, at the alarm, after the alarm.
POST <API endpoint>
Authorization: Bearer <API key>
Content-Type: application/json
{
"deviceId": "<Device ID>",
"eventCode": "motion.event",
"images": [
{ "type": "base64", "data": "data:image/jpeg;base64,<picture before the alarm>" },
{ "type": "base64", "data": "data:image/jpeg;base64,<picture at the alarm>" },
{ "type": "base64", "data": "data:image/jpeg;base64,<picture after the alarm>" }
]
}GC Surge answers with the status 202 (accepted) when it received the alarm.
Step 6: Answer Have you entered these settings on the device?
Button | Result |
|---|---|
Mark as configured manually | Status Configured manually. It becomes Receiving alarms when the first alarm arrives. |
Skip for now | Status Setup needed. When you have entered the settings, open Sites & Cameras, expand the site, open the device Actions > Setup details and click Mark as configured manually. |
Step 7: Under Forward Alarms (Optional), click Add Forward Alarm if alarms of this device should go to a specific alarm receiver (Alarm Forwarding per Site & Device). Otherwise click Done.
Step 8: Trigger one alarm on the device. The status changes to Receiving alarms and the alarm appears in Recordings.
Symptom | Cause | What to do |
|---|---|---|
Status stays Configured manually, no alarm arrives | The device does not send, or sends to a wrong value. | Compare every value on the device with Setup details. Check outbound internet access of the device. Trigger a test alarm. |
REST: the request is refused as not authorised | The API key is missing or wrong. | Copy the key again with the copy button. Check that there is no space before or after it. |
REST: the request is refused as invalid | The JSON is not valid, or the device ID is missing. | Check the JSON. Send the Device ID exactly as shown. |
REST: the request is accepted but nothing appears in Recordings | The device ID belongs to another device, or the time range in Recordings does not include now. | Check the device ID. Set the time range to Last 24 hours. Look under the right site. |
E-mail: the device reports a send error | Wrong server, port, encryption or login. | Enter all SMTP values exactly as shown. Check the encryption setting. Use the test button of the device. |
E-mail: sending works but no alarm appears | The recipient address is wrong, or the e-mail has no picture. | Use the recipient address from Setup details. Switch on picture attachment. |
FTP: upload fails | Wrong host, port, folder or login, or the firewall blocks FTP. | Enter the values exactly as shown. Allow outbound FTP on the site firewall. Try passive mode on the device. |
Alarms arrive under the wrong device | Details of another device were used. | Enter the details of the right device. |
The status is Setup needed | You chose Skip for now. | Open Actions > Setup details and click Mark as configured manually. |
You think the API key is known to others | The key was shared. | Delete the device and add it again to get new details. Then update the device. |
My camera brand is not on the list. Can I still use it? Yes, if it can send alarms by e-mail, FTP or HTTP. Click Device sends to us when you add it.
Thank you — your feedback goes to the team that owns this page.