Block camera| This block fetches still images and snapshots from a camera and provides the video stream for the control Block camera. The video runs via the controller or directly from the device to the camera; this is selected on the control. |
Inputs |
||
| FG | Enable | Optional. 0 blocks the camera: there is no image, a running video is ended and the tile shows that the camera is blocked. Not 0 enables it. Not connected: the camera counts as enabled. |
| ST | Snapshot trigger | Optional. Takes a snapshot. Evaluated is the edge set under "Trigger". Not connected: snapshots only via the button on the control. |
| SR | Snapshot reset | Optional. Not 0 sets the counter of new snapshots to 0, the images remain. Not connected: the counter is only reset via the control. |
Outputs |
||
| ST | Status | Result of the last still image request: 0 = OK, greater than 0 = HTTP code of the camera (e.g. 401 = login failed), less than 0 = no connection or invalid URL. |
| SA | Snapshot count | Number of new snapshots, at most as many as the ring buffer holds. |
Parameters |
||
| Still image URL | Optional. Address at which the camera delivers a single image, http or https; an MJPEG address also works, the first image is then taken each time. Empty: with an MJPEG stream, the still image and snapshots come from the stream. With RTSP, MPEG-TS and HLS there is then neither a still image nor snapshots, the snapshot button disappears. Certificates are not checked, so self-generated camera certificates work. | |
| User, password | Credentials of the camera, they apply to still image and stream. Basic and Digest are supported. | |
| Timeout | Waiting time for the camera in seconds. | |
| HTTP header, user agent | Optional. Normally leave empty: cameras that log in with user and password need neither. The
fields are meant for requests that demand an additional detail, such as an API key on a video recorder or on an
upstream proxy. HTTP header 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 example: Mozilla/5.0, only if the camera answers in the browser but not via the
controller. Empty: the controller identifies itself with its default identifier.Both apply to the still image, snapshots and MJPEG via the controller. RTSP, MPEG-TS and direct access from the device do not send them. |
|
| Video | ||
| Stream URL | Optional. Address of the video stream as seen from the controller, e.g.
rtsp://192.168.1.50/Streaming/Channels/102. Empty: the control only shows the still image, unless a direct
URL is entered there. For mobile devices and VPN, the substream of the camera is recommended.
Over VPN, only one stream per controller runs via the controller at a time, even with several
cameras; another device shows the still image in the meantime. |
|
| Video format | Automatic follows the URL: rtsp is RTSP, the ending .m3u8 HLS, .ts
MPEG-TS and everything else MJPEG. If this does not match the camera, set the format explicitly. HLS only works
directly from the device, not via the controller. MPEG-TS means the continuous stream of a camera, video files on a web server do not work with it. The field appears as soon as a stream URL is entered. |
|
| Snapshot | ||
| Trigger | Edge at input ST that takes a snapshot: rising, falling or any change. | |
| Ring buffer maximum | Upper limit for the number of snapshots, 1 to 100. How many are kept until the oldest is replaced is set by the user on the control via the gear, 10 by default. If that value is above the maximum, the maximum applies and the oldest snapshots are deleted. | |
| Delay | Waiting time in milliseconds between trigger and snapshot. | |
| Snapshot mail | ||
| Active, address, subject, text, file extension | Sends each snapshot as a mail with the image attached. The other fields appear when Active is switched on. | |