Hello @alq.cev,
Thanks for your docs. I’ve tried out to do a similar example like you did but unfortunately I cannot get the thermostat values like you do with {{ state_attr('climate.tado_smart_thermostat_su0658204416', 'current_temperature') }}
Is there an official documentation what is allowed to be used as expression?
You can’t use the temperate data like that, instead it has to be used as a template.
The template syntax has to be done in the yaml editor, the visual editor can’t handle templates yet.
service: eltako.gateway_1_send_message
data:
id: FF-82-3E-69
eep: A5-10-06
current_temperature: >-
{{ state_attr('climate.tado_smart_thermostat_su0658204416', 'current_temperature') }}
target_temperature: >-
{{ state_attr('climate.tado_smart_thermostat_su0658204416', 'temperature') }}
enabled: true
Note that the “>-” is the important part for the template syntax.
Thanks, it works!
I was not aware that there is such a mighty way to do individual stuff: Templating - Home Assistant
@philipp14 First of all, thank you very much for taking on the integration of Eltako 14-RS485 in Home Assistant. My Eltako/Enocean installation is currently running on Homematic CCU3 with Cuxd and ioBroker and I would like to switch to Home Assistant. I have read all your instructions and I am now stuck on the correct configuration.yaml file. My actuators are FSB14, FSR14 and FUD14. They are controlled via the FAM USB gateway. In your tests, there are often just a few actuators in the ideal sequence. Unfortunately, this is not the case with my installation. The electrician left me this constellation. In which order do I have to create the configuration.yaml? In my installation, do I first have to create all FSB14s, then all FSR14s and then all FUD14s sorted one below the other as in the PCT14, or do I have to go by the addresses?
Here are a few screenshots of my installation.
Thank you very much in advance.
Oliver
Hello @omxgit,
First of all, all your devices are supported!
You can keep the existing addresses of your previous automation. Just enter per device one of them as sender id into the HA config. Important is that in PCT14 the correct controller function is set. Which looks correct in your screenshots. (You can only use those id in conjunction with FGW14-USB oder FAM14 for FAM-USB and USB300 addresses must match to their base ids.)
In the HA config you need to group first regarding gateways. In your case probably only FGW14-USB. (Having a second gateway makes sense if you have a second bus or if you want to use features not supported by FGW14-USB.)
Then you need to group regarding HA platforms (light, switch (almost the same like light but for different purpose), cover, sensor, binary_sensor, …). Order does not matter.
Then you enter your devices/HA entities. For receiving status messages the id and eep (expected message content) needs to match. For sending commands the sender id and eep is important. Here you can use your existing ids from PCT14.
You can also try to use EnOcean Device Manager (eo_man). It can automatically generate the HA config for you by reading the memory of your devices, same what you see in PCT14. Then you would just need to replace the sender ids.
Hello @philipp14 thank you for your feedback.
I have generated a yaml file with your EnOcean Device Manager.
The FAM14 was entered as the gateway. I only have the FAM-USB, not the FGW14-USB.
The FAM-USB is connected to the Home Assistant Server via USB.
Just like before to the Homematic CCU3 / ioBroker.
I don’t know which sender IDs I should enter, and whether I can simply change the FAM14 to FAM-USB in the yaml file.
Below I send you the beginning of the generated code with my change in FAM-USB .
At the moment it does not work.
I would be very grateful for any help.
Best regards Oliver
eltako:
general_settings:
fast_status_change: False
show_dev_id_in_dev_name: False
gateway:
- id: 1
device_type: fam-usb # you can simply change fam14 to fgw14usb
base_id: FF-8C-CA-80
# comment:
devices:
light:
# Related devices: Button FE-FB-4B-94 (Type: Button, Adr: FE-FB-4B-94), FE-FB-57-BA (Type: None, Adr: FE-FB-57-BA), HA Controller FF-8C-CA-82 (Type: Smart Home, Adr: FF-8C-CA-82)
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 51
- id: 00-00-00-02
name: FSR14_4x 00-00-00-02 (1/4)
eep: M5-38-08
sender:
id: 00-00-B0-02
eep: A5-38-08
# Related devices: Button FE-FB-4B-9B (Type: Button, Adr: FE-FB-4B-9B), Button FE-FB-4F-B3 (Type: Button, Adr: FE-FB-4F-B3), Button FE-FB-47-BF (Type: Button, Adr: FE-FB-47-BF), FE-FB-57-BA (Type: None, Adr: FE-FB-57-BA), Button FF-C5-70-83 (Type: Button, Adr: FF-C5-70-83), HA Controller FF-8C-CA-83 (Type: Smart Home, Adr: FF-8C-CA-83)
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 51
- id: 00-00-00-03
name: FSR14_4x 00-00-00-03 (2/4)
eep: M5-38-08
sender:
id: 00-00-B0-03
eep: A5-38-08
# Related devices: Button FE-FB-81-12 (Type: Button, Adr: FE-FB-81-12), Button FE-FB-47-D2 (Type: Button, Adr: FE-FB-47-D2), Button FE-FB-47-C5 (Type: Button, Adr: FE-FB-47-C5), FE-FB-57-BA (Type: None, Adr: FE-FB-57-BA), Button FF-C5-70-82 (Type: Button, Adr: FF-C5-70-82), HA Controller FF-8C-CA-84 (Type: Smart Home, Adr: FF-8C-CA-84)
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 51
- id: 00-00-00-04
name: FSR14_4x 00-00-00-04 (3/4)
eep: M5-38-08
sender:
id: 00-00-B0-04
eep: A5-38-08
# Related devices: FE-FB-57-BA (Type: None, Adr: FE-FB-57-BA), Button FF-C5-70-8E (Type: Button, Adr: FF-C5-70-8E), HA Controller FF-8C-CA-85 (Type: Smart Home, Adr: FF-8C-CA-85)
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 51
- id: 00-00-00-05
name: FSR14_4x 00-00-00-05 (4/4)
eep: M5-38-08
sender:
id: 00-00-B0-05
eep: A5-38-08
You can scan all devices like you did. Then plug in fam-usb as well and connect it. It will appear in the devices list. If you then generate the config again it contains both fam14 and fam-usb. Actually you can keep both in the config. When selecting the gateway in HA you can simply choose fam-usb. Didn’t forget to plug it back in before adding it.
Hello @Philipp thanks for the quick feedback. Unfortunately I have not managed to get my " FAM-USB" to show up in the list as a gateway.
What I found out is that I seem to have a “FAM-USB” with ESP3. In your EnOcean Device Manager it was recognized as USB300.
Unfortunately, I could not get the gateway into the list as you described. Could the reason be that my gateway is neither FAM-USB nor USB300? I also noticed that the FSR14_2x are not recognized correctly.
Thank you in advance.
Oliver
When you use a transceiver with ESP3, USB300 should work for you.
What device do you exactly use? Can you send a link to the description?
Regarding your screenshot eo_man already managed to connect to com5 with ESP3 otherwise it would not appear in the list. What happens when you click ‘connect’?
Will it be displayed in the right combobox (where we can see FAM14) as well?
Regarding FSR14-2x there was a typo in my config but you can edit all entries manually if you like.
Fix is available in v0.1.20
Hi @philipp14 I just phoned the dealer/developer where I bought my FAM-USB. He told me that a FAM-USB purchased directly from Eltako only works with Eltako’s own control panel. The firmware on the FAM-USB gateway that the dealer sold me has been changed the firmware for use with other control panels. My FAM-USB has the TCM 310 chip and ESP3. The dealer is very familiar with Enocean and asked me for the developer who is developing the new HA integration. I sent him the link to your Github repository.
To the eo_man. I clicked the connect button. But my FAM-USB/USB300 gateway did not show up in the combo box where the FAM14 is.
Thank you very much for the change on the FSR14_2x.
I will try it again on the weekend.
Best regards Oliver
Hello,
I recently integrated my Eltako v14 Series into Homeassist with this cool integration - coming from IP Symcon. At the moment I can react to Input Modules FTS14EM, can use the FSR14x4 switches for switching usual lights and even my FSB14 are working for my rollos.
My only problem remaining are the FUD14 dimmers.
In my actual setting I can switch them on and off, but am not able to set them to specific values via any automation/scenes.
Here is my actual config ( under lights )
- id: 00-00-00-29
eep: A5-38-08
name: FUD14 - Arbeitszimmer
sender:
id: 00-00-B0-29
eep: A5-38-08
In Dimmer with HexID 29 I implemented B0-29 as funktion32 which is “value set by controller”.
However the integration only gives me an on/off Switch which works but no dimming buttons.
Is there any way to realize that?
I found the eltako_send_message function but do not get much further as I am unsure what Data to send.
Any easy solution? Or any idea on this?
Hi Phillipp,
Hi all,
after the release of v1.4. i tried out your solution with an USB300 as my gateway. I was able to integrate all my lights without any problems. However with my cover/shutter integration i have a problem which i cant solve on my own.
Logs:
2024-04-14 08:06:54.961 ERROR (Thread-5) [enocean.communicators.SerialCommunicator] Received ESP3 response with with return code WRONG_PARAM (3) - 0x02 ['0x3'] [] OrderedDict()
2024-04-14 08:06:56.771 ERROR (Thread-5) [enocean.communicators.SerialCommunicator] Received ESP3 response with with return code WRONG_PARAM (3) - 0x02 ['0x3'] [] OrderedDict()
2024-04-14 08:06:58.484 ERROR (Thread-5) [enocean.communicators.SerialCommunicator] Received ESP3 response with with return code WRONG_PARAM (3) - 0x02 ['0x3'] [] OrderedDict()
My setup:
HA OS → USB300 → FAM14 → FSB14
Eltako v1.4.2
My config (abstract):
eltako:
gateway:
- id: 1
base_id: FF-88-03-00
device_type: enocean-usb300
devices:
light:
- id: FF-8F-AB-01
name: F4SR14_LED FF-8F-AB-01 (1/4)
eep: M5-38-08
sender:
id: FF-88-03-01
eep: A5-38-08
cover:
- id: FF-8F-AB-96
name: FSB14 FF-8F-AB-96 (1/2)
eep: G5-3F-7F
sender:
id: FF-88-03-40
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
Sender ID is in the PCT14 with function 31.
I tried to understand the Error Message, but couldnt figure if the problem is based on my config or some other problem with the integration.
Hello @philipp14 the installation has now worked.
I can control my switches, dimmers and cover.
The USB300 gateway was not displayed in the combobox and did not appear in the file generated by eo.man.
I manually wrote the USB300 gateway into the yaml. file and it worked.
The FSR14_x2 were not recognized yet.
Unfortunately, no status is transmitted, e.g. for the lights.
I cannot see in the dashboard whether the light is on or off.
Is this intended, or am I doing something wrong?
Best regards Oliver
Hello @philipp14 and @Hersfeld,
I’m new to the home assistant universe. I’m currently trying to move my FHEM implementation to Home Assistant. The Eltako implementation in HA is working so far, many thanks to @philipp14 for the effort. I can control lights (FSR14-4) and also get the status back. With the FSB14 I can control my shutters, but I don’t get the status back, neither “open”, “closed”, the driving status nor the current position. How exactly was your solution to the problem?
Thanks for your help in advance!
Hello @uchristan2,
in this case I would check if the ids of the FSBs are correct. Some people do not consider that PCT14 shows the ids in decimal and in the config you need to enter hexadecimal numbers. This is often the issue.
Hello @philipp14 ,
Thank you very much for your quick answer. I think I configured it correctly because I also checked my configuration with the Device Manager. The only thing I adjusted is the transmitter ID, since I had already assigned one here for FHEM:
eltako:
general_settings:
fast_status_change: False
show_dev_id_in_dev_name: True
gateway:
- id: 1
base_id: FF-E4-75-80
device_type: fgw14usb # Supported gateways: gam14, fgw14usb
devices:
light:
- id: 00-00-00-09
eep: M5-38-08
name: Licht Büro
sender:
id: 00-10-00-09
eep: A5-38-08
cover:
- id: 00-00-00-13
eep: G5-3F-7F
name: Rollo Büro
sender:
id: 00-10-00-13
eep: H5-3F-7F
device_class: shutter
time_closes: 34
time_opens: 35
Unfortunately, my shutter looks like that no position is displayed (the shutter was moved all the way down and up again) and an error appears when I want to move to a certain position.
Can you spot an error in the config here?
Thank you!
Can you try 00-00-00-0D instead of 00-00-00-13 as cover id.
Sender id is correct but pct14 shows decimal values instead of hexadecimal for the addresses in the left area.
Perfect! Thats how it works. Thank you very much for your help! Now I understand it too!
Unfortunately, since my FAM14 also has an FSB14 with the ID 19(dec)/13(hex), this confused me a little!
Yes, it is!