Soracom

Cut out still images at regular intervals from videos obtained by SoraCam, detect people with SORACOM Flux, and notify by email. The detected person count data is accumulated in SORACOM Harvest, enabling simple visualization. Furthermore, by configuring SORACOM Lagoon, you can create a fully customizable dashboard.

Overview

This app template uses recorded videos acquired by the always-on cloud recording function of the IoT camera “ATOM Cam” compatible with Soracom Cloud Camera Services (hereafter SoraCam). Still image acquisition and person detection with SORACOM Flux, and the detected data are notified by email and also accumulated in SORACOM Harvest. Data accumulated in SORACOM Harvest can be easily visualized, and by using SORACOM Lagoon, you can also visualize images and data with a fully customizable dashboard. This app is useful for:

• Regularly count people with AI without visually checking always-recorded footage
• By customizing instructions (prompts) for AI, you can also count things other than people
• Data can be created for crowding level or utilization rate of people to be counted or other monitoring targets
• Notify users as needed

Example Email Notification

The emails sent will look like this:

Estimated Cost When Running the Flux App

The estimated cost for running the Flux app created from this template is as follows.
This explanation assumes the interval timer event source is set to run once every 10 minutes.

• In this Flux app, the event count is 144 times per day, and with 31 days of operation per month, the total event count is 4,464.
• With the SORACOM Flux Developer plan, up to 10,000 events per account per month are available free of charge. If you exceed 10,000 events/month, a charge of 0.11 yen per event will apply.
• In this Flux app, the AI action is executed 144 times per day, and since the AI model “Amazon Bedrock – Amazon Nova Lite” uses 3 credits per execution, 432 credits are used per day. With 31 days of operation per month, 13,392 credits are used.
• With the SORACOM Flux Developer plan, up to 1,500 credits per account per month are available free of charge. If you exceed 1,500 credits/month, a charge of 0.044 yen per credit will apply.
• The event and credit limits are initially set to the same as the free bundle. If the limit is reached, the app will no longer launch or execute actions triggered by events. If you want to use more, please update the upper limit in advance. If you set a limit that exceeds the monthly bundle, excess events or credits will be billed on a pay-as-you-go basis.

Prerequisites

Before deploying (executing) the app with this template, please prepare the following:

• SoraCam setup: Install SoraCam, assign a license, and confirm the device ID.

For details, refer to SORACOM documentation Install a SoraCam-compatible camera (Add a camera) STEP 1 to STEP 4. please tanslate from Japanese with your web browser translation feature enabled.

• Email setup: A verified recipient email address.

For details, refer to SORACOM documentation Email Settings.

This Flux app is also an app template version of the DIY IoT recipe SORACOM IoT Recipe: People Detection and Notification with IoT Camera (Cloud Always Recording License Edition), so please also refer to the IoT recipe for more details. The method for configuring SORACOM Lagoon is also described in the recipe. please tanslate from Japanese with your web browser translation feature enabled.

Creating the App

Customizing Settings

At the time of app creation, you can set the interval at which the app operates, the target SoraCam, and the recipient email address. For the email address, select a verified recipient address from the [Select Email Address] button.

Actions to Take After Creating the App

App Customization

By changing the text in the prompt field of the AI action, you can change which targets to count. To configure under what conditions to notify, change the number in payload.output.person >= 0 in the execution condition field of the Email notification action.

Troubleshooting

If things do not work as expected, please check the app’s execution history. For details, see View Logs.