Zaptec network requirements and communication protocols

Internet connection requirement

To function properly, all Zaptec chargers require an internet connection to communicate with Zaptec Cloud. The available communication methods depend on the specific charger model: 

Supported communication methods by model

  • Zaptec Pro: 4G LTE-M, Wi-Fi, PLC (Power Line Communication).
  • Zaptec Go: 4G LTE-M, Wi-Fi.
  • Zaptec Home 4G (Expired): 4G LTE-M (only for ZCH04 <), Wi-Fi.
  • ZapCharger Pro (Expired): 4G LTE-M (only for ZCS030772 -31071), Wi-Fi.

Each charging station uses approximately 5MB per charging cycle. and the anticipated daily data consumption for a Zaptec Pro is around 3 MB. 

 

 

How to connect to network

For step-by-step instructions on connecting your Zaptec charger to the internet, refer to the following guides:

 

 

Network security and communication protocols 

All network traffic and communication between Zaptec charging stations and Zaptec Cloud are encrypted. The following network services and ports must be open for Zaptec Pro to function with Zaptec Portal. All listed ports are outgoing, and you have to open them in active firewalls. Notably, Zaptec Pro links to the necessary services without opening incoming ports, even if they are located behind a NAT.


Supported protocols  

  • 4G LTE-M1: eSIM från Telenor
  • Wi-Fi 2.4GHz: IEEE 802.11 b / g / n (fast kanal 1 - 11)
    Minimum signal strength per charging station: -74 dBm.  
  • Powerline Communication (PLC): HomePlug Green PHY®, 10 Mbit/s

 

 

Communication and network requirements 

1. MQTT

  • Port: TCP port 8883
  • Domain: zapcloud.azure-devices.net
  • Function:
    • A connection to Azure IoT Hub, which uses MQTT over TLS, acts as a primary communication channel between Zaptec Pro and Zaptec Portal.
    • The condition of the charger is transmitted to Zaptec Portal, and it receives control commands such as start/ stop charging.
  • Security:
    • Communication is encrypted using TLS v1.2.
    • Server certificate is verified by Zaptec Pro.
    • When it is connected, the server verifies the charger using a unique password that is generated during production.
  • More info on Azure IoT Hub: https://docs.microsoft.com/en-us/azure/iot-hub/about-iot-hub

 

2. HTTPS

  • Port: TCP port 443 (multiple domains)
  • Function:
    • Zaptec Pro connects to Zaptec Portal by means of HTTPS in order to download firmware updates.
  • Security:
    • This communication is encrypted. Zaptec Pro verifies the server certificate before the update is download.
    • Firmware update is verified cryptographically before being installed.
  • Domains used during firmware updates:
    • zapcloud-api.azurewebsites.net
    • devices.zaptec.com
    • api.zaptec.com

3. Outgoing ports

Port Type port Domain(s)
123 UDP no.pool.ntp.org
443 TCP

zapcloud-api.azurewebsites.net

devices.zaptec.com

api.zaptec.com
8883 TCP zapcloud.azure-devices.net
53 DNS

 

4. DHCP

  • Port: UDP port 68
  • Function:
    • DHCP is used on the local network to assign an IP address to Zaptec Pro and give the IP address to the DNS server. DHCP server with a sufficient number of IP addresses – one for every device connected.
  • Requirements:
    • When installing with dynamic IP addresses (DHCP), the network must be dedicated.
    • If the network is shared with others, it is easy to run out of IP addresses, resulting in the chargers risking the connection.
    • If the lease time is too long, it can take time for the chargers to get a new assigned IP address. Since the chargers are individually connected, each charger requires its own IP address, so make sure there is enough in the DHCP.
  • Security: 
    • WPA security: WPA2 for Zaptec Pro.

 

5. DNS

  • Port: UDP port 53
  • Function:
    • Zaptec Pro uses DNS to look up the IP addresses of the domains used to communicate Zaptec Portal.
  • Fallback DNS server (if DHCP fails to specity one):
    • If the DHCP server does not specify a DNS server, or if it does not respond promptly, Zaptec Pro uses the DNS server (or DNS servers) specified by the DHCP server, in addition to Google (8.8.8.8) and Cloudflare (1.1.1.1) DNS servers.

 

6. NTP

  • Port: UDP-port 123 no.pool.ntp.org
  • Function:
    • If the Zaptec Pro real-time clock is wrong, the charging station cannot authenticate itself with Zaptec Portal. Zaptec Pro has to be connected to an NTP server to update the internal clock. This communication takes place via UDP port 123.
  • NTP server used by Zaptec Pro: no.pool.ntp.org.
  • The hostname used for NTP is static. It cannot be changed by the user at present.

 

 

 

 

Updated

Was this article helpful?

39 out of 99 found this helpful

Have more questions? Submit a request