I have a setup with a FTS14KS as a gateway running for over a year without problems. Recently I installed a new site just the same way. It worked fine until now. After a reboot of my Odroid no messages were sent to or received from the gateway. I reinstalled the eltako integration with no effect. What could be the problem?
Edit: The problem was solved after I restored an old backup and reapplied changes.
Yesterday I had a general short circuit (for which I’m not sure about the cause, but that’s probably irrelevant), but my Linux box to which my FGW14-USB is connected, rebooted. Or that’s what I expect anyway, the openHAB instance made a new start - I should have checked for a reboot, but forgot, and now it’s too late, as I’ve rebooted since.
/dev/ttyUSB0 had also disappeared, which meant i couldn’t control my Eltako devices anymore.
So now I wonder: could the short circuit have caused the FGW14-USB to send a power surge to the Linux box’ USP port, causing problems?
Has anyone experienced something like this? Or the opposite: a general short circuit (only the ‘master’ circuit breaker was OFF, non of the ‘subsidiaries’), without issues?
Thanks for anyone’s feedback!
Unfortunately, I am very new to home assistant. I am currently switching my control center from myhomeControl (Bootup) to home assistant because my old PC crashed.
I am using FAM14 and FGW14 (IMPORTANT: not FGW14-USB) but via a COM cable that is connected to HA with an adapter to USB. And, of course, a few actors (see configuration).
I have installed everything so far, HACS and the plugin, I have read the configuration via Enocean Device Manager (eo_man), and clicked “Write HA sender to devices.”
When I then save the configuration, I get the following message: "invalid literal for int() with base 16: 00-00-B0-01 do you want to try to continue
I decided to continue for the time being.
My problem is that I can control the lights on and off (very quickly), but unfortunately HA does not show the current status of the lights, and I cannot move my blinds either.
When starting HA, the following errors appear in the log
Logger: homeassistant.components.cover
Quelle: helpers/entity_platform.py:676
Integration: Abdeckung ([Dokumentation](https://www.home-assistant.io/integrations/cover), [Probleme](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+cover%22))
Erstmals aufgetreten: 14:21:49 (14 Vorkommnisse)
Zuletzt protokolliert: 14:21:49
Error adding entity cover.eltako_gw_1_00_00_00_20 for domain cover with platform eltako
Error adding entity cover.eltako_gw_1_00_00_00_21 for domain cover with platform eltako
Error adding entity cover.eltako_gw_1_00_00_00_22 for domain cover with platform eltako
Error adding entity cover.eltako_gw_1_00_00_00_23 for domain cover with platform eltako
Error adding entity cover.eltako_gw_1_00_00_00_24 for domain cover with platform eltako
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 676, in _async_add_entities
await self._async_add_entity(
entity, False, entity_registry, config_subentry_id
)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 1002, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1380, in add_to_platform_finish
await self.async_added_to_hass()
File "/config/custom_components/eltako/device.py", line 99, in async_added_to_hass
self.load_value_initially(latest_state)
~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/config/custom_components/eltako/cover.py", line 120, in load_value_initially
raise e
File "/config/custom_components/eltako/cover.py", line 88, in load_value_initially
self._attr_current_cover_position = latest_state.attributes['current_position']
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
KeyError: 'current_position'
and one more:
Logger: eltako
Quelle: custom_components/eltako/gateway.py:253
Integration: Eltako ([Dokumentation](https://github.com/grimmpp/home-assistant-eltako), [Probleme](https://github.com/grimmpp/home-assistant-eltako/issues))
Erstmals aufgetreten: 14:21:49 (3 Vorkommnisse)
Zuletzt protokolliert: 14:38:36
EnOcean Gateway - fgw14usb (Id: 1) (FF-B0-FB-80): Maybe have wrong device id configured!
EnOcean Gateway - fam14 (Id: 2) (FF-B0-FB-80): Maybe have wrong device id configured!
my config enocean-device-manager
eltako:
general_settings:
fast_status_change: False
show_dev_id_in_dev_name: False
gateway:
- id: 1
device_type: fam14
base_id: FF-B0-FB-80
# comment: Bus Gateway
devices:
cover:
# Cover
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 31
- id: 00-00-00-17
name: FSB14 00-00-00-17 (1/2)
eep: G5-3F-7F
sender:
id: 00-00-B0-17
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
# Cover
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 31
- id: 00-00-00-18
name: FSB14 00-00-00-18 (2/2)
eep: G5-3F-7F
sender:
id: 00-00-B0-18
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
# Cover
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 31
- id: 00-00-00-19
name: FSB14 00-00-00-19 (1/2)
eep: G5-3F-7F
sender:
id: 00-00-B0-19
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
# Cover
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 31
- id: 00-00-00-1A
name: FSB14 00-00-00-1A (2/2)
eep: G5-3F-7F
sender:
id: 00-00-B0-1A
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
# Cover
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 31
- id: 00-00-00-1B
name: FSB14 00-00-00-1B (1/2)
eep: G5-3F-7F
sender:
id: 00-00-B0-1B
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
# Cover
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 31
- id: 00-00-00-1C
name: FSB14 00-00-00-1C (2/2)
eep: G5-3F-7F
sender:
id: 00-00-B0-1C
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
# Cover
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 31
- id: 00-00-00-1D
name: FSB14 00-00-00-1D (1/2)
eep: G5-3F-7F
sender:
id: 00-00-B0-1D
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
# Cover
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 31
- id: 00-00-00-1E
name: FSB14 00-00-00-1E (2/2)
eep: G5-3F-7F
sender:
id: 00-00-B0-1E
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
# Cover
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 31
- id: 00-00-00-1F
name: FSB14 00-00-00-1F (1/2)
eep: G5-3F-7F
sender:
id: 00-00-B0-1F
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
# Cover
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 31
- id: 00-00-00-20
name: FSB14 00-00-00-20 (2/2)
eep: G5-3F-7F
sender:
id: 00-00-B0-20
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
# Cover
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 31
- id: 00-00-00-21
name: FSB14 00-00-00-21 (1/2)
eep: G5-3F-7F
sender:
id: 00-00-B0-21
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
# Cover
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 31
- id: 00-00-00-22
name: FSB14 00-00-00-22 (2/2)
eep: G5-3F-7F
sender:
id: 00-00-B0-22
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
# Cover
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 31
- id: 00-00-00-23
name: FSB14 00-00-00-23 (1/2)
eep: G5-3F-7F
sender:
id: 00-00-B0-23
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
# Cover
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 31
- id: 00-00-00-24
name: FSB14 00-00-00-24 (2/2)
eep: G5-3F-7F
sender:
id: 00-00-B0-24
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
light:
# Relay
# 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-01
name: F4SR14_LED 00-00-00-01 (1/4)
eep: M5-38-08
sender:
id: 00-00-B0-01
eep: A5-38-08
# Relay
# 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: F4SR14_LED 00-00-00-02 (2/4)
eep: M5-38-08
sender:
id: 00-00-B0-02
eep: A5-38-08
# Relay
# 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: F4SR14_LED 00-00-00-03 (3/4)
eep: M5-38-08
sender:
id: 00-00-B0-03
eep: A5-38-08
# Relay
# 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: F4SR14_LED 00-00-00-04 (4/4)
eep: M5-38-08
sender:
id: 00-00-B0-04
eep: A5-38-08
# Relay
# 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: F4SR14_LED 00-00-00-05 (1/4)
eep: M5-38-08
sender:
id: 00-00-B0-05
eep: A5-38-08
# Relay
# 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-06
name: F4SR14_LED 00-00-00-06 (2/4)
eep: M5-38-08
sender:
id: 00-00-B0-06
eep: A5-38-08
# Relay
# 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-07
name: F4SR14_LED 00-00-00-07 (3/4)
eep: M5-38-08
sender:
id: 00-00-B0-07
eep: A5-38-08
# Relay
# 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-08
name: F4SR14_LED 00-00-00-08 (4/4)
eep: M5-38-08
sender:
id: 00-00-B0-08
eep: A5-38-08
# Relay
# 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-09
name: F4SR14_LED 00-00-00-09 (1/4)
eep: M5-38-08
sender:
id: 00-00-B0-09
eep: A5-38-08
# Relay
# 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-0A
name: F4SR14_LED 00-00-00-0A (2/4)
eep: M5-38-08
sender:
id: 00-00-B0-0A
eep: A5-38-08
# Relay
# 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-0B
name: F4SR14_LED 00-00-00-0B (3/4)
eep: M5-38-08
sender:
id: 00-00-B0-0B
eep: A5-38-08
# Relay
# 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-0C
name: F4SR14_LED 00-00-00-0C (4/4)
eep: M5-38-08
sender:
id: 00-00-B0-0C
eep: A5-38-08
# Relay
# 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-0D
name: F4SR14_LED 00-00-00-0D (1/4)
eep: M5-38-08
sender:
id: 00-00-B0-0D
eep: A5-38-08
# Relay
# 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-0E
name: F4SR14_LED 00-00-00-0E (2/4)
eep: M5-38-08
sender:
id: 00-00-B0-0E
eep: A5-38-08
# Relay
# 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-0F
name: F4SR14_LED 00-00-00-0F (3/4)
eep: M5-38-08
sender:
id: 00-00-B0-0F
eep: A5-38-08
# Relay
# 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-10
name: F4SR14_LED 00-00-00-10 (4/4)
eep: M5-38-08
sender:
id: 00-00-B0-10
eep: A5-38-08
# Relay
# 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-11
name: F4SR14_LED 00-00-00-11 (1/4)
eep: M5-38-08
sender:
id: 00-00-B0-11
eep: A5-38-08
# Relay
# 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-12
name: F4SR14_LED 00-00-00-12 (2/4)
eep: M5-38-08
sender:
id: 00-00-B0-12
eep: A5-38-08
# Relay
# 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-13
name: F4SR14_LED 00-00-00-13 (3/4)
eep: M5-38-08
sender:
id: 00-00-B0-13
eep: A5-38-08
# Relay
# 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-14
name: F4SR14_LED 00-00-00-14 (4/4)
eep: M5-38-08
sender:
id: 00-00-B0-14
eep: A5-38-08
# Relay
# 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-15
name: FSR14_2X 00-00-00-15 (1/2)
eep: M5-38-08
sender:
id: 00-00-B0-15
eep: A5-38-08
# Relay
# 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-16
name: FSR14_2X 00-00-00-16 (2/2)
eep: M5-38-08
sender:
id: 00-00-B0-16
eep: A5-38-08
FAM14
BA is on 2
AUTO is on 1
FGW14
is on 6
I’ve now set the FM14 to position 1 and the FGW14 to position 10 to perform another scan.
The FGW14 is now displayed in the PCT14 software, but there are no assignments stored, or does it need one?
I’m starting out with a new installation (FAM14, FGW14-USB, FTS14, FSR14, …) and I’m a bit confused which release of @philipp14 home-assistant-eltako I should use, is tested and validated to work? # v2.0.0-alpha-rc1?
HASS version: Home Assistant OS 16.2 VM in Proxmox
Edit of this message 07/10: I’ve successfully managed to setup home-assistant-eltako in my test environment using the feature-branch: git clone GitHub - grimmpp/home-assistant-eltako: Integration for Eltako 14 series in Home Assistant --branch feature-branch
Hey there. I am experiencing a similar Issue.
I can receive telegrams just fine. When switching FSB14 through wall mounted hardware switch, the telegrams come in correctly:
2025-11-01 18:49:17.553 DEBUG (SyncWorker_49) [eltako] [cover 00-00-00-0e] state: open, opening: False, closing: False, closed: False, position: 1
2025-11-01 18:49:18.379 DEBUG (Thread-3) [eltako] [Gateway] [Id: 1] Received message: <RPSMessage from 00 00 10 26, db0 = 50, status = 0x30 (T2, N, 0 repetitions)>
2025-11-01 18:49:18.555 DEBUG (Thread-3) [eltako] [Gateway] [Id: 1] Received message: <RPSMessage from 00 00 10 26, db0 = 00, status = 0x20 (T2, U, 0 repetitions)>
2025-11-01 18:49:19.534 DEBUG (Thread-3) [eltako] [Gateway] [Id: 1] Received message: <EltakoWrappedRPS from 00 00 00 0e, status 30, data 02>
2025-11-01 18:49:19.539 DEBUG (SyncWorker_9) [eltako] [cover 00-00-00-0e] G5_3F_7F - {'_state': 2, '_time': None, '_direction': None}
2025-11-01 18:49:19.540 DEBUG (SyncWorker_9) [eltako] [cover 00-00-00-0e] state: closing, opening: False, closing: True, closed: False, position: 1
That said, I can not control the devices form the Dashboard.
Up and Down buttons are grey, because the entities are not available.
I had it working once, but after a container restart I am stuck with this state. Even complete resetting home assistant didn’t help.
I’d be glad to hear any advice.
FAM14 is also on BA2 and Auto.
I’m also experiencing a strange behaviour after installing the latest bugfix a few days ago. I can control all my covers when I use my shortcuts that I implemented in HA via decluttering-card. However, I do not get back a status for all of them. Those which don’t report back an open/closed state, can’t be controlled in the Eltako integration. In the integration, the buttons are greyed out and it says that the entity is not availabe anymore. As said, just for a few covers, not for all.
In the past, everything worked smoothly, but now I’m a little bit confused.
Can you confirm it was working with the last version ?
Also do mi d Sharing, how you achieved the right side part for your covers withe open closed „Ampel“-State?
Yes, it worked fine with the last version. And as said, it still “works” - in the way that I can open and close the covers via the custom buttons I created but not directly in the Eltako integration - in my setup (FAM14, FGW14-USB, several FSB14).
I created the custom buttons by using the decluttering-card extension (available in HACS: GitHub - custom-cards/decluttering-card: 🧹 Declutter your lovelace configuration with the help of this card). After installation you can add the code to your dashboard in the raw configurator editor:
decluttering_templates:
rollo_buttons:
description: Responsives Rollosteuerungstemplate für volle Abschnittsbreite
default:
title: Rollosteuerung
card:
type: horizontal-stack
cards:
- type: custom:button-card
name: '[[title]]'
tap_action:
action: none
show_icon: false
styles:
card:
- width: 160px
- height: 40px
- background-color: transparent
- border: none
- box-shadow: none
- justify-content: start
name:
- font-size: 14px
- font-weight: normal
- justify-self: start
- text-align: left
- type: custom:button-card
icon: mdi:chevron-up
tap_action:
action: call-service
service: cover.open_cover
service_data:
entity_id: '[[entity]]'
styles:
card:
- flex: 1
- height: 40px
- border-radius: 3px
- box-shadow: none
- border: none
- type: custom:button-card
icon: mdi:pause
tap_action:
action: call-service
service: cover.stop_cover
service_data:
entity_id: '[[entity]]'
styles:
card:
- flex: 1
- height: 40px
- border-radius: 3px
- box-shadow: none
- border: none
- type: custom:button-card
icon: mdi:chevron-down
tap_action:
action: call-service
service: cover.close_cover
service_data:
entity_id: '[[entity]]'
styles:
card:
- flex: 1
- height: 40px
- border-radius: 3px
- box-shadow: none
- border: none
- type: custom:button-card
entity: '[[entity]]'
icon: mdi:circle
name: |
[[[
const pos = entity.attributes.current_position;
const state = entity.state;
if (state === 'opening' || state === 'closing') return "Fährt";
if (pos === 0) return "Zu";
if (pos === 100) return "Offen";
if (pos > 0 && pos < 100) return `${pos}%`;
return "???";
]]]
show_icon: true
show_name: true
tap_action:
action: none
styles:
card:
- flex: 1
- height: 40px
- border-radius: 3px
- box-shadow: none
- border: none
- display: flex
- flex-direction: column
- justify-content: center
- align-items: center
icon:
- width: 14px
- height: 14px
name:
- font-size: 11px
- margin-top: 2px
state:
- operator: template
value: |
[[[
return entity.state === 'opening' || entity.state === 'closing';
]]]
styles:
icon:
- color: deepskyblue
- operator: template
value: |
[[[
return entity.attributes.current_position === 0;
]]]
styles:
icon:
- color: red
- operator: template
value: |
[[[
return entity.attributes.current_position === 100;
]]]
styles:
icon:
- color: green
- operator: template
value: |
[[[
const p = entity.attributes.current_position;
return p > 0 && p < 100 && entity.state !== 'opening' && entity.state !== 'closing';
]]]
styles:
icon:
- color: orange
After adding the code you can add a new custom card and add the following code:
type: custom:decluttering-card
template: rollo_buttons
variables:
- entity: cover.eltako_gw1_00_00_00_01
- title: Raffstore Wohnzimmer
You need to add a new custom card for each cover you want to control. Hope it works fine for you. If yes, please let me know if you also can still control your covers via the custom buttons.
Hey, I am completely stomped on my FSB14 adapters and I am starting to question my sanity 
I have many shutters connected with FSB14. This seems fine.
I have use the PCT14 and eo-man without any problems and i managed to get a working config for my lights (FSR-2x). These show status and everything without fault!
My FSB - not so much. Here is a part of the config:
cover:
# Cover
# Use 'Write HA senders to devices' button or enter manually sender id in PCT14 into function group 2 with function 31
- id: FF-8A-87-82
name: FSB14 00-00-00-02 (1/2)
eep: G5-3F-7F
sender:
id: FF-C3-A7-82
eep: H5-3F-7F
device_class: shutter
time_closes: 25
time_opens: 25
In eoman the device looks like "FSB14 00-00-00-00-02 (1/2) - Address 00-00-00-02. External Address FF-8A-87-82. The Base-ID of my FAM 14 is FF-8A-87-80 so it makes perfect sense.
So what i did - i checked my config and added my USB300 with its base id(FF-C3-A7-80) and added the Sender Address to that (so adding 00-00-00-02 to FF-C3-A7-80 => FF-C3-A7-82. I cannot - for the life of me, make it work.
in PCT there is the entry with Funktion 31 for exactly that Address.
Could someone help me?
For additional information, i get in the logs:
Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:676
integration: Sensor (documentation, issues)
First occurred: 01:01:32 (1 occurrence)
Last logged: 01:01:32
Error adding entity sensor.eltako_gw1_ff_c3_a7_80_received_messages_per_session for domain sensor with platform eltako
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 676, in _async_add_entities
await self._async_add_entity(
entity, False, entity_registry, config_subentry_id
)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 915, in _async_add_entity
unit_of_measurement=entity.unit_of_measurement,
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 533, in unit_of_measurement
if self._is_valid_suggested_unit(suggested_unit_of_measurement):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 383, in _is_valid_suggested_unit
raise ValueError(
...<2 lines>...
)
ValueError: Entity <class 'custom_components.eltako.sensor.GatewayReceivedMessagesInActiveSession'> suggest an incorrect unit of measurement: Messages.
and
Logger: homeassistant.components.cover
Source: helpers/entity_platform.py:676
integration: Cover (documentation, issues)
First occurred: 01:01:32 (16 occurrences)
Last logged: 01:01:32
Error adding entity cover.eltako_gw1_ff_8a_87_a7 for domain cover with platform eltako
Error adding entity cover.eltako_gw1_ff_8a_87_a8 for domain cover with platform eltako
Error adding entity cover.eltako_gw1_ff_8a_87_a9 for domain cover with platform eltako
Error adding entity cover.eltako_gw1_ff_8a_87_aa for domain cover with platform eltako
Error adding entity cover.eltako_gw1_ff_8a_87_ab for domain cover with platform eltako
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 676, in _async_add_entities
await self._async_add_entity(
entity, False, entity_registry, config_subentry_id
)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 1002, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1380, in add_to_platform_finish
await self.async_added_to_hass()
File "/config/custom_components/eltako/device.py", line 102, in async_added_to_hass
self.load_value_initially(latest_state)
~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/config/custom_components/eltako/cover.py", line 120, in load_value_initially
raise e
File "/config/custom_components/eltako/cover.py", line 88, in load_value_initially
self._attr_current_cover_position = latest_state.attributes['current_position']
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
KeyError: 'current_position'
Thank you everyone and especially philip for working on this btw. It is awesome to have this integration and I am just feeling stupid … 
Hi,
have you solved the problem? Because i have the same
Perhaps you can answer my question:
I have FHEM and would like to switch to HA. My hardware is FAM14 with various actuators, and everything works.
Is it possible to control lamps with the USB300 and Eltako? Or do you have to connect directly to the hardware via USB?
Perhaps you can give me a quick answer!
Hi Manni,
I am sorry but I didn’t get it to work. Since last year I have switched from eltako to Shelly. Maybe someone else can help you with this problem.
Hi! I am having problems with the following setup:
FAM14 (Funk-Antennenmodul) on the upper DIN rail
Hold cable from FGW14-USB to FAM14 is connected
FGW14-USB connected via USB to Home Assistant (HAOS on Proxmox)
HA integration installed via HACS, configuration.yaml populated using eo_man export
73 devices and 261 entities appear correctly in HA
Gateway shows "Connected" with correct Base-ID FF-80-35-80
eo_man scan worked perfectly via FAM14, all devices found, HA sender IDs written to devices
Problem:
"Last Message Received: Unknown" on the gateway device in HA
No commands from HA reach the relays (lights, covers do not respond)
Cover entities show "Unknown" state
The FGW14-USB is not connected to the RS485 bus. Since it sits on a separate DIN rail from the FAM14, there are no jumper bridges connecting it to the bus. The jumper bridges on the lower DIN rail end at the last FSB14. There is a visible gap between the last FSB14 and the FGW14-USB with no jumper bridge.
Is the Hold connection between FAM14 and FGW14-USB sufficient for full bus communication, or is an additional connection required? If yes, what needs to be connected to what?
Thank you!
EUL esp3-gateway + FAM14 : sender ID offset ignored on RS485 — independent FSR14 channel control impossible
Setup:
-
Home Assistant (Docker) + Eltako integration (grimmpp)
-
Gateway: Busware EUL V2.3 (ESP32-C3, TCM515),
device_type: esp3-gateway -
Bus: FAM14 → RS485 → FSR14_4x (4-channel relay)
-
Base ID:
04-2D-74-AA
Problem: I want to control 4 FSR14 channels independently using virtual sender IDs (04-2D-74-AF, B0, B1, B2) defined in configuration.yaml.
HA logs confirm the integration sends the correct offset IDs:
Send message: <Regular4BSMessage from 04-2D-74-AF> - Serialized: a55a6b0701000008042d74af00cf
However, the FSR14 always learns 04-2D-74-AA (base ID) during teach-in, regardless of which sender HA uses. Result: all 4 channels respond simultaneously.
Root cause identified: FAM14 replaces the sender ID with its own base ID (AA) when bridging radio → RS485. So all channels learn the same ID.
Question: Is there any way to make this work with EUL (radio gateway) only, without adding a FGW14-USB/RS485 direct gateway? For example:
-
FAM14 configuration in PCT14 to preserve sender offsets?
-
Different teach-in method?
-
Or is FGW14-USB the only solution?
Anyone running this integration on a recent Home Assistant version like 2026.5 .4 or .3?
Would love to hear if your Eltako setup works as expected. Thank you.
I've managed to find the time to answer my own above question: yes 
Working with latest version on Home Assistant OS 17.3.
HACS installation fails, make sure to install via . git clone GitHub - grimmpp/home-assistant-eltako: Integration for Eltako 14 series in Home Assistant · GitHub eltako
Edit - I'm noticing a constant unusual CPU load around 30% unfortunately on the vanilla install with no Eltako actions ongoing. Rebooted in Safe Mode and then I notice the expected idle load @ 1-2%. Disabled all other add-ons and same issue.
Checked with Glances addon:
Pinned task: python3 -m homeassistant --config /config
CPU Min/Max/Mean: 0% / 37.5% / 28.1%Affinity: 0
MEM Min/Max/Mean: 21.6% / 21.7% / 21.7%Memory info: rss: 431992832 / vms: 836374528 / shared: 77295616 / text: 4096 / lib: 0 / data: 628101120 / dirty: 0@philipp14 would you perhaps be willing to help troubleshoot, please?
There is a PR that fixed the problem! https://github.com/grimmpp/home-assistant-eltako/pull/176/
Here are my ELI5 steps in HAOS with Studio Code Server addon to apply:
- open Studio Code Server
- Top left click hamburger icon -> Terminal -> New Terminal
- in bottom terminal window make sure to select bash!
- cd /config/custom_components
- git clone GitHub - grimmpp/home-assistant-eltako: Integration for Eltako 14 series in Home Assistant · GitHub eltako
- cd /config/custom_components
- git clone GitHub - grimmpp/home-assistant-eltako: Integration for Eltako 14 series in Home Assistant · GitHub eltako_pr176
- cd eltako_pr176
- git fetch origin pull/176/head:pr176
- git checkout pr176
- cp -r custom_components/eltako ../
- restart home assistant
Hi there,
I’m having issues integrating my shutters
eltako:
gateway:
- base_id: FF-DD-F2-00
device_type: fam14
devices:
cover:
- device_class: shutter
eep: G5-3F-7F
id: 00-00-00-0E
name: FSB14 - Musikzimmer Osten
sender:
eep: H5-3F-7F
id: 00-00-B1-0E
time_closes: 13
time_opens: 13
id: 1
serial_path: /dev/enocean
The base ID FF-DD-F2-00 is the only ID that works correctly and results in status updates from the shutters in HA.
The cover ID 00-00-00-0E is correct and has been verified via the log output when pressing the physical button. The cover response is received by HA as well.
The sender ID 00-00-B1-0E has been added to the FSB14 (13–14) channel 2 with function 31. However, the shutter does not react when using the HA controls.
Connection:
FAM14 --> mini USB --> router --> ser2net --> home server --> socat --> Home Assistant
This was my working OpenHab configuration:
Bridge enocean:bridge:fam14 "Eltako Bridge FAM14" [
path="rfc2217://openwrt-eg.lan:5000",
rs485BaseId="00000000",
rs485=true,
enableSmack=true,
espVersion="ESP2",
sendTeachOuts=false
] {
Thing enocean:rollershutter:actuator_music_east "Rollladenaktor Musikzimmer Osten" [
enoceanId="0000000E",
senderIdOffset=14,
sendingEEPId="A5_3F_7F_EltakoFSB",
receivingEEPId="F6_00_00","A5_3F_7F_EltakoFSB"
] {
Channels: Type rollershutter:rollershutter [shutTime=13]
}
}
Based on this, I also tried using 00-00-00-00 as the base station ID, but in that case I did not receive any status updates from the physical buttons. I also tried using 00-00-00-0E as the sender address, but this did not work either.
Any suggestions?
Logs from working OpenHAB actions
2026-07-21 09:06:08.742 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2026-07-21 09:06:08.742 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type RADIO_ERP1, payload A5000D01080000000E0001FFFFFFFFFF00
2026-07-21 09:06:08.759 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Unknown/unsupported ESP2Packet: 6B07000D01080000000E0096
2026-07-21 09:06:09.073 [DEBUG] [nternal.messages.ESP2PacketConverter] - Received ESP2 message telegram: 8B05010000000000000E30CF
2026-07-21 09:06:09.073 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Converted to: RADIO_ERP1 with RORG RPS for 0000000E
2026-07-21 09:06:09.073 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG RPS for 0000000E payload F6010000000E30 received
2026-07-21 09:06:09.073 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - ESP Packet payload F6010000000E30 for 0000000E received
2026-07-21 09:06:11.680 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2026-07-21 09:06:11.680 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type RADIO_ERP1, payload A500FF00080000000E0001FFFFFFFFFF00
2026-07-21 09:06:11.698 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Unknown/unsupported ESP2Packet: 6B0700FF00080000000E0087
2026-07-21 09:06:11.938 [DEBUG] [nternal.messages.ESP2PacketConverter] - Received ESP2 message telegram: 8B07001D010A0000000E20E8
2026-07-21 09:06:11.939 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Converted to: RADIO_ERP1 with RORG _4BS for 0000000E
2026-07-21 09:06:11.939 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG _4BS for 0000000E payload A5001D010A0000000E20 received
2026-07-21 09:06:11.939 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - ESP Packet payload A5001D010A0000000E20 for 0000000E received
2026-07-21 09:06:12.281 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2026-07-21 09:06:12.281 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type RADIO_ERP1, payload A5000D02080000000E0001FFFFFFFFFF00
2026-07-21 09:06:12.290 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Unknown/unsupported ESP2Packet: 6B07000D02080000000E0097
2026-07-21 09:06:12.911 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2026-07-21 09:06:12.911 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type RADIO_ERP1, payload A5000D02080000000E0001FFFFFFFFFF00
2026-07-21 09:06:12.955 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Unknown/unsupported ESP2Packet: 6B07000D02080000000E0097
2026-07-21 09:06:13.368 [DEBUG] [nternal.messages.ESP2PacketConverter] - Received ESP2 message telegram: 8B05020000000000000E30D0
2026-07-21 09:06:13.369 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Converted to: RADIO_ERP1 with RORG RPS for 0000000E
2026-07-21 09:06:13.369 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG RPS for 0000000E payload F6020000000E30 received
2026-07-21 09:06:13.369 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - ESP Packet payload F6020000000E30 for 0000000E received
2026-07-21 09:06:14.409 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Enqueue new send request with ESP3 type RADIO_ERP1 without callback
2026-07-21 09:06:14.409 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Sending data, type RADIO_ERP1, payload A500FF00080000000E0001FFFFFFFFFF00
2026-07-21 09:06:14.425 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Unknown/unsupported ESP2Packet: 6B0700FF00080000000E0087
2026-07-21 09:06:14.809 [DEBUG] [nternal.messages.ESP2PacketConverter] - Received ESP2 message telegram: 8B07000F020A0000000E20DB
2026-07-21 09:06:14.810 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Converted to: RADIO_ERP1 with RORG _4BS for 0000000E
2026-07-21 09:06:14.810 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG _4BS for 0000000E payload A5000F020A0000000E20 received
2026-07-21 09:06:14.810 [DEBUG] [rnal.handler.EnOceanBaseThingHandler] - ESP Packet payload A5000F020A0000000E20 for 0000000E received
Logs from Home Assistant telegrams
Jul 21 09:02:55 home hass[1156823]: 2026-07-21 09:02:55.308 DEBUG (SyncWorker_5) [eltako] [Gateway] [Id: 1] Send message: <Regular4BSMessage from FF-DD-F2-0E, data 00-0E-02-08, status = 0x00> - Serialized: a55a6b07000e0208ffddf20e0066
Jul 21 09:02:55 home hass[1156823]: 2026-07-21 09:02:55.310 DEBUG (SyncWorker_5) [eltako] [cover 00-00-00-0E] G5_3F_7F - {'_state': None, '_time': 14, '_direction': 2}
Jul 21 09:02:55 home hass[1156823]: 2026-07-21 09:02:55.310 DEBUG (SyncWorker_5) [eltako] [cover 00-00-00-0E] state: open, opening: False, closing: False, closed: False, position: 90
I changed the config for this test to:
eltako:
gateway:
- base_id: FF-DD-F2-00
device_type: fam14
devices:
cover:
- device_class: shutter
eep: G5-3F-7F
id: 00-00-00-0E
name: FSB14 - Musikzimmer Osten
sender:
eep: H5-3F-7F
id: FF-DD-F2-0E
time_closes: 13
time_opens: 13
id: 1
serial_path: /dev/enocean
Hi everyone,
I think I’ve found an issue with the current Eltako integration on recent Home Assistant versions.
Environment
- Home Assistant Green
- Home Assistant OS 18.1
- Home Assistant Core 2026.7.4
- Supervisor 2026.07.3
- FGW14-USB
- FAM14
- Base ID: FF-AD-41-80
- Repository: grimmpp/home-assistant-eltako
- Tested:
- feature-branch
- version2.1
Device
M5-38-08 actuator
YAML:
eltako:
gateway:
- id: 1
device_type: fgw14usb
serial_path: /dev/serial/by-id/...
base_id: FF-AD-41-80
devices:
light:
- id: 00-00-00-01
eep: M5-38-08
name: Hauseingang
sender:
id: 00-00-B0-01
eep: A5-38-08
What works
- Gateway connects successfully.
- Device is created.
- Teach-In Button is available.
- ID sensor is available.
- Bus communication works.
What does NOT work
The Light entity is never created.
I added debug logging inside light.py.
EltakoSwitchableLight(...) is created.
async_add_entities() receives exactly one light entity.
However, no light.* entity is registered in Home Assistant.
The device only contains:
- Teach-In Button
- ID Sensor
No Light entity.
Additional finding
Both feature-branch and version2.1 still contain the bug in
config_helpers.get_id_from_gateway_name()
which fails with:
ValueError: invalid literal for int():
'1, BaseId: FF-AD-41-80'
Parsing until the comma fixes this problem.
Has anyone successfully tested M5-38-08 on Home Assistant Core 2026.7.x?
[quote=“danielehemann-sudo, post:424, topic:49712”]
I think I’ve found an issue with the current Eltako integration on recent Home Assistant versions.
Environment
- Home Assistant Green
- Home Assistant OS 18.1
- Home Assistant Core 2026.7.4
- Supervisor 2026.07.3
- FGW14-USB
- FAM14
- Base ID: FF-AD-41-80
- Repository: grimmpp/home-assistant-eltako
- Tested:
- feature-branch
- version2.1
Device
M5-38-08 actuator
YAML:
eltako:
gateway:
- id: 1
device_type: fgw14usb
serial_path: /dev/serial/by-id/...
base_id: FF-AD-41-80
devices:
light:
- id: 00-00-00-01
eep: M5-38-08
name: Hauseingang
sender:
id: 00-00-B0-01
eep: A5-38-08
What works
- Gateway connects successfully.
- Device is created.
- Teach-In Button is available.
- ID sensor is available.
- Bus communication works.
What does NOT work
The Light entity is never created.
I added debug logging inside light.py.
EltakoSwitchableLight(...) is created.
async_add_entities() receives exactly one light entity.
However, no light.* entity is registered in Home Assistant.
The device only contains:
- Teach-In Button
- ID Sensor
No Light entity.
Additional finding
Both feature-branch and version2.1 still contain the bug in
config_helpers.get_id_from_gateway_name()
which fails with:
ValueError: invalid literal for int():
'1, BaseId: FF-AD-41-80'
Parsing until the comma fixes this problem.
Hi Philipp,
this is a follow-up to my previous post. Thanks to your previous hints I was able to fix several issues and make significant progress.
The original problems (light entity not being created and config_helpers.get_id_from_gateway_name() parsing) are now resolved.
The current issue is different and much more specific.
Environment
- Home Assistant Green
- Home Assistant OS 18.1
- Home Assistant Core 2026.7.4
- Supervisor 2026.07.3
- Repository: grimmpp/home-assistant-eltako
- FGW14-USB
- Base ID: FF-AD-41-80
Current status
The integration now works as expected regarding setup:
- Gateway connects successfully.
- Light entity is created.
- Teach-In button is available.
- Bus receive works.
- Incoming wall switch telegrams are received correctly.
To narrow down the issue I added logging to the integration.
When switching the light I can verify that the complete send path is executed:
light.py
→ device.py
→ gateway.py
→ eltakobus.serial
→ FGW14-USB
The generated telegrams are:
ON
a55a6b07010000090000b00a0036
OFF
a55a6b07010000080000b00a0035
The log shows:
DEVICE.PY send_message() reached
Gateway Send message
eltakobus.serial Sent message
So the telegram definitely leaves Home Assistant.
The actuator, however, completely ignores the telegram.
At the same time receiving telegrams from the bus works perfectly.
Question
Is there anything special about sending via FGW14-USB compared to FAM14?
Or does the generated Regular4BSMessage miss something required by an FSR14/M5-38-08 actuator?
I’m running out of ideas after several evenings of debugging and would really appreciate any hint where to continue looking.
Thanks again for maintaining this integration.