Scheduled removal of the parameters: image.name and image.timestamp.
Date of deletion: February 27, 2024

Now those values stored in fields "name" and "created" of the the media.image object parameter.

As announced by kial , now parameters image.name and image.timestamp are no longer added to messages that already contain the media.image media file parameter in the new form.

We adjusted the output of our JSON generating engine to prevent escaping of forward slash ‘/’ inside string values.

Forward slash character escaping is not required by JSON format and if you are parsing JSON by any modern parsing library this change will not be visible for you. However if you rely on pure textual output from a REST API call and parse our JSON somehow manually in the code you may need to adjust your parsing scheme.

Update to Geofence Experience

We have rolled out an update that significantly enhances the geofence experience. Previously, geofences were maintained within plugin or calculator configurations, leading to several issues:

• Updating a single geofence required updating the entire list of geofences.
• Sharing geofences between calculators was not possible.

To address these issues, we introduce a new geofence concept while retaining the old one.

Key Features of the New Geofence System

• Independent Entity: A geofence is now an independent entity characterized by an id, name, geometry (polygon, circle, or corridor), and metadata.
• Enhanced Integration: Geofences can be linked with various components such as plugins, calculators, or streams.
  • Streams: Linked geofences enable selective message transmission within or outside designated geofences.
  • Plugins: Linked geofences enrich message parameters with geofence names and metadata.
  • Calculators: Linked geofences are utilized within selectors, validators, and counters.

Additional Features

• Grouping: Geofences can be organized into groups, similar to the grouping of devices.
• Access Management: Geofence access can be managed through ACLs.
• Subaccount Access: Access to geofences from unrelated subaccounts can be granted.
• Priority System: Geofences have a priority range from 0 to 100, with higher priority geofences being checked first in case of intersections.

This update enhances your telematics solution by incorporating robust geocoding functionality, improving usability, and enabling more flexible and powerful geofence management.

You can find more technical details here.

We've added a configurable delay before sending a webhook request. It could be helpful in some cases where the peer is not ready to process the request immediately.

We've implemented some changes to storage containers:

1. You can attach custom metadata to storage containers.
2. We removed a restriction that prevented access to subaccount's containers or CDNs with the owner's token.
3. You can grant access to the containers to subaccounts.

We are deprecating Snapshots functionality in devices.

If you were using this system to retrieve device messages snapshots please make sure you switch to GET /gw/devices/XXX/messages call instead. The call without parameters will return all messages currently stored in the device in the same format as snapshot, just not archived.

On Monday, August 19 any REST API call to snapshots will return deprecated warning.

On Monday, September 23 REST API calls with access to snapshots will be not available to use anymore.

We have extended the REST API method by adding an optional command ID. This makes it convenient to query the result of a specific command using the following endpoint:

GET /gw/devices/{devices-selector}/commands-result/{command-id}

Additionally, the ability to fetch multiple command results remains available:

GET /gw/devices/{devices-selector}/commands-result

We have introduced the ability to assign geofences to individual devices, simplifying configurations on top of flespi. Now, each device can have its own unique set of geofences. For example, a plugin can combine its own assigned set of geofences with the device's geofence set.

GET, POST, DELETE /gw/devices/{device-selector}/geofences/{geofence-selector}

We will also support such assignments for calculators.

We have added an alternative set of parameters to the hit test geofences REST API method.

The first set tests whether the coordinate hits the selected geofences.

GET /gw/geofences/{geofences-selector}/hittest
{
 "lat": 0,
 "lon": 0
}

The second set returns a set of geofences that are within the specified boundary.

GET /gw/geofences/{geofences-selector}/hittest
{
 "max_lat": 0,
 "max_lon": 0,
 "min_lat": 0,
 "min_lon": 0
}

We've implemented some changes to CDNs:

1. You can attach custom metadata to CDN.
2. You can grant access to the CDNs to subaccounts.

We enhanced device media transparency with new log message (event code = 28) that is published when the media file is accessed via HTTP.

For those who are using method POST /gw/devices/{device-id}/calculate we have important change that requires from your an action.

There are 2 variants how to trigger this API call and provide to flespi configuration for calculation:

1. Providing all configuration for counters, selectors, validators directly in the REST API call.
2. Providing calc_id (ID of calculator) from which this selectors, counters, validators will be used during the actual calculation.

We are deprecating a second variant of data provisioning in this API call - when calculation configuration is provided via referenced calc_id. On January 14, 2025 an attempt to use this method with calc_id in the parameters will return an error. From today when you are calling this REST API method with second variant configuration it adds deprecated warning into REST API call response.

Please modify your integration and provide into this API method all selectors, counters and validation configuration directly. You can add a GET /gw/calculators/{calc_id} call to retrieve calculator configuration beforehand and supplying its parameters to the calculation call. Or just hard code the configuration to calculate in the code directly.