This article provides a technical reference for the network requirements, security standards, and communication protocols used by Zaptec charging stations. For setup and troubleshooting, see the separate guides linked below.

• Zaptec Go: Click here to learn how to connect to Wi-Fi.
• Zaptec Pro: Click here to learn how to connect to Wi-Fi.

Supported communication methods by model

Network requirements

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.

• Wi-Fi:
  • 2.4GHz (IEEE 802.11 b/g/n), channels 1–11
  • Minimum signal strength: -74 dBm per charging station
  • WPA2 security recommended
• Powerline Communication (PLC):
  • HomePlug Green PHY®, 10 Mbit/s
• 4G LTE-M:
  • eSIM provided by Telenor (where applicable)

Communication and network requirements 

MQTT

• Port: TCP port 8883
• Domain: *.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.
  • The 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

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 downloaded.
  • Firmware update is verified cryptographically before being installed.
• Domains used during firmware updates:
  • devices.zaptec.com
  • api.zaptec.com
  • firmwaredeployment.zaptec.com

Outgoing ports

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.

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 specify 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.

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 26 September 2025 12:42