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.

As previously announced, we have updated the following Soracom service entry points in order to support HTTP Keep-Alive.

When a device sends data to Soracom using HTTP, it may optionally specify a Connection: keep-alive directive in the HTTP request header in order to reuse the underlying TCP connection and reduce the reconnection data usage when sending additional HTTP requests. This update increases the maximum timeout from 5 seconds to 65 seconds, allowing Soracom Air for Cellular and Soracom Arc devices sending HTTP requests to Soracom service entry points at intervals shorter than 65 seconds to maintain the TCP connection and reduce data usage.

Affected Entry Points

• Soracom Beam HTTP Entry Point
• Soracom Beam Website Entry Point
• Soracom Funk HTTP Entry Point
• Soracom Funnel HTTP Entry Point
• Soracom Harvest Data/Files HTTP Entry Point
• Unified Endpoint HTTP Entry Point

Effective Date

This update is now being rolled out as of November 6, 2024.

Action Required

• If you would like to use the extended Keep-Alive timeout, we recommend waiting until the roll out is complete.
• If your device cannot support the extended Keep-Alive timeout, we recommend disabling Keep-Alive by updating your device to include the Connection: close directive in your HTTP request headers.

If you have any questions or concerns, please don't hesitate to contact the Soracom Support team.

As previously announced, we have now updated the valid timestamp range that can be specified when saving data to Harvest Data with a custom timestamp. Prior to this update, it was possible to specify any arbitrary date and time for the custom timestamp, which could lead to unexpected behavior, such as when the date and time value provided by the device significantly differs from the actual date and time due to the device's internal clock drift.

With this update, Harvest Data will now return an error without saving the data if the difference between the date and time specified by the device and the actual date and time greatly exceeds that of normal use cases.

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

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

plan01s and plan01s-LDV

2G, 3G, 4G/LTE updates

(*1) plan01s only

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

planX3 and planX3-EU

(*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.

The Soracom Flux Amazon Bedrock - Anthropic Claude 3.5 Sonnet AI action has been upgraded in accordance with Amazon Bedrock's Claude 3.5 Sonnet V2 upgrade.

No action is required for customers already using the Amazon Bedrock - Anthropic Claude 3.5 Sonnet AI action.

If you would like to confirm the version of the Claude 3.5 Sonnet model, you can check the Model ID details returned from Claude 3.5 Sonnet in the AI action response.

For additional information, please refer to the Soracom Flux: AI actions documentation.

We are pleased to announce that we have added a Sound Detection feature to the Unlimited Live Streaming Limited Preview for Soracom Cloud Camera Services (SoraCam).

With this feeature, you can now enable or disable sound detection for SoraCam compatible cameras as well as adjust the sound detection sensitivity from the User Console. The Sound Detection settings are available on the Live Streaming tab of the Unlimited Live Streaming Limited Preview.

This feature is currently available as part of the Unlimited Live Streaming Limited Preview. Please refer to the Unlimited Live Streaming Limited Preview (Japanese) documentation for instructions on how to apply for the Limited Preview.

We are pleased to announce an update to the Variables feature in Soracom Lagoon 3. With this update, users can now search for resources by their SIM or device name using regular expressions. This enhancement makes it easier to build data visualizations using the names assigned to resources (such as IoT SIMs or Sigfox devices), rather than their IMSI, device ID, or other identifier.

To search for resources by name using a regular expression, simply prepend name to the expression, such as name/sample-[0-9]/.

For more details on using this feature, please refer to the Variables documentation (Japanese).

We are pleased to announce that we have improved the OTA (over-the-air) update behavior for delivering Subscription Containers to compatible Soracom IoT SIMs.

Subscription Containers are a feature available on certain Soracom IoT SIMs which allows you to add extra subscription plans to the same SIM for additional coverage and redundancy. When adding a subscription container to a SIM, the additional subscription plan is delivered using an OTA update.

In some cases such as a weak signal or loss of connection, the OTA update process may be interrupted. Until now, restarting the OTA update has required waiting for at least 25 hours, moving the device to a new location to resolve connection issues, and manually deleting a device's cellular session or rebooting the device to re-trigger the OTA update, with a maximum of 3 retries before giving up.

With this update, we have improved the retry mechanism so that OTA updates are automatically restarted as quickly as 5 minutes once Soracom detects that connection issues have been resolved. The maximum number of retries has also been extended to 12 retries. Together, these improvements will help to reduce both the number of errors in delivering Subscription Containers to SIMs and the time needed to complete an OTA update.

Effective Date

This update will be automatically applied for all customers on August 14, 2024.

Please note the improved delivery mechanism will only apply to Subscription Containers that are added on or after this date. Subscription Containers that are added prior to this date will still be delivered using the previous OTA update mechanism.

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

plan01s and plan01s-LDV

Coverage updates

(*1) plan01s only

planX3 and planX3-EU

(*2) planX3 only

We are excited to announce a new firmware update (v3134) for the Soracom LTE-M Button, packed with enhancements and new features to improve functionality and user experience.

Features and improvements

New Alert mode

This firmware introduces a new Alert mode. Like the standard click function, this mode will send an uplink message when the button is clicked. However, this mode prioritizes sending the uplink message without any extra delays, and will disable the ability to accidentally cancel uplink messages to ensure that clicks are delivered, making it useful for emergency situations.

Alert mode also features a new configurable Network Standby setting which will keep the network connection open for a short period after every uplink, so that subsequent clicks can be sent immediately without the need to reconnect. Alert mode can also be combined with the existing Heartbeat behavior so that you can identify if a button has lost coverage or needs new batteries.

Battery voltage in all messages

Battery voltage, previously reported only in Status and Heartbeat uplink messages, is now included in all uplink messages. Now, no matter if you are using the standard Event (click) modes, the Timer mode, or the new Alert mode, you can monitor your button's battery voltage without the need to separately trigger a Status message or enable Heartbeat.

Automatic Status message

This firmware now features a setting to automatically send a Status message every 24 hours. When enabled, this setting allows for remotely modifying a button's operating mode or settings, without requiring any user interaction. The Status message can also be used to trigger a firmware update if available, allowing the button to stay updated similarly without any user interaction.

Better LED patterns

The LED will now show 1 short blink, 2 short blinks, or 1 long blink corresponding to the type of click detected, allowing a user to visually confirm their intended click. In addition, the LED will now blink slowly when connecting to a network, and quickly once connected and sending the uplink message. Finally, when the button is configured for the new Alert mode, the LED will blink orange after each click, making it easy to differentiate from other modes.

Bug fixes

(Breaking change) Fixed incorrect Rising and Falling edge events

The Rising and Falling edge events in firmware v2220 were mistakenly implemented in reverse, resulting in the button data indicating "Rising edge" instead of "Falling edge" when a circuit using the 2-wire accessory is closed, and vice-versa. As this may have an impact on some circuit designs, these values have been swapped in the new firmware in order to match the original intended behavior:

• v2220 behavior:
  • When a circuit is closed, the button data indicates a “Rising edge” event
  • When a circuit is opened, the button data indicates “Falling edge” event
• v3134 behavior:
  • When a circuit is closed, the button data indicates “Falling edge” event
  • When a circuit is opened, the button data indicates “Rising edge” event

In order to avoid breaking existing applications, the v2220 behavior has not been altered. However, if your application relies on separating Rising and Falling edge events, please note that you will need to switch your application logic when updating to v3134.

Note: Due to hardware limitations, the button may still occasionally incorrectly detect the type of edge event (Rising or Falling). While enabling edge debounce can reduce this issue, incorrect detections may still occur due to an inconsistent or noisy signal from a loose wire, faulty switch, or other circuit components.

Removed unexpected TCP uplink message

In v2220, the button periodically sends a TCP uplink message to Soracom Beam. This message was used for testing and does not contain any user data, however as the button sends actual button data via UDP and a Soracom Beam TCP configuration is not required, a “configuration not found” error would occur. This TCP uplink message has been removed from the new firmware.

How to update

To update your button firmware, please contact the Soracom Support team with the ICCID(s) of your button(s) in order to receive firmware update instructions and for additional assistance. Please don't hesitate to reach out if you are unsure of whether your button has the latest firmware, or if you have any other questions or concerns.