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.
Who it is for: Admins who set up sites and devices, and the technician or site contact who helps on site.
Watch:
Add sites manually opens a dialog with two tabs.
Add One 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.
Add Multiple Devices
This tab uploads a device sheet for the site. Importing many devices at once is coming soon. Until then, add devices one at a time.
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: How should alarms be sent to GC Surge?
Method | Description on screen | 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 2: 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. 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.
Then 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. Open the device from Sites & Cameras when you have entered the settings. |
Step 3: 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.
Test it
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. Use Configure the device yourself.
Thank you — your feedback goes to the team that owns this page.