1 December, 2021

November 2021 change log

Major flespi improvements in November 2021.

The winter has come. Today, the very first winter day in the northern hemisphere, we have a lot of snow. I hope cold fresh air will help us eliminate the growing threat of the new covid19 strain labeled Omicron. 

Despite the epidemiological situation flespi is up and running and showed 100% monthly uptime in the EU region and 99.997% uptime in the RU region due to a 67-second downtime caused by uplink provider network issues. We are one month apart from a tremendous five-nines yearly uptime in both regions which may become an achievement number one in 2021 for flespi. I believe this is exactly what our users want from us — uninterruptible service with easy-to-use and at the same time powerful functionality.

Important notice for our Free users! 

We are cutting the limits to make the Commercial accounts more valuable and attractive compared to the Free ones and to prevent improper use of the latter. Since Free accounts are only intended for Development and Testing purposes, we believe that 5 devices per channel are more than enough to test flespi and build a PoC on top of it.

Here’s the list of changes:

  • channels: from 3 to 2
  • streams: from 2 to 1
  • TCP connections per channel: from 100 to 5
  • some minor restrictions

Updated limitations and restrictions for Free accounts are listed here. We will activate these restrictions for all Free users on Monday, December 13, 2021.

  • In November we continued to focus on the flexibility of data transformations. A month ago we started with the post-processing channels and now moving this concept further by providing the same level of functionality on the plugins level, where each data transformation is managed by the user for each particular device. In short, it is now possible to add, transform, and delete parameters with arbitrary names via user-supplied code by using plugins. In December we will continue further by introducing plugin types, where each plugin type is able to perform a specific type of action — be it arbitrary code, parameters transformation by the specific scheme, parameters removal, and so on. The processing in plugins is done asynchronously which means we can inject data into messages by querying a third-party database — for example, look up and add a street address from Google directly into each message or look up and add coordinates detected via LBS when satellite information is not available.
  • I’m sure a lot of you guys have already noticed the Platform logs button in the flespi panel menu. Each user now has access to their REST API access logs history which moves our transparency as a middle-level platform one step higher.
  • We integrated two new protocols into flespi: icargps and reachfar together with a lot of new devices and features for already existing protocols.

I wish our users a great work and life balance, a wonderful and beautiful Christmas time, and of course a great & safe New Year party!