Confirmed working devices

[mak-gitdev]

This thread to list the confirmed working devices for now.

[fabi9163]

I got the following devices working:

• FSB14
• F4SR14-LED
• FSR61

Click here for a short description on how I managed to pair them:

• Prerequisites:
  • HA
    • Add-On with running configuration (enocean-port pointing to usb300 device)
  • Eltako-Hardware:
    • FAM14 (which needs to be configured to forward telegrams to modbus (Top switch "BA" for example to position 2)
    • FSB14/FSR14 to pair with
• Pairing-Steps
  • Declare your eltako-devices in devices-file configured in "devices-file" in addon configuration like following

  [myFsb14NameChannel1]
  address = 0xFF83XXXX # Id of the Actor itself which is set from the FAM14 during initialisation. You have to calculate it or search for the answer-telegram in the protocoll-tab in the addon after pressed the already working hardware-switch
  sender  = 0xFF82XXXX # unique id of the usb300 + offset
  model = eltako/FSB14
  
  [myFsb14NameChannel2]
  address = 0xFF83XXXX # same id, will be paired to selected hardware-channel in pairing-process
  sender  = 0xFF82XXXX # unique id of the usb300 + offset
  model = eltako/FSB14
  
  [myFsr14Channel1-4]
  address = 0xFF83XXXX # same id, will be paired to selected hardware-channel in pairing-process
  sender  = 0xFF82XXXX # unique id of the usb300 + offset
  model = eltako/FSR14
  
  [myFsr61]
  address = 0x0426XXXX
  sender  = 0xFF82XXXX # unique id of the usb300 + offset
  model = eltako/FSR61
  ... repeat for each cover/light
  

  • Restart addon to create new devices in HA.
  • Each device has to be paired separate to the corresponding eltako-aktor-channel
  • For FSB14 (cover-actor with 2 channels)
    • Locate the aktor which have to be paired to HA (press the already working switch and it should blink)
    • For channel 1 set the top rotary-knob to "180", for channel 2 set it to "200"
    • set the middle knob to "LRN", the FSB14 starts blinking and is in "learn"-mode
    • Open the HA-device which should be paired and klick the "_pairing" button.
    • The blinking actor should stop after some seconds.
    • Switch back the middle knob to were it was (for me it was 0)
  • For F4SR14-LED (4 channel light-aktor)
    • Locate the aktor which have to be paired to HA (press the already working switch and it should blink)
    • Set the channel you want to pair with with the buttom rotary-knob (1-4)
    • (the top rotary-knob seems to be not relevant)
    • set the middle knob to "LRN", the FSR14 starts blinking and is in "learn"-mode for the selected channel
    • Open the HA-device which should be paired and klick the "_pairing" button.
    • The blinking actor should stop after some seconds.
    • Switch back the middle knob to were it was (for me it was 3) and set the buttom-knob to where it was (for me it was "Auto")
  • For FSR61 (in wall light-aktor)
    • set the button knob to 40 (direction key)
    • set the top knob to "LRN", the FSR61 is in "learn"-mode
    • Open the HA-device which should be paired and klick the "_pairing" button.
    • The blinking actor should stop after some seconds.
    • Switch back the knobs to where they were
    • To get the actual state of the Light the acknowlege-telegram have to be enabled
      • set the top knob to CLR
      • (in less thant 10 seconds) turn the button knob 3 times counter clockwise to the end
      • LED should be 2 seconds solid on and then off

[mak-gitdev]

FSB61

0. Make sure that confirmation telegrams are enabled on your FSB61. If needed, have a look at your user manual for the procedure. Otherwise, you won't get any feedback from the cover and this won't work.
1. In the device file, add the following lines:

[myFSB61]
address = 0xYYYYYYYY # address of your FSB61
model = eltako/FSB61
sender = 0xFFXXXXXX # base id of your EnOcean transceiver + unique offset

2. Restart the addon to add your device and open the device page. You should have something like this:
   
3. Put the FSB61 into PC pairing mode (lower rotary = MAX, upper rotary = LRN). The FSB61 LED should start blinking.
4. Go to the HA device page of your FSB61 and click the pairing button. The FSB61 led should stop blinking indicating pairing success.
5. Set the FSB61 rotary switches back to your required working configuration.
6. Set shut_time to the time in seconds (adjustable by steps of 100 ms) necessary to move the cover from TOP position to BOTTOM position.
7. That's it.

FUD61

[myFUD61]
address = 0xYYYYYYYY # address of your FUD61
model = eltako/FUD61
sender = 0xFFXXXXXX # base id of your EnOcean transceiver + unique offset

[t-kern]

FD62 is also working fine with FUD61 setup

[Genesis57]

FSB61

0. Make sure that confirmation telegrams are enabled on your FSB61. If needed, have a look at your user manual for the procedure. Otherwise, you won't get any feedback from the cover and this won't work.
1. In the device file, add the following lines:

[myFSB61]
address = 0xYYYYYYYY # address of your FSB61
model = eltako/FSB61
sender = 0xFFXXXXXX # base id of your EnOcean transceiver + unique offset

2. Restart the addon to add your device and open the device page. You should have something like this:
   
3. Put the FSB61 into PC pairing mode (lower rotary = MAX, upper rotary = LRN). The FSB61 LED should start blinking.
4. Go to the HA device page of your FSB61 and click the pairing button. The FSB61 led should stop blinking indicating pairing success.
5. Set the FSB61 rotary switches back to your required working configuration.
6. Set shut_time to the time in seconds (adjustable by steps of 100 ms) necessary to move the cover from TOP position to BOTTOM position.
7. That's it.

FUD61

[myFUD61]
address = 0xYYYYYYYY # address of your FUD61
model = eltako/FUD61
sender = 0xFFXXXXXX # base id of your EnOcean transceiver + unique offset

FSB61 works fine. Tanks a lot.

[LutzDi]

FUD14

• For pairing it's needed to set the upper rotary switch to PCT and the middle rotary switch to LRN

[myFud14]
address = 0xYYYYYYYY # address of you FUD14
sender  = 0xFFXXXXXX # unique id of the usb300 + offset
model = eltako/fud14

---

FSR14-4x and FSR14-2x

• Pairing works identically with the description mentioned above for the FSR14LED

[myFSR14]
address = 0xYYYYYYYY # address of you FSR14
sender  = 0xFFXXXXXX # unique id of the usb300 + offset
model = eltako/fsr14

---

Hoppe window handle FHF

[myWindowHandle]
address = 0xYYYYYYYY #address of the window handle, has to be detected through the logs
rorg = 0xF6
func = 0x10
type = 0x00

[t-ice]

I can also confirm that FSB14 and FSR14-2 are working.
I added sender addresses via PCT14 and used the function 51 for FSR14-2 and the function 31 for FSB14.

[mak-gitdev]

@deniszlh,

I myself don't own any series 14 devices, and can't find any meaningful data from the FAM14 documentation.
My feeling is that 83:E2:A8:00 could be the EURID of the FAM14 while FF:E2:A8:10 could be one of the 128 Base IDs of the FAM14.
More details on EURID and Base ID in the EURID specification.
Here is an excerpt of that document:

EURID     EnOcean Unique Radio Identifier which is unique to every
          transmitting EnOcean radio device

Base-Id   Alternative Source-Id’s range, which can be used for sending
          instead of the EURID. The reserved Base-Id range is from
          0xFF800000 to 0xFFFFFFFE in steps of 128. A device selects a
          Base-Id and can then only use 128 Id’s from this Base-Id.

I may be wrong so once again, I hope @t-ice, @fabi9163 or @LutzDi could give you some advices.

[t-ice]

Hi together,

the Base-ID is shown in the PCT14 tool.
The address of each channel can be derived by the addresses like shown in the picture.
E.g. if your base id is 83:E2:A8:00,
then the Adr. 1- 2 from the picture is 83:E2:A8:01 for channel 1 and 83:E2:A8:02 for channel 2.
I hope this helps.

[deniszlh]

Hi, I'm making some strides but not there yet.
I confim the Base ID I get from PT14 is FF:E2:A8:00
Here what I did:

• I decided to simplify my enoceanmqtt.device doc to limit it to only one FSR14-4 for the debugging
• I used the PCT14 tool to clean all the pairing in the "ID mapping range"
• I renamed the address and sender according to @t-ice advise (starting from XX:XX:XX:01 incrementall for both address and sender) then stop/start the addon then paired only for the first lamp (FFE2A801)
• The situation now is the same (I can command the lamp from HA but have no feedback) however the logs are different... HA receive an input from FF:E2:A8:23 which is the address of another lamp but whch is not paired

Definitely something going wrong but I really can't grasp what, any thoughts? thanks in advace

Hereunder the logs when I light on the lamp:
2024-01-28 11:11:41,230 DEBUG: Received PUBLISH (d0, q0, r0, m0), 'enoceanmqtt/chambre Zoé/a5/req', ... (50 bytes)
2024-01-28 11:11:41,231 DEBUG: Got MQTT message: enoceanmqtt/chambre Zoé/a5/req
2024-01-28 11:11:41,233 DEBUG: Send Payload: clear+raw_data
2024-01-28 11:11:41,234 DEBUG: enoceanmqtt/chambre Zoé/a5: req={}
2024-01-28 11:11:41,235 DEBUG: Trigger message to: enoceanmqtt/chambre Zoé/a5
2024-01-28 11:11:41,238 DEBUG: sensor data: 01:00:00:09
2024-01-28 11:11:41,239 INFO: sending: FF:C9:00:01->FF:E2:A8:01 (-255 dBm): 0x01 ['0xa5', '0x1', '0x0', '0x0', '0x9', '0xff', '0xc9', '0x0', '0x1', '0x0'] ['0x3', '0xff', '0xe2', '0xa8', '0x1', '0xff', '0x0'] OrderedDict([('COM', {'description': 'Command ID', 'unit': '', 'value': 'Command ID 0', 'raw_value': 0}), ('TIM', {'description': 'Time in 1/10 seconds. 0 = no time specifed', 'unit': 's', 'value': 1.3877787807814457e-17, 'raw_value': 0}), ('LCK', {'description': 'Lock for duration time if time >0, unlimited time of no time specified. Locking may be cleared with "unlock". During lock phase no other commands will be accepted or executed', 'unit': '', 'value': 'Unlock', 'raw_value': 0}), ('DEL', {'description': 'Delay or duration (if Time > 0); 0 = Duration (Execute switching command immediately and switch back after duration) 1 = Delay (Execute switching command after delay)', 'unit': '', 'value': 'Duration', 'raw_value': 0}), ('SW', {'description': 'Switching command ON/OFF', 'unit': '', 'value': 'Off', 'raw_value': 0})])
2024-01-28 11:11:41,240 DEBUG: Clearing data buffer.
2024-01-28 11:11:41,340 INFO: Sending packet
2024-01-28 11:11:41,341 DEBUG: FF:C9:00:01->FF:E2:A8:01 (-255 dBm): 0x01 ['0xa5', '0x1', '0x0', '0x0', '0x9', '0xff', '0xc9', '0x0', '0x1', '0x0'] ['0x3', '0xff', '0xe2', '0xa8', '0x1', '0xff', '0x0'] OrderedDict([('COM', {'description': 'Command ID', 'unit': '', 'value': 'Command ID 0', 'raw_value': 0}), ('TIM', {'description': 'Time in 1/10 seconds. 0 = no time specifed', 'unit': 's', 'value': 1.3877787807814457e-17, 'raw_value': 0}), ('LCK', {'description': 'Lock for duration time if time >0, unlimited time of no time specified. Locking may be cleared with "unlock". During lock phase no other commands will be accepted or executed', 'unit': '', 'value': 'Unlock', 'raw_value': 0}), ('DEL', {'description': 'Delay or duration (if Time > 0); 0 = Duration (Execute switching command immediately and switch back after duration) 1 = Delay (Execute switching command after delay)', 'unit': '', 'value': 'Duration', 'raw_value': 0}), ('SW', {'description': 'Switching command ON/OFF', 'unit': '', 'value': 'Off', 'raw_value': 0})])
2024-01-28 11:11:41,444 DEBUG: 0x02 ['0x0'] [] OrderedDict()
2024-01-28 11:11:41,445 INFO: got response packet: OK
2024-01-28 11:11:42,935 DEBUG: FF:E2:A8:23->FF:FF:FF:FF (-46 dBm): 0x01 ['0xf6', '0x70', '0xff', '0xe2', '0xa8', '0x23', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x2e', '0x0'] OrderedDict()
2024-01-28 11:11:42,936 INFO: received: FF:E2:A8:23->FF:FF:FF:FF (-46 dBm): 0x01 ['0xf6', '0x70', '0xff', '0xe2', '0xa8', '0x23', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x2e', '0x0'] OrderedDict()
2024-01-28 11:11:42,939 INFO: unknown sensor: FF:E2:A8:23 (RORG = 0xf6)

hereunder the enoceanmqtt.devices

############### LAMPES ####################

[chambre Zoé]
#AB-1 lampe chambre zoé - - Addr 35
address = 0xFFE2A801 # same id, will be paired to selected hardware-channel in pairing-process
sender = 0xFFC90001 # unique id of the usb300 + offset
model = eltako/FSR14

[chambre amis]
#AB-2 lampe chambre amis - - Addr 36
address = 0xFFE2A802 # same id, will be paired to selected hardware-channel in pairing-process
sender = 0xFFC90002 # unique id of the usb300 + offset
model = eltako/FSR14

[salle a manger]
#AB-3 lampe salle a manger - - Addr 37
address = 0xFFE2A803 # same id, will be paired to selected hardware-channel in pairing-process
sender = 0xFFC90003 # unique id of the usb300 + offset
model = eltako/FSR14

[bureau]
#AB-4 lampe bureau - - Addr 38
address = 0xFFE2A804 # same id, will be paired to selected hardware-channel in pairing-process
sender = 0xFFC90004 # unique id of the usb300 + offset
model = eltako/FSR14

[t-ice]

Your address seems to be wrong (not like I previously wrote sender address, I edited this comment). Addr 35 is in hexadecimal 0x23, thus your address is FF:E2:A8:23. Maybe some broadcasting is happening that turning it on works with 0xFFE2A801 too.

[deniszlh]

@t-ice @mak-gitdev
Thank you for your help - it works now, all lights are ok and screens up/down function works too (still have to figure out what the parameters are but it's all working)
Lessons learned / I made some newbie mistakes but learned a lot, thank you:

• failing in converting decimal to Hex
• failing addressing properly the devices (I thought that using an incremental number would work without foloowing the naming found in PCT14)

Thanks again for your help, very much appreciated

[cdennig]

Hey folks,

just wanted to give feedback regarding the Eltako integration, especially for FSB14/FSR14. I have installed the addon last week and setup everything successfully for these two device types. It since then works like a charm - very good quality.

Thanks all and keep up the good work!

Chris

[sipodd]

Hi all,

i'd like to add some Information to the Eltako specific pairing:

1. You don't need to fiddle with the wheels on the Eltako modules, if you got a Laptop and PCT14 Software from the Eltako Website. Its not the most intuitive piece of software....but its usefull and you can backup your Eltako config ;-)
   Just connect the Laptop with the FAM14 using a (micro) USB Cable.

One hint: in PCT14 its important to press "Daten übernehmen" before you click on another module!

2. Some Information on the Module specific functions for the pairing:

• F4SR14: "senderadress" from device_file in Funktionsgruppe 2 - Funktion 51

• FUD14: "senderadress" from device_file in Funktionsgruppe 3 - Funktion 31

• FSB14: "senderadress" from device_file in Funktionsgruppe 2 - Funktion 31

• vSwitches get Funktion 2

here an exemple FUD14 (unfortunatly only in German)

Basically, there is only one function on each module that got the word "controller" in it...this is the one you want to pair your HA with.

• F4HK14 (not supported yet, but requested) Funktionsgruppe 3 - Funktion 65

[einfachtimo]

Hey, i am trying to run the addon but just getting this error.

[einfachtimo]

and here are the other settings...

[mak-gitdev]

@einfachtimo,

Somewhere in your device file, it seems you have an address set to 0xYYYYYYYY, which is an incorrect value

[einfachtimo]

Hey, just wanted to say that the integration works absolutely perfect!
Covers, lights and dimmers are integrated! Thank you very much!

Is it possible to use a real Enocean-Button as a trigger for a Sonos radio automation?

[mak-gitdev]

Hi @einfachtimo,

Nice you finally got it running.

Not sure I fully understood your question but the EnOcean device is available in HA and you can use it for whatever automation you want.