Internet and network requirements for ZapCharger PRO
Wifi 2.4 GHz, IEEE 802.11 b/g/n (channel 1-11)
PLC – HomePlug Green PHY®,10 Mbit/s
DHCP server with sufficient IP addresses - one for each connected device
NOTE: If the WiFi 2.4GHz wireless network is set up with automatic channel selection, then ZapCharger PRO may lose and / or not be able to connect to the wireless network if the WiFi network switches to channel 12 and / or 13.
All traffic and communication between charging stations and the cloud solution is encrypted.
All the following network services are required for the ZAPTEC charging stations to function together with ZAPTEC Portal (Cloud solution, ZapCloud). All ports mentioned are outgoing, and have to be opened in any active firewalls. ZAPTEC charging stations connects to its required services even if it is behind NAT without any incoming port mappings.
TCP Port 8883: zapcloud.azure-devices.net
A connection to Azure IoT Hub, using MQTT over TLS, serves as the main communication channel between the ZAPTEC charging stations and ZapCloud. The state of the charger is sent to ZapCloud, and control commands (like start/stop charging) is received. The communication is encrypted using TLS, the server´s certificate is verified by the ZAPTEC charging station, and the server verifies the charger when it connects using a unique password set during production.
More information about Azure IoT Hub can be found here:
TCP Port 443 (multiple domains)
The ZapCharger Pro connects to ZapCloud using HTTPS to download firmware updates. This communication is encrypted, and the ZAPTEC charging station verifies the certificate of the server.
The following domains are used during firmware updates:
UDP Port 68
DHCP is used on the local network to assign an IP-address to the ZapCharger Pro and to provide the IP address of the DNS server to be used.
UDP Port 53
DNS is used by the ZAPTEC charging station to look up the IP-address of the domains used to communicate with ZapCloud. ZAPTEC charging station will use the DNS server(s) specified by the DHCP server.
UDP Port 123: no.pool.ntp.org
As some ZAPTEC charging stations does not have a real time clock, a connection to a network time protocol server is required to have an up to date clock on the charging station. The correct time and date is required to authenticate with ZAPTEC Portal (ZapCloud).
The NTP-server used by the ZAPTEC charging station is no.pool.ntp.org.
This hostname is fixed and cannot be changed by the user at this point.