In the EnOcean Teach-In process, the transmitting device sends a special telegram containing its EEP and Device ID; the receiver memorises this information so it can decode later telegrams correctly and bind the sender to a specific action.
True
Teach-In is the self-commissioning workflow that replaces software binding. First the receiver (actuator) is placed into Teach mode, usually via a physical button. The transmitter (a switch or sensor) then sends a Teach-In telegram carrying its EEP and 32-bit Device ID. The receiver stores the pair (Device ID = EEP, mapped to action) in non-volatile memory, and every subsequent telegram from that sender triggers the bound action. Unlike KNX, where the binding of Group Objects to Group Addresses is performed in ETS, EnOcean Teach-In happens entirely in the field with no PC tool required.
Always log the Device ID of every taught device on a paper plan; if the receiver loses its memory after a firmware reset, you will need that list to rebuild the bindings in the right order.
EnOcean bank in preparation
The full EnOcean bank isn't available yet. Drop your email to get notified at launch and grab an early-bird discount.
Join the waitlist →See the 9 other EnOcean practice questions
Related questions
- EnOcean is best known for its battery-less devices: energy is harvested from a piezo-electric element (mechanical push-button), a solar cell (sensors with a small photovoltaic panel) or a Peltier element (thermal gradient), eliminating battery maintenance over a 10 to 20 year service life.1. Architecture · Energy Harvesting
- The EEP (EnOcean Equipment Profile) identifies each device type by a RORG-FUNC-TYPE triplet (e.g. F6-02-01 = 2-channel Rocker push-button), enabling a receiver to decode the telegram correctly without any manual configuration.2. EEP · EnOcean Equipment Profile
- ESP3 (EnOcean Serial Protocol v3) is the communication protocol between an EnOcean radio module (TCM 310 / TCM 515) and a host gateway or PC over a UART link: packets begin with the sync byte 0x55, followed by a header, a data section and a CRC8.3. ESP3 protocol · Serielles Protokoll
- EnOcean Secure uses a rolling code (an incremental counter) together with a CMAC (Cipher-based MAC built on AES-128) to authenticate every telegram and block replay attacks, which is critical for security-grade applications such as alarms and wireless locks.6. Security · Rolling Code
- ePIRE (EnOcean Profile for Initial Resync Exchange) is the standardised protocol for secure pairing during Teach-In: it covers the generation and distribution of the shared AES key between a Secure-capable transmitter and receiver.6. Security · ePIRE