New platform RF iNELS (eLan)

Supported devices - this is tricky question.

All devices are present and should be controllable over MQTT as elan2mqtt simply passes all messages both ways with no check. However that means you have to manually define them in HA configuration as template mqtt devices. From that point of view all devices are supported.

What you are more interested in is which devices are supported for autodiscovery. At the moment these are supported:

  • lights = device type set to light or dimmed light in eLan
  • thermostats = device type set to heating in eLan

I have been able to test those devices: RFSA-66M, RFDA-11B, RFSTI-11G (as heating in eLan)

For the others you have to go manual way.

If you can send me their messages for:

  • device info
  • status info
  • action commands + reply messages

I can try to add them to autodiscovery

Hello. Thank you so much for your help.
In version 1.6, all my devices were automatically added to the Home Assistant, now I see the state of the RFSTI-11g thermostat and the RFWD-100 door sensor.
If there is a template for manually adding devices, please share.
Thanks again for your work!

To manually add devices you have to follow HA documentation for MQTT integration

For example:




but there are others…

You may take look into main_worker.py where definitions are created. They are not in format required for HA config files but can give you some hints.

What is important for you is that elan2mqtt creates two topics for each device:

  • Status messages are using topic /eLan/device_mac_address/status
  • Command messages are using topic /eLan/device_mac_address/command

Device_mac_adress is the adress printed on each device (without : ) and is part of device URL seen in the web console.

If you create config for new device please share it. I’ll try to add it to autodiscovery.


For RFWD-100 I just guessed format of status message. Plese test it and if you could share full status message from it it would help. I beleive it reports more information.

1 Like

RFWD-100 from chrome developer console:

Summary

RFWD-100/state (closed door):

{alarm: true, detect: false, tamper: “closed”, automat: false, battery: true, disarm: false}
alarm: true
detect: false
tamper: “closed”
automat: false
battery: true
disarm: false

RFWD-100/state (open door):

{alarm: true, detect: true, tamper: “closed”, automat: false, battery: true, disarm: false}
alarm: true
detect: true
tamper: “closed”
automat: false
battery: true
disarm: false

Now the door sensor does not display a change in state, it is always in the off state, regardless of whether the door is open or closed.
Hope this information helps.

Yes. It helps. New version is in GIT. Hopefully it is right this time.

Hello, i’m a newbie in Home assistant, so tried to manually add RF actor, but it doesn’t work. Could you help me to figure out what is wrong? Thanks.

switch:
  - platform: mqtt
    name: Zavlaha_V1
    unique_id: eLan-211020
    state_topic: eLan/211020/status
    command_topic: eLan/211020/command
    json_attributes_topic: eLan/211020/status
    payload_off: '{"on":false}'
    payload_on: '{"on":true}'
    value_template: '{%- if value_json.on -%}{"on":true}{%- else -%}{"on":false}{%- endif -%}'
    device:
      name: Zavlaha_V1
      identifiers: eLan-switch-211020
      connections:
        - - mac
          - '211020'
      manufacturer: Elko EP
      model: RFSA-66M

Hello! After upgrading to version 1.10, elan2mqtt does not start. What can be done?
Hass Log :

20-05-12 21:32:13 ERROR (SyncWorker_4) [supervisor.docker] Can't create container from addon_964047f9_elan2mqtt: 404 Client Error: Not Found ("No such image: 964047f9/armv7-addon-elan2mqtt:1.10")

After a complete removal and reinstallation, everything worked.

Hi. i just wanted to say THANK YOU for this wonderful addon. works great (initial startup took quite som time but that is ok) and i can finnaly use something better than that stupud iNELS app.
THANX

well it was great while it lasted… was forced to migrate to RPI4 and to make a new install and since then the addon does not start with nothing more than “s6-overlay-suexec: fatal: can only run as pid 1” error in log…
i dont keep my hopes up but if you update the addon in the future i will sure test it out…

Dors this help?

well when installing localy and editing the config.yaml to include this init:false it did solve the error and addon successfully launched. setting it up right now but the stupid elko gateway keeps freezing…
but that is HW problem so thanks for the tip :slight_smile:

Please help.
Log from eLan MQTT:

what command line arguments need to be checked?

[2023-02-05 20:31:23,186] {socket_listener.py:304} ERROR - SOCKET LISTENER: Something went wrong. But don’t worry we will start over again.
Traceback (most recent call last):
File “/elan2mqtt-1.16.0/socket_listener.py”, line 302, in
asyncio.get_event_loop().run_until_complete(main())
File “/usr/local/lib/python3.10/asyncio/base_events.py”, line 646, in run_until_complete
return future.result()
File “/elan2mqtt-1.16.0/socket_listener.py”, line 143, in main
mqtt_cli.connect(mqtt_broker, 1883, 120)
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 914, in connect
return self.reconnect()
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 1044, in reconnect
sock = self._create_socket_connection()
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 3685, in _create_socket_connection
return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source)
File “/usr/local/lib/python3.10/socket.py”, line 845, in create_connection
raise err
File “/usr/local/lib/python3.10/socket.py”, line 833, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
[2023-02-05 20:31:23,187] {socket_listener.py:307} ERROR - But at first take some break. Sleeping for 5 s
[2023-02-05 20:31:28,191] {socket_listener.py:304} ERROR - SOCKET LISTENER: Something went wrong. But don’t worry we will start over again.
Traceback (most recent call last):
File “/elan2mqtt-1.16.0/socket_listener.py”, line 302, in
asyncio.get_event_loop().run_until_complete(main())
File “/usr/local/lib/python3.10/asyncio/base_events.py”, line 646, in run_until_complete
return future.result()
File “/elan2mqtt-1.16.0/socket_listener.py”, line 143, in main
mqtt_cli.connect(mqtt_broker, 1883, 120)
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 914, in connect
return self.reconnect()
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 1044, in reconnect
sock = self._create_socket_connection()
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 3685, in _create_socket_connection
return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source)
File “/usr/local/lib/python3.10/socket.py”, line 845, in create_connection
raise err
File “/usr/local/lib/python3.10/socket.py”, line 833, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
[2023-02-05 20:31:28,191] {socket_listener.py:307} ERROR - But at first take some break. Sleeping for 5 s
[2023-02-05 20:31:32,755] {main_worker.py:1067} ERROR - MAIN WORKER: Something went wrong. But don’t worry we will start over again.
Traceback (most recent call last):
File “/elan2mqtt-1.16.0/main_worker.py”, line 1065, in
asyncio.get_event_loop().run_until_complete(main())
File “/usr/local/lib/python3.10/asyncio/base_events.py”, line 646, in run_until_complete
return future.result()
File “/elan2mqtt-1.16.0/main_worker.py”, line 855, in main
mqtt_cli.connect(mqtt_broker, 1883, 120)
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 914, in connect
return self.reconnect()
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 1044, in reconnect
sock = self._create_socket_connection()
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 3685, in _create_socket_connection
return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source)
File “/usr/local/lib/python3.10/socket.py”, line 845, in create_connection
raise err
File “/usr/local/lib/python3.10/socket.py”, line 833, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
[2023-02-05 20:31:32,755] {main_worker.py:1070} ERROR - But at first take some break. Sleeping for 10 s
[2023-02-05 20:31:33,198] {socket_listener.py:304} ERROR - SOCKET LISTENER: Something went wrong. But don’t worry we will start over again.
Traceback (most recent call last):
File “/elan2mqtt-1.16.0/socket_listener.py”, line 302, in
asyncio.get_event_loop().run_until_complete(main())
File “/usr/local/lib/python3.10/asyncio/base_events.py”, line 646, in run_until_complete
return future.result()
File “/elan2mqtt-1.16.0/socket_listener.py”, line 143, in main
mqtt_cli.connect(mqtt_broker, 1883, 120)
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 914, in connect
return self.reconnect()
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 1044, in reconnect
sock = self._create_socket_connection()
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 3685, in _create_socket_connection
return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source)
File “/usr/local/lib/python3.10/socket.py”, line 845, in create_connection
raise err
File “/usr/local/lib/python3.10/socket.py”, line 833, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
[2023-02-05 20:31:33,198] {socket_listener.py:307} ERROR - But at first take some break. Sleeping for 5 s
[2023-02-05 20:31:38,285] {socket_listener.py:304} ERROR - SOCKET LISTENER: Something went wrong. But don’t worry we will start over again.
Traceback (most recent call last):
File “/elan2mqtt-1.16.0/socket_listener.py”, line 302, in
asyncio.get_event_loop().run_until_complete(main())
File “/usr/local/lib/python3.10/asyncio/base_events.py”, line 646, in run_until_complete
return future.result()
File “/elan2mqtt-1.16.0/socket_listener.py”, line 143, in main
mqtt_cli.connect(mqtt_broker, 1883, 120)
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 914, in connect
return self.reconnect()
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 1044, in reconnect
sock = self._create_socket_connection()
File “/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py”, line 3685, in _create_socket_connection
return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source)
File “/usr/local/lib/python3.10/socket.py”, line 845, in create_connection
raise err
File “/usr/local/lib/python3.10/socket.py”, line 833, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
[2023-02-05 20:31:38,286] {socket_listener.py:307} ERROR - But at first take some break. Sleeping for 5 s

“coonection refused” means that the eLan doesn’t accept connection from addon. Did you properly setup both addon and eLan?
In the addon IP address, username and password are the key settings

The eLAN IP address is 172.16.16.9
user: admin
password: elkoep
What’s wrong with me?

Hmm. Sorry. Just looked again at the error meesage. It is not an elan problem. It is mqtt problem.
Add-on can’t connect to your MQTT server. Check if it is accessible and username&password for mqtt is correct…

I am a complete beginner and therefore I ask how do I set up an MQTT server, please?

Sorry MQTT is out of scope of this thread. Please look into/follow HA documentation where this is described

or use one of video tutorials which could be found on youtube (for example Home Assistant MQTT Install and Setup - A Beginner's Guide - YouTube )

Ahoj,
nemáte odzkoušeno i s novou bránou eLAN-RF-103?
Mně se zatím spojení nedaří.

Help is needed. I am newbie to home assistant. An error occurs when installing the repository.