Integration of Zaptec Go 2?

[jvdlely]

Hi all,

A few days ago, a Zaptec Go 2 wallbox was installed. I tried to configure the Zaptec Go 2 in EVCC but it does not work. I am aware that this newest Zaptec wallbox is not in the list of the supported Zaptec wallboxes. Nevertheless, I checked the API pages on the Zaptec web site and could not find a difference between the Zaptec Go and Zaptec Go2. I hoped I could at least add the Zaptec Go 2 charger with 'normal Zaptec Go capabilities. From the API pages on the Zaptec web site, I can communicate with my Zaptec Go 2 charger.
My EVCC runs in a docker. I also tried EVCC on a Raspberry Pi but also on the Pi, I could not add the Zaptec Go 2. My car (KIA Ev3) and grid meter (Homewizard P1) are working fine in EVCC.
I used the trail sponsor token to test.
Am I doing something wrong? Or should I wait till a new template for the Go2 is developed? Of course I am willing to sponser that with a token :-)
Hope someone can me guide to the right direction! Thanks.

Best regards,
Jan van der Lely (NL)

This is the error I get:
'Apr 06 14:30:33 evcc[2409140]: [main ] INFO 2025/04/06 14:30:33 evcc 0.200.4

Apr 06 14:30:33 evcc[2409140]: [main ] INFO 2025/04/06 14:30:33 using config file: /etc/evcc.yaml
Apr 06 14:30:33 evcc[2409140]: [db ] INFO 2025/04/06 14:30:33 using sqlite database: /var/lib/evcc/evcc.db
Apr 06 14:30:39 evcc[2409140]: [main ] INFO 2025/04/06 14:30:39 listening at :7070
Apr 06 14:30:39 evcc[2409140]: [main ] FATAL 2025/04/06 14:30:39 charger [my_charger] cannot create charger 'my_charger': cannot create charger type 'template': yaml: line 3: did not find expected key:
Apr 06 14:30:39 evcc[2409140]: type: zaptec
Apr 06 14:30:39 evcc[2409140]: id: xyz
Apr 06 14:30:39 evcc[2409140]: user: xyz
Apr 06 14:30:39 evcc[2409140]: password: xyz
Apr 06 14:30:39 evcc[2409140]: [main ] FATAL 2025/04/06 14:30:39 will attempt restart in: 15m0s
Apr 06 14:30:44 evcc[2409140]: [main ] ERROR 2025/04/06 14:30:44 version check failed: Get "https://api.github.com/repos/evcc-io/evcc/releases/latest": dial tcp: lookup api.github.com: i/o timeout (installed: 0.200.4)`

This is my config:

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

log: debug
levels:
cache: error

interval: 30s

sponsortoken: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJldmNjLmlvIiwic3ViIjoidHJpYWwiLCJleHAiOjE3NDQ5MDkyMDAsImlhdCI6MTc0MzYxMzIwMCwic3BlIjp0cnVlLCJzcmMiOiJtYSJ9.jVHPPS0pR5g8_IujRGpHEHLUBmfnR_tyECWP-UfQSOU

meters:

• type: template
  template: homewizard
  usage: grid
  host: 192.168.178.163
  name: grid1

site:
title: B24
meters:
grid: grid1

loadpoints:

• title: Garage # display name for UI
  charger: my_charger # charger

chargers:

• name: my_charger
  type: template
  template: zaptec
  id: xyz
  user: xyz
  password: xyz

[mfuchs1984]

According to the datasheet, it supports ocpp, so you should be able to use
https://docs.evcc.io/en/docs/devices/chargers#ocpp-16j-compatible-charger-with-smart-charging-profile

[jvdlely]

Thanks for the tip! I will test this tonight when I am at home.

[Robert28021962]

Ha, ik heb evcc en zaptec go2 gekoppeld. Dat werkt maar ik wil instellen dat hij uitsluitend op de beschikbare zone energie laad en niet bij plust uit het net. Is dat jou gelukt? Ik weet niet wat ik waar moet instellen….. kan jij me helpen?

[StefanSchoof]

charger [my_charger] cannot create charger 'my_charger': cannot create charger type 'template': yaml: line 3: did not find expected key:

Is it possible that your indentation in the yaml is not right?

Please format your config as code. https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#fenced-code-blocks

[jvdlely]

Hi Stefan,

This is my yaml:

log: debug
levels:
  cache: error

# unique installation id
# plant: d65c3b4988b1d477e18c0e0650d9e40edc9d22adfd6f8cb3018aee46d02f8015

interval: 30s # control cycle interval

# trial token, valid until 2025-04-17
sponsortoken: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJldmNjLmlvIiwic3ViIjoidHJpYWwiLCJleHAiOjE3NDQ5MDkyMDAsImlhdCI6MTc0MzYxMzIwMCwic3BlIjp0cnVlLCJzcmMiOiJtYSJ9.jVHPPS0pR5g8_IujRGpHEHLUBmfnR_tyECWP-UfQSOU


meters:
- type: template
  template: homewizard 
  usage: grid  
  host: 192.168.178.163  
  name: grid1


site:
  title: B24
  meters:
    grid: grid1

loadpoints:
  - title: Garage # display name for UI
    charger: my_charger # charger
    # vehicle: my_car # default vehicle

chargers:
  - name: my_charger
    type: template
    template: zaptec
    id: xxxx
    user: xxxx
    password: xxxx

[rea7mic]

Hello @jvdlely,
as @StefanSchoof already mentioned please post your yaml code, maybe some typo or other code related stuff is glitching.

On my side an Zaptec Go is running (without OCPP), but i want upgrade later this year to Go 2 model because of auto 1p-3p switching and other cool features.

If you want, you can also try the new evcc WebUI config to add Zaptec charging station. I had migrated all my settings from yaml to WebUI, maybe not all hardcore custom user settings are present, but it works really nice. Thanks to evcc-Team.

[jvdlely]

Hello @rea7mic,
I also choose the Go 2 because of the 1p/3p switching :-)
I also tried to add the charger via the Web GUI but I got exactly the same error as in my first post. I must be doing something wrong....

[rea7mic]

Hi, that's weird.. we need to isolate the error, step by step. thanks for sharing your evcc config. I had compared your settings with my old saved evcc.yaml config and it seems the config is OK. Another point what the logfile output reported is api.github.com timeout and evcc version check failed.

Please, can you double check from evcc server / Raspberry command line that external internet access is 100% working? You said your car and powermeter is ok, but we can try the following commands:

ping -c5 api.github.com

and

ping -c5 api.zaptec.com

you should see ping responses from github and zaptec - in case there is an timeout, then we know something is "blocked" and finally with wget, we can test the response from Zaptec API-Endpoint

wget -O- https://api.zaptec.com

200 OK is the perfect response.

Greetings
Michael

[jvdlely]

Hi Michael,

All pings work fine and the wget is also ok. Commands were executed from the EVCC docker.
I edit the yaml file in Visual Studio Code with yaml linting enabled. No yaml errors are showing.

Greetings, Jan

PING api.github.com (140.82.121.5): 56 data bytes
64 bytes from 140.82.121.5: seq=0 ttl=51 time=23.106 ms
64 bytes from 140.82.121.5: seq=1 ttl=51 time=17.016 ms
64 bytes from 140.82.121.5: seq=2 ttl=51 time=17.681 ms
64 bytes from 140.82.121.5: seq=3 ttl=51 time=19.321 ms
64 bytes from 140.82.121.5: seq=4 ttl=51 time=19.301 ms

--- api.github.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 17.016/19.285/23.106 ms
/app # ping -c5 api.zaptec.com
PING api.zaptec.com (40.113.89.243): 56 data bytes
64 bytes from 40.113.89.243: seq=0 ttl=111 time=30.386 ms
64 bytes from 40.113.89.243: seq=1 ttl=111 time=26.894 ms
64 bytes from 40.113.89.243: seq=2 ttl=111 time=26.760 ms
64 bytes from 40.113.89.243: seq=3 ttl=111 time=26.898 ms
64 bytes from 40.113.89.243: seq=4 ttl=111 time=27.582 ms

--- api.zaptec.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 26.760/27.704/30.386 ms
/app # wget -O- https://api.zaptec.com
Connecting to api.zaptec.com (40.113.89.243:443)
writing to stdout
<!doctype html>
<html lang="en">
<title>api.zaptec.com</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no"/>
<style>
    html, body {
        height: 100%;
    }

    body {
        margin: 10px 20px;
        background-color: #222;
        font-family: sans-serif;
        font-size: .7em;
        color: #ccc;
        overflow: hidden;
    }

    a:link, a:visited, a:hover {
        color: #ccc;
    }

    #logo {
        top: 25%;
        position: relative;
        height: 100px;
        text-align: center;
        width: 400px;
        margin-left: auto;
        margin-right: auto;
    }

    #links {
        position: absolute;
        bottom: 10px;
        left: 20px;
    }

    #footer {
        position: absolute;
        bottom: 10px;
        right: 20px;
        text-align: right;
    }

    ul {
        list-style-type: none;
    }

    ul, li {
        padding: 0;
        margin: 0;
    }

    /* Logo SVG style */
    .cls-1 {
        fill: #fff;
    }

    .cls-2 {
        fill: none;
        stroke: #fff;
        stroke-miterlimit: 10;
        stroke-width: 7px;
    }
</style>
<script type="text/javascript">
    document.addEventListener("DOMContentLoaded", async function () {
        const url = location.href;
        const match = url.match(/\/([^\/]*).azurewebsites.net/);
        const serverName = match ? match[1] : 'api.zaptec.com';
        document.title = serverName;
        document.getElementById('logoTitle').innerText = serverName;
        
        try {
            const response = await fetch('https://api.zaptec.com/api/constants');
            const jsonData = await response.json();
            document.getElementById('version').innerText = jsonData.Version;
        } catch (e) {
            document.getElementById('version').innerText = "0.0.0";
        }
        
        document.getElementById('currentYear').innerHTML = new Date().getFullYear();
        document.getElementById('footer').style.display = 'block';

    });
</script>
<body>
<div id="logo">
    <span id="logoTitle"></span>
    <svg xmlns="http://www.w3.org/2000/svg" id="Layer_1" data-name="Layer 1" viewBox="0 0 496.35 216.59">
        <title>white</title>
        <path class="cls-1" d="M246.87,130.36v6.72H203.1v-5.92l33.77-44.81H203.5V79.63h43.05v5.92l-33.76,44.81Z"/>
        <path class="cls-1"
              d="M273.64,136.36a19,19,0,0,1-7.48,1.44,14.63,14.63,0,0,1-9.88-3.32,10.85,10.85,0,0,1-3.88-8.68,11,11,0,0,1,3.72-8.64q3.72-3.28,12.12-5L278.4,110v-1.76a7.22,7.22,0,0,0-2.08-5.6q-2.08-1.92-6.16-1.92a10.44,10.44,0,0,0-6.28,1.76,9.23,9.23,0,0,0-3.4,5.36l-6.8-1.76a15.48,15.48,0,0,1,6.08-8.52,18,18,0,0,1,10.64-3.17q7.28,0,11.2,3.53t3.92,10v20.4a3,3,0,0,0,1.16,2.68,4.29,4.29,0,0,0,3.32.28v5.76q-4.87.64-7.6-.56a5.59,5.59,0,0,1-3.36-4.16A13.16,13.16,0,0,1,273.64,136.36Zm1.48-7a8,8,0,0,0,3.28-6.52v-7.2l-8.16,1.76q-6,1.2-8.36,3.08a6.08,6.08,0,0,0-2.36,5,5.94,5.94,0,0,0,2,4.76A8.16,8.16,0,0,0,267,132,12.57,12.57,0,0,0,275.12,129.36Z"/>
        <path class="cls-1"
              d="M325.65,136.24a17.13,17.13,0,0,1-7.72,1.72,15.82,15.82,0,0,1-7.6-1.84A13.35,13.35,0,0,1,305,131v20.49h-7.2V95.23H305v6.09a14.19,14.19,0,0,1,5.4-5,15.72,15.72,0,0,1,7.56-1.84,17.5,17.5,0,0,1,7.76,1.72,16.68,16.68,0,0,1,6,5A22.55,22.55,0,0,1,335,108a29.7,29.7,0,0,1,0,16.44,21.49,21.49,0,0,1-3.4,6.84A16.68,16.68,0,0,1,325.65,136.24Zm-17.52-31.72q-3.31,3.75-3.32,10.24v3q0,6.41,3.32,10.16a11.55,11.55,0,0,0,17.44-.44q3.33-4.2,3.32-11.24T325.61,105a11.6,11.6,0,0,0-17.48-.44Z"/>
        <path class="cls-1"
              d="M349,135q-2.59-2.48-2.6-7.92V101.4h-6.48V95.23h6.48V83h7.12V95.23h9.52v6.17h-9.52V126a5.38,5.38,0,0,0,1.24,4c.83.8,2.36,1.2,4.6,1.2a20.86,20.86,0,0,0,2.44-.12c.67-.08,1.38-.2,2.12-.36v6.16a23.28,23.28,0,0,1-3,.48,31.89,31.89,0,0,1-3.28.16C353.62,137.48,350.75,136.66,349,135Z"/>
        <path class="cls-1"
              d="M380.87,136.32a17,17,0,0,1-6.36-4.84,20.06,20.06,0,0,1-3.8-6.8,27.79,27.79,0,0,1,0-16.8,20.23,20.23,0,0,1,3.76-6.88,17.55,17.55,0,0,1,6.32-4.89,18.82,18.82,0,0,1,7.92-1.68q8.25,0,13,5.61t4.8,14.88v2.4H376.27q.32,6.56,3.76,10.48a11.33,11.33,0,0,0,9,3.92,11.56,11.56,0,0,0,7-2.12,10.13,10.13,0,0,0,3.84-5.88L406.2,126a17.07,17.07,0,0,1-6.49,8.84A18.32,18.32,0,0,1,389,138,19.81,19.81,0,0,1,380.87,136.32Zm-.08-32.76a14.42,14.42,0,0,0-4.12,8.24h22.56a12.09,12.09,0,0,0-3-8.16,9.89,9.89,0,0,0-7.68-3A11,11,0,0,0,380.79,103.56Z"/>
        <path class="cls-1"
              d="M423.24,104.92q-3.44,4.23-3.44,11.28t3.44,11.24a11.19,11.19,0,0,0,9.12,4.2,10,10,0,0,0,6.72-2.32,11.67,11.67,0,0,0,3.68-6.56l6.41,3a16.25,16.25,0,0,1-6.13,8.92A17.49,17.49,0,0,1,432.36,138a20.1,20.1,0,0,1-8.16-1.64,17.31,17.31,0,0,1-6.4-4.76,20.24,20.24,0,0,1-3.88-6.88,27.9,27.9,0,0,1,0-17,20.14,20.14,0,0,1,3.88-6.88,17.44,17.44,0,0,1,6.4-4.77,20.27,20.27,0,0,1,8.16-1.64A17.43,17.43,0,0,1,443,97.68a16,16,0,0,1,6.05,8.76l-6.25,3.12a11.64,11.64,0,0,0-3.68-6.56,10,10,0,0,0-6.72-2.32A11.14,11.14,0,0,0,423.24,104.92Z"/>
        <path class="cls-1" d="M82.83,133.22l30.52-41.17H95.8l-4-6h33.1l-24.83,34.84,45.62-7.56a.26.26,0,0,1,.14.49Z"/>
        <circle class="cls-2" cx="108.43" cy="108.44" r="57.93"/>
    </svg>
</div>
<div id="links">
    <ul>
        <li><a href="https://zaptec.com">https://zaptec.com</a></li>
        <li><a href="https://portal.zaptec.com">https://portal.zaptec.com</a></li>
        <li><a href="https://api.zaptec.com/help">API documentation</a></li>
        <li><a href="https://zaptec.com/downloads/ZapChargerPro_Integration.pdf" target="_blank">Integrating with Zaptec
            charging systems</a></li>
    </ul>
</div>
<div id="footer" style="display:none">
    api.zaptec.com / version <span id="version"></span><br/>Copyright 2017 to <span id="currentYear"></span> Zaptec
    Charger AS
</div>
</body>
</html>

-                    100% |*******************************************************|  5851  0:00:00 ETA
written to stdout
/app # ```

[jvdlely]

Hi all,

First, thanks everyone for the suggestions to solve the problem of adding the Zaptec Go 2 charger to EVCC. Finally I found out what was wrong: my password for the charger had a leading zero. I read in the docs that I should enclose the password then with quotes. But that did not help .While getting more and more frustrated by the hour, I decided to change my password to something else, without a leading zero. And guess what: the charger was added right away! I guess I should report this as a bug?
Well, one happy guy over here, ready to experiment with EVCC the coming days! Thanks again for the suggestions!

[rea7mic]

Hello Jan, that are wonderful news - and important for other Zaptec Go 2 users in the near future.