EcoEdge ECO1624 — ESPHome-Compatible 24V Controller
A 16-port 24V controller that fits into ESPHome-based smart home setups through its native MQTT integration — the same open protocol ESPHome uses to talk to Home Assistant.
ECO1624 in an ESPHome Ecosystem
ESPHome is a popular framework for creating custom firmware for ESP32 and ESP8266 devices. Most ESPHome installations integrate with Home Assistant via the native API or MQTT. ECO1624 uses the same MQTT approach, which means it sits naturally alongside ESPHome devices in a mixed automation setup — all entities appear in Home Assistant, all controlled through the same MQTT broker.
The key difference is that ECO1624 is a purpose-built hardware product rather than a DIY firmware project. It ships ready to use: no flashing, no YAML firmware compilation, no GPIO wiring. Where ESPHome excels at creating custom sensors and small relay boards, ECO1624 solves the specific problem of driving 16 × 24V loads from a DIN-rail enclosure.
How ECO1624 and ESPHome Devices Coexist
A typical Home Assistant setup with ESPHome devices and ECO1624 looks like this:
- ESPHome devices (temperature sensors, motion sensors, custom relays) connect via native API or MQTT
- ECO1624 connects via MQTT auto-discovery
- All entities — from ESPHome and ECO1624 — appear in the same Home Assistant instance
- Automations can reference any entity regardless of whether it comes from ESPHome or ECO1624
Example: an ESPHome temperature sensor in the living room triggers an ECO1624 port to open the heating zone valve:
automation:
- alias: Living Room Heating
trigger:
- platform: numeric_state
entity_id: sensor.living_room_temp_esphome
below: 20.5
action:
- service: switch.turn_on
target:
entity_id: switch.eco1624_port_2
MQTT Topics Compatible with ESPHome Conventions
ECO1624's MQTT topic structure follows the same conventions used by ESPHome's MQTT component.
State topics publish "ON" / "OFF" strings, command topics accept the same,
and an availability topic reports "online" / "offline" — all identical to
ESPHome MQTT output format.
This means any Node-RED flow, script, or automation built to work with ESPHome MQTT devices also works with ECO1624 with no modification to the message format.
When to Use ECO1624 vs a DIY ESPHome Board
DIY ESP32 + relay board
- Flexible — customise every pin and function
- Usually 5V or 12V relays — needs 24V adapter for actuators
- 8 or fewer channels without stacking modules
- Requires soldering or jumper wiring
- No DIN-rail form factor without custom enclosure
- Firmware maintenance on you
EcoEdge ECO1624
- 16 channels in one compact DIN module
- Native 24V DC — wire actuators directly
- Surge-protected outputs, per-channel LEDs
- Screw terminals — no soldering required
- Fits 35mm DIN rail in your distribution board
- OTA firmware updates via web UI
For sensors and custom I/O, ESPHome is the right tool. For 24V output control at scale, ECO1624 is the production-grade alternative that installs in minutes.
Frequently Asked Questions
Is there an official ESPHome component for ECO1624?
An official ESPHome external component is on the firmware roadmap. Currently, ECO1624 integrates with Home Assistant via MQTT auto-discovery, which works identically alongside ESPHome devices.
Can ECO1624 work alongside my existing ESPHome devices?
Yes. ECO1624 and ESPHome devices coexist on the same MQTT broker and Home Assistant instance. All entities appear together in your dashboard and can be referenced in the same automations.
Does ECO1624 use the same MQTT format as ESPHome?
Yes. ECO1624 uses ON/OFF string payloads on state and command topics, with an availability topic — the same convention as ESPHome's MQTT component. Existing MQTT flows work without modification.
Can I flash custom firmware on ECO1624?
ECO1624 ships with dedicated firmware optimised for its 16-port hardware. Custom firmware flashing is not officially supported, but documentation on the hardware platform is available in the docs for advanced users.
Add 16 × 24V outputs to your ESPHome setup
DIN-rail mounted, MQTT-native, ready in minutes.