Please upgrade to v0.9.64 or later version as soon as possible if you are running a version between v0.9.58 and v0.9.62! All versions of this integration between v0.9.58 and v0.9.62 has had an issue with the signalr reconnect error handling that causes lots of failed accesses to Easee signalr servers. Installing a newer version will help improve the stability of the Easee servers and free up resources for more quick response. You might not have experienced any problems in your installation but under the hood there has been lots of issues. See more details in the release note of v0.9.64.

Custom component to support Easee EV chargers and equalizers.

The status sensor is the default sensor and has the following values

disconnected
awaiting_start
charging
ready_to_charge
completed
error

Some of the other non-common sensors like Current and Voltage are disabled by default (shown as "unavailable"). They can be enabled in the HA GUI via Integrations->[Easee Name]->Devices->[Easee Equilizer Name] and under Diagnostic click on Current/Voltage->gear_icon and then Enable it. Each of these sensors has also attributes which contain values like current and voltage per phase. See #271 on how to use these attributes.

There are 2 different methods of installing the custom component

1. Add this repository from HACS->Integrations.
2. Restart Home Assistant.
3. Install the component from Settings->Integrations. You may have to clear the browser cache to make the Easee integration appear in the list.

1. Make sure you have git installed on your machine.
2. Navigate to you home assistant configuration folder.
3. Create a custom_components folder of it does not exist, navigate down into it after creation.
4. Execute the following command: git clone https://github.com/nordicopen/easee_hass.git easee
5. Run bash links.sh

Since v0.9.47 the integration only includes the chargers and equalizers that has been added to the Easee official app, rather than showing all that are available to the logged in user. This change was done becuase in larger installations there could be 10s or 100s of chargers listed which in most cases does not make much sense. So if you do not see all your products in the integration, open the official app and make sure they are listed there first. Note also that if no chargers at all are added to the app the error message "No sites found in this account" will be displayed at installation.

Configuration is done through in Configuration > Integrations where you first configure it and then set the options for what you want to monitor.

The basic use of the integrations from the UI should be self-explanatory. The integration defines a number of services that can be used from automations and scripts to control the charger and the charging process. The available services can be found in Home Assistant at Developer tools->Services.

The easiest way to set up services and their parameters is to use the automation editor or the developer tools. However, you can also write the code in plain yaml. The UI will use device_id as target for the services. This is a random string generated internally by HA and is not very user friendly. To simplify for hard-core coders and to be backward compatible with previous versions of this integration you can also use charger_id or circuit_id as targets. Three examples that will do the same thing:

service: easee.set_circuit_dynamic_limit
data:
  device_id: b40f1f45d28b0891
  current_p1: 10

service: easee.set_circuit_dynamic_limit
data:
  charger_id: EVK1234
  current_p1: 10

service: easee.set_circuit_dynamic_limit
data:
  circuit_id: 30456
  current_p1: 10

For details on the Easee API, please refer to https://developer.easee.cloud/reference

A full debug log can be enabled by entering following into configuration.yaml and restarting Home Assistant

logger:
  default: info
  logs:
    pyeasee: debug
    custom_components.easee: debug

One option for development is to use the VS Code Dev Container. You need to have Docker installed.

1. Open a new blank vscode
2. Select Command palette->Dev containers: Clone repository in named container volume
3. Follow the prompts
4. Wait for the container to be built.
5. Press Ctrl+Shift+P and select Tasks: Run Task > Run Home Assistant on port 9125.
6. Wait for Home Assistant to start and go to https://localhost:9125/.
7. Walk through the Home Assistant first-launch UI.
8. Go to https://localhost:9125/config/integrations, click Add Integration and add the Easee integration.
9. To debug, press F5 to attach to the Home Assistant running in the container.

Always run

$ make lint

before pushing your changes.

We are using Lokalise to handle submission of translations. They provide us with an amazing platform that is easy to use and maintain.

To help out with the translation of the Easee integration click here. If you are asked to login it is normally easiest to use "Log in with GitHub".

If you want to add a new language, please open an issue here in this repo.

The translations are pulled when a new release of the integration is prepared. So you must wait until there is a new release until your look for your updates.

If you want to add new elements that needs translation you should enter them in /translations/en.json and submit a PR. The new keys will appear in Lokalise when the PR is merged.

This project was started by the late Niklas Fondberg, @fondberg. The repository has been inherited by his collaborators.

The project is supported by