eebus lets evcc crash on docker

[swestland85]

Describe the bug

Trying to get eebus up and running on a evcc running on docker on a synology NAS (DS416play).

When adding eebus to the yaml config I get the following error:

[main ] FATAL 2024/12/03 14:09:12 failed configuring eebus: could not get machineid: open /etc/machine-id: no such file or directory; for manual configuration use plant: caf5c742810cf7bda8e093d2787c9c88b16762700a9b8125ad8807f60bcdcf85

Adding file machine-id file to the file mapping and adding the suggested machine-id, will fix this error message.

Now evcc will start, however the webconfig never becomes accessible and the docker will reboot after 15 minutes going into an infinite loop.

cannot create charger 'my_charger': cannot create charger type 'template': cannot create charger type 'eebus': timeout

eebus times out.

Steps to reproduce

1. add eebus to yaml
2. add plant: for the machine-id
3. add eebus charger

Configuration details

#plant: fd2371f0ba8725a310c23f7e8e708afa77461493ac9b9794ae67f82da7bc4d9f
site:
  - title: Blaricum # display name for UI
    meters:
      grid: my_grid # grid meter reference
    residualPower: 100
tariffs:
  grid:
    type: template
    template: tibber
    token: removed
    homeid: removed
loadpoints:
  - title: Oprit # display name for UI
    charger: my_charger # charger reference
    vehicle: BMW # reference to standard vehicle
    mode: minpv # charge mode (off, now, minpv, pv)    
vehicles:
  - name: BMW
    type: template
    template: bmw
    title: X5
    user: removed # User account (e.g. email address, user id, etc.)
    password: remvoed # Password of the user account (use single quotes in case of leading zeros)
    capacity: 26 # Battery capacity in kWh (optional)
    hcaptcha: [hcaptcha]
meters:
  - name: Enphase
    type: template
    template: enphase
    usage: pv
    host: 192.168.2.213 # IP address or hostname
    token: [token]
eebus:
  shipid: EVB-510-061-355
  certificate:
    public: |
      -----BEGIN CERTIFICATE-----
      MIIBvTCCAWOgAwIBAgIRAcyYJVawVRQ+VsR8DLaj9qkwCgYIKoZIzj0EAwIwPjEL
      MAkGA1UEBhMCREUxDTALBgNVBAoTBEVWQ0MxCTAHBgNVBAsTADEVMBMGA1UEAwwM
      RVZDQ19IRU1TXzAxMB4XDTI0MTIwMzEyMzAwNVoXDTM0MTIwMTEyMzAwNVowPjEL
      MAkGA1UEBhMCREUxDTALBgNVBAoTBEVWQ0MxCTAHBgNVBAsTADEVMBMGA1UEAwwM
      RVZDQ19IRU1TXzAxMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAESOkdLGhclC5J
      FKD6w9oNElBrd2WOHOfUgMbqUS9JyFCXTkCk0yxhQEM9vsW2okyc70sp0NrK0K/F
      Xfv+5Seq0aNCMEAwDgYDVR0PAQH/BAQDAgeAMA8GA1UdEwEB/wQFMAMBAf8wHQYD
      VR0OBBYEFGQd3P1IkhdZr6dF2xQgDGlLTTzNMAoGCCqGSM49BAMCA0gAMEUCIQCU
      POMAl3b/SUPruDNWHAQd+ufzZr3yxw8eqEWHQk8nxAIgBRH/Al5sH0V8qMGI3iAS
      znwH07ONCF5/f2LhRcRCOFA=
      -----END CERTIFICATE-----
    private: |
      -----BEGIN EC PRIVATE KEY-----
      MHcCAQEEIGpNtxIpfMFOHXlR4vDHbgyHZsC3aoKBg+w0lBR/9aS7oAoGCCqGSM49
      AwEHoUQDQgAESOkdLGhclC5JFKD6w9oNElBrd2WOHOfUgMbqUS9JyFCXTkCk0yxh
      QEM9vsW2okyc70sp0NrK0K/FXfv+5Seq0Q==
      -----END EC PRIVATE KEY-----
chargers:
  - name: my_charger
    type: template
    template: eebus
    ski: EVB-510-061-355
    ip: 192.168.2.187 # IP address (optional)

Log details

[main  ] FATAL 2024/12/03 14:09:12 failed configuring eebus: could not get machineid: open /etc/machine-id: no such file or directory; for manual configuration use plant: caf5c742810cf7bda8e093d2787c9c88b16762700a9b8125ad8807f60bcdcf85
[main] cannot create charger 'my_charger': cannot create charger type 'template': cannot create charger type 'eebus': timeout

What type of operating system are you running?

Docker container

Nightly build

• I have verified that the issue is reproducible with the latest nightly build

Version

evcc version 0.131.8

[andig]

There is no crash. Error message says it all.

[swestland85]

There is no crash. Error message says it all.

Well if I add plant: or map machine-id there is no error, it just hangs and keep restarting.

I think my post explains the situation, so the 'question' isnt resolved.

[andig]

Well if I add plant: or map machine-id there is no error, it just hangs and keep restarting.

Do you have a log?

[swestland85]

Well if I add plant: or map machine-id there is no error, it just hangs and keep restarting.

Do you have a log?

Yes:

2024-12-09T09:56:24.296574089Z stdout [main ] INFO 2024/12/09 10:56:24 listening at :7070
2024-12-09T09:56:24.289152171Z stdout [eebus ] INFO 2024/12/09 10:56:24 Local SKI: 641ddcfd48921759afa745db14200c694b4d3ccd
2024-12-09T09:56:23.894180721Z stdout [db ] INFO 2024/12/09 10:56:23 using sqlite database: /root/.evcc/evcc.db
2024-12-09T09:56:23.838477672Z stdout [main ] INFO 2024/12/09 10:56:23 using config file: /etc/evcc.yaml
2024-12-09T09:56:23.830159339Z stdout [main ] INFO 2024/12/09 10:56:23 evcc 0.131.8
[main ] FATAL 2024/12/09 10:57:54 cannot create charger 'my_charger': cannot create charger type 'template': cannot create charger type 'eebus': timeout
[main ] FATAL 2024/12/09 10:57:54 will attempt restart in: 15m0s

That's it, webconfig doesnt come online and it will reboot in 15 minutes.

[andig]

Again, error message says it all.

cannot create charger 'my_charger': cannot create charger type 'template': cannot create charger type 'eebus': timeout

[DerAndereAndi]

ski: EVB-510-061-355 this is not a valid SKI.

[swestland85]

@DerAndereAndi thanks, I thought the EVB number should be the correct one, For my EVBox livo 2?

Now I added to yaml:
log: debug

The following interesting info came back into the log, including the correct ski!

[main  ] INFO 2024/12/09 13:11:48 using config file: /etc/evcc.yaml
[db    ] INFO 2024/12/09 13:11:48 using sqlite database: /root/.evcc/evcc.db
[eebus ] INFO 2024/12/09 13:11:48 Local SKI: 641ddcfd48921759afa745db14200c694b4d3ccd
[eebus ] DEBUG 2024/12/09 13:11:48 starting websocket server on :4712
[eebus ] DEBUG 2024/12/09 13:11:48 mdns: announce
[eebus ] DEBUG 2024/12/09 13:11:48 mdns: using zeroconf
[main  ] INFO 2024/12/09 13:11:48 listening at :7070
[eebus ] DEBUG 2024/12/09 13:11:48 mdns: new - ski: 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 name: Livo-EVB-510-061-355 brand: EVBox model: Livo typ: ChargingStation identifier: EVBox-Livo-EVB-510-061-355 register: false host: EVB-510-061-355.local. port: 4712 addresses: []
[eebus ] DEBUG 2024/12/09 13:11:48 mdns: update - ski: 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 name: Livo-EVB-510-061-355 brand: EVBox model: Livo typ: ChargingStation identifier: EVBox-Livo-EVB-510-061-355 register: false host: EVB-510-061-355.local. port: 4712 addresses: [192.168.2.187]
[eebus ] DEBUG 2024/12/09 13:12:18 mdns: stop announcement

But still eebus timeout and no webconfig coming online. I will try later to see if the Livo can find the HEMS after start evcc initially, before timeout. Maybe this is required.

now also changed shipid: under eebus to the EVBox Livo ski, log now contains the following:

[db    ] INFO 2024/12/09 13:16:45 using sqlite database: /root/.evcc/evcc.db
[eebus ] INFO 2024/12/09 13:16:46 Local SKI: 641ddcfd48921759afa745db14200c694b4d3ccd
[eebus ] DEBUG 2024/12/09 13:16:46 starting websocket server on :4712
[eebus ] DEBUG 2024/12/09 13:16:46 mdns: announce
[eebus ] DEBUG 2024/12/09 13:16:46 mdns: using zeroconf
[main  ] INFO 2024/12/09 13:16:46 listening at :7070
[eebus ] DEBUG 2024/12/09 13:16:46 mdns: new - ski: 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 name: Livo-EVB-510-061-355 brand: EVBox model: Livo typ: ChargingStation identifier: EVBox-Livo-EVB-510-061-355 register: false host: EVB-510-061-355.local. port: 4712 addresses: [192.168.2.187]
[eebus ] DEBUG 2024/12/09 13:16:46 trying to connect to 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 at EVB-510-061-355.local.
[eebus ] DEBUG 2024/12/09 13:16:46 initiating connection to 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 at EVB-510-061-355.local.:4712/ship/
[eebus ] DEBUG 2024/12/09 13:16:46 connection to 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 failed: dial tcp: lookup EVB-510-061-355.local. on 8.8.8.8:53: no such host
[eebus ] DEBUG 2024/12/09 13:16:46 trying to connect to 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 at 192.168.2.187
[eebus ] DEBUG 2024/12/09 13:16:46 initiating connection to 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 at 192.168.2.187:4712/ship/
[eebus ] DEBUG 2024/12/09 13:16:49 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 websocket read error:  websocket: close 4452: Node rejected by application.
[eebus ] DEBUG 2024/12/09 13:16:49 ski 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 disconnected
[eebus ] DEBUG 2024/12/09 13:16:49 mdns: announce
[eebus ] DEBUG 2024/12/09 13:16:49 mdns: using zeroconf
[eebus ] DEBUG 2024/12/09 13:16:49 delaying connection to 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 by 850ms to minimize double connection probability
[eebus ] DEBUG 2024/12/09 13:16:50 trying to connect to 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 at EVB-510-061-355.local.
[eebus ] DEBUG 2024/12/09 13:16:50 initiating connection to 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 at EVB-510-061-355.local.:4712/ship/
[eebus ] DEBUG 2024/12/09 13:16:50 connection to 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 failed: dial tcp: lookup EVB-510-061-355.local. on 8.8.8.8:53: no such host
[eebus ] DEBUG 2024/12/09 13:16:50 trying to connect to 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 at 192.168.2.187
[eebus ] DEBUG 2024/12/09 13:16:50 initiating connection to 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 at 192.168.2.187:4712/ship/
[eebus ] DEBUG 2024/12/09 13:16:53 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 websocket read error:  websocket: close 4452: Node rejected by application.
[eebus ] DEBUG 2024/12/09 13:16:53 ski 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 disconnected

and after 20 retries the node rejected error changes into:

[eebus ] DEBUG 2024/12/09 13:21:47 connection to 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 failed:  remote error: tls: error decrypting message

[DerAndereAndi]

In your EVBox device you also need to allow it to communicate with evcc. Otherwise it will continue to reject all connection attempts.

[swestland85]

Yes I was assuming this, I have no access to the charger now so will try tomorrow with the installer app if it can find the EVCC as HEMS and then allow connectivity.

[swestland85]

I added evcc on the charger as hems, the following error comes up;

[eebus ] DEBUG 2024/12/10 14:38:53 connection to 0910a9eadfd4820e518e2f9b429620a1efe9f8d5 failed: remote error: tls: internal error

I'm not sure how to further debug this error?