EnOcean USB300 - How to connect to OR

Hello Forum,

I have a quite stable OR v.2.6 running with all types of sensors and devices, but I have no clue how to use the USB300 enOcean Tranceiver inside OR.
The USB device is correctly recognized by the Raspberry Pi (latest Raspian Strecth Lite image):

$ lsusb
Bus 001 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC

But now I do not know at all how to continue. I have a simple window contact to integrate. That contact has two possible profiles to use:

  • EnOcean, Equipment Profile (EEP), A5-14-01 (4BS)
  • EnOcean, Equipment Profile (EEP), D5-00-01 (1BS)
    Can anybody give me a hint or a link how to see in OR the status of that contact (1BS) and as well the battery status (4BS)?

Thanks a lot in advance.


Hi again,

meanwhile I found that page
and I managed to do all the settings which are described there. The enOcean log file shows

INFO 2017-09-08 23:09:00,157 (EnOcean): Started reader thread for port [COM port: /dev/ttyUSB0, Protocol: ESP3, Communication Layer: RXTX]
INFO 2017-09-08 23:09:00,209 (EnOcean): Received EnOcean gateway base ID : 0xFFA7B880

so I think I connected the USB 300 correctly. I have created an OR device (enOcean command) with

DeviceID: 0x00002600
EnOceanCommand: CO
EEP: D5-00-01

All this is read via a custom sensor, but I do not receive ‘0’ or ‘1’. The log file says the following:

WARN 2017-09-08 23:22:35,699 (EnOcean): Unknown EnOcean property ‘’.
WARN 2017-09-08 23:22:35,699 (EnOcean): Unknown EnOcean property ‘’.
WARN 2017-09-08 23:22:35,699 (EnOcean): Unknown EnOcean property ‘’.
INFO 2017-09-08 23:22:35,700 (EnOcean): Created EnOcean Command (ID = ‘0x00002600’, EEP (Type = ‘D5-00-01’, Contact = ‘N/A’)).

I am not sure what I have to enter as DeviceID. The label on the contact says
VDC: H116001


The device ID looks strange to me. Mine look like 0x0087950A or 0x008B78CD. More significant digits than you have. I use the following procedure to find IDs: I try to send some telegrams and look in the log file what was received. The corrected Id should be there.

Hi Michal,

meanwhile I found the correct device ID (0x01A90837), but all kind of sensors for that window contact are still reporting N/A. Is there anything else what I can do to see that it communicated to OR correctly.

I used DolphinView Basic in Windows for checking the correct function of the window contact and that all works fine.

now I got it. The USB dongle was recognized as /dev/ttyUSB1 and not as /dev/ttyUSB0.


last comment:
is there a way to make OR compatible to enOcean Profile (EEP) A5-14-01 ?
OR and my window contact works with D5-00-01, but the A5-14-01 would as well broadcast the battery status.

Is there a way that I can make that by myself?


Does the device support two profiles (D5-00-01 and A5-14-01) ? This would mean the device has to send two telegrams. Hard to imagine that it works like this.

No, the device supports two profiles. It can be either or. The profile A5-14-01 sends more than just OPEN & CLOSED, it is as well transmitting the battery status. So is there a way in OR to read that profile as well?