Neverending Perpetual Motion
Share your code. npm Orgs help your team discover, share, and reuse code. Create a free org »


3.3.1 • Public • Published


an enocean implementation for node.js

full documentation, is (partly) available at the projects new homepage

The EnOcean technology is an energy harvesting wireless technology used primarily in building automation systems, and is also applied to other applications in industry, transportation, logistics and smart homes. Modules based on EnOcean technology combine micro energy converters with ultra low power electronics, and enable wireless communications between batteryless wireless sensors, switches, controllers and gateways.


to find out whats new in the latest version see the changelog

for a full documentation of the interface visit the wiki-page (Work In Progress)

for a fully functional server/client boilerplate see node-enocean-server-template


npm install node-enocean

receiving telegrams

the enocean object is an event emitter. it emits events for all kinds of things that may happen. with the following code you can listen for any type of package.

var enocean      = require("node-enocean")();

to only listen for known sensor data, use


teach in automaticly

to make a sensor known you have to bring the enocean object into a lerning state by calling .startLearning() When a sensor is successfully learned, a "learned" event is fired.


the learning phase stops after a configurable timeout. the default is 60 seconds. during runtime you can change this timeout with enocean.timeout=30

teach in by hand

you can also change a learned sensor or add a new one by hand. this only works after the ready event was fired.

        eep: "f6-02-03",
        manufacturer:"Enocean GmbH"

teach in by editing the knownSensor File

alternatvely you can also hand edit the knownSensors.json file. By default its located at ./modules/knownSensors.json.

EEP Resolvers

the enocean object has a property called .eepResolvers. This is an array which holds functions that can handle specific EEPs. When a known Sensor is received, the eep is determined form the sensorFile. Then the databytes of the telegram are passed to each resolver function one after the other until one of them returns somthing other than null. The build in resolvers implement the following eep

  • f6-03-02
  • d5-00-01
  • a5-02-01
  • a5-02-02
  • a5-02-03
  • a5-02-04
  • a5-02-05
  • a5-02-06
  • a5-02-08
  • a5-02-09
  • a5-02-0A
  • a5-02-0B
  • a5-02-10
  • a5-02-11
  • a5-02-12
  • a5-02-13
  • a5-02-14
  • a5-02-15
  • a5-02-16
  • a5-02-17
  • a5-02-18
  • a5-02-19
  • a5-02-1A
  • a5-02-1B
  • a5-02-20
  • a5-02-30
  • a5-04-01
  • a5-04-02
  • a5-04-03
  • a5-05-01
  • a5-06-01
  • a5-06-02
  • a5-06-03
  • a5-07-01
  • a5-09-04
  • a5-10-06
  • a5-11-02
  • a5-12-01
  • a5-30-01
  • d2-32-02

I will add more when i need them or find the time to add some random ones. if you need a specific eep that is currently not supported, just let me know. It will be a pleasure to add it.

you can easily implement your own eep handler, by adding a function to the .eepResolver array.

var enocean      = require("../")();  // require node-enocen
    if(eep==="a5-99-99") {
        return {
            type:"custom",value:"Hello World!"
    return null

you can test you implementation by calling enocean.getData with your implemented eep and some test data.


sending Data

sending data can be done in raw form. just pass a string to the send function.


there now is a sendAsync function which returns a promise. It therefor is thenable and yieldable so it works with frameworks like co. It can be used with ES7 async/await. sendAsync returns after sending, successful receiving is not guaranteed

async function test(){
  await enocean.sendAsync("5500010005700838")

to make it easier to send Data, there are separate modules that implement certain EEPs. The following modules are currently available.

to find out how to use them, see the examples in the example folder here or in the other modules repository.

the base address

for sending Data the base address is needed. You don't have to care about it though, because its handled automatically for you. If you are interested in the details see "sending Data" in the wiki. you can access your base address with enocean.base

the config object

the learned sensors are saved in the knownSensors.json file located in ./modules/knownSensors if you want to change the location of the file, you can pass a config object when creating the enocean object. you can also change the location of the configFile and the timeout of the learning phase.

var enocean      = require("node-enocean")({

the sensor file

the sensorFile can be an empty json file. your initial sensor file should look like this:


the config file

the configFile must contain a base address. If you don't know your base address, put "00000000" in. your initial configFile should look like this:


special thanks for supporting this project:

  • Collin Payne (complyNC)
  • Matteo Di Sabatino (
  • Rafael Kähm (


npm i node-enocean

Downloadsweekly downloads









last publish


  • avatar