Pareto Anywhere & EnOcean Alliance Devices

EnOcean Alliance Devices

Wireless sensors that transmit data for Pareto Anywhere to make sense of.

Wirelessly monitor environmental conditions, occupancy and smart building interactions using the connectivity infrastructure and software stack of your choice.

EnOcean Alliance devices transmit identifiers and sensor data.

Pareto Anywhere middleware affords you the freedom to choose:

  • any compatible connectivity infrastructure,
  • any software stack,

processing and relaying the data between the two, in a standard format that makes sense.

Supported EnOcean Equipment Profiles (EEP)

EnOcean Alliance devices communicate using telegrams which are structured by EnOcean Equipment Profile (EEP) types. Devices transmit their identifier and additional payload data using one or more EEPs which are represented in the format XX-XX-XX.

The EEP types, and hence EnOcean Alliance devices, currently supported by Pareto Anywhere are listed below, grouped organisationally by their first character pair (the RORG).

A5-XX-XX 4BS

Devices that have an EEP beginning with A5 use 4 Byte Communication (4BS) telegrams, the following of which are currently supported:

Source of truth: /reelyactive/advlib-eep-4bs
EEP dynamb Properties Devices
A5-04-01 relativeHumidity, temperature
A5-04-02 relativeHumidity, temperature
A5-04-03 relativeHumidity, temperature EnOcean ETHSx, …
A5-04-04 relativeHumidity, temperature
A5-07-01 batteryVoltage, isMotionDetected EnoPuck, …
A5-07-02 batteryVoltage, isMotionDetected
A5-07-03 batteryVoltage, illuminance, isMotionDetected
A5-09-04 carbonDioxideConcentration, temperature, relativeHumidity EnoPuck CO2, …
A5-14-05 batteryVoltage, isMotionDetected

D1-XX-XX MSC

Devices that have an EEP beginning with D1 use Manufacturer Specific Communication (MSC) telegrams, the following of which are currently supported:

Source of truth: /reelyactive/advlib-eep-msc
EEP dynamb Properties Devices Mfr. Id
D1-07-10 batteryVoltage, passageCounts EnoSense People Counter 0x047
D1-07-11 batteryVoltage, soundPressure EnoSense Noise Sensor 0x047
D1-09-01 batteryVoltage,
carbonDioxideConcentration,
relativeHumidity,
temperature
0x047

D2-XX-XX VLD

Devices that have an EEP beginning with D2 use Variable Length Data (VLD) telegrams, the following of which are currently supported:

Source of truth: /reelyactive/advlib-eep-vld
EEP dynamb Properties Devices
D2-14-41 acceleration,
illuminance,
isContactDetected,
isMotionDetected,
relativeHumidity,
temperature
EnOcean STM 550, …
D2-14-50 pH, temperature
D2-14-51 dissolvedOxygen, temperature
D2-15-00 isMotionDetected, passageCounts

D5-XX-XX 1BS

Devices that have an EEP beginning with D5 use 1 Byte Communication (1BS) telegrams, the following of which are currently supported:

Source of truth: /reelyactive/advlib-eep-esp
EEP dynamb Properties Devices
D5-00-01 isContactDetected EnOcean EMCSx, …

F6-XX-XX RPS

Devices that have an EEP beginning with F6 use Repeated Switch Communication (RPS) telegrams, the following of which are currently supported:

Source of truth: /reelyactive/advlib-eep-rps
EEP dynamb Properties Devices
F6-02-02 isButtonPressed EnOcean ESRPx, EnOcean EDRPx, …

  On the label   Many devices will include their EEP directly on the label. If not, consult the documentation provided with the device.

  Let's integrate it!   It is straightforward to integrate any well-documented EEP into our open source /reelyactive/advlib-esp library and sub-libraries. Contact us to discuss, or simply create a GitHub pull request!

  With the USB Gateway   Our Run Pareto Anywhere on a PC tutorial provides step-by-step instructions to run on your personal computer—with the EnOcean USB Gateway. Or Run Pareto Anywhere on a Raspberry Pi instead.
Together, let's make sense of things   Get Started