OpenHab 3.0.0 and Enocean Binding ignoring sender id

Hi Markus, what kind of enocean bridge are you using? FAM14?? FGW-USB?

@damator Im using Enocean PI as a Gateway:

for debugging you have to do the following by using putty:

sudo openhab-cli console
log:set DEBUG org.openhab.binding.enocean

Then you can see much more debugs messages. Your setup is not the same as my setup so I don’t know if I can help much more…

Why do you have configured a rockerswitch (enocean:rockerSwitch:64fddb7ded:rockerswitchB) ?

Normally you’d link e.g. a dimmer-item to the channel of the actor and control it via this only.

Maybe it is a procedural error. I always create an equipment from thing and add it to my OpenHab model and then the rockerswitch is automatically created.

Try this:
Add an enocean thing. Then go the things settings and select a channel. Link your desired channel to a new created item.
That’s it, now you should be able to control your thing via the item.

Thx for the hint @dirkdirk . But the behaviour is exactly the same like in my approach.@damator I also added this line via console, But I do not get any Enocean packets on the console.

Best regards

hi markus, try to restart openhab…

Tried did not help seems I am stuck

Then I’d go back: delete all things besides one (eg spots wohnzimmer), all rockers all items. Then create item and link to dimmer-channel of the one thing like mentioned by dirkdirk.
Then test if that works.

After that add complexity by adding additional things and items.

Do not know if anyone is still reading. But i want to give you an update. Created two central Switches:

Switch1:

UID: enocean:centralCommand:643fcc16fa
label: Schreibtischlampe
thingTypeUID: enocean:centralCommand
configuration:
  enoceanId: 058F6CB8
  senderIdOffset: 1
 suppressRepeating: true
 sendingEEPId: A5_38_08_01
 receivingEEPId: F6_00_00
 broadcastMessages: true
bridgeUID: enocean:bridge:6f9bd4b35d

Switch 2:

UID: enocean:centralCommand:6f9bd4b35d:8369d60d25
label: Partylampe
thingTypeUID: enocean:centralCommand
configuration:
  enoceanId: 0591BAE3
  senderIdOffset: 2
  suppressRepeating: true
  sendingEEPId: A5_38_08_01
  receivingEEPId: F6_00_00
  broadcastMessages: true
bridgeUID: enocean:bridge:6f9bd4b35d

Put first switch in learningmode and sent teachin message:

Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2021-02-03 22:18:31.624 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type                     RADIO_ERP1, payload A5E0400080000000010F01FFFFFFFFFF00
2021-02-03 22:18:31.626 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Sending raw data: 55000A0701EBA5E0400080000000010F01FFFFFFFFFF00AD
2021-02-03 22:18:31.637 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2021-02-03 22:18:31.639 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 1 optional length 0 packet type 2
2021-02-03 22:18:31.641 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 00 received
2021-02-03 22:18:31.643 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Response without listener
2021-02-03 22:18:31.865 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2021-02-03 22:18:31.867 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 10 optional length 7 packet type 1
2021-02-03 22:18:31.871 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG _4BS for 058F6CB8 payload A51AEBF708058F6CB80000FFFFFFFF5000 received
2021-02-03 22:18:33.118 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2021-02-03 22:18:33.120 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 14 optional length 7 packet type 1
2021-02-03 22:18:33.124 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG MSC for  payload D100D0FE0303000000058F6CB80000FFFFFFFF4A00 received

Put second switch in learningmode and sent teachin message:

2021-02-03 22:23:29.548 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2021-02-03 22:23:29.551 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type RADIO_ERP1, payload A5E0400080000000020F01FFFFFFFFFF00
2021-02-03 22:23:29.554 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Sending raw data: 55000A0701EBA5E0400080000000020F01FFFFFFFFFF0026
2021-02-03 22:23:29.562 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2021-02-03 22:23:29.564 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 1 optional length 0 packet type 2
2021-02-03 22:23:29.567 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 00 received
2021-02-03 22:23:29.568 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Response without listener
2021-02-03 22:23:29.793 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2021-02-03 22:23:29.795 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 10 optional length 7 packet type 1
2021-02-03 22:23:29.799 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG _4BS for 0591BAE3 payload A51AEBF7080591BAE30000FFFFFFFF3900 received
2021-02-03 22:23:31.317 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2021-02-03 22:23:31.319 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 14 optional length 7 packet type 1
2021-02-03 22:23:31.323 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG MSC for  payload D100D0FE03030000000591BAE30000FFFFFFFF3A00 received

If you compare the teachin msg it looks good:
A5E0400080000000010F01FFFFFFFFFF00
A5E0400080000000020F01FFFFFFFFFF00

After sending the teachin the actuator confirms that learning has been done.

Now I want to switch on my first actuator (SenderId 1) I use the associated Switch Channel which I link to an Item:

This is what happens on the Physical Layer:

2021-02-03 22:31:32.825 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2021-02-03 22:31:32.827 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type RADIO_ERP1, payload A501000009000000010F01FFFFFFFFFF00
2021-02-03 22:31:32.829 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Sending raw data: 55000A0701EBA501000009000000010F01FFFFFFFFFF0032
2021-02-03 22:31:32.840 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2021-02-03 22:31:32.843 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 1 optional length 0 packet type 2
2021-02-03 22:31:32.845 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RESPONSE with code RET_OK payload 00 received
2021-02-03 22:31:32.847 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Response without listener
2021-02-03 22:31:33.138 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2021-02-03 22:31:33.141 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 7 optional length 7 packet type 1
2021-02-03 22:31:33.144 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG RPS for 058F6CB8 payload F670058F6CB83000FFFFFFFF4400 received
2021-02-03 22:31:33.146 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - ESP Packet payload F670058F6CB830 for 058F6CB8 received
2021-02-03 22:31:33.233 [TRACE] [ernal.transceiver.EnOceanTransceiver] - Received Sync Byte
2021-02-03 22:31:33.236 [TRACE] [ernal.transceiver.EnOceanTransceiver] - >> Received header, data length 7 optional length 7 packet type 1
2021-02-03 22:31:33.239 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG RPS for 0591BAE3 payload F6700591BAE33000FFFFFFFF3C00 received
2021-02-03 22:31:33.241 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - ESP Packet payload F6700591BAE330 for 0591BAE3 received

On Message is sent with the correct SenderId:

A501000009000000010F01FFFFFFFFFF00

But both actuators turn on the light. I am not able to control them independantly with the SenderId. Same happens if I toggle the switch on the other Thing.

In the log you can see that both actuators are giving feedback:

2021-02-03 22:31:33.144 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG RPS for 058F6CB8 payload F670058F6CB83000FFFFFFFF4400 received
2021-02-03 22:31:33.239 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG RPS for 0591BAE3 payload F6700591BAE33000FFFFFFFF3C00 received

I am out of ideas and disappointed. Maybe I should give a try to alternatives.

I assume you cleared all previously taught-in sensors in your actuators before you did the teach-in ?

Yes. I did this with the delete procedure of the actuator.

How do you do the teach-in ?
Telegram for teach-in of TF61L looks quite different in the docs from what you sent to the device :

GFVS: Lerntelegramm 0xE0400D80,

I use the teach in already created when using centralCommand.I checked the manual and you are right. The value might be wrong.

Try another sub-EEP, perhaps the binding already has this teach-in message built-in.

HIghly appreciate you fast answers. But I have to ask stupid was is sub_EEP?
I saw you can configure the Channel. So I tried to modify it by doing this:

This translates into this message:

A5E0400D80000000010F01FFFFFFFFFF00

But Problem still exists.

Enocean EEPs are normally 3 bytes : A5-38-08. The binding handles vendor “enhancements” by adding a “sub-type” or “command” eg. distinguish switching and dimming for central-command:

But I think you should first follow my advise and only configure one thing/actuator and try if that works and only switches the one actuator. In the log it looks it really sends one telegram containing the senderoffset “1”. If on that single message both actuators react AND you did not even have the 2nd actuator configured in OH, then clearly the 2nd actuator is not memory-cleared correctly,

If that works, reverse it: remove actuator 1 from OH and try to switch only actuator 2. If the first also reacts, then again this one is not factory-reset properly.

Only after these two steps are successfully completed, define both actuators simultaniously and see if they both only react on messages directed to them.

Hi double checked this.

only switches the one actuator.

Memory deleted both actuators. No reaction on the switches Anymore.
Remove all things. Create actuator A again. Send TeachIn.
Works like a charm. Light can be switched on without the other being switched on. (Actuator B still in learning mode)

Remove actuator 1 from OH
Add actuator B with senderid offset 20 to openhab
Put B in Learning Mode teachin (A is not in learning mode and not configured in OH) - Feedback from B is positive
Switch only B: Light from B and A are going on. (Remember A is not even registered in OH anymore). I
If I do additional factory reset on A it is not stwiched anymore. Next Test I will try sub command 2 if this is not working I will switch to FHEM and test there.

Thank you again for your patient support.

Caution: if you have actor B in learning mode while switching A, B is taught in to “follow” A if A sends ack telegrams. This happens on Enocean-level without any influence of OH.