search

evcc-io / evcc

Solar Charging ☀️🚘
https://evcc.io
MIT License
3.67k stars 686 forks source link

EVCC not starting after update to 0.127.0 #14321

Closed pandamouse84 closed 5 months ago

pandamouse84 commented 5 months ago

Describe the bug

EVCC is not starting after having updated to 0.127.0

Steps to reproduce

  1. Update to 0.127.0
  2. Have a look at the logs

Configuration details

# open evcc at http://evcc.local:7070
network:
  schema: http
  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070

log: info
levels:
  cache: error

# unique installation id
plant: XXX

interval: 30s # control cycle interval

meters:
  - type: template
    template: varta
    usage: grid
    host: XXX.XXX.XXX.XXX
    port: 502
    name: gridVarta

chargers:
  - name: wallboxElli
    type: template
    template: ellipro
    ip: XXX.XXX.XXX.XXX
    ski: XXX

loadpoints:
  - title: Carport
    charger: wallboxElli

tariffs:
  co2:
    type: grünstromindex
    zip: XXXXX
  currency: EUR
  grid:
    type: fixed
    price: 0.2999

site:
  title: Mein Zuhause
  meters:
    grid: gridVarta
  residualPower: 100

eebus:
  certificate:
    private: |
      -----BEGIN EC PRIVATE KEY-----
Xxx
      -----END EC PRIVATE KEY-----
    public: |
      -----BEGIN CERTIFICATE-----
Xxx
      -----END CERTIFICATE-----

Log details

Using config file: /config/custom_yaml/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/custom_yaml/evcc.yaml'
[main  ] INFO 2024/06/12 22:03:14 evcc 0.127.0
[main  ] INFO 2024/06/12 22:03:14 using config file: /config/custom_yaml/evcc.yaml
[db    ] INFO 2024/06/12 22:03:14 using sqlite database: /data/evcc.db
[main  ] INFO 2024/06/12 22:03:14 listening at :7070
[main  ] FATAL 2024/06/12 22:03:14 cannot create charger 'wallboxElli': cannot create charger type 'template': cannot create charger type 'eebus': eebus not configured
[main  ] FATAL 2024/06/12 22:03:14 will attempt restart in: 15m0s

What type of operating system are you running?

HomeAssistant Add-on

Version

0.127.0

eny34 commented 5 months ago

Same issue here:

[main ] FATAL 2024/06/12 22:08:15 cannot create charger 'wallbox6': cannot create charger type 'template': cannot create charger type 'eebus': eebus not configured [main ] FATAL 2024/06/12 22:08:15 will attempt restart in: 15m0s

pandamouse84 commented 5 months ago

btw.

will attempt restart in: 15m0s

From the logs it looks like he is trying to restart every 3 minutes. Maybe you want to put the correct var in that text.

pandamouse84 commented 5 months ago

Referring to the changelog I would check #14298, the fix applied for EEBUS, maybe the bug is in there.

kloeppb commented 5 months ago

Same error here just upgraded from working system version 0.126.6

Using config file: /config/evcc.yaml starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml' [main ] INFO 2024/06/12 22:14:13 evcc 0.127.0 [main ] INFO 2024/06/12 22:14:13 using config file: /config/evcc.yaml [db ] INFO 2024/06/12 22:14:14 using sqlite database: /data/evcc.db [mqtt ] INFO 2024/06/12 22:14:14 connecting evcc-2062920207 at tcp://localhost:1883 [main ] INFO 2024/06/12 22:14:14 listening at :7070 [main ] FATAL 2024/06/12 22:14:17 cannot create charger 'connect_pro': cannot create charger type 'template': cannot create charger type 'eebus': eebus not configured [main ] FATAL 2024/06/12 22:14:17 will attempt restart in: 15m0s

MarcusLindemann commented 5 months ago

Same issue here after upgrading working system from 0.126.6 to 0.127 on Raspbian bullseye.

[main ] INFO 2024/06/12 22:39:21 evcc 0.127.0
[main ] INFO 2024/06/12 22:39:21 using config file: /etc/evcc.yaml
[db ] INFO 2024/06/12 22:39:25 using sqlite database: /var/lib/evcc/evcc.db
[mqtt ] INFO 2024/06/12 22:39:26 connecting evcc-354576817 at tcp://xxxxx:1883
[mqtt ] DEBUG 2024/06/12 22:39:26 tcp://xxxxx:1883 connected
[main ] INFO 2024/06/12 22:39:26 listening at :7070
[main ] FATAL 2024/06/12 22:39:26 cannot create charger 'wallbox2': cannot create charger type 'template': cannot create charger type 'eebus': eebus not configured
[main ] FATAL 2024/06/12 22:39:26 will attempt restart in: 15m0s
cschnatz commented 5 months ago

Same issue too after upgrading from 0.126.6 to 0.127

Jun 13 06:35:07 csc-evcc evcc[273886]: [main ] FATAL 2024/06/13 06:35:07 cannot create charger 'Links': cannot create charger type 'template': cannot create charger type 'eebus': eebus not configured

The config itself contains the eebus configuration


  certificate:
    public: |
      -----BEGIN CERTIFICATE-----
    XYZ
      -----END CERTIFICATE-----

    private: |
      -----BEGIN EC PRIVATE KEY-----
      XYZ
      -----END EC PRIVATE KEY-----```
dennisfisch commented 5 months ago

Same here, upgrading from working 0.125.0 to 0.127.0

pencoe commented 5 months ago

Just to add my voice: same here after upgrading from 0.126.5 to 0.127.0

mattbalzer commented 5 months ago

Same here, upgrading from not working 0.126.6 to 0.127.0

VolkerK62 commented 5 months ago

Ich denke, ihr könnt aufhören mit "bei mir auch". ;-)

Marty56 commented 5 months ago

Funktioniert immer noch nicht.

[main  ] INFO 2024/06/13 05:40:57 evcc 0.127.0
[main  ] INFO 2024/06/13 05:40:57 using config file: /config/mydockerdata/evcc/yaml/evcc.yaml
[db    ] INFO 2024/06/13 05:40:58 using sqlite database: /config/mydockerdata/evcc/sql/evcc.db
[mqtt  ] INFO 2024/06/13 05:40:58 connecting evcc at tcp://192.168.10.132:1884
[main  ] INFO 2024/06/13 05:40:58 listening at :7070
[main  ] FATAL 2024/06/13 05:40:58 cannot create charger 'wallbox': cannot create charger type 'template': cannot create charger type 'eebus': eebus not configured
[main  ] FATAL 2024/06/13 05:40:58 will attempt restart in: 15m0s
Using config file: /config/mydockerdata/evcc/yaml/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/config/mydockerdata/evcc/sql/evcc.db evcc --config /config/mydockerdata/evcc/yaml/evcc.yaml'
[main  ] INFO 2024/06/14 08:02:14 evcc 0.127.1
[main  ] INFO 2024/06/14 08:02:14 using config file: /config/mydockerdata/evcc/yaml/evcc.yaml
[db    ] INFO 2024/06/14 08:02:14 using sqlite database: /config/mydockerdata/evcc/sql/evcc.db
[mqtt  ] INFO 2024/06/14 08:02:14 connecting evcc at tcp://192.168.10.132:1884
[eebus ] INFO 2024/06/14 08:02:14 Local SKI:  d7138aeb02b47ae2a6f10eebeb83e3d87dca63b1
[main  ] INFO 2024/06/14 08:02:14 listening at :7070
[main  ] FATAL 2024/06/14 08:03:44 cannot create charger 'wallbox': cannot create charger type 'template': cannot

Log mit Debug Log Level

[main ] INFO 2024/06/14 08:09:46 evcc 0.127.1
[main ] INFO 2024/06/14 08:09:46 using config file: /config/mydockerdata/evcc/yaml/evcc.yaml
[db ] INFO 2024/06/14 08:09:46 using sqlite database: /config/mydockerdata/evcc/sql/evcc.db
[mqtt ] INFO 2024/06/14 08:09:46 connecting evcc at tcp://192.168.10.132:1884
[eebus ] INFO 2024/06/14 08:09:46 Local SKI: d7138aeb02b47ae2a6f10eebeb83e3d87dca63b1
[mqtt ] DEBUG 2024/06/14 08:09:46 tcp://192.168.10.132:1884 connected
[eebus ] DEBUG 2024/06/14 08:09:46 mdns: announce
[eebus ] DEBUG 2024/06/14 08:09:46 mdns: using zeroconf
[eebus ] DEBUG 2024/06/14 08:09:46 starting websocket server on :4712
[main ] INFO 2024/06/14 08:09:46 listening at :7070
[eebus ] DEBUG 2024/06/14 08:09:46 mdns: start search
[eebus ] DEBUG 2024/06/14 08:09:46 ski: b456c8f752941d4da9333d84438f5b60848dd805 name: Elli-Wallbox-2111A1924D brand: Elli model: Wallbox typ: Wallbox identifier: Elli-Wallbox-2111A1924D register: false host: wallbox-2111A1924D.local. port: 4712 addresses: [192.168.10.94]
[eebus ] DEBUG 2024/06/14 08:09:46 delaying connection to b456c8f752941d4da9333d84438f5b60848dd805 by 2.761s to minimize double connection probability
[eebus ] DEBUG 2024/06/14 08:09:49 trying to connect to b456c8f752941d4da9333d84438f5b60848dd805 at 192.168.10.94
[eebus ] DEBUG 2024/06/14 08:09:49 initiating connection to b456c8f752941d4da9333d84438f5b60848dd805 at 192.168.10.94:4712
[eebus ] DEBUG 2024/06/14 08:09:54 connection to b456c8f752941d4da9333d84438f5b60848dd805 failed: dial tcp 192.168.10.94:4712: i/o timeout
[eebus ] DEBUG 2024/06/14 08:09:54 trying to connect to b456c8f752941d4da9333d84438f5b60848dd805 at wallbox-2111A1924D.local.
[eebus ] DEBUG 2024/06/14 08:09:54 initiating connection to b456c8f752941d4da9333d84438f5b60848dd805 at wallbox-2111A1924D.local.:4712
[eebus ] DEBUG 2024/06/14 08:09:59 connection to b456c8f752941d4da9333d84438f5b60848dd805 failed: dial tcp 192.168.10.94:4712: i/o timeout
[eebus ] DEBUG 2024/06/14 08:09:59 restarting mdns search
[eebus ] DEBUG 2024/06/14 08:09:59 delaying connection to b456c8f752941d4da9333d84438f5b60848dd805 by 9.043s to minimize double connection probability
[mqtt ] ERROR 2024/06/14 08:09:59 tcp://192.168.10.132:1884 connection lost: EOF
[mqtt ] DEBUG 2024/06/14 08:10:00 tcp://192.168.10.132:1884 connected
[mqtt ] DEBUG 2024/06/14 08:10:00 tcp://192.168.10.132:1884 subscribe Energie/SENSOR
[eebus ] DEBUG 2024/06/14 08:10:08 trying to connect to b456c8f752941d4da9333d84438f5b60848dd805 at 192.168.10.94
[eebus ] DEBUG 2024/06/14 08:10:08 initiating connection to b456c8f752941d4da9333d84438f5b60848dd805 at 192.168.10.94:4712
[eebus ] DEBUG 2024/06/14 08:10:13 connection to b456c8f752941d4da9333d84438f5b60848dd805 failed: dial tcp 192.168.10.94:4712: i/o timeout
[eebus ] DEBUG 2024/06/14 08:10:13 trying to connect to b456c8f752941d4da9333d84438f5b60848dd805 at wallbox-2111A1924D.local.
[eebus ] DEBUG 2024/06/14 08:10:13 initiating connection to b456c8f752941d4da9333d84438f5b60848dd805 at wallbox-2111A1924D.local.:4712
[eebus ] DEBUG 2024/06/14 08:10:18 connection to b456c8f752941d4da9333d84438f5b60848dd805 failed: dial tcp 192.168.10.94:4712: i/o timeout
[eebus ] DEBUG 2024/06/14 08:10:18 restarting mdns search
[eebus ] DEBUG 2024/06/14 08:10:18 delaying connection to b456c8f752941d4da9333d84438f5b60848dd805 by 23.827s to minimize double connection probability
[eebus ] DEBUG 2024/06/14 08:10:41 trying to connect to b456c8f752941d4da9333d84438f5b60848dd805 at 192.168.10.94
[eebus ] DEBUG 2024/06/14 08:10:41 initiating connection to b456c8f752941d4da9333d84438f5b60848dd805 at 192.168.10.94:4712
[eebus ] DEBUG 2024/06/14 08:10:46 connection to b456c8f752941d4da9333d84438f5b60848dd805 failed: dial tcp 192.168.10.94:4712: i/o timeout
[eebus ] DEBUG 2024/06/14 08:10:46 trying to connect to b456c8f752941d4da9333d84438f5b60848dd805 at wallbox-2111A1924D.local.
[eebus ] DEBUG 2024/06/14 08:10:46 initiating connection to b456c8f752941d4da9333d84438f5b60848dd805 at wallbox-2111A1924D.local.:4712
[eebus ] DEBUG 2024/06/14 08:10:51 connection to b456c8f752941d4da9333d84438f5b60848dd805 failed: dial tcp 192.168.10.94:4712: i/o timeout
[eebus ] DEBUG 2024/06/14 08:10:51 restarting mdns search
[eebus ] DEBUG 2024/06/14 08:10:51 delaying connection to b456c8f752941d4da9333d84438f5b60848dd805 by 48.41s to minimize double connection probability
[main ] FATAL 2024/06/14 08:11:16 cannot create charger 'wallbox': cannot create charger type 'template': cannot create charger type 'eebus': i/o timeout
[main ] FATAL 2024/06/14 08:11:16 will attempt restart in: 15m0s
[eebus ] DEBUG 2024/06/14 08:11:40 trying to connect to b456c8f752941d4da9333d84438f5b60848dd805 at 192.168.10.94
[eebus ] DEBUG 2024/06/14 08:11:40 initiating connection to b456c8f752941d4da9333d84438f5b60848dd805 at 192.168.10.94:4712
[eebus ] DEBUG 2024/06/14 08:11:45 connection to b456c8f752941d4da9333d84438f5b60848dd805 failed: dial tcp 192.168.10.94:4712: i/o timeout
[eebus ] DEBUG 2024/06/14 08:11:45 trying to connect to b456c8f752941d4da9333d84438f5b60848dd805 at wallbox-2111A1924D.local.
[eebus ] DEBUG 2024/06/14 08:11:45 initiating connection to b456c8f752941d4da9333d84438f5b60848dd805 at wallbox-2111A1924D.local.:4712
[eebus ] DEBUG 2024/06/14 08:11:50 connection to b456c8f752941d4da9333d84438f5b60848dd805 failed: dial tcp 192.168.10.94:4712: i/o timeout
[eebus ] DEBUG 2024/06/14 08:11:50 restarting mdns search
[eebus ] DEBUG 2024/06/14 08:11:50 delaying connection to b456c8f752941d4da9333d84438f5b60848dd805 by 2m49.99s to minimize double connection probability
[eebus ] DEBUG 2024/06/14 08:14:40 trying to connect to b456c8f752941d4da9333d84438f5b60848dd805 at 192.168.10.94
[eebus ] DEBUG 2024/06/14 08:14:40 initiating connection to b456c8f752941d4da9333d84438f5b60848dd805 at 192.168.10.94:4712
[eebus ] DEBUG 2024/06/14 08:14:45 connection to b456c8f752941d4da9333d84438f5b60848dd805 failed: dial tcp 192.168.10.94:4712: i/o timeout
[eebus ] DEBUG 2024/06/14 08:14:45 trying to connect to b456c8f752941d4da9333d84438f5b60848dd805 at wallbox-2111A1924D.local.
[eebus ] DEBUG 2024/06/14 08:14:45 initiating connection to b456c8f752941d4da9333d84438f5b60848dd805 at wallbox-2111A1924D.local.:4712
[eebus ] DEBUG 2024/06/14 08:14:50 connection to b456c8f752941d4da9333d84438f5b60848dd805 failed: dial tcp 192.168.10.94:4712: i/o timeout
[eebus ] DEBUG 2024/06/14 08:14:50 restarting mdns search
[eebus ] DEBUG 2024/06/14 08:14:50 delaying connection to b456c8f752941d4da9333d84438f5b60848dd805 by 3m52.229s to minimize double connection probability
[eebus ] DEBUG 2024/06/14 08:18:42 trying to connect to b456c8f752941d4da9333d84438f5b60848dd805 at 192.168.10.94
[eebus ] DEBUG 2024/06/14 08:18:42 initiating connection to b456c8f752941d4da9333d84438f5b60848dd805 at 192.168.10.94:4712
[eebus ] DEBUG 2024/06/14 08:18:45 delaying connection to b456c8f752941d4da9333d84438f5b60848dd805 by 4m2.979s to minimize double connection probability
[eebus ] DEBUG 2024/06/14 08:18:47 connection to b456c8f752941d4da9333d84438f5b60848dd805 failed: dial tcp 192.168.10.94:4712: i/o timeout
[eebus ] DEBUG 2024/06/14 08:18:47 trying to connect to b456c8f752941d4da9333d84438f5b60848dd805 at wallbox-2111A1924D.local.
[eebus ] DEBUG 2024/06/14 08:18:47 initiating connection to b456c8f752941d4da9333d84438f5b60848dd805 at wallbox-2111A1924D.local.:4712
[eebus ] DEBUG 2024/06/14 08:18:52 connection to b456c8f752941d4da9333d84438f5b60848dd805 failed: dial tcp 192.168.10.94:4712: i/o timeout
[eebus ] DEBUG 2024/06/14 08:18:52 restarting mdns search
Uhrenradio commented 5 months ago

Scheint aber kein prinzipielles Problem mehr mit EEBus zu sein: Bei mir startet das Image 0.127.1 wieder sauber auf (Das war mal ein schneller BugFix). Wenn Logs und YAML weiter helfen kann ich die auf Anfrage gerne posten...

andig commented 5 months ago

I/o timeout hat nix hiermit zu tun.

Marty56 commented 5 months ago

wenn ich heute Abend Zuhause bin, schalte ich die Wallbox vom Strom. Mal sehn, ob es danach geht. Das hatte ich früher schon mal. Die Elli Box ist echt Scheiße.

eny34 commented 5 months ago

Bei mir funktioniert alles. Auch mit Elli Box, 0.127.1 und Enyaq über MySkoda. Danke für den schnellen fix.

dennisfisch commented 5 months ago

Dito - alles super und vielen Dank für das Release. Klasse, dass das so schnell gefixed wurde! :D

Oberfranke commented 5 months ago

Bei mir kommt auch mit dem Update 127.1 die Meldung, dass der Server nicht konfiguriert ist

pandamouse84 commented 5 months ago

@Marty56: Restart via the Elli App should fix the problem too ;)

pandamouse84 commented 5 months ago

@Oberfranke: Can you provide a screenshot or log, sound to me like a different problem.