Version History

FogLAMP v1


Release Date: 2019-02-21

  • FogLAMP Core

    • Performance improvements and Bug Fixes
    • Introduction of Safe Mode in case FogLAMP is accidentally configured to generate so much data that it is overwhelmed and can no longer be managed.
  • GUI

    • re-organization of screens for Health, Assets, South and North
    • bug fixes
  • South

    • Many Performance improvements, including conversion to C++
    • Modbus plugin
    • many other new south plugins
  • North

    • Compressed data via OMF
    • Kafka
  • Filters: Perform data pre-processing, and allow distributed applications to be built on FogLAMP.

    • Delta: only send data upon change
    • Expression: run a complex mathematical expression across one or more data streams
    • Python: run arbitrary python code to modify a data stream
    • Asset: modify Asset metadata
    • RMS: Generate new asset with Root Mean Squared and Peak calcuations across data streams
    • FFT (beta): execute a Fast Fourier Transform across a data stream. Valuable for Vibration Analysis
    • Many others
  • Event Notification Engine (beta)

    • Run rules to detect conditions and generate events at the edge
    • Default Delivery Mechanisms: email, external script
    • Fully pluggable, so custom Rules and Delivery Mechanisms can be easily created
  • Debian Packages for All Repo’s


Release Date: 2018-10-10


Release Date: 2018-09-25


Release Date: 2018-07-13

Fixed Issues

  • Open File Descriptiors
    • open file descriptors: Storage service did not close open files, leading to multiple open file descriptors


Release Date: 2018-07-05

New Features

  • Python version upgrade
    • python 3 version: The minimal supported python version is now python 3.5.3.
  • aiohttp python package version upgrade
    • aiohttp package version: aiohttp (version 3.2.1) and aiohttp_cors (version 0.7.0) is now being used
  • Removal of south plugins

Known Issues

  • Issues in Documentation
    • plugin documentation: testing FogLAMP requires user to first install southbound plugins necessary (CoAP, http)


Release Date: 2018-04-23

New Features

  • Changes in the REST API
    • ping Method: the ping method now returns uptime, number of records read/sent/purged and if FogLAMP requires REST API authentication.
  • Storage Layer
    • Default Storage Engine: The default storage engine is now SQLite. We provide a script to migrate from PostgreSQL in 1.1.1 version to 1.2. PostgreSQL is still available in the main repository and package, but it will be removed to an operate repository in future versions.
  • Admin and Maintenance Scripts
    • foglamp status: the command now shows what the ping REST method provides.
    • setenv script: a new script has been added to simplify the user interaction. The script is in $FOGLAMP_ROOT/extras/scripts and it is called
    • foglamp service script: a new service script has been added to setup FogLAMP as a service. The script is in $FOGLAMP_ROOT/extras/scripts and it is called foglamp.service.

Known Issues

  • Issues in the REST API
    • asset method response: the asset method returns a JSON object with asset code named asset_code instead of assetCode
    • task method response: the task method returns a JSON object with unexpected element "exitCode"


Release Date: 2018-01-18

New Features

  • Fixed aiohttp incompatibility: This fix is for the incompatibility of aiohttp with yarl, discovered in the previous version. The issue has been fixed.
  • Fixed avahi-daemon issue: Avahi daemon is a pre-requisite of FogLAMP, FogLAMP can now run as a snap or build from source without avahi daemon installed.

Known Issues

  • PostgreSQL with Snap: the issue described in version 1.0 still persists, see Known Issues in v1.0.


Release Date: 2018-01-09

New Features

  • Startup Script:
    • foglamp start script now checks if the Core microservice has started.
    • foglamp start creates a core.err file in $FOGLAMP_DATA and writes the stderr there.

Known Issues

  • Incompatibility between aiohttp and yarl when FogLAMP is built from source: in this version we use aiohttp 2.3.6 (check here). This version is incompatible with updated versions of yarl (0.18.0+). If you intend to use this version, change the requirements for aiohttp for version 2.3.8 or higher.
  • PostgreSQL with Snap: the issue described in version 1.0 still persists, see Known Issues in v1.0.


Release Date: 2017-12-11


  • All the essential microservices are now in place: Core, Storage, South, North.
  • Storage plugins available in the main repository:
    • Postgres: The storage layer relies on PostgreSQL for data and metadata
  • South plugins available in the main repository:
    • CoAP Listener: A CoAP microservice plugin listening to client applications that send data to FogLAMP
  • North plugins available in the main repository:
    • OMF Translator: A task plugin sending data to OSIsoft PI Connector Relay 1.0

Known Issues

  • Startup Script: foglamp start does not check if the Core microservice has started correctly, hence it may report that “FogLAMP started.” when the process has died. As a workaround, check with foglamp status the presence of the FogLAMP microservices.
  • Snap Execution on Raspbian: there is an issue on Raspbian when the FogLAMP snap package is used. It is an issue with the snap environment, it looks for a shared object to preload on Raspian, but the object is not available. As a workaround, a superuser should comment a line in the file /etc/ Add a # at the beginning of this line: /usr/lib/arm-linux-gnueabihf/ Save the file and you will be able to immediately use the snap.
  • OMF Translator North Plugin for FogLAMP Statistics: in this version the statistics collected by FogLAMP are not sent automatically to the PI System via the OMF Translator plugin, as it is supposed to be. The issue will be fixed in a future release.
  • Snap installed in an environment with an existing version of PostgreSQL: the FogLAMP snap does not check if another version of PostgreSQL is available on the machine. The result may be a conflict between the tailored version of PostgreSQL installed with the snap and the version of PostgreSQL generally available on the machine. You can check if PostgreSQL is installed using the command sudo dpkg -l | grep 'postgres'. All packages should be removed with sudo dpkg --purge <package>.