andig
andig
I'm using the linter action in https://github.com/andig/evcc/pull/497/checks?check_run_id=1474850871: Go artefacts are already cached: steps: - name: Setup uses: actions/setup-go@v2 with: go-version: ^1.14 id: go - uses: actions/cache@v2 with: path: | ~/go/pkg/mod...
While both might be problematic in terms of GC or race detection, CGO can introduce additional issues for cross-compiling. It would be great if CGO was recognizable on its own....
Refs https://github.com/evcc-io/evcc/issues/13056 Also renames `targetsoc` to `limitsoc` because it really _is_ a limit. /cc @naltatis @premultiply
Refs https://github.com/evcc-io/evcc/issues/10379 Experimental
Fix https://github.com/evcc-io/evcc/issues/13007 by adding a method to validate the set current against actual value
Fix https://github.com/evcc-io/evcc/issues/7193 This PR attaches the event hub to the cache as downstream consumer. Hence event hub always has access to synchronised cache.
Add the following vehicle settings to config ui: - mode - mincurrent - maxcurrent - phases - priority