The Universal Bridge is a cloud service that allows you to add a wide range of cloud-based, AI-powered analytics to existing IP Cameras and NVRs without requiring any additional hardware on-site.
The SMTP Connector allows 3rd party clients & devices (Cameras, NVRs, VMS', other services) to send video clips to Lumeo using SMTP. When the Universal Bridge receives video clips, it saves them to the Lumeo Cloud and runs the configured Lumeo pipeline on it in the cloud.
The SMTP Connector only works with devices and clients that allow specifying a SMTP server to be used to send emails. It will not accept emails relayed from other mail servers.
|SMTP Port||PlainText Port : Clients connecting over plaintext must support the SMTP STARTTLS extension and issue the STARTTLS command before attempting to authenticate. Insecure authentication is not supported.|
TLS Port : Clients connecting over this port do not need to use STARTTLS to enable authentication, as this connection is secure by default.
|SMTP Username||Workspace Application ID||See SMTP Authentication Section below.|
|SMTP Password||Universal Bridge Token||See SMTP Authentication Section below.|
|Email Sender (From)||Any unique email address (does not have to be functional).||_ This address will be used to identify this camera within Lumeo. Set/view in Camera detail -> Settings -> Universal Bridge -> External Source Identifier.|
_ Is prefixed to the resulting deployment’s name and incoming video clips uploaded to Lumeo cloud.
* If the Pipeline has an Trigger Immix Alarm Node node, this From email will be set as the Immix Alarm’s destination address.
|Email Recipient (To)|
|Deploys the specified Pipeline using the Clip attached to the Email, on the first available Gateway in the Workspace.|
See Email Recipient Section below for more details.
|Subject||Any||Unused by Lumeo|
Find on the Settings tab in Console.
Username: Workspace ID (found in Settings tab, left nav)
Password: Universal Bridge Token (generated and revokable in Settings tab -> Universal Bridge section)
Watch out for Camera limits on Username and Password
Some cameras may limit the length of the username and password fields and truncate values you enter.
For workspace id / username, you can remove the dashes to shorten the length if required to fit in the limits.
Email "From" address is used to correlate the clip with Cameras in Lumeo. To associate with an existing camera, navigate to the Camera details page and set the External Identifier to the desired email under Universal Bridge settings.
If a Camera with the From address is not found, the Universal Bridge will create a new Virtual Camera in your workspace and assign the From address as it's External Identifier.
Email Recipient corresponds to the email’s To MIME header. Its syntax options are below:
[email protected]: Deploys the Default Pipeline for the Camera, specified in Camera -> Settings -> Universal Bridge
[email protected]: Deploys the specified Pipeline for the attached clip
Note that if you are using
[email protected]as the Recipient, and the From address is not mapped to an existing camera, or the Default pipeline for that Camera is not set, the clip will be saved to Lumeo cloud, but not processed.
The first time a clip is processed by the Universal Bridge, a "Reference Deployment" is created. This is listed in Camera detail -> Settings -> Universal Bridge section.
For future clips, Universal Bridge creates a new deployment of given pipeline, reusing the configuration of the Reference Deployment of that pipeline, while overriding inputs and metadata specific to the Universal Bridge.
This lets you create a master “Video Verification” pipeline that you can keep up to date (such as by adding a new alert mechanism) — and generates a per-Camera “reference” deployment when the first inbound clip is received. This “reference” deployment can be updated with per-Camera settings such as ROI adjustments, for future clips.
Deleting a Reference Deployment will cause a new one to be created with the next Clip.
To set a per-camera configuration for the pipeline, Edit & (optionally) redeploy the Reference Deployment :
- Click on the Reference Deployment listed in Camera Settings
- Edit the deployment settings by clicking the pencil icon on the Configuration tab.
- (Optionally) Update the deployment and run it after editing the settings to see the updated settings in action.
When the Universal Bridge receives a video clip, it will save it to Lumeo Cloud, and queue it up to be processed. Lumeo will schedule these deployments to be processed on any of the gateways available in the workspace in a load-balanced fashion. Once scheduled, these deployments will appear in the Deployments list page.
- Media Format : Universal Bridge only works with video clips (images sent will not be processed)
- Queueing : If all gateways in the workspace have reached their configured max number of the deployments running, the clips are queued at the workspace level to be deployed when a gateway deployment slot is available. During Beta, the status of the queue is not available through Console but available through the Lumeo API.
- Early terminated deployments : As of this Beta, events or alerts (such as email alerts or Immix alarms) may be missed if they are configured to also send a clip with the event/alert. This happens when the deployment processing finishes before the email has had a chance to be sent out. As a workaround during this beta, ensure you set the Clip Node’s clip duration to be a few seconds shorter than the expected incoming clip length.
- Unable to be authenticate or see anything happening on Lumeo Console:
- First verify SMTP communication is working by using the test function available on many cameras like AXIS, and check the Events page for events generated by the Universal Bridge.
- Verify that application ID and application token are correct
- When using the Immix node, the sender e-mail can override the ‘Immix To Email’ to send alarm if the “Enable Universal Bridge Override” option is enabled. Additionally at this time there is side effect that if the save clips and sent clips are same length, Immix node may not sent out the e-mail. The solution is to have size of the Immix node clips to be shorter than the original sent clip.
Updated 3 months ago