{"id":17799757,"url":"https://github.com/tmjo/charger-card","last_synced_at":"2025-05-06T18:08:12.631Z","repository":{"id":37080098,"uuid":"308752409","full_name":"tmjo/charger-card","owner":"tmjo","description":"A lovelace card for electrical vehicle (EV) home chargers and charging robots.","archived":false,"fork":false,"pushed_at":"2024-04-25T07:14:41.000Z","size":1286,"stargazers_count":106,"open_issues_count":21,"forks_count":63,"subscribers_count":4,"default_branch":"master","last_synced_at":"2025-05-06T18:08:00.105Z","etag":null,"topics":["charger","charging-robot","easee","elbil","electric-vehicle","evcharger","hacs","hass","home-assistant","homeassistant","lovelace"],"latest_commit_sha":null,"homepage":"","language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/tmjo.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":".github/FUNDING.yml","license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null},"funding":{"github":["tmjo"]}},"created_at":"2020-10-30T21:57:43.000Z","updated_at":"2025-05-05T11:24:01.000Z","dependencies_parsed_at":"2024-01-16T00:18:59.229Z","dependency_job_id":"5ed03e4f-693b-4b47-b321-278ce89845b5","html_url":"https://github.com/tmjo/charger-card","commit_stats":{"total_commits":194,"total_committers":13,"mean_commits":"14.923076923076923","dds":"0.11855670103092786","last_synced_commit":"fb83c2be692d756d41005ea0b5e627ca1f0a4f9c"},"previous_names":[],"tags_count":26,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tmjo%2Fcharger-card","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tmjo%2Fcharger-card/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tmjo%2Fcharger-card/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tmjo%2Fcharger-card/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/tmjo","download_url":"https://codeload.github.com/tmjo/charger-card/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":252741369,"owners_count":21797027,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["charger","charging-robot","easee","elbil","electric-vehicle","evcharger","hacs","hass","home-assistant","homeassistant","lovelace"],"created_at":"2024-10-27T12:10:24.383Z","updated_at":"2025-05-06T18:08:12.608Z","avatar_url":"https://github.com/tmjo.png","language":"TypeScript","funding_links":["https://github.com/sponsors/tmjo","https://www.buymeacoffee.com/tmjo"],"categories":[],"sub_categories":[],"readme":"  # EV Charger Card\n\n[![hacs][hacs-badge]][hacs-url]\n[![Buy me a coffee](https://img.shields.io/static/v1.svg?label=Buy%20me%20a%20coffee\u0026message=🥨\u0026color=black\u0026logo=buy%20me%20a%20coffee\u0026logoColor=white\u0026labelColor=6f4e37)](https://www.buymeacoffee.com/tmjo)\n\n\u003e EV Charger card for [Home Assistant][home-assistant] Lovelace UI\n\n\nBy default, Home Assistant does not provide any card for controlling chargers for electrical vehicles (EVs). This card displays the state and allows to control your charger - and it is now made fully customizable so you could also use it for «anything» else as well, for instance your electric car.\n\n![Preview of charger-card][preview-image]\n\n**💡 Tip:** If you like this project consider buying me a cup of ☕️:\n\n\u003ca href=\"https://www.buymeacoffee.com/tmjo\" target=\"_blank\"\u003e\n  \u003cimg src=\"https://cdn.buymeacoffee.com/buttons/default-black.png\" alt=\"Buy Me A Coffee\" width=\"150px\"\u003e\n\u003c/a\u003e\n\n\u003cbr\u003e\n\u003cbr\u003e\n\u003cbr\u003e\n\n\n# Installation\n\n### Installation with HACS\n\nInstallation with [HACS][hacs] (Home Assistant Community Store) is highly reccomended but requires that you have this installed on your Home Assistant. The charger-card is available just by searching for `Charger Card` under the Frontend-section of HACS.\n\n### Manual\nAlternatively you could install the card manually by following the steps below:\n\n1. Download `charger-card.js` file from the [latest-release].\n2. Put `charger-card.js` file into your `config/www` folder.\n3. Add reference to `charger-card.js` in Lovelace. There are two ways to do that:\n   1. **Using UI:** _Configuration_ → _Lovelace Dashboards_ → _Resources_ → Click Plus button → Set _Url_ as `/local/charger-card.js` → Set _Resource type_ as `JavaScript Module`.\n   2. **Using YAML:** Add following code to `lovelace` section.\n      ```yaml\n      resources:\n        - url: /local/charger-card.js\n          type: module\n      ```\n4. Add `custom:charger-card` to Lovelace UI as any other card (using either UI-editor or YAML-configuration).\n\n# Configuring and using the card\n\nAfter installation, the card can be configured either using Lovelace UI editor or YAML-code.\n\n1. In Lovelace UI, click the 3 dots in top right corner and select _Edit Dashboard_\n2. Click Plus button to add a new card.\n3. Find _Custom: Charger Card_ in the list.\n4. Choose `brand` from the list which fits your need or select other.\n5. Choose `entity` and select the main status sensor of your charger.\n6. Now you should see the preview of the card!\n7. Do your customizations in UI editor or manually in the YAML code editor.\n\nEven if you prefer to configure an advanced and custom YAML-code, it is reccomended to use the UI at first since it will generate a template for the YAML-code that you can continue modifying.\n\nHere is a list of the options. See [_advanced configuration_](#advanced-configuration) further down for more details.\n\n| Name                               |   Type    | Default      | Description                                                                                                                                                                                                                                                                                                                            |\n| ---------------------------------- | :-------: | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `type`                             | `string`  | **Required** | `custom:charger-card`                                                                                                                                                                                                                                                                                                                  |\n| `brand`                            | `string`  | **Required** | Select the template charger or system. If available it will try to set a pre-defined setup for your system and will assume you have all entities with default names from the integration. You can still edit your configuration in YAML if you system does not comply with these assumptions. See advanced config for further details. |\n| `entity`                           | `string`  | **Required** | The main status sensor for your charger (for Easee, look for the one named `status`).                                                                                                                                                                                                                                                  |\n| `customCardTheme`                  | `string`  | Optional     | Select a built-in theme of colors, or use `theme_custom` to apply the theme you have applied in HA.                                                                                                                                                                                                                                    |\n| `chargerImage`                     | `string`  | Anthracite   | Select a charger image from the built-in default images                                                                                                                                                                                                                                                                                |\n| `customImage`                      | `string`  | Optional     | Path to custom image of your charger (`png` or `svg`). This will override the chargerImage selection. (For images in the www-folder of HA, try path `\\local\\image.png`                                                                                                                                                                     |\n| `compact_view`                     | `boolean` | `false`      | Show a compact view of the card.                                                                                                                                                                                                                                                                                                       |\n| `show_name`                        | `boolean` | `true`       | Show a friendly name of the charger and the location (if provided)                                                                                                                                                                                                                                                                     |\n| `show_leds`                        | `boolean` | `true`       | Show status leds for the charger, fits best with Easee chargers and when using built-in images.                                                                                                                                                                                                                                        |\n| `show_status`                      | `boolean` | `true`       | Show status of the charger.                                                                                                                                                                                                                                                                                                            |\n| `show_collapsibles`                | `boolean` | `true`       | Show the collapsible menu buttons which will open detailed sensors when clicked.                                                                                                                                                                                                                                                       |\n| `show_toolbar`                     | `boolean` | `true`       | Show a toolbar with buttons that can call a service or do stuff.                                                                                                                                                                                                                                                                       |\n| `show_stats`                       | `boolean` | `true`       | Show data table (stats).  |\n| `details`                       | `details` | Optional        | Details for customization if the default brand template doesn't do what you want it to. This mus be done manually with YAML-code. See [_advanced configuration_](#advanced-configuration)  |\n\n\n\n\n## Features\n\n- Fully customizable for your needs, the card works for different chargers and other entities if you read the [_advanced configuration_](#advanced-configuration) section and customize it to your needs. For chargers that are supported by default templates, the setup is very easy: select brand and main entity and you should be done.\n- Animations: If choosing the default images of Easee chargers in any color, you can also choose to show leds which will behave according to charger status. This is identical to how the charger looks physically and similar to the Easee app and web site. Two leds for standby, all leds when connected, flashing while charging and so on. If SmartCharging is enabled, leds will be blue.\n- Collapsible menu buttons: Click on one of the menu buttons (if you have enabled them) to get more info, config or limit settings. Can also be customized.\n- Possibility to set current limits from UI. Current limits can also be customized.\n- Customizable data table (stats) items that can depend on charger status and show relevant information.\n- Customizable toolbar with buttons to call services or do something which. The toolbar can depend on charger status and show relevant actions.\n\n## Supported languages\n\nThis card supports translations. Please, help to add more translations and improve existing ones. Here's a list of supported languages:\n\n- English\n- Norsk bokmål (Norwegian)\n- Svenska (by [jockesoft](https://github.com/jockesoft))\n- German (by [DeerMaximum](https://github.com/DeerMaximum))\n- Danish (by [dykandDK](https://github.com/dykandDK))\n- Catalan (by [gerardag](https://github.com/gerardag))\n- Dutch (by [posixx](https://github.com/posixx))\n- [_Your language?_][add-translation]\n\n## Supported models\n\nThis card was originally made to support charging robots from [Easee](https://easee-international.com/), but has been further developed to be fully configurable and customizable and can be used with any kind of charger. It can even be used for other things than EV-chargers, for instance your electric car or something completely different. Some `brand`s are added with built-in support to make the configuration really easy:\n\n- Easee\n- [_Your charger?_](https://github.com/tmjo/charger-card/wiki/How-to-add-template-for-new-brand)\n\nSee [Wiki on how to add a brand](https://github.com/tmjo/charger-card/wiki/How-to-add-template-for-new-brand).\n\n# Advanced configuration\n\nIf your brand is on the list of supported models, you should be able to get away just by selecting the `brand` and `entity` main sensor from the UI editor of Home Assistant. However, if you want to fully customize it or use it for something else than supported by default `brand`s, you must do this yourself with YAML-code. It may seem overwhelming at first, so a trick can be applying a built-in `brand` as a template and start modifying the YAML code from there - this will give you the basic structure. Also see the examples further down.\n\n| Name                               |   Type    | Default      | Description                                                                                                                                                                                                                                                                                                                            |\n| ---------------------------------- | :-------: | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `debug`                             | `boolean`  | `false` | Apply `true` to enable some debugging features which will appear in Developer Tools of your browser (Ctrl+Shift+I in Chrome). Useful if something doesn't work.\n| `localize`                             | `boolean`  | `true` | Apply `false` to disable all translations, for instance if you want to fully customize texts and the translation feature for some reason messes up you stuff. Normally not necessary.\n| `details`                       | `details` |        | Details for customization if the default brand template doesn't do what you want it to. See [`details`-items](#details-items)  |\n\n\n\n## Details items\n\n| Config             | Text         |\n| ------------------ | ------------------------------------------------- |\n| name               | Single entity with configuration details as shown in [`entity`-items](#entity-items). |\n| location           | Single entity with configuration details as shown in [`entity`-items](#entity-items). |\n| status             | Single entity with configuration details as shown in [`entity`-items](#entity-items). |\n| substatus          | Single entity with configuration details as shown in [`entity`-items](#entity-items). |\n| smartcharging      | Single entity with configuration details as shown in [`entity`-items](#entity-items). Controls white or blue leds for easee chargers.|\n| info_left          | List of entities with configuration details as shown in [`entity`-items](#entity-items). Defines static icons shown top-left of the card.|\n| info_right         | Same as `info_left`, but for static icons shown top-right of the card.|\n| group1             | List of entities with configuration details as shown in [`entity`-items](#entity-items). Defines the content of first collapsible-button (default: limits).|\n| group2             | List of entities with configuration details as shown in [`entity`-items](#entity-items). Defines the content of second collapsible-button (default: info).|\n| group3             | List of entities with configuration details as shown in [`entity`-items](#entity-items). Defines the content of third collapsible-button (default: config).|\n| stats              | Provide the states of `entity` defined as main status sensor, then a list of entities with configuration details as shown in [`entity`-items](#entity-items). Defines the datatable statistics (stats) in lower part of card. It may change depending on status of charger, or it is possible to define `default` as a state. See example. |\n| toolbar_left       | Provide the states of `entity` defined as main status sensor, then a list of entities with configuration details as shown in [`entity`-items](#entity-items). Defines the left aligned command buttons on the toolbar at the bottom of the card. It may change depending on status of charger, or it is possible to define `default` as a state. See example.                                                     |\n| toolbar_right      | Same as `toolbar_left` but right aligned command buttons on the toolbar.                                           |\n| currentlimits      | Override the card default current limits by specifying a list of numbers. Used for current limit features of the card (if configured). You can also use `dropdownitems` for each item to customize the dropdown if you prefer. |\n| statetext          | Override or custom-translate the status sensor state by providing better or cleaner text. See example. You may force off translation by adding a leading '_' to your text, but it is usually not neccessary.|\n| collapsiblebuttons | Specify `text` and/or `icon` to customize the collapsible-buttons `group1`,`group2` and `group3` respectively. See example.|\n\n\n## Entity items\n\n| Config                | Text                                                                                                                                                                                                                                                                                                                                                        |\n| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| entity_id             | Specify an entity id that you want to use for the specific feature. Enter `calculated` to perform mathematical functions instead, see further down how.|\n| attribute             | You can specify an attribute of the entity to use instead of entity state as value. |\n| unit                  | Card will use the entity `unit_of_measurement` as default, but you can override it here by entering the unit you want.|\n| unit_show             | Define if the unit should be shown next to the value or not.|\n| unit_showontext       | Define if the value and unit should be shown next to the tooltip text|\n| text                  | Card will use the entity `friendly_name` as default, but you can override it here by entering the text you want. Used as tooltip text for icons and as information on stats.|\n| service               | You can specify a service that you wish to link to the entity, check available services in HA Developer Tools. Use full format like `domain.servicename`|\n| service_data          | Specify the service data corresponding to the service you want to call. If it is not a static call, but for instance a call with a value selected from a dropdown menu, enter `#SERVICEVAL#` as a special token which will be replaced by the card when called. See advanced configuration for example. |\n| icon                  | Card will use the entity icon as default, and will try to detect device class icons as well. If you want to override it, do it here by specifying a valid icon.|\n| round                 | If you would like to round down the number, specify an integer to define the number of digits.|\n| type                  | Choose between `info`, `service` and `dropdown`. Info-items will appear as icons with tooltip, clicking them opens the more-info popup for the entity. Service-items will do the same, but call a service when clicked (if it is provided). Dropdown-items will show a dropdown list to select from a list and call a specified service with this number as service data. |\n| dropdownitems         | List of items used for dropdown values if the type is `dropdown`. Defaults to `currentlimits` if not specified. |\n| calc_function         | Choose between `min`, `max`, `mean`, `sum` to define a mathematical function to be performed on a specified list of entities or attributes. The result will be used on the sensor provided you specify `calculated` instead of a real `entity_id`. Then add a list of entities to be calculated in `calc_entities`.|\n| calc_entities         | A list of entites or entity attributes that are used for the mathematical function. Specify a list of `entity_id`s and add `attribute`s if you prefer to use that.|\n| conditional_entity    | Specify a boolean entity (returning on/off or true/false) to define if the entity should be shown based on state condition.|\n| conditional_attribute | Specify a boolean entity and its attribute (returning on/off or true/false) to define if the entity should be shown based on state attribute condition.|\n| conditional_invert    | Invert the conditional rule, so that true/on means hide and false/off means show |\n\n\n## Advanced example (Easee charger)\nIn service data, you can choose if you want to use device_id or entity_id depending on the service interface you are using. The Easee-example below was changed from entity_id to device_id due to changes in the integration.\n\nItems in capital letters are meant to be replaced with your actual names, but do not change the ones surrounded by # such as #SERVICEVAL# as these are used in the code. When you do the configuration from UI, the card config tries to fill your data automatically.\n\n```yaml\ntype: custom:charger-card\nentity: sensor.CHARGERNAME_status\ncustomCardTheme: theme_custom\nchargerImage: Red\nbrand: easee\nshow_leds: true\ndetails:\n  name:\n    entity_id: sensor.CHARGERNAME_status\n    attribute: name\n  location:\n    entity_id: sensor.CHARGERNAME_status\n    attribute: site_name\n  status:\n    entity_id: sensor.CHARGERNAME_status\n  substatus:\n    entity_id: sensor.CHARGERNAME_reason_for_no_current\n  smartcharging:\n    entity_id: switch.CHARGERNAME_smart_charging\n  currentlimits:\n    - 0\n    - 6\n    - 10\n    - 16\n    - 20\n    - 25\n    - 32\n  statetext:\n    disconnected: disconnected\n    awaiting_start: awaiting_start\n    charging: charging\n    completed: completed\n    error: error\n    ready_to_charge: ready_to_charge\n  collapsiblebuttons:\n    group1:\n      text: click_for_group1\n      icon: mdi:speedometer\n    group2:\n      text: click_for_group2\n      icon: mdi:information\n    group3:\n      text: click_for_group3\n      icon: mdi:cog\n  info_left:\n    - entity_id: binary_sensor.CHARGERNAME_online\n      text: online\n  info_right:\n    - entity_id: sensor.CHARGERNAME_voltage\n      text: voltage\n      unit_show: true\n    - entity_id: sensor.CHARGERNAME_power\n      text: power\n      unit_show: true\n  group1:\n    - entity_id: sensor.CHARGERNAME_dynamic_charger_limit\n      text: dyn_charger_limit\n      service: easee.set_charger_dynamic_limit\n      service_data:\n        device_id: DEVICEID\n        current: '#SERVICEVAL#'\n    - entity_id: sensor.CHARGERNAME_dynamic_circuit_limit\n      text: dyn_circuit_limit\n      service: easee.set_circuit_dynamic_limit\n      service_data:\n        device_id: DEVICEID\n        currentP1: '#SERVICEVAL#'\n    - entity_id: sensor.CHARGERNAME_max_charger_limit\n      text: max_charger_limit\n      service: easee.set_charger_max_limit\n      service_data:\n        device_id: DEVICEID\n        current: '#SERVICEVAL#'\n    - entity_id: sensor.CHARGERNAME_max_circuit_limit\n      text: max_circuit_limit\n      service: easee.set_circuit_max_limit\n      service_data:\n        device_id: DEVICEID\n        currentP1: '#SERVICEVAL#'\n    - entity_id: sensor.CHARGERNAME_offline_circuit_limit\n      text: offline_circuit_limit\n      service: easee.set_circuit_offline_limit\n      service_data:\n        device_id: DEVICEID\n        currentP1: '#SERVICEVAL#'\n  group2:\n    - entity_id: binary_sensor.CHARGERNAME_online\n      text: online\n    - entity_id: sensor.CHARGERNAME_voltage\n      text: voltage\n      unit_show: true\n    - entity_id: sensor.CHARGERNAME_power\n      text: power\n      unit_show: true\n    - entity_id: sensor.CHARGERNAME_current\n      text: charger_current\n      unit_show: true\n    - entity_id: sensor.CHARGERNAME_circuit_current\n      text: circuit_current\n      unit_show: true\n    - entity_id: sensor.CHARGERNAME_energy_per_hour\n      text: energy_per_hour\n      unit_show: true\n    - entity_id: sensor.CHARGERNAME_session_energy\n      text: session_energy\n      unit_show: true\n    - entity_id: sensor.CHARGERNAME_lifetime_energy\n      text: lifetime_energy\n      unit_show: true\n  group3:\n    - entity_id: switch.CHARGERNAME_is_enabled\n      text: enabled\n    - entity_id: switch.CHARGERNAME_enable_idle_current\n      text: idle_current\n    - entity_id: binary_sensor.CHARGERNAME_cable_locked\n      text: cable_locked\n    - entity_id: switch.CHARGERNAME_cable_locked_permanently\n      text: perm_cable_locked\n    - entity_id: switch.CHARGERNAME_smart_charging\n      text: smart_charging\n    - entity_id: sensor.CHARGERNAME_cost_per_kwh\n      text: cost_per_kwh\n    - entity_id: binary_sensor.CHARGERNAME_update_available\n      text: update_available\n    - entity_id: binary_sensor.CHARGERNAME_basic_schedule\n      text: schedule\n  stats:\n    default:\n      - entity_id: sensor.CHARGERNAME_session_energy\n        text: session_energy\n        unit_show: true\n      - entity_id: switch.CHARGERNAME_cable_locked_permanently\n        text: cable_locked\n      - entity_id: binary_sensor.CHARGERNAME_basic_schedule\n        text: schedule\n    disconnected:\n      - entity_id: sensor.CHARGERNAME_session_energy\n        text: session_energy\n        unit_show: true\n      - entity_id: switch.CHARGERNAME_cable_locked_permanently\n        text: cable_locked\n      - entity_id: calculated\n        text: used_limit\n        unit: A\n        unit_show: true\n        calc_function: min\n        calc_entities:\n          - entity_id: sensor.CHARGERNAME_dynamic_charger_limit\n          - entity_id: sensor.CHARGERNAME_dynamic_circuit_limit\n          - entity_id: sensor.CHARGERNAME_max_charger_limit\n          - entity_id: sensor.CHARGERNAME_max_circuit_limit\n          - entity_id: sensor.CHARGERNAME_offline_circuit_limit\n    awaiting_start:\n      - entity_id: sensor.CHARGERNAME_session_energy\n        text: session_energy\n        unit_show: true\n      - entity_id: binary_sensor.CHARGERNAME_basic_schedule\n        text: schedule\n      - entity_id: switch.CHARGERNAME_smart_charging\n        text: smart_charging\n      - entity_id: calculated\n        text: used_limit\n        unit: A\n        unit_show: true\n        calc_function: min\n        calc_entities:\n          - entity_id: sensor.CHARGERNAME_dynamic_charger_limit\n          - entity_id: sensor.CHARGERNAME_dynamic_circuit_limit\n          - entity_id: sensor.CHARGERNAME_max_charger_limit\n          - entity_id: sensor.CHARGERNAME_max_circuit_limit\n          - entity_id: sensor.CHARGERNAME_offline_circuit_limit\n    charging:\n      - entity_id: sensor.CHARGERNAME_session_energy\n        text: session_energy\n        unit_show: true\n      - entity_id: sensor.CHARGERNAME_energy_per_hour\n        text: energy_per_hour\n        unit_show: true\n      - entity_id: sensor.CHARGERNAME_circuit_current\n        text: circuit_current\n        unit_show: true\n      - entity_id: sensor.CHARGERNAME_output_limit\n        text: output_limit\n        unit_show: true\n      - entity_id: sensor.CHARGERNAME_current\n        text: current\n        unit_show: true\n      - entity_id: sensor.CHARGERNAME_power\n        text: power\n        unit_show: true\n    completed:\n      - entity_id: sensor.CHARGERNAME_session_energy\n        text: session_energy\n        unit_show: true\n      - entity_id: binary_sensor.CHARGERNAME_basic_schedule\n        text: schedule\n      - entity_id: calculated\n        text: used_limit\n        unit: A\n        unit_show: true\n        calc_function: min\n        calc_entities:\n          - entity_id: sensor.CHARGERNAME_dynamic_charger_limit\n          - entity_id: sensor.CHARGERNAME_dynamic_circuit_limit\n          - entity_id: sensor.CHARGERNAME_max_charger_limit\n          - entity_id: sensor.CHARGERNAME_max_circuit_limit\n          - entity_id: sensor.CHARGERNAME_offline_circuit_limit\n    error:\n      - entity_id: sensor.CHARGERNAME_session_energy\n        text: session_energy\n        unit_show: true\n      - entity_id: binary_sensor.CHARGERNAME_basic_schedule\n        text: schedule\n    ready_to_charge:\n      - entity_id: sensor.CHARGERNAME_session_energy\n        text: session_energy\n        unit_show: true\n      - entity_id: binary_sensor.CHARGERNAME_basic_schedule\n        text: schedule\n      - entity_id: calculated\n        text: used_limit\n        unit: A\n        unit_show: true\n        calc_function: min\n        calc_entities:\n          - entity_id: sensor.CHARGERNAME_dynamic_charger_limit\n          - entity_id: sensor.CHARGERNAME_dynamic_circuit_limit\n          - entity_id: sensor.CHARGERNAME_max_charger_limit\n          - entity_id: sensor.CHARGERNAME_max_circuit_limit\n          - entity_id: sensor.CHARGERNAME_offline_circuit_limit\n  toolbar_left:\n    default:\n      - {}\n    disconnected:\n      - {}\n    awaiting_start:\n      - service: easee.action_command\n        service_data:\n          device_id: DEVICEID\n          action_command: stop\n        text: stop\n        icon: hass:stop\n      - service: easee.action_command\n        service_data:\n          device_id: DEVICEID\n          action_command: resume\n        text: resume\n        icon: hass:play\n      - service: easee.action_command\n        service_data:\n          device_id: DEVICEID\n          action_command: override_schedule\n        text: override\n        icon: hass:motion-play\n    charging:\n      - service: easee.action_command\n        service_data:\n          device_id: DEVICEID\n          action_command: stop\n        text: stop\n        icon: hass:stop\n      - service: easee.action_command\n        service_data:\n          device_id: DEVICEID\n          action_command: pause\n        text: pause\n        icon: hass:pause\n    completed:\n      - service: easee.action_command\n        service_data:\n          device_id: DEVICEID\n          action_command: stop\n        text: stop\n        icon: hass:stop\n      - service: easee.action_command\n        service_data:\n          device_id: DEVICEID\n          action_command: override_schedule\n        text: override\n        icon: hass:motion-play\n    error:\n      - service: easee.action_command\n        service_data:\n          device_id: DEVICEID\n          action_command: reboot\n        text: reboot\n        icon: hass:restart\n    ready_to_charge:\n      - service: easee.action_command\n        service_data:\n          device_id: DEVICEID\n          action_command: stop\n        text: stop\n        icon: hass:stop\n      - service: easee.action_command\n        service_data:\n          device_id: DEVICEID\n          action_command: override_schedule\n        text: override\n        icon: hass:motion-play\n  toolbar_right:\n    default:\n      - service: persistent_notification.create\n        service_data:\n          message: Firmware update is available, but only possible when disconnected!\n          title: Update\n        text: update\n        icon: mdi:file-download\n        conditional_entity: binary_sensor.CHARGERNAME_update_available\n    disconnected:\n      - service: easee.action_command\n        service_data:\n          device_id: DEVICEID\n          action_command: update_firmware\n        text: update\n        icon: mdi:file-download\n        conditional_entity: binary_sensor.CHARGERNAME_update_available\n```\n\n## Development\nWant to contribute to the project? Translations? Adding your `brand` as a pre-defined template?\n\nFirst of all, thanks! Check [contributing guideline](./CONTRIBUTING.md) for more information. See [Wiki on how to add a brand](https://github.com/tmjo/charger-card/wiki/How-to-add-template-for-new-brand).\n\n\n\n\n\n## License\nMIT © [Tor Magne Johannessen][tmjo]\n\nThis project was initially inspired by \u003ca href=\"https://github.com/denysdovhan/vacuum-card\" target=\"_blank\"\u003evacuum card\u003c/a\u003e by denysdovhan. Thanks!\n\n\u003c!-- Badges --\u003e\n[npm-url]: https://npmjs.org/package/charger-card\n[hacs-url]: https://github.com/hacs/integration\n[hacs-image]: https://img.shields.io/badge/HACS-Custom-orange.svg\n[hacs-badge]: https://img.shields.io/badge/HACS-Default-41BDF5.svg?style=for-the-badge\n[buymeacoffee-url]: https://www.buymeacoffee.com/tmjo\n\n\n\u003c!-- References --\u003e\n[home-assistant]: https://www.home-assistant.io/\n[hacs]: https://hacs.xyz\n[preview-image]: https://user-images.githubusercontent.com/54450177/97765425-56874900-1b12-11eb-9c0c-87721e0b5748.png\n[latest-release]: https://github.com/tmjo/lovelace-charger-card/releases/latest\n[ha-scripts]: https://www.home-assistant.io/docs/scripts/\n[edit-readme]: https://github.com/tmjo/lovelace-charger-card/edit/master/README.md\n[add-translation]: https://github.com/tmjo/lovelace-charger-card/tree/master/src/translations\n[tmjo]: https://github.com/tmjo\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftmjo%2Fcharger-card","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ftmjo%2Fcharger-card","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftmjo%2Fcharger-card/lists"}