Your support

This open-source project is developed in my free time. Your donation would help me dedicate more time and resources to improve project, add new features, fix bugs, as well as improve motivation and helps me understand, that this project is useful not only for me, but for more users.

Intro

This integration is for users which have smart ESO energy meters and does not have technical possibilities to add P1 interface (for example meter is far away from wireless reception). Keep in mind, that ESO site provides data for last 24 hours, therefore refresh rate is quite slow (check for new data is performed every 2 hours). If you wish for real-time statistics - consider using 3rd party meters (like Shelly 3EM) or utilise P1 interface of smart meter.

Disclaimer

This component is in testing stage! Errors or miscalculation, breaking changes should be expected! Any feedback or requests should be raised as an issue.

Installation

HACS

1. Navigate to HACS Integrations
2. Click Custom repositories
3. Paste repository URL https://github.com/algirdasc/hass-eso to Repository field
4. Choose Integration category
5. Click Add
6. Install & configure component (see Configuration)
7. Restart HA

Native

1. Upload custom_components directory to your HA config directory
2. Configure component (see Configuration)
3. Restart HA

Configuration

The integration is configured entirely from the Home Assistant UI (config flow). Legacy YAML configuration is deprecated; any existing eso: block is automatically imported into the UI on startup (see Migrating from YAML).

UI configuration

1. Go to Settings → Devices & Services → Add Integration
2. Search for ESO Energy Consumption
3. Step 1 – ESO account: enter your mano.eso.lt username and password.
4. Step 2 – Two-factor authentication (email): ESO emails a one-time code on every login, so a mailbox is required. Enter the mailbox that receives those codes so Home Assistant can read them automatically (see Two-factor authentication below).
5. Step 3 – Select objects: the integration logs in and auto-discovers your eso objects.

After setup, the account appears under Settings → Devices & Services with each object listed beneath it:

• Add object – discovers your objects and adds one as a new entry.
• Reconfigure (per object) – set that object's name, consumed/returned tracking, and an optional price entity for cost statistics — directly on the object, no nested menus.
• Configure (on the account) – update the ESO password and mailbox (2FA) settings.
• Delete (per object) – stop tracking that object.

Migrating from YAML

If you already have an eso: block in configuration.yaml, it is imported automatically into a config entry on the next restart. Once the integration appears under Settings → Devices & Services, remove the eso: block from configuration.yaml.

Two-factor authentication

ESO now sends a mandatory one-time code by email on every login. When a mailbox is configured (UI step 2), the integration completes that step automatically: it reads the latest code from your mailbox and submits it. To keep email traffic to a minimum it persists the authenticated session (eso_session.json in the HA config directory, valid ~3 weeks) and only performs a full login + 2FA when that session has expired.

A mailbox is required — without it the integration cannot log in while 2FA is enforced on your account.

The mailbox settings you provide are:

Object settings

Each object (metering point) exposes the following settings via Reconfigure:

Example with cost calculation

The example below is using the Nord Pool integration for Home Assistant. It creates an entity tracking spot market (hourly) electricity price. The additional_costs parameter is used to add any cost margins which depend on a particular energy contract.

sensor:
  - platform: nordpool
    region: "LT"
    currency: "EUR"
    VAT: true
    precision: 5
    low_price_cutoff: 0.95
    price_in_cents: false
    price_type: kWh
    additional_costs: "{{ 0.08470 + 0.007 | float }}" # 0.08470 ESO, 0.007 ENEFIT

Then, when reconfiguring an object, set its price entity to the Nord Pool price entity (e.g. sensor.nordpool_kwh_eur_ext). This triggers creation of an additional HA entity tracking energy costs.

To display the Cost information in the HA Energy dashboard, in the Energy configuration popup click the Use an entity tracking the total costs option and select the entity called My House (cost).

TODO

• [ ] Test with multiple objects