Soracom Orbit is an inline data processing service that gives you the ability to write a WebAssembly (WASM) module that transforms device data as it passes to and from the cloud. Soracom provides SDKs for developing WASM modules in multiple programming languages.

Soracom Orbit Development Environment version 2022-05 is now available, which updates the following development dependencies:

• AssemblyScript
  • Update Node.js to v16 LTS
  • Update development dependencies
    • jest 27.5.1
    • prettier 2.6.2
    • eslint 8.16.0
    • TypeScript 4.7.2
• Rust
  • Update Rust to 1.61.0
• TinyGo
  • Update TinyGo to 0.23.0
• Common
  • Update SORACOM CLI installation method, which will install the latest version while creating your development container

For more information, please refer to the Soracom Orbit: Environment Setup documentation.

As of May 26, 2022, pricing for the S+ Camera WP v2.1 has been revised.

• Old price: ¥109,780
• New price: ¥105,600

Prices are in Japanese Yen (¥) and include Japanese consumption tax.

For more details, visit the product page (Japanese).

Soracom Funnel is an adapter service that forwards data from a device directly to a cloud service.

By default, when Funnel forwards data, metadata such as IMSI and timestamp is added to the forwarded data, which can be helpful for many applications. However, in some use cases, you may want to disable this behavior. With this update, you can now select the Payload only option which will suppress adding metadata and instead send the data as-is.

In addition, when using Funnel to forward binary data to AWS IoT, Funnel will encode the data in base-64 for compatibility before sending it to AWS IoT. This update also introduces a new Send Payload as Binary option which will send binary data as-is without base-64 encoding.

To use the Send Payload as Binary option, choose the AWS IoT service, then select Binary as the content type, enable the Payload only option, and finally enable the Send Payload as Binary option.

You can find additional information in the Soracom Funnel documentation.

We are pleased to announce the launch of Soracom Cloud Camera Services, a cloud camera service that allows users to continuously record video content to the cloud.

To get started with cloud recording, purchase a compatible camera device (ATOM Cam 2) and a license from the Soracom IoT Store (Japanese), then follow the Getting Started instructions (Japanese) to set up your camera device.

• For more information on the features, see the ATOM Cam 2 product page (Japanese).
• For additional instructions on how to use the ATOM app and the Soracom User Console, see Soracom Cloud Camera Services (Japanese).

For further information on this release, please refer to the "Soracom Cloud Camera Services," a Cloud-based Always-on Recording Service for the IoT Era (Japanese) blog.

FutureNet MA-S120 Series Starter Kits by CENTURY SYSTEMS Co., Ltd. are now available from the Soracom IoT Store.

The FutureNet MA-S120 Series are power-saving IoT gateways equipped with a 3G/LTE Cat-4 cellular module. FutureNet MA-S120/L Starter Kit and FutureNet MA-S120/GLA Starter Kit are now available from the Soracom IoT Store and each include a plan-K2 Soracom IoT SIM for Japan.

FutureNet MA-S120/L Starter Kit

• Availability: Japan only
• Price: 63,140 yen (tax included, bundled with a 2,000 yen Soracom platform coupon)
• Included Accessories: AC adapter, cellular antenna, Soracom IoT SIM for Japan (plan-K2, data communication only)

For more information, please refer to the product page (Japanese).

FutureNet MA-S120/GLA Starter Kit

• Availability: Japan only (however this model can be used outside of Japan when used with a SIM that provides coverage outside of Japan, such as a Soracom IoT SIM)
• Price: 74,140 yen (tax included, bundled with a 2,000 yen Soracom platform coupon)
• Included Accessories: AC adapter, cellular antenna, Soracom IoT SIM for Japan (plan-K2, data communication only)

For more information, please refer to the product page (Japanese).

When sending data to Soracom Funk, Funnel, and Harvest Data, fees are calculated based on the number of requests made. You can now download a CSV file containing the number of requests made to these services in order to check how much of each service has been used.

Usage history is available for the past 6 months (monthly) or the past 90 days (daily), and will include the number of requests aggregated by IMSI and by month or day. For Soracom Funnel, request usage is further aggregated by Funnel adapter, and for Soracom Funk, request usage is further aggregated by cloud service.

You can download the usage statistics CSV from the User Console by accessing the "Billing" page, and selecting the type of CSV from the "Download traffic stats as CSV" section.

The Soracom API has a "maximum number of requests" per minute (i.e. a rate limit) for related APIs (hereinafter referred to as "API groups").

If a system using the Soracom API calls an API at a higher rate than the set limit, the HTTP status code 429 is returned from the Soracom platform and the system must wait up to one minute before calling the API again.

Since the "maximum number of requests" is different for each API group, and since the rate limits are subject to change, we have not historically listed rate limits on the Soracom Developers site.

Instead, with this new change, when your system calls an API the following information about the rate limits will be returned so you can determine the "maximum number of requests".

• X-Soracom-Ratelimit-Limit
• X-Soracom-Ratelimit-Remaining
• X-Soracom-Ratelimit-Seconds-Before-Refresh

Based on the returned information, your system can invoke the API according to the rate limit. Alternatively, you may apply for a rate limit increase by contacting Soracom Support with details of your use case.

For more information, see Rate Limits. (Japanese)

We are pleased to release a new Soracom X/Y Image panel that can use incoming sensor data as coordinates to position an image over a custom background that can be panned and zoomed.

The panel consists of a background and sensor images that are positioned using x and y coordinates obtained from device queries.

Input data can be mapped to any background by specifying maximum and minimum expected values for each device.

While the obvious use case is custom maps, the ability to translate device data into X/Y coordinates opens up the opportunity to display any kind of numerical data in unlimited ways.

The Soracom X/Y Image panel also introduces the ability to use Soracom Harvest Files as an image store directly from inside Lagoon, especially convenient when you would prefer to keep any image data private.

For more information, please refer to the Soracom X/Y Image documentation. (Japanese)

The Soracom User Console is a vital part of Soracom platform, and as such we are continuously working to improve the user interface and experience. As you may have noticed, we have recently updated the header and navigation menu with a new look and feel.

This update also introduces a couple changes to improve functionality and nagivation.

The account menu located on the right-hand side of the header now includes additional information about your account type (individual or corporate) and login method (root user or SAM user):

In addition, the "Usage Statistics" link previously located in the account menu has been moved to the more logical "Logs & Statistics" section of the main menu. You can access it by clicking the menu button on the left-hand side of the header:

API keys and tokens generated using the Soracom API or CLI can now be revoked at any time using the following new APIs:

• Auth:logout
• User:revokeUserAuthTokens
• Operator:revokeOperatorAuthTokens

When generating an API key and token, you can specify a duration for which the token will remain valid. However, there was previously no way to manually revoke the token earlier than the valid duration once issued. In order to prevent an API key and token from being abused, you therefore had to specify a custom duration appropriate for your application.

With this update, an API key and token can be immediately revoked by calling the above APIs as soon as the key and token are no longer needed.

For more infomration, please refer to API Reference Guide.