We are excited to announce that Soracom Flux now supports the newly-released Anthropic Claude 3.5 Haiku model from Amazon Bedrock.

To use Anthropic Claude 3.5 Haiku in your Soracom Flux application, simply add an AI action and select Amazon Bedrock - Anthropic Claude 3.5 Haiku from the list of available AI models.

Each AI action request sent to Anthropic Claude 3.5 Haiku will consume the following number of Flux credits:

Model	Consumed credits
Amazon Bedrock Anthropic Claude 3.5 Haiku	40 Credits

For more information on Soracom Flux, please refer to the Soracom Flux documentation.

Soracom Cloud Camera Services (SoraCam) provides a notification feature, currently available as a Public Beta, that sends alerts via email or webhook when specific SoraCam events occur. This update introduces a new interface that allows users to monitor the number of notifications sent during the current month and review the notification delivery status from the past two weeks for the following paid notification types:

• Events triggered by changes in the status of SoraCam-compatible cameras (e.g., device online, device offline, cloud continuous recording stopped)
• Events detected by SoraCam-compatible cameras (e.g., motion detection, sound detection)

This enhancement enables easier management and troubleshooting of the notification process by allowing users to:

• Verify that notifications are triggered and sent as intended
• Investigate potential issues if there are any notification delivery errors
• Optimize settings based on the number of notifications sent, such as adjusting motion or sound detection sensitivity

For more details, please refer to Check Usage of Notification (Japanese) documentation.

We are pleased to announce the following coverage updates for Soracom Air for Cellular connectivity.

plan01s and plan01s-LDV

2G, 3G, 4G/LTE updates

Country	Network	Before	After	Remarks
Australia	Optus	3G, 4G/LTE	4G/LTE	3G sunset
Australia	Telstra	3G, 4G/LTE	4G/LTE	3G sunset
Austria	Magenta	2G, 3G, 4G/LTE	2G, 4G/LTE	3G sunset
Canada	Telus	3G, 4G/LTE	-	Network shutdown
Chile	Claro	2G, 3G	2G, 3G, 4G/LTE	4G/LTE open
Chile	Movistar	2G, 3G, 4G/LTE	3G, 4G/LTE	2G sunset
Dominican Republic	Altice	-	2G, 3G, 4G/LTE	Network open (*1)
Faroe Islands	Telecom	-	3G, 3G	Network open
Kenya	Airtel	2G, 3G	2G, 3G, 4G/LTE	4G/LTE open (*1)
Kosovo	IPKO	-	2G, 3G	Network open
Kyrgyzstan	O!	-	3G, 4G/LTE	Network open
Maldives	Dhiraagu	-	2G, 3G	Network open (*1)
Mali	Orange	-	2G, 3G, 4G/LTE	Network open (*1)
Mexico	AT&T	-	3G, 4G/LTE	Network open
Oman	Ooredoo	-	2G	Network open (*1)
Peru	Claro	2G, 3G	2G, 3G, 4G/LTE	4G/LTE open
Philippines	Globe	-	2G	Network open
Serbia	MTS	2G	2G, 4G/LTE	4G/LTE open
Sierra Leone	Airtel	-	2G, 3G	Network open (*1)
Spain	Yiogo	2G, 3G, 4G/LTE	4G/LTE	2G & 3G sunset
Sweden	Telenor	2G, 3G, 4G/LTE	3G, 4G/LTE	2G sunset
Thailand	dtac	2G, 3G	2G, 3G, 4G/LTE	4G/LTE open

(*1) plan01s only

LPWAN (LTE Cat.M1 and NB-IoT) updates

Country	Network	Before	After	Remarks
Czech Republic	Vodafone	2G, 4G/LTE	2G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Denmark	3	3G, 4G/LTE	3G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Denmark	TDC	2G, 4G/LTE	2G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Denmark	Telenor	2G, 4G/LTE	2G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Denmark	Telia	2G, 4G/LTE	2G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Finland	DNA	2G, 4G/LTE	2G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Finland	DNA	2G, 4G/LTE	2G, 4G/LTE, NB-IoT	NB-IoT open
France	Orange	2G, 3G, 4G/LTE	2G, 3G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Ireland	3	2G, 3G, 4G/LTE	2G, 3G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Ireland	3	2G, 3G, 4G/LTE	2G, 3G, 4G/LTE, NB-IoT	NB-IoT open
Liechtenstein	FL1	2G, 3G, 4G/LTE	2G, 3G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Mexico	AT&T	-	3G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Norway	Telenor	2G, 4G/LTE	2G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Norway	Telenor	2G, 4G/LTE	2G, 4G/LTE, NB-IoT	NB-IoT open
Norway	Telia	2G, 4G/LTE	2G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Spain	Movistar	2G, 3G, 4G/LTE	2G, 3G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Sweden	Telenor	3G, 4G/LTE	3G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Sweden	Telia	2G, 4G/LTE	2G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Switzerland	Sunrise	3G, 4G/LTE	3G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open

planX3 and planX3-EU

Country	Networks	Before	After	Remarks
Austria	A1	2G, 3G, 4G/LTE	2G, 3G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open
Denmark	Hi3G	-	3G	Network open
Mayotte	Orange	2G, 3G, 4G/LTE	2G, 3G, 4G/LTE, LTE Cat.M1	LTE Cat.M1 open (*2)
Mexico	Telefonica	2G	3G, 4G/LTE	2G sunset, 3G and 4G/LTE open (*2)
Sweden	Hi3G	-	3G	Network open
Sweden	Telenor	2G, 3G, 4G/LTE	3G, 4G/LTE	2G sunset
Uruguay	Movistar	-	3G, 4G/LTE	Network open (*2)
Uzbekistan	Unitel	-	2G, 3G	Network open (*2)

(*2) planX3 only

For complete details about data rates, supported carriers and radio types, and coverage in other countries, please refer to the Supported Carriers documentation.

We are pleased to announce that Soracom Flux now allows generating Incoming Webhook URLs for Flux Channels.

Flux Channels serve as connectors between Event Sources (such as data sent by a device) and Actions (such as an AI model for processing that data). With the new Incoming Webhook URL feature, you can now submit data into a specific channel by simply sending an HTTP request to the webhook. This feature allows you to trigger Actions at any point of a Flux app from an external source, such as a third party automation tool or your own custom integration.

Moreover, Incoming Webhook URLs are protected using a randomly generated value and do not require complex authentication procedures or management of API keys, making them widely compatible with different services and simple to implement.

For more information on Incoming Webhook URLs, Channels, or Actions, please refer to the Soracom Flux documentation.

We are excited to announce that Soracom Cloud Camera Services (SoraCam) videos recorded with cloud continuous recording can now be exported as videos or still images to Soracom Harvest Files.

In addition to the current standard export option, you can now choose to export to Harvest Files. The differences are as follows:

Standard export

• Exported files are available for 10 minutes after each file is exported, during which the file can be downloaded. After this time, the file will no longer be available.
• There are no additional charges.

Export to Harvest Files

• Exported files will be stored in Harvest Files for 731 days, during which the files can be downloaded. After this time, the files will no longer be available.
• You can use placeholders such as {device_id} and {date} to specify the directory name where the exported files are saved within Harvest Files.
• Additional Harvest Files charges will apply based on the size of the exported files (the amount of data saved to Harvest Files) and the size of the downloaded videos (the amount of data downloaded from Harvest Files). For example, if you export a video once and download it twice, you will be charged for one write and two reads. For more details, please refer to the Pricing & Fee Schedule: Soracom Harvest Files.

If you have any questions or concerns, please feel free to contact Soracom Support.

We are excited to announce a new tag feature for Soracom Cloud Camera Services (SoraCam), allowing you to assign tags to SoraCam compatible cameras directly from the User Console. This feature enables more flexible camera management, letting you attach custom tags such as the camera's location, purpose, administrator's name, or other attributes.

Once tags have been added to cameras, you can then easily filter by tags to quickly find and manage a particular camera.

When using tags, each camera can have up to 10 tags, and each tag can have a maximum of 12 characters.

For more information about SoraCam, please refer to the Soracom Cloud Camera Services documentation (Japanese).

We are pleased to announce that Soracom Flux now supports a new action to execute Soracom APIs.

With this new feature, Soracom APIs can be triggered automatically based on input data from IoT devices or timers. For example, a Soracom API action can be configured to automatically update a SIM tag, switch the SIM to another group, or start a Soracom Peek packet capture session based on data uploaded by a device, or periodically check data usage, SIM status, or online status according to a timer. Responses from each Soracom API request can be further linked to other Flux actions such as an AI, Webhook, or Notification action.

For more information on using the Soracom API Action, please refer to the Soracom Flux documentation.

We are excited to announce that you can now customize the panels that are displayed in the Soracom User Console dashboard. With this update, you can choose which panels are visible in order to focus on the information that is most important to your application.

• To hide a panel, simply click the X icon in the upper-right corner of the panel.
• Panel visibility (including displaying a panel again) can be managed from the gear icon (
  
  ) in the upper-right corner of the dashboard screen.

We are pleased to announce that Soracom Flux is now compatible with Azure GPT-4o mini.

When building a Flux application, you can specify an AI Action in order to send a request to an AI model for processing. With this update, you can now send requests to the Azure OpenAI (GPT-4o mini) model. While Azure OpenAI (GPT-4o mini) supports image analysis, this model makes it more affordable to analyze and process text-based IoT data without images.

Each Azure OpenAI (GPT-4o mini) request will consume Flux credits according to the following types of request:

Model	Consumed credits
Azure OpenAI (GPT-4o mini)	6 Credits (without an image)
Azure OpenAI (GPT-4o mini)	150 Credits (with an image)

For more information, see the Soracom Flux documentation.

We are excited to announce the addition of a new notification feature to Soracom Cloud Camera Services (SoraCam), which allows users to receive notifications via email or webhook when certain events occur. With these notifications, operators will be able to manage the status of multiple SoraCam-compatible cameras more efficiently, such as facilitating rapid response in case of a camera malfunction.

The following events can trigger notifications:

• Account events (free of charge):
  • A SoraCam device was added
  • A SoraCam device was removed
  • A SoraCam device was shared
• Device events (paid):
  • A SoraCam device came online
  • A SoraCam device went offline
  • A SoraCam device's cloud recording was interrupted
• Detection events (paid):
  • Motion or sound was detected

For more details on the notification feature, please refer to Notification Settings (Japanese). Additional information on pricing is available in the Pricing Details (Japanese).