Signalfluss

EnOcean sensor (868 MHz)
  ↓  radio telegram (Sender ID + EEP payload)
EnOcean KNX Gateway
  ↓  EEP decode: extract temperature, on/off, lux value
  ↓  DPT conversion: scale to correct KNX data type
  ↓  KNX TP group telegram → group address
KNX bus (all devices on TP line)
  ↓
KNX actuator / visualisation / logic controller

Reverse path (gateway → sensor):
  Not possible for unidirectional EnOcean sensors
  Bidirectional sensors (D2-xx-xx VLD) support response
  — requires gateway with bidirectional 868 MHz transceiver

ETS6-Kanalkonfiguration (pro EnOcean-Sender)

Channel parameters (one set per EnOcean device):

  1. Sender ID:
     — 32-bit hex address printed on sensor label
     — e.g. 0xFEF7E123
     — Or captured via PCAP (see section below)

  2. EEP selection:
     — Select from dropdown: A5-04-01, F6-02-01, D5-00-01, etc.
     — Gateway validates telegram structure against selected EEP
     — Incorrect EEP = silent decode failure (no KNX telegram sent)

  3. Sub-datapoints:
     — EEP A5-04-01 has 2 sub-DPs: temperature (DP1) and humidity (DP2)
     — Assign separate KNX group address to each sub-DP
     — Sub-DP numbering per EEP spec (EnOcean Alliance document)

  4. KNX group address assignment:
     — Drag sub-DP to group address in ETS6 group view
     — DPT automatically inferred from EEP (overrideable)

  5. Teach-in (optional for Weinzierl):
     — Weinzierl 634 supports manual ID entry (no physical learn mode)
     — Physical learn button also available for automatic ID capture

Sender-ID-Erfassung über PCAP

Equipment needed:
  EnOcean USB 300 (USB stick 868 MHz receiver)
  PC with USB port
  FT4 analyzer (EnOcean Dolphin View / FT4 software)
  or: Wireshark with EnOcean plugin

Capture procedure:
  1. Plug EnOcean USB 300 into PC
  2. Open FT4 analyzer (free download from EnOcean)
  3. Select COM port for USB 300
  4. Activate sensor (press button, cover PIR lens, open window)
  5. Telegram appears in FT4 log:
     RORG | Sender ID       | EEP data    | Status
     0xA5 | FE F7 E1 23     | 00 2A 40 08 | 0x00

  Sender ID is bytes 4–7 of the raw telegram
  (big-endian, most significant byte first)

  6. Note both Sender ID and RORG byte for EEP selection:
     0xA5 = 4BS → EEP family A5-xx-xx
     0xD5 = 1BS → EEP family D5-xx-xx
     0xF6 = RPS → EEP family F6-xx-xx

Entwurfsmuster: Ersttelegramm beim Start

Problem:
  Gateway powers on → no stored sensor values
  KNX logic controller reads group address → gets 0 or invalid
  HVAC logic may incorrectly command heating/cooling
  before first valid temperature telegram arrives (up to 10 minutes)

Solution options:

  1. Initialization delay in KNX logic:
     — Block HVAC output for first 15 minutes after bus power-on
     — Flag: "valid data received" bit set on first telegram receipt
     — All logic checks flag before using sensor value

  2. Gateway "send on startup" parameter:
     — Some gateways (Weinzierl 634) can send a "no data" telegram
     — on startup, allowing logic to detect uninitialized state

  3. Backup sensor for critical zones:
     — KNX wired room temperature sensor as fallback
     — Logic: IF EnOcean_valid = false THEN use KNX_wired_temp
     — Eliminates dependency on wireless for first-boot period

  4. Watchdog telegram monitoring:
     — ETS6 logic: if no telegram from sensor for 30 minutes → alarm
     — Prevents silent failure if sensor battery depletes (hybrid types)
     — Photovoltaic: may legitimately not transmit in darkness