Skip to content

Prerequisites and used third party libraries

Technical Requirements

The different containers of the IoTC require the Docker environment to run. Specific requirements (i.e. RAM, CPU) depend on the number of connected end points to the IoTC at runtime and their communication frequency. Typical installations (e.g. 100 connected AP, 500 EnOcean end points).

The IoTC was load tested in laboratory conditions with 200 Gateways / APs with trasnfering in total 2000 EnOcean Messages within 10 seconds. No issues or message lose was detected.

For Azure Cloud deployments we recommend to use the docker-compose.yml file listed in azure_deployment directory.

Used 3rd party components and libraries, OSS Components


  • Redis Community(
  • Python 3.8 (
  • Docker Community (
  • NGINX Community (
  • Mosquitto (

Python Libraries:

  • Async Redis (aioredis,, MIT License)
  • HIREDIS (hiredis,,BSD License)
  • Licensing (licensing,,MIT License)
  • Protobuf (protobuf,,
  • Pydantic (pydantic,,MIT License)
  • Redis (redis,,MIT License)
  • Tornado (tornado,,Apache License 2.0)
  • Flask (flask,,BSD=
  • Conexion (conexion,,
  • Azure (azure,,MIT)
  • Bitstring (bitstring,,MIT)
  • crc8 (crc8,,MIT)
  • paho-mqtt (paho-mqtt,,BSD=
  • pycryptodome (pycryptodome,,
  • Celery (celery,,