On the configuration tab, you should have an option named use_dev_name_in_entity.
Make sure this is disabled.
Hi @tluethi71,
Please go to:
- Settings
- →
Devices & Services - →
MQTT - → Click on
xx Devices(where xx is the number of MQTT devices) - → Click on any
e2m_devices - → In the
Device infosection (located top left), click on ⋮ →MQTT info - → Unfold any of the payload fields and copy the content here.
EDIT
Ok, I think there is an error in versions comparison.
It will be fixed later.
You can still share the data requested above so I can confirm that.
Thanks
hi @mak-dev
thanks for your suport. I did so… See the looooonng Payload fields 
What I noticed is the fact that the message appears after a HA restart a couple of times (30-40 times) but then it disapears again.
e2m_bewegungsmelder_flur_og _voltage (sensor.e2m_buero_bewegungsmelder_voltage)
MQTT discovery data:
Topic: homeassistant/sensor/enocean_A50703_018AE576_NONE_voltage/config
Payload
state_topic: enoceanmqtt/bewegungsmelder/flur_og
value_template: '{{ value_json.SVC | round(2) }}'
device_class: voltage
unique_id: enocean_A50703_018AE576_NONE_voltage
name: e2m_bewegungsmelder_flur_og_voltage
device:
name: e2m_bewegungsmelder_flur_og
identifiers: 018AE576
model: A5-07-03 @018AE576
manufacturer: EnOcean
configuration_url: http://tools.enocean-alliance.org/EEPViewer/profiles/A5/07/03/A5-07-03.pdf
platform: mqtt
Subscribed topics:
enoceanmqtt/bewegungsmelder/flur_og
10 zuletzt empfangene Nachrichten
Received 11:08:46
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:08:46.366638'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:08:48
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:08:48.700216'
SVC: 2.9
ILL: 21
PIRS: 1
Received 11:09:19
QoS: 0
Payload: _RSSI_: -65
_DATE_: '2023-12-10T11:09:19.180571'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:11:11
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:11:11.704795'
SVC: 2.9
ILL: 21
PIRS: 1
Received 11:11:43
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:11:43.159996'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:12:59
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:12:59.145474'
SVC: 2.9
ILL: 22
PIRS: 1
Received 11:13:34
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:13:34.948602'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:13:49
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:13:49.877166'
SVC: 2.9
ILL: 21
PIRS: 1
Received 11:14:21
QoS: 0
Payload: _RSSI_: -61
_DATE_: '2023-12-10T11:14:21.444525'
SVC: 2.9
ILL: 22
PIRS: 0
Received 11:44:15
QoS: 0
Payload: _RSSI_: -65
_DATE_: '2023-12-10T11:44:15.644098'
SVC: 2.9
ILL: 21
PIRS: 0
Transmitted messages:
e2m_bewegungsmelder_flur_og _pir (binary_sensor.e2m_buero_bewegungsmelder_pir)
MQTT discovery data:
Topic: homeassistant/binary_sensor/enocean_A50703_018AE576_NONE_pir/config
Payload
state_topic: enoceanmqtt/bewegungsmelder/flur_og
value_template: '{% if value_json.PIRS == 1 %}ON{% else %}OFF{% endif %}'
device_class: occupancy
unique_id: enocean_A50703_018AE576_NONE_pir
name: e2m_bewegungsmelder_flur_og_pir
device:
name: e2m_bewegungsmelder_flur_og
identifiers: 018AE576
model: A5-07-03 @018AE576
manufacturer: EnOcean
configuration_url: http://tools.enocean-alliance.org/EEPViewer/profiles/A5/07/03/A5-07-03.pdf
platform: mqtt
Subscribed topics:
enoceanmqtt/bewegungsmelder/flur_og
10 zuletzt empfangene Nachrichten
Received 11:08:46
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:08:46.366638'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:08:48
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:08:48.700216'
SVC: 2.9
ILL: 21
PIRS: 1
Received 11:09:19
QoS: 0
Payload: _RSSI_: -65
_DATE_: '2023-12-10T11:09:19.180571'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:11:11
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:11:11.704795'
SVC: 2.9
ILL: 21
PIRS: 1
Received 11:11:43
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:11:43.159996'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:12:59
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:12:59.145474'
SVC: 2.9
ILL: 22
PIRS: 1
Received 11:13:34
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:13:34.948602'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:13:49
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:13:49.877166'
SVC: 2.9
ILL: 21
PIRS: 1
Received 11:14:21
QoS: 0
Payload: _RSSI_: -61
_DATE_: '2023-12-10T11:14:21.444525'
SVC: 2.9
ILL: 22
PIRS: 0
Received 11:44:15
QoS: 0
Payload: _RSSI_: -65
_DATE_: '2023-12-10T11:44:15.644098'
SVC: 2.9
ILL: 21
PIRS: 0
Transmitted messages:
e2m_bewegungsmelder_flur_og _lux (sensor.e2m_buero_bewegungsmelder_lux)
MQTT discovery data:
Topic: homeassistant/sensor/enocean_A50703_018AE576_NONE_lux/config
Payload
state_topic: enoceanmqtt/bewegungsmelder/flur_og
value_template: '{{ value_json.ILL | round(1) }}'
device_class: illuminance
unit_of_measurement: lx
unique_id: enocean_A50703_018AE576_NONE_lux
name: e2m_bewegungsmelder_flur_og_lux
device:
name: e2m_bewegungsmelder_flur_og
identifiers: 018AE576
model: A5-07-03 @018AE576
manufacturer: EnOcean
configuration_url: http://tools.enocean-alliance.org/EEPViewer/profiles/A5/07/03/A5-07-03.pdf
platform: mqtt
Subscribed topics:
enoceanmqtt/bewegungsmelder/flur_og
10 zuletzt empfangene Nachrichten
Received 11:08:46
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:08:46.366638'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:08:48
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:08:48.700216'
SVC: 2.9
ILL: 21
PIRS: 1
Received 11:09:19
QoS: 0
Payload: _RSSI_: -65
_DATE_: '2023-12-10T11:09:19.180571'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:11:11
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:11:11.704795'
SVC: 2.9
ILL: 21
PIRS: 1
Received 11:11:43
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:11:43.159996'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:12:59
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:12:59.145474'
SVC: 2.9
ILL: 22
PIRS: 1
Received 11:13:34
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:13:34.948602'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:13:49
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:13:49.877166'
SVC: 2.9
ILL: 21
PIRS: 1
Received 11:14:21
QoS: 0
Payload: _RSSI_: -61
_DATE_: '2023-12-10T11:14:21.444525'
SVC: 2.9
ILL: 22
PIRS: 0
Received 11:44:15
QoS: 0
Payload: _RSSI_: -65
_DATE_: '2023-12-10T11:44:15.644098'
SVC: 2.9
ILL: 21
PIRS: 0
Transmitted messages:
e2m_bewegungsmelder_flur_og _rssi (sensor.e2m_buero_bewegungsmelder_rssi)
MQTT discovery data:
Topic: homeassistant/sensor/enocean_A50703_018AE576_NONE_rssi/config
Payload
state_topic: enoceanmqtt/bewegungsmelder/flur_og
value_template: '{{ value_json._RSSI_ }}'
unit_of_measurement: dBm
device_class: signal_strength
entity_category: diagnostic
unique_id: enocean_A50703_018AE576_NONE_rssi
name: e2m_bewegungsmelder_flur_og_rssi
device:
name: e2m_bewegungsmelder_flur_og
identifiers: 018AE576
model: A5-07-03 @018AE576
manufacturer: EnOcean
configuration_url: http://tools.enocean-alliance.org/EEPViewer/profiles/A5/07/03/A5-07-03.pdf
platform: mqtt
Subscribed topics:
enoceanmqtt/bewegungsmelder/flur_og
10 zuletzt empfangene Nachrichten
Received 11:08:46
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:08:46.366638'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:08:48
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:08:48.700216'
SVC: 2.9
ILL: 21
PIRS: 1
Received 11:09:19
QoS: 0
Payload: _RSSI_: -65
_DATE_: '2023-12-10T11:09:19.180571'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:11:11
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:11:11.704795'
SVC: 2.9
ILL: 21
PIRS: 1
Received 11:11:43
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:11:43.159996'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:12:59
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:12:59.145474'
SVC: 2.9
ILL: 22
PIRS: 1
Received 11:13:34
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:13:34.948602'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:13:49
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:13:49.877166'
SVC: 2.9
ILL: 21
PIRS: 1
Received 11:14:21
QoS: 0
Payload: _RSSI_: -61
_DATE_: '2023-12-10T11:14:21.444525'
SVC: 2.9
ILL: 22
PIRS: 0
Received 11:44:15
QoS: 0
Payload: _RSSI_: -65
_DATE_: '2023-12-10T11:44:15.644098'
SVC: 2.9
ILL: 21
PIRS: 0
Transmitted messages:
e2m_bewegungsmelder_flur_og _last_seen (sensor.e2m_buero_bewegungsmelder_last_seen)
MQTT discovery data:
Topic: homeassistant/sensor/enocean_A50703_018AE576_NONE_last_seen/config
Payload
state_topic: enoceanmqtt/bewegungsmelder/flur_og
value_template: >-
{{ value_json._DATE_|regex_replace(find='\..*$',
replace='')|as_datetime()|as_local() }}
device_class: timestamp
entity_category: diagnostic
unique_id: enocean_A50703_018AE576_NONE_last_seen
name: e2m_bewegungsmelder_flur_og_last_seen
device:
name: e2m_bewegungsmelder_flur_og
identifiers: 018AE576
model: A5-07-03 @018AE576
manufacturer: EnOcean
configuration_url: http://tools.enocean-alliance.org/EEPViewer/profiles/A5/07/03/A5-07-03.pdf
platform: mqtt
Subscribed topics:
enoceanmqtt/bewegungsmelder/flur_og
10 zuletzt empfangene Nachrichten
Received 11:08:46
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:08:46.366638'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:08:48
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:08:48.700216'
SVC: 2.9
ILL: 21
PIRS: 1
Received 11:09:19
QoS: 0
Payload: _RSSI_: -65
_DATE_: '2023-12-10T11:09:19.180571'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:11:11
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:11:11.704795'
SVC: 2.9
ILL: 21
PIRS: 1
Received 11:11:43
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:11:43.159996'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:12:59
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:12:59.145474'
SVC: 2.9
ILL: 22
PIRS: 1
Received 11:13:34
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:13:34.948602'
SVC: 2.9
ILL: 21
PIRS: 0
Received 11:13:49
QoS: 0
Payload: _RSSI_: -60
_DATE_: '2023-12-10T11:13:49.877166'
SVC: 2.9
ILL: 21
PIRS: 1
Received 11:14:21
QoS: 0
Payload: _RSSI_: -61
_DATE_: '2023-12-10T11:14:21.444525'
SVC: 2.9
ILL: 22
PIRS: 0
Received 11:44:15
QoS: 0
Payload: _RSSI_: -65
_DATE_: '2023-12-10T11:44:15.644098'
SVC: 2.9
ILL: 21
PIRS: 0
Thanks for the excerpt.
That confirms the issue.
Entity name should have been voltage instead of e2m_bewegungsmelder_flur_og_voltage.
EDIT: I released addon version 0.1.28-1 which should fix this issue.
Hi @all,
There is a preview version available for the support of Eltako devices.
It will later be merged in HA_enoceanmqtt 0.2.1.
In the meantime, you can use it and let me know if you have any issues.
To report an issue with this version, use the discussion panel of the repository ,or simply PM me.
EDIT: Supported Eltako devices.
Hi @mak-dev,
Thanks for all the work you put into this project! I am completely new to home assistant and currently trying to automatize the roller shutters installed in my rented flat. Currently, they are controlled using a Eltako FFD remote control where there is an entry for every room and they can be opened or closed one by one.
For the home assistant setup I use an Enocean USB 300 and I was successful to integrate it into the configuration file and I can see all the signals from the Eltako FFD remote control. My issue is now, I have no idea how to control the roller shutters with home assistant. My idea would be to check all the telegrams for the different rooms and somehow replicate this to send these telegrams via the USB 300. Is this something that would be possible? I checked all the documentation I could find but for this specific case using the FFD remote as a starting point, I was not successful. I just add a screenshot of one of the telegrams from the DolphonView if this helps:
Thank you very much in advance, it would be great if you could give me some hints on how to proceed.
Hi,
I am hoping someone can help me get this Addon working as it’s exactly what I have been looking for.
I am running HA on a Raspberry Pi 4, latest build (completely up to date as of this morning). I have a Enocean USB300 dongle plugged into a port and the USB device file was found on the Addon Config page. The dongle lights flash when I press an Enocean rocker switch. When I start the HA addon I get the follow logfile
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Preparing to start…
Retrieved devices file: /config/enoceanmqtt.devices
use_dev_name_in_entity is USER-DEFINED (false)
Starting EnOceanMQTT…
/usr/lib/python3.11/html/parser.py:170: XMLParsedAsHTMLWarning: It looks like you’re parsing an XML document using an HTML parser. If this really is an HTML document (maybe it’s XHTML?), you can ignore or filter this warning. If it’s XML, you should know that using an XML parser will be more reliable. To parse this document as XML, make sure you have the lxml package installed, and pass the keyword argumentfeatures="xml"into the BeautifulSoup constructor.
k = self.parse_starttag(i)
2024-01-26 15:33:16,388 INFO: Logging to file: /config/enoceanmqtt.log
2024-01-26 15:33:16,389 INFO: Loading config file /data/enoceanmqtt.conf
2024-01-26 15:33:16,391 DEBUG: Global config: {‘enocean_port’: ‘/dev/ttyUSB0’, ‘log_packets’: ‘true’, ‘overlay’: ‘HA’, ‘db_file’: ‘/data/enoceanmqtt_db.json’, ‘mapping_file’: ‘’, ‘ha_dev_name_in_entity’: ‘false’, ‘mqtt_discovery_prefix’: ‘homeassistant/’, ‘mqtt_host’: ‘192.168.1.211’, ‘mqtt_port’: ‘1883’, ‘mqtt_client_id’: ‘enocean_gateway’, ‘mqtt_keepalive’: ‘60’, ‘mqtt_prefix’: ‘enoceanmqtt/’, ‘mqtt_user’: ‘XXX-XX’, ‘mqtt_pwd’: ‘*****’, ‘mqtt_debug’: ‘true’}
2024-01-26 15:33:16,469 INFO: Selected overlay : Home Assistant
2024-01-26 15:33:17,573 INFO: Mapping file correctly read: /app/enocean-mqtt/enoceanmqtt/overlays/homeassistant/mapping.yaml
2024-01-26 15:33:17,574 INFO: Device database /data/enoceanmqtt_db.json correctly read/created
Exception ignored in: <function Client.del at 0x7f7d982e80>
Traceback (most recent call last):
File “/app/venv/lib/python3.11/site-packages/paho_mqtt-2.0.0rc2-py3.11.egg/paho/mqtt/client.py”, line 850, in del
self._reset_sockets()
File “/app/venv/lib/python3.11/site-packages/paho_mqtt-2.0.0rc2-py3.11.egg/paho/mqtt/client.py”, line 1083, in _reset_sockets
self._sock_close()
File “/app/venv/lib/python3.11/site-packages/paho_mqtt-2.0.0rc2-py3.11.egg/paho/mqtt/client.py”, line 1069, in _sock_close
if not self._sock:
^^^^^^^^^^
AttributeError: ‘Client’ object has no attribute ‘_sock’
Traceback (most recent call last):
File “/app/venv/bin/enoceanmqtt”, line 33, in
sys.exit(load_entry_point(‘enocean-mqtt’, ‘console_scripts’, ‘enoceanmqtt’)())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/app/enocean-mqtt/enoceanmqtt/enoceanmqtt.py”, line 121, in main
com = HACommunicator(conf, sensors)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/app/enocean-mqtt/enoceanmqtt/overlays/homeassistant/ha_communicator.py”, line 74, in init
super().init(config, sensors)
File “/app/enocean-mqtt/enoceanmqtt/communicator.py”, line 43, in init
self.mqtt = mqtt.Client(client_id=client_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: Client.init() missing 1 required positional argument: ‘callback_api_version’
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
I am not that familiar with the python error messages but it looks like there is an mqtt client set up error.
I do have the MQTT integration installed as well. This works well and I use it extensively together with my house broker (on a separated machine: 192.168.1.211). Could there be a conflict?
Many thanks in advance.
Ist it possible to use Ser2net with EnOceanMQTT?
If yes, how does the configuration must look like?
Thanks in advance.
Hello everyone
What is the model of your roller shutters ? FSB61, FSB14, FJ62 ?
With this information, I will be able to guide you to the best solution to control your shutters.
My understanding is that you have the addon installed your RPi4 and your broker is somewhere else on your local network. Right ?
So it seems that your MQTT settings of the addon are not correct.
To use an external broker, you should add under mqtt_broker:
host: <host address>
port: <host port>
user: <username>
pwd: <password>
EDIT: There seems to be an issue. I need to have a closer look and will push a fix by tomorrow.night.
Normally you could simply replace ser2net with the MQTT connection.
You can install HA_enoceanmqtt as:
- addon: in this case, the EnOcean transceiver is connected on the same machine as HA.
- docker or standalone: in this case, the EnOcean transceiver can be located on another machine far from the HA machine, for example, close to EnOcean devices.
But if your use case requires, for some reasons, to still use ser2net, then I think on the machine where HA_enoceanmqtt is installed, you could reverse the stream (kind of net2ser), to create a virtual serial port on that machine.
Then use this virtual serial port for HA_enoceanmqtt.
In this case, socat is your friend to reverse from TCP to serial.
1 Like
Awesome, thank you! Ist there an way to find out which ones they are from remote? Unfortinately I don’t have a way to access them.
Edit: I was able to find out, it’s FJ62NP-230V
My understanding is that you have the addon installed your RPi4 and your broker is somewhere else on your local network. Right ?
Correct.
To use an external broker, you should add under
mqtt_broker:
They have been added to the config page - see the Global config construct (I have X’ed out the username and passwd). I have checked that these credentials work (using MQTT Explorer).
Thanks for looking.
Hi @jacquo,
I fixed the issue I was referring to in my previous message.
Please upgrade the addon to version 0.1.28-2 and please let me know if everything is ok now.
Thanks for spotting the issue 
Hi @Automatorium,
Great you found the model.
You have two possiblities to control your shutters:
- Replicate the commands emitted by your Eltako FFD using virtual buttons already available in the current addon version.
- Send specific FJ62 commands to directly control your FJ62, only available with the preview version I talked about in this message:
Hi @mak-dev,
I think I would prefer the first option. Are you referring to the virtual devices? Could you give me a hint how to set it up for my case? I would like to send the signal via the USB300 if possible. That’s the event log I have for pressing one of the buttons on the FFD:
event_type: button_pressed
data:
id:
- 255
- 147
- 82
- 3
pushed: 1
which: 0
onoff: 0
origin: LOCAL
time_fired: “2024-01-26T18:36:04.772523+00:00”
context:
id: 01HN2EJV14MB4RZCASZK7CPMP5
parent_id: null
user_id: null
This is the log from log Viewer:
2024-01-27 12:37:21.468 DEBUG (Thread-2) [enocean.communicators.SerialCommunicator] FF:93:52:03->FF:FF:FF:FF (-83 dBm): 0x01 [‘0xf6’, ‘0x70’, ‘0xff’, ‘0x93’, ‘0x52’, ‘0x3’, ‘0x30’] [‘0x0’, ‘0xff’, ‘0xff’, ‘0xff’, ‘0xff’, ‘0x53’, ‘0x0’] OrderedDict()
2024-01-27 12:37:21.707 DEBUG (Thread-2) [homeassistant.components.enocean.dongle] Received radio packet: FF:93:52:03->FF:FF:FF:FF (-83 dBm): 0x01 [‘0xf6’, ‘0x0’, ‘0xff’, ‘0x93’, ‘0x52’, ‘0x3’, ‘0x20’] [‘0x0’, ‘0xff’, ‘0xff’, ‘0xff’, ‘0xff’, ‘0x53’, ‘0x0’] OrderedDict()
2024-01-27 12:37:21.710 DEBUG (Thread-2) [enocean.communicators.SerialCommunicator] FF:93:52:03->FF:FF:FF:FF (-83 dBm): 0x01 [‘0xf6’, ‘0x0’, ‘0xff’, ‘0x93’, ‘0x52’, ‘0x3’, ‘0x20’] [‘0x0’, ‘0xff’, ‘0xff’, ‘0xff’, ‘0xff’, ‘0x53’, ‘0x0’] OrderedDict()
Btw, do I need to add something in the field shown below in the ha_enoceanmqtt configuration? I installed the MQQT broker addon, but I am not sure how to check if it works correctly.
Hi @mak-dev , I somehow missed this experimental addon for Eltako devices…
I tried to add an FJ62NP-230V, it doesn’t work. It adds all my other devices (strangely the MQTT broker doesn’t remove the not needed devices from my previous “normal” enocean addon configuration (like virtual shutter button), I alrady restarted everything), even in the log it says “Created sensor: {‘name’: ‘enoceanmqtt/Rolladen_Wohnzimmer_Eltako’, ‘address’: 69288100, ‘model’: ‘eltako/fj62np’}” and “INFO: Succesfully connected to MQTT broker.” , but it doesnt send a subscribe like for other devices, for example “DEBUG: Sending SUBSCRIBE (d0, m1) [(b’enoceanmqtt/Taster_Flur_Virtuell/req/#', 0)]”
What did I miss there?
Confirming that the issue is fixed after the upgrade.
Thank you very much for a quick turn around. Much appreciated.
Hi,
Please install version 0.0.11 of the preview version.
I added the list of supported Eltako devices in this post:
You will get something like this for FJ62:
pairingbutton is to send the pairing telegram to the FJ62unlock_pairingbutton is to put the FJ62 into pairing modeshut_timeis the exact time required for the cover to move from top position to bottom position. It is used to compute the cover position.
Hope it helps.
Thanks for your feedback
1 Like
Hi.
Thank you very much, it’s working like a charm! I finally could integrate my Eltako devices into home assistant without any problems.
Just one minor thing (I don’t care about it tbh), in diagnostic it shows two last_seen and two rssi variables. It seems like it’s showing one from the shutter module itself and one from the buttons/status it sends back.
For your issue, I think you’ve defined two entries with the same address in your device file.
Please let me know.