How can I integrate bidirectional EnOcean actuators with EEP F6-02-01?

Add-ons Bindings
, ,
1

Hello everybody,

I’m still an OH3 newb, but I know about EnOcean and home automation. Does any of you know about the EnOcean bindings?

I tried to integrate an Eltako FMS14. It receives the EEP F6_02_01 and can communicate bidirectionally. The OH3-Thing is taught-in into the FAM14 / FMS14 / FMS 14 as a directional button (up/on).

If I try to integrate the FMS14 as a classic device, I can control the actuator. But I don’t see the current status. For example, if someone presses the physical EnOcean light switch, the OH3 view continues to remain as before.

If I integrate FMS14 as a switching / dimming actuator, nothing happens. The OH3-thing can neither be learned nor controlled in the FMS14. Sounds understandable to me, because in this case the wrong EEP is stored. If I change the EEP manually in the code of the thing to F6_02_01, it doesn’t work either.

Does anyone have any idea how I can integrate the actuator’s feedback channel?

It worked wonderfully with the FUD14 and FSR14 :slightly_smiling_face: but I’m struggeling to integrate the FMS14.

Gretings

2

Hi Stefan,

Unfortunately, I do not have an FMS14, but I do have other Eltako switch actuators.
If you create a thing “switching / dimming actuator” and put in the correct EnOceanID you should be able to get the current status via the “Switch” channel. If you then also teach in a correct Sender ID into you FMS14 (as GFVS) then you should also be able to control it via this Switch channel. (EEP Reveiving → PTM200 / EEP Sending → Switch)

Regards

3

Hi Wuehli,

thanks a lot for your quick response. It’s not possible to teach into FMS14 as GFVS. There is no available function even in hardware nor in the PCT14-tool. I made a screenshot of the available selections in the tool. image

I tried to define a rocker switch with this code:

UID: enocean:classicDevice:FTXMJQ88:9c28ecf770
label: 1_test_working_sender
thingTypeUID: enocean:classicDevice
configuration:
  senderIdOffset: 38
  suppressRepeating: false
  sendingEEPId: F6_02_01
  receivingEEPId: F6_02_01
bridgeUID: enocean:bridge:FTXMJQ88

I can switch the FMS14 with the Channel “Rocker Switch” / “virtualSwitchA (Switch)” - that works fine :slight_smile: but I receive no feedback signal :frowning:

Then I defined a switching/dimming actuator like this

UID: enocean:centralCommand:FTXMJQ88:c72f69b252
label: 1_test_receiver
thingTypeUID: enocean:centralCommand
configuration:
  enoceanId: FF9C7AA5
  senderIdOffset: 38
  suppressRepeating: false
  sendingEEPId: A5_38_08_01
  receivingEEPId: F6_00_00
  broadcastMessages: true
bridgeUID: enocean:bridge:FTXMJQ88

So I can’t control nor teach-in my FMS14 :frowning: But if I switch the FMS14 with a physical switch, I receive a feedback signal in die generalswitch-channel. :slight_smile:

So I tried to combine the codes to this one:

UID: enocean:centralCommand:FTXMJQ88:56b6c26156
label: 1_test_comb
thingTypeUID: enocean:centralCommand
configuration:
  enoceanId: FF9C7AA5
  senderIdOffset: 38
  suppressRepeating: false
  sendingEEPId: F6_02_01
  receivingEEPId: F6_00_00
  broadcastMessages: true
bridgeUID: enocean:bridge:FTXMJQ88

In this case I can’t control my FMS14, but I still receive the feedback signal.

Any further ideas? :sos:

4

Frankly im also still a beginner in openhab.
But as far as is understood the binding you can not mix up EEPs
a central command can’t send F6 thats why you can’t control it.
But have you tried to teach in your “1_test_receiver”?

Maybe @fruggy83 could help here?

5

I don’t think so. The EEP’s are mixed up for receiving and sending telegrams in standard switch/dimmer-definition. Standard-sending-eep is A5_38_08_0X, and standard-receiving-eep is F6_00_00. So they are already mixed up.

And if I choose an unknown EEP in the code-definition, I get an error-message. So I think it should be possible.

The teach-in for “1_test_receiver” was not possible. No reaction from the FMS14 in the hardware-teach-in. And even no reaction from the FMS14, if I defined the settings manually by using PCT41-Tool. :thinking:

6

Hi Stefan @Mahoni

The ClassicDevice Thing is the way to go in this case. It sends RockerSwitch messages (F6) and can listen to such messages too. However the FMS14 does not answer with RockerSwitch messages instead it uses PTM200 messages for its answers. You just did the combination for the wrong ThingType :slight_smile:

I guess you currently have to do the following:

  1. Create a ClassicDevice Thing
  2. Set PTM200 EEP (F6_00_00) for ReceivingEEP
  3. Link its RockerSwitch channel to an item
  4. Add another dummy channel for listening and set its EnOceanId to your FMS14 Id

The dummy channel will allow to receive messages from your FMS14. These messages are then handled by the PTM200 EEP.

UID: enocean:classicDevice:gtwy:d099899cd1
label: Classic Device
thingTypeUID: enocean:classicDevice
configuration:
  senderIdOffset: 10
  suppressRepeating: false
  sendingEEPId: F6_02_01
  receivingEEPId: F6_00_00
bridgeUID: enocean:bridge:ipgtwy
channels:
  - id: DummyChannel
    channelTypeUID: enocean:rockerswitchListenerSwitch
    label: Dummy
    description: ""
    configuration:
      enoceanId: aabbccdd

You just have to define the senderidOffet and enoceanId correctly.

Best regards
Daniel

7

Hi Daniel @fruggy83

and thanks for your response. I’m going crazy with the configuration of the FMS14 :wink:

This code is receiving messages from FMS14 (different FMS14 to above)

UID: enocean:rockerSwitch:FTXMJQ88:FF9C7A9F
label: 2_wozi_receiver
thingTypeUID: enocean:rockerSwitch
configuration:
  enoceanId: FF9C7A9F
  receivingEEPId: F6_00_00
bridgeUID: enocean:bridge:FTXMJQ88

and this classic device with a ListenerSwitch is not receiving anything. The DummyChannel remains in status “off”. But I can control my FMS14 :slight_smile:

UID: enocean:classicDevice:FTXMJQ88:6d869487a1
label: 2-Wozi-Classic Device
thingTypeUID: enocean:classicDevice
configuration:
  senderIdOffset: 32
  suppressRepeating: false
  sendingEEPId: F6_02_01
  receivingEEPId: F6_00_00
bridgeUID: enocean:bridge:FTXMJQ88
channels:
  - id: DummyChannel
    channelTypeUID: enocean:rockerswitchListenerSwitch
    label: Dummy
    description: ""
    configuration:
      enoceanId: FF9C7A9F

Any further ideas? Thanks :+1:

8

Short feedback: it’s working :slight_smile:

I had to use RockerSwitchListenerSwitchChannelB, even the hardware is connected to channel A from the FMS14 :roll_eyes:

This code is working fine:

UID: enocean:classicDevice:EnoBridge:EnOceanThing
label: Label
thingTypeUID: enocean:classicDevice
configuration:
  senderIdOffset: 127
  suppressRepeating: false
  sendingEEPId: F6_02_01
  receivingEEPId: F6_02_01
bridgeUID: enocean:bridge:EnoBridge
location: location
channels:
  - id: EnOcean_FMS14_Channel_B
    channelTypeUID: enocean:rockerswitchListenerSwitch
    label: EnOcean_FMS14_Channel_B
    description: ""
    configuration:
      channel: channelB
      enoceanId: FEDCBA

Thanks for your support! :slight_smile: