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

      13 days later

      • adsa

      • Post #146
      • Edited

      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
}
        14 days later

        We've implemented some changes to storage containers:

        1. You can attach custom metadata to storage containers. Image Preview
        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.
          6 days later

          • adsa

          • Post #148
          • Edited

          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.

            15 days later

            • shal

            • Post #149

            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.

              a month later

              • adsa

              • Post #150

              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

              • Post #151

              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

              • Post #152

              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
}
              11 days later

              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.
              5 days later

              • shal

              • Post #154

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

                14 days later

                • shal

                • Post #155

                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.

                  5 months later

                  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.

                  Write a Reply...