text:
Unhealthy container after upgrade

Describe the bug
I try to do weekly updates of EVCC.
Running EVCC in a Docker Stack.
After tonights "docker stack rm EVCC" and "docker stack deploy compose.yml EVCC" I noticed EVCC did not report healthy in my monitoring.
The web interface is down.
Weirdly it seems to be running 2 dockers at the same time?
Steps to reproduce
Remove the docker stack, pull in new images and redeploy.
bart@nas:~$ docker stack ps EVCC --no-trunc
ID                          NAME              IMAGE                                                                                NODE      DESIRED STATE   CURRENT STATE                 ERROR                                                        PORTS
iglmyk6pfi0i6unb77jr7u98o   EVCC_evcc.1       andig/evcc:nightly@sha256:031a0e286f17a1ea11800e0244a0236364eebee63c1b43611920823418017678   nas       Running         Starting about a minute ago
5mujgkufqp8zpfc2w18w2ukvs    \_ EVCC_evcc.1   andig/evcc:nightly@sha256:031a0e286f17a1ea11800e0244a0236364eebee63c1b43611920823418017678   nas       Shutdown        Failed about a minute ago     "task: non-zero exit (1): dockerexec: unhealthy container"
r633cwlo8h46ru67qfpp38xvm    \_ EVCC_evcc.1   andig/evcc:nightly@sha256:031a0e286f17a1ea11800e0244a0236364eebee63c1b43611920823418017678   nas       Shutdown        Failed 4 minutes ago          "task: non-zero exit (1): dockerexec: unhealthy container"
0xjhqsnxo1kaybv2qr2zzfuza    \_ EVCC_evcc.1   andig/evcc:nightly@sha256:031a0e286f17a1ea11800e0244a0236364eebee63c1b43611920823418017678   nas       Shutdown        Failed 7 minutes ago          "task: non-zero exit (1): dockerexec: unhealthy container"
kfbt4svsm2ax6k0ck9g0rjtkh    \_ EVCC_evcc.1   andig/evcc:nightly@sha256:031a0e286f17a1ea11800e0244a0236364eebee63c1b43611920823418017678   nas       Shutdown        Failed 10 minutes ago         "task: non-zero exit (1): dockerexec: unhealthy container"

Configuration details
interval: 10s

site:
- title: qsfqsfqsdfqsdf
  meters:
    grid: HuisMeter
    pvs:
    - pvHuis
    - pvTuinHuis
  residualpower: 100

messaging:
  events:
    start:
      title: Laadbeurt gestart
      msg: Er is een laadbeurt gestart op qsfqsfqsdf
    stop:
      title: Laadbeurt gestopt
      msg: |
        Oplader {{.title}} heeft een laadbeurt voltooid
        Er is {{round (divf .chargedEnergy 1000) 2 }} kWh geleverd op {{.chargeDuration}}.
    connect:
      title: Wagen aangesloten op qsfdsqdqdsf
      msg: Er is een auto aangesloten op de lader in qsfsqfqsdf
    disconnect:
      title: Wagen ontkoppeld op qsdfsqdfsqdf
      msg: De wagen is ontkoppeld van de lader in qsfdqsfqsdf
  services:
    - type: telegram
      token: sqfdqsfqsfd:qsfdqsdfsqdf
      chats:
        - qsfdqsfqsf

tariffs:
  currency: EUR # (default EUR)
  grid:
    # static grid price
    type: fixed
    price: 0.28 # [currency]/kWh

  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.12 # [currency]/kWh

meters:
  - name: HuisMeter
    type: modbus
    model: sdm # specific non-sunspec meter
    id: 1
    energy: Sum # only required for charge meter usage
    #via TCP:
    uri: 192.168.4.184:8899
    rtu: false # serial modbus rtu (rs485) device connected using simple ethernet adapter
  - name: pvHuis
    type: sma
    uri: 192.168.4.230
    password: qsfdqsfqsff
  - name: pvTuinHuis
    type: sma
    uri: 192.168.4.231
    password: qsdfsqfsqf

sponsortoken: qsfdqsfsqf

log: debug
levels:
    core: debug
    cc-main: debug

influx:
  url: http://192.168.4.250:8086
  database: EVCC
  token: "qsdfqsfqsf=="
  org: "qsdfsqfd"

chargers:
- name: ChargingPointAlfen
  type: alfen
  uri: 192.168.4.178 # TCP ModBus address

loadpoints:
- title: Alfen # display name for UI
  charger: ChargingPointAlfen # Wallbox Referenz
  vehicles:
  mode: now # charge mode (off, now, minpv, pv)
  phases: 3
  mincurrent: 12
  maxcurrent: 16

vehicles:

Log details
bart@nas:~$ docker service logs EVCC_evcc
EVCC_evcc.1.ownq8k6ch161@nas    | [main  ] INFO 2022/10/14 23:53:56 evcc 0.104.2 (f787eaac)
EVCC_evcc.1.ownq8k6ch161@nas    | [main  ] INFO 2022/10/14 23:53:56 using config file: /etc/evcc.yaml
EVCC_evcc.1.ownq8k6ch161@nas    | [main  ] INFO 2022/10/14 23:53:56 listening at :7070
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] WARN 2022/10/14 23:53:57 locking phase config to 3p for switchable charger
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] INFO 2022/10/14 23:53:57 site config:
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] INFO 2022/10/14 23:53:57   meters:      grid ✓ pv ✓ battery ✗
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] INFO 2022/10/14 23:53:57     grid:      power ✓ energy ✓ currents ✗
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] INFO 2022/10/14 23:53:57     pv 1:      power ✓ energy ✓ currents ✓
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] INFO 2022/10/14 23:53:57     pv 2:      power ✓ energy ✓ currents ✓
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] INFO 2022/10/14 23:53:57 loadpoint 1:
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] INFO 2022/10/14 23:53:57   mode:        now
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] INFO 2022/10/14 23:53:57   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] INFO 2022/10/14 23:53:57   meters:      charge ✓
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] INFO 2022/10/14 23:53:57     charge:    power ✓ energy ✓ currents ✓
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:57 phase timer inactive
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:57 pv timer inactive
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:53:57 ----
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:57 charge power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:53:57 pv power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:53:57 grid power: 568W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:53:57 site power: 668W
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:57 charge currents: [0 0 0]A
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:57 charger status: A
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:07 ----
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:07 charge power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:07 pv power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:07 grid power: 563W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:07 site power: 663W
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:07 charge currents: [0 0 0]A
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:07 charger status: A
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:17 ----
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:17 charge power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:17 pv power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:17 grid power: 555W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:17 site power: 655W
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:17 charge currents: [0 0 0]A
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:17 charger status: A
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:27 ----
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:27 charge power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:27 pv power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:27 grid power: 554W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:27 site power: 654W
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:27 charge currents: [0 0 0]A
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:27 charger status: A
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:37 ----
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:37 charge power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:37 pv power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:37 grid power: 568W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:37 site power: 668W
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:37 charge currents: [0 0 0]A
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:37 charger status: A
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:47 ----
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:47 charge power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:47 pv power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:47 grid power: 554W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:47 site power: 654W
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:47 charge currents: [0 0 0]A
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:47 charger status: A
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:57 ----
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:57 charge power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:57 pv power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:57 grid power: 555W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:54:57 site power: 655W
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:57 charge currents: [0 0 0]A
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:54:57 charger status: A
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:55:07 ----
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:55:07 charge power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:55:07 pv power: 0W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:55:07 grid power: 558W
EVCC_evcc.1.ownq8k6ch161@nas    | [site  ] DEBUG 2022/10/14 23:55:07 site power: 658W
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:55:07 charge currents: [0 0 0]A
EVCC_evcc.1.ownq8k6ch161@nas    | [lp-1  ] DEBUG 2022/10/14 23:55:07 charger status: A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [main  ] INFO 2022/10/14 23:50:47 evcc 0.104.2 (f787eaac)
EVCC_evcc.1.iglmyk6pfi0i@nas    | [main  ] INFO 2022/10/14 23:50:47 using config file: /etc/evcc.yaml
EVCC_evcc.1.iglmyk6pfi0i@nas    | [main  ] INFO 2022/10/14 23:50:47 listening at :7070
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] WARN 2022/10/14 23:50:48 locking phase config to 3p for switchable charger
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] INFO 2022/10/14 23:50:48 site config:
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] INFO 2022/10/14 23:50:48   meters:      grid ✓ pv ✓ battery ✗
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] INFO 2022/10/14 23:50:48     grid:      power ✓ energy ✓ currents ✗
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] INFO 2022/10/14 23:50:48     pv 1:      power ✓ energy ✓ currents ✓
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] INFO 2022/10/14 23:50:48     pv 2:      power ✓ energy ✓ currents ✓
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] INFO 2022/10/14 23:50:48 loadpoint 1:
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] INFO 2022/10/14 23:50:48   mode:        now
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] INFO 2022/10/14 23:50:48   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] INFO 2022/10/14 23:50:48   meters:      charge ✓
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] INFO 2022/10/14 23:50:48     charge:    power ✓ energy ✓ currents ✓
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:48 phase timer inactive
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:48 pv timer inactive
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:50:48 ----
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:48 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:50:48 pv power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:50:48 grid power: 551W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:50:49 site power: 651W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:49 charge currents: [0 0 0]A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:49 charger status: A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:50:58 ----
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:58 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:50:58 pv power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:50:58 grid power: 555W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:50:59 site power: 655W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:59 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [main  ] INFO 2022/10/14 23:41:21 evcc 0.104.2 (f787eaac)
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:59 charger status: A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:08 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [main  ] INFO 2022/10/14 23:41:21 using config file: /etc/evcc.yaml
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:08 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [main  ] INFO 2022/10/14 23:41:21 listening at :7070
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:08 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] WARN 2022/10/14 23:41:22 locking phase config to 3p for switchable charger
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:08 grid power: 557W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:09 site power: 657W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:09 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] INFO 2022/10/14 23:41:22 site config:
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:09 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] INFO 2022/10/14 23:41:22   meters:      grid ✓ pv ✓ battery ✗
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:18 ----
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:18 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:18 pv power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:18 grid power: 553W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] INFO 2022/10/14 23:41:22     grid:      power ✓ energy ✓ currents ✗
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:19 site power: 653W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] INFO 2022/10/14 23:41:22     pv 1:      power ✓ energy ✓ currents ✓
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] INFO 2022/10/14 23:41:22     pv 2:      power ✓ energy ✓ currents ✓
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:19 charge currents: [0 0 0]A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:19 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] INFO 2022/10/14 23:41:22 loadpoint 1:
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:28 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] INFO 2022/10/14 23:41:22   mode:        now
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:28 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] INFO 2022/10/14 23:41:22   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:28 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] INFO 2022/10/14 23:41:22   meters:      charge ✓
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:28 grid power: 555W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] INFO 2022/10/14 23:41:22     charge:    power ✓ energy ✓ currents ✓
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:29 site power: 655W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:41:22 phase timer inactive
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:29 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:41:22 pv timer inactive
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:29 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:22 ----
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:38 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:41:22 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:38 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:22 pv power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:38 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:23 grid power: 601W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:23 site power: 701W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:38 grid power: 551W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:39 site power: 651W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:41:23 charge currents: [0 0 0]A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:39 charge currents: [0 0 0]A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:39 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:41:23 charger status: A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:48 ----
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:48 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:32 ----
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:48 pv power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:48 grid power: 549W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:41:32 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [main  ] INFO 2022/10/14 23:44:30 evcc 0.104.2 (f787eaac)
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:49 site power: 649W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:32 pv power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:49 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [main  ] INFO 2022/10/14 23:44:30 using config file: /etc/evcc.yaml
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:33 grid power: 600W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:49 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [main  ] INFO 2022/10/14 23:44:30 listening at :7070
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:33 site power: 700W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:58 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:41:33 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] WARN 2022/10/14 23:44:31 locking phase config to 3p for switchable charger
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:58 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:41:33 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] INFO 2022/10/14 23:44:31 site config:
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:58 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] INFO 2022/10/14 23:44:31   meters:      grid ✓ pv ✓ battery ✗
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:58 grid power: 548W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:42 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] INFO 2022/10/14 23:44:31     grid:      power ✓ energy ✓ currents ✗
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:41:42 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:51:59 site power: 648W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] INFO 2022/10/14 23:44:31     pv 1:      power ✓ energy ✓ currents ✓
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:59 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] INFO 2022/10/14 23:44:31     pv 2:      power ✓ energy ✓ currents ✓
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:51:59 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:42 pv power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:08 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:43 grid power: 614W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] INFO 2022/10/14 23:44:31 loadpoint 1:
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:08 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] INFO 2022/10/14 23:44:31   mode:        now
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:08 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:43 site power: 714W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] INFO 2022/10/14 23:44:31   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:41:43 charge currents: [0 0 0]A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:08 grid power: 553W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] INFO 2022/10/14 23:44:31   meters:      charge ✓
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:09 site power: 653W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:09 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] INFO 2022/10/14 23:44:31     charge:    power ✓ energy ✓ currents ✓
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:09 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:41:43 charger status: A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:18 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:52 ----
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:18 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:41:52 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:31 phase timer inactive
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:18 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:52 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:31 pv timer inactive
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:18 grid power: 551W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:53 grid power: 618W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:44:31 ----
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:19 site power: 651W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:41:53 site power: 718W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:31 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:19 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:41:53 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:44:31 pv power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:19 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:41:53 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:44:31 grid power: 609W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:28 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:44:31 site power: 709W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:28 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:02 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:31 charge currents: [0 0 0]A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:28 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:31 charger status: A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:28 grid power: 546W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:02 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:44:41 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:02 pv power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:29 site power: 646W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:03 grid power: 625W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:41 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:29 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:44:41 pv power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:29 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:03 site power: 725W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:44:41 grid power: 598W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:38 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:03 charge currents: [0 0 0]A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:38 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:03 charger status: A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:38 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:44:41 site power: 698W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:12 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:41 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:12 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:42 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:12 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:44:51 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:13 grid power: 615W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:51 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:38 grid power: 545W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:13 site power: 715W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:39 site power: 645W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:39 charge currents: [0 0 0]A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:39 charger status: A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:48 ----
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:48 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:48 pv power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:48 grid power: 548W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:49 site power: 648W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:49 charge currents: [0 0 0]A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:49 charger status: A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:58 ----
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:58 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:58 pv power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:58 grid power: 558W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:52:59 site power: 658W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:59 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [main  ] INFO 2022/10/14 23:47:39 evcc 0.104.2 (f787eaac)
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:52:59 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [main  ] INFO 2022/10/14 23:47:39 using config file: /etc/evcc.yaml
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:08 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [main  ] INFO 2022/10/14 23:47:39 listening at :7070
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:08 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:08 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] WARN 2022/10/14 23:47:39 locking phase config to 3p for switchable charger
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] INFO 2022/10/14 23:47:39 site config:
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:08 grid power: 546W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] INFO 2022/10/14 23:47:39   meters:      grid ✓ pv ✓ battery ✗
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:09 site power: 646W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:09 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] INFO 2022/10/14 23:47:39     grid:      power ✓ energy ✓ currents ✗
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] INFO 2022/10/14 23:47:39     pv 1:      power ✓ energy ✓ currents ✓
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:09 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] INFO 2022/10/14 23:47:39     pv 2:      power ✓ energy ✓ currents ✓
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:18 ----
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:18 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] INFO 2022/10/14 23:47:39 loadpoint 1:
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:18 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] INFO 2022/10/14 23:47:39   mode:        now
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:18 grid power: 550W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:19 site power: 650W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] INFO 2022/10/14 23:47:39   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] INFO 2022/10/14 23:47:39   meters:      charge ✓
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:19 charge currents: [0 0 0]A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:19 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] INFO 2022/10/14 23:47:39     charge:    power ✓ energy ✓ currents ✓
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:28 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:39 phase timer inactive
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:28 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:28 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:39 pv timer inactive
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:28 grid power: 562W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:47:39 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:40 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:29 site power: 662W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:47:40 pv power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:29 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:47:40 grid power: 587W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:29 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:47:40 site power: 687W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:38 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:40 charge currents: [0 0 0]A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:38 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:40 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:47:49 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:50 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:38 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:47:50 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:47:50 grid power: 611W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:38 grid power: 549W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:39 site power: 649W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:47:50 site power: 711W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:39 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:50 charge currents: [0 0 0]A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:39 charger status: A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:48 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:50 charger status: A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:48 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:48 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:47:59 ----
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:48 grid power: 563W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:00 charge power: 0W
EVCC_evcc.1.iglmyk6pfi0i@nas    | [site  ] DEBUG 2022/10/14 23:53:49 site power: 663W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:00 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:00 grid power: 557W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:00 site power: 657W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:00 charge currents: [0 0 0]A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:49 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:00 charger status: A
EVCC_evcc.1.iglmyk6pfi0i@nas    | [lp-1  ] DEBUG 2022/10/14 23:53:49 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:09 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:10 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:13 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:13 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:10 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:22 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:44:51 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:22 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:44:51 grid power: 602W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:22 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:44:51 site power: 702W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:23 grid power: 599W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:51 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:23 site power: 699W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:51 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:23 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:01 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:01 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:01 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:01 grid power: 631W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:01 site power: 731W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:01 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:02 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:23 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:11 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:11 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:11 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:32 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:32 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:11 grid power: 626W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:32 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:11 site power: 726W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:33 grid power: 601W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:11 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:33 site power: 701W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:11 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:33 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:21 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:21 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:21 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:21 grid power: 604W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:21 site power: 704W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:21 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:33 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:21 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:31 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:42 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:10 grid power: 576W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:31 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:10 site power: 676W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:31 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:42 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:31 grid power: 604W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:10 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:42 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:31 site power: 704W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:43 grid power: 606W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:31 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:31 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:43 site power: 706W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:41 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:43 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:41 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:43 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:41 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:52 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:41 grid power: 585W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:41 site power: 685W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:41 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:52 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:41 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:52 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:51 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:53 grid power: 600W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:42:53 site power: 700W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:51 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:10 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:19 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:53 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:20 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:42:53 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:02 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:20 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:02 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:20 grid power: 565W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:20 site power: 665W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:02 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:03 grid power: 598W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:20 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:03 site power: 698W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:20 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:29 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:51 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:30 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:51 grid power: 589W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:30 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:45:51 site power: 689W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:30 grid power: 559W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:30 site power: 659W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:30 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:30 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:51 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:45:51 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:39 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:01 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:40 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:40 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:03 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:01 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:03 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:01 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:40 grid power: 556W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:12 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:01 grid power: 563W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:40 site power: 656W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:40 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:01 site power: 663W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:40 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:01 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:12 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:49 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:12 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:50 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:13 grid power: 601W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:01 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:50 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:13 site power: 701W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:13 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:11 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:13 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:50 grid power: 566W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:11 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:11 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:22 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:50 site power: 666W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:11 grid power: 577W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:22 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:11 site power: 677W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:50 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:48:50 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:11 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:22 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:23 grid power: 599W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:48:59 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:23 site power: 699W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:00 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:00 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:11 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:00 grid power: 578W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:21 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:21 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:00 site power: 678W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:21 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:00 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:00 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:21 grid power: 568W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:09 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:21 site power: 668W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:10 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:10 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:21 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:21 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:31 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:10 grid power: 564W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:23 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:10 site power: 664W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:31 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:23 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:10 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:32 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:31 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:10 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:31 grid power: 584W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:32 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:19 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:31 site power: 684W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:32 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:20 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:31 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:31 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:20 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:33 grid power: 617W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:20 grid power: 564W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:41 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:20 site power: 664W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:33 site power: 717W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:33 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:20 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:33 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:20 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:29 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:42 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:42 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:30 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:42 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:30 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:30 grid power: 572W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:43 grid power: 603W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:43 site power: 703W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:43 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:30 site power: 672W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:43 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:30 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:52 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:30 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:52 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:39 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:40 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:41 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:40 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:52 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:40 grid power: 565W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:41 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:40 site power: 665W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:53 grid power: 598W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:43:53 site power: 698W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:41 grid power: 580W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:53 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:41 site power: 680W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:43:53 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:41 charge currents: [0 0 0]A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:44:02 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:41 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:02 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:51 ----
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:44:02 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:51 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:44:03 grid power: 604W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:40 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:51 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:44:03 site power: 704W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:40 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:51 grid power: 567W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:03 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:49 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:46:51 site power: 667W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:03 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:51 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:50 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:44:12 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:46:51 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:12 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:50 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:01 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:50 grid power: 571W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:01 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:50 site power: 671W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:50 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:01 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:49:50 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:01 grid power: 560W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:01 site power: 660W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:49:59 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:00 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:01 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:00 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:01 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:00 grid power: 553W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:00 site power: 653W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:00 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:00 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:09 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:10 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:10 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:44:12 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:10 grid power: 554W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:44:13 grid power: 598W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:10 site power: 654W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:44:13 site power: 698W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:10 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:10 charger status: A
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:13 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:19 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:20 charge power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:13 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:20 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:44:22 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:20 grid power: 562W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:22 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:20 site power: 662W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:44:22 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:44:23 grid power: 598W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [site  ] DEBUG 2022/10/14 23:44:23 site power: 698W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:20 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:11 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:20 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:29 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:30 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:11 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:30 pv power: 0W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:23 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:11 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:30 grid power: 561W
EVCC_evcc.1.0xjhqsnxo1ka@nas    | [lp-1  ] DEBUG 2022/10/14 23:44:23 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:11 grid power: 561W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:30 site power: 661W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:30 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:11 site power: 661W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:11 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:30 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:11 charger status: A
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:39 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:40 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:21 ----
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:40 pv power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:40 grid power: 550W
EVCC_evcc.1.5mujgkufqp8z@nas    | [site  ] DEBUG 2022/10/14 23:50:40 site power: 650W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:21 charge power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:21 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:21 grid power: 562W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:21 site power: 662W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:21 charge currents: [0 0 0]A
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:40 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:21 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:31 ----
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:31 charge power: 0W
EVCC_evcc.1.5mujgkufqp8z@nas    | [lp-1  ] DEBUG 2022/10/14 23:50:40 charger status: A
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:31 pv power: 0W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:31 grid power: 570W
EVCC_evcc.1.r633cwlo8h46@nas    | [site  ] DEBUG 2022/10/14 23:47:31 site power: 670W
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:31 charge currents: [0 0 0]A
EVCC_evcc.1.r633cwlo8h46@nas    | [lp-1  ] DEBUG 2022/10/14 23:47:31 charger status: A

Tried to remove the stack and redeploy:
bart@nas:~$ docker stack rm EVCC
bart@nas:~$ docker stack deploy -c /EVO500/AppsConfig/dockercomposefiles/docker-EVCC/docker-compose.yml EVCC
bart@nas:~$ docker stack ps EVCC --no-trunc
ID                          NAME          IMAGE                                                                                NODE      DESIRED STATE   CURRENT STATE                 ERROR     PORTS
7d4hak78hlf4u3dv1g77mjbzc   EVCC_evcc.1   andig/evcc:nightly@sha256:031a0e286f17a1ea11800e0244a0236364eebee63c1b43611920823418017678   nas       Running         Starting about a minute ago

Weirdly enough it says it is still running 104.2 ?
bart@nas:~$ docker logs EVCC_evcc.1.7d4hak78hlf4u3dv1g77mjbzc
[main  ] INFO 2022/10/15 00:02:13 evcc 0.104.2 (f787eaac)
[main  ] INFO 2022/10/15 00:02:13 using config file: /etc/evcc.yaml
[main  ] INFO 2022/10/15 00:02:13 listening at :7070

What type of operating system are you running?
Linux
Version
Linux nas 5.15.0-50-generic #56-Ubuntu SMP Tue Sep 20 13:23:26 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.1 LTS
Release:        22.04
Codename:       jammy

Although the container in some way seems to be up it is not listening on 7070 anymore:
bart@nas:~$ sudo lsof -i -P -n | grep LISTEN | grep 7070
bart@nas:~$

Images are up to date:
bart@nas:~$ docker image ls | grep andi
andig/evcc                          latest    009715c90545   8 hours ago     53.1MB
andig/evcc                          <none>    c5826aa62924   18 hours ago    53.1MB
andig/evcc                          <none>    063f8a351aac   2 weeks ago     49.7MB

Hab das gleiche Problem.
Nach dem Upgrade auf 0.105.1 wird mir der Container als unhealthy angezeigt.
Der native Webzugang funktioniert jedoch, allerdings über Traefik  nicht mehr, was am unhealthy  liegen könnte.
Das Evcc Log sieht unspektakulär aus.
Mein Docker läuft auf einer Synology DS916+ mit x86_64 SOC.
lg
Rubinho

--Update--
Das Problem ist auch in der aktuellen Nightly und in der 0.105.0 vorhanden. Ein Downgrade auf 0.104.2 behebt das Problem.
@hyperbart  The reason why your webinterface is not working could be Traefik (Do you have Traefik in use?) Traefik does a healthcheck and if it is negative, no proxy will be established.

Was genau tut denn der "Healthcheck" technisch?

I don’t have a Traefik running but I do have Cloudflare tunnel. But that does normally nog intervene with other containers. EVCC is only attached to an extra network where the cloudlared container also resides so it can tunnel traffic outwards.
i will try later today what happens if I take away the network, then it should run standalone.
@premultiply : no idea about the healthcheck.

@premultiply Ich kann dir das auch nicht wirklich sagen. Manche Images haben einen, manche nicht. Ich glaube @andig muss ihn bewusst eingebaut haben, oder hat sich einem Basisimage bedient, der ein Healthcheck integriert hat. Was der genau prüft, ist mir noch nicht klar. Im Container-Log sehe ich zumindest nichts.

Was gibt denn http://evcc.local:7070/api/health (bzw. mit der IP) zurück im Browser?

Das hier...
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
Keine Ahnung, ob das der Fehler ist oder der Healthcheck kaputt ist.

Kommando zurück.
Wenn ich im Browser auf Rohdaten klicke, steht da "ok"

Das hier spuckt mir Docker inspect aus...
Output [main ] INFO 2022/10/15 08:56:56 evcc 0.105.1 [main ] ERROR 2022/10/15 08:56:56 health check failed

@premultiply : URL gives nothing because the port is not yet open.
@andig : I just deployed but it still exits with the following error. See below
bart@nas:~$ docker stack ps EVCC --no-trunc
ID                          NAME              IMAGE                                                                                NODE      DESIRED STATE   CURRENT STATE                 ERROR                                                        PORTS
4z4qjj2bp8zp4xh0azkaho4zz   EVCC_evcc.1       andig/evcc:nightly@sha256:eb229e21cfbf01f361d71cff98d43583cbf604e29db26cd6258df6d3acd5bfd8   nas       Running         Starting about a minute ago
rjheacxcjlf61ut55dju6ze55    \_ EVCC_evcc.1   andig/evcc:nightly@sha256:eb229e21cfbf01f361d71cff98d43583cbf604e29db26cd6258df6d3acd5bfd8   nas       Shutdown        Failed about a minute ago     "task: non-zero exit (1): dockerexec: unhealthy container"

@hyperbart
It probably doesn't help you, but for me the new version 0.105.2 works again. Did you delete the old image?

@rubinho76
By switching from nightly to latest it appears to be working again. Took some time to start the container apparently. (around a minute or so).
I'll check if switching to nightly works too.

Nightly still has the issue (I am not a developer, so don't know if that is to be expected). I once switched to nightly's to be able to enjoy the new GUI by @premultiply  👍 .
Switched back to latest and exactly after a minute the container comes up.

@hyperbart
At the moment the "latest" is the newest version. The nightly is 6 hours old and still has the bug
If you are happy with the stable versions, leave it on latest.

authors: hyperbart premultiply rubinho76


text:
Remove TODO

We have done all of the items on this list, and I think we should be
using issues for this type of thing anyway.

Coverage remained the same at 98.182% when pulling 1359c544178b48a6c679720811d0664c35e32a52 on lencioni:remove-todo into 4fabf9146ac8914b162df4d91ef512b378cbe5e6 on evcohen:master.

Can you rebase? Will merge right after 😄

Rebased!

source: gharchive/pull-request

authors: coveralls evcohen lencioni

license: mit

license_type: permissive

license_source: bigquery


text:
Allow aria- props to be null/undefined

Currently, the aria-proptypes rule has the odd property that it won't allow aria- props to be reset by setting them to null or undefined. For example, these are invalid:
<Heading aria-level={null} />
<Heading aria-level={undefined} />

I'm guessing that this behavior is unintended. There's currently a check for value === null, where value comes from getPropLiteralValue(); but that doesn't work for null itself, because getPropLiteralValue() returns the string "null" in that case.

@TrevorBurnham thank you!

authors: TrevorBurnham jessebeach


text:
🛑 /getHashtagFeedByID - Get hashtag feed by ID is down

In 962398d, /getHashtagFeedByID - Get hashtag feed by ID (https://tiktok.evelode.com/getHashtagFeedByID?id=13100&cache_timeout=0&license_key=$API_KEY) was down:

HTTP code: 0
Response time: 0 ms

Resolved: /getHashtagFeedByID - Get hashtag feed by ID is back up in d819814 after 23 minutes.

source: gharchive/issue

repo: evelode/tiktok-status

license: MIT

license_source: github-api


text:
chore(build): Add new encrypted key.

It's hard to decrypt a key when it's empty.  This fixes that.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: dtardoin-eb ebtravis

repo: eventbrite/eventbrite-sdk-javascript


text:
Data completion function results in duplicates

When a dataset with missing rows is passed to a line or area chart, it results in duplication of rows in the tooltip of the chart. This seems to be caused by the getCompletedData function.
This may happen with other chart types as well.
This issue needs reproducing and more information, but flagging so it’s on the issues list.

@hughess could you give some clarification as to how getCompletedData is supposed to work? Is it just adding missing columns in rows?

@csjh for sure.
There are 2 purposes:

Fill in missing rows in a multi-series dataset so ECharts displays the results correctly
Allows for the handleMissing option so user can choose how nulls or missing values should be displayed (e.g., should there be gaps, or should the line interpolate?)

ECharts handles missing values inconsistently across chart types and situations, so getCompletedData attempts to return a full dataset that will make the results consistent every time.
In example-project, the Chart Testing folder has pages dedicated to these situations. It might be easiest to look at those and turn off the function to see what the difference is.
I have a bunch more info about the individual situations it solves for if that would be helpful. A couple simple examples below.
There might be a better way to implement the handling of missing values in general, though I believe that would involve a rethinking of how we pass data to the ECharts component.
Example Situations
Example 1 - "missing X"

You have dataset of revenue for 2 countries (Canada and US) from 2010 to 2019
There is no year 2005 in the dataset
Depending on the chart type, the x-axis might not show 2005 (i.e. it would skip straight from 2004 to 2006 without additional space in between)
What we want here is to show 2005 on the axis with no data

Example 2 - "missing Y"

You have dataset of revenue for 2 countries (Canada and US) from 2010 to 2019
The US is missing 2006, so only has 9 rows vs. Canada's 10
Depending on the chart type, the US data can get shifted off the correct x-axis values if it's not filled in

authors: csjh hughess

repo: evidence-dev/evidence


text:
How do i send to all client?

Thank you very much for your code.
How do i send to all client?

Sorry, I saw it, thank you again for sharing，nice man，i like you.

2.3 After the update, we can finally send packages with json

Hello,
i have the same issue.
All my client is connected to the server but their reveive only the package what they send.
How did you fix it ?
Thx.

@Ookami-Git call c.broadcastAll()

Hi,
Thank you for the quick reply !
Where i call this ?
in handlepacket.js ?
For example if i want send this everywhere :
    case 'hello':
        console.log("Hello from client: "+data.kappa);
        c.sendHello();
        break;

Where i need to add c.boradcastAll() ?

You're welcome :p

authors: Droog159 Ookami-Git evolutionleo

repo: evolutionleo/GM-Online-Framework


text:
Add blake2 precompile

Part of #20.

This should be implemented to follow https://github.com/ethereum/EIPs/issues/152.

Merging this. Keep the issue open so that it will be changed to reflect the EIP.

repo: ewasm/ewasm-precompiles


text:
Console application

This is a simple console application that shows how to get started using the SDK.

Kindly also add the referenced dlls in the bin folder of Console application.

authors: asimnazir shtrip

repo: exactonline/ClientSDK


text:
Inquiry: Fast method for classifying faces in a group of photos

I hope this message finds you well.
I have a question regarding the capabilities of CompreFace and I would appreciate your assistance. I am currently looking for a fast method to classify faces in a group of photos, where similar faces are labeled with the same tag. The tags can be initially random and can be modified later. I have already utilized the CompreFace DetectionFace method to extract thumbnails and embedding datasets for each face in the photos.
Now, I am wondering how I can proceed to classify these photos. I would like to group the photos based on the similarity of the faces. For example, if there are 20 photos in a group and each photo contains 1-3 faces, there are approximately 5 unique faces among the 20 photos. Therefore, I aim to separate the 20 photos into 5 groups.
Could you please let me know if it is possible to achieve this using the existing CompreFace REST API? Your support and guidance in this matter would be greatly appreciated.
Thank you very much.

I described it here:
https://github.com/exadel-inc/CompreFace/discussions/1049

authors: neozhu pospielov

repo: exadel-inc/CompreFace


text:
not checking the value of R0 when loading existing precomputation matrix

The current naming convention of the matrix file does not have R0 (bounding box) information. It won't complain when loading an existing matrix file computed with a different R0.

R0 has a real_t type, it is better to be stored in matrix file rather than be passed in the file name. Now matrix binary file starts with R0, then followed by the precomputation matrices.

repo: exafmm/exafmm-t


text:
error: during the realization of XXX(self: XXX)

I have run the following python program program5.py by codon.
class T12Hb789 ():
BR280BRF = 90
def D2z16jwnb8 ( self )  :
for wX4214N8 in range ( 1 , 10 , 1 ) :
self.BR280BRF+=self.BR280BRF
if name == 'main':
UZ6M31H= T12Hb789();
UZ6M31H.D2z16jwnb8()
print(UZ6M31H.BR280BRF)
And it output error message as follow:
codon_program5.py:5:5-9: error: 'T12Hb789' object has no attribute 'BR280BRF'
codon_program5.py:8:2-22: error: during the realization of D2z16jwnb8(self: T12Hb789)
I hava run it by both python3 and pypy3 and output the following content:
46080
The related files can be found in https://github.com/starbugs-qurong/python-compiler-test/tree/main/codon/python_5

@starbugs-qurong Same as in #320
class T12Hb789:
    BR280BRF: int = 90  # type int

Thank you. Same as #320, it can be compiled and executed in the right way after declaring the types of class members.

authors: elisbyberi starbugs-qurong

repo: exaloop/codon


text:
Refactor Secrets class

def get_value_as_attribute(self, key):
    val = self.get(key)
    if val is None:
        raise AttributeError(f'{key} value is not defined')
    return val

Secrets.__getattr__ = get_value_as_attribute

Credits to @ahsimb

repo: exasol/notebook-connector


text:
Password is exposed in EXPLAIN VIRTUAL for EXA connections

If a connection is used in a Virtual Schema that stores username and password, this information should not be exposed in the resulting pushdown SQL. This works fine for JDBC connections, but not for the special EXA connection:
CREATE CONNECTION sys_connection TO 'jdbc:exa:localhost:42627' USER 'SYS' IDENTIFIED BY 'exasol';
CREATE VIRTUAL SCHEMA vs USING adapter.jdbc_adapter
WITH connection_name = 'SYS_CONNECTION'
sql_dialect='EXASOL' schema_name = 'LS'
import_from_exa='TRUE' exa_connection_string='localhost:42627';

Execution of explain virtual select x from vs.t; returns the pushdown:
IMPORT FROM EXA AT 'localhost:42627' USER 'SYS' IDENTIFIED BY 'exasol' STATEMENT 'SELECT * FROM "LS"."T"'
The question is why do we need a special exa_connection_string? If this is redundant we can just use the information from the provided connection. However this would be changed behavior.

Closed with #95

authors: AnastasiiaSergienko snehlsen

repo: exasol/virtual-schemas


text:
Add background to the text block

I hope to have the function that can add background to the text block, so that it is no longer a transparent bottom, which is convenient to overlay on linear tools such as arrows.

@s-charvin
Hi,
Is this something like https://sharp-curie-5a59d5.netlify.app/ you want?

I don't know if there is a problem with my network here. After opening the link you sent, I saw a blank Excalidraw page, but it has three more functions than the official website: Grab, Eraser, Stickynote. Is this the Stickynote feature you want me to see? If so, I don't think this is what I want. Specifically, you can take a look at the example shown in the following link or picture.
Example

Check text feature only. Sticky note is not proper.
I have added a background option for text.
On Sat, Mar 12, 2022 at 11:38 AM hello @.***> wrote:

I don't know if there is a problem with my network here. After opening the
link you sent, I saw a blank Excalidraw page, but it has three more
functions than the official website https://excalidraw.com/: Grab,
Eraser, Stickynote. Is this the Stickynote feature you want me to see? If
so, I don't think this is what I want. Specifically, you can take a look at
the example shown in the following link or picture.
Example
https://excalidraw.com/#room=91a4e9d9a1b4a5655549,24ERzloGDjQXXG_42S9UHw
[image: image]
https://user-images.githubusercontent.com/38879886/158006249-db8f0781-8889-4eeb-b35e-17f7ec288a5a.png
—
Reply to this email directly, view it on GitHub
https://github.com/excalidraw/excalidraw/issues/4909#issuecomment-1065823544,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASYUWOOHRPJBVANE2WXOXBDU7QYFVANCNFSM5QRKCR7Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

thanks for your help!
I looked again and found it, but the background doesn't look quite symmetrical. Is this function only available through the link you sent? If so, I'll save this link for future use.

仅检查文本功能。便笺不合适。我为文本添加了一个背景选项。
…
On Sat, Mar 12, 2022 at 11:38 AM hello @.> wrote: I don't know if there is a problem with my network here. After opening the link you sent, I saw a blank Excalidraw page, but it has three more functions than the official website https://excalidraw.com/: Grab, Eraser, Stickynote. Is this the Stickynote feature you want me to see? If so, I don't think this is what I want. Specifically, you can take a look at the example shown in the following link or picture. Example https://excalidraw.com/#room=91a4e9d9a1b4a5655549,24ERzloGDjQXXG_42S9UHw [image: image] https://user-images.githubusercontent.com/38879886/158006249-db8f0781-8889-4eeb-b35e-17f7ec288a5a.png — Reply to this email directly, view it on GitHub <#4909 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASYUWOOHRPJBVANE2WXOXBDU7QYFVANCNFSM5QRKCR7Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you commented.Message ID: @.>

Duplicate of https://github.com/excalidraw/excalidraw/issues/4323. But I dont get why this is closed, as I am unable to make text with a background in the excalidraw app.

authors: KronosTheLate abhaymahajanwh s-charvin

repo: excalidraw/excalidraw


text:
Add IDs to elements

#235

I don't think date.getTime() is good candidate for generating ids. It has low resolution: two elements can be created at the same time.
Incremental ids are also bad, as it would be a little bit tricky to restore elements.
Maybe it's better to use something like https://github.com/ai/nanoid

I just added nanoid support. Initially I didn't want to use a library because it would add to the bundle size but this is very small :) Thank you for this library!

What’s the use case for ids? We haven’t needed them so far.

I started playing with the idea of separating selected elements from all elements and in terms of development and UI, everything seemed to be working fine. However, there was one nuance where there was a need to find elements from UI into the scene. Because everything is mutable, comparing objects works but I do not think that it is a good alternative because objects can change etc.
For example, during my experiment, in order to find if the hit element is selected, I was doing something like this:
if (this.state.selectedElements.find(sel => sel.id === hitElement.id)) {
  ...
}

Using IDs just made it feel safer than using something like:
// checking reference can be problematic if the element object is going to be replaced instead of mutated
if (this.state.selectedElements.find(sel => sel === hitElement)) {
  ...
}

I see. In this context that makes sense.

authors: GasimGasimzada nanot1m vjeux


text:
Fix middle handles on mobile

For rendering we always use mouse in order to check which handles to display but when doing the hit test, we used pointer which has a different size. So we couldn't use the middle handles for small shapes. This is now fixed.
cc @j-f1 as you added it in #790

Oops, thanks for spotting this! That was definitely not something I considered when laying out the handles.


text:
feat: Changeable grid size [WIP]

Fixes #2110
Experimental
When I create a document with a specific grid size I would like this information to stay with the document, even if the the grid is not on at the time of the save. Currently the information is stored in the file as null when the grid is off.
Changes

[x] Add showGrid to AppState
[x] gridSize cannot be null anymore
[ ] Backwards compatibility (make sure the null cases to get the default value)
[ ] UI to change the grid size
[ ] Collaboration mode (sync the gridSize but not the showGrid)

Ideas are welcome for the UI if we are going to have that changeable.
Test it

Go to preview
Enable grid
Show Stats for nerds
Click on the grid size to change it (currently just increases it by 5)

Alternative solution
If we decide that it's not that important to change the grid size let's remove the gridSize from the state and use only the GRID_SIZE: example PR.

This is really good! Makes it much nicer to mock layouts accurately. Definite thumbs up for adding this.

closing in favor of https://github.com/excalidraw/excalidraw/pull/8364 (not gridSize, but gridStep, though)

authors: Coffeeling dwelle lipis


text:
Configuration Feedback

In the latest JavaScript rewrite (workspace branch). We've been talking about how we can simplify configuration in general. Here is a breakdown of that feedback which would cause some code to be deleted 👍🏻 .
Constructor
On a platform like java I think we would know a lot of the defaults that wouldn't change often in terms of services and configuration.  Seems like we could default all the items of the Configuration Manager and have a simple empty constructor. The ExceptionlessClient could have a startup method where we pass a Function/Predicate that contains a new configuration object and a user could set any properties on that. Thoughts?
Combine Configuration and Configuration Manager?
Is there any reason we shouldn't combine these and move services into an aggregate root property?
Simplifying of services.
The module collector, request info collector environment collector and error parser probably will never change in most implementations so it doesn't make sense defining services or interfaces for them. If we simply do the work in the plugin we can simplify services configuration all together. We also moved these into a services property to clean up configuration.
Configuration endpoint
We try to load the configuration settings via submission client from a preconfigured config subdomain https://config.exceptionless.io. I noticed this was missing.
Server url
Setting the server url should override the config and heartbeat server urls as well (So if you are self hosting it will set all the servers to the same).

Constructor
On a platform like java I think we would know a lot of the defaults that wouldn't change often in terms of services and configuration. Seems like we could default all the items of the Configuration Manager and have a simple empty constructor. The ExceptionlessClient could have a startup method where we pass a Function/Predicate that contains a new configuration object and a user could set any properties on that. Thoughts?

If you see here: https://github.com/exceptionless/Exceptionless.Java/blob/2a9d5e09af22c0c2f86e7d1a29087a8242377efc/src/main/java/com/exceptionless/exceptionlessclient/configuration/ConfigurationManager.java#L55
I am utilizing the builder pattern. So ideally I don't want someone to initialize the ConfigurationManager using new. Because then he/she needs to pass all the values with lots of nulls I guess.
ConfigurationManager.builder().submissionClient(xxx).build();

So here it would be like calling the all argument constructor with all nulls but with xxx as the value for submission client. So if someone wants to customize the configuration manager he/she can do with this builder and pass it here:
https://github.com/exceptionless/Exceptionless.Java/blob/2a9d5e09af22c0c2f86e7d1a29087a8242377efc/src/main/java/com/exceptionless/exceptionlessclient/ExceptionlessClient.java#L38
So like above, all the classes are following a builder pattern so the client should be built in this way:
ExceptionlessClient.builder().configurationManager(configuraitonManager).build()

So  in summary an example where someone wants to customize by adding a new plugin, he/she needs following code:
  ConfigurationManager configurationManager =
        ConfigurationManager.builder()
            .configuration(
                Configuration.builder().serverUrl("server-url").apiKey("api-key").build())
            .build();
    configurationManager.addPlugin(
        "plugin-name", 100, (ctx, cm) -> System.out.println("Do something"));
    ExceptionlessClient client =
        ExceptionlessClient.builder().configurationManager(configurationManager).build();

Let me know if I am not clear enough 😅

Combine Configuration and Configuration Manager?
Is there any reason we shouldn't combine these and move services into an aggregate root property?

The only reason I broke them down is to avoid passing ConfigurationManager to its children such as SettingsManager or SubmissionClient. I am strictly against cyclic dependencies.

Server url
Setting the server url should override the config and heartbeat server urls as well (So if you are self hosting it will set all the servers to the same).

By default during creation if heartbeatServerUrl and configServerUrl are not given then it is configured to serverUrl by default. But I don't think setting serverUrl should update all three URLs. The user should update them separately as it can cause confusion.

Simplifying of services.
The module collector, request info collector environment collector and error parser probably will never change in most implementations so it doesn't make sense defining services or interfaces for them. If we simply do the work in the plugin we can simplify services configuration all together. We also moved these into a services property to clean up configuration.

#51

Configuration endpoint
We try to load the configuration settings via submission client from a preconfigured config subdomain https://config.exceptionless.io. I noticed this was missing.

#52

Server url
Setting the server url should override the config and heartbeat server urls as well (So if you are self hosting it will set all the servers to the same).

By default during creation if heartbeatServerUrl and configServerUrl are not given then it is configured to serverUrl by default. But I don't think setting serverUrl should update all three URLs. The user should update them separately as it can cause confusion.

It should because if you are self hosting would be the only time you would set the serverUrl and at that time you'd want all the endpoints to talk to your self hosted service.

Constructor
On a platform like java I think we would know a lot of the defaults that wouldn't change often in terms of services and configuration. Seems like we could default all the items of the Configuration Manager and have a simple empty constructor. The ExceptionlessClient could have a startup method where we pass a Function/Predicate that contains a new configuration object and a user could set any properties on that. Thoughts?

If you see here:
https://github.com/exceptionless/Exceptionless.Java/blob/2a9d5e09af22c0c2f86e7d1a29087a8242377efc/src/main/java/com/exceptionless/exceptionlessclient/configuration/ConfigurationManager.java#L55
I am utilizing the builder pattern. So ideally I don't want someone to initialize the ConfigurationManager using new. Because then he/she needs to pass all the values with lots of nulls I guess.
ConfigurationManager.builder().submissionClient(xxx).build();

So here it would be like calling the all argument constructor with all nulls but with xxx as the value for submission client. So if someone wants to customize the configuration manager he/she can do with this builder and pass it here:
https://github.com/exceptionless/Exceptionless.Java/blob/2a9d5e09af22c0c2f86e7d1a29087a8242377efc/src/main/java/com/exceptionless/exceptionlessclient/ExceptionlessClient.java#L38
So like above, all the classes are following a builder pattern so the client should be built in this way:
ExceptionlessClient.builder().configurationManager(configuraitonManager).build()

So in summary an example where someone wants to customize by adding a new plugin, he/she needs following code:
  ConfigurationManager configurationManager =
        ConfigurationManager.builder()
            .configuration(
                Configuration.builder().serverUrl("server-url").apiKey("api-key").build())
            .build();
    configurationManager.addPlugin(
        "plugin-name", 100, (ctx, cm) -> System.out.println("Do something"));
    ExceptionlessClient client =
        ExceptionlessClient.builder().configurationManager(configurationManager).build();

Let me know if I am not clear enough 😅

That works, Seeing this again I think we should rename configurationManager to configuration. It doesn't manage anything it just hold settings.


text:
Fix revise_auth:model generation command args

When running the command that is present in the readme right now, this is the output:
> rails g revise_auth:model first_name last_name id_number
    generate  model
       rails  generate model first_name email:string:index password_digest:string confirmation_token:string confirmed_at:datetime confirmation_sent_at:datetime unconfirmed_email:string last_name id_number
      invoke  active_record
      create    db/migrate/20230822222738_create_first_names.rb
      create    app/models/first_name.rb
      invoke    test_unit
      create      test/models/first_name_test.rb
      create      test/fixtures/first_names.yml
      insert  app/models/first_name.rb
      insert  db/migrate/20230822222738_create_first_names.rb
🚚 Your Revise auth database model has been generated!

Next step:
  Run "rails db:migrate"

Generating a FirstName model instead of an User one with the added fields

I wonder if there is a way to have it skip the default class_name in that case? It's probably impossible for Rails to know if the first argument is the class or the first attribute.
https://github.com/excid3/revise_auth/blob/main/lib/generators/revise_auth/model_generator.rb#L10C55-L10C55

I think when including other attributes you'll need to specify model name as the first argument.

authors: excid3 francocorreasosa gathuku


text:
Stacking

This might not be considered an issue, however I am attempting to layer a canvas underneath a div tag that contains a large number of custom objects.  The intent is to draw lines between those objects on the canvas and thus make the objects look as if they are connected.  I have tried using z-index both in CSS and directly in the style tag on the canvas element and it is not working, The canvas simply pushing the content down the page.   Is this by design or is there a setting that I am missing?  Thank you!

Hi @bearsystems,
This is in fact not an issue of this library ;-)
z-index alone will not help you place things on top of each other. What you need is position as well.
Here's a demo of that (not my site, I just found that after a quick search): https://www.tutorialrepublic.com/codelab.php?topic=faq&file=css-overlay-one-div-over-another-div
Hope that helps!
Stefan

authors: bearsystems stefanloerwald


text:
Allow Bokeh plots to be glued and pasted

Using the JSON-type output from Bokeh, this creates appropriate HTML and
Javascript nodes in the output when the Bokeh+JSON mimetype is found.

Whoops, I meant to create this against my own fork. Sorry for the noise!

repo: executablebooks/MyST-NB


text:
Write the "Strings" concept

Official docs:
https://book.cairo-lang.org/ch02-02-data-types.html#string-types

Exercism Concepts docs:
https://exercism.org/docs/building/tracks/concepts
Use Python track's concepts as inspiration for format:
https://github.com/exercism/python/tree/main/concepts/

@misicnenad Let me work on this task.

authors: Ephraim-nonso misicnenad

repo: exercism/cairo


text:
flip tests shim

swap order of args to test_equal()

Pete, please don't do that again. Glenn and I are going thru making the tests match the spec. Please revert that change.

OK, reversed

authors: axtens petelomax

repo: exercism/euphoria


text:
sorting-room: add a type-switch concept

Teach about this syntax:
switch v := i.(type) {
case T:
    // here v has type T
case S:
    // here v has type S
default:
    // no match; here v has the same type as i
}

@jmrunkle If you want you can also include this as part of the type assertion concept. Many tracks said that things are a bit easier if the concepts are not cut too small.

If you want you can also include this as part of the type assertion concept. Many tracks said that things are a bit easier if the concepts are not cut too small.

Sounds good. I will do that since it simplifies things.

This is done between the exercise itself and the type-assertion concept

authors: jmrunkle junedev

repo: exercism/go


text:
tree-building: rm stub with full solution

not full but it's not a stub

OK :dancer:


text:
Using rake to build C is extremely weird

My recommendation is to use CMake similar to what is done in the C++ track.
Using rake to build C code is just... weird.  I doubt anyone that is well steeped in C is going to be familiar with rake.

:+1:

I didn't realize that we were doing that. I wholeheartedly agree that we should use CMake (or plain make) for this.

Don't mind either way. I chose Ceedling because it is one of the unit test frameworks recommended in Test Driven Development for Embedded C, and I wasn't sure if Boost was overkill for unit testing C code.

You can use Unity (ceedling's test framework) without ceedling project management. :)

cgreen is a unit test framework designed with the needs of C in mind.  It does mocking via link-time substitution.  However, the framework may not work properly on Windows.  The last time I checked on it a couple years ago, it assumed unix and therefore had problems functioning properly on Windows.
I don't think you want to use a C++ oriented unit-test framework for testing C code.  I don't think it's reasonable to assume that C programmers know C++.  If they did, they wouldn't use C anymore :smile_cat:.

"Exception names should end with a trailing 'Error'."

Unity is ANSI C, so works everywhere. :)

I don't think you want to use a C++ oriented unit-test framework for testing C code.

Unity is pure C :)

There's also greatest, which doesn't depend on anything and is actively un-opinionated about development style.

It looks like everything is using make at this point.

authors: LegalizeAdulthood kytrinyx lpil ryanplusplus silentbicycle sunzenshen

repo: exercism/xc