...
https://avisec.atlassian.net/wiki/x/AYDVtw
Configuration
The images sent by a bmetry solution take another path than images sent by other cameras. Bmetry images are not visible in the portal, as the content of individual images is rarely of interest. As such, the browse page of a bmetry camera will be empty, or merely show the images that were captured the “regular” way by a schedule or manually, but you can still use the portal to configure your solution by clicking on the configure menu option:
...
The serial of the master itself is added implicitly and does not need to be configured.
Endpoint configuration
As bmetry images are routed differently and never go through the usual post-processing steps as other images do, configuring a forwarding endpoint in a table configuration has no effect. Instead, you need to configure the endpoint you want the images forwarded to for processing here. If you do not configure an endpoint here, you will not receive any images!
...
You can forward to either an FTP server, or to an AWS S3 bucket under your control. Do not configure both. If you do, the FTP server takes priority, the S3 bucket will receive nothing.
FTP configuration
Host: The fully qualified domain name of your FTP server.
...
User and Password: Credentials to log into the FTP server for the file transfer.
S3 configuration
Bucket: Name of the bucket to send to.
Key and Secret: Access key and Secret key of an AWS user that has putObject permission for the bucket.
Common configuration
These fields affect both FTP and S3 uploads the same:
...
Time format: You can choose a format for the timestamp as it will be inserted into the filename. These include milliseconds, as for some bmetry-solutions a resolution of one second may not be enough. Choose whatever time format suits you best.
API Documentation
The API documentation has moved here: https://avisec.atlassian.net/wiki/x/AYDVtw
...