Place for information about telematics hub updates.

We supported special streaming protocol called nis . This protocol is used in Russia only, and although it is very stupidly designed - HTTP/SOAP based with just one message per HTTP request - it is quite popular on CIS space for inter-servers communications. Feel free to use it.

nis streaming protocol was updated to send values for Digital inputs, outputs and Analog inputs. The number of streamed Analog inputs is limited up to 8 for nis and wialon_retranslator streams.

We have removed deprecated fields " ident " and " phone " from the devices REST API. These fields was left for backward compatibility for a few months. In addition, we have removed old stream subscriptions REST API methods also marked as deprecated a few months ago. More details are placed in this article: https://flespi.com/blog/sync-up-with-changes-in-the-flespi-device-api

Platform has changed the way it accumulating logs when operating under subaccounts hierarchy . Say you have account root with subaccount sub and it branched another subaccount subsub . Tree looks like this: root<=sub<=subsub. Now imagine that you have log message for the subsub account, for example device was connected. Before the update : logs both in realtime (subscribing to flespi/logs/#) and in history mode (accessible via REST ) where placed by the system into an account subsub and all its parents: sub and root . Thus when operating with large volumes we have quite a big storage size of root top-account basically multiplied by the number of subbaccounts it has. After the update : the log message will be stored exactly and only at the account where it was generated. E.g if you have device or channel that belong to some subaccount you can access log messages for this entity only from its account. This is applied to both REST and MQTT. Toolbox was modified accordingly and now has account selector whenever you have some flespi accounts to switch between.

We increased telemetry expiration time up to 370 days.

We've added the "status" field for each device setting. It's indicating the source of the current setting value (if available) and the flespi platform intention to read the new current value or apply the pending setting value. The full documentation is available here: https://flespi.io/docs/#/gw/!/devices

Platform update affects devices with ident collisions. Collision occurs when two or more devices have the same ident, device type and share a common channel. The device with the lowest identifier remains unlocked, other devices will be blocked using the "bad configuration" code.

adsa We have reverted update until some problems being solved.

Next Monday, on October 14, we will install an update with the small change in our Telematics Gateway REST API. Once installed, the devices creation method ( POST , https://flespi.io/docs/#/gw/!/devices/post_devices ) will require the " device_type_id " and " configuration " fields to be specified. Also, the " configuration " object for all device types will require an " ident " field. Please review your integrations and correct them to always include such fields when you're creating devices. If you have any questions, please contact us in the chat embedded in the flespi.io panel or on forum.flespi.com

adsa The problems were resolved and the update was installed.

[Changelog] flespi telematics hub

YuryAheichyk

YuryAheichyk 1NCE modem has been updated, added Source address optional configuration field, which allows to check the SMS sender when receiving a message additionally

adsa

We have added the ability to disable devices. This feature can help mitigate channel loading bursts caused by channel inaccessibility or connectivity issues. Once a device is disabled, existing connections will be closed and new connections will be rejected. Only disabled devices can be moved between subaccounts.

Corresponding REST API method:

HTTP Method: PUT

Endpoint: gw/devices/{devices-selector}

Request body:

{
  "enabled": false
}

adsa

We've implemented some changes to storage containers:

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

adsa

We've extended the functionality of the storage containers by publishing all posted messages to the MQTT bus. This way, you can subscribe to the topic flespi/message/storage/containers/+ to receive all new container messages.

shal

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.

adsa

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

adsa

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.

adsa

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
}

adsa

We've implemented some changes to CDNs:

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

shal

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

shal

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:

Providing all configuration for counters, selectors, validators directly in the REST API call.
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.

adsa

Upcoming Update (Scheduled for April 1st, 2025)

The following API methods will now require the data parameter as a mandatory field:

DELETE /storage/cdns/files
DELETE /storage/containers/messages
DELETE /gw/devices/media

Action Required

Update your API calls to ensure they include the required data payload.
Review integrations and webhooks that interact with these endpoints.

If you have any questions or need support, please reach out to our development team.

YuryAheichyk

For custom user-data ingestion protocols (such as http, mqtt, etc) following device-specific parameters are now automatically removed from channel messages:

device.id
device.type.id
device.name

Previously only channel-specific parameters (ident, peer, protocol.id etc) were automatically replaced with their actual values.

These are reserved system parameters in flespi and should not be present in custom message payloads.

shal

In assets that are designed to track drivers, trailers, etc and available now in experimental mode we renamed last_interval asset property to last to keep naming in sync with devices and calculators. Please update your integration in case you are already started to use it.

adsa

Important: Upcoming Change to Parameter Naming Validation

We've identified an inconsistency in how flespi handles parameter names containing minus signs (-) that we need to address.

Current Situation:

Device messages currently accept parameter names with minus signs (e.g., "engine-rpm", "custom-value")
However, device telemetry doesn't support minus signs in parameter names
This causes parameters with minus signs to be missing from telemetry, even though they appear in messages

What's Changing:
To ensure consistency across the platform, we will synchronize the validation rules. After this update, device messages will no longer accept parameter names containing minus signs.

Impact:

Any existing parameters with minus signs will need to be renamed
This affects custom parameters sent via HTTP/MQTT channels or created by plugins
Standard flespi parameters are not affected (they already follow the correct naming convention)

Recommended Actions:

Review your device configurations and custom integrations for parameter names containing minus signs
Replace minus signs with underscores (e.g., "engine-rpm" → "engine_rpm") or dots for hierarchy (e.g., "engine-rpm" → "engine.rpm")
Update any applications or scripts that send data to flespi with the new parameter names
If using plugins that create parameters with minus signs, update their configuration

Best Practice Reminder:
Parameter names should only contain:

letters (a-z)(A-Z)
Numbers (0-9)
Dots (.) for hierarchy
Underscores (_) as separators

This change ensures that all parameters visible in messages will also be available in telemetry, providing a more consistent and reliable experience.