Hallo,

ich bekomme nach der korrekten Konfiguration des Fahrtz´zeugs folgenden Fehler laut LOG:
[main ] ERROR 2024/01/24 22:35:27 creating vehicle ev4 failed: cannot create vehicle type 'template': cannot create vehicle type 'tesla': cannot get vehicles: 412 Precondition Failed

Ich vermute, dass dies mit der geänderten Tesla-API zusammenhängt.
Laufen hierzu schon die Anpassungen?
openWB hat ähnliche Probleme.

Vielen Dank!

@thecem mit https://github.com/evcc-io/evcc/blob/master/.github/workflows/documentation.yml können wir seit einiger Zeit vom evcc Repo aus auch die Doku aktualisieren. Vielleicht lässt sich dieser oder ein ähnlicher Mechanismus auch nutzen, um die Releases hier automatisch zu erstellen? PR welcome!

Getting the following error when trying to update from 0.100 to 0.101: Can't install andig/evcc:0.101: 404 Client Error for http+docker://localhost/v1.41/images/create?tag=0.101&fromImage=andig%2Fevcc&platform=linux%2Farm64: Not Found ("manifest for andig/evcc:0.101 not found: manifest unknown: manifest unknown")

tried restart, no go.
On HA 2022.9.4.

Is it posible to change the panel_admin option to false?
https://developers.home-assistant.io/docs/add-ons/configuration/#optional-configuration-options

The default value is true. With this value only HA Admins can see evcc in the sidebar.

Hello,
I setup the evcc hassio add-on and got it running. I can reach it using http://my-ip:7070, but if I try to open the web ui within the add on at the supervisor or at the sidebar I get the 502: Bad Gateway error.
The ports in the add-on are default. In the evcc.yaml port 7070 is used.

How can I solve this?

Thanks for your help.

Daniel

Hi,
I installed the version 0.114.0 of the evcc adon on Home Assistant 2022.11.5.

When I use evcc as addon in Home Assistant I get the following error:

Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main ] INFO 2023/03/05 23:51:06 evcc 0.114.0
[main ] INFO 2023/03/05 23:51:06 using config file: /config/evcc.yaml
[main ] INFO 2023/03/05 23:51:06 starting ui and api at :7070
[db ] INFO 2023/03/05 23:51:06 using sqlite database: /data/evcc.db
[mqtt ] INFO 2023/03/05 23:51:06 connecting evcc-289635650 at tcp://172.16.1.63:1883
[main ] FATAL 2023/03/05 23:51:06 could not open port- check that evcc is not already running (cannot create charger 'wallbox5': cannot create charger 'template': cannot create charger 'keba': listen udp :7090: bind: address already in use)
[main ] FATAL 2023/03/05 23:51:06 will attempt restart in: 5m0s

I used the evcc.yaml below. This file seems working, if I use the it on a standalone evcc on Ubuntu.

network:
schema: http
host: XXXXXX # .local suffix announces the hostname on MDNS
port: 7070

log: info
levels:
cache: error

plant: XXXXX

interval: 10s # control cycle interval

meters:

• name: pv2
  type: custom
  power: # Leistung (W)
  source: mqtt
  topic: XXXX
• name: grid1
  type: custom
  power: # Leistung (W)
  source: mqtt
  topic: XXXX
• name: battery3
  type: custom
  soc: # in %
  source: mqtt
  topic: XXXX
  power: # Leistung (W)
  source: mqtt
  topic: XXXX

chargers:

• type: template
  template: keba
  host: XXX.XXX.XXX.XXX
  name: wallbox5

vehicles:

• type: template
  template: audi
  title: XXXX
  user: [email protected]
  password: XXXXXXXXXX
  capacity: 14
  phases: 3
  icon: car
  cache: 15m
  mode: now
  minSoc: 0
  targetSoc: 100
  minCurrent: 6
  maxCurrent: 32
  name: ev4

loadpoints:

• title: Wallbox
  charger: wallbox5
  vehicle: ev4
  mode: off
  phases: 3
  mincurrent: 6
  maxcurrent: 32
  resetOnDisconnect: true

site:
title: My home
meters:
grid: grid1
pv:
- pv2
battery:
- battery3

tariffs:
currency: EUR # (default EUR)
grid:
type: fixed
price: 0.XXXX # [currency]/kWh

feedin:
type: fixed
price: 0.XXXX # [currency]/kWh

mqtt:
broker: XXX.XXX.XXX.XXX:1883
user: XXXX
password: XXXXXXX

Hi! When clicking on Open User Interface (Benutzeroberflääche Öffnen) I get a 502 Bad Gateway.

Any ideas?

It would be great if in the Add-on config a port could be specified which forwards directly to the evcc WebUI, not showing HA "chrome" around it. That way showing evcc on a small screen would be more clean.

Nach einem Update von 0.116.4 auf 0118.0 meldet EVCC leider immer 502 Bad Gateway.

An der evcc.yaml wird nichts geändert. HomeAssistant ebenfalls nicht.

Nachdem die Wallbox (Elli, eebus) nicht verbinden kann kommt nach dem Timeout dann allerdings die

FEHLER BEIM STARTEN
cannot create charger 'wallbox'
cannot create charger 'template'
cannot create charger 'eebus'
i/o timeout
Bitte überprüfe deine Konfigurationsdatei. Sollte dir die Fehlermeldung nicht weiterhelfen, suche in unseren GitHub Diskussionen nach einer Lösung.

.. Seite.

Hier noch ein Auszug vom Log (Debug mode)

Neustart HomeAssistant, Elli Wallbox, Neukopplung brachten keine Abhilfe.

Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main ] INFO 2023/06/11 13:18:10 evcc 0.118.0
[main ] INFO 2023/06/11 13:18:10 using config file: /config/evcc.yaml
[main ] INFO 2023/06/11 13:18:10 starting ui and api at :7070
[db ] INFO 2023/06/11 13:18:10 using sqlite database: /data/evcc.db
[mqtt ] INFO 2023/06/11 13:18:10 connecting evcc-660423155 at tcp://192.168.188.56:1883
[mqtt ] DEBUG 2023/06/11 13:18:10 tcp://192.168.188.56:1883 connected
[eebus ] INFO 2023/06/11 13:18:10 Local SKI: 54e07c6b293baf90c3c2a6c0ef18ac641c9aa5b9
[eebus ] DEBUG 2023/06/11 13:18:10 mdns: announce
[eebus ] DEBUG 2023/06/11 13:18:10 mdns: using zeroconf
[eebus ] DEBUG 2023/06/11 13:18:10 starting websocket server on :4712
[eebus ] DEBUG 2023/06/11 13:18:10 mdns: start search
[eebus ] DEBUG 2023/06/11 13:18:10 ski: bb661a4fc1650c04c34f53c1154259651ddab929 name: Elli-Wallbox-2223A2K669 brand: Elli model: Wallbox typ: Wallbox identifier: Elli-Wallbox-2223A2K669 register: false host: wallbox-2223A2K669.local. port: 4712 addresses: [192.168.188.16]
[eebus ] DEBUG 2023/06/11 13:18:10 delaying connection to bb661a4fc1650c04c34f53c1154259651ddab929 by 1.565s to minimize double connection probability
[eebus ] DEBUG 2023/06/11 13:18:11 trying to connect to bb661a4fc1650c04c34f53c1154259651ddab929 at 192.168.188.16
[eebus ] DEBUG 2023/06/11 13:18:11 initiating connection to bb661a4fc1650c04c34f53c1154259651ddab929 at 192.168.188.16:4712
[eebus ] DEBUG 2023/06/11 13:18:12 bb661a4fc1650c04c34f53c1154259651ddab929 websocket read error: websocket: close 4452: Node rejected by application.
[eebus ] DEBUG 2023/06/11 13:18:12 restarting mdns search
[eebus ] DEBUG 2023/06/11 13:18:12 delaying connection to bb661a4fc1650c04c34f53c1154259651ddab929 by 7.799s to minimize double connection probability
[eebus ] DEBUG 2023/06/11 13:18:19 trying to connect to bb661a4fc1650c04c34f53c1154259651ddab929 at 192.168.188.16
[eebus ] DEBUG 2023/06/11 13:18:19 initiating connection to bb661a4fc1650c04c34f53c1154259651ddab929 at 192.168.188.16:4712
[eebus ] DEBUG 2023/06/11 13:18:20 bb661a4fc1650c04c34f53c1154259651ddab929 websocket read error: websocket: close 4452: Node rejected by application.
[eebus ] DEBUG 2023/06/11 13:18:20 restarting mdns search
[eebus ] DEBUG 2023/06/11 13:18:20 delaying connection to bb661a4fc1650c04c34f53c1154259651ddab929 by 26.428s to minimize double connection probability
[eebus ] DEBUG 2023/06/11 13:18:46 trying to connect to bb661a4fc1650c04c34f53c1154259651ddab929 at 192.168.188.16
[eebus ] DEBUG 2023/06/11 13:18:46 initiating connection to bb661a4fc1650c04c34f53c1154259651ddab929 at 192.168.188.16:4712
[eebus ] DEBUG 2023/06/11 13:18:46 bb661a4fc1650c04c34f53c1154259651ddab929 websocket read error: websocket: close 4452: Node rejected by application.
[eebus ] DEBUG 2023/06/11 13:18:46 restarting mdns search
[eebus ] DEBUG 2023/06/11 13:18:46 delaying connection to bb661a4fc1650c04c34f53c1154259651ddab929 by 42.695s to minimize double connection probability
[eebus ] DEBUG 2023/06/11 13:19:29 trying to connect to bb661a4fc1650c04c34f53c1154259651ddab929 at 192.168.188.16
[eebus ] DEBUG 2023/06/11 13:19:29 initiating connection to bb661a4fc1650c04c34f53c1154259651ddab929 at 192.168.188.16:4712
[eebus ] DEBUG 2023/06/11 13:19:29 bb661a4fc1650c04c34f53c1154259651ddab929 websocket read error: websocket: close 4452: Node rejected by application.
[eebus ] DEBUG 2023/06/11 13:19:29 restarting mdns search
[eebus ] DEBUG 2023/06/11 13:19:29 delaying connection to bb661a4fc1650c04c34f53c1154259651ddab929 by 2m39.879s to minimize double connection probability
[main ] FATAL 2023/06/11 13:19:40 cannot create charger 'wallbox': cannot create charger 'template': cannot create charger 'eebus': i/o timeout
[main ] FATAL 2023/06/11 13:19:40 will attempt restart in: 5m0s
[eebus ] DEBUG 2023/06/11 13:22:09 trying to connect to bb661a4fc1650c04c34f53c1154259651ddab929 at 192.168.188.16
[eebus ] DEBUG 2023/06/11 13:22:09 initiating connection to bb661a4fc1650c04c34f53c1154259651ddab929 at 192.168.188.16:4712
[eebus ] DEBUG 2023/06/11 13:22:10 bb661a4fc1650c04c34f53c1154259651ddab929 websocket read error: websocket: close 4452: Node rejected by application.
[eebus ] DEBUG 2023/06/11 13:22:10 restarting mdns search
[eebus ] DEBUG 2023/06/11 13:22:10 delaying connection to bb661a4fc1650c04c34f53c1154259651ddab929 by 5m29.943s to minimize double connection probability
[eebus ] DEBUG 2023/06/11 13:24:40 mdns: stop announcement

Die URL direkt (über Port 7070) aufzurufen ist leider ebenfalls erfolglos - solange nicht die "finale" Fehlermeldung kommt. Im Firefox meldet er, dass die Websocketverbindung nicht aufgebaut werden kann. :(

"Firefox kann keine Verbindung zu dem Server unter ws://homeassistant.local:7070/ws aufbauen."

Viele Grüße

Describe the bug

When I use the nightly add on in home assistant it seems to use a very old version. If I use the "normal" version it uses newer version.

Is there a way to force a new version?

Nightly:
Using config file: /config/evcc.yaml
starting evcc: 'evcc --config /config/evcc.yaml --sqlite /data/evcc.db'
[main ] INFO 2023/01/03 12:40:39 evcc 0.107.1 (c87df312)
[main ] INFO 2023/01/03 12:40:39 using config file: /config/evcc.yaml
[main ] INFO 2023/01/03 12:40:39 starting ui and api at :7070
[main ] FATAL 2023/01/03 12:40:51 cannot create charger 'twc3': invalid charger type: twc3
[main ] FATAL 2023/01/03 12:40:51 will attempt restart in: 5m0s

Normal:
Using config file: /config/evcc.yaml
starting evcc: 'evcc --config /config/evcc.yaml --sqlite /data/evcc.db'
[main ] INFO 2023/01/03 12:45:43 evcc 0.110.1
[main ] INFO 2023/01/03 12:45:43 using config file: /config/evcc.yaml
[main ] INFO 2023/01/03 12:45:43 starting ui and api at :7070

Steps to reproduce

...
Using config file: /config/evcc.yaml
starting evcc: 'evcc --config /config/evcc.yaml --sqlite /data/evcc.db'
[main ] INFO 2023/01/03 12:45:43 evcc 0.110.1
[main ] INFO 2023/01/03 12:45:43 using config file: /config/evcc.yaml
[main ] INFO 2023/01/03 12:45:43 starting ui and api at :7070

Configuration details

Using config file: /config/evcc.yaml
starting evcc: 'evcc --config /config/evcc.yaml --sqlite /data/evcc.db'
[main  ] INFO 2023/01/03 12:45:43 evcc 0.110.1
[main  ] INFO 2023/01/03 12:45:43 using config file: /config/evcc.yaml
[main  ] INFO 2023/01/03 12:45:43 starting ui and api at :7070

Log details

Using config file: /config/evcc.yaml
starting evcc: 'evcc --config /config/evcc.yaml --sqlite /data/evcc.db'
[main  ] INFO 2023/01/03 12:45:43 evcc 0.110.1
[main  ] INFO 2023/01/03 12:45:43 using config file: /config/evcc.yaml
[main  ] INFO 2023/01/03 12:45:43 starting ui and api at :7070

What type of operating system are you running?

Docker container

Version

No response

Hi,
as mention in my previous post I'm new to HASSIO but I've been using evcc. Yesterday I finally got it running under HASSIO, at least the app shows up and the meters are shown correctly.
As the vehicle is not shown properly under 0.110.1 the latest evcc versions seem to need some tuning as I'm coming from an older version and there are now commands like evcc-vehicle for troubleshooting on the command line.
Entering those to the Terminal produces an error since apparently the evcc command is not recognized.

Where is evcc located within HASSIO, is there a way to navigate there? I can't find the installation...
How to control evcc via command line?

BR
Michael

Hi,
I think to use the build in Modbus proxy, the port that is used by Modbus proxy needs to be exposed by the add-on.
Default port is 5200 I think
Could you add this, or is there a way to expose the port to home assistant by our own?

Thank you!
letsid

There is a new preferred way to store configs. We should implement that and somehow provide a migration for legacy installations

https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/

https://developers.home-assistant.io/docs/add-ons/configuration/#add-on-advanced-options

Hello everyone,

When configuring my Tesla, I used the "tesla-command" setting with the correct tokens.

When starting evvc the following error occurs:

[main ] ERROR 2024/01/26 07:07:26 creating vehicle ev4 failed: cannot create vehicle type 'template': template not found: tesla-command

If I use the same settings on a linux-evvc everything works.

Is the above not yet supported by the HA-plugin?

Greetings

I installed the add-on and it is shown in side bar. As configured it starts at system start and I tried to start in manually. But it doesn't work. Each time I click the sidebar entry it says "Add-on is not running. Please start it first". Any ideas?

Just to be sure: Do I only have to install the plugin or do I have do install the evcc.io system seperatly before the add-on works? And where? ;-)

I got the problem that evcc addon is restarting every 3 minutes. Before it was working without issues.
I found out that supervisor is restarting the addon: [supervisor.addons.addon] Watchdog found addon evcc is unhealthy, restarting...

When I use a browser to go to http://IP:7070/api/health I get OK

But when I run

docker exec addon_..._evcc sh -c "/usr/local/bin/evcc -c /config/evcc.yaml health"
...
[main  ] ERROR  _timestamp_ health check failed

I'm not experienced enough for docker if this above command is correct, but I think this is executed considering the Dockerfile.

Is there anything I can do to debug this further?
For now I deactivated the watchdog and evcc addon is working fine.

Hallo zusammen,

ich wollte gerade meine aktuelle EVCC Installation die separat in einer VM läuft in das HomeAssistant Addon kopieren, leider bekomme ich dann folgende Meldung: failed configuring hems: creating device id: machineid: machineid: open /etc/machine-id: no such file or directory.

Daraufhin habe ich die machine-id Datei in den /etc Ordner von HomeAssistant kopiert, leider auch ohne Erfolg.
Eigentlich erstellt doch die EVCC Konfiguration diese ID oder nicht. Das passiert natürlich nicht, wenn ich die .yaml Datei einfach nur kopier. Funktioniert das überhaupt?

Danke.
Gruß

Hello,

I would really like to use evcc, but unfortunately I can't even get it to start :(

In my config folder from the HA I created a file evcc.yaml. Unfortunately I get an error when trying to start it, with the information that the config cannot be found... where is my mistake?

Thanks.

GEtting timeouts for any ip address in config:

Any ideas anyone? :-)

Hi, when I configure OCPP as charger, the add on doesn't start anymore (Bad Gateway 502). Only the few following lines show up in the logs:

starting evcc: 'evcc --config /config/evcc.yaml --sqlite /data/evcc.db'
[main  ] INFO 2023/02/10 22:04:28 evcc 0.112.5
[main  ] INFO 2023/02/10 22:04:28 using config file: /config/evcc.yaml
[main  ] INFO 2023/02/10 22:04:28 starting ui and api at :7070

When I configure a different wallbox, it starts without any problem.

This works

chargers:
  - name: stellplatz
    type: template
    template: tplink
    host: 192.0.2.2 # IP-Adresse oder Hostname
    standbypower: 15

This doesn't

chargers:
  - name: stellplatz
    type: template
    template: ocpp
    meter: false

Can you help me to solve this?

Hi,

I'm new to HASSIO while I've been running EVCC on a separate Raspi for a while. It's running well there, also with the latest version.
Now I I'm going my first steps in HASSIO and installed the EVCC addon yesterday.
I'm using the same EVCC.yaml as on the other Raspi, just modified the IP address of the host, but unfortunately I don't get this thing running under HASSIO.
Error message:
failed configuring hems
creating device id
could not get machineid: open /etc/machine-id: no such file or directory; for manual configuration use plant: 31c8b2670e3a30826056e8be77d7dbb8739e47b7c8526f3512cf747f47db8c0a
machineid: open /etc/machine-id: no such file or directory

What is wrong with that?

BR
Michael

I am running evcc for almost one year and until December 2023 it worked absolutly fine. It is running as HACS Add-on in Home Assistant. And this is running in a "virtuel maschine" on a synology DS1522. Any idea, what I can do? Thanks!!!

On port 7070 I do get this error:

Fehler beim Starten
cannot create vehicle 'Citroen'
cannot create vehicle type 'template'
invalid key: targetsoc

I did get nearly the same error only with the Hyundai. It changes after a reboot sometimes.

This is my config:

meters:

• name: my_grid
  type: template
  template: rct-power
  usage: grid
  host: 192.168.178.197
• name: my_pv
  type: template
  template: rct-power
  usage: pv
  host: 192.168.178.197
• name: my_battery
  type: template
  template: rct-power
  usage: battery
  host: 192.168.178.197

chargers:

• type: template
  template: keba
  host: 192.168.178.169
  serial: *****
  name: Keba Wallbox

tariffs:
currency: EUR
grid:
type: fixed
price: 0.3368 # [currency]/kWh
feedin:
type: fixed
price: 0.08 # [currency]/kWh

vehicles:

• name: Ioniq5
  type: template
  template: hyundai
  title: Ioniq5
  user: *****
  password: *****
  vin: *****
  capacity: 72
  phases: 3
  icon: car
  cache: 15m
  language: de
  mode: minpv
  targetSoc: 80
• name: Citroen
  type: template
  template: citroen
  title: c5 aircross hybrid
  user: *****
  password: *****
  vin: *****
  capacity: 12
  phases: 1
  icon: car
  cache: 15m
  language: de
  mode: pv
  targetSoc: 100
  loadpoints:
• title: F19
  charger: Keba Wallbox
  mode: now
  phases: 3
  mincurrent: 10
  maxcurrent: 16
  resetOnDisconnect: true

site:
title: F19 Home
meters:
grid: my_grid
pvs:
- my_pv

Do you create a repo in evcc-io?

I added the "https://github.com/evcc-io/hassio-addon"-URL in the repository settings of Home Assistant 10.1.
In the Add-on Store i find the category "Evcc" but there are no addons available.
i did test a different version of Home Assistant -> same issue
Reboot -> same issue

Is this a known issue or what can i do to resolve this problem?
Thank you

I have successfully configured EVCC in my HA installation, everything works perfectly.

The only thing that is a bit annoying: I have to manually enable the charging by clicking on "fast charging" in the EVCC web interface. I don't seem to find a way to automate this as the EVCC integration doesn't expose any of the controls to HA. Would be great if that was possible.

Could you please look into this?

evcc-io/evcc#3806 (reply in thread)

If evcc is hosted in a docker environment on home assistant the OAuth 2.0 redirecting is not working correctly, because the url of mercedes for the authentification process get's blocked in the home assistant container.

I am littlebit confused what are the network ports settings in the configuration page are for becuse this ports are not opened on the host.
Nevertheless I configured modbusproxy in evcc.yaml but the connection is timing out.

HASS IP: 192.168.1.50

modbusproxy:
  - port: 5200
    uri: 192.168.5.225:502 #Inverter


meters:
  - name: huawei_grid
    type: template
    template: huawei-dongle-powersensor
    usage: grid
    modbus: tcpip
    id: 1
    host: 192.168.1.50 #IP of HASS
    port: 5200

[site ] ERROR 2023/08/05 12:14:12 grid meter: read failed: modbus: exception '4' (server device failure), function '3' [site ] ERROR 2023/08/05 12:14:12 grid meter: read failed: modbus: exception '4' (server device failure), function '3'

When I am using the Inverter IP in meters settings then the connection is working.
What is wrong here?

In Addon-Configuration if I see it right there is no way to forward the port 7070 externally for the webui. I would like to use it like homeassistant_ip:7070.

In my evcc.yml the homeassistant ip is already set, but as I said the access over the host ip is not possible, I can only access the webui in homeassistant.

[site ] ERROR 2022/09/20 17:06:42 grid meter: read failed: could not open /dev/ttyUSB1: operation not permitted

ha hardware info & ls -l /dev/serial/by-id lists the stick on /dev/ttyUSB1

Sorry, wrong seciton

Hi,

since the latest update 2 days ago my HA-Addon won't start anymore, giving me the following error in the log:

Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2023/12/24 17:05:38 evcc 0.123.1
[main  ] INFO 2023/12/24 17:05:38 using config file: /config/evcc.yaml
[main  ] INFO 2023/12/24 17:05:38 starting ui and api at :7070
[main  ] FATAL 2023/12/24 17:05:39 failed configuring loadpoints: failed configuring loadpoint: 1 error(s) decoding:

* '' has invalid keys: resetondisconnect
[main  ] FATAL 2023/12/24 17:05:39 will attempt restart in: 5m0s

I have the same error on 2 separate instances. I wish I could go into more troubleshooting, but I cannot understand the fatal error at all.
A fresh install with the same config didn't change the problem.

I have problems with scheduled loading of my vehicle and therefore wanted to create an issue.

Unfortunately i have no access to the complete log under Home Assistant. The "Protokoll" that i can see at the Add-ons/evcc page is only limited to a few lines and not scrollable.

How can i access the complete log?

Hi
I have inserted the Repository but i am not able to find the addon.

I have:

• Elli Connect @ v3.8.13
• evcc @ 0.121.2

When I try to run evcc confgiure I reach to the point of pairing both. Elli UI detects evcc and I click on "pair" - Elli asks to confirm evcc's SKI, but they don't match. I click on "ok" anyway. Then I press Enter in evcc. After some minutes I see:

Führe folgende Einstellungen durch:

 Identifikationsschlüssel (SKI) 60e799cfb00228fe9ac7aedd75da962ae7020a7f
 IP-Adresse 192.168.178.29

Teste die Konfiguration von Elli Charger Connect (Beta) ...
   Fehler: cannot create charger 'eebus': i/o timeout

 Der Test von Elli Charger Connect (Beta) ist fehlgeschlagen.

What shall I do now?

Using config file:  /config/evcc.yaml
starting evcc: 'evcc --config  /config/evcc.yaml'
[main  ] INFO 2022/09/28 17:25:06 evcc 0.104
[main  ] INFO 2022/09/28 17:25:06 using config file: /config/evcc.yaml
[main  ] INFO 2022/09/28 17:25:06 listening at :7070
[main  ] FATAL 2022/09/28 17:25:06 machineid: open /etc/machine-id: no such file or directory
[main  ] FATAL 2022/09/28 17:25:06 will attempt restart in: 5m0s

Seems like a docker/addon specific issue. Please help

Hello,

I've installed EVCC as add on in homeassistant. It works so far. Now I wanted to setup the RFID identifier. In the documentation it is mentioned that I should use "evcc charger" on the commandline. I tried it with the "Advanced SSH & Web Terminal" wich is also installed as an add on inside HA. I get always command not found.

Can someone give me a hint how to receive the RFID identifier in the EVCC add on?

Thanks

Hi, I'm new to this addon - so maybe, I've just missed some steps during the setup...

I am running HomeAssistant for some time now, having my Inverter included and also my openWB so far.
Now, I want to add EVCC into HomeAssistant, in order to get information from my Skoda Enyaq into the system.

As an alternative method, I found an integration "skodaconnect" - which will connect to the skodaconnect servers.... - but I think, I would prefer EVCC, because that would allow me to get the SoC from Skoda into the OpenWB more easily.

But after the installation of this Addon - and starting it, I am just getting an 502: Bad Gateway error.
Do I need to install something else?
Do I need to change some configurations?
I haven't seen any further documentation here on the readme... but have I missed something?

Hi
Today I found that an mqtt topic I am using in the meter configuration got a timeout since last update to 0.120.0
Before the update it worked.

evcc.yaml
...
meters:

• name: grid_meter
  type: custom
  power:
  source: mqtt
  topic: ha/sensor/energie_surplus2/state
  timeout: 30s # don't accept values older than timeout
  scale: -1
  ...

And the (new) definition of the sensor in HA:
...

• platform: template
  sensors:
  energie_surplus2:
  friendly_name: "PV Ueberschuss (inkl. Akku Ladung)"
  unit_of_measurement: 'W'
  value_template: >-
  {% if ((states('sensor.battery_charge_discharge_power') | int) > 0) %}
  {{ states("sensor.power_meter_active_power") | int }}
  {% else %}
  {{ states("sensor.power_meter_active_power") | int + states("sensor.battery_charge_discharge_power") | int }}
  {% endif %}
  ...

Befor update the friendly_name was "PV Überschuss (inkl. Akku Ladung)"
After Update this topic got a timeout in ha:
[site ] ERROR 2023/09/19 18:57:34 grid meter: ha/sensor/energie_surplus2/state outdated: 34s

Changed Ü ==> Ue and everything worked again

I've been using EVCC on a VM for over nine months and now wanted to switch to the addon in the Home Assistant.
However, I haven't managed to integrate the old evcc.db via the config for the sqlite_file yet.

The sql file is not read in the predefined /data/... as well as in other folders and is not visible in the loading processes.

Hello,

I'm having an issue with my EVCC Addon.
It worked quite a while, but since some weeks it's randomly producing an error with the sponsortoken I need for it.
The Addon stays in a sort of loop starting up giving the error:

FATAL 2023/12/24 13:04:48 sponsortoken: rpc error: code = Unknown desc = token contains an invalid number of segments

I wrote to andig already, but he says, the token is correct, it may be a problem with HA.
When installed on my comptuer directly (outside HA) it works, but I want to use the addon because of some parameters I can't reach in the standalone installation.

As I do sponsor the addon for using it, I would like to have a working system. It's not feasible to get new sponsortoken every week, as a new token also doesn't always solve the problem.
Also re-installation of the addon doesn't help.

Do you have an idea, what's going wrong? Can I help with some logs?

Thanks for helping

Dietmar Grasl
49686a9f_evcc_2023-12-28T16-44-58.884Z.log
supervisor_2023-12-28T16-45-20.105Z.log

Hi, I was trying to set up the evcc hassio addon with my GoodWe Inverter. I get the following message after starting the addon:

cannot create meter 'my_grid'
cannot create meter 'template'
template not found: goodwe-hybrid

using the GoodWe yaml template in the provided evcc.yaml template (edited to my needs):

meters:
  - name: my_grid
    type: template
    template: goodwe-hybrid
    usage: grid      
    
    # Modbus TCP
    modbus: tcpip
    id: 247
    host: aaa.bbb.ccc.ddd # Hostname
    port: 502 # Port 

Can't install andig/evcc:0.93: 404 Client Error for http+docker://localhost/v1.41/images/create?tag=0.93&fromImage=andig%2Fevcc&platform=linux%2Famd64: Not Found ("manifest for andig/evcc:0.93 not found: manifest unknown: manifest unknown")

Since I restarted my home assistant, the evcc add-on is in a ongoing starting procedure for a few days now.

What sould I do now?

After many hours of trial and error I managed to get the add-on to work. The biggest issue is with the Loadpoint configuration. I have no clue what value to enter for charge meter. If I leave it at „meter“ the system fails to start with an error message that the Loadpoint has an issue.
I put an # in front of the line. Now the system starts and works but with a message:

Garage: charger logic error: disabled but charging

Below I have pasted the relevant part of the yaml file.
I would be very grateful if someone could tell me what value to put for meter.
Many thank is advance!
Joop

meters:

• name: grid
  type: template
  template: sonnenbatterie
  usage: grid
  host: 192.168.178.51 # IP-Adresse oder Hostname

• name: battery
  type: template
  template: sonnenbatterie
  usage: battery
  host: 192.168.178.51 # IP-Adresse oder Hostname

• name: pv
  type: template
  template: sonnenbatterie
  usage: pv
  host: 192.168.178.51 # IP-Adresse oder Hostname

charger definitions

name can be freely chosen and is used as reference when assigning charger to vehicle

for documentation see https://docs.evcc.io/docs/devices/chargers

chargers:

• name: go-e
  type: template
  template: go-e
  host: 192.168.178.100 # IP-Adresse oder Hostname

vehicle definitions

name can be freely chosen and is used as reference when assigning vehicle to loadpoint

for documentation see https://docs.evcc.io/docs/devices/vehicles

vehicles:

• name: car1
  type: xxx
  title: xxx
  capacity: 68 # kWh
  user: myuser # user
  password: mypassword # password
  vin: WREN...
  onIdentify: # set defaults when vehicle is identified
  mode: pv # enable PV-charging when vehicle is identified
  minSoc: 20 # immediately charge to 20% regardless of mode unless "off" (disabled)
  targetSoc: 90 # limit charge to 90%

site describes the EVU connection, PV and home battery

site:
title: Home # display name for UI
meters:
grid: grid # grid meter
pv:
- pv # list of pv inverters/ meters
battery:
- battery # list of battery meters

residualPower: 0 # additional household usage margin
prioritySoc: 0 # give home battery priority up to this soc (empty to disable)
bufferSoc: 0 # continue charging on battery above soc (0 to disable)
bufferStartSoc: 0 # start charging on battery above soc (0 to disable)
maxGridSupplyWhileBatteryCharging: 0 # ignore battery charging if AC consumption is above this value
smartCostLimit: 0 # set cost limit for automatic charging in PV mode

loadpoint describes the charger, charge meter and connected vehicle

loadpoints:

• title: Garage # display name for UI
  charger: go-e # charger

meter: charge # charge meter NO IDEA WHAT TO PUT HERE

Hi,

i am trying to install the Add-on on Home assistant. But i get the following error.

Mein EVCC als Add-on in Homeassistant startet nicht mehr nach dem Update!
Using config file: /config/evcc.yaml
Config not found. Please create a config under /config/evcc.yaml.
Die Addon-configs werden seit einem der letzten HA Updates in /addon_configs/49686a9f_evcc/ gespeichert. Dort ist das evcc.yaml auch.

Scheint dass EVCC das dort nicht sucht.
Wenn ich den Ordner in der Config ändere kommt gleiche Fehlermeldung.

Originally posted by @stefa75 in evcc-io/evcc#10978 (comment)

Hi!

Would it be possible to update the add-on to the latest version of lvcc since TWC3 is now added to the master branch?

That will provide support for Tesla Wall Changers

Thanks

Hi,

am not able to start the add-on in my HA with setting up KEBA p30-x Wallbox. It looks like the port 7090 is already using on the docker network.

Using config file: /config/evcc.yaml
starting evcc: 'evcc --config /config/evcc.yaml --sqlite /data/evcc.db' br>
[main  ] INFO 2023/01/22 12:41:39 evcc 0.111.1
[main  ] INFO 2023/01/22 12:41:39 using config file: /config/evcc.yaml
[main  ] INFO 2023/01/22 12:41:39 starting ui and api at :7070
[main  ] FATAL 2023/01/22 12:41:39 cannot create charger 'my_charger': cannot create charger 'template': cannot create charger 'keba': listen udp :7090: bind: address already in use
[main  ] FATAL 2023/01/22 12:41:39 will attempt restart in: 5m0s

Cannot reach Tesla API anymore:

Anyone else with this problem?