Home / Documentation / ecoMain

Ethernet and local integration

ecoMain Ethernet Local Integration Guide

Connect ecoMain over Ethernet for local energy monitoring. Find it on your local network, verify the connection in Windows, and bring real-time electricity data into Home Assistant or another system that supports Modbus TCP.

ecoMainEnglishV1.06 August 2026
Start the Ethernet setup ↓ View original PDF ↗

Quick start

  1. Connect ecoMain over Ethernet Connect it to your local area network.
  2. Check DHCP Make sure DHCP is enabled on the network.
  3. Verify that ecoMain is online Use its device host name.
  4. Add ecoMain to your local system Use Home Assistant or another platform that supports Modbus TCP.
Front view of ecoMain with status indicators and pairing button.
ecoMain front panel shown on the guide cover.

Revision history

Version Date Description
V1.0 2026-08-06 Initial release

© Enecess. All rights reserved. Specifications are subject to change without notice.

1. Overview

ecoMain automatically initializes its wired connection after you connect it to the local area network (LAN). Once it is online, a local Modbus TCP client can use its host name to access data without looking up the IP address or setting up DNS manually.

  • Stable connection. Ethernet avoids issues caused by Wi-Fi signal strength and wireless interference.
  • Low latency. The wired connection suits real-time data acquisition and control.
  • Continuous operation. Use it with systems that stay online, including energy management systems (EMS) and Home Assistant.

2. Start accessing ecoMain

2.1 Network requirements

  • DHCP is enabled on the LAN.
  • ecoMain and the client device are on the same LAN.

ecoMain has built-in multicast DNS (mDNS). After startup, it generates a unique local host name.

2.2 Device host name

The host name is the fixed prefix enecess-main- followed by the device serial number (SN). Keep any leading zeroes.

enecess-main-<Device SN>
Device SN Host name
003516000585 enecess-main-003516000585

2.3 Find the device serial number

Find the serial number on the ecoMain device label or in the ecoMain app.

ecoMain device label with the serial number highlighted.
Figure 1. Device label with the SN field highlighted.
ecoMain app with the device information control highlighted.
Figure 2. Device information in the ecoMain app.

2.4 Power on ecoMain and verify communication

2.4.1 Hardware connection

  1. Connect the power cable Connect it to the ecoMain power interface. Refer to the ecoMain User Manual for wiring details.
  2. Connect Ethernet Plug one end into the ecoMain Ethernet interface and the other into a router or switch on the LAN.
  3. Power on ecoMain Check the wiring before powering on the device.
ecoMain with the Ethernet cable at the top, power cable below and power and network LEDs marked.
In this photo, the Ethernet cable connects at the top and the power cable at the bottom. The two middle callouts identify the power and network indicators.
  • Power indicator. A steady light indicates normal power.
  • Network indicator. A steady light indicates an established Ethernet link.
  • The network indicator can briefly turn off during startup. It should remain steadily on after startup completes in about 1–2 minutes.

2.4.2 Verify the network in Windows

After startup, ping the host name to check that ecoMain is reachable on the local network before continuing with Modbus TCP.

  1. Open Command Prompt

    Press Win + R, enter cmd, then choose OK or press Enter.

    Windows Run dialog with cmd in the Open field.
    Open Command Prompt from the Windows Run dialog.
  2. Run the ping command Put a space after ping. Replace <Device SN> with your device serial number, then press Enter. 
    ping enecess-main-<Device SN>

    For serial number 003516000585, run:

    ping enecess-main-003516000585

    On a successful connection, Command Prompt shows replies from the device IP address. The example uses an address in the form 192.168.xx.xx.

    Windows Command Prompt showing successful ping replies from the ecoMain device IP address.
    Successful ping replies confirm that the device is reachable on the LAN.

3. Local system integration

ecoMain exposes a standard Modbus TCP interface. The guide lists Home Assistant, Modbus Poll, PLCs, SCADA and Node-RED as examples of local systems that can use the interface.

Home Assistant integration and Energy Dashboard

  1. Install the enecess integration for ecoMain Download it through HACS. See the enecess integration repository for detailed instructions.
    HACS integration download dialog for enecess in Home Assistant.
    Download the enecess integration through HACS.
  2. Restart Home Assistant

    Open Settings → System → Restart.

    Home Assistant restart confirmation dialog.
    Restart Home Assistant after installing the integration.
  3. Add the discovered ecoMain Select the device Home Assistant discovers. If there are several ecoMain devices, match the serial number.
    Home Assistant integration screen with a discovered ecoMain device.
    Select the discovered ecoMain device with the matching SN.
  4. View live data

    Open Overview to see real-time device data.

    Home Assistant view showing real-time ecoMain readings.
    View real-time ecoMain readings in Home Assistant Overview.
  5. Set up the Energy Dashboard Configure ecoMain in the Energy Dashboard. For dashboard setup, see Home Assistant’s home energy management documentation.
    Home Assistant Energy Dashboard with example energy charts.
    Example of ecoMain energy monitoring in the Energy Dashboard.

Interface versions. Home Assistant screens may change between releases. Refer to the current enecess integration instructions during setup.

4. Troubleshooting

4.1 Ping cannot find the device

  • Check that ecoMain has started and finished network initialization.
  • Confirm the serial number and the host name format enecess-main-<Device SN>.
  • Make sure DHCP is enabled and the client and ecoMain are on the same LAN.

4.2 Cannot access ecoMain by host name

  • Check that the network allows devices to reach one another and that client isolation is disabled.
  • Check that the LAN allows mDNS multicast. Across VLANs, the network needs to forward mDNS between the relevant segments.

Publisher contact

Energy assets easy to access

QR code for the enecess YouTube channel.
YouTube
QR code for enecess on Facebook.
Facebook