Working with Eltako FAM14

[magic2910]

Hi all,
I am looking for an home Assistant addon to manage my Eltako FUD14 Dimmers and FSR14-2x connected via FAM14.
Is this possible with this addon?

[mak-gitdev]

Hi,

This is not yet available but definitely in the todo list.

See #1 and this discussion on HA forum

[Sentinel-sys]

Hi all,

is there some new information about FAM14 integration. I followed the links and read all the posts but at some point I got confussed and gave up.
I understood that there is a hacky way and a proper way to get this working. I would try the proper way but I get lost in "tech speak" :-)

Also it is quite tricky to follow along with all this forums, discussions, posts and so on.

I would like to contribute a write an wiki article of some sort. But for this I first need to understood how it works and then get it working by myself.

Anyone how is willing to help me. I have the hardware here:

FAM14
FSB14
F4SR14-LED
USB300

Installed Home Assistant and HA-enoceanmqtt-addon

Thank you
Joe

[tbarbette]

I've got the exact same setup.

First launch the enoceanmqtt with the default enoceanmqtt.conf correctly configured but don't bother adding buttons or else. The idea is to recover the baseid of your USB300 in the MQTT integration.

You'll have normally one device, look for that :

And get the base id there :

Then, with the base ID you can invent some sender IDs to create virtual switch buttons, exactly like the physical ones you probably have.
Add the following for each light (yes, it will be long). My base id is 0xFFEDA9XX. I used the number of my relays as last digits.

[relay/PorchLight]
address = 0xFFFFFFFF
sender = 0xFFEDA921
rorg    = 0xF6
func    = 0x02
type     = 0x01
virtual = 1

Then, the button will appear in Home Assistant.

A0, A1, B0, B1 are basically like pressing the 4 buttons of the physical switches.
You can start the learning process on your F4SR14-LED like the physical switches, one by one. Yes it's long and painful.

Basically now it should work, but the buttons are not very convenient... So what you want is to create virtual "template" switch. But first, for those button to reflect the state of your light, you want also to integrate the feedback from the FAM14. After actionning each interruptor (virtual or physical), you'll get a message in "response" to the switch being pressed in the enoceanmqtt log.

Why? Even if you manage to record the state when you interact with relays from HA, the physical buttons are still there and you want their feedback too.

Create "state" entities in enoceanmqtt.conf with the address, one by one:

[relay_state/Porch]
rorg    = 0xf6
func = 0x02
type = 0x01
address = 0xFFE80D01

The funny part is that it's the same device type. The reason is the FAM14 basically echo the datagram with the current state of the relay. So it appears as a switch... But it actually reflects the state of the relay :)

Okay, you get the "actioner", and the "state", let's build a nice button out of that :

switch:
  - platform: template                                                                                                                                                                                                                                        
     switches:
      porch_light:                                                                                                                                                                                                                                                        
        friendly_name: Porch power
        value_template: "{{ is_state('binary_sensor.e2m_relay_state_porch_bo_pressed', 'on') }}"
        turn_on:
          - service: select.select_option
            data:
              option: AO
            target:
              entity_id: select.e2m_relay_porchlight_action
        turn_off:
          - service: select.select_option
            data:
              option: AI
            target:
              entity_id: select.e2m_relay_porchlight_action

And tadaaam :

A bit painfull to create 24 relays, but once done it works like a charm :)

[SteffenS27]

Hi, I saw this nice post here - tried to implement the switch. History: I added virt. switches and also the state switch - I can control the light in my house via the AI and AO manual orders - but the protocoll above do not work.
What I also mentioned is that, when I press a wall switch PTM210 the sensors _AI_pressed show action, but not when I act it via the virt. switch with the manual AI (but lights do also turn on ) <-- is there something wrong?

[LutzDi]

@tbarbette

Hi Tom,

great tutorial, thx for your excellent work. I'm dealing exactly with the same setup, I have FAM14 with multiple switches and dimmers, physical rollers installed and a USB300 stick connected to HA. I see the data flowing and tried everything to configure the setup right - but unfortunately, my lights keep off... Let me mention that I'm not really familiar with HA, I'm standing at the beginning of my career :). And I'm pretty sure that I'm the problem because I didn't get the whole picture in my head.

I'm struggling with what exactly I'm triggering from HA. The roller? The switch? Which device IDs I'm using where in the config? Am I right if I say I don't need to teach HA all switches directly because I will trigger them from HA with a virtual button over the USB300 to the FAM14, what will forward the stuff to the devices I want to switch? Let's say I have the following:

• FAM14
• FSR14-2x
• FT55

I can switch on/off the light with the FT55, everything is up and running from an Eltako/Enocean perspective. Now I've configured the USB300 with HA successfully, MQTT and EnoceanMQTT add-on is running. I see the relay and the relay_state under the MQTT and in the logs I see data flowing. So until here, I think I'm on the right track. But as I said my lights keep dark.

My question would be:

I've created a virtual sender address coming from the MQTT device info as you mentioned in your guide. I just started counting the last two digits with 01

• Is this correct?

I've added a relay/eating room to the config. But:

• What exactly is the right device ID I have to enter for address?
• What exactly is the right device ID I have to enter for sender? > Here I enter the virtual ID of my MQTT device with the 01 added, correct?

I've added a relay_state/eating room to the config. But:

• What exactly is the right device ID I have to enter for address?

I've created a button like you and I see it in my dashboard. But:

• Depending on the information that I have to enter for the address coming from the answers above I need information on which entries for binary_sensor as well as data options A0/A1 I have to use...

Last but not least, what do I have to do with the USB300 stick related to the FAM14:

• Do I have to teach the FAM14 to accept messages coming from the USB300? Sorry for that silly question but it's the first time playing around with Eltakto and the USB300 stick...

I really would appreciate it if you please could lead me in the right direction because at the moment I don't understand the flow of steering Eltako stuff with HA over the existing FAM14. I really like the approach but I need help the get it up and running...

Thx a lot for your time, effort and help again. I'm looking forward to your positive answer.

CU
Lutz

[LutzDi]

@tbarbette, @Sentinel-sys, hi all,

I got it working! After thinking a bit that Enocean won't accept any message from devices that are not configured in the system I found the point: I have to configure every virtual button to the reactor of the Eltako system... Works now like a charm. This was what I didn't get... Now I know how to proceed and with PCT14 it's still boring but easier if you know what to do.

But if I'm allowed let me please ask another question:

• As I said I have also physical rollers but I didn't get the right status back in HA if I switched the light on or off with the physical roller. Which address for the state has to be configured in roller_state? The address of the physical roller or the address of the reactor?

Any idea for me?

Thx and brgds
Lutz

[LutzDi]

Hi all,

I also got the last thing about the status sorted out... Sometimes it needs only time... the trick was that I use the xxx_bo_xxx binary sensor in the button config for the status and the ID of the reactor itself in the devices.conf file. But why is the xxx_ao_xxx binary sensor not working? What is the reason for this...?

thx and brgds
Lutz

[SteffenS27]

Hi Lutz, what I made working is, that i can create the switch and I can switch between on and off (AI and AO) but what always happens is that the state of the sensor, indicated by like the example:
value_template: "{{ is_state('binary_sensor.e2m_relay_state_porch_bo_pressed', 'on') }}"
is not working because it always goes back in on position - but it is because it is only a impulse and not a permanent signal..
And even because of the ..._pressed is only activating in my system when I push the real wall switch and it is not acting using the virtual switch
Regards Steffen

[Sentinel-sys]

Hi,

thank you very much for your super detailed answer. I almost don't need to write a howto anymore... :-)

I will try that then immediately times on a test switch. But before that one more question. What exactly do you mean by the "learning process"?
Do I learn the virtual switches in my FAM14 or F4SR14-LED and map the virtual switch to the respective actuator?
If so, I probably do that via the PCT14 software, right? With this I know unfortunately also not really. Is there anything to consider?
Thanks a lot
Joe

[tbarbette]

Personnaly I use the physical white roller on the FSR14-LED but PCT14 will work too (never used it). Don't you have physical switches in the house? Didn't you program them? Or someone else did it for you?

[LutzDi]

@Sentinel-sys

Hi Joe,

did you get everything up and running with the FAM14 and HA? I just asked @tbarbette also about more help because I didn't get it working. What was the trick for you to configure everything right?

BTW: I also have a Wibutler installed at the moment... perhaps you can help me to find the right way...

thx a lot and brgds
Lutz

[Sentinel-sys]

Right.
I bought my house from a general contractor. The price also included the electrical systems, including Enocean. There was, is, even a home control, WiButler, which already controls the Eltako Enocean devices.
I would like to have that but all under one interface in Home Assistant. Therefore, here is my attempt.
One more question comes to mind. With the FSB14 I control my shutters and sun protection. Especially with the sunshade, I can also adjust the angle of the slats with a slightly longer pressure on the physical switch. Would that also work with the virtual switch? What about closing the shutters only to a certain percentage?
Questions about questions... :-)
BTW. I have here in the house PTM 210 switch.

[tbarbette]

For the shutters you can use the appropriate device type instead, but I don't know about that :)

Indeed the virtual switches work like the PTM 210, except you ignore in general the second channel.