CAMNET
Event servers
HTTP
For camera make/models which do not offer EBNT_FAMID as an event by network type, the CAMNET event servers can be used. For more on event servers see System, Connections.

Each camera make uses a different way of setting up an HTTP trigger. The concepts here can be applied to other cameras.

This is how Panasonic cameras let you set up an HTTP trigger using its browser app.

CAMNET server does not use image data sent as part of a trigger. If the camera does not offer sending no image, have it send the smallest size.
[ camnet event servers, sample http setup ]
For this camera, which offers multiple trigger channels, two are generally useful to CAMNET server. One is the usual motion detection channel. The other is the onboard sensor. Sensors are good for event detection because they are not easily fooled -- the false detection rate is low. This example sets up the motion detection event. The TCP event server page in this guide covers another camera, setting up the sensor on that camera.

To set up a trigger, click one of the numbers under the No. column. This example uses trigger 4. Check Enable Image Buffer/Transfer Trigger, and set the drop-down selection to Motion Detection. Click Next.

[ camnet event servers, sample http setup ]
Set the times the trigger is to be active. All the time is good. Fill the other fields as shown in the image below, as a starting point.
[ camnet event servers, sample http setup ]
You do not want the image data transferred to CAMNET server so select No Transfer, Memory Overwrite (or the other No Transfer option -- this memory overwrite mode applies to storing the image on the camera's SD card).

For Send Notification When Triggered, select Send HTTP Notification. Click Next.

[ camnet event servers, sample http setup ]
Set the Host Name to that of CAMNET server. The IP address will do. Set Port No. to the port CAMNET server is running the HTTP event server. The default port CAMNET server uses for the HTTP event server is 4042.

The Login ID and Password are not used. This camera's IP was registered when CAMNET server started the camera, so this camera is already known to CAMNET server. (Sending an HTTP /trigger: event is allowed from any IP; you can use the server System, Server ACL to limit what IP address is allowed to connect to CAMNET server.)

For File Path, the following are recognized. If nothing is recognized, MD window 1 (same as /MD_0) is used. For HTTP event triggers, set the File Path or URI to start with a forward slash (e.g., /MD_7).

      MD_0 to MD_9   : motion window, starting at 0  (motion window 1 to 8 in logs) [MD_8 and MD_9 report same as MD_7]
      MD_            : motion window 1 [same as MD_0]
      AUD_           : audio  (A in logs) [it must include the trailing underscore]
      PIR_           : PIR/sensor  (P in logs)
      EXT1_          : extension event1  (little-x in logs)
      EXT2_          : extension event2  (big-X in logs)          [do not use %5F for the underscore]
      I0_            : digital input 0
      I1_            : digital input 1
      I2_            : digital input 2
      I3_            : digital input 3   (big-X in logs; it shares the same notification bit as EXT2_)