IP camera| With this function block
images from an IP camera can be transferred to the visualization. The communication with the camera takes place only within the internal network; no port forwarding is required, since the camera is read out by the controller and forwarded to the app over a secure connection. The communication with the camera takes place exclusively via http or https requests. The camera must also support this. If the web interface of the camera has a snapshot function, this can generally be read out as well. Cameras that can only be displayed via a manufacturer's app cannot be connected. Live stream and audio are likewise not possible. |
Inputs |
||
| FG |
Enable |
Optional enable; if the input is
not connected, the block is always enabled. |
| ST |
Snapshot
trigger |
This input takes a snapshot
and optionally sends an email as well. |
| SD | Snapshot reset | Resets the output Number of snapshots. Is controlled by the control element. |
Outputs |
||
| ST |
Status | 0 if the request was successful, otherwise an error code (for support only): positive values are the HTTP error code returned by the camera (e.g. 401 = login rejected, 404 = link not found), negative values indicate connection errors (camera not reachable, timeout or invalid link). |
| SA |
Snapshot
count |
Number of snapshots |
Parameters |
||
| URL
Http |
URL of the snapshot function of the camera. When this URL is called, a still image must be returned. | |
| User |
User name |
|
| Password |
Password |
|
| Timeout |
Maximum wait time for the request in seconds. |
|
| Verify certificate |
Verification of the server certificate for
https connections. Disabled by default, since cameras
mostly use self-signed certificates. |
|
| HTTP header |
Optional. Normally leave empty: cameras that log in with user and password do not need this.
Meant for requests that demand an additional detail, such as an API key on a video recorder or on an
upstream proxy. Example: X-API-KEY: 1234abcd, as expected e.g. by the integration API of UniFi Protect.
Several headers in the format Name: Value;Name2: Value2, so a value must not contain a
semicolon. |
|
| User agent |
Optional. Only needed if the camera answers in the browser but not via the controller.
Example: Mozilla/5.0. Empty: the controller identifies itself with its default
identifier. |
|
| Snapshot |
||
| Trigger |
Trigger for taking a snapshot, for example a motion detector. A still image is stored and can be displayed via the control element. | |
| Ring buffer |
Number of how many images are stored before the oldest is deleted. | |
| Delay |
Delay between trigger and capture. | |
| Mail sending |
||
| Active |
Enable mail sending. With each snapshot trigger an email with the stored image is sent. | |
| Address |
Email address | |
| Subject |
Subject | |
| Text |
Text | |
| File extension |
Extension of the image file, normally png or jpg. The controller itself cannot determine the image type, therefore the extension must be specified manually. | |