This community template connects the Elko EP eLAN-RF gateway (eLAN-RF-003 or eLAN-RF-Wi-003) to TapHome and controls wireless iNELS RF elements through the local HTTP API of the gateway. The TapHome Core talks to the gateway over plain HTTP on port 80 (no HTTPS) and needs no cloud connection. The template covers the six channels of an RFSA-66M switching actuator, one RFSA-61B, both channels of an RFSA-62B, the temperature of an RFTC-10/G thermostat and the temperature correction of one heating zone.
Which template to use
This variant requires TapHome Core 2026.1.40991 or newer. It takes the plain eLAN password and computes its SHA1 hash itself. On an older Core use Elko EP eLAN-RF (iNELS RF), which asks for the SHA1 hash of the password (40 hexadecimal characters) instead. Apart from the password field, both templates are identical — same devices, same scripts.
Gateway installation and network
The gateway is powered from the supplied 10–27 V DC adapter or over PoE (24 V DC) from the router. It manages up to 40 RF actuators and 16 temperature zones; its radio range is up to 100 m in open space. In a metal switchboard the external antenna AN-E improves reception, and the RFRP-20 repeater extends the range. The manufacturer requires a minimum distance of 1 cm between the gateway and an actuator.
eLAN-RF-003 (Ethernet)
- Connect the power supply and plug the gateway into the local network with an Ethernet cable.
- DHCP is enabled by default, so the router assigns the IP address. Find it in the router’s client list, or in the iNELS RF phone app (iHC-MAIRF for Android, iHC-MIIRF for iOS) under Settings → eLAN Settings → search, which lists the discovered gateways with their IP addresses.
- The template addresses the gateway by a fixed IP address — reserve it in the router (DHCP reservation) or set a static IP in the gateway web interface under Settings → IP Settings. After a change, use the new IP address; the TapHome Core must be in the same subnet or be routed to it.

eLAN-RF-Wi-003 (Wi-Fi model)
The Wi-Fi model starts its own network for the first configuration:
- About one minute after power-up, the Wi-Fi network ELAN-RF-WI appears. Connect to it with the password
00000000. - Open the factory default address
192.168.1.1in a web browser and log in (see below). - Under Settings, switch the network settings to Static IP, set an address in the subnet of the home network and the default gateway of that network, and save.
- Connect the gateway to the home network with an Ethernet cable, so that the TapHome Core can reach it at the new address.

Login to the gateway
Enter the IP address of the gateway in a web browser. The factory login for the administrator is user name admin and password elkoep; the login data can be changed under Settings → Accounts. The template logs in to the gateway with a user name and password; the user name parameter defaults to admin.

A long press of the button on the front panel until the yellow LED starts flashing resets the gateway: the IP address and the login data return to the factory settings (on the eLAN-RF-003, DHCP is selected again). After a reset, update the IP address and password in TapHome as well.
Adding the RF elements to the gateway
Every element has to be paired with the gateway before TapHome can control it. In the web interface open Settings → Devices and press (+):
- Product Type — select the type of the RF element (for example RFSA-61B).
- Address — enter the RF address printed on the element and its box (six-character hexadecimal code).
- Label and Type — any name and an icon for the eLAN floorplan.
- Press Create.

Heating elements and temperature zones are set up in the iNELS RF phone app — according to the manufacturer, the web interface only shows the measured and set temperature of thermal components.
Import parameters
| Parameter | Meaning |
|---|---|
| IP address of eLAN-RF | IP address of the gateway (port 80, HTTP) |
| eLAN user name | Login name of the gateway web interface, default admin |
| eLAN password | Plain password of that account — the template sends its SHA1 hash to /login |
| eLAN ID (one per element) | RFSA-66M channels 1–6, RFSA-61B, RFSA-62B channels 1–2, RFTC-10/G thermostat and the heating zone |
The eLAN ID is the identifier of the element in the HTTP API of the gateway: the template reads GET /api/devices/<id>/state and writes PUT /api/devices/<id>. It is not the six-character RF address from the box — that one is only used when the element is added to the gateway. The manufacturer manuals do not describe the HTTP API.
In the TapHome app, the template is imported as a Packet Parser module and these parameters are filled in during the import.
The gateway API runs over plain HTTP without encryption. Keep the gateway and the TapHome Core on a trusted local network.
Device capabilities
The module checks its session every 30 seconds (GET /api). When the gateway does not answer with HTTP 200, it logs in again (POST /login with the user name and the SHA1 hash of the password) and keeps the session cookie AuthID for all further requests. If the login fails, the module reports a login error.
Switching actuators
RFSA-66M channels 1–6, RFSA-61B and RFSA-62B channels 1–2 are on/off switches. Each one reads its state every 5 seconds and switches by writing on: true or on: false.
Service attributes of every channel: automatic mode, whether a delay is running, the set time of delayed off and delayed on (in seconds), whether the element is locked, and its eLAN ID.
Service actions of every channel:
| Action | Parameter |
|---|---|
| Delayed off | time 2–3600 s |
| Delayed on | time 2–3600 s |
| Automatic mode | on / off |
RFTC-10/G temperature
The thermostat temperature sensor reads the temperature IN value every 30 seconds. Service attributes show whether heating is on, the temperature of the external probe (temperature OUT, °C) and the raw state returned by the gateway.
Heating zone temperature correction
A variable that reads and writes the temperature correction of one heating zone of the gateway every 30 seconds. Written values are rounded to 0.5 and limited to −5 … +5. Service attributes show the zone mode, the zone power and the raw zone state; service actions set the zone mode (1–4) and the zone power (0–2).
Troubleshooting
Login error on the module
- Check the user name and the plain password entered during import.
- Check that the TapHome Core is at least version 2026.1.40991. On an older Core, use Elko EP eLAN-RF (iNELS RF) with the SHA1 hash of the password.
- After a reset of the gateway, the password is back to the factory value
elkoep.
A device reports that the gateway does not respond
- Check the eLAN ID of that device and that the element was added under Settings → Devices.
- The gateway IP address changed — open it in a browser and update the module, or reserve the address in the router.
The thermostat shows no temperature
The template reports an error when the temperature IN field is missing in the thermostat state. Check the raw state service attribute: it shows what the gateway returned for that eLAN ID, so a wrong ID (for example the ID of a relay) is easy to spot.
An RF element does not react
Signal problems are on the radio side of the gateway: move the gateway out of a metal switchboard or use the external antenna AN-E, keep the range under 100 m in open space, or add the RFRP-20 repeater.
